Related
Deleted by user
I suggest you to completely charge your phone for half a day and then try to power it on. It should at least get stuck in the M logo.
Sent from my MB525 using XDA App
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Was your battery low when you tried flashing? It will not charge in bootloader mode so if you're battery is low you will have issues. If you boot with volume up pressed does it give you a message?
Try the Mcgyver battery fix found in this forum.
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse
Deleted by user
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
gookia2000 said:
Hi all, I am a proud owner of a t-mobile defy (for about 2 months now!) and my hands got itchy today and went ahead to "debrand" it following the guide by Higgsy.
I was trying to flash a uk 2.21 rom onto my t-mobile defy (rooted with z4root).
Well, I managed to do all the steps of the guide. my phone was recognised by rsdlite, i selected the uk 2.21 sbf file, i clicked start, and it started flashing the different code groups. Finally, it said "finished" and "PASS". Here is when the problem started. The phone did not reboot into android. It was just a blank screen with a white light on the top (where the green led is to inform you about new messages.)
i panicked and disconnected the phone (the white light turns off after disconnecting), took out the battery, tried rebooting, tried rebooting into recovery (power + vol down), tried rebooting into bootloader (power + vol up). Nothing worked. it just stayed dead.
I then plugged it back into the computer. immediately the white light came back on and rsdlite recognised my phone. i tried flashing again - same result. I then tried flashing the 2.52 uk rom - same result.
even more panicky now, i unplugged everything and decided to take a nap and hopefully think of some ingenious solution to the problem. now, after a 3 hour rest, i tried plugging the phone back into the computer. the white light comes on, but now rsdlite doesnt even recognise the phone.
In essence, is my phone bricked? I cannot:
1) load into recovery to do a nandroid restore (yes, i have a nandroid backup copy)
2) load sbf files from rsdlite. every sbf file i tried doesnt seem to work. now its worse as rsdlite doesnt even recognise my phone.
i have even tried doing a nandroid restore via adb. but i get the error message that no phone was detected in the command prompt. perhaps its because the phone was not started in recovery mode.
The only explanation i can think of is that i have recently updated to the t-mobile 3.6.360 update and that might be the reason why so many people before me were able to flash their defy's roms successfully while i got stuck.
Can anyone please help? I LOVED my defy more than any other phone, and 2 months was too shortlived!
Click to expand...
Click to collapse
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse
Deleted by user
Actually, all you have to do is press the power button while the LED is on and RSDLite is running. You will hear the USB detection sound and your phone will appear on the list. It won't appear as it normally would but it will be listed.
Then just choose the Froyo ROM and then click start to flash it. It'll take less than 10 minutes...
There's no other way that I know of to get it working. Even in the link that I posted, you can check and see that no one even bothered to give me an idea of what to do. I had to figure this out myself.
I figured it was the bootloader protection that was causing the problem so the logical choice was to flash the only T-Mo ROM available which happens to be the leaked Froyo.
It's been almost 24 hours and I've had no problems with FroYo so as far as I'm concerned, I'm good.
gookia2000 said:
Beach Head, thanks for your reply. you have provided me with a glimmer of hope!!! the leaked tmobile froyo sbf is one i have not tried. I will certainly try to flash my defy with that once i have gotten it recognised by rsdlite.
I believe my phone is currently not being recognised by rsdlite due to insufficient battery. (cant confirm this, as all i see when i plug in the usb is a white light on my phone. but ever since i started this entire nightmare, i think i have attempted flashing at least 5 different sbf files and considerable battery has been drained.) I will try the Mcgyver battery fix next.
skateguitar, THERE IS HOPE!!! i havent confirmed it yet but i think we all got stuck cos we were trying to flash from a "non-downgradeable" 3.6.360 firmware. and rsdlite does not recognise our phones due to low battery (your phone was left with a white light on after flashing for 1 whole night.) SO... i propose this course of action: 1) perform the Mcgyver battery fix and try to get our phones recognised by rsdlite first. 2) once recognised, flash with the leaked tmobile froyo sbf.
Does anyone have any better suggestions before i plunge head first to save my phone?
Click to expand...
Click to collapse
Yes all i wanted to say was that you might have lost your downgradability and thats why phone does not boot. Simple thing is to flash the original sbf like what beachhead suggested. It definitely should work.
Sent from my MB525 using XDA App
Guess what, it works!!!
Deleted by user
Glad I could help you out!
Enjoy Froyo!
gookia2000 said:
OHMYGOODNESS!!! I LOVE YOU GUYS!!!
My Defy has been flashed with the t-mobile froyo leaked rom and IT WORKS!!! I was so mentally set with the idea that my defy has been bricked and I just threw $400 down the drain... NOW I AM SO HAPPY!!!
Anyway, just for your information, here is what I did:
- I first tried to get my defy recognised by rsdlite. I tried Beach Head's suggestion of pressing the power button while the led is on to no effect. I reckon that the battery has just been drained too low. So, i went ahead with the McGuyver battery fix.
- Alas, with the wires protruding precariously from my phone, rsdlite finally recognised my phone. I went to load the leaked t-mobile froyo rom and went ahead flashing it.
- And, guess what, IT WORKS!!!
Thank you all so much, especially beach head, for your help in this forum! I would have gone to the mobile store to get another phone if not for you guys!!!
Click to expand...
Click to collapse
I have the same problem, and will probably end up trying to flash the leaked Tmobile Rom.
Can you point me to where you downloaded this file? I think I found the thread, but I want to be sure
Deleted by user
got it! Thanks!
Now to ultimately decide if I want to flash this, since it's non-downgradeable
To update, flashing this rom has fixed my phone. Yay! Thanks!
I wonder if it was the 3.66x update that Moto pushed out - this phone was brand new, bought in Dec 2010, no other hacking done on it...
Beach_Head said:
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
Click to expand...
Click to collapse
How did you get it to show up in rsd
I'm not working on my phone because i think i messed it up enough, so i took it to a store that fixes phones. The guy told me that he had my battery on a universal charger and he still cant get rsd lite to recognize it... What can i do
Another Happy Defy User
Just to confirm, I was seeing the same thing gookia2000 was seeing. Here was my resolution in case it helps anyone:
I was able to get mine working by flashing the US Stock Froyo build as explained in this thread: http://forum.xda-developers.com/showthread.php?t=938708&highlight=bricked&page=2
I found this thread to be super helpful as it helped me confirm my suspicion that the battery being low was the issue: http://forum.xda-developers.com/wik...#Recover_Nearly_Bricked_Phone_.28hopefully.29
Thankfully my wife has the same phone so I borrowed her battery, otherwise I would have been going McGyver style per Sorensiim (da' man) as seen here:
http://forum.xda-developers.com/showthread.php?t=892026
So happy this nightmare is over - running Froyo is a little bonus love!
Thanks to all @ XDA!!!
-Dave
Defy wont come on get a white light!
im having the same prob i did the the steps but its not working is there anything else i can do or is there a video of the proceeder
I have the same issue with a Telstra defy. I can get RSD to recognise something is connected but it isnt listed as MB525 like before but as "S Flash OMAP3630" I have flashed various SBF files but nothing is changing.
Good morning, Motorola Milestone 2 Users.
Today I will tell you something I've been through while trying to install a new ROM.
First of all, I've used RSD Lite v4.9 to flash the 2.2 version of android on an already 2.3 MS2, which made me has the impression I've bricked the phone.
I was flashing the 2.2 with the RSD and then suddenly the phone stopped working and the progress on the software asked me to power up manually the phone, which was impossible.
I removed the battery and have put it again, but for my desperation, nothing.
This will be basically a manual to:
http://forum.xda-developers.com/showthread.php?t=1420276
If your phone don't boot or show anything, but it brights the charger light on the left of the phone, it means it's already on bootloader screen, so, just put a usb data cable and plug it in your computer and run RSD and put the newest .sbf file and flash it.
Is your phone working ok now though?
If you don;t mind this shameless plug of my own thread, some more information can be found here
It contains information about what custom roms you can use other such things, and hopefully I have included how to fix any other problems you might run into. Should you look it over and think im missing something just let me know and I'll add it in with due thanks
Holy mother DreadPirateDan, I am really sorry, I tried to help, I looked for it over and over and didn't find this post of yours, I am really ashamed, really sorry.
If and admin could, please delete this post.
And again, sorry mate.
lol it's all good you encouraged me to reformat my thread... Looking back at it I decided it was pretty sucky and confusing, Hopefully it's more straight forward now.
It's not like it's taken off or anything so it's quite understandable that people might not know of it's existence .
Hey
I tried to get my phone faster and found the [ROM][Minimal] Nothing But Speed 1.0 Thread.
I downloaded the rom that says Recommended SBF for Defy+: DEFYPLUS_U3_4.5.1-134_DFP-132 (I use it too)
Flashed it with RSD lite all went well it said now rebooting left it 5 mins nothing.
So I hit the power button wait few minutes nothing, Pull battery out for a few minutes put it back in hold the power button for like 30 secs wait few mins, no lights, no screen, no vibration, not a damn thing.
Battery was at 80% when I started and I have tried to hook up a USB wire with red and black hooked onto positive and negative as had trouble flashing last time and it said battery was low so had to do that. It wont show anything!
I should of left it as I am not sure how to fix this if you cannot even get it to start booting.
No one have any idea whats going on?
Was your previous rom a higher version than 132?
I tried to flash a 1321 rom to my defy plus which was OTA updated to 231 and it seemed to kill it. No response. Plugging in the USB cable would light the led and rsdlite would show connected. So i just flashed my 231 ROM again and it worked.
If you plug in your phone to usb and run rsdlite, see if it shows connected. If so, just flash the correct rom and it will work again.
I did try to flash the new rom 4.0.1 I think it was but got a error at boot (tried this before but used different steps this time hoping it would work) But before I was able to flash it back to 2.3.5 and it updated to 2.3.6 no problems at all.
This time it wont boot. It shows a white light if I hit the power when the USB is connected but not the charger and RSD lite did not show it was connected. Might try it a few times with different ways like connecting phone then starting it or starting it then connecting the phone see if any will read it.
Apart from that only other thing I can think of is take it back and hope they cant get it working and send me a new one. Or they will get it working and not sure what they do if its had custom roms flashed, I guess I will have to pay for the repair?
Ok got it to flash in RSD lite. I tried to flash the rom that worked last time but it still wont boot at all.
I think I may need a CM9 SBF file as I flashed the CM9 kernel and gapps or something. I did not do this last time I tried.
Would this be why I cannot flash back to the ROM that was working before?? and if so how can I get the kernel back or a ROM that will work with the one I have?
Being that the defy is virtually unbrickable, all you need to do is flash a stock 2.3.6 rom, but make sure that the CG/BL version is the same as the version you were running previously. Most probably try 132/1321 since these are the latest rootable roms. If there's a chance that you were running 231, then these roms will leave your defy dead, and you will have to flash a 231 rom. Kernel doesn't really matter, because a full stock SBF will have everything needed to bring the phone back to life.
Edit: i just realised: i hope you're not trying to flash rom zips through rsdlite. only sbfs. thought of this since you said you flashed a 4.0.1 rom which should NOT be an sbf. if you meant that you flashed the ICS rom through the clockworkmod, then ignore this whole para.
ok not sure what the version is how can I tell??
I followed the instructions on this page
forum.xda-developers.com/showthread.php?t=1432100
I think I downloaded the one that says:
NEW Latest build by Epsylon3: 16 Apr 2012
Edit:
Oh sorry I am a bit of a NOOB but where is the best place to fine SBF files for the versions I have I seen there are heaps on here but not sure what ones are right to use.
Ok I have it going again thanks. I think I must of had the 231 rom as all the rest but that didnt work.
Can I flash any rom with the 231 version??? as this is a german one not sure if that will matter but if I come into problems I might need to flash a new one.
Since you want to install ICS, doesn't really matter.
Follow the steps here to root 231: http://forum.xda-developers.com/showthread.php?t=1542956 These are full SBFs so your earlier 231 download would be wasted i guess.
Then install ICS from here: http://forum.xda-developers.com/showthread.php?t=1432100
Or some other rom if you like.
Yeah thanks, I already found that thread before had as I found out in about 30mins of installing it that it wont root.
I think I am going to keep it 2.3.6. Do you run ICS?? I tried to install it twice and got problems both times using 2 different ways and the link you posted was one of them.
What is the fastest rom?? will I be able to do the nothing but speed 1 rom now or have I upgraded to high?
I just wanted to get alot of crap off and get it a little faster but I dont want to overclock it.
I actually own an xperia play (previously used a blade), i'm helping a friend with his defy+.
Originally the plan was to root and debloat because the stock phone was painfully and surprisingly slow and laggy. In the meantime he decided to upgrade OTA to 231 (came with 1321 stock) in the hopes that the update would speed it up. Since 231 has a painful root procedure of downloading two SBFs, we then decided to go the whole hog and upgrade to ICS.
First tried Quarx's Apr 20th, but the buttons backlight stayed on. I know there's a fix for that, but then decided to try Epsylon's Apr 17th. Working fine so far. Only gripes are the lack of HWA means opera mobile etc. won't run, but making do with mini/next.
Since there is now a root method for 231, you can run any rom that uses a GB kernel. Just install 2nd init first, then boot into CWM and install a rom. Note that for the defy+, if you install the CM9 kernel, the system seems to die, so only install the CM9 rom.
99% after you switch to ICS you wouldn't wanna go back to 2.3.
I have DEFY(Green Lens).If i flash stock DEFY+ rom on DEFY, what issues will i face other than camera and battery issues. Will i be able to flash froyo sbf again and go back to froyo.
if you flash defy+rom your camera wont work. and do not use sbf.it will update the bl version and it will be difficult to go back to 2.2
Sent from my MB525 using xda premium
Battery wont be recognised and you won't be able to charge the device unless you flash a patch.
Sent not from your device!
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Don't flash Defy+ sbf on Defy. It will become a mess. You can't downgrade is not that easy so don't try.
What if that has been done? And why the phone reboots when cold?
Greetings,
I am about to start a new question before I catch this thread, so I write a reply. If the admin thinks this should be a new thread, please do appropriate operation.
This is my situation: My phone is given by others, and I don't know much about its history. Upon receiving it has been flashed a system (not original) which says (I write down from the "about phone" info menu):
System version
45.3.109.ME525+.ChinaRetail.cn.CN
Model
ME525+
Android version
2.3.6
Baseband version
EPU93_U_00.60.00
Kernel version
2.6.32.9-ga28fcc4
[email protected] #1
Internel verion number
4.5.3-109_DPP-11_WSL
So it seems to be a Defy+. But, after studied information from internet including this forum, I think it's actually a Defy:
1, On a label inside the box it says MB525;
2, The battery is 1500mAh instead of 1650mAh;
And, my camera lens looks green. Using method from http://forum.xda-developers.com/showthread.php?t=1116694 , "Detected SOC device" appeared. The ROM has been rooted when using ADB.
Though unlike the previous replies of this thread said, camera and battery is OK, The phone has a very BIG problem: it reboots when cold. When the temperature is under 15℃ or so, it will reboot. The reboot process seems raised some heat, and after temperature is down it reboots again, until the battery is drained out. If it is really cold, the phone will reboot continuously and never get into system.
I think maybe it has something to do with the modified ROM, So after studying the beginner's guide of http://forum.xda-developers.com/showthread.php?t=1216982, I flashed a stock ROM from http://sbf.droid-developers.org/umts_jordan/list.php, which, as it should be, get my phone "fake bricked " (dark screen when boots). I realized that because the phone has been flashed a defy+ ROM, with the BL=5, I cannot flash any stock ROM listed in that page. So in a haste I flashed a ME525+ ROM again from another site (claiming this is an stock ROM), which says ME525+, Android 2.3.4, 4.5.3-109_DPP-6, and the phone can boot now, but the reboot-when-cold problem persists, besides the camera is useless.
I appreciate that you read my lengthy description. So my question is:
1, Is this reboot-when-cold problem related to the ROM? or, can the problem be fixed (without sending back to moto-factory, for it's long out of the warranty)?
2, If the reboot-when-cold problem can not be fixed, Which ROM should I flash now?
luweitest said:
Greetings,
I am about to start a new question before I catch this thread, so I write a reply. If the admin thinks this should be a new thread, please do appropriate operation.
This is my situation: My phone is given by others, and I don't know much about its history. Upon receiving it has been flashed a system (not original) which says (I write down from the "about phone" info menu):
System version
45.3.109.ME525+.ChinaRetail.cn.CN
Model
ME525+
Android version
2.3.6
Baseband version
EPU93_U_00.60.00
Kernel version
2.6.32.9-ga28fcc4
[email protected] #1
Internel verion number
4.5.3-109_DPP-11_WSL
So it seems to be a Defy+. But, after studied information from internet including this forum, I think it's actually a Defy:
1, On a label inside the box it says MB525;
2, The battery is 1500mAh instead of 1650mAh;
And, my camera lens looks green. Using method from http://forum.xda-developers.com/showthread.php?t=1116694 , "Detected SOC device" appeared. The ROM has been rooted when using ADB.
Though unlike the previous replies of this thread said, camera and battery is OK, The phone has a very BIG problem: it reboots when cold. When the temperature is under 15℃ or so, it will reboot. The reboot process seems raised some heat, and after temperature is down it reboots again, until the battery is drained out. If it is really cold, the phone will reboot continuously and never get into system.
I think maybe it has something to do with the modified ROM, So after studying the beginner's guide of http://forum.xda-developers.com/showthread.php?t=1216982, I flashed a stock ROM from http://sbf.droid-developers.org/umts_jordan/list.php, which, as it should be, get my phone "fake bricked " (dark screen when boots). I realized that because the phone has been flashed a defy+ ROM, with the BL=5, I cannot flash any stock ROM listed in that page. So in a haste I flashed a ME525+ ROM again from another site (claiming this is an stock ROM), which says ME525+, Android 2.3.4, 4.5.3-109_DPP-6, and the phone can boot now, but the reboot-when-cold problem persists, besides the camera is useless.
I appreciate that you read my lengthy description. So my question is:
1, Is this reboot-when-cold problem related to the ROM? or, can the problem be fixed (without sending back to moto-factory, for it's long out of the warranty)?
2, If the reboot-when-cold problem can not be fixed, Which ROM should I flash now?
Click to expand...
Click to collapse
Try a defy SBF. If it leads to a soft brick then try a defy plus SBF. The camera can be fixed by using only 2ndboot ROMs.
Sent from my MB526 using Tapatalk
hotdog125 said:
Try a defy SBF. If it leads to a soft brick then try a defy plus SBF. The camera can be fixed by using only 2ndboot ROMs.
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
That's what I have done; it seems I have to try those Defy+ SBFs until find a one that suites for Defy.
solved
I struggled through finally. After I flashed CyanogenMod 7 stable, cm-7.2.0-jordan.zip, the phone does not reboot at low temperature again. Before that I flashed a modified BL5 JDGC_2.12.0.sbf from other sites. I can't imagine why other ROMs will cause low temperature rebooting, but anyway the phone now works in winter and I am happy! :victory:
HELP
I apologize for flooding.
Dear doctors, I need your help VERY!
The problem is this: Download Firmware "CM10 (18.11 + fixBlue). Sbf" decided to ask ..
Turned off the phone, turned on while holding the top of the rocker gromkasti through RSD sew phone, at the end of installation, the phone asks him to reboot manually, generally overloaded, nothing should be loaded, worked the battery, the identity thing, then threw this thing, after a while the phone stopped included at connection to a computer white LED lights up, and the sound came from the connection on the PC .. decided to postpone until the phone as he waited for the new display and touch screen, just 3 days before receiving parts, decided to try to flash .. diode zagoraetsya only when connected to fraction of a second, and gave sound on the PC. Now the identity thing, not only delivers sound on the PC .. and not simply vklyuchaetsya (bought a frog, thought battery low, etc., loaded it as it is .. and no results ..
Doctors ask for your help regarding my vostonavleniya Defayki ..
ps Tried different Mutko with USB, battery and buttons, nothing pomaglo (RSD does not see (sorry for the google translate
Hi guys, you are my last hope!
Bought my Defy early 2011 and regularily updated with custom ROMs, so you could say I know a thing about rooting, RSD Lite, fixed sbfs, ...
Or at least I though I knew, but I still managed to kill my phone I think.
Here's what happend:
I tried to install Epsylon3s nightly from may 8th (http://defy.wdscript.fr/defy-cm9/). Before that, I was on CM 7.1
After installing the zip and rebooting, I saw the bootlogo, then i was asked for my pin code. As soon as i entered it, again to the bootlogo, again the pin, and so on.
So i realized something was wrong.
Could not get into recovery, so I flashed
JORDN_U3_97.21.51.sbf
as this often helped me in the past.
I then tried this one:
http://forum.xda-developers.com/showthread.php?t=1498843
Also didn't start.
So back to
JORDN_U3_97.21.51.sbf
But here it might be, that I misclicked (I have quite some SBFs in that folder, cause I wanted to be prepared in case something went wrong), as after that, I never got my Defy to work again.
I was stuck at the Motorola M logo.
Coudln't get into recovery, so no zips for me anymore, only flashing of sfb.
That's basically when I entered panic mode. As I didn't know what I just flashed, I could only guess the problem. So I tried the Ginger2Froyo (http://forum.xda-developers.com/showthread.php?t=1486731) in case I went to BL6. Also tried http://forum.xda-developers.com/showthread.php?t=1552152
But in this process, my RSD Lite started to behave strange:
when flashing, it's building the image, uploads it, checks checksum. But once it says "rebooting" it immediately jumps to 100% and pass. Phone how ever stays black and white LED.
Of course I can still flash other SBFs, and I tried various (JRDNEM_U3_3.4.3-36-1.7. sbf for example). But I either get the instant PASS, which tells me something didn't work, or sometimes I get the neverending bootlogo and RSD telling me to start the phone manually.
So... that's my story.
I can't seem to find a single SBF that would work for me. I screwed up big time.
To make this clear: at this point I don't care about downgradeability or anything thelike. Whatever makes my Defy work again, is fine. Froyo, Ginger, ICS, or whatever.
So if anybody still has any advice for me, I'll love you forever! Promise!
Thanks a lot in advance for any help you sure will offer,
Clock
Try this if you haven't :
Go into stock recovery and make a factory reset
Sent from my MB526 using XDA App
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Have u tried this thread:
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade
Clock1999 said:
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Click to expand...
Click to collapse
Im sorry , thought you mean custom recovery when you say you can't enter recovery.
I was in the nearly same situation but i never changed my bootloader...., by me out works to power up my phone with pressed volume button down to enter stock recovery ...
So I'm sorry i couldn't help you
Sent from my MB526 using XDA App
You just like to play with your defy, don't ya
Have you tried the suggestions under Common problems/questions in this guide?
Thanks for all the responses.
However all the guides seem to point to two options only:
1) Flash this one Eclair (which I already mentioned that I did, that it used to work, but since the "instant 100% on rebooting" doesn't anymore.
2) Factory Reset/Wipe. Which I cannot, as I don't get into Recovery Mode. All I can do atm, is flash SBFs. Defy won't enter Recovery Mode (which I guess is a pretty bad sign)
But the way I always understood it, was that you only need to be careful what you install, so you don't lose downgradeability. And that, once lost, you wouldn't be able to flash "older" roms, but newer ones would always be possible.
So shouldn't there always be a rom, that saves me?
What about Defy+ roms? Any advice on that? Which best to try first? So far, I haven't touched Defy+ roms at all.
Thanks for the support!
Did you try this:
When Off, press Vol. down and power.
You'll get an exclamation mark inside a triangle.
Press both Vol. up and down at the same time.
Now you suppose to be in stock recovery and you can do factory reset.
Do the above after flashing stock SBF.
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Clock1999 said:
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
Click to expand...
Click to collapse
If you flash any of the defy+ roms, camera won't work..there isn't a fix or patch for that..
Doesn't matter from where I send it, what matters is written above
corrinti said:
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Click to expand...
Click to collapse
Hi,
as I mentioned above, I already tried this ROM but it gives me the same result as all the others: stuck at bootlogo.
Maybe there is a special trick on which ROM I should flash before flashing this one?
Sorry, I do not know how to help. Just no idea now, try to dig the forum.
Once I had very similar problem - whatever I flashed I was stuck at bootlogo. And in my case I found out that just before flash my internal memory had been filled with some mess, which was not removed by any wipes (cache, dalvik cache, cache partition) and after any flash memory was too filled to start the system.
But finally I could flash Chinese eclair (CG5), which at last started horribly laggy, and I could wipe private data from a system - it gave me more than 1GB of internal memory back (from 40MB after all wipes and clean system install) and a way to flash whatever I wanted without a problem.
So even if it is also your problem, my way is not available to you now. Maybe you can find as small sbf file as possible and try then.
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Clock1999 said:
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Click to expand...
Click to collapse
I could use CG5 full sbf which will not boot for you as you put BL6 and maybe BL7.
To boot from flashed sbf it cannot be lower BL version.
I suppose that now you have a memory problem - flashing sbf do not wipe the memory.
At first I would try getting into stock recovery (even several times, just pull battery out, wait a minute, power, vol -, battery in) - if successful then do a factory reset and reboot.
If not I would try to find out a smallest sbf with proper BL version - just to give it more chance to boot with small memory available, if not then again try to get into stock recovery.
I'm the happiest guy around, as I finally revitalized my Defy.
For all you guys, who already tried everything: here's what worked for me.
Just let it rest a few days.
After I hadn't touched my phone for a couple of days, I thought about giving it one last try. So I flashed the Defy+ SBF (4th in this list: http://sbf.droid-developers.org/umts_jordanplus/list.php), like I've done multiple times before.
But this time, when rebooting, I wasn't stuck at the M-logo, but in a bootloop. And that gave me the smiles as I knew, that now I should be able to enter Stock Recovery again. From there on, it was no problem to get to a stable base again. After flashing the BL6 Froyo, I'm now on CM9 and everything is fine.
Thanks for all you help.
Sometimes, you just have to give it a rest...
Clock
It is a next such case I see in moto forums ;-) but it is really hard to give a tip: leave it for few days and check again
Use the sbf_flash for Linux
Sent from my MB526 using Tapatalk 2