I think I have finally, fully bricked my Droid 2.
A little background: This is my fifth one, mostly all for hardware issues stemming from poor craftsmanship in the refurbed phones. This one though, is gone as far as I can see it. I got this phone last week, and had waiting a week to make sure everything was fine. It was, so last night I rooted it and tried to put Epic 2.7 on it. It failed Epicly (no pun intented) and I was forced to do a full SBF on it. In the process, something got a hiccup and I was left with Droid 2 flashing "Service Required" and a RSD Lite telling me it had 100% successfully flashed. I tried once again to flash it using the SBF from a different source, and the battery died halfway through. The USB port won't even engage now so I can't charge my battery, even when it's off. When I try to turn it on, it says "Service Required" then below, it flashed "Battery Low, cannot run" or something to that effect. Well, can't flash it if I can't charge it, eh? I'm stuck in a catch-22 and I can't really see a way out.
I'm going to try my luck tomorrow and take it back to Verizon, claim it's their fault (my ERI reflash code was manually changed in one of my older phones I had received, so anything is possible now) and jump ship to a Galaxy or something non-HTC. In the mean time, is there anything I could try and do to remedy this?
Note: I didn't know where to put this, sorry if it's in the wrong section.
drburke said:
I think I have finally, fully bricked my Droid 2.
A little background: This is my fifth one, mostly all for hardware issues stemming from poor craftsmanship in the refurbed phones. This one though, is gone as far as I can see it. I got this phone last week, and had waiting a week to make sure everything was fine. It was, so last night I rooted it and tried to put Epic 2.7 on it. It failed Epicly (no pun intented) and I was forced to do a full SBF on it. In the process, something got a hiccup and I was left with Droid 2 flashing "Service Required" and a RSD Lite telling me it had 100% successfully flashed. I tried once again to flash it using the SBF from a different source, and the battery died halfway through. The USB port won't even engage now so I can't charge my battery, even when it's off. When I try to turn it on, it says "Service Required" then below, it flashed "Battery Low, cannot run" or something to that effect. Well, can't flash it if I can't charge it, eh? I'm stuck in a catch-22 and I can't really see a way out.
I'm going to try my luck tomorrow and take it back to Verizon, claim it's their fault (my ERI reflash code was manually changed in one of my older phones I had received, so anything is possible now) and jump ship to a Galaxy or something non-HTC. In the mean time, is there anything I could try and do to remedy this?
Note: I didn't know where to put this, sorry if it's in the wrong section.
Click to expand...
Click to collapse
This is the correct section And if your phone turns on at all, it's not bricked Your phone would need to be 100% gone to be bricked
Hmm. Perhaps the statement "My phone hates me and put me in a catch-22" is a better qualified statement then? haha.
drburke said:
Hmm. Perhaps the statement "My phone hates me and put me in a catch-22" is a better qualified statement then? haha.
Click to expand...
Click to collapse
Probably I was just trying to cheer you up
For you to be able to do anything if your battery is really dead you need to find away to charge it or get a charged battery to try to do another SBF. Make sure the SBF is the 2.3.20 verizon version (assuming you have the 2.3.2 update)because the 2.2.0 version won't load on your updated D2. If you aren't succeding in windows there is a linux method that anybody can try via my ubuntu livecd. I'll update this post with links when I get on my laptop.
Sent from my DROID2 using XDA App
Reboot into recovery.you should see the ! Android. Press the search button on the keyboard. Scroll down to wipe data with the arrow keys and press ok. Delete to go back to the main screen. Then go to reboot and hit ok.
Sent from my DROID2 using XDA App
This happened to me as well. You need to find another battery to use or buy a 3rd party external charger.
The phone will only charge the battery when software is installed. The phone is nowhere near bricked but you do need a full battery to SBF back to a workable state.
I don't think Epic 2.7 should be used on updated D2's because I don't think the ROM is compatible with the updated version. I could be wrong though.
I seem to remember an editor at engadget or bgr had this problem on an original droid? I think they made some Frankenstein charger with a jumper or something and got it to charge so they could fix their software. They wrote an article about it.
Related
So I had to get my screen repaired, which they did, but in turn they ruined some other things. So when I brought it back the next day, they gave me a refurb evo. Not bad, whatever. But unfortunately, it came with 2.2 which I'd never rooted before. So I started with this guide http://forum.xda-developers.com/showthread.php?t=765496 but I ran into a problem and was forced to close cmd, but then I found http://forum.xda-developers.com/showthread.php?t=787304 and tried it out, but now connecting my evo to the computer after the whole ADB thing doesn't bring up the menu. It simply charges, but says USB device not recognized. Did I mess something up real bad with the adb thing? Any help is greatly appreciated.. this is getting really frustrating
Now I'm not even sure if it's charging.. the light shows after I plug it in for a minute, but it says battery status: Discharging. The battery icon isn't showing it as charging though.. This is really starting to worry me. Refurb crap
I dont understand this:
Zori said:
and tried it out, but now connecting my evo to the computer after the whole ADB thing doesn't bring up the menu.
Click to expand...
Click to collapse
If you used unrevoked why are you now trying to use adb? What menu? My shot in the dark translation is that you told it to remember your setting to charge by default.
Menu-Settings-Connect to PC- check ask me.
I first tried the old method which I posted with the complex cmd stuff and everything, it didn't work. So then I was gonna try the simpler method of HBOOT and everything, but when I connected to the computer to get rid of PC36IMG from the SD card first it won't recognize the evo. And the default is set to charge, but ask me is checked. It doesn't ask, it just lags it for a little while and then starts charging.
EDIT: Guys this is getting ridiculous! I've tried 2 different batteries and 2 different charging cables and if I can get the charging light to turn on, it just says discharging! The phone won't even read my SD card! I don't know what to do! I'm gonna take it off the cable now so it doesn't completely the discharge the battery and hopefully wakes me up when I need it to, if the battery lasts. Please guys, I need help asap I've been working on this thing for hours and I have a midterm to study for..
Double edit: I'm gonna put it on the cable.. hoping that once it discharges all the way it'll start charging? Or even if it does drain all the way it'll stay on at least.. I can't even get the charging light to turn on right now. Man, this is horrible. I'm really really worried. I just paid $110 to get this fixed, this is driving me crazy. If anyone can help, please do.
Unrevoked, then rom manager to flash a new rom = full root in 20 minutes at the most.
To do the unrevoked method, as far as I know, I have to connect to my computer and do that HBOOT crap right? Well, I can't connect to my computer. In fact, it just rained my battery last night, shut off the phone, then charged it to about 90%. Now I turned it on again, and it's just "discharging" all over again. This is ridiculous. I'm gonna go back to the Sprint store for the fourth day in a row and probably end up getting another refurb piece of crap that won't work.
Zori said:
I'm gonna go back to the Sprint store for the fourth day in a row and probably end up getting another refurb piece of crap that won't work.
Click to expand...
Click to collapse
Um.. you broke the screen on the first one, and then you messed up the second one they gave you. So...
Award Tour said:
Um.. you broke the screen on the first one, and then you messed up the second one they gave you. So...
Click to expand...
Click to collapse
The second one had a faulty microUSB jack and it never read the microSD. I messed it up? I got another one today. Let this thread die. And you're a jackass btw ^.^
Hello XDA Community!
I made a post about this issue before, but have more details so hopefully someone can help me figure out this issue.
My phone even when unplugged from my PC continuously says USB Connected/ USB Debugging in the notification menu.
Also, when I try and reboot the phone, instead of booting even to the Vibrant logo screen, the loading circle continuously blinks on and off, without actually booting.
As I type this, I am not holding down the power button, and the loading circle is blinking on and off by itself....
I used to be able to turn the phone on into recovery mode in the past, but now when I try to reboot into recovery I get a big yellow picture that says "Downloading"
The only way the phone will turn on is if it is plugged in.
I am fairly certain that this reboot issue and the USB issue are correlated in some way.
Did anyone else have this issue with their phones? And if so, how did you solve it?
Another thing I have just discovered...
When the phone is on and idle, the USB Connection notification will constantly blink on and off, which is why I think the phone would do the same when trying to power on!
Is this a hardware issue or a software issue?
I have not flashed anything in a very long time before this issue started happening so I believe a restore is unnecessary .
Someone please help me! This is very annoying, not only do I have NO notification bar because of the constant USB Connection notification turning on and off, I cannot turn on my phone at all unless it is plugged in!
ACK!
Take it back
I carry the insurance, so personally if this was happening to me I would not even mess with it. It sounds like you have a genuine problem with the phone and it needs to be replaced.
If it is possible to do try a nandroid backup of your phone to make getting back to where you are on your new device easier. Then take your phone back to stock with the recovery image here -->
http://forum.xda-developers.com/showthread.php?t=734475 (Thank you justanothercrowd)
One you have a stock device see if you are still having the issue. If you are take it back as defective. Even if you don't have the insurance, that sounds like a factory defect and should be covered by the factory warranty. The insurance just makes the process easier and makes sure they just give you a swap out at the store rather than having to wait for repairs. It also covers things the warranty does not, such as screen breakage - which is the specific reason I carry the insurance.
Ah crap wish I had insurance.... Do I have to do that whole odin procedure or is there a one click un root procedure as well?
Sent from my SGH-T959 using XDA App
Nevermind i just read through that link you posted. So when i go to a t mobile store do i have to unroot or can i just hide my root applications until i get a new phone?
Sent from my SGH-T959 using XDA App
I actually have not had reason to go back to stock, or even use odin yet at this point. My only roms were .zip files that I flashed via clockwork recovery.
I would say that your best best it to just follow the instructions on justanothercrowd's thread very carefully and deliberately. You are already having issues with reboots and your USB port, so this is not the time to deviate into experiments.
So to cut you off and just answer you next three questions:
Q) Can I just . . .
A) No! Just follow the directions exactly.
Q) But can I . . .
A) No! Just follow the directions exactly.
Q) Do I have to . . .
A) Hey look, Just follow the damn directions exactly!
Sorry, I can't help much beyond that. You chose to modify your phone and risk that you would not have issues, just like the rest of us here. In your case you did have issues. Now you have to get it back to stock so they don't have any reason to claim you caused this or that your warranty is void. I hope all goes well and it works out for you. Let as know and keep us posted. Good luck.
Lo N Slo said:
Nevermind i just read through that link you posted. So when i go to a t mobile store do i have to unroot or can i just hide my root applications until i get a new phone?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
We must have been typing at the same time LOL.
There is a thread on unrooting, and basically it is just deleting a few things. After doing this you should not have any non-stock applications on the phone and there would be no reason to think it was rooted unless they went digging on the file system. Personally, I would delete those telltale files just in case, it looks a little suspicious to bring in a phone that looks like it has not been used since you bought it, but they have no proof you did anything and you can claim that you first did a factory reset to see if it would fix the problem.
Just want to keep this thread going, as I am having the exact same issue as the OP as of today. It happened out of the blue, and I haven't flashed anything new to my phone since JI6 was released, other than that, it's just a stock, rooted phone.
Hoping someone has an idea, but I will likely get it replaced under warranty, since the GPS has never worked either.
damnit damnit damnit I really wish I had warranty.
Random question about clockword mod recoveries.
If I were to do a backup right now, and save that file to my computer, could I restore that file later on a different phone after I root my replacement?
I don't have that many mods flashed, and I know all of the apps can be synced, but still it would be sooo convenient .
I believe that is how it works, so yes. It should be no different then when you clone a hard drive to put the image on multiple computers for easy distribution.
It is (just like the cloning metaphor) hardware specific. Just like I could not purchase a upgrade computer and expect a cloned image to work, don't expect to create a Vibrant backup and restore it on a Captivate.
That said, you should be able to restore your backup to new (identical) hardware.
By the way, what is the warranty on these? I thought it was a year for defects. I didn't think the Vibrant had been around long enough yet for anyone to be off warranty.
it should be a year, but there was also the option for a purchased warranty. I did not purchase a warranty, so I should be good on just my manufacturer's defect warranty
Being discussed here:
http://forum.xda-developers.com/showthread.php?t=817643
so my mytouch 4g wont turn on even with a different battery. i plug it it in and it gives me a flash on th screen but thats it. any suggestion without sending it in
Take it to a tmo store, they'll swap it.
I got it off of Craigslist I think it was previously tampered with
Sent from my HTC Desire using XDA App
so i was in the process of doing a custom splash screen last night. i went through all the instructions on how to push the custom splash through terminal. everything went how the instructions said, but once i reboot it my phone turned off and never came back on. it doesnt power on, boot into recovery, nothing! i put the phone to charge and the red light comes on on the top left but when i take it off the charger it stays on.
i been rooted for about a month now and i was running cm7 build 8 when this happened. i just want to see if anybody has any idea on what going on. i tired everything i can think of. taking out the battery and normally powering on and nothing. taking off the battery and volume down and power to boot into recovery and nothing. taking off the battery, sd card, sim, putting back the battery and doing both normal power on and to boot into recovery and nothing.
First of all you just hijacked the guys old dead thread and second it sound like you just bricked your phone. As there is boot animation and there is slash screen. Seems like you flashed wrong thing. If the screen don't even turn on its dead then.
Sent from my HTC Glacier
Don't flame the poor guy! He's got it bad enough as is! And he didn't flash the "wrong thing" there are several threads on flashing splash screens in this phone's forum. Cut the guy some slack. He knows it may be bricked, he's just hoping it's not. And he was hoping for someone to provide some possible help. Not be be given **** for not opening a new thread.
i thread jacked because the thread was old and didnt want to clutter by starting a new one when im having some what the same problem. but no i pushed the splash image. i had already flashed a boot animation a few day back. i had call of android running on my phone as a boot animation. i just want to know is theres other methods of reaching hboot or recovery.
First of all don't put words in my mouth as my post does not contain any flame, second when I said wrong thing I meant he may not have meet the requirement for the splash image if he did correctly then obviously he would have had it up and running. Best thing for him would be going back to the original thread where he downloaded the image and asking the OP and troubleshoot it but at this point its to late all he can do now is warn others.
But if his phone is not old lol he can social engineer and play the victim card and send it back to HTC but first would be trying TMo saying he didn't get the POST OTA as he had PRE OTA and when he try to install the OTA it went blank and act like he has no idea what is going on, as he simply just want the phone to work or he will cancel service and do acting best of his life.
i already know i probably super bricked it. becuase ive bricked it before but not like this. i was able to fix it very quickly before. its like if the phone just doesnt have a battery. im just going to wait to see if anybody else has any more input. if not ill head to the tmo store see what they can do.
BlackSHELF said:
But if his phone is not old lol he can social engineer and play the victim card and send it back to HTC but first would be trying TMo saying he didn't get the POST OTA as he had PRE OTA and when he try to install the OTA it went blank and act like he has no idea what is going on, as he simply just want the phone to work or he will cancel service and do acting best of his life.
Click to expand...
Click to collapse
I do apologize for using the word flame. It was too strong. But I get fired up when people criticize instead of offering insight. If you had posted the above paragraph first, I wouldn't have had any issues. This is good and viable option. Albeit a last resort, but much better than criticizing for thread jacking. And I am the OP of the thread that he's using and am doing EVERYTHING I can to help him figure out a way to get this resolved.
coupetastic-droid said:
i already know i probably super bricked it. becuase ive bricked it before but not like this. i was able to fix it very quickly before. its like if the phone just doesnt have a battery. im just going to wait to see if anybody else has any more input. if not ill head to the tmo store see what they can do.
Click to expand...
Click to collapse
ok, I just got caught up on your issue. I am going to do a little research and see if I can come up with anything to maybe help. Do you have adb set up? What recovery are you running?
Same thing happened to me, flashed a rom rebooted and the phone never turned on again.
thanx every one for trying to help. i tried everything i can think of and i could not get that phone to power on at all. it was completely dead. so i went to the tmo store by my pad and they gave me a brand new one. now i just need to gain s=off on this one which i cant do for some reason. i dont know why since it was fairly easy to gain s=off on my other mt4g. ill figure out though.
coupetastic-droid said:
thanx every one for trying to help. i tried everything i can think of and i could not get that phone to power on at all. it was completely dead. so i went to the tmo store by my pad and they gave me a brand new one. now i just need to gain s=off on this one which i cant do for some reason. i dont know why since it was fairly easy to gain s=off on my other mt4g. ill figure out though.
Click to expand...
Click to collapse
Don't know if you used this guide yet or not but I will post it anyway http://forum.xda-developers.com/showthread.php?t=858996
toby4059 said:
Don't know if you used this guide yet or not but I will post it anyway http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
I aready got s=off but thanx anyways.
Sent from my CM7 Glacier using XDA App
Hi.
I had the same problem on my htc glacier (mytouch 4g) which was turn it on, stuck on the htcwelcome screen, keep loading and then turn off automatically. My phone is rooted and cusome flashed to the new htc 3.0 sense when this happened, i did a back up and restore to the oem mytouch sense and now it is working just perfectly. So if your phone is rooted you might give it a shot and hope it will work again
i had same prob kinda
i flashed a rom was useing it for a week and today i went to use camera and while camera was loaded the screen shut off like not beining used it did the crt thing and all then it wouln't come out of it so i pulled battary after like 5 min of a lighted black screen and went to power phone back on and nothing like no batt.....
anyways what i was geting to is that i called tmoble and they said it sounded like a hardware problem if you can plug it in to wall or car charger and nothing.. when i plug it into a usb on pc i get
hsusbs or something so u all might want to look into that.
i have s mytouch 4g it wont boot
i rooted my mytouch 4g ussing gfree and then i installed sense 3.0 rom and it worked then force closed left me in bootloader then from there flasheed cm7 worked good for 15 days then said force closed again then never turned back on aghain now when i plug it back in it tells me cannot install drivver software and it recognizes it as qhsusb_dload any solutions or its a gonner contact me at [email protected]
Hi guys,
Tried searching for my problem, but though I found some similar stuff, noone had quite my problem.
I was checking my Nexus S after a trip and it was with the 'emergency only' message. This sometimes happens to me, not sure if it's due to the roaming activation or caused by a bug where the radio subsystem crashes after a long period without network.
Anyway, I proceeded to my common solution: Turn off and reboot.
Except that after the phone was off, it would not turn on.
It doesn't even vibrate. It doesn't show anything when connected to the wall socket or to the computer. It's just completely dead.
Now, I'm not even sure if this is a hardware or software problem. Any idea on how I can debug this?
Here's what I've tried:
1. Take the battery out: no changes (even tried leaving it out overnight).
2. Charge the phone overnight: no change.
Next step: I'll go to a store and try a different battery... meanwhile I'm without my primary phone which sucks... Can anyone help?
Thanks in advance!
Try booting your phone into the bootloader. Hold the power button and volume up button simultaneously.
If it is not the battery, i can see what else you can do, a "dont turn on" phone is a dead end...
Sent from my Nexus S using XDA App
Guess I'm screwed... I had some pics and other data there... anyway I can get it back? i.e. is there a way to remove the internal sd card?
saranyan said:
Try booting your phone into the bootloader. Hold the power button and volume up button simultaneously.
Click to expand...
Click to collapse
Was this tried? Cause if that works there's hope for you yet.
BlackHawkA4 said:
Was this tried? Cause if that works there's hope for you yet.
Click to expand...
Click to collapse
Yup, it was one of the first things I tried. No sign of life... I can't get a single sign that the phone is even being powered. It's like the battery was taken out.
nunocordeiro said:
Yup, it was one of the first things I tried. No sign of life... I can't get a single sign that the phone is even being powered. It's like the battery was taken out.
Click to expand...
Click to collapse
Sounds like something is wrong with the hardware then. Have you brought it the store? Might need to get a new one on warranty.
I have the same issue with my old Blackberry 9000. It worked fine up until I stopped using it. Left it in a drawer for a few months. Went to sell it to Sprint. Wouldn't turn on. No LED, no nothing. Worked fine months before when I was still using it. To this day I have no idea what's wrong with it and it doesn't turn on.
Why not get an external battery charger and charge the battery up and then test it?
All true, and after trying with a new battery I'll have a bit more information.
But what strikes me as odd is that I didn't leave it in a drawer - I didn't even let the battery run down... it was just a damn reboot! I shut it down, and then couldn't power it up again (try and imagine THAT happening to you). It would be odd for the battery to be sucked dry all of a sudden...
I have a feeling that there's something else... maybe while shutting down something burned out in the power circuitry....? =S
No one ever heard of anything like what I'm experiencing? It sucks to be the only one!
Thanks for all the help so far, guys!
If you can get to download mode nothing is lost. Just flash new image via Odin.
Sent from my GT-I9000 using Tapatalk
nunocordeiro said:
All true, and after trying with a new battery I'll have a bit more information.
But what strikes me as odd is that I didn't leave it in a drawer - I didn't even let the battery run down... it was just a damn reboot! I shut it down, and then couldn't power it up again (try and imagine THAT happening to you). It would be odd for the battery to be sucked dry all of a sudden...
I have a feeling that there's something else... maybe while shutting down something burned out in the power circuitry....? =S
No one ever heard of anything like what I'm experiencing? It sucks to be the only one!
Thanks for all the help so far, guys!
Click to expand...
Click to collapse
Never heard of that happening, but it's a possibility... Still, I would first attribute it to a bad battery and try that first
Sent from my Nexus S 4G
With a new battery (that works on another nexus S) still no luck. =(
I still can't find anyone with this problem. I feel like the unluckiest idiot on Earth.
I assume I can't get to download mode since I can't even get the phone to report it is charging (it used to do that even if off). Do you want me to try anything, though? I'm open to suggestions until Monday. Then I'm taking it to Samsung. Hope they can recover my pictures.
BTW, my receipt doesn't have the IMEI and a customer service rep told me I need it on the receipt or they won't give me free support. How can I get it with the phone off?
Regards and thanks to all who responded,
Nuno
nuno, if you cant power on even with a new charged battery, then it's a harware fault and nothing can me done... =o\
but thanks for the advice, i never thought about the data in sd card, i guess i should make some backups! =o)
nun
BTW said:
Look under your battery. IMEI should be printed on the sticker beneath. Good luck!
Click to expand...
Click to collapse
I've got the same problem: dead nexus s after a reboot. It says "no service" emergency call does not work. I tried pretty much everything like switching the battery, recovery mode, plug it in, etc. I even updated its image to the latest I've got access to. No luck. I'm already contacting samsung to get it replaced.
odd things can happen ... it sucks
igorgatis said:
I've got the same problem: dead nexus s after a reboot. It says "no service" emergency call does not work. I tried pretty much everything like switching the battery, recovery mode, plug it in, etc. I even updated its image to the latest I've got access to. No luck. I'm already contacting samsung to get it replaced.
Click to expand...
Click to collapse
Did you try flashing a different rom? Or radio/
I haven't experienced this myself but I'm very interested on what happened. Did you guys flash any custom ROMS? or Radios for that matter?
This looks very similar to what i have. I just got my nexus s GT-i9023, it doesn't boot into fast boot, recovery, download mode or normal. The most activity i have got so fare is when i take the battery out, put it back it, and try turn the phone on it will sometimes flash then do nothing. I have looked every ware. When i use "./platform-tools/adb get-state" it returns "unknown". Any help would be great.
What i think i did was this:
- Unlocked bootloader, this worked
- restart
- installed clockwork mod with fast boot, this worked
- wiped data
- wiped cache (correct me if i spelt that wrong, or anything else)
- flashed cyanogenmod, this got an error but i didn't notice it the first time and i can't remember what it was.
- flashed gapps, this didn't work, when i restarted the phone it said that the installer for gaps had quit.
- restarted
- flashed cyanogenmod again, this is when i noticed the error
- restarted, didn't change anything
- wiped data
- wiped cache
- flashed i9020t recovery, this http://forum.xda-developers.com/showthread.php?t=1061855 i think this is what stuffed it up because my phone is i9023
- wiped data after flashing, thats what it said to do, i thought it was strange but i went along with it.
- wiped cache
- reboot
- now doesnt work.
Take it to the store where you purchased and claim ignorance!
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: