Hi there,
your first thought might be: Ah jeez another one posting the same **** 2000 people posted before ^^. But anyways i think my problem is a special case:
yesterday i wanted to flash another radio to my htc magic via clockwork recovery. However something must have gone wrong. After the recovery rebooted my phone i got stuck at the "htc magic" splash screen. Pressing the home or the back or vol-down button or home and back button at the same time doesnt change the situation. still stuck at splash screen. fastboot and recovery dont seem to work.
After some really bad panicking minutes, i pulled the batery out of the phone and let it rest, while googling and searching the **** out of every forum on the net. Some minutes later i reassembled the battery and started the htc magic without pressing any other buttons, hoping it would juts boot and say "kidding ))" on the display. but yeah ... it didnt ^^.
Now im coming to the odd part, which differs from most other posts i saw on other forums and here on xda: after quite a while my htc magic suddenly made that "bling bling" sound, as it did whenever it started android successfully. i nearly burst into tears when i heard that sound, hoping that i would be able to access the phone via fastboot or adb. but ... i wasnt able to :S. the screen went black after that "bling bling" sound and stayed that way until i pulled the battery again.
i could repeat that procedure and reproduce the sound and behaviour, but i couldnt access the phone via any possible way i could find on the web :S.
hopefully somebody, who knows more can help. my last step would be jtagging the phone. but the tools are kinda pricy for such an "old" phone. and i couldnt find anyone in my area who could borrow me the tools or repair the phone for cheap money.
thanks in advance im counting on your knowledge
Try this low cost JTAG
tested by me with 2 T-Mobile Mytouch 3G
thanks for your fast response. if jtagging really is my last chance:
- what did you pay for all the parts of the schematic ?
- how long did it take you to put everything together?
- do i need a parallel port on my computer, or is it possible to use an usb port ?
- and do you think a newbie to smoldering and stuff could be successfully assembling all those parts?
- can you provide me with links and/or other pictures, which could help me?
thanks again for your effort
kinda exciting this whole thing :>
Related
Hi,
Phone info :
ipl : 3.08
SPL: 3.08
GSM: 01.12.10
OS : 4.0.0.0
Using a rom i upgraded a year ago.
So yesterday i decided to update my music on the phone, so not a big deal, but when i tryed to play 1 my telephone said it was out of memory and just went really slow, so i decided a reset, bad move.
After the reset it goes to the 2nd loading screen and just hangs there, i cant do anything.
When booting i can go into the screen with all the colors. (gotta press the cam button).
I already googled 2 days but cant find anything to fix this.
Any idea's ?? or is my phone dead ?
didnt remember this forum to be this dead.... any word ?
All my snarky comments about your misplaced impatience can be set aside for later abuse.
For now, here's how you fix it:
Charge on a wall charger with phone turned off. Verify green light before going any further (flashes don't work on less than 50% charge, and a full charge is the only way to be sure when you can't boot the OS).
Let it boot until it's stuck in bootloader mode (the three-color screen).
Hook it to a computer that you have previously synced to the phone with. Verify that "USB" appears in the bottom of the screen. If not, you're probably hosed.
Flash the ROM you loaded again (or get another ROM, doesn't matter...the one in my Sig is pretty nice, if you re-skin Manila after loading it). If you unlocked this phone before adding the ROM you last had, do NOT flash back to OEM ROM unless you can flash a ROM that removes the unlock (for G4, it's the Remove HardSPL procedure).
After that, you can stave off a lot of these kind of memory problems in the future by loading some kind of RAM indicator (QuickMenu has a built-in one, can manage running programs, and gives you a Windows desktop-style start menu for programs instead of the dumb endless folder parade) to let you know you have too many programs running, and you need to do a soft reset every once in a while, just to jog it clean. It also would be wise for you to load a cleaner to clear out your temp files...you'd be shocked how much crap piles up under the OS when you're not looking.
One last thing, do us a favor and put all your phone's info in your Sig...it helps others have a strong footing for making suggestions...not everyone would know off-hand that you have a G3 or a G4 without that info, and your problems can be made a LOT worse by someone offering the wrong answer based on not clearly identifying your hardware.
Hi,
First, Sorry for my impatient, it kinda sucked to have to go back to my old phone and recharge every 30 mins
In this impatiency (dont know if its a word but it sounds cool ) i found out my t-mobile contract was up for renewal, so i did that and ordered a new HTC Touch HD (will update my sig assoon as it ships )
So i guess ill fix this phone, and find a dutch ROM and give it to my dad, he's always working with excel etc and i think this is perfect
Thanks for your response and fix, sorry again for my impatience.
Sorry, double post, pretty slow forum lately
(first of all, I didn't knew where else to post this topic to ask this, excuse me if it's posted somewhere wrong)
So I kinda gave up on my magic, R.i.P.
now i was wondering...
that if I take my phone back to the store... and that i shouldn't get a new one immediatly, bcuz they have to send it to htc facotry... how big is the chance they will know I rooted it and it didn't just mallfunction from its own?
or isn't it possible that they just throw in some new rom? They made it so it shouldn't be to hard to get that fixed...
anyone perhaps has experience with sending back his phone or going back to the store?
tell me what happened... did you get a new one, did you had to pay something to get it fixed or just bought a new phone...
all information is welcome either here on the board or by email first_dimension at hotmail dot com <-
thanks ahead guys...
greetings
a desperate dumazz belgian guy who ****ed up his phone badly
What has actually happened to your phone, can you describe the problem please, it may not have to go back to the repair center. Thanks
uhm, while flashing it, it fell down of my desk, battery got disconnected, ...
now i get my "proximus" (wich is my mobile provider) startup screen, wich doesn't go away
cant enter boot menu (by pressing menu + power on)
nor safe mode (home + power on)
cant even connect to my computer to flash a new rom or anything...
so it's completely bricked i been looking on the internet for days now tried every solution...
nada man...
nothing more than my startup screen...
(edit)
the only thing i can still do is like, when i hit the trackball and power on button it lights up a blue led...
but i read every magic does that even if not bricked...
I heard that someone thought they bricked their phone because they couldn't do anything with all the button combinations but when they tried fastboot it worked and unbricked their phone. I mean he didn't go into fastboot, he just plugged his phone in via usb and just tried fastboot.
I'm saying try fastboot. If that doesn't work then I'm sorry but you have to return it to get it fixed but since they can't get into anything I'm sure they won't know that it is bricked.
thanks for the reply m8, but i tried this already...
just sais waiting for device or sumthing...
i think i read that answer on some other board aswell that someone was lucky enuf to have that but not here, not in my case
bummer i guess...
My carrier offers insurance to replace a phone even if it was lost or stolen. If this was an option for you, I guess you would have already thought about reporting it "stolen," but I figured I'd mention it anyway.
Sorry to hear about your phone.
I bricked my mytouch and I just called T-mo customer service and they're sending me a replacement for free since it's still under warranty.
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
Hi to all peeps in the forum, definetly the state of the art forums in terms of Android. I have a simple question thought. Last week i was trying to change my custom firmware to a different one on a mytouch 3g 1.6. I think i ended up soft bricking my phone. The firmware i was trying to add to the phone was a Modacos because ive read someone saying he was using it in his mytouch 3g and it was running pretty ok. Ok my fault, later someone told me that He would never use a modacos in his cel phones. Anyways, my question is, do i need jtag to unbrick that phone, or is there any walkaround to save the phone? I can do whatever i want with it since its not my regular day phone. Here are some specifics on what is it with the phone.
1. Does it charges when plugged in? Yes it does
2. It shows a blue light if i hit the power+back button at the same time with black screen.
3. If not, the only thing that immediately shows is the android unfolding files image no matter if its connected to the usb or anything like that.
4. I will attach an image so you guys can see the only thing that shows up
answer
Hi there,
for what you have described in your post, the only way you have to re-gain access to your phone is ossing the JTAG method since you can't access directly fastboot on that phone (back + power).
if you plug the phone it's correct for the battery to charge, since this is just an electrical process and doesn't involve processor or system.
google for "htc magic JTAG unlock" you will find all informations you need to bring your phone back to life.
good luck!
Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve
To get into the bootloader , keep the volume up button pressed and then press the power button. Is this what you tried to do?
And I didn't get the part where you wiped through the bootloader. As far as I know there is no option there. Do you mean the stock recovery?( The yellow dots are there in the stock recovery)
Sent from my MB526 using xda app-developers app
wahat3 said:
Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve
Click to expand...
Click to collapse
Check out this link all the best :good: