how to De-Bricking Magic 32a! - myTouch 3G, Magic Android Development

please I've been searching for this
i have only access to the blue led mode (trackball+power) how to use it and with which cable
mine is from Israeli mobile operator: Pelephone

pretty sure it's bricked.
Theres a thread about the cable or whatever, look it up. I have no idea how it works though and I don't even know if the method is succesful.
I'm just sure your phone is dead

that Phone is Dead. Abandon all hope. eBay for parts is all you have left to look forward too.

I just did the same thing. The blue light also gave me some hope. Think positively, now you have an excuse to buy a Nexus One.

don't give up... i had only the blue led function a week ago, my phone is alive and kicking now... not my first one tho.... here is what i did:
I performed a SPL flash, the phone rebooted ,it took long time rebooting so i got panicked i pulled out the battery ( wasn't a smart move ).
tried to start the phone.. now i was stuck at the first splash screen.
-pulled out the battery and back again start the phone... stuck at the first splash screen or boot looping endlessly,
-did all possible key combinations to get in fastboot, recovery mode... nothing.
-cried for help, got directed to a post similar to mo my case... worked for me hope it dose for everyone else.
here is what i did (followed):
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-went to sleep
-woke up in the morning, went back to my old duct taped SE phone
-came home in the evening
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image!
flashed again but this time checked all steps twice before i check them a third time, and flashed the SPL and radio and the rom.

hotweiss said:
i just did the same thing. The blue light also gave me some hope. Think positively, now you have an excuse to buy a nexus one.
Click to expand...
Click to collapse

Related

Phone is borked?

Hi guys,
My girlfriend somehow has borked her phone.
From what she's explained, she used Task 29 to wipe her phone, or something to that degree, and then tried to flash a GSM ROM to it. However she in on Sprint, so I assume it's a CDMA phone.
As of right now, the phone appears off. If you hold the power down, nothing. If you take the battery out, put it back in, and hold Vol Down it'll boot into the bootloader (I believe that's what it is, the colorful background thing) however the bootloader soon goes away and back to the black screen.
Sometimes the phone will randomly boot up to the HTC logo, and then back to blackness.
Does anyone have any idea what she's supposed to do at this point? Or what I should do to get a ROM on there? I have 0 experience with Windows Mobile roms, so I don't know what happened or what to do next. Guidance of what happened and what to do next would be appreciated so I can solve this issue and understand the situation past 'is it borked'
Thanks everyone
EDIT UPDATE: I figured it out. Her battery was dead lol however USB charging wouldn't work. I happen to have an external charger hah so I saved the day. I was now able to boot into the bootloader, have it stay there, and put a ROM on there. Easy Peasy.

Bricked?

Need a little help here. The other day I turned on our old D2 BC I need aa replacement phone and its given me hell. First boot it went into the Liberty boot animation and wouldn't stop looping. My girl rebooted into recovery and flashed Liberty again and apparently it was working fine which I did not know. When she did this she didn't tell me so I was under the impression I needed to do what she did. I went to recovery, wiped and flashed Liberty, I believe its 2.0. Now I can't get it to even go into recovery. The only thing that happens is sometimes when I plug it in to a power source it will go straight to a liberty screen and just sit there. Not even an animation. Any ideas? I'm fixing my Ubuntu right now so maybe I can access ADB commands from there. It won't detect on Windows.
Sent from my Nexus S 4G using xda premium
update: I finally got this phone to do something and idk how? I have tried to let it charge for a few days now and I'm thinking that 'somehow'(???) the battery got f'd up because just now when I plugged it in to finally try to connect through ADB, a black screen popped up. at top it Read: Bootloader > next line > D2.37 then at the bottom two lines that read Battery Low, Unable to Program. ....any thoughts? other than a new battery?
you need to get the battery charged with another phone or an external charger (stay away from homemade chargers as they can mess up stuff). What happened is the battery got too low to either start or finish sbf'ing so it went to bootloader and the phone won't charge without software so until you charge or buy a charged battery you are stuck. It's very fixable but you are stuck.

[Q] Nexus S Stock ICS stuck on Google

Hi,
I have a stock Nexus S with ICS (4.0.3) manually installed over 2.3.6 (Vodafone UK). My phone has started acting strangly over the last couple of weeks where it would get stuck at the Google logo. I have taken out the battery and then inserted it back again and then it always used to work.
Today, the kids made a snowman and I took it out to take a picture. Turned on the camera but could not press the button for taking the pic. Turned off the phone but when turned back on, it was stuck at Google. I have taken out the battery several times but it is still stuck at the google logo.
It is highly unlikely that water got into it as I have a protective cover and it was not dropped.
I have tried to get it into recovery but I cannot go beyond the initial screen. When I click on recovery, it gets stuck at the Google logo again.
Many thanks in advance.
..
Hi,
Thanks so much. Unfortunately, I have a weird problem as I am unable to unlock the bootloader. I typed "fastboot oem unlock" and then, it give me a prompt so ask whether I was sure etc. etc. I click on the volume up, selected yes and then clicked the power button.
The bootloader screen still says "LOCKED STATE - LOCKED".
Please help....
..
Hi, the download link is not working.
Thanks.
..
Hi,
Managed to download the file the second time, thanks. The following error message appeared when I executed the command:
sending 'bootloader' (1536 KB)... OKAY
writing 'bootloader'... FAILED (remote: Bootloader Locked - Use "fastboot oem un
lock" to Unlock)
Off course, fastboot oem unlock does not work....
What to do now?
..
Thank you very much. U are a star. I will now try Vodafone warranty/support and just take it from there.
Having just suffered the same problem (unrooted not unlocked) with my Nexus S (stuck on Google screen at boot up and recovery doing nowt - clearing cache not working) I did the crazy thing of removing the battery and warming the phone with a hair-dryer then when it was warm stuck battery back in and suddenly it boots OK! Phone works ok but I think I still have the problem although at the moment I'm not prepared to turn it off to check.
I'm not sure why this worked, and I still think something is either wrong with the phone or ICS 4.0.3 - anyone?
..
I'm seeing a bunch of people having the issue after the ICS OTA including myself. It has to be something with the update.
Right my phone is bootlooping and cannot unlock the bootloader in fastboot. I am hoping to be in touch with Adam about the resurrector, since it seems to not be working with the t-mobile version.
It may be sensible to downgrade back to 2.3.6 while this problem is sorted. Our smartphones are a very important part of lives and up-time is more important than extra functionality.
How would that work considering that the bootloader cannot be unlocked and we cannot boot into recovery? The resurrector???
..
The problem a few of you here are describing are a classical Nexus S problem, it burns out the mainboard , the so called PBA ( phone board assembly )
turn it in at your nearest service center, say that you get stuck at the google logo with the 4 buttons lit up, which i take is your case even though you pull out your battery and stick it back in, i had the same problem, in the start it worked just fine with taking out battery and putting it back in, but it got worse over time and suddenly when i ran out of power one day, i couldn't for the life of me boot my phone back up again, must have taken out the battery 25-50 times and try to boot it.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=6bd0b738bd5ab761&hl=en
big thread about it here.
So, what you are saying is that because the mainboard has burned out, it is stuck at the Google logo?
kashifmeh said:
So, what you are saying is that because the mainboard has burned out, it is stuck at the Google logo?
Click to expand...
Click to collapse
Basicly yes, because it cannot boot from the internal sd card when it's burned out, if you read that thread in the link i posted, you will see that your far from the only one with that problem, i had it and turned it in at my nearest service center, took them 6 days, i delivered it the 2nd feb and got mine back the 8th, a weekend was included in those days, so if you deliver yours on monday, you should have it back by friday latest , its covered by the basic 2 year warranty from samsung, its a known problem they have.
Hi,
Just got my phone back from Vodafone. The covering letter confirmed that the main board has been replaced and it is now working fine.
However, it is now at 2.3.4, which is a shame. Strangely, the baseband version is still I9023XXKD1. build number is GRJ22. Wonder whether I will ever get an OTA update to ICS with this configuration??
Many thanks to everyone for their help.
..

Xoom won't boot up...

So, I was using fastboot to flash some recoveries for testing (EOS, rogue, cwm) and suddenly my xoom doesn't want to turn on (last command I issued was fastboot reboot and it never turned back on).
I have it plugged in and the charging light shows its charging. It was at around 80% battery so I don't think that's the issue.
Any help please? Any way to force a power on?
Try power button and volume up together...
Sent from my MZ601 using Tapatalk 2
Yeah, I've tried.
Tried just about everything at this point. Probably going to send it in for repair today.
Just keep trying hopefully u get it working again....i had same problem, i mean i couldnt powered it up and thought it was bricked, but after a 30mins and couple of tries more got it up again. Did full wipe of all data and since than enjoy fresh and clean JB xoom
Same problem!!!
I had the same problem testerday and till can't fix it. Please help. I was doing the reffered here http://forum.xda-developers.com/archive/index.php/t-995108.html and the problem appeared after step10 (Type "./fastboot reboot" (wait for reboot)), but it not reboot!!!! I just can see the motorola image from the beginning and that's it.
Please, HELP US!!!!
Nah, my xoom is a bit over a year old and its been heavily used. Not saying I throw it around or anything but I imagined it would have some sort of hardware malfunction eventually.
Just to be clear, I'm not even getting a splash screen or anything. No display at all and from what I can tell, no response from pushing buttons.

Dead Phone

Well the thing is..i've been using my HTC ONE S for a while now...
Then after a while i tried to root my phone via recovery.
I unlocked the bootloader successfully since when i boot on bootloader my phone said on the top of the screen "UNLOCKED".
Then when i tried to get to recovery...it was stuck on entering recovery..nothing happened.
Installed CWM v6 touch and non-touch same results.
I was going to try TWRP but i went to bed.
Next morning during the day my phone ran out of battery. i mean 0%
i tried to turn it on when i leave it on the charger like an hour.
after an hour the pone didnt boot up..it just dead.
the pc doesnt recognize it at all...the charger makes a "bip" everytime i plug in the phone the led blinks a couple of times before fade again
tried hard/soft reset, tried to put it on bootloader, pressed Vol - and Power button, i keep em pressed for like a minute and nothing happened.
It doesnt show up a Qualcomm dispositive. i mean is not bricked, i never installed a custom ROM/RUU/
he worked like a charm the entired day before ran out of battery.
Tried to replug the battery nothing happened same results.
Sometimes when i tryed to only press the power button the screen flash a bit and then dies.
At the end i let the phone the entire night charging(more than 12hours)
Same results......
my phone doesnt have warranty....
I NEED HELP!
cold tdythis
mike_san said:
Well the thing is..i've been using my HTC ONE S for a while now...
Then after a while i tried to root my phone via recovery.
I unlocked the bootloader successfully since when i boot on bootloader my phone said on the top of the screen "UNLOCKED".
Then when i tried to get to recovery...it was stuck on entering recovery..nothing happened.
Installed CWM v6 touch and non-touch same results.
I was going to try TWRP but i went to bed.
Next morning during the day my phone ran out of battery. i mean 0%
i tried to turn it on when i leave it on the charger like an hour.
after an hour the pone didnt boot up..it just dead.
the pc doesnt recognize it at all...the charger makes a "bip" everytime i plug in the phone the led blinks a couple of times before fade again
tried hard/soft reset, tried to put it on bootloader, pressed Vol - and Power button, i keep em pressed for like a minute and nothing happened.
It doesnt show up a Qualcomm dispositive. i mean is not bricked, i never installed a custom ROM/RUU/
he worked like a charm the entired day before ran out of battery.
Tried to replug the battery nothing happened same results.
Sometimes when i tryed to only press the power button the screen flash a bit and then dies.
At the end i let the phone the entire night charging(more than 12hours)
Same results......
my phone doesnt have warranty....
I NEED HELP!
Click to expand...
Click to collapse
Run the OEM RUU first ( you need to know what network the phone is locked too and choose the matching RUU, should you have a few options to choose from then choose the highest number or latest version, if it's unlocked choose the HTC RUU again the latest or highest definition).
http://forum.xda-developers.com/showthread.php?t=2094414
If all else fails ...
Send it back to HTC service centre. Best outcome they'll repair it for free, worst outcome they will tell you how much it'll cost to be repaired and if you choose not to repair then you have to pay P&P for device to be returned. The choice is yours!
Hope that helps.
Optimus.prime.htc said:
Run the OEM RUU first ( you need to know what network the phone is locked too and choose the matching RUU, should you have a few options to choose from then choose the highest number or latest version, if it's unlocked choose the HTC RUU again the latest or highest definition).
http://forum.xda-developers.com/showthread.php?t=2094414
If all else fails ...
Send it back to HTC service centre. Best outcome they'll repair it for free, worst outcome they will tell you how much it'll cost to be repaired and if you choose not to repair then you have to pay P&P for device to be returned. The choice is yours!
Hope that helps.
Click to expand...
Click to collapse
The thing is when i connect my phone to the pc it does nothing. to run the RUU i need to be able to at least install the drivers
mike_san said:
Well the thing is..i've been using my HTC ONE S for a while now...
Then after a while i tried to root my phone via recovery.
I unlocked the bootloader successfully since when i boot on bootloader my phone said on the top of the screen "UNLOCKED".
Then when i tried to get to recovery...it was stuck on entering recovery..nothing happened.
Installed CWM v6 touch and non-touch same results.
I was going to try TWRP but i went to bed.
Next morning during the day my phone ran out of battery. i mean 0%
i tried to turn it on when i leave it on the charger like an hour.
after an hour the pone didnt boot up..it just dead.
the pc doesnt recognize it at all...the charger makes a "bip" everytime i plug in the phone the led blinks a couple of times before fade again
tried hard/soft reset, tried to put it on bootloader, pressed Vol - and Power button, i keep em pressed for like a minute and nothing happened.
It doesnt show up a Qualcomm dispositive. i mean is not bricked, i never installed a custom ROM/RUU/
he worked like a charm the entired day before ran out of battery.
Tried to replug the battery nothing happened same results.
Sometimes when i tryed to only press the power button the screen flash a bit and then dies.
At the end i let the phone the entire night charging(more than 12hours)
Same results......
my phone doesnt have warranty....
I NEED HELP!
Click to expand...
Click to collapse
When you mean you tried to replug the battery, does it mean you were able to open the casing of your oneS? It seems your problem is you have a bad battery, or else your battery is dead.
kasuma_asuma said:
When you mean you tried to replug the battery, does it mean you were able to open the casing of your oneS? It seems your problem is you have a bad battery, or else your battery is dead.
Click to expand...
Click to collapse
yeah i was able to open the phone, the battery is connected via pin to the motherboard (i though it was solder to the main base)
I'm going to try to charge the battery with an external charger, then plug in to the phone and see what happens.
Is all because of a bug on CWM....TWRP the best!
Testing
mike_san said:
yeah i was able to open the phone, the battery is connected via pin to the motherboard (i though it was solder to the main base)
I'm going to try to charge the battery with an external charger, then plug in to the phone and see what happens.
Is all because of a bug on CWM....TWRP the best!
Testing
Click to expand...
Click to collapse
yes, as I can recall on the battery pin, you'll just have to connect the red and black pin to an external power supply, good luck mate! you can do it! :highfive:

Categories

Resources