Related
Okay, I used a G1 since October 20th, and rooted a few months later when I felt the process was easy enough and could be reversed. I'm not sure how long it'll take on the myTouch, but I'm thinking I'll wait and keep my G1 by my side for Tethering purposes, only because I'm scared to death of breaking the ROM. I mean, we don't even have the original ROM do we? Or at least the SAPPIMG.NBH with all of the myTouch factory software on it? The DREAIMG.NBH used to get back to RC29 was a life saver whenever I goofed things up on my G1. I'd just reflash it from the phone, on the road, and then could do all the rooting on the device. The biggest problem I'm running into is that I'm stuck on a 4 yr old iBook G4, so making the goldcard is going to be weird. I'll probably have to find a way to do it through MS VirtualPC with Windows XP and turn on USB pass-through. Any ideas?
Does anyone know of a way to backup the myTouch ROM before digging in too deep? I love nandroid's capabilities, and the cyanogen recovery 1.4 is of GREAT use on my G1, is it compatible with the myTouch? I'm sure some of this is available by digging through the threads, but this computer's 800x600 screen size is KILLING me (the laptop display cracked, so I'm stuck on an external monitor, and maximum output is 800x600)
Plus, if I have to do any exchanges, it's best to keep everything at factory before sending it in. And I will definitely need to do that should I have any problems. So a factory SAPPIMG would be great. Know how to get ahold of one? Anyone?
Wow, 85 reads, no replies rather surprised, but a regular search on Google for the MyTouch SAPPIMG ROM pulled up a page here on xda...
http://forum.xda-developers.com/showthread.php?t=533641
Is this REALLY the myTouch ROM? even if it's the one from before the "Work Email" app came as an OTA (COC1 is the build) that'd be fine, the phone will pull that later on and I don't use it anyway...
Any ideas on whether or not this particular "update.zip" style ROM will refresh me back if i get in a bind and break android? I'm putting some hope on it. According to what's in the rooting thread, the ION's radio ROM is the same as the myTouch's shipping radio, right? Other than that, the SPL is the only other thing that'd need replaced before doing a warranty exchange, so that's all that's left to "unroot" the device. Anyone have access to that, or have a way to dump it?
Allong the same line as this... I am in Japan on a DOCOMO HT-03. Doubt there is a rom avail around here... I havent gotten in to the rooting yet.. But can i use nandroid to creat a back up of my own(with all of my settings).. Or even Extract the orignal rom, to post here as a repository for anyone else...
I've been flashing different roms for awhile, and decided to go from OpenEclair to one of the "new" ones that requires the new SPL and radio. Went fine. No problem. Used the new rom for about a week, but really got screwed by a massive bug I found in it today, so I wanted to go back to my OE nandroid backup.
I went to reflash to my original SPL. It was a ZIP, so I treated it like a ROM and used AmonRa's recovery to flash it. Said it went fine. Rebooted, expecting to get back into fastboot and flash my radio.
I can't get into fastboot. All it does is show Rogers then HTC Magic in a boot loop. ADB devices shows nothing, fastboot devices shows nothing. Back and Power doesn't work. Home back and power doesn't work. Vol down doesn't work.
Am I as bricked as I think I am?
Yes, it sounds bricked. The proper method to go from 6.x --> 3.x radios and matching SPL is to use fastboot. You have to flash radio and SPLs in matching pairs, you can only use the update.zip format for SPL when it already matches your radio (ie. 1.33.2005 ---> 1.33.2010 w/ the 3.22.20.17 radio).
I believe you should normally flash radios first as well. If you don't get it fixed id like to buy it, need parts. Anyways, most the time when you can't get into fastboot or anything else, it is bricked. Best bet is to get warranty if you still have it. Unfortunately the new phones won't be rootable yet
its best to follow guides when downgrading/upgrading spl/radio (cursordroids for example) when not knowing completely what your doing.. sorry my friend.. sounds like your phone is now a boat anchor
i flashed a 1.33.2010 SPL with a 3.?? radio and now all i get is the logo screen no fast boot, i can enter debug mode (action button) but nothing else sounds like its bricked, but hey its been fun
to be honest i was in this situation last week after leaving my phone off for a hour fastboot was working
oh this is sounding more promising, see what happens when i get home, i see there have been a few people about that have been in the same situation and got out of it so fingers crossed
unfortunantly none of the above worked, wow after 10 years of flashing **** i finally killed something !!.... mind you i still have to make up the serial cable this weekend and see if i can fix it like that
Oh well, you guys should know better ... radio/spl/recovery upgrade/downgrade is a child play, if you do it with fastboot and in the correct order (radio - spl - recovery).
I just hope you can get your Magic back to life.
yeah i was a little distracted at the time, never mind, im going to boot into the radio bootloader and see if i can fix it this weekend, fingers crossed
ruimoura said:
Oh well, you guys should know better ... radio/spl/recovery upgrade/downgrade is a child play, if you do it with fastboot and in the correct order (radio - spl - recovery).
I just hope you can get your Magic back to life.
Click to expand...
Click to collapse
i have flashed not in that order and never bricked and also i have flash different things like radios in different orders and no brick
Just a (long) update on trying to get the phone repaired...
First thanks to bcrook, KAwAtA and digitaljeff for the prompt replies at confirming my screw up.
Ruimoura, why even post? Nothing helpful, and not even commiserating. "Oh well, you guys should know better ...". I hope someone is there when you make a mistake to rub it in.
Anyway...
This was a Rogers Magic used in the states on AT&T.
Heres what happened if anyone is interested:
I searched the forums and tried every trick I could find, including the gold card method; no luck. To be honest, I'm not sure I did the gold card right, but I tried my best. I even looked into the jtag idea, but it seems like more work then its worth to me, and no one seems to have been successful with it yet.
I then called HTC to find out what a repair would cost. HTC said they don't have that phone in their parts list and can't service it because it is a Rogers phone and they don't work with Rogers. They told me I would have to call Rogers for service.
Called Rogers and explained the situation (carefully; blaming the 911 update ). Rogers lectured me on how dare I take their phone off their network, and that they have no interest in helping me at all and "contacting HTC is easy. Whats wrong with you?". I explained that I contacted HTC and they said to contact Rogers. They said (after some fighting) call this number and then gave me the same number HTC has on their website.
Called HTC again and explained the situation. After checking their parts database, the person I was talking to this time confirmed what the person I previously talked to said. HTC doesn't service the Rogers Magic but he felt, like I, that was kinda crazy and called the repair location directly to confirm. After a bit of time on hold, he came back and said that Rogers phones are serviced through a place called FutureTel in canada, and gave me their contact number.
I called FutureTel and it was a very short conversation. "What store are you calling from?" I Explained I wasn't calling from a store and why I was calling. "We only work with Rogers directly. We won't support you." and they hung up.
I have to say, both times I called HTC the people I talked to were incredibly polite and honestly seemed like they wanted to help. Rogers and FutureTel seemed like they truly resented having to pick up the phone. Maybe its a cultural thing I'm not aware of, but it honestly seemed, from the first word, that they hated talking to me.
So, as near as I can tell, you can't even pay someone to fix a Rogers HTC Magic.
At this point I'm back suffering on my old WinMo phone and desperately hoping that the rumored March 23 release date for the Verizon Nexus One is legitimate since T-Mobile isn't really an option.
Hi there, today I received my HTC Inspire 4G, so I start to play with it and I notice that the screen or the resolution is very poor, I compare with my friend Inspire 4G, and his HTC the screen resolution is awesome, the colors are so nice... while mine the resolution is awful like low pixels..
Is this is a bug or something or it is a factory problem with the video card driver or something???
anyone with this screen resolution issue and can this be fixed or maybe return it to the store?
hmmm curious to see what this looks like you got any pictures by chance?
how can i take a screen shot without rooting it...
with a camera...
this is what I'm taking about
Yea it shouldn't look like that. For simplicities sake, I'd take it back and just have them replace it.
Sent from my Desire HD using XDA Premium App
mudknot2005 said:
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
I know it should look like this...
damn... just have it for 3 hours
thanks a lot for your help
I mean you could go through rooting it s-off and flash the stock ruu. To see if it was just a bad flash from the factory, but honestly it would just be easier to take it back get a new one and make sure it is fully operational.
mudknot2005 said:
I mean you could go through rooting it s-off and flash the stock ruu. To see if it was just a bad flash from the factory, but honestly it would just be easier to take it back get a new one and make sure it is fully operational.
Click to expand...
Click to collapse
yeah, I could try it, I bought it from amazon wireless, and I'm from another country, so returning it it's gonna take long..
should I root it and try re-flashing the RUU?
Well if you root and s-off might as well flash a stock/custom rom. It might solve your problem it might not. If it doesn't you can always revert back to stock and ship it back. I recommend the Ace Hack kit. It takes a little longer then the one click, but you won't run into any trouble after doing it. Least you will know if its a a software or hard ware issue.
mudknot2005 said:
Well if you root and s-off might as well flash a stock/custom rom. It might solve your problem it might not. If it doesn't you can always revert back to stock and ship it back. I recommend the Ace Hack kit. It takes a little longer then the one click, but you won't run into any trouble after doing it. Least you will know if its a a software or hard ware issue.
Click to expand...
Click to collapse
I already downloaded the ACe Hack kit, but dont know how where to begin...
I already make the Gold Card
Once you have the gold card made the rest is simply typing scripts in command prompt, plus a bit on the phone, provided you have adb working and your device is recognized.
Extract the contents of the hack kit and open the readme html file for the instructions.
limx said:
yeah, I could try it, I bought it from amazon wireless, and I'm from another country, so returning it it's gonna take long..
should I root it and try re-flashing the RUU?
Click to expand...
Click to collapse
where u from? u are SCARING ME , im from venezuela and im planning on buying the inspire 4g from amazon TODAY!
Chad_Petree said:
where u from? u are SCARING ME , im from venezuela and im planning on buying the inspire 4g from amazon TODAY!
Click to expand...
Click to collapse
I'm from Panama, but the phone was shipped to NY to a friend, so I can return it without problem..
Well last night I rooted it, downgrade it, flashed with the original rom, flashed to Coredroid rom, flashed to Android Revolution rom, in every rom it has the pixalation and the screen resolution problem, and unrooted it, flashed with the original rom again, and all is like new..
so it is a hardware issue.. today I'll call to amazon custom service to make the replacement..
I'll post when they replaced the phone and have it again..
thx for your help mudknot2005
ok, i called and talked to them, it's a hardware issue , so I will send it back on Monday, wait about a week and got a new phone...
I'm glad they gonna replace it..
Anytime that is what we are here for. I am guessing you turned s-off back on? If not I would do that before you ship it. To make sure all you need to do is boot into hboot, holding down volume down and power while it is restarting.
Glad to hear amazon is going to handle the issue .
I got 3 in a row with bad screens. Made me wonder if there was a bad shipment here in Pittsburgh. I wound up getting an atrix but am taking it back also. It's very buggy, I've had to do battery pulls almost daily due to the phone freezing up.
I hope your able to solve your problem. I live close to an att store so I didn't try any of the mentioned methods.
Best of luck with it.
Sent from my MB860 using XDA Premium App
Entire screen resolution issue
Sorry to hear everyone else is having problems, too. What led up to my issue is I tried RC Kingdom's newest ROM, and then all hell broke loose on my poor screen. And yes, I followed the youtube video on his page to make sure I installed it properly. It was sharp and crisp before I installed that ROM. I have tried everything in this thread to resolve my resolution issue, but to no avail. Tried using the stock RUU to reset back to factory. No cigar. Then I re-rooted and put my backup from nandroid on. No bueno. After that I installed CoreDroid's newest rom, RCKingdom's newest rom, and Virtuous's newest rom. Again, no luck. And I did this all from both 4ext recovery, and CWM. Attached I have provided 4 screenshots from various areas to show it's a ROM-wide issue. If anyone could help, I would <3 you forever!
If there is anything I am lacking to provide assistance, please don't hesitate to ask. I may be a noob, but I used the forum search tool, google, didn't make a new thread, and tried resetting back to stock, so please be gentle.
EDIT: I'm looking more closely at the screen, and it looks like the picture on the screen isn't filled up to the edges. Can anyone else either confirm of deny this? Thanks!
EDIT2: The edge of the picture on the screen definitely doesn't match up to the phone screen. From what I've researched on google, it could mean bad flash memory, either from time, or a bad flash. Does anyone else have ideas?
snowman0269 said:
Sorry to hear everyone else is having problems, too.
Click to expand...
Click to collapse
Your first sentence caught my eye. Just wanted to say this issue is very rare. Not sure if you realize this, but you responded to a 5 month old thread, where only 2 people had this problem. Haven't seen anyone mention this issue happening since then. Back in March, the Inspire was brand spanking new, so that might explain why a couple of people had the problem back then, maybe due to a few manufacturing process glitches that happens with some brand new products.
Now on to your problem. I took a look at your screen shots, and I honestly don't see any issues with your resolution. The 1st screen shot looks like you were in mid-swipe when you took it - the icon tilting effect is a normal thing when swiping between screens on a Sense 3.0 ROM using the 3D effect. The other 3 screenshots look fine. I do see a little jagginess in the scroll page indicator in your Sense dock, but I'm viewing your images on a 24" monitor and I'm willing to bet that jagginess isn't noticeable on a 4.3" screen.
One thing to keep in mind about Sense 3.0 ROMs is that a lot of stuff has been manually resized and doesn't always look its clearest. For example, I've noticed that on a lot of Sense 3.0 lockscreens the icon font looks a tad blurry. But I did notice that you said the problem happens on the stock RUU, which might indicate you've got a hardware problem that cropped up coincidentally while you were flashing ROMs.
Do your screen shots represent what you're actually seeing? Be sure to look at them on a computer monitor before answering. Regarding the issue you mentioned where your image doesn't go all the way to the edge of the screen, can you post of a picture of your phone taken with a camera? I can compare your phone's screen to mine.
So long story short I need to figure out how to pull a copy of the tmo bootloader off a S-off device if this is possible. I have one and i used the euro version to root but now that i have root and tried to load the stock euro back i dont have wi fi. the rest of the phone is great its just an annoying side effect that im looking to fix. I already went through the sensation fourm and tried most of the bootloaders that people pulled off and none have worked. So i want to try to pull a copy off of my GFs S-off sensation. If someone could tell me how to do it that would be great. If your a dev in the greater sacramento area and want to mess around with an S-off and can fix it by all means you can take the phone for a min
I just want to fix it lol.
nick
I didnt buy these devices i got them from HTC. just causse ppl keep asking that
I think I bricked my phone, but wanted to check here first. Needed to send device back for warranty service, but may have just hosed myself. Was running new ICS FW 3.24 and testing ARHD & IC ROMS without issue.
I set my CID back to T-MOB010 as device was originally with ADB. Rebooted into bootloader and verified the updated CID was shown and it was.
Now this is where I think I choked....
I meant to flash RUU to take back to stock, but got my steps mixed up and did the fastboot command to put S-On back onto the device. Now the damn thing won't even boot up....black and no signs of life. My PC can no longer see it either.
Any suggestions or should I give up hope because of hat one mis-step?!?
I know you have probably done all this but heres what I would do. I would take the battery out then put it back in then hold volume down and power on and see if hboot will turn on. If hboot won't turn on your bricked. sorry dude. Also if you would have ran a stock RUU it would have s-on your phone as it would have flashed stock hboot I believe.
Any suggestions or should I give up hope because of hat one mis-step?!?
Click to expand...
Click to collapse
Sorry i think your only chance is Warranty !!
If your provider is tmobile I have a fun fact for ya. There going to ask you 3 questions after they waste an 30 minutes of your time trying to trouble shoot "it just won't turn on". They ask you, is it in one piece(yes)? Is there any physical damage(no)? Are the water indicators white(yes)? Is the battery damaged(no)? If you answer correctly they'll send you out a new phone right then and there. If you lie and send your old one back and lets say it's been ran over, they'll charge your account full price for the phone. When the new one arrives you send the old one back. They never ask about rooting or anything of that nature, so your not telling them any lies. NICE. Also they're going to ask a bunch about the battery on the phone. They're hoping just your battery is ****ed up. To speed past this step tell them you have a second HTC battery made for the Sensation that doesn't work either.
Yes, it won't even go to HBOOT now, so I'm pretty sure I'm toast. Thanks for the replies!