Database Users

[Q] defy+ stuck on boot logo

Hi, i have defy+ (mb526)
android version: 2.3.7
kernell: 2.6.32.9-gb08c3c8
cyanogenMod-7.1..0-jordan
Gingerbread GWK74
I want to flash CM 7.2 (http://forum.xda-developers.com/showthread.php?t=1445259) but after flash rom, I stuck on boot logo, i wait 30minut, reboot, wait, reboot... but without succes.

You must delete the user data of your previous rom first. Go to CWM Recovery and choose 'wipe data/factory reset'. This will remove all your user data (apps, app data, settings etc.) so you should have a backup if you want to keep the data!

i try this, but without succes. I'am still on boot logo (google) :-(

Dobre den,
There is something wrong in your phone setting : the kernel you mention in your first post (2.6.32.9-gb08c3c8) is a Froyo kernel and your phone (MB526) has a GB bootloader who only accept GB kernel...
So I think the best for you is to flash a full GB SBF via RSDLite before flashing the CM 7.2 Defy+.
Nashle...;-)

This has happened to me... A LOT. the way i fixed it was to redownload CM7 from the pc, because something went wrong the first time.

mankymoo said:
This has happened to me... A LOT. the way i fixed it was to redownload CM7 from the pc, because something went wrong the first time.
Click to expand...
Click to collapse
Your phone is a Defy or a Defy+ ? because I'm not sure you help a lot with this kind of answers.

Thanx, after flash ful SBF GB via RSDlite, everything is OK

I have q defy, however the filestructure is almost exactly the same and a fresh install of anything is the key (usually) to fix any problem... therefore I tend to ask them to do that before anything else
Sent from my MB525 using XDA App

stuck on bootlogo
i have defy+ (stock 2.3.6 - 4.5.1-134_DFP-1321)
rooted & flashed Quarx's 3 Mach ICS CM9 nightly..
i tried to update that but i guess i flashed some wrong zip in recovery & phone showed some bootloader error..
so i flashed full sbf via RSDlite to return to my stock rom..after flashing is complete, rsdlite reboots my phone, phone is stuck on motorola bootlogo & rsdlite shows "please manually powerup this phone"..still connected to usb..even when i disconnect phone from usb, phone keeps rebooting & stuck on bootlogo..

update
clearing data/cache in stock recovery solved the problem..back on CM9

Bootloop, SBF issue >please help

I accidentaly installed the CM9 kernel when i should have installed the CM7 one with ICS. Then i made a nandroid restore of my previous CM7. Than... phone dead. Starting but no CWM no ROM booting.
As i have had CM7 with GB kernel( i think) i flashed ( not knowing) an old SBF than didn't booted. I tried the JORDN_U3_97.21.51 T-Mobile It boots, i can root it, install CWM.
But than when i try to install a CM7 nightly ( installed ok) it dies again. Starts but No CWM no Rom booting.
What to do? I don't know what SBF to flash or what method to install?
Problem update I red that the above SBF has a CG Version 3: SBF 2.51 (Éclair) (Defy) so i installed several CG Version 4: SBF 3.4.2 (Froyo) (Defy).
They don't work. RSD says PASS but phone is dead .No stock recovery no boot. Only way to get it back to life is if i flash the eclair again.
I red that if i get a back screen when booting i have installed a lower CG version. As i tested with version 4, version 5 GB is the only option. I didn't try it out because there are some issues. Froyo would have been much more easier.

i think many readers of your post are getting problems with understanding your problem ...
you got a stock defy, rooted it, installed 2ndinit via apk, booted into recovery (vol- at blue led) and installed CM7 zip ??? correct ???
after succesfull install of CM7 your phone doesn't turn on? Black screen?
black screen after zip is (i think) impossible ... but i can fail ...
i would like to help you, but first you have to give the detailed steps you did and what you wanted to do ...

To make it simplier
I installed the JORDN_U3_97.21.51 T-Mobile (which is 2.1 update1) It boots, i can root it, install 2nd-init > CWM. Set Normal boot.
Than in CWM nothing works.
Installing a CM7 nightly, or restoring a CWM backup.
I install a CM7 nightly like this> In CWM> Custom Recovery> Wipe data, wipe cache> install Cm7 zip, install Gaaps zip. After this, phone restarts, screen is on, logo appears and i wait and wait. Nothing happens.
Do i have to install a special CM7 build?
The CWM backup does not restore. It says that files are missing ( like android.secure..) I am not interested in keeping downgrade ability. i would like to try another SBF. I am not 100% sure what SBF to use from the wiki page.
I red that the SBF i installed has some special "problems" here> http://forum.xda-developers.com/showthread.php?t=905371. They are talking of a CWM revoery app by tenfair here> http://forum.xda-developers.com/showthread.php?t=875233
Maybe that works^. Will try it after the phone is fully charged.

so, ok ... thats detailed as i wish
ok, the problem is clear i think ... first of all eclair is not a nice system for a defy ... upgrade to froyo or even gingerbread ... (keep in mind, that GB has problems with green lens camera) ...
than you can root it with SuperOneClick e.g. ... if this is running correctly, you can install 2ndinit via apk ... then boot, vol- while blue led (i know, you know how ) ... in that clockworkmod recovery you can wipe the devices data and cache partition (even wipe dalvik cache in advanced menu) ... then install CM7.2-nightly-.... .zip ... you may have to flash an fixed sbf with the nessesary kernel for CM7 at this point to boot ...
if this is working fine, you can install the gapps.zip via recovery ...
also try to set boot to 2ndinit in boot-menu ... i don't think it's "normal" boot for CM7 ... but i can't try at the moment cause of my bricked defy ...

Thanks for the reply.
The problem is that i can't install other Froyo SBF's. Will try Gingerbread SBF. The last froyo didn't boot, will try a new one. Weird, i know. Maybe someone can tell me which CM7 to flash? An older one with Kernel ? I didn't think the install would be so tricky.

Froyo Full-SBF doesn't boot on your defy?
be aware of flashing Gingerbread then ... if GB doesn't boot, you will have a problem downgrading to froyo / eclair ...
it sonds crazy, that froyo isn't booting on your device ... have you done a full wipe after froyo sbf? it's important ...

I'm on the Eclair SBF right now. What should i do? Go into recovery and do a wipe or install a new Froyo SBF? It's about the CG value maybe. I understand the mechanism but don't know how to check the CG value. If i search for my current eclair SBF i get all sorts of weird stuff. Nevertheless i will try and try until i succeed. It took me a while to figure out the Rooting method. Superoneclick does not work. It's a special method for the 2.51.
The thing is that i wanted to go the my Nordic SBF( the one Quarx used during the first days of CM7) and it didn't booted. That's why i tried this one. Funny ho flashing the wrong kernel(CM9 instead of CM7) can brake things like this. What i don't understand is how my CWM backup didn't restore. It restored well, finished, then phone dead. No CWM.
edit: i just red: 2.51 is Not downgradable. But no downgrade to what??? Will try to some Froyo SBF's, see if works. But that does not solve my CM7 issues.

Tried a few Froyo SBF's. Wiped data/cache in Stock Recovery. RSD says PASS than phone does not boot. Only the 21.51 eclair works all the time.....Where next?
Update 2 got it to work with this>
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=cg

OMG i dn't understand what was going on with your defy, but i'm happy to know your on the road again
the only sbf that are running are the stock eclair you have (21.51) and the modded BL6 with Froyo Kernel ???

Glad it worked.
DJ_Synergy said:
OMG i dn't understand what was going on with your defy, but i'm happy to know your on the road again
the only sbf that are running are the stock eclair you have (21.51) and the modded BL6 with Froyo Kernel ???
Click to expand...
Click to collapse
Yes but now i am running CM9 flawlessly. So happy. The only thing that bothers me is the Chinese Boot screen )). But that can be changed. It's great that one SBF works, moded or not. I tried like 6,7 other Stock sbf's before. So a message to whom tries to install SBF's: Stay away from JORDN_U3_97.21.51 SBF. Even the Rooting method is awful (until you find it) .

HI Deonix, I have the similar problem. However I am unable to use RSDlite as it gives a failure messg when u click start. I tried JRDNEM_U3_3.4.3-36-1.7.sbf and JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B50AA028.0R_USAJORDANRTINT15_P003_A020_HWp3_Service1FF.sbf.
Both failed, I will try using the rsdlite after the cache and factory rest this time based on your suggestions. Can you tell, if your adb command was listing your device, as mine is not.
my CWM is also gone I get some old android recovery system 3e instead which fails after signature check.

Hi,
I think I know what is your problem.
I also installed the firmware JORDN_U3_97.21.51 and now I can only install any Custom ROM after installing the firmware fix for JORDN_U3_97.21.51.
I did upload it for you: http://www.4shared.com/rar/o02VEk_v/firmware.html?refurl=d1url
It is the following:
Install JORDN_U3_97.21.51;
Rootear;
Install the Recovery;
Install the fix;
enter the recovery and install any rom you want, remembering to delete the caches (data and Dalvik cache)
ps: have 100% of the battery before installing the SBF.
any problems let me know.

Sometimes you could get stuck in a bootloop and all you need to do is pull battery and reboot
Sent from my MB525 using xda premium

Same Problem, Please help!
Deonix said:
Yes but now i am running CM9 flawlessly. So happy. The only thing that bothers me is the Chinese Boot screen )). But that can be changed. It's great that one SBF works, moded or not. I tried like 6,7 other Stock sbf's before. So a message to whom tries to install SBF's: Stay away from JORDN_U3_97.21.51 SBF. Even the Rooting method is awful (until you find it) .
Click to expand...
Click to collapse
Hey bro.
Even i have got the Defy working, but its not detecting the device when connected to the computer, i have done all the basic troubleshooting, is it working for you??
is it bcoz this room is for ME525??

[Q] screen is blank defy plus

GUYS i am stuck in a Big problem.......
i actually wanted to change my ROM from Quarx Nightly Builds(jb) to WIUI (jb) according to the instructions in http://forum.xda-developers.com/showthread.php?t=1161110 i installed 2ndinit 1.4.2 and went to bootmenu and kept the default to 2ndint and after that when i went to recovery 2 options were their 1)stock recovery and 2) (forgot name) recovery so i went to stock memoery to wipe cache /data but i found nothing so i rebooted but from here trouble started it stuck at motorola ICON and dont start i asked 1 of my group mate about this he told me to flash my phone with SBF file so i flashed it sum SBF file later found that its SBF file of DEFY not DEFY + and now the phone does'nt even start only blank screen no "DISPLAY IS SEEN" pls any help i will be thank full to them

rahul uzumaki said:
GUYS i am stuck in a Big problem.......
i actually wanted to change my ROM from Quarx Nightly Builds(jb) to WIUI (jb) according to the instructions in http://forum.xda-developers.com/showthread.php?t=1161110 i installed 2ndinit 1.4.2 and went to bootmenu and kept the default to 2ndint and after that when i went to recovery 2 options were their 1)stock recovery and 2) (forgot name) recovery so i went to stock memoery to wipe cache /data but i found nothing so i rebooted but from here trouble started it stuck at motorola ICON and dont start i asked 1 of my group mate about this he told me to flash my phone with SBF file so i flashed it sum SBF file later found that its SBF file of DEFY not DEFY + and now the phone does'nt even start only blank screen no "DISPLAY IS SEEN" pls any help i will be thank full to them
Click to expand...
Click to collapse
Can you enter to the bootloader, if you can, try flashing another SBF.

LeonardoJegigzem said:
Can you enter to the bootloader, if you can, try flashing another SBF.
Click to expand...
Click to collapse
yeap actually the phone was not at all starting so one of my fb friend told me too on the phone pressing the power button -vol and putting the battery at the same tym and vola bootloder is on and then i flashed it with standard SBF file anyway thanks a TON :good:

[Q] Can't load after downgrade to 7.2 Jordan

Hi all
I use to run cm-7.2 Jordan without any issues. Decided however to upgrade and test cm10 but since I didn't find it stable enough I decided to downgrade back to 7.2. The flash succeed without issues but when I reboot I get stuck with the Google logo and the os never boot up.
I tried to go through cm.7.1 but no luck there, same issue.
Any clue how i can resolve this?

llavsor said:
Hi all
I use to run cm-7.2 Jordan without any issues. Decided however to upgrade and test cm10 but since I didn't find it stable enough I decided to downgrade back to 7.2. The flash succeed without issues but when I reboot I get stuck with the Google logo and the os never boot up.
I tried to go through cm.7.1 but no luck there, same issue.
Any clue how i can resolve this?
Click to expand...
Click to collapse
Try to wipe all from stock recovery ----> Power+Vol dwn

Kayant said:
Try to wipe all from stock recovery ----> Power+Vol dwn
Click to expand...
Click to collapse
Thanks for quick reply. I tried that and the phone loaded a android character with a triangle and a exclamation mark. I don't have a good feeling about that

llavsor said:
Thanks for quick reply. I tried that and the phone loaded a android character with a triangle and a exclamation mark. I don't have a good feeling about that
Click to expand...
Click to collapse
That's good sorry forget to say you need to hold VOL dwn& Vol Up at the same time then wipe all...
Good luck

Exactly the same problem here, cannot downgrade to CM7.
Any good news?

Flash official froyo (I used ver 2.2.2)sbf via rsdlite. Root it using superoneclick and install 2init bootmenu 2.0. In custom recovery do full factory wipe follow with restore your nandroid 7.2 if you have them. If it booting hang at start screen, flash any froyo fixed sbf that contain the froyo kernel(optional). This way all your previous user data will still be intact.
Sent from my awesome rooted Defy: 2.3.6 XDA premium

So the recovery won't work and will have to start with SBF. Will wait until I have the computer environment to do so.
Thanks!

Kayant said:
Try to wipe all from stock recovery ----> Power+Vol dwn
Click to expand...
Click to collapse
farsight73 said:
Flash official froyo (I used ver 2.2.2)sbf via rsdlite. Root it using superoneclick and install 2init bootmenu 2.0. In custom recovery do full factory wipe follow with restore your nandroid 7.2 if you have them. If it booting hang at start screen, flash any froyo fixed sbf that contain the froyo kernel(optional). This way all your previous user data will still be intact.
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone

llavsor said:
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
Click to expand...
Click to collapse
Wipe all from stock recovery that's you needed to do btw before installing cm7.... Sbf is not needed.
Go to stock recovery and wipe all your ROM should boot...
Let's Go ^_^

llavsor said:
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
Click to expand...
Click to collapse
Factory reset from stock bootmenu again. If it still hangs, flash sbf again with another factory reset afterwards just to be safe. BTW, I've had times where 3+ sbf flashes with factory resets were needed to get the phone to boot again.
One problem you might be having is if you formatted /data and /cache to ext4. Maybe it was just me, but I had to reinstall CM10, change back to ext3, flash sbf, then install CM7. Changing to ext3 and flashing CM7 didn't work -- same problem you're having. I wasn't sure if ext4 was the problem so I made sure I changed back to ext3 before sbf flashing. I'm not sure if the sbf reformats the partitions or just wipes them like a factory reset. If you've already flashed the sbf, then you can't install a CM10 rom to change back to ext3... Worse come to worse, you maybe able to install one of the custom sbf's with CM10 custom kernel preinstalled, change to ext3, flash official sbf, factory reset, then install CM7. I haven't looked into them because I make my own custom sbf's .
Bravo users are having this exact problem and my solution is to ensure that /data and /cache are ext3, flash the sbf and start from scratch -- the only guaranteed way I know of to fix this problem. Another Bravo user had the same problem and managed to fix it by changing some /data permissions over adb -- the user didn't specify the exact things done so I'm waiting on a reply with more details.

skeevy420 said:
Factory reset from stock bootmenu again. If it still hangs, flash sbf again with another factory reset afterwards just to be safe. BTW, I've had times where 3+ sbf flashes with factory resets were needed to get the phone to boot again.
One problem you might be having is if you formatted /data and /cache to ext4. Maybe it was just me, but I had to reinstall CM10, change back to ext3, flash sbf, then install CM7. Changing to ext3 and flashing CM7 didn't work -- same problem you're having. I wasn't sure if ext4 was the problem so I made sure I changed back to ext3 before sbf flashing. I'm not sure if the sbf reformats the partitions or just wipes them like a factory reset. If you've already flashed the sbf, then you can't install a CM10 rom to change back to ext3... Worse come to worse, you maybe able to install one of the custom sbf's with CM10 custom kernel preinstalled, change to ext3, flash official sbf, factory reset, then install CM7. I haven't looked into them because I make my own custom sbf's .
Bravo users are having this exact problem and my solution is to ensure that /data and /cache are ext3, flash the sbf and start from scratch -- the only guaranteed way I know of to fix this problem. Another Bravo user had the same problem and managed to fix it by changing some /data permissions over adb -- the user didn't specify the exact things done so I'm waiting on a reply with more details.
Click to expand...
Click to collapse
Okey good advice.
Here is where I am at now. I have flashed a number of different SFBs and I end up with the same situation every time. RSDLIte finish the process nicely but the phone get stuck with the flashing M. When I reboot manually I get passed the M and to the Android text/logo and there I get stuck.
I get advice to do a factory reset but how do I do that. The CW bootloader is gone and I can't get to the original boot loader either. I hit volume down and power, get to the triangle screen where I am supposed to hit the right bottom corner but nothing happens.
So I cant boot the phone to get into a menu where I can change to ext3 if this is a problem.
Please help, how can I get further?

Since I have no luck restoring stock rom I now have the following plan.
Install ClockWorkMod recovery with ADB.
Using recovery to do a factory reset and clear cache.
Flash a CM10 ROM (or any rom that will successfully boot up my phone).
From that start over to downgrade to CM9 to find a stable ROM.
The question I have now is if I will be able to use ADB with the USB connection mode I get from the bootloader (volume up+pwr button)? Or does ADB actually require that I can boot my phone and go into some other USB mode such as UMS or MTP.
Second question. Playing with restoring stock ROM i run out of battery and now my defy wont charge (only see a big question mark when loading). Seems like I get no power when USB is connected so is there a way for me to charge the battery or do I need to find another happy camper in town with a working defy that can power up my battery?

llavsor said:
Okey good advice.
Here is where I am at now. I have flashed a number of different SFBs and I end up with the same situation every time. RSDLIte finish the process nicely but the phone get stuck with the flashing M. When I reboot manually I get passed the M and to the Android text/logo and there I get stuck.
I get advice to do a factory reset but how do I do that. The CW bootloader is gone and I can't get to the original boot loader either. I hit volume down and power, get to the triangle screen where I am supposed to hit the right bottom corner but nothing happens.
So I cant boot the phone to get into a menu where I can change to ext3 if this is a problem.
Please help, how can I get further?
Click to expand...
Click to collapse
In froyo, you should hit vol up/down together to enter stock recovery.
If you have your cm7 nandroid or your gingerbread nandroid 2.3.6. In,custom recovery cm10, restore them. Your phone would not boot but you have your cm7 or gingerbread cwm by then, that you could format cache and total wipe back to ext.3 in the recovery menu, format/wipe follow with another nandroid restore and flash fix sbf from rsdlite.
But then the best way is go back totally clean by flashing stock froyo and root, install 2init with bootmenu 2.0. Then total wipe in recovery follow with restore your cm7 or gingerbread nandroids and flash the corresponding fix sbf via rsdlite.
Charging dead rom defy would need the MacGyver trick then. But some say if you leave it connected overnight in pc usb would charged it somehow but slow..
On 2nd thought.. you need to tell us yoyr defy model...green lense, red lense or the defy plus?? These models has their own characteristics in term of play around in cwm and way of flashing..
Sent from my awesome rooted Defy: 2.3.6 XDA premium

farsight73 said:
In froyo, you should hit vol up/down together to enter stock recovery.
If you have your cm7 nandroid or your gingerbread nandroid 2.3.6. In,custom recovery cm10, restore them. Your phone would not boot but you have your cm7 or gingerbread cwm by then, that you could format cache and total wipe back to ext.3 in the recovery menu, format/wipe follow with another nandroid restore and flash fix sbf from rsdlite.
But then the best way is go back totally clean by flashing stock froyo and root, install 2init with bootmenu 2.0. Then total wipe in recovery follow with restore your cm7 or gingerbread nandroids and flash the corresponding fix sbf via rsdlite.
Charging dead rom defy would need the MacGyver trick then. But some say if you leave it connected overnight in pc usb would charged it somehow but slow..
On 2nd thought.. you need to tell us yoyr defy model...green lense, red lense or the defy plus?? These models has their own characteristics in term of play around in cwm and way of flashing..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
Thanks for very informative reply. I have a Defy 525 with red lens.

It's working.
I found a friend blessed with a defy and used that to charge the battery, tried to charge it over night with USB but it didn't work.
I then followed the steps from the last post and managed to flash a stock rom and then from there I rooted the phone with SuperOneClick, installed 2ndInit with ADB (guess you could use an apk installer from the phone as well ). I booted into recovery and flashed 7.2.0 Jordan from CM and now I am where I started a few weeks back.
Thank you all for your help.

That was the low battery problem.......
Since i had this i allways look for a full battery
If you think your defy is dead , a look for a empty battery won't be mad
Could anybody took a reminder info into beginners guide
MB525 red lense

TWRP Recovery has killed my defy

Hello guys, unfortunately my defy + with CM 10.1 does not work since I installed TWRP Recovery 2.6.3.0, I also lost the ClockworkMod recovery, and so I can not restore my copy CM 10.1, the phone is not charging (it is now only 25 %) ask for help.

If your phone don't boot
Charge battery with external charger
Flash .sbf firmware
Wipe data in stock recovery....
Reboot
Root
Install recovery
Restore nandroid
Be happy again
If it's boot
Copy system/bootmenu folder from
extracted nightly .zip file (last you've uesed and paste it on the rigth place using adb or rootexplorer
Sent from my MB525 red , froyo 2.2.2 german blurless service.sbf, as stock rom

thanks Bone for the answer, what is the right place to copy system / bootmenu?
I could try with the TWRP Recovery file manager

If you're have working twrp you can flash cwm recovery.zip or flash rom which contains cwm recovery
Sent from my MB525 red , froyo 2.2.2 german blurless service.sbf, as stock rom

thanks bone, I flashed CM 11 with TWRP recovery and everything went well, I'll try this rom and then after I will do a restore of the CM10

you can not completely kill our defy as our bootloader is locked...

iAjayIND said:
you can not completely kill our defy as our bootloader is locked...
Click to expand...
Click to collapse
It is hard to kill but it's possible....
Throw in from 10m to asphalt ground,,
Over roll it with an airplain
Pull usb cable during sbf flash in the moment when rsd flashes the bootloader partition
Cheers
Sent from my MB525 red , froyo 2.2.2 german blurless service.sbf, as stock rom

mb 525 not powering after flashing.. i am only getting white light while connecting usb cable..please help any solution