Hi guys
Before I explain I'd like to say that yes, I have read other threads on similar topics, although none seem to have the same symptoms as me...
This week I bought a software-bricked Defy on eBay with the hopes of fixing it and giving it to a friend. I first tried flashing an old Eclair SBF to no avail (only switched on to bootloader) and thought that it could be failing due to it being on a newer firmware. So then I tried Froyo, and when that didn't work either (bootloops like when I received the phone) I thought my last resort was a CG 5 SBF, so I went for the JORDN_U3_97.21.51 build. This seems to get further into the booting process, with the MotoBLUR animation appearing but I get a BP Panic - 0x00080010 above the animation before the phone switches off. Thinking I had nothing to lose I tried a Gingerbread ROM, but that just bootlooped too so I went back to 97.21.51. I realise I've probably painted myself into a corner by flashing these
I'm all out of ideas with how to get the phone any further and have searched for the BP panic to no avail. I can get into stock recovery and bootloader, although the recovery seems to have issues with accessing the cache sometimes.
Thanks for reading
The same panic have y for the last 2 weeks, after flashing hangs in bootloader (red logo and no animation), after other flash hangs on a animated red logo and thats where you must give it time 3 or 4 min. wating, when its dont works you can try to pul out battery and do it in again while you hold the start and vol. down button, then in recovery menu wipe Dalvik cache and wipe cahe. Maby it works then, when not you can try like me to go again tho recovery and there restore stockrom, thats the way ym getting my defy work again. There are many ways to get it back to work again and it cost me 2 weeks after flashing maby 15 diverend roms to get it works and even than when it works, 2 days work whit rooting it and get 3G alive. So when you think its dead, maby RSDlite can bring it back to live, just like here.
Now my Defy MB525 working like a Defy 526 on Gingerbread.
So don't give up, when you can see whit RSDlite the phoon, it must be possible to get it work, only problem here was on a moment when the battery was empty, but here on XDA you can find the megayver method (charging on a ohter cell like a duo) or what y have don, get my old nokia loader (5V) and whit 2 wires hangs on the battery power it up to 4.1 V, succes.
Thanks, although I was just getting repeated boot loops rather than it hanging on the logo... And that wasn't animated either. How did you manage to restore the stock ROM through the recovery? Did you have a flashable zip? Please bear in mind that I did not get a custom recovery installed
I'll look out for the low battery problem. Thanks for your advice
ben_duder said:
Thanks, although I was just getting repeated boot loops rather than it hanging on the logo... And that wasn't animated either. How did you manage to restore the stock ROM through the recovery? Did you have a flashable zip? Please bear in mind that I did not get a custom recovery installed
I'll look out for the low battery problem. Thanks for your advice
Click to expand...
Click to collapse
U should have wiped cache and data after flashing Froyo!!!!!!
It would have booted!!!!
Now u flashed GB!! Ur stuck there!!!
Flash gb again and Go to stock recovery and wipe data!!!! If know how to do it!!!
Sent from my MB526 using xda premium
nogoodusername said:
U should have wiped cache and data after flashing Froyo!!!!!!
It would have booted!!!!
Now u flashed GB!! Ur stuck there!!!
Flash gb again and Go to stock recovery and wipe data!!!! If know how to do it!!!
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks, although I'm pretty sure I did wipe cache and data... and I definitely did (several times ) after flashing Gingerbread. I feel like whatever is preventing Froyo and Gingerbread from booting is the same thing as what is giving me the BP panic on the CG 5 Eclair ROM.
I would suspect a hardware issue here.w
Sent from my MB525 using Tapatalk
I think it might be too It's a shame because I can enter recovery and bootloader okay, and the seller said it broke during a failed software update so I thought it would be a simple matter of reflashing an SBF.
what is bp panic?
what happens when it is booting?
Sent from my MB525 using xda premium
When I try to boot the CG 5 Eclair I get past the static Motorola logo (hence further than any other build) but the MotoBLUR animation is stuttery, with a BP panic at the top (see picture). This goes on for quite a while, then the phone switches off and this loops.
Ok if occurred during a software update, find out which he was installing and try that one. May also be worth trying motoupdate.
Sent from my MB525 using Tapatalk
I might try that, but won't it be useless now that I've flashed CG 5? I'll look into MotoUpdate
Is the general consensus that this is an unfixable hardware issue, then?
Apolgoies if you've already tried this, but I had a Defy which would do the same, either stuck on M logo or error in bootloader.
Each time I just plugged it into PC / USB at bootloader screen, and used RSD Lite to try another ROM. Eventually I found one which worked. I think I tried 5 before finding one which didn't cause any problems.
My defy was a ME525+ and the ROM which finally worked was "DEFYPLUS_U3_4.5.1-134_DFP-132_BLUR"
So, if you haven't already, I'd just suggest try a few more ROMS, flashed from Bootloader / RSD Lite.
Hope it helps somehow
I have a defy with a red lens that was running cyanogenmod 7.1. I hadn't used it in a while and when I started it up it was having multiple issues that reflashing didn't fix. I followed some bad advise from another site and tried to flash back to TMO official froyo rom. obviously that screwed up my phone and now I am stuck in a boot loop. What I need to know is what rom i can safely flash to and then be able to reroot and flash back to cyanogen or another custom rom. I have tried reading on the forums,but they don't seem to make sense for what I need to do. If you could at least point me in the right direction I would greatly appreciate it. thanks.
Your solution lies here
Thank . I so much thought the error was from trying to downgrade.
Sent from my SGH-T959V using XDA
i am noob and dont know what happened to my defy as i rooted and put CM7 on it and have been using it for last 6 months but today when i restarted my defy it got stuck at google logo.. and when i try to go into custom recovery it only shows official recovery.. dont know what to do.. Pl help as little help would be really appreciated..
Edit: Never Mind got it.. Used RSD lite to restore it..
Hi Everyone,
I successfully rooted my Motorola Defy+ (MB526), and furthermore I was able to install CM10.1 onto the phone. However once the phone booted up I had a number of processes fail. Of great concern the com.google... process failed, and essentially made the phone unusable. Since receiving these error messages I made the decision to perform a factory reset / wipe.
I have since tried to install both CM7 and CM9, however whenever the phone boots just after the Motorola / Cyanogen boot screens I see the following error message -
https://www.dropbox.com/s/4jwu9pta32dpyqf/Defy-Encryption-Message.jpg
Any advice on how to fix this issue will be greatly appreciated.
Kind Regards,
Davo
You downgraded without converting to ext3. Search for aroma full wiper n use it.
Sent from my MB526 using xda app-developers app
install froyo kernel, format to ext3, wipe, and if it doesnt give errors you are good, and you can install cm7 and 9
https://www.dropbox.com/s/dfinvahg1pvr4hm/kernel-froyo-222-179-4-signed.zip
Hi Guys,
Thanks for your suggestions; ultimately I decided to flash a new SBF file using RDS Lite. However after following the instructions at this link -
Root Defy+ bl7 2.3.6 Tested !! DFP-188, DFP-231, DF | Roms | Baseband fix[kdarknight]
- I am now unable to get past the Motorola "Big Red M" symbol. Basically the phone won't boot up fully, therefore I cannot apply any Kernel or ROM fixes, mostly because I have lost CWM and any way of installing it.
I am hopeful of locating an appropriate SBF file that will allow my phone to boot again.
Kind Regards,
David
Hi everyone!
I am having very strange problem with stock rom "JORDN _U3_6.36.0" from T-Mobile USA on standard Defy. Each time i power phone up, it starts booting up then restarts itself in to stock recovery and perform hard/factory reset. After that it boots normally, but all settings gone.
I am not using T-mobile sim or moto blur account , so i skip registration using "ebluroff" trick. Is that can be the cause of the problem?
Some backstory: when i bought the phone it had CyanogenMod 7 installed on it. I used it for 2-3 years,even updated it several times up to 7.2.
Then some time ago i started having issues with it, so i had to flash stock rom with 2.1 Android.
I decided not to do anything with the phone, until i got some advice, so i any help would be greatly appreciated.
What were the issues faced? Anyhow one of the things you can try is to upgrade to 2.2, via rsd lite
Sent from my Nexus 5 using Tapatalk
thekguy said:
What were the issues faced? Anyhow one of the things you can try is to upgrade to 2.2, via rsd lite
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Well, thing is i want to keep my downgrade ability. I rooted the phone with superoneclick and install 2ndInit 1.4.2, but the problem is that it doesn't see SD card because it is Eclair. How people installed nandroid backups on 2.1? There has to be the way to move to 2.2 without flashing full SBF, because as i already mentioned it had CyanogenMod 7 when i bought it, so it is possible.
DEN383 said:
Well, thing is i want to keep my downgrade ability. I rooted the phone with superoneclick and install 2ndInit 1.4.2, but the problem is that it doesn't see SD card because it is Eclair. How people installed nandroid backups on 2.1? There has to be the way to move to 2.2 without flashing full SBF, because as i already mentioned it had CyanogenMod 7 when i bought it, so it is possible.
Click to expand...
Click to collapse
Some update. After hours of digging i found out these thread http://forum.xda-developers.com/showthread.php?t=899450
So, i first flashed defy 2.2_boot_only FIXED FSB, then after reboot custom recovery started working, so restored Droid22 rom from it.
Phew, i knew it was possible. So now i have rooted chines (?) android 2.2.1 on my phone and working custom recovery. I am gona stick on it for a while until i find best 2.3.3. nandroid ROM.
Just wanted to clarify was it right order - first flashing fixed SBF then restoring nandroid backup? I couldnt get custom recovery working without updating bootmenu first.
I also wanted to add that i did custom recovery data|cash wipe before flashing fixed SBF, before AND after restoring nandroid backup.
I saw that lots of people had problem like me , hope my message will help.
Here is link to another forum which has working download links http://www.addictivetips.com/mobile...ed-rooted-android-2-2-froyo-on-motorola-defy/