Related
My Nexus one won't turn on. I tried flashing RADIO 32.24.00.22U_4.03.00.21_2 that I downloaded from Modaco.
After it failed to install showing the error message like
"Multiple Radio images"
and a few others I try to reboot it.
when trying to reboot it there showed a picture of a android and a orangish arrow and a box.
Help...I think I bricked it.
Help?
Please?
Can you get into boot loader? Hold down the track ball, then power on, and keep holding down the track ball...
Also, try holding down the "volume down" toggle button while powering on if the track ball method doesn't work...
If both don't do anything but take you to that same screen, let it sit on that screen for a bit, say 10 minutes just in case...
If still nothing, see what happens when you plug your phone into your computer with the data cable, is it recognized? If so, can you get ADB to recognize it?
Jackasaur said:
Help?
Please?
Click to expand...
Click to collapse
can u get to the recovery image? if u can, its not bricked.
well I tried plugging it into the computer, I tried the wall charger, and nothing seems to work. The LED doesn't come on, and the button combination doesn't work. So I think it's dead for good. :C Before everything got screwed All I saw was a box and an arrow pointing at a android. Which I think meant it was unboxing. I then thought it froze so I tried to take the battery out, and after that it didn't turn on anymore. No LED, no recovery, no nothing. :C Quite sad.
Why the f are so many people intent on taking their batteries out while the phone is updating? I'm not saying that led to the bricking...but it probably didn't help.
Jackasaur said:
well I tried plugging it into the computer, I tried the wall charger, and nothing seems to work. The LED doesn't come on, and the button combination doesn't work. So I think it's dead for good. :C Before everything got screwed All I saw was a box and an arrow pointing at a android. Which I think meant it was unboxing. I then thought it froze so I tried to take the battery out, and after that it didn't turn on anymore. No LED, no recovery, no nothing. :C Quite sad.
Click to expand...
Click to collapse
This part takes a few minutes. I am not totally sure what is happening at this point but I'm assuming it's not good to remove battery during this. Mine sat on that screen for a few min and then finished.
Try to boot up with volume down button held. Then use volume arrows to choose recovery and hit power.
uansari1 said:
Why the f are so many people intent on taking their batteries out while the phone is updating? I'm not saying that led to the bricking...but it probably didn't help.
Click to expand...
Click to collapse
Everyone expects everything to be instant these days... "Uh oh! The screen isn't doing anything, it's been at least 20 seconds! I could just wait and leave it for a few minutes like all the guides say to do. Or I could take my battery out...how could that hurt, right?"
For me it took a good 3-4 minutes on the screen with the arrow and the box.
Anyways, if you can't get to the recovery then you might be buying a new N1.
ahh it took like 5 minutes for me, I have to admit I was a little worried since you dont see status bars or anything, but like said, the guides warn for this.
I cant imagine that removing the battery broke it though, he should be able to load a recovery image
I feel sad for him so bumping
Bleh. I'll just have to wait and see. I'll contact HTC.
tomsan84 said:
ahh it took like 5 minutes for me, I have to admit I was a little worried since you dont see status bars or anything, but like said, the guides warn for this.
I cant imagine that removing the battery broke it though, he should be able to load a recovery image
I feel sad for him so bumping
Click to expand...
Click to collapse
If you remove the battery during the period he did, which is when the phone is actually flashing the radio ROM, yes removing the battery can and likely did break it for him. There are 2 ways to brick an Android device, while flashing a radio ROM and while flashing an SPL...
OP, have you tried any of the button combos we have recommended? Have you tried putting your battery in the phone, then without turning it on, putting it on the charger to see if it can charge the battery at least (you said it wasn't even turning on, which is likely because you have a dead battery)... charge the battery first, then try the button combo's we recommended.
And please, when you report back, and not to sound like an ass, do so clearly and systematically (I can't tell from your posts what did or didn't happen, and whether you tried anything we suggested, nor what the current state of the phone is)... so, please use this format to make it clear to us trying to help:
Battery: Charged or Wouldn't Charge (LED will come on if it is charging)
Trackball+Power: Booted into boot loader, yay! or Went to the damn box
Volume down+Power: Booted into fast boot! or Went to the damn box
And remember, you have to hold down the button, either trackball or volume down, then press the power and keep holding down the trackball or volume down until it either goes to boot loader or it goes to the box screen... you might want to even wait for a minute on the box screen(if it goes to that) while holding down the button to make sure it can't get into boot loader...
Okay so I took the battery out, put it back in, and tried charging it. The Battery LED did not come on, so I'm guessing it's not charging.
The Trackball+Power did not work.
The Volume down+Power did not work.
I think I most likely broke it, due to the fact that I took the battery out while it was flashing the radio ROM onto the phone. I kinda did it on a impulse, which is my fault. So do you think it'd be possible if I did contact HTC they'd send me a swap, and not be able to make my phone work or turn on, and everything will go on as if I "broke" it and not unlock it or anything?
Jackasaur said:
Okay so I took the battery out, put it back in, and tried charging it. The Battery LED did not come on, so I'm guessing it's not charging.
The Trackball+Power did not work.
The Volume down+Power did not work.
I think I most likely broke it, due to the fact that I took the battery out while it was flashing the radio ROM onto the phone. I kinda did it on a impulse, which is my fault. So do you think it'd be possible if I did contact HTC they'd send me a swap, and not be able to make my phone work or turn on, and everything will go on as if I "broke" it and not unlock it or anything?
Click to expand...
Click to collapse
It sounds like you have a true brick... disruption of the radio ROM flashing causes lots of bricks, and did so for you.
It is pretty common, at least with T-Mobile with the G1, to call them up and tell them your phone asked you to update, and while updating it froze and won't turn on or charge anymore. Not sure if HTC will handle it the same as T-Mobile did, but if they do they will just send you a new unit, you send the old one back, and you are back up and running... they might ask that you send it to them first, but there is no way for them to test if it was rooted/unlock boot loader if it can't be powered on, so you should be fine.
Sweet. So I called HTC, and they said they'll repair it, but I asked for a swap instead, so I'll be getting one by either Wednesday, or Thursday. Good stuff! I'll tell you all how it goes. :] Now I am stuck with my Nokia N95. Thanks for all your help.
Did you tell them you have an unlocked bootloader?
uansari1 said:
Did you tell them you have an unlocked bootloader?
Click to expand...
Click to collapse
he doesnt have 2 tell em
lightforce said:
he doesnt have 2 tell em
Click to expand...
Click to collapse
Yeah, he doesn't have to tell them... but they don't have to cover his phone either.
If they find out it's unlocked after the fact, they can charge you to repair the phone.
How exactly will they know he unlocked the bootloader if the device cannot even properly turn on, unless htc has other methods of being able to "restore" the phone, then he should be rather ok. Am I not looking into this deeply enough? Can the phone turn on with a new battery or something? Does HTC have alternatives ways of checking?
Eclair~ said:
How exactly will they know he unlocked the bootloader if the device cannot even properly turn on, unless htc has other methods of being able to "restore" the phone, then he should be rather ok. Am I not looking into this deeply enough? Can the phone turn on with a new battery or something?
Click to expand...
Click to collapse
That's my point man.. I don't know. All they have to see is that open padlock and they can deny the claim.
Hi all,
I have had loads of problems with this phone, so I decided to do a factory reset.
It rebooted as normal until it got to the Motoblur setup page
It asks for the Motoblur details to be entered, but once you have entered them and pressed the 'next' button, it goes back to the previous screen instead of the next step and then gets stuck in a never ending loop.
I've tried skipping the sign in process but instead of skipping it, it just goes back to the first Motoblur account setup screen instead.
Out of desperation, I have tried to make several new Motoblur accounts but every single time, it gets to 80% completion, then stops.
I have even left running all night (plugged in) and it still freezes at 80%
I can't do another factory reset because it won't get past the Motoblur setup screen.
I've tried to do a hard reset by holding x and powering the phone on but this doesn't work. It just brings up the triangle and android robot but it does not go to the next step despite me leaving it for several minutes.
Only had it for 7 weeks and am awaiting a response from Expansys on what to do.
Any help from you guys will be greatly appreciated.
Apply a debrand image of your system and do a full wipe
phorenzik said:
I've tried to do a hard reset by holding x and powering the phone on but this doesn't work. It just brings up the triangle and android robot but it does not go to the next step despite me leaving it for several minutes.
Click to expand...
Click to collapse
Have you pressed the @ key when you get to this step with the robot and the triangle? That should bring up the reset menu, and then you use the volume and camera buttons to choose and select the option you require.
Cheers,
Steve.
StevePritchard said:
Have you pressed the @ key when you get to this step with the robot and the triangle? That should bring up the reset menu, and then you use the volume and camera buttons to choose and select the option you require.
Cheers,
Steve.
Click to expand...
Click to collapse
I didn't know you had to press @
Thanks
I've done a hard reset, but I still have the exact same problem.
If I try to input my proper Motoblur details it instantly says connection failed (it doesn't seem to even try to connect as fails the instant you press 'next)
Creating a new account hangs at 80%
Any more ideas before I throw it against a wall?
I notice there was an option to boot from SD in the recovey mode.
Would this allow me to boot an official motorola rom?
If so, where would I get the rom from?
A walkthorugh on exactly how to do this would be appreciated if this method could fix my issues.
I'm really annoyed because I sold my HD2 for this phone and I'm regretting it.
Thanks
phorenzik said:
I didn't know you had to press @
Thanks
I've done a hard reset, but I still have the exact same problem.
If I try to input my proper Motoblur details it instantly says connection failed (it doesn't seem to even try to connect as fails the instant you press 'next)
Creating a new account hangs at 80%
Any more ideas before I throw it against a wall?
Thanks
Click to expand...
Click to collapse
I think you need internet connection in order to validate your account or create a new one. Check your APN settings first, or do it on wifi.
Hi,
I've tried it whilst connected to my wifi router. I've even tried it via the data connection but nothing happens.
It seems that despite the data/wifi connections being there, it just ignores them.
I think this is the issue. It's not connecting and I don't know why
The phone displays the wifi/3G data symbols in the task bar but it doesn't seem to be using them during the Motoblur setup
Mine is dead too!!!
Hello everybody,
Greetings from sunny, flooded, blown away, Queensland Australia!
Long time lurker, first time poster...
I have a...
Vodafone-Australian-2.2-Milestone2
2 weeks old and its an expensive paper weight. It was rooted and thats about it, had a bunch of root required apps on there, installed the bootstrap, but hadnt installed Xrecovery yet.
I was playing around the other day. changing settings, installing and uninstalling a heap of apps, testing them. Some app suggested I restart or it restarted itself, cant recall, and that was the end. Boots until it gets past the M, and then its just bootloop city.
Won't register on comp in RSD or anything. Will boot to stock recovery and cleared cache and data several times, but that didnt fix anything. Won't even charge the battery. It will run an update but has to be signed. Problem is, we havent had any updates yet on these phones in Australia and there are no custom roms. What update.zip could I get to try to fix it, because I think thats about my only hope.
While recovery was wiping the data and cache it would stop frequently and each time I would touch the ok in the bottom corner of the screen and it would continue, and seemingly despite the 10 or more stops, completes fine. Surely thats not normal.
Out of ideas, I would just send it back with a story but the vodafone boot animation is replaced with disco flashing lights. and thats all it does, non-stop. Do you think they will notice someone has been tinkering?
Ideas? Thoughts?
Oh, and forgot to mention, when I first got it I had the same problem with the Motorola sign in wizard on startup, for quite a while, cant remember how I got around it though. Stop trying to sign in and just get out of that wizard, install ADW Launcher or similar and dont go near any Moto apps. You are only required to do a Gmail sign in, not Moto.
That's the problem though.
I'm stuck at the Motoblur sign in and it will not skip.
Whenever I select skip, it just goes back to the motoblur sign in page instead of going to the home screen.
Basically, in a nutshell, this is what's wrong:
I can't sign in to motoblur (gets stuck in a loop)
I can't create a new motoblur account (crashes at 80% every time)
I can't skip the sign in process (takes me back to the motoblur sign in page instead of loading home screen)
This is my first and last Motorola phone. Not good at all.
So what happens if you press press home or back repeatedly instead of skip? And if all fails reflash new SBF
benking1972 said:
So what happens if you press press home or back repeatedly instead of skip? And if all fails reflash new SBF
Click to expand...
Click to collapse
It just goes back to the motoblur setup/signin screen no matter how many time I press home, back or skip. It's as if a dll is missing and it's unable to boot to the home screen.
How do I flash a new SBF?
Motorola have agreed to let me return it but if I can do it myself I'd rather do it.
I have found this guide http://forum.xda-developers.com/showthread.php?p=11155476#post11155476
but the link to the UK SBF is dead
Yeah, that's the one, and the link to UK SBF works fine for me. If you can't get it to flash that way, then you are going to have to do it the way I am about to do mine, which is...
http://forum.xda-developers.com/showthread.php?t=804088
Failing that, send it back and be done with it.
since its so new id send it back. you shouldnt be having this problem at all. the milestone 2 is a very solid phone. i had mine running for 90 days straight not even a reboot or crash or anything lol. sounds like you just got a duff one. with any piece of technology theres bound to be a few that slip through the net. even if you find a fix for your problem you dont know what is causing it. and if youve had problems before then somethings obviously wrong. since theyve agreed to let you return it then thats your best option.
Probably i should send mine one back as well.
Bought a new Milestone 2 yesterday (from ebay, Chinese guys but as per retail package phones are for UK market). Put the SIM in just to check before wiping out everything from my old Defy. Made a call, checked the version and the menu and put the SIM back to Defy to backup all I needed. Plugged Milestone to the mains. 3 hours later found promising "Fully charged" on the screen and put the SIM in. That was it... Since I can't power the phone whatever I do. I thought the Power button went off as I tried to perform hard reset (x+Pwr), BRM (Arrow up+Pwr) and nothing happent at all. But then I put the phone on the charger again and the Power button worked fine switching the screen off and back on.
Any other methods to get the phone running?
UPDATE: It's strange and weird, but I've just had an idea to remove SD card and it worked - the phone powered on immediately!! Formatted the card using card reader, put it back - the phone works flawlessly. Fantastic! =))
Hello all. First let me state that I rather not make a thread to ask help on a problem that seems to have happened to a few owners, but my knowledge as to how I could resolve the issue is severely lacking..
At some point today my phone was ringing but the screen would not show. I thought about taking the battery out and turning it back on but there would be no HTC, Bootanimation, anything. It was Just a black-lit screen which responds due to tactile feedback and the four touchkeys light up as usual. At first there was an odd sound that would play after a few minutes so I decided to charge it but again there was nothing. Even tried to access bootloader with -Vol and Power still no screen.
I asked a friend of mine to call my phone to see if it would ring but they said it instantly goes to voicemail as if my phone was off. Note that I WAS SURE IT WAS ON.
Adb seems to work with it as it seems whatever I need to do I have to do it through there.
G2 rooted with gfree method
CM7.1 RC1
Clockwork Recovery
Again i am sorry if I bothered those with posting something others would think is "too common of a problem" as I have no experience in fixing this issue. Plus I would like to try any option available as I would not like to try and have my phone replaced (because of the risk of discovering root and obtaining a G2 with stock gingerbread which is currently not rootable)
Please help..
It sounds like you're suffering from some sort of hardware failure. You need to send your phone in for repair/replacement.
The Unnamed Time Lord said:
Hello all. First let me state that I rather not make a thread to ask help on a problem that seems to have happened to a few owners, but my knowledge as to how I could resolve the issue is severely lacking..
At some point today my phone was ringing but the screen would not show. I thought about taking the battery out and turning it back on but there would be no HTC, Bootanimation, anything. It was Just a black-lit screen which responds due to tactile feedback and the four touchkeys light up as usual. At first there was an odd sound that would play after a few minutes so I decided to charge it but again there was nothing. Even tried to access bootloader with -Vol and Power still no screen.
I asked a friend of mine to call my phone to see if it would ring but they said it instantly goes to voicemail as if my phone was off. Note that I WAS SURE IT WAS ON.
Adb seems to work with it as it seems whatever I need to do I have to do it through there.
G2 rooted with gfree method
CM7.1 RC1
Clockwork Recovery
Again i am sorry if I bothered those with posting something others would think is "too common of a problem" as I have no experience in fixing this issue. Plus I would like to try any option available as I would not like to try and have my phone replaced (because of the risk of discovering root and obtaining a G2 with stock gingerbread which is currently not rootable)
Please help..
Click to expand...
Click to collapse
A. They don't care if its rooted.
B. You can root stock Gingerbread.
Same issue here...
I'm facing the same issue, when i try to unlock the phone (power button or trackpad) the screen lights but stays black, and the buttons are also backlit. I have to lock again with power button and unlock again to get to the actual screen.
It first happened a few days ago, and since i didn't reboot/restart in weeks i tried to reboot but the same issue comes back.
then i shut it down, pulled the battery and then back, and restarted: the phone goes directly to that black backlit screen, i tried several times and tried recovery with no luck, so i thought my phone was messed up although i did have some haptic feedback, well in fact the phone was actually booting, but just not showing anything else than the backlit screen; i waited a minute or so to the booting completes (still shows nothing), then i lock/unlock the screen again and there it is, asking for the pin code.
I tried to go to the recovery again to try to wipe dalvik-cache, i know for sure it goes to recovery, but with a totally black screen, not even backlit this time; the trackpad is too sensitive in the recovery to just blindly navigate in the menu, so it is not useable at all.
Then i had the idea to go to Rom Manager, i reflashed the rom from my sd-card, and enabling wipe dalvik-cache, which worked (all through a black screen). After a few minutes i "felt" it rebooting (vibrating) but still back to that black backlit screen, and i locked/unlocked it again and back it was asking pin code...
I also tried to roll back recovery to 3.0.2.4, since i remember i updated it a few weeks ago, but still the same issue.
I don't know what else to do without accessing the recovery, i wanted to try another kernel, or remove the trackpad wake... is there a way to do it via a script? I guess it's what Rom manager does...
Next step will be a total wipe, but i need to make some room on my sdcard for backup purposes first...
If anyone has an idea to sort this out, i'm highly interested...
I'll try to get a logcat, maybe could give a hint
Edit: Virtuous sense 2.0.0 (used it with no issue since it came out, could it be a hw issue?)
Edit2 : attached logcat
Is the pin screen differant than the usual one ie white number keys? If it is that's the sim lock screen you need to call the carrier to get the code or find out the default. Or just get a new sim lol
nah it's the 4 digit pin code, i didn't lose it btw, it's still working and i can use the phone, but i have a black backlit screen whenever i want to wake the phone, and thus when i receive a phone call, i don't know who it is and i blindly press/swipe the screen to answer, because if i want to use the same trick of locking /unlocking, it doesnt work as the lock button is also used to reject a call...
Maybe rip and reinstall the phone app?
asim0 said:
I'm facing the same issue, when i try to unlock the phone (power button or trackpad) the screen lights but stays black, and the buttons are also backlit. I have to lock again with power button and unlock again to get to the actual screen.
It first happened a few days ago, and since i didn't reboot/restart in weeks i tried to reboot but the same issue comes back.
Click to expand...
Click to collapse
I have the same exact problem as this EXCEPT, it's intermittent. Sometimes when I wake the phone I get an all black but backlight screen, and other times it's fine. I'm on CM7.1.
But a superwipe and reflash will probably fix it. Also don't restore system data on TB
I know i still can use wipe data + cache + dalvik through rom manager, and i always used to superwipe before switching roms, but how can i do that now when the recovery is all blacked out?
can anyone guide me to a script or something i could do while the phone is active, to tell him to reboot to recovery and flash that superwipe?
anyway i'll try the regular wipe and keep the thread updated
---------- Post added at 02:42 PM ---------- Previous post was at 02:35 PM ----------
SuperDave81 said:
EXCEPT, it's intermittent.
Click to expand...
Click to collapse
On my side if i leave the phone locked more than 30 seconds, it happens 100% of the time; also I noticed that now the backlight blinks 2 or 3 times (1 second blinking) when locked, first a few minutes after locking, and then randomly, about 3 or 4 times per hour; I guess it's getting worse;
I've read on another thread that it could be video cable getting loose, but since mine is still under guarantee, i won't open it right now just to check, if i can't fix by wiping / superwiping (when i know how to), i'll use that guarantee, which is one month left (lucky me)
EDIT: one other thing that makes me think it's no hardware, when the black screen appears because of a phone call or a message, the ringtone and notification sound are both half as loud as they should be, this is all really strange
after backing up my data, i reflashed the rom via Rom Manager, and I wiped data and cache (which equals to factory reset) this time: the first screen that should show the pin code numpad was already a black (backlit) screen!!
Also, thinking about it, i realised that the "flash rom from sdcard" menu in Rom Manager is in fact "Flash ZIP from sdcard": the zip doesn't have to be a ROM!!
So I tried flashing a new kernel this way, also some framework modifications (extended settings, removed TP wake, etc...) they all install Ok, but still this black screen...
Also I was about to flash SuperWipeG2.zip this way, but if it doesn't fix my problem, I will be stuck with a blacked out recovery, as SuperWipe wipes everything including /system; so if anyone has an idea to tell Rom Manager to flash two zips (Superwipe then Rom) i'll be willing to try, or a script to do that;
Maybe i'll have a look of the scripts in Superwipe and in the rom, and put both zips together... don't know if it's possible?
Maybe I'll try the Superwipe alone if I can get a spare phone, just in case...
Other thing:I used the phone's gps for more than 5 hours with the screen lit, and it never flickered even once; so it's hard to believe it's a screen connection issue...
Just to keep this updated, everything i did, including superwipe didn't change this issue, so i sent it back to the technical support (under guarantee) and I got it back today; the report that came with it says the screen has been replaced; so it was hardware finally...
Hi, i have same problem.. Black screen in recovery and during the boot. When the system boots, screen is OK. Sometimes i have also blackscreen when I want to use HW keyboard. I tried 4ext, reflash older versions of CW but still the same. I can see a screen through Android Screen Monitor and I can cotrol it. But phone is blak, only backlight. Can somebody say, how to solve this issue?
So, for other, if you cant see screen, you can use Android Screen Monitor for Windows and connect phone through USB and see a screen.
G1ForFun said:
A. They don't care if its rooted.
B. You can root stock Gingerbread.
Click to expand...
Click to collapse
WAIT one minute... they don't care? where was I when this meeting took place?
I had this issue as well on a spare G2 I had.
The screen was just black but you could tell it was lit, hardware keys were lit as well.
The phone was actually my brothers and it rooted w/ CM7.
I ended up selling the phone as is on Ebay but after some research it was a failure in the hardware for the screen and I found extensive instructions on how to replace it that I didn't wish to do.
I never attempted to get it replaced and kind of wish I did now if they don't care about the device being rooted.
I purchased my G2 before he had his, and it's never had the issue so not sure what to think of it.
Saintfyre said:
I ended up selling the phone as is on Ebay but after some research it was a failure in the hardware for the screen and I found extensive instructions on how to replace it that I didn't wish to do.
Click to expand...
Click to collapse
I think I have similar issue, can you post where you found those instructions?
Thanks in advance!
http://www.youtube.com/watch?v=u-dR8CHEGjY&feature=youtube_gdata_player
Sent from my HTC Vision using XDA Premium App
I used the same tutorial to change the LCD but after I put the new its just the backlight but nothing else... I will give it another go maybe and have a look again at those ribbon cables! I guess...
---------- Post added at 10:59 AM ---------- Previous post was at 10:09 AM ----------
I found on ebay: HTC-Desire-Z-T-Mobile-G2-A7272-Slide-Flex-Cable-Ribbon
or I found also with the chassis for a bit more.
Thinking to buy this, it would be great if anyone could confirm that it would help "my condition" ?
THanks in advance!
In terms of cables, yes the flex cables are what you want.
Sent from my T-Mobile G2
I originally posted this over on the MotorolaDefy.com forums, but it seems to be pretty dead, so I'm going to quote over my post and then update it with what I have tried since.
Generally, I don't like to post on forums asking for assistance, I know how many repeat problems you guys probably have to read, but I don't know what else to do at this point. I've had my Defy running Cyanogen Mod for months, and earlier today I noticed the Wifi wasn't connecting properly, so I rebooted it. Lo and behold, it became stuck at the Cyanogen Mod screen, it might have something to do with me installing BusyBox earlier in the day. In anycase, I followed this guide: (link removed, since this is my first post - not really important since I figured out the McGyver trick) to attempt to fix the problem. Now the phone won't boot at all, I can't even get to the boot loader screen. RSD Lite still recognizes the phone when it is plugged in, and the white light still comes on when it is charging. I'm scared ****less to take any further actions without input from somebody with more experience. I have to head out to work now, but I wanted to post this before I left. If anybody has a solution to my problem (and I'd be grateful), then I'll attempt it in a few hours. All I'm trying to do is reset it to factory default so that I may reload Cyanogen Mod onto it. The phone worked beautifully up until this point. I am on Telus and I live in Canada, if that is at all relevant. Thanks!
Click to expand...
Click to collapse
So, since then, I've gotten my screen working again, I had to use the McGyver trick (gypsy-rigged usb cable to the contacts of the battery) to jump start the bootloader, and I managed to flash in the Froyo 2.2, 3.4.2-179 sbf. It ran! Thank god in heaven! But... it got stuck at the T-Mobile logo consistently. Next, I tried flashing in Froyo 2.2, 3.4.2-177 sbf. Again, it miraculously boots but it hangs at the pulsing Motorola logo.
That brings me to where I am currently, which is; I have absolutely no idea what to do next. All I want is to get my Defy up and running with a stable version of Cyanogen Mod again. It ran flawlessly before and I loved my phone, best phone I've ever had. I'm stressing out pretty hard, and I've tried all I can find on the internet. Please, XDA, help me!
Edit: I doubt this is relevant, but more information can't hurt, so I'll add that my Defy is one of the newer ones with the red-lense.
Have you remembered to wipe data and cache (factory reset) in stock recovery?^^
If you still have that data from when you ran cm7, and you're trying to boot stock, it could prevent you from booting! Happened to me once and i just couldn't see what the problem was! Really annoying.
That sounds like it could be the issue, you're supposed to be able to do that by holding volume down while powering it up, correct? Because that doesn't seem to do anything for me.
Not working? Strange. Hold volume down before pressing power button and keep it pressed untill you se a warning triangle. Then hit both volume keys to enter the recovery. Still not working?
Sorry, I should have been more specific, I can get to the little Android guy and exclamation mark, but when I touch the bottom right corner, no menu comes up. I've never actually had to access the stock recovery before, Cyanogen made it so simple. Am I supposed to be doing something other than tapping the screen?
Update: Google is my friend. I found a suggestion that I hit the up and down volume buttons at the same time, and the menu appeared! I wiped the cache and all the use data (important stuff is on a memory card anyway, I'll just have to get my contacts back). I did get an error, reading: "E:Can't mount CACHE:recovery/log". I rebooted the system regardless and IT BOOTED!
Thanks for pointing me down the right path, I owe you and this forum a great debt!
I'm now going to charge this bad boy back to full before I attempt to reload Cyanogen. (Since having wires hang out the back is starting to get old.)
I managed to short out something doing the McGyver trick, because I'm getting the question mark battery problem. Hopefully it's an issue with the battery and not the phone. I'm incredibly disappointed, the phone is fairly new and I loved it, and don't have the money to drop replacing it since there are more urgent things to attend to. I guess all I can do is hope for the best.
As of now, it won't even boot. I'm going to try the battery in a friends phone and his in mine to try to identify the problem.
Lunk23 said:
I'm going to try the battery in a friends phone and his in mine to try to identify the problem.
Click to expand...
Click to collapse
I always recommend THIS solution over the McGyver method. Defy is farely often owned phone, so guys... first of all, don't let the battery drain completely; second - if this happens, don't rush into jump starting it. Try all other options first, ask somebody to recharge your battery and don't do McGyver, unless you've run out of other options.
Now try connecting your phone to the wall charger and don't try to start it for at least an hour. I've had plenty of cases when brand new Defy, Defy+ or Atrix, that have never been rooted, leave alone jump started, show the battery with "?" in it when battery drains completely and takes some thirty minutes or so of charging until the phone is able to start again.
Good luck, my friend!
I had made this. .... just in case it can help you
http://forum.xda-developers.com/showthread.php?t=1551472
Help me, XDA Developers, you're my only hope. I've tried everything else, and no luck. It just keeps getting worse.
First off, my girlfriend and I recently purchased a used Motorola Defy to replace her broken G1. When the guy we bought it from showed it to us, it was working perfectly. We put her SIM card in, and it was fine. So we paid for it, brought it home, and everything was fine. We set up the phone, and quickly realize that the old owner's account was still registered, and the only way to unregister them was to reset to factory defaults. And this is where everything went to hell.
Shortly afterwards, the phone became very irratic. It would only turn on when it decided to. The LED light would SOMETIMES light up when it's plugged in, but not all the time. And when we managed to get it to turn on, it'd either get stuck at the Motorola logo, or go all the way in and then freeze up about two minutes later. I figured it might be the firmware. Maybe the original owner had installed a custom ROM without telling us, and resetting to factory default had messed up somehow. So I decided to (possibly re-)root the phone, and install Cyanogen. After 500 startup attempts, which was just enough to get it to turn on 3 times, and configure root setup and install the bootloader, I am now completely unable to get the phone past bootloader. What's worse is, even though I've got the Cyanogenmod install file on the microSD, Clockworkmod can't mount the card. At all. It is now taking even more attempts to turn on, and it refuses to get past the recovery console/clockworkmod.
TL;DR: It keeps getting worse. I'm half expecting it to turn into a pile of dust by the time I'm done trying to fix it, and everything I do that SHOULD make it better just makes it worse. Please help D:
Update: The phone will no longer even turn on... In order to get the LED to turn on, I have to remove the battery, unplug the phone from the USB, replace the battery, then replace the USB. I don't think that's helping...
See you have a full battery and try to flash stock froyo sbf.
The sbf: http://forum.xda-developers.com/showthread.php?t=966537 (chose any froyo sbf form there fe CEE DEBLUR)
How: somewhere here http://forum.xda-developers.com/showthread.php?t=1216982
After the flashing with RSlite go to stock recovery and wipe data(factory reset) from there. (see how in above threat)
It could well be that he had an outdated custom rom that wasn't able to do a good factory reset from settings. Tho I advice you to take a look at CM7 or a MIUI ROM cause it is really much better then the stock rom's. Everything takes less time and on the CM7.2.0 stable release there are less bugs than in the official rom.
Please report back
Still trying to get it to turn back on. But if I do, I will try that. thank you.
Try pressing Press power+Vol up. You should get into bootloader mode. If you don't get white tekst, your battery is to low. The easiest way to solve that is to find someone with a defy and loan it's battery for a day. Then do the Press power+Vol up and connect to rds lite... (read further is all-in-one defy beginners guide).
If you can't find someone with a defy, you can go McGyver (There is a link in the Wiki page or just google)
Well, I *was* getting the error on the bootloader saying battery too low. So I left it to charge for a bit, now I'm getting absolutely nothing. Not even lighting up anymore... -sigh- I don't think there's any hope for this thing...
UPDATE: Well, after leaving it for a few minutes, I managed to get it to light up. Right back to the "Battery Low Cannot Program" message. -_-
Another update: Won't charge. Still getting the same damn error.
MacGyver'd the **** out of it. Got to the bootmenu, successfully installed Nordic, now running beautifully. Thank you so much for your help, I was about ready to test this thing's physical durability. D:<
DJLols said:
Well, I *was* getting the error on the bootloader saying battery too low. So I left it to charge for a bit, now I'm getting absolutely nothing. Not even lighting up anymore... -sigh- I don't think there's any hope for this thing...
UPDATE: Well, after leaving it for a few minutes, I managed to get it to light up. Right back to the "Battery Low Cannot Program" message. -_-
Another update: Won't charge. Still getting the same damn error.
Click to expand...
Click to collapse
You need to get a fully charged battery, i've heard of people cutting their wires or something to charge the battery, but once it has enough of a charge you can flash it with RSDlite like labsin said,
I had this problem too. RSDlite is the only thing that'll get it to boot up again, and then
"You need to do a data wipe. Press vol- and power. You will get an exclamation mark and android. It is the stock recovery. Next press both vol+ and vol- together. You will enter custom recovery. Do a data wipe from there.. That should help.. "
Good luck!
That's exactly what I did, actually, and it worked like a charm. Thank you, though. ^_^