So i was messing around with the Bootmenu the other day and deleted everything in the internal memory including the framework, now my Motorola Defy won't switch on, and RSD lite won't recognize it. i have an external battery charger and a second battery so the battery isn't the problem. Can anyone help?
RIP unfortunately, no way to recover as yet
Sent from my MB526 using Tapatalk
Related
Problem: Phone wont turn on, at all. Completely unresponsive
Now for the lengthy story.
My original x had liberty aosp running nicely with an OC set on boot at 1200. A nice clump of pixels died randomly one day, so I called verizon for a replacement. I got my replacment refurbished X in the mail, and sbf'd to froyo, for rooted gingerbread upgrade.
I nandroid backed up my old X. I then installed liberty aosp to my new X, and then immediately restored the nandroid from the old X.
My new phone was running great for about a day, then I went and added some changes from the UOT Kitchen, and installed the app that makes the logcat the boot animation.
Again, the phone worked fine for a day or so, then while I was running google maps, it rebooted randomly.
It went through the boot logo, to recovery, so I just hit reboot. It went all through the boot animation, then back to the boot logo, then back through the boot animation.
I made it back to the home screen, then left it alone. After a while it rebooted again on its own. Sometimes the screen would black out, and be completely unresponsive. I pulled the battery, then put it back in, and it wouldn't turn on.
Sometimes, it would take the battery being out for 5 minutes for the phone to accept it, and turn on.
Now, just repeat the two previous paragraphs a few times, and you will get what happened to me.
After a while, I just restored my old working nandroid from the old X. It too had the same problem. I figured it might be my OC, so I set the settings back to stock. Same thing still..
I was then going to wipe data, and install liberty aosp again. The phone was in the recovery menu, so I went to mount usb storage, plugged it in to the computer, and nothing happened.
So, I unmounted usb storage, and hit reboot. The phone booted to the bootloader menu. I unplugged the computer, then tried to power off the phone, but the power button didn't work. So I pulled the battery......
Now the phone wont turn on at all. The battery was at a 70 percent charge at the final time it worked.
Once, I got the phone to boot to the bootloader menu, but once I got my sbf ready to go, the bootloader menu had frozen. Phone was unresponsive to inserting usb, and the sbf program didn't read my phone as being connected.
Again, im now back to a for real bricked phone, that when I hold the power button, it wont turn on. I did leave the phone plugged in, and later today, im going to try using a friends battery...
My dilemma, is now I can't send the phone back for another replacement, for fear it will work at the shop, and they will see my rootedness, then charge me for a new phone, even though im 99% percent sure nothing I did caused this crap.
Anybody have any ideas?
Sent from my DROID2 using Tapatalk
Sent from my DROID2 using Tapatalk
Refurbs not rootable??
I am having similar problems with a refurb X. I have SBF'd several times. The latest was using the Linux mehtod. Then I do the data and cache wiping and install CM7 Nightly 42 and Gapps.
Most of the time when the screen times out and goes to sleep it doesn't come back. When it does, it is by rebooting itself.
Other times it will just randomly reboot.
A few times I have had to remove the battery.
I am going to try a different ROM today and see if that changes things.
Use the linux too found here, has worked on many bricked phones, will work if you can get phone into bootloader mode for sure
www.droidxforums.com/forum/droid-x-sbf/23638-linux-solution-your-windows-rsd-lite-problems.html
DROID X running liberty GB V.8
STAYFROSTY777 said:
Use the linux too found here, has worked on many bricked phones, will work if you can get phone into bootloader mode for sure
www.droidxforums.com/forum/droid-x-sbf/23638-linux-solution-your-windows-rsd-lite-problems.html
DROID X running liberty GB V.8
Click to expand...
Click to collapse
That is exactly what I used to SBF. It works to SBF but when I load CM7 the device starts the random reboot and freezing stuff.
Does it only reboot with CM or does it do it when you sbf as well? If it does it when after you sbf, that is a legit problem. I would suggest if it does it in sbf, leave it unrooted and return it, they wont be able to tell it was rooted because sbf takes you back to stock froyo.
Sent from my NookColor using XDA Premium App
Mine continued to reboot after I SBF'd back to 2.2.1. I went ahead and did the upgrade that was pushed over the Verizon network and now it doesn't reboot.
Could it be something with the newer released Droid X devices and the kernel used in the OTA upgrade by Verizon?
Hi all,
Nasty problem with my 1 month old Motorola Defy+ (MB526)
Last weekend I installed ICS9 from Quarx (20120318 build). I did this using 2ndinit CWM. Made an android backup of my stock setup, I did this over my stock SBF 4.5.1.-134_DFP-74. Used the gapps.zip and battery fix.
The system worked pretty well, but time by time it was unstable. When turned off, it had lots of difficulty to boot up again, lots of reboots and 2-3 battery pulls.
I was planning to flash another ROM when I had the time. Yesterday it worked well, started fully loaded, used it as MP3 for long time, when I went to sleep it was 48% (the accu).
This morning, I stepped in car and phone turned out to be dead. Connected it to my car charger, and it came back to life. However, immediate reboot etc. So I decided to (while driving) put back my stock nandroid backup.
It all turned out well. Stock ROM booted but gave the notice (translation from dutch): "Battery of your device is invalid and cannot be charged. Replace the battery with a battery from your Motorola"
hmm, tried it with my USB cable at the office, and now at home again with the normal charger..
What happened? Any ideas on how to solve this?
The complication is that now my device is rooted and has 2ndinit starter, warranty is more difficult.
Solution: red lens battery fix
I’m not sure it’s exactly the same issue, but my Defy+ totally refuses to charge with Quarx CM9 build 20120318 + CM9 kernel from [1].
Unfortunately I noticed only once the battery was dead empty.
I couldn’t even get it to boot with the USB charger pluged in, and the only way I could get it to boot again was to charge my battery pack in friend’s Defy.
Then I applied the « Battery fix for red lens » provided here [1] which kind of fixed the problem. Now the battery charges again, but it won’t charge over 80/85%.
I had done a « Clean battery stats » from the boot menu after installing CM9 before this whole story, so I don’t know if it had any effect.
If anyone knows better please let me know!
The instability you noticed may be due to the Android debug bug… in CM9 builds. You have to leave Android USB debug (from System params->Debug features, translated from french on, otherwise it will lag like hell most of the time and drain the battery due to the init process eating up the CPU.
[1] http://forum.xda-developers.com/showthread.php?t=1432100
Hi, I installed the battery fix immediatly after flashing the Quarx ROM, so that should not be the problem.
In the meanwhile I have been trying some things with the battery calibration software. That one flawlessy sees that my battery is 100% charged (i did that using the mcguyver method). But, resetting the calibration file on the phone won't help.
In the meantime I have been able to delete all traces (2ndinit boot, titanium backup and unrooted my phone) so I am considering to RMA the phone, no matter the fact how long that is going to take..
Unless, someone here has a last excellent advice..
fokkeh said:
...the mcguyver method...
Click to expand...
Click to collapse
Great! You have just fried your battery (like a few others who tried going McGyver). Get a new battery now and don't use the McGyver method again
From what do you draw this conclusion?
The battery showed more problems BEFORE i used the mcguyver method than after. When the problems started I never even heard of the method. I used it to regain life in my mobile (which I am using atm) and charge the battery, which was succesfull. Charger over USB does not work (because battery is not recognized), but that problem occured before the mcguyver.
So until now for me it did not cause the problem, but it helped me to be able to use my phone again, much better than before. I performed the method very accurately and I am 100% sure it did not make contact with connectors it should not connect to.
fokkeh said:
From what do you draw this conclusion?
The battery showed more problems BEFORE i used the mcguyver method than after. When the problems started I never even heard of the method. I used it to regain life in my mobile (which I am using atm) and charge the battery, which was succesfull. Charger over USB does not work (because battery is not recognized), but that problem occured before the mcguyver.
So until now for me it did not cause the problem, but it helped me to be able to use my phone again, much better than before. I performed the method very accurately and I am 100% sure it did not make contact with connectors it should not connect to.
Click to expand...
Click to collapse
Well now that your phone is alive, then go to stock and reclaim warranty! Do RMA.!
Yes I will, restored everything to stock and deleted trace from MicroSD.
But, I am still annoyed by the fact that my phone will be gone for 3-4 weeks
fokkeh said:
Yes I will, restored everything to stock and deleted trace from MicroSD.
But, I am still annoyed by the fact that my phone will be gone for 3-4 weeks
Click to expand...
Click to collapse
I understand that bro!! Even my phone was away for couple of weeks recently! Just pray they don't flash the latest SBF(BL7_ as they did in mine!
Does flashing a full sbf not work either? like this http://forum.xda-developers.com/showthread.php?t=1574651
Puckying said:
Does flashing a full sbf not work either? like this http://forum.xda-developers.com/showthread.php?t=1574651
Click to expand...
Click to collapse
Hi, this morning everything changed again, I decided to give it one more try with the latest Quarx CM9 nightly (20120330), wiped data, flashed nightly.zip, gapps and kernel but waited with the battery. After that I wiped cache, dalvik and battery stats.
Reboot and battery seems alive? very strange. But I don't want the kind of buggy CM9 builds anymore, so decided to put back my 2 hours old nandroid backup, using Restore.
Strangly, battery problem was back again. ****! Than just for fun I did data/cache/dalvik/battery stats wipe on stock, and that did not help either.
Now I am back on CM9 again, but thats running O.K. (battery is working!) but not stable enough for me. CM7 (cannot remember which build) gave the problem as well.
With the latter in mind I think (and thus agree with you) flashing a fresh SBF will probably solve the problem, but I am not 100% sure. I want to be able to put back my stock setup for possible RMA. My stock is 4.5.1.-134_DFP-74 and I cannot find that one on internet. And I cannot put it back to stock otherwise right?
The one Pranks gave you in your post (4.5.1-134_DFP-1321) is that a deblurred one? Because when I put a new one, I would like it to be a deblurred. I hate all the bloatware.
I have no idea, but I think he said it was from his own defy so I am guessing it the complete original blurred thing.
---------- Post added at 01:57 PM ---------- Previous post was at 01:31 PM ----------
I redid the cm9 flashing too and now at least it is telling me the battery is charging. But it stays stuck at a big battery icon and a red led is on.
Will see if it goes past that screen with a bit more juice.
---------- Post added at 02:06 PM ---------- Previous post was at 01:57 PM ----------
Yessss, it started up!
All is fixed. I flashed the proposed stock non-fixed SBF and now running stock 2.3.6 without any battery problems. Excellent The SBF is rootable.
I removed BLUR by editing build.prop as proposed somewhere on this forum. you have to perform full wipe after editing the build.prop) I am very happy with me new DEBLURRED stock. Titanium can remove other bloatwhere like "cardiotrainer".
Happy
fokkeh said:
All is fixed. I flashed the proposed stock non-fixed SBF and now running stock 2.3.6 without any battery problems. Excellent The SBF is rootable.
I removed BLUR by editing build.prop as proposed somewhere on this forum. you have to perform full wipe after editing the build.prop) I am very happy with me new DEBLURRED stock. Titanium can remove other bloatwhere like "cardiotrainer".
Happy
Click to expand...
Click to collapse
Cardiotrainer however for me is one of the most imp app!!
I've had my defy for quite some time now with no special issues.
Flashed quarx CM10 several months ago and worked great for a long time but now it stays stuck on the CM logo and doesn't boot.
No problem getting into bootloader but doesn't go into recovery mode. Tried pressing down button and then powered up my phone but nothing.
The one thing that might be relevant is this happened after installing "bluetooth file transfer", enabling bluetooth (normally off on my defy) and transfering several google apps to another phone. Worked fine for a day or so and then just wouldn't boot.
Anyone have any suggestions?
If you can access custom recovery then backup your data and reflash ROM. If not start from sbf.
Sent from my MB526 using xda app-developers app
Dear all,
It happened to me twice that after I put my replacement battery (BF5X for Defy originally) in my Defy+ phone, I was stuck in CM boot loop (blue circle). I'm using version cm-10-20130709 specifically. I'm not 100 percent sure if this caused the boot loop, but I couldn't use my phone afterwards even if I changed back to the original battery. Eventually I had to flash it to work again. I'd really like to use my spare battery cause it's convenient.
I'm a little scared to change batteries now, even though I'm not absolutely positive that these issues are linked. Nandroid backup and recovery (teamwin tools) are also not working for me what makes the situation even worse. Did anybody else experience this problem?
Thanks. Best wished! Yours hoopy frood
It seems that changing the battery wont cause bootloop issue.But some times it was.when u get the battery out of the defy,and let it lose power for 2~5mins,the clock in motherboard will be shutdowned(seems that it also had other works been stopped),so at this time, your defy will gets random bootloop(probably yes).what u should do is pull the batt out are get it in again,and boot again!
Sent from my MB526 using xda app-developers app
Hi,
I tried to change ROM (from default) ad install googleapps my Defy+ and never got to the point where I saw android load up.
During the hole process everything ran 100%.
On the last system reboot nothing happened.
Now all i get on screen is:
Boatloader 0.9.1
battery low
cannot program
I have read many forum threads ans watch many videos but nothing worked.
I installed RDS Lite but am not sure which SBF to donwdload.
Plus, even if I get the correct sbf I never get to the message needed on the phone.
All I ever see is:
Boatloader 0.9.1
battery low
cannot program
Any ideas how to get the phone back to working condition?
Thanks