Database Users

My tmobile mytouch 3g is bricked how can unbrick it??

Hey people greeting first of all by stupidity i flashed a new radio 32a radio on my 32b mytouch by accident now my phone its bricked it just stay stuck on the first splash scree i cant fastboot or recovery mode my pc dosnt reconize my phone ether what can i do??? Help please
mytouch 3g
32b s on g
slp 1.33.2010

if you cant fastboot/recovery/anything, it's pretty much bricked. If you get some blue LED, there isnt much hope for that either.

i got no blue led it just stay on the first splash screen no recovery mode or fastboot

morepr said:
i got no blue led it just stay on the first splash screen no recovery mode or fastboot
Click to expand...
Click to collapse
Then you're bricked. Means you need a new phone.

no ooo
people there is a solution via the usb when it is stuck at the first splash screen just search
mine is totally bricked and still no solution !!!

call tmobile.
I did the same thing yesterday and I told them that My phone updated itself then wouldnt turn back on.
my new one is in the mail and will be here in 2 days
just act naive and clueless.
as long as your still under warranty, your all good.

thanks ppl i try everything but this its not going no where the pc dosnt want to recognize my phone and i try everything just gonna throug it in the toilet and call the insurence

At least sell it for parts, you can probably squeeze 40 bucks out of it or similar. Check the going rates on eBay for non-functional handsets.

I know its a bit late....but I fixed my 'bricked' MT3G
I was searching around the web for a solution to my problem, and needless to say, there wasn't much out there for me besides the typical... "it's bricked, buy a new phone."
So here's my story:
Earlier today I decided to upgrade my MT3G to Cyanogen's 5.0.7 Android 2.1 rom. I had used the experimental 5.0.6 rom, and found it to be a bit more "glitchy" than I was comfortable with. So, I went online for what I figured to be a very simple upgrade...and downloaded both the rom and a kernel (which was 32A not 32B).
Needless to say, after installing the rom, the kernel, my gapps update, and resetting my phone... it did nothing but hang on the MT3G screen. After about 30-45 min...I knew something was wrong and I freaked. It was unresponsive to multiple attempts to reboot, and was not being seen by my computer.
That's when the online search began... I looked for other individuals who've suffered the same fate and kept coming up with the same "you're screwed" response. Having recovered more "bricked" iPhones in the past than I can count, I knew this could not be the case. For me, as long as the phone turned on and flashed some sort of screen, there's still hope.
So what did I do...
Well, I first attempted to boot the phone into recovery mode...but it would not work. Next, i figured I would try doing a fastboot... and what do ya know... it worked!
From there I used multiple combinations of plugging in the phone via usb and resetting and putting into recovery mode until I found one that worked.
So here's my steps:
(Note: this has only been tested if you accidentally installed the 32A kernel on your 32B device)
1. Power on the phone... If you continuously sit at the green MT3G screen, take off the back and take out the battery.
2. Plug in your USB cable (VERY IMPORTANT, will explain later)
3. Next, replace the battery and hold down both the [home] and [power] buttons, if it merely turns on to the green screen, and you get no response from your computer's usb notification window...take out the battery again
4. Fastboot your phone (hold down [back] and [power] arrows) While your phone in connected to your computer, it should make a notification sound.
5. Restart your phone from Fastboot, AS SOON as it shuts off, hold down the [home] and [power] keys.
6. Continue holding until you hear a notification sound from your computer...at that point it should boot into recovery mode.
7. Wipe your handset (just for good measure) and reinstall your update package...DELETE that wrong kernel from your sd card so you dont make the same mistake again.
Summary:
I have no clue as to why it works, but I've done this 3 times now just to verify, and each time it has worked. For some reason, the USB connection to the handset acts as a precursor to the phone booting. I will stress that without plugging in the USB, my phone did not boot into recovery mode. However, after I did plug it in...Fastbooted....Reset....and Booted into Recovery it worked perfectly.
I am still suffering lags on my device (more so than before) and this could be a product of my stupidity, or this rom being laggy. Either way it works, and I don't have to purchase a new phone!!!

Mod. edit: not dev related, moved to general

I experienced the same problem which can not boot recovery.
I've tried your way above but no luck.
Is there another way?
HTC MAGIC MY TOUCH
SAPPHIRE PVT 32B ENG S-OFF H
radio-2_22_23_02
cm-5.0.7-DS-signed

T-Mobile myTouch 3G - stuck on splash
Today I probably flashed my phone with a wrong (32A) SPL. I can't access fastboot, recovery mode or anything, including access from PC (either Linux or Window$). But it's stuck on splash - if it was totally bricked, would it still load a splash screen? Is there any hope?

Sigh.. I have the same problem.. Blue LED If I hold down the track ball but can't get to fastboot or recovery..
My problem started after I flash the HTC rom from the website.. Sigh.. I think it was the radio that did it..
Anyone found a way to get around this (w/o jtag)?

I am also experiencing the same problems. Blue LED works, cannot get into fastboot, bootloader, or recovery. It just sits on the opening splash screen.
Any other ideas?

Looks like I will just sell mine as a "bricked" device and hope to salvage a few bucks. Sigh

THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU. I would keep going but you get the point. I downloaded ROM Manager, and I flashed a Cyanogen Nightly ROM from 11-5-2010 and I got nothing but a Green spalsh screen and a reboot cycle. You instructions ROCK!!!

I went crazy and prayed a few times to unbrick my phone. I tried different things and then nothing worked. So I had the phone on for a bit and it restarted twice and then ran. Just let in sit for a while. Give it time. Maybe itll work for u too. goodluck

have a mytouch 3g 1.2 with the old radio and SPL, i acidently bricked it trying to flash the new radio and SPL and now i cant get into recovery or fastboot and the flash screen is frozen, pleassssssee help me get this fixed it has been completel useless for the last week or so

Succesfully unbrick with wiggler Mytouch 3G 1.2
as Ezterry instruction i follow his guide, and build my own JTAG.
My God its working 100%..

awebagar said:
as Ezterry instruction i follow his guide, and build my own JTAG.
My God its working 100%..
Click to expand...
Click to collapse
Can I ship you my bricked device so you can practice unbricking? I can pay you in random electronics

PLZZ Help M boot Logo/Fail Flash Cyanogenmod rom

Hello. Well to start off I had recently rooted my Droid2 which was running the OTA GB. So I started looking for roms like I use to with froyo and the leaked GB. Was looking for something to change the battery life frame poor to great. Anyway I came upon Cyanogenmod's Rom for Droid 2 For the ota gb. I made a nandroid back up, downloaded it and was ready to flash. Seconds away in boot recovery and while i was looking for the file before I think I hit "apply update" instead of "search for zip file on scdard(or what ever sentence it says) and i got it but it started loading an update. I was like wtf kinda freaked out and I did a battery pull . Now my phone stays at the M boot logo and i have no way to go back. I heard the SBF for GB ota isnt her yet . if anyone can help I would be grateful. Plz Help
Things I've tried/
1.Battery Pull.
2.Hold power button + hold X(doesnt work like froyo Poo)
3.Tried going back with rsdlite 5.3.1 with moto drivers(it won't show my device ;'( )
4.Left this message on xdadev / please help

SOLVEd
{[SOLVED]}
Used bootloader way in by holding power button and up. rsd that way and got it to work.. Guess this is to who ever made my mistake . heres the solution

T3viin said:
{[SOLVED]}
Used bootloader way in by holding power button and up. rsd that way and got it to work.. Guess this is to who ever made my mistake . heres the solution
Click to expand...
Click to collapse
I just tried this on my friend's D2 (I am very experienced with the inc), and I seem to be having the same problem. I have tried Sbfing, but RSDlite will not recognize the phone. I have booted to recovery, nothing (Stock recovery), and the bootloader (Says too little charge)
What can I do?

Charge your battery in another phone like yours. Borrow someones spare battery. Take battery to verizon store and see if they can charge it somehow. There is a thread on here somewhere on how to do a hack job on your cable and hook the wires directly to your battery and charge it independent of the phone. I can't post a link so I hope you can find it by searching.
Sent from my DROID2 using XDA App

dmeadows013 said:
I just tried this on my friend's D2 (I am very experienced with the inc), and I seem to be having the same problem. I have tried Sbfing, but RSDlite will not recognize the phone. I have booted to recovery, nothing (Stock recovery), and the bootloader (Says too little charge)
What can I do?
Click to expand...
Click to collapse
I've had this problem 4 times in the last week. I used a terminal based OS to SBF using ADB.
And in the same step I re rooted my phone. Whole thing takes about 15-20 minutes.
The steps are on the CMWiki.

[Q] I think my Atrix is hard bricked. Can someone verify this?

Here's the story...
I got this phone refurbished for a penny just over a month ago. It's awesome... sexy exterior, simple form, banging specs, super fast loads and renders. However, I tried to root it so I could use a force-Webtop app (for streaming Netflix to my TV), and apparently the phone was updated before it was resold to me, so when I tried to root it bricked.
To root, I used a YouTube link I found on XDA, but got a Failed To Boot error when restarting my phone. After searching for a while, people called it a "soft brick" and said to use RSD Lite to flash the factory sbf. I followed the instructions word for word and now it won't do anything... when I hit the power button, the green light goes on for 2 seconds. That's it.
Is there any hope for my phone? If not, I'm going to take it back to AT&T and try to get it replaced. It was refurbished and the deal is still going on, so they shouldn't balk.

Just an observation, but it sounds like it may need to be charged. You'll need to use a wall charger if it's totally dead.
Sent from my MB860 using XDA App

Even when charging for a while, it gives the same boot error 0x1000 and I can't enter flash mode... says "battery too low to flash" even after plugged in all day.

Did you plug in the phone itself? That may be not enough.
You need somehow charge the battery without your phone. Special cable, wall charger, or direct USB-to-battery connection.
I have this one:
http://www.ebay.com/itm/AC-Dock-Wal...098585?pt=PDA_Accessories&hash=item3368c56359

skywalker993 said:
Even when charging for a while, it gives the same boot error 0x1000 and I can't enter flash mode... says "battery too low to flash" even after plugged in all day.
Click to expand...
Click to collapse
Yes it's a hard brick and no solution (at least not yet). You had a soft brick until you flashed that sbf file. You flashed it and the sbf file is for android 2.2 and people who have 2.3 the use of that sbf file will hard brick the phone.

Ashenphoenix said:
Yes it's a hard brick and no solution (at least not yet). You had a soft brick until you flashed that sbf file. You flashed it and the sbf file is for android 2.2 and people who have 2.3 the use of that sbf file will hard brick the phone.
Click to expand...
Click to collapse
Not true. You can only verify a hard brick if the phone says "Entering Nvflash". As posted before, you need to charge you battery to really verify if the phone is bricked.

Actually, the error should read as this:
SVF:105.1:2
Failed to boot 0X1000​
And then it would probably just shut off without even trying to enter any other modes.
http://forum.xda-developers.com/showthread.php?t=1160408
matthew5025 said:
Not true. You can only verify a hard brick if the phone says "Entering Nvflash". As posted before, you need to charge you battery to really verify if the phone is bricked.
Click to expand...
Click to collapse

skywalker993 said:
Here's the story...
I got this phone refurbished for a penny just over a month ago. It's awesome... sexy exterior, simple form, banging specs, super fast loads and renders. However, I tried to root it so I could use a force-Webtop app (for streaming Netflix to my TV), and apparently the phone was updated before it was resold to me, so when I tried to root it bricked.
To root, I used a YouTube link I found on XDA, but got a Failed To Boot error when restarting my phone. After searching for a while, people called it a "soft brick" and said to use RSD Lite to flash the factory sbf. I followed the instructions word for word and now it won't do anything... when I hit the power button, the green light goes on for 2 seconds. That's it.
Is there any hope for my phone? If not, I'm going to take it back to AT&T and try to get it replaced. It was refurbished and the deal is still going on, so they shouldn't balk.
Click to expand...
Click to collapse
did you even unlock the bootloader or did you "just root it b4 flashing the sbf"

Take it back to AT&T. If for some reason they won't take it, go to the Motorola website and see if it still has warranty. I bought it refurbed online as well and when I got the SVF:105.1:2
Failed to boot 0X1000
screen, they were able to fix it and send it back.

Try the auto unlock method for ATRIX 4g. Ur phone is soft bricked that will fix it.
http://forum.xda-developers.com/showthread.php?p=15930466
Sent from my MB860 using xda premium

live4nyy said:
Actually, the error should read as this:
SVF:105.1:2
Failed to boot 0X1000​
And then it would probably just shut off without even trying to enter any other modes.
http://forum.xda-developers.com/showthread.php?t=1160408
Click to expand...
Click to collapse
It should flash Entering Nvflash for a brief moment before going blank. It doesn't turn off, it enters Nvflash mode, the last resort of fixing a bricked phone which only moto can use.

[Q] Defy bricked. Wont turn on, only white led on pc

I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport somehow, but i had fully charged it and i was not out all day enough for it to run out fully... I take my phone home, not really giving it much importance, and i noticed it was stuck on the bootlogo.. so i went into recovery and tried to re-flash the rom and fix it, but when i was installing the ROM again, the phone shut off randomly (i heard that happened with a certain recovery menu software sometimes, i cant remember the name)... then the phone wouldn't charge and/or turn on, and when I connect it to the pc, nothing happens other than the white led coming on.. RSD won't recognize it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it before by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOL A_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
I don't know what to do?? I read that defy's are really hard to brick... But mine got bricked out of nowhere.. wtf?

Niko. said:
I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport somehow, but i had fully charged it and i was not out all day enough for it to run out fully... I take my phone home, not really giving it much importance, and i noticed it was stuck on the bootlogo.. so i went into recovery and tried to re-flash the rom and fix it, but when i was installing the ROM again, the phone shut off randomly (i heard that happened with a certain recovery menu software sometimes, i cant remember the name)... then the phone wouldn't charge and/or turn on, and when I connect it to the pc, nothing happens other than the white led coming on.. RSD won't recognize it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it before by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOL A_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
I don't know what to do?? I read that defy's are really hard to brick... But mine got bricked out of nowhere.. wtf?
Click to expand...
Click to collapse
Hey there. Well, if it's still flashable it ain't bricked. I've got my other one to not be recognized (broken bootloader), which is beyond usual repair. So, did you you flash some random SBF before the rescue one you're trying out now? There's a problem with previously flashed GingerBread or Defy+ SBF images. So it would be good to know, what was the SBF running before trying "JORLA_U3_3.4.2_107-9". Also according to http://sbf.droid-developers.org/phone.php?device=27 that is 2.2.1 and there's also a "Android 2.2.2 Blur_Version.34.4.802.MB525.Latam.en.01". Tried that as well?
Anyhow, if the phone is seen by RSDlite it actually powers on and is recoverable. If the screen is just staying black, then you probably tried a downgrade from a Gingerbread SBF and didn't watch out for the BL-version.
If it's a BL-version problem then this might help. Also there is a guide to unbrick. And yes, keep an eye out for the battery level. Best would be an external charger, as the phone does not charge. McGyver way should still work though.
If it shows a LED and is seen over USb, it's not dead (yet)
Also look out for section "Common Problems/Questions" here.

htto said:
Hey there. Well, if it's still flashable it ain't bricked. I've got my other one to not be recognized (broken bootloader), which is beyond usual repair. So, did you you flash some random SBF before the rescue one you're trying out now? There's a problem with previously flashed GingerBread or Defy+ SBF images. So it would be good to know, what was the SBF running before trying "JORLA_U3_3.4.2_107-9". Also according to http://sbf.droid-developers.org/phone.php?device=27 that is 2.2.1 and there's also a "Android 2.2.2 Blur_Version.34.4.802.MB525.Latam.en.01". Tried that as well?
Anyhow, if the phone is seen by RSDlite it actually powers on and is recoverable. If the screen is just staying black, then you probably tried a downgrade from a Gingerbread SBF and didn't watch out for the BL-version.
If it's a BL-version problem then this might help. Also there is a guide to unbrick. And yes, keep an eye out for the battery level. Best would be an external charger, as the phone does not charge. McGyver way should still work though.
If it shows a LED and is seen over USb, it's not dead (yet)
Also look out for section "Common Problems/Questions" here.
Click to expand...
Click to collapse
No, i have not flashed other SBF's ever... only CM roms but i did it through the phone itself, in recovery mode.. I'll try the 2.2.2 one you told me about and see how that works out!
EDIT: No luck, the phone stays at a black screen.. it wont even reboot when RSD is done flashing.. i have to take the battery out and put it in bootloader again for RSD to say it PASSED the flashing

Niko. said:
No, i have not flashed other SBF's ever... only CM roms but i did it through the phone itself, in recovery mode.. I'll try the 2.2.2 one you told me about and see how that works out!
EDIT: No luck, the phone stays at a black screen.. it wont even reboot when RSD is done flashing.. i have to take the battery out and put it in bootloader again for RSD to say it PASSED the flashing
Click to expand...
Click to collapse
Too bad Anyway, did you try 8. from here, that is
"
If you get " Please manually power up this phone " in RSD Lite pull battery out > put your battery back > reboot into stock recovery by holding Power button and Vol- button > Choose Wipe data/cache > Choose Reboot system now
"? Also holding Power and Vol-Down while inserting battery is said to work.
I wonder if there is an SBF that also flashes cache and userdata partitions...

Nope, it just stays black-screened.... It only works if i do VOL-UP for bootloader mode, but that doesnt help

Umm, as a shot into the blue: Did you try to reinstall the Defy drivers from Motorola? It seems that missing those hinder RSD lite from detecting the Phone as MB52x and instead just show the Processor identification, i.e. "S Flash OMAP3630"

Try dfp 231. The processor identification is correct( rsdlite has been set up properly).
Sent from my MB526 using Tapatalk

thekguy said:
Try dfp 231. The processor identification is correct( rsdlite has been set up properly).
Click to expand...
Click to collapse
Yeah, it worked also for the defy in this thread.
And just for reference the original thread with the hinted SBF:in post #4
"
WIIII i have successfull unbriked my defy with this rom
defyplus_u3_4.5.1-134_dfp-231_cn_sign_ucadefyemarab1b50aa009.0r_pds03c_usajr dngibrird15_p015_a030_service1ff.sbf.gz
"
Basically had the same BL7-problem.

htto said:
Yeah, it worked also for the defy in this thread.
And just for reference the original thread with the hinted SBF:in post #4
"
WIIII i have successfull unbriked my defy with this rom
defyplus_u3_4.5.1-134_dfp-231_cn_sign_ucadefyemarab1b50aa009.0r_pds03c_usajr dngibrird15_p015_a030_service1ff.sbf.gz
"
Basically had the same BL7-problem.
Click to expand...
Click to collapse
wtf, the phone flashed correctly and everything but the screen won't turn on.... The computer recognizes it as MB526 now, and i can touch the home button and stuff and it will vibrate like it used to when it worked... i can also make the ringtones play using the moto portal page... Everything works (except for calls) other than the fact that i still have a black screen... the screen just wont turn on... Also it said it had very little internal memory compared to what it had before (had at least 2 gb i think.. now not even one)
I had sent the phone over to fix, and they told me it was unfixable... Is it possible that the guy (it wasnt an official company) who "tried to fix it" simply took parts out of it ? -_- (if he had taken parts out of it im guessing the phone wouldnt turn on at all..?)
What can i do to turn the screen on??
EDIT: i flashed DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
I couldnt find the one you posted there so i did the central europe one...

Niko. said:
wtf, the phone flashed correctly and everything but the screen won't turn on.... The computer recognizes it as MB526 now, and i can touch the home button and stuff and it will vibrate like it used to when it worked... i can also make the ringtones play using the moto portal page... Everything works (except for calls) other than the fact that i still have a black screen... the screen just wont turn on... Also it said it had very little internal memory compared to what it had before (had at least 2 gb i think.. now not even one)
I had sent the phone over to fix, and they told me it was unfixable... Is it possible that the guy (it wasnt an official company) who "tried to fix it" simply took parts out of it ? -_- (if he had taken parts out of it im guessing the phone wouldnt turn on at all..?)
What can i do to turn the screen on??
EDIT: i flashed DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
I couldnt find the one you posted there so i did the central europe one...
Click to expand...
Click to collapse
Umm, according to this thread it is supposed to be this one.
The GR vs CN maybe doesn't make a difference, but maybe the P022_A022 vs. P015_A030?
Doesn't a working phone portal allow for somehow to get logs/adb etc?

[Q] Defy not booting/blank screen

(Motorola defy MB525) Well, deciding to upgrade from quarx's android 4.2 to 4.4 I went and gave the whole flashing method a try again but I made a mistake on a couple areas and I was stuck in bootloader or the motorola logo appearing on and off over and over. That was because my battery was near death or pretty much dead, so I used the mcgyver method to flash it while it was being charged which 'worked'. It did the usual 'SW update in progress' and the sbf flashed, but after the phone just went to a blank screen (as if it were off) and no longer turns on or goes anywhere. Holding the power button and/or pressing the volume buttons does nothing. I cannot access bootloader or recovery or even get the phone to display. If I connect my defy to my computer, the white led charge light comes on briefly then goes away when the cable is fully connected. Thats the only thing that makes me think my phone isn't totally broke but, I cannot flash anything with RSD Lite again, it does not detect my phone as pressing the 'start' button does nothing.
I even went and bought one of the universal battle chargers thinking my battery just needed to be charged, but even after a full charge the phone has been no different. I'm at a loss, Is my cable the issue? Is my defy just busted? I really need some advice...

Anyone have any ideas? I uploaded a video to youtube showing the problem I have a bit better.
https://www.youtube.com/watch?v=Q25klbN9kWE
The same thing happens whether I have the battery inserted or no. Its very confusing.

Try to charge the battery with another defy or with an adapter, I think that has no charge

I already charged it with a universal charger (http://www.amazon.com/gp/product/B002XY5F6A/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1) But was no different. Wouldn't this have worked? It gave me the green LED (full charge) after I left it connected for a while

If mcgyver cable is made properly, and you can't enter bl, you may have bricked your device
Sent from my MB526 using Tapatalk

thekguy said:
If mcgyver cable is made properly, and you can't enter bl, you may have bricked your device
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
I thought even if a defy is bricked you can at least get into bootloader. Can I unbrick it then?

You should be able to get into bl even then, but since you cannot, for some odd reason, there is no alternate method left
The brief white led glow seems to indicate a damaged bl, as when the internal eMMC is wiped completely
Sent from my MB526 using Tapatalk

Motorola defy is not booting
Hi can any one help me on this.
I rooted my defy and upgraded to jelly bean. It was working fine for a year and after that I found issue. So I tried to upgrade to kitkat cwm11, however it didnt work. So, did a factory reset and when i tried upgrading again, it threw an error saying, unable to mount sd card and unable to clear cache and data. After this I couldnt clear any settings or upgrade anything. Tried with different SD card and it didnt work as well. Finally, phone is not booting and when I tried to go to recovery option it doesnt work, even default motorola recovery doesnt work. My phone is not detecting in computer as well. Phone stays dead on moto logo. Please tell me how to upgrade the phone.

thekguy said:
You should be able to get into bl even then, but since you cannot, for some odd reason, there is no alternate method left
The brief white led glow seems to indicate a damaged bl, as when the internal eMMC is wiped completely
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
Alright, I guess my defy is toasted :/ Thank you for the information.
gokul_eee09 said:
Hi can any one help me on this.
I rooted my defy and upgraded to jelly bean. It was working fine for a year and after that I found issue. So I tried to upgrade to kitkat cwm11, however it didnt work. So, did a factory reset and when i tried upgrading again, it threw an error saying, unable to mount sd card and unable to clear cache and data. After this I couldnt clear any settings or upgrade anything. Tried with different SD card and it didnt work as well. Finally, phone is not booting and when I tried to go to recovery option it doesnt work, even default motorola recovery doesnt work. My phone is not detecting in computer as well. Phone stays dead on moto logo. Please tell me how to upgrade the phone.
Click to expand...
Click to collapse
Open a new thread

(Sorry double post) Wow, progress!!!
I tried the mcgyver method one last time and upon connecting the second usb cable I heard the windows chime that tells a new device has connected, but still nothing on screen. On a whim I launched RSD lite and tried flashing an SBF which did work! Halfway through the flashing process the screen came on giving me the 'SW Update in progress', though after the flash I'm back at bootloader, Did the flash work? I tried flashing another sbf but same deal, just back at bootloader. Is there a certain sbf I should use?? Please help if you can I'm getting there!

Dfp 231
Sent from my MB526 using Tapatalk