Need help, I bricked my Defy Green lense.
Some how after trying to flash a miui rom, it went to bootloader after I pressed the "reboot device now" in the clockworkmod recovery. So I tried to flash my sbf, but in the reboot, the phone just turned off, an haven't been able to turn it on, I already tried the Mc Giver method to charge the phone, (as it worked before) but the phone does nothing,
Any help would be thanked...
Sent from my PC36100 using Tapatalk 2
Use RSDLite and an original SBF to flash it back to normal operation.
Questions go in the Q&A section
That Android you put on it?
You must try to put exactly the last ROM haved one Defy ...
ScYcS said:
Use RSDLite and an original SBF to flash it back to normal operation.
Click to expand...
Click to collapse
I was flashing the original SBF with RSD Lite, right after, during the reboot, it turned it self off, an from then on, I haven't been able to Even Turn It On, it shows no activity what so ever...
Sent from my PC36100 using Tapatalk 2
Try it again maybe with a different SBF and flash it again with RSDLite?
ScYcS said:
Try it again maybe with a different SBF and flash it again with RSDLite?
Click to expand...
Click to collapse
Thanks but I can't even get it to the bootloader screen, that's why I thought it didn't have battery and tried to charge it the normal way, an since nothing happened, I tried the McGiver way an it didn't work either...
Sent from my PC36100 using Tapatalk 2
USE This and careful defy SBF Or Defy+ SBF
http://forum.xda-developers.com/showthread.php?t=966537
OR this For Downgrade to eclair If Flashed 2.3.x
http://www.4shared.com/rar/xzT3dMXv/JORDN_U3_972151.html
Related
I tried to flash Fizzion rom and then all it would do is get stuck at the M. . Then i couldn't get clockwork recovery to come up.. I tried to sbf and it keeps failing at the very end of a long ass process.. I used sbf on this phone once before and had no problems.. Now it doesn't do anything but go to the bootloader. .It's a friends phone so im kinda freaking out..
What version were you on and what sbf versiln did you try to flash?
Sent from my DROIDX using XDA App
2.3.15 trying to use 2.3.15 sbf
Can you boot into stock recovery? (Home and power, at triangle push search button once)
If you can, try to wipe data and cache.
Sent from my DROIDX using XDA App
I wish i could boot into stock recovery.. doesn't do anything but go to the bootloader.
boredmug said:
I tried to flash Fizzion rom and then all it would do is get stuck at the M. . Then i couldn't get clockwork recovery to come up.. I tried to sbf and it keeps failing at the very end of a long ass process.. I used sbf on this phone once before and had no problems.. Now it doesn't do anything but go to the bootloader. .It's a friends phone so im kinda freaking out..
Click to expand...
Click to collapse
Some friend you are.... Lol.
Sent from my DROIDX using XDA App
lol.. well now it boots up.. I said it failed the sbf flash but it booted into stock 2.2. . wtf?
boredmug said:
I tried to flash Fizzion rom and then all it would do is get stuck at the M. . Then i couldn't get clockwork recovery to come up.. I tried to sbf and it keeps failing at the very end of a long ass process.. I used sbf on this phone once before and had no problems.. Now it doesn't do anything but go to the bootloader. .It's a friends phone so im kinda freaking out..
Click to expand...
Click to collapse
Sometimes it will say it failed at the end, but it just isn't overwriting bp-passthroug. This isnt an essential file if you are already on the same version as the sbf you are using. These are radio files I believe... So if this part fails...oh well. As long as it is writing the system files, that is what you should be concerned about for the most part.
Please help...very similar situation I am in as was boredmug. I Flashed the Fission Rom...then it got stuck on the "M" boot animation...I did some research and used RSD Lite 4.8 to flash 2.3.15 sbf from bootloader... It started working fine and then right at the end of the process my bootloader said "Battery low...Unable to program". I know my battery was fully charged..
Could I just need a new battery maybe?? hopefully???
jeraspie28 said:
Please help...very similar situation I am in as was boredmug. I Flashed the Fission Rom...then it got stuck on the "M" boot animation...I did some research and used RSD Lite 4.8 to flash 2.3.15 sbf from bootloader... It started working fine and then right at the end of the process my bootloader said "Battery low...Unable to program". I know my battery was fully charged..
Could I just need a new battery maybe?? hopefully???
Click to expand...
Click to collapse
I had this happen to me before. You will need to charge your battery before you continue. I hope you did not fry out your battery as this has also happened to me. Give it a full charge as well.
There is a full 340 SBF that you can use with RSD Lite as well as a zip, maderstcok for 340. With the maderstcok update ( which works just as well as flashing with RSD Lite ) it doesn't matter which bootloader you have as long as you are on 2.3.15. It will update all files so you are on the latest version of Android.
Make sure you guys are wiping data/cache as well before SBF or installing new ROMS.
When I plug the phone into USB port and the led is green and the bootloader still says "Battery low, Cannot program." Would it help to get another battery?
It also says "NEW_MAP Blank" above the battery low message. Does that have something to do with it?
Sent from my Ginger Tazz using XDA App
jeraspie28 said:
When I plug the phone into USB port and the led is green and the bootloader still says "Battery low, Cannot program." Would it help to get another battery?
It also says "NEW_MAP Blank" above the battery low message. Does that have something to do with it?
Sent from my Ginger Tazz using XDA App
Click to expand...
Click to collapse
USB port charging is not enough to charge the phone properly. You will need to charge the phone with the wall charger while the phone is off or take it to a Verizon store so they can charge it for you. Usually the batteries from VZW come with less then half a charge. They can also test your battery to make sure it's still good.
I finally solved the problem by "rigging" up the battery to another USB cable wires. Crazy, but it worked. I'm all good now.. Thanks.
http://www.droidforums.net/forum/te...ons/99781-droid-not-booting-odd-behavior.html
Jeremy
So I tried to SBF back to 2.3.340 like I done before and now I get stocked on the red M logo. When I try to go into recovery I only get to the exclamation point and pressing the search button doesn't do anything!!
What can I do?
Help please. I don't see an answer on the forums
Thanks
UPDATE: I had the system-only SBF. Found the SBF full and it worked.
Now try to figure how to install the zip files because my phone is not letting me
Venc said:
So I tried to SBF back to 2.3.340 like I done before and now I get stocked on the red M logo. When I try to go into recovery I only get to the exclamation point and pressing the search button doesn't do anything!!
What can I do?
Help please. I don't see an answer on the forums
Thanks
Click to expand...
Click to collapse
It sounds like you did the "system only" sbf.. Make sure it's the full sbf
Sent from my DROIDX using XDA App
bigshotrob22 said:
It sounds like you did the "system only" sbf.. Make sure it's the full sbf
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Hey,
Is it even out? I don't see it online
EDIT: I think I found the full SBF. I'll try it. Thanks
UPDATE: bigshotrob22 you are awesome!! Thank you it worked!!! Now I have to cancel my order for the replacement LOL
That happened to me. I SBF'd back to .340 and still had the Red M logo from the Gingerbread .595.
I was unable to get into recovery at all. I eneded up not having the phone for the day and did the SBF again when I got home, you can still access the bootloader, just not recovery (or atleast I was able to) to do the SBF back to .340.
You said you have done the SBF before..my issue with was I did not go into the factory recovery FIRST and wipe all data. I have since done three SBF's and wipe data (in stock recovery, not BOOT STRAP) first. I wiped data, DID NOT REBOOT device. Powered off, and went straight into the bootloader to SBF.
That seems to work for me now.
If it is the samething that happened to me...the wipe did not completely do its job. I make it a habit to wipe 3-4 times before doing anything.
try pushing the volume button up& down at the same time instead of search
Sent from my DROIDX using XDA App
I think i bricked my Droid X. i was running Rubix Focused and tryed to flash GingerAle 3.0 and now it just sits at the moto "M" logo. i can get into the recovery by pulling the battery but even after a wipe and a recovery it still just sits. did i brick it, and if so how can i fix it? please help, reletivly new to flashing roms.
P.S. I'll love you forever if i can fix it =)
now i think i really did it. I tried running a recovery image from a few days ago and now i cant get back into the recovery menu...
Sounds Like SBF Time
Sounds like SBF is going to be your friend here, if you don't know how, head to
http://forum.xda-developers.com/showpost.php?p=11118819&postcount=2
and look for "SBF: What is it, and what does it do?!?"
OK, so i SBFed the phone, got all the way through it, got to the phone is rebooting and it just sits at the Moto "M" again. did i SBF wrong or what?
EDIT: I can get into the stock recovery... sort of. i can get to the ! with the droid next to it but nothing happens when i push the search button.
hmm, I know GB doesnt use the search button to pass that, try using vol UP+DOWN at the same time. perhaps the stock recovery isn't modified from SBF?
Woot that worked. got into recovery. wiped data and tryed a reboot, got stuck at logo again. should i try flashing back to the Rubix focused i had before?
Edit: it now boots into <3e> recovery and i get the e: signature verification failed instillation aborted when i try to install Rubix or Gingerale.
You can't install a custom roms from stock recovery
Sent from my DROIDX using XDA Premium App
try doing a full wipe data/cache a couple of times. that usually works for me
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
YAY
Fixed it!!! yay!! I had to flash the full SBF file, not just the system one. thanks for the help guys
thats ur best bet. full sbf
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
I need to get my defy back to stuck cause I'm having issues with the camera (it is always getting an error «cannot connect to camera») and I need to have it replace.
I restored nandroid of my original stock rom, removed 2nd init, unroot the device, I even factory reset and format my sd card.
Thing is when I turn the phone on, led blinks blue and if press volume down it goes to but menu, is there any option to remove that as well?
Can't flash full sbf because non of them is the same as my stuck rom and if they notice anything and they always check everything, I won't get the phone replace.
Thank you for helping me
Sent from my MB525 using xda premium
Any help?
Sent from my MB525 using xda premium
JakeOcn said:
Any help?
Sent from my MB525 using xda premium
Click to expand...
Click to collapse
just full SBF Help u. try
http://sbf.droid-developers.org/umts_jordan/list.php
jalal-jap said:
just full SBF Help u. try
http://sbf.droid-developers.org/umts_jordan/list.php
Click to expand...
Click to collapse
Is there any other way to fix that? because my usb port is broken so I cant flash an sbf :/
In Bootmenu you have a option to remove it. Once you entered the bootmenu on blue led, goto System and choose to uninstall BootMenu.
Hello... I am using defy red lens. Yesterday I was flashing a new ROM but that ROM stuck in a boot logo.
I go to the stable recovery and and wipe everything but that didn't help. So I tried to flash it by RSD Lite but the problem is windows doesn't detect my phone. It says the device is malfunction.
Actually this problem always happens in the previous ROM which I was using(Mokee OS revised) and I searched through internet and find that this problem arises because I use defy+ build and flash GB Kernel. That's why I decided to change the ROM.
But now I am stuck in the boot menu. All I can do is 1. Access bootloader 2.Access stable recovery.
Does anyone know how to solve this problem? sorry for my english.
abhi9029 said:
Hello... I am using defy red lens. Yesterday I was flashing a new ROM but that ROM stuck in a boot logo.
I go to the stable recovery and and wipe everything but that didn't help. So I tried to flash it by RSD Lite but the problem is windows doesn't detect my phone. It says the device is malfunction.
Actually this problem always happens in the previous ROM which I was using(Mokee OS revised) and I searched through internet and find that this problem arises because I use defy+ build and flash GB Kernel. That's why I decided to change the ROM.
But now I am stuck in the boot menu. All I can do is 1. Access bootloader 2.Access stable recovery.
Does anyone know how to solve this problem? sorry for my english.
Click to expand...
Click to collapse
for defy plus nah need to flash GB kernal nd try to connect yo fone by any other comp....
deepugustin said:
for defy plus nah need to flash GB kernal nd try to connect yo fone by any other comp....
Click to expand...
Click to collapse
I cant go to recovery. All I can see that the boot logo. I can access BootLoader and stock recovery. And stock recovery has no option of ' Install from SD card'. What can I do now.
Make sure you have latest drivers and rsdlite. Run rsdlite with administrator privileges. Try another computer if it still doesn't work. Make sure you are in bootloader mode.
You can also try compatibility mode.
Sent from my MB526 using xda app-developers app
hotdog125 said:
Make sure you have latest drivers and rsdlite. Run rsdlite with administrator privileges. Try another computer if it still doesn't work. Make sure you are in bootloader mode.
You can also try compatibility mode.
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Tried everything that you said but it didn't help.