Disconnecting phone calls - G1 General

Hi Guys,
I'm having a little problem that appears to be getting worse and worse.... I've tried quite a couple of different builds for my G1 (Dev phone with Vodafone sim) and ever since i started changing builds i started to get regular hangups during phone-calls. In the beginning this would happen once every couple of days but by now its become so frequent that the phone is basically useless as a phone; i cant get any call to last longer than 30 to 40 seconds (sometimes even as short as 10 secs). Note: When i install the SIM in an old Nokia i can make calls for ages without any issue...
What happens is basically the same as what would happen if you would press the disconnect button yourself; The screen just tells me the call has ended and there's no strange errors of hangups or whatever.
Does anybody have any idea on how to locate where this problem is coming from, or even better, how to fix this so i can call people with my phone like its supposed to?
Im currently running the following:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.29.26I
with the SuperHero V2 'Official' Release hero build and recovery Util: JFv1.42.

Do you wipe before going to any build?

supremeteam256 said:
Do you wipe before going to any build?
Click to expand...
Click to collapse
Full SD-format and wipe at every single build!

What builds does it do it on? Have there been any builds your phone has worked good?

supremeteam256 said:
What builds does it do it on? Have there been any builds your phone has worked good?
Click to expand...
Click to collapse
To tell you the truth, im not certain.... When i got the phone it only ran a couple of days on the standard 'oem' dev build and that didnt give me any problems i can remember (but than again, i didnt make that many phone-calls those first days still havnig my old phone and all). After a day or 2 i received some ota update on my phone and when googling what that was all about i found the 'world of custom builds', swapped to JF's and every custom build since has been problematic, one worse than the other!
Im trying right now to replace the JF recovery console to something else, see if that changes anything but i dont think could have anything to do with the issue.....

There is the cyanogon 1.2 recovery you can try. For troubleshooting purposes which you may not want to do is reload the original rc29 image. Basically put it back to stock and see if it still has the same problem. If you have the special H SPL then make sure to downgrade the spl before you attempt to do that. If the problem still exsist i would assume something would be wrong with the phone and if you have any kind of warranty or insurrance take advantage of that. You can also try different radio's and see if that helps at all. Again if you have the special SPL to downgrade it so you don't brick your phone.

supremeteam256 said:
There is the cyanogon 1.2 recovery you can try. For troubleshooting purposes which you may not want to do is reload the original rc29 image. Basically put it back to stock and see if it still has the same problem. If you have the special H SPL then make sure to downgrade the spl before you attempt to do that. If the problem still exsist i would assume something would be wrong with the phone and if you have any kind of warranty or insurrance take advantage of that. You can also try different radio's and see if that helps at all. Again if you have the special SPL to downgrade it so you don't brick your phone.
Click to expand...
Click to collapse
Hrm... yeah... If something is wrong with the phone the only way to find out would be downgrading everything...... That would be something.
But for some reason i still think its a bit of a strange problem to be hardware related.... The phone does dial right, accept calls correctly and hanging up also is flawless and my gut feeling is telling me that if this were hardware related all or any of those would be messed up as well.... And i really dont want to send the phone all the way back to the people at brightstar.....
But im on the cyanogen recover right now and wiping everything to see ho things work out.... ill post back here with results....

When dealing with electronics anything can affect something even if it doesn't make sense. Let me know what happens when you change the recovery. And if the problem still persist then I would just start from scratch and downgrade everything to stock and then try again and see if that makes any difference.

Related

Video of me bricking my Magic, what went wrong?

Hey guys,
Few of you in the cyanogenmod irc room the other night might have recalled me totally bricking my t-mobile mytouch by pulling the battery after a reboot... dumbest thing I have ever done. I consider myself a fairly knowledgeable linux geek, but unfortunately I panicked and did the worst possible thing, pulling my batt and completely bricking my phone.
I was installing the 4.1.999 cyanogen mod. Phone was so toast it wouldn't charge. Status led's wouldn't work, it was 100% toast. Fortunately I was able to have it replaced and would like to try again in a day or so.
Here is a video showing exactly what I did, please excuse the length of the video it goes from start to finish, backing up and flashing everything, up until the point where I pulled the battery. I'd love to know what I did wrong, so I can try again!
View the video here on vimeo -> http://vimeo.com/7022688
Ok, here's what you did wrong:
The first steps are good... You've installed the 1.6 update, then applyed the cyanogen rom... After that I've seen that it was installed a new radio... That might have killed your phone...
At least that appears to be the problem... But why a new radio was installed, no idea... (I don't think you did it on purpose)...
the phone you have there is a magic not a dream.For a start that dosnt help!! Other than that i think yiou have put Dream radio on the device, It not being a dream is the problem as when it detects its the wrong radio the phone goes into a safe mode where it wont turn on to save breaking it.
HTC might fix it under warranty as they did me but it WILL come back with perfect spl on.I have flashed the wrong radio on 2 phones yes 2! now i learn from my mistakes Oh and when/if it gets fixed and you bypass perfect spl, You cant put any ROM Other than donut based ones so no hero takes the fun out of flashing
All bricks I've seen are because you guys install new( in most cases wrong radio- from different phone or MotherBoard version) or changing SPL (exception: people with perfect SPL). I'm asking WHY you do this , WHAT FOR ? Putting different rom /rooting etc does NOT require changing anything and is simple as bread and butter, and you CAN'T damage the phone !! Sorry to see this I'm not 100% sure but it looks like you have flashed with wrong radio. As my predecessor said I think only HTC can fix it... To all people DO NOT TOUCH SPL AND RADIO IF YOU JUST WANT TO PUT HERO ROM OR ROOT THE PHONE (exception ppl with perfect SPL)
i accidently flashed the radio for ION on my 32A last week. got my phone fixed under warranty thank god. but i got the perfected SPL.
if you do get the perfected SPL, you dont really need to change your SPL to flash stuff on your phone.
just replace your recovery using the recovery flasher apk a.k.a the one click root.
reboot to recovery, flash a new ROM that is rooted.
then using the adb shell method, flash a new recovery permanently to your phone.
i have had no issues using that method since i got my perfected SPL.
whalesalad said:
Hey guys,
Few of you in the cyanogenmod irc room the other night might have recalled me totally bricking my t-mobile mytouch by pulling the battery after a reboot... dumbest thing I have ever done. I consider myself a fairly knowledgeable linux geek, but unfortunately I panicked and did the worst possible thing, pulling my batt and completely bricking my phone.
I was installing the 4.1.999 cyanogen mod. Phone was so toast it wouldn't charge. Status led's wouldn't work, it was 100% toast. Fortunately I was able to have it replaced and would like to try again in a day or so.
Here is a video showing exactly what I did, please excuse the length of the video it goes from start to finish, backing up and flashing everything, up until the point where I pulled the battery. I'd love to know what I did wrong, so I can try again!
View the video here on vimeo -> http://vimeo.com/7022688
Click to expand...
Click to collapse
after applying the 4.1.999 update you pressed the trackball to reboot your suppose to hold the home key while its rebooting on that step till the mytouch screen shows up also you need to wipe the ext. redo the last step then the my3g should be fine in other words reflash the cyanogen
u install wrong recovery
Install instructions for an HTC Magic (32B ONLY!!!)/ION/MyTouch3G
Same as above if you are using CM-Recovery 1.4.
OR
Same as above EXCEPT step 2
Download HTC ADP 1.6 DRC83 http://www.androidspin.com/downloads...ooted_base.zip
*You have to manually reboot MT3G and hold home.
he can use the ra recovery image it works because i used it on mine
Turns out I used the wrong recovery image before doing the cyanogen flash.
I followed this guide on my second phone (swapped out my old white one for a black mytouch) and am running 4.1.999 right now - http://forum.xda-developers.com/showpost.php?p=4666075&postcount=282

Does anyone know how to unbrick the CDMA Hero?

My phone shut off and has not been able to turn since. I tried flashing a ROM and didnt relive after that. Please help.
What do you mean it doesn't turn on? What happens when you hold the power button?
it doesn't boot ...it is as if it were dead
Check to make sure it is charged and the battery is installed properly. I have had the battery so dead that it didnt even vibrate to indicate booting.
Yeah. Let it sit on the charger for a few minutes, make sure battery is in right and everything is plugged.
Check for amber LED, let it charge a few minutes, then try again and do it like that every couple minutes. If nothing still, buy a new battery or exchange it.
nothing so far ...ive scheduled an appointment to repair ...i know they wont be able to do anything for this phone. I wanted to see if I can avoid not having to give up my HTC hero and deal with a replacement phone for a while.
ummmm, how did this happen?
you may not want to say for fear of bashing but I promise I won't, as far as I've seen it takes a very unique set of circumstances to actually brick these things
EDIT: my prediction: you tried to flash a GSM rom onto it
so when attempting to get the download file for the Eclair 2.1v1.5 rom it stated that the radio posted is recommended. Prior to flashing the radio i did a nandroid backup and then I flashed the radio. During the flash screen (open box to phone image) it blacked out after about 20 seconds.
kel_o91 said:
so when attempting to get the download file for the Eclair 2.1v1.5 rom it stated that the radio posted is recommended. Prior to flashing the radio i did a nandroid backup and then I flashed the radio. During the flash screen (open box to phone image) it blacked out after about 20 seconds.
Click to expand...
Click to collapse
sorry bout what happened. I know jack-diddley-squat about radios...so I might have been in your place if I tried it.
kel_o91 said:
so when attempting to get the download file for the Eclair 2.1v1.5 rom it stated that the radio posted is recommended. Prior to flashing the radio i did a nandroid backup and then I flashed the radio. During the flash screen (open box to phone image) it blacked out after about 20 seconds.
Click to expand...
Click to collapse
So my theory is that this nOOb flashed the GSM radio. Here is what he did.
He seen the post on the Eclair 2.1v1.5 rom on our forums and got click happy. Clicking on the link under that thread for the GSM ROM.
The current build is based on Lox and Behnaam's GSM 2.1 v1.5.
Click to expand...
Click to collapse
Which took him here:
http://htcpedia.com/forum/showthread.php?t=1448
Then he flashed the radio in this post.
(Suggested radio 63.18.55.06JU_6.35.09.26)
Click to expand...
Click to collapse
So yea he didn't read, just clicked, have fun with that.
And i suppose you didn't flash a recovery img after rooting? Well next time you will learn to read.
Have you tried booting into recovery and doing a nandroid restore?
i've never heard of a bricked CDMA hero... but i guess flashing a GSM radio would do the trick
ok i searched and this may be the FIRST EVER bricked CDMA htc hero!
correct me if i'm wrong but i couldn't find anything on google about this.
maybe we should sticky this, or delete that link to the gsm rom so this doesn't happen again?
yeah i guess i did flash a gsm rom which definitely pwnd my phone ...i did everything possible. hard reset buttons. basically couldnt do anything with adb as the phone was completely shut off so no way to connect. Well all in all i learned my lesson. The techs at the sprint store couldnt do anything to fix the original phone so they said what the heck and provided me with a brand new google branded hero.
We all have done it!
kel_o91 said:
yeah i guess i did flash a gsm rom which definitely pwnd my phone ...i did everything possible. hard reset buttons. basically couldnt do anything with adb as the phone was completely shut off so no way to connect. Well all in all i learned my lesson. The techs at the sprint store couldnt do anything to fix the original phone so they said what the heck and provided me with a brand new google branded hero.
Click to expand...
Click to collapse
Flash lesson 101, read-read-read!!!
Don't worry we 'ALL' have done it. And LEARNED from it.
Keep on going!!!
I'm glad to hear you got your phone replaced. I don't understand how you couldn't boot into any mode that would allow you to fix this. But I don't mess with radios whatsoever.
thedudejdog said:
maybe we should sticky this, or delete that link to the gsm rom so this doesn't happen again?
Click to expand...
Click to collapse
+1 Please sticky and/or remove link. We don't need people jumping the gun and flashing ROMs that will brick their phones.
Cheers.
WhiteWidows said:
So my theory is that this nOOb flashed the GSM radio. Here is what he did.
He seen the post on the Eclair 2.1v1.5 rom on our forums and got click happy. Clicking on the link under that thread for the GSM ROM.
Which took him here:
http://htcpedia.com/forum/showthread.php?t=1448
Then he flashed the radio in this post.
So yea he didn't read, just clicked, have fun with that.
And i suppose you didn't flash a recovery img after rooting? Well next time you will learn to read.
Click to expand...
Click to collapse
Wow, way to show class. Nothing like a little compassion around the holiday season, I see. You are a true class act, and I bet your friends and family are very proud of the way carry yourself. Unfortunately, not everyone can be as perfect as you are, so try to take it easy on the rest of us.
Let it go guys... on all sides of the argument.
he made a simple enough mistake. It's been remedied. Lets all move on.
obelisk79 said:
Let it go guys... on all sides of the argument.
he made a simple enough mistake. It's been remedied. Lets all move on.
Click to expand...
Click to collapse
+1 for this
How does a radio flash stop a phone from turning on?
Isn't the whole point of a recovery mode, to be able to "recover" if something goes wrong.
Shame on you whitewidows, for bashing him... The whole reason people get things working is because of trail and error.
If anything he helped us all by confirming that a wrong radio flash will completely ruin your recovery console, possibly bootloader, and (maybe even some actual hardware).
Hopefully this doesn't discourage users from trying to hack our radio.

Stuck on "stick together" screen... Please Help....

Hello,
I'm a noob, through and through. I think that I did everything correctly. I flashed Artemis v8.0 and followed the instructions, then it said that it was completed successfully. When it boots, however, it gets stuck on the "stick together" screen and displays the R G and D information in the bottom-left as it should. Also, when I access the bootloader and re-run the flash, I see no image version information listed. I should mention that the flashing process only took about two minutes. I already did a hard reset.
Did I do something wrong? What do I do?
Update: I tried flashing KUMAR and have the same results; the only dirrerence is that the information listed for D has changed to 1.66.KUMAR... oh my...
...Wow.... I can't believe it. It won't turn it on at all after flashing the original LEO ROM. Looks like I'm toast now...****...
What radio are you running? What model phone is it?
The radio is default. I didn't touch that. I installed HSPL then flashed a couple of ROMs, none of which worked. I think that I may have flashed the wrong version of the official LEO ROM fromthe sticky. So, it looks like I'm screwed. The best way to learn from your mistakes is to lose $500.
you still didnt say what phone, tmous is different from all other hd2's
if its a tmous, then yea, i suspect its gone. (it was possibly recoverable at your first and second posts, cos that was roms that dont support 576meg ram, so flashing a tmous specifric rom would(i think) have fixed it, but what official rom did you flash? anything other than the tmous 2.10 rom will have had a bad radio, and as we all know by now, the wrong radio bricks tmous's
(Edit - sorry, didn't mean to rub it in, just wanted to explain what had happened at each step)
I flashed LEO 1.48 (WWE) from the stickied thread. I can't post the link because I'm new. I don't even know what TMOUS means, so I suspect that's not a good thing. It's the model with 1024 MB ROM is all that I know. If I can find out exactly what, let me know.
shiznit1707 said:
I flashed LEO 1.48 (WWE) from the stickied thread. I can't post the link because I'm new. I don't even know what TMOUS means, so I suspect that's not a good thing. It's the model with 1024 MB ROM is all that I know. If I can find out exactly what, let me know.
Click to expand...
Click to collapse
Yea, tmous is T Mobile US. They will ONLY accept roms of the 2.10 family. Thats why your first 2 rom flashes failed.
However the damage was done by the radio. Stock roms come with a radio as part of the rom, and the official rom you flashed is oooold. Certainly it has a ..51.. radio.
Any radio with ..51.. in the version will not support the 576meg ram that the tmous has, and as it turns out, they stop the phone even powering on. (or powers on but black screen, the PC sees it as a qualcomm usb device, if it sees it at all.)
I've yet to see anyone offer any kind of fix, though i have seen people say they have had it replaced by tmob.
Unlucky.
samsamuel said:
Yea, tmous is T Mobile US. They will ONLY accept roms of the 2.10 family. Thats why your first 2 rom flashes failed.
However the damage was done by the radio. Stock roms come with a radio as part of the rom.
Any radio with ..51.. in the version will not support the 576meg ram that the tmous has, and as it turns out, it stops the phone even powering on. (or powers on but black screen, the PC sees it as a qualcomm usb device, if it sees it at all.)
I've yet to see anyone offer any kind of fix, though i have seen people say they have had it replaced by tmob.
Unlucky.
Click to expand...
Click to collapse
...Thanks for your help...
samsamuel said:
Yea, tmous is T Mobile US. They will ONLY accept roms of the 2.10 family. Thats why your first 2 rom flashes failed.
However the damage was done by the radio. Stock roms come with a radio as part of the rom.
Any radio with ..51.. in the version will not support the 576meg ram that the tmous has, and as it turns out, it stops the phone even powering on. (or powers on but black screen, the PC sees it as a qualcomm usb device, if it sees it at all.)
I've yet to see anyone offer any kind of fix, though i have seen people say they have had it replaced by tmob.
Unlucky.
Click to expand...
Click to collapse
So, I now have a couple of options. I could go back to the store and play dumb, or I could physically damage it and pay the $150 or so to get it replaced. Thoughts?
shiznit1707 said:
So, I now have a couple of options. I could go back to the store and play dumb, or I could physically damage it and pay the $150 or so to get it replaced. Thoughts?
Click to expand...
Click to collapse
I'd take it back. Say it was on charge overnight, you woke up and it's like that. Can;t hurt to try, eh? be all gutted and that, moaning about lost contacts and such.
samsamuel said:
I'd take it back. Say it was on charge overnight, you woke up and it's like that. Can;t hurt to try, eh? be all gutted and that, moaning about lost contacts and such.
Click to expand...
Click to collapse
So if they don't take it back, would they take note of the fact that my warranty is voided so I couldn't go ahead and pay the $150 for a new one? I really appreciate your help.
if they figure out the warranty its void im sure they'll still fix it, they'll just charge for it.
samsamuel said:
if they figure out the warranty its void im sure they'll still fix it, they'll just charge for it.
Click to expand...
Click to collapse
Alright, they took it back no questions asked. I'm going to actually end up saving $200 because of this - my contract is up in a week! Thanks for your help, samsamuel. Great community here. Now I just hope I'm not stupid enough to try it again!
heh so there is a silver lining after all.
you used HSPL?
if you did that and you go back to store make sure you dont have HSPL more on your phone!!!!!!
I have made the same mistake, i flash the rom energy 1apr , the flash was made succesfuly end phone was started normal and functioned , i close the phone and when i opened him , the phone stock on the wake up screen ( htc on white screen ). what kan I do?, please help me
i had some how same problem before like Sticking in boot screen
1. i tried hard reset hold Volume up+down and press end button till it will start and then it will ask you if you wanna do reset and press volume up for accept after that finish it will ask again to press volume up for boot then it would boot. if does then you need to correct the radio and also ROM which is correct for you
2. another is task29 method
let me know if you could make it...
thanx , i am at work , bath will try later
@costinn : try to flash the proper Radio ROM. It happened to a lot of people because they do not learn about the radio compatibility! Try 2.08.50.08 and you will be fine!

Holy hell... a lot of work

Alright, I have an HTC Magic which essentially acts as my backup phone since I have a Desire. I figured I would try my hand out at flashing a rom on the Magic. Am I missing something, because it seems like a LOT of work. For something that people make out to be so simple, it sure is a pain. Every step I take, I run into issues. At this point I need to:
- Make a Goldcard. (Actually done, I think...?)
- "Fix" my SPL as it's "perfected.
- Update the Radio since the "fix" will apparently mess it up.
- Update the recovery using a customer recovery image.
- Then maybe flash a ROM to it and hope it works.
Am I missing something...or is this WAY more work then people make it out to be. Looking through the forums before starting this... people made it seem like all you had to do was make a Goldcare, copy the rom .zip to it, and use the fastboot method to flash it. I have flashed ROMs on WinMo several times, and it's never been nearly this much run around...even when things mess up. I thought doing this on Android was easier then on WinMo...
So... am I missing something? Is there an easier way that doesn't involve all this run around? Even so, hopefully I have almost everything I need at this point. Is there anything else I am going to run into that is going to cause a need for even MORE work? Any tips here? Thanks.
UPDATE: On trying to flash the SPL "fix" it goes through the installation then tells me that the CID is incorrect. I have tried it 4 or 5 times, using two different cards. It shouldn't be wrong. Any help? Don't understand why it keeps telling me the CID is incorrect. I have noticed though, for some reason, every time I restart the Magic, it gives me a different number when trying to get the CID. Is there a way to bypass this? Have been trying for 4 hours and have gotten no where at all...
Whiterin said:
Alright, I have an HTC Magic which essentially acts as my backup phone since I have a Desire. I figured I would try my hand out at flashing a rom on the Magic. Am I missing something, because it seems like a LOT of work. For something that people make out to be so simple, it sure is a pain. Every step I take, I run into issues. At this point I need to:
- Make a Goldcard. (Actually done, I think...?)
- "Fix" my SPL as it's "perfected.
- Update the Radio since the "fix" will apparently mess it up.
- Update the recovery using a customer recovery image.
- Then maybe flash a ROM to it and hope it works.
Am I missing something...or is this WAY more work then people make it out to be. Looking through the forums before starting this... people made it seem like all you had to do was make a Goldcare, copy the rom .zip to it, and use the fastboot method to flash it. I have flashed ROMs on WinMo several times, and it's never been nearly this much run around...even when things mess up. I thought doing this on Android was easier then on WinMo...
So... am I missing something? Is there an easier way that doesn't involve all this run around? Even so, hopefully I have almost everything I need at this point. Is there anything else I am going to run into that is going to cause a need for even MORE work? Any tips here? Thanks.
UPDATE: On trying to flash the SPL "fix" it goes through the installation then tells me that the CID is incorrect. I have tried it 4 or 5 times, using two different cards. It shouldn't be wrong. Any help? Don't understand why it keeps telling me the CID is incorrect. I have noticed though, for some reason, every time I restart the Magic, it gives me a different number when trying to get the CID. Is there a way to bypass this? Have been trying for 4 hours and have gotten no where at all...
Click to expand...
Click to collapse
I guess that I should be moving this to General since this is a Q&A and not a means to simplify what you are trying to accomplish.
Moving to:
Magic General
Discussion about the T-Mobile myTouch 3G, HTC Magic (general Q&A, tips & tricks)
Wow, do I know how you feel.... I recently got a Vibrant (galaxy s). So sine I got a new phone I unrooted my MT3g and sent it in on warranty since it was kinda scratched, so I can give it to my wife. Well with my first phone I was able to do the on click root since it came originally loaded with cupcake.... Well as it turns out if it comes pre loaded with donut you can't downgrade any more...lol So I had to do the gold card method.....it sucked.....
I can't even get stuff to work with the Goldcard. It keeps telling me the CID is incorrect... which it may be, since it gives me a new number every time I restart the damned thing. It can't be this hard to root all Android devices I hope... this is just ridiculous.
Whiterin said:
I can't even get stuff to work with the Goldcard. It keeps telling me the CID is incorrect... which it may be, since it gives me a new number every time I restart the damned thing. It can't be this hard to root all Android devices I hope... this is just ridiculous.
Click to expand...
Click to collapse
No, its not.... A good example is to root the vibrant you just flash a update.zip file...lol. But the sapphire/magic/mytouch is a great phone with allot of development support. But from what I understand one of the hardest roots..
Well that sucks. Kinda wanted to see how Froyo would run on it, and wanted to get a feel of how it was done before attempting it on the Desire. How did you manage to get the thing flashed?
Whiterin said:
Well that sucks. Kinda wanted to see how Froyo would run on it, and wanted to get a feel of how it was done before attempting it on the Desire. How did you manage to get the thing flashed?
Click to expand...
Click to collapse
the CID error tells me your gold card creation failed.
Check the process description at theunlockr.com. that worked for me.
My first mistake was formatting FAT and NOT FAT32. It must be formatted FAT32.
I used a 2GB PNY and it works great.
yes, our phone (the sapphire, magic, MT3G, whatever the carrier calls it) is one of the craziest to root. I have the 1.2 version that came out after the fender, so by default i need to do the goldcard method. I made the goldcard, but then my daughter dropped my phone, and i had to get it replaced, someone is currently borrowing my card reader, so i have to wait to root the new one.
one step from reading the forums that alot of people miss, is replacing the first two digits of the "gold card id" to 00.. you have to do this, or the thing wont work. at least if you're having issues on the gold card step you're not close enough to the steps that can BRICK your phone...
all i can say is make sure you follow the directions STEP BY STEP, i've seen a number of people who flash the wrong image first and it totally bricks the phone. in my case that would suck, as being on the non-contract plan, i get no discount for new phones.
hope that helps a little.
Yes, the zeros are critical but as I recall theunlockr link above (paste and cut) takes care of that for you. The gold card is the hard part to get right.. The rest is very straightforward.
Thanks for the input guys. Going to try a few more things.
Alright. Following the instructions. Step by step, I am still getting "CID Incorrect! Update Fail!"
This is very frustrating as there isn't any reason it shouldn't be working...
Darklordzim said:
yes, our phone (the sapphire, magic, MT3G, whatever the carrier calls it) is one of the craziest to root. I have the 1.2 version that came out after the fender, so by default i need to do the goldcard method. I made the goldcard, but then my daughter dropped my phone, and i had to get it replaced, someone is currently borrowing my card reader, so i have to wait to root the new one.
one step from reading the forums that alot of people miss, is replacing the first two digits of the "gold card id" to 00.. you have to do this, or the thing wont work. at least if you're having issues on the gold card step you're not close enough to the steps that can BRICK your phone...
all i can say is make sure you follow the directions STEP BY STEP, i've seen a number of people who flash the wrong image first and it totally bricks the phone. in my case that would suck, as being on the non-contract plan, i get no discount for new phones.
hope that helps a little.
Click to expand...
Click to collapse
Not to thread jack, you know you can use any GoldCard with any phone, as long as it was made properly.
Any ideas on why this one isn't working then? Saying "Incorrect CID" when I try to flash anything with it.
Not sure. I know it took me 3 tries to get mine working right.
Sent from my HTC Magic using XDA App

[Q] bricked my hd2 but my computer recognizes it...?

so i flashed my phone with the wrong radio i believe but the strange thing is that my computer recognizes it. the doesnt turn on at all but i here the sound of a device being plugged in when i plug it into winodws. is there a chance its not bricked?
the sound doesn't necessarily indicate much.
what did you do? specifics, please?
can you get into bootloader?
i was trying to flash a stock rom and i guess it didnt work?
minnieman said:
i was trying to flash a stock rom and i guess it didnt work?
Click to expand...
Click to collapse
mate. as i said, specifics please. like what rom / type of phone do you have? what rom were you flashing? you said radio, now you say rom.
also, as i asked, can you get into bootloader?
please, if you want help, we need information.
minnieman said:
so i flashed my phone with the wrong radio i believe but the strange thing is that my computer recognizes it. the doesnt turn on at all but i here the sound of a device being plugged in when i plug it into winodws. is there a chance its not bricked?
Click to expand...
Click to collapse
You may try and follow this solution, I suggested earlier. Click here
Let us know if it worked.
sorry i was vague, i was in a rush to get to work this morning and on top of it i was panicking. i flashed the stock image:
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship
i tried that on a hd2 so i could flash hspl3 again and use wp7 on my hd2.
i ended up just sending it in, but if they send it back with no repairs ill try your method... i relly hope they just send me a new one though. i mean... i flashed a stock image to the hd2, so shouldnt they see no hspl and just the stock spl?
again, more details are needed.
like what type of hd2 do you have? if it is a us tmo brand, i believe it is bricked (as you flashed a .51 radio.)
if you flashed your stock rom from your sd card, hspl is removed. if you flashed over usb, and did not uninstall hspl, hspl is still there.
what i don't get is if you can flash a rom, why are you saying it is bricked? no offense, but each post seems to change the story (first it was a rom, the a radio, now you are flashing roms but sending the phone in, still don't know if you can get into booloader, but now you sent the phone in or is it in your possession???) and i am not following what you did, where you started or what is going on. maybe i am totally missing what you are saying (which is possible)...hope someone can help you.
i have the 1024 us tmous hd2. i tried to flash to a stock rom, forget i said radio. i tried to flash the .51 which i did not know would brick my phone, so i played dumb with htc and sent it in to get repaired. if they dont repair it i am kinda SOL because i flashed using usb and they will see it has HSPL. sorry, do i need to include anything else? i am just kinda a noob... sorry.
i swear i posted a response. hmm.
thank you for the details. your assessment of the situation is spot on; unfortunately your phone is indeed bricked. and likely htc will not know about hspl...or so i have heard from others.
curious, why did you send it to htc? did tmobile reject it? if not, and htc doesn't give you a new one, try getting it to tmobile (under warranty)- worked for me when the phone stopped working for unknown reason. good luck.
possible to make it back to work...?
jsmccabe78 said:
i swear i posted a response. hmm.
thank you for the details. your assessment of the situation is spot on; unfortunately your phone is indeed bricked. and likely htc will not know about hspl...or so i have heard from others.
curious, why did you send it to htc? did tmobile reject it? if not, and htc doesn't give you a new one, try getting it to tmobile (under warranty)- worked for me when the phone stopped working for unknown reason. good luck.
Click to expand...
Click to collapse
here i am one of the ppl out there have the HD2 bricked.
I have tmo version, Couple months ago i was trying to flash a office rom, which is i don't remember which one, but i really sure it was a HTC Office Rom., I let the phone do it thing while flashing, but after the flashing the screen go off and didn't back on working anymore, I still have the bricked phone though, and i was wondering if any possible method apply to the above problem?
i will looking forward to hear from u, Thank U,
chhada said:
here i am one of the ppl out there have the HD2 bricked.
I have tmo version, Couple months ago i was trying to flash a office rom, which is i don't remember which one, but i really sure it was a HTC Office Rom., I let the phone do it thing while flashing, but after the flashing the screen go off and didn't back on working anymore, I still have the bricked phone though, and i was wondering if any possible method apply to the above problem?
i will looking forward to hear from u, Thank U,
Click to expand...
Click to collapse
Were you able to get into bootloader Chhada?
nicedude_abad said:
Were you able to get into bootloader Chhada?
Click to expand...
Click to collapse
no dude, nothing respond with the power button, *_* it doesn't do anything,
headache
man this could be very tiring ive tryed everything from hard soft chilled any kind reset.volume down red green white button hold down but one thing is weird is when i connect it to the pc wiht the thing off it makes a sound like it sees it but no luck with tmobile rom update. ill send to tmobile and play the good guy http://media.xda-developers.com/images/smilies/confused.gif

Categories

Resources