Ok, so here´s the deal:
I´ve recently got myself a Defy+ after my regular defy was stolen (no tracking software watsoever =/).
Since a lot of people told me the defy+ was just a red lens defy, i´ve thought that the same methods used for one were valid for the other.
Since it came with 2.3.4, I´ve just rooted it and installed 2nd Init. No problems until there.
The problem is: every single custom ROM I´ve tried installing through custom recovery (clockwork mod) gives me a bootloader error. I´ve tried CM7 and CM9.
It locks on the bootloader screen with the error, and won´t even let me get into recovery mode. Every time I have to restore a full sbf (only one I found to work), root, install 2nd init and then restore a backup from the original firmware I made.
Any ideas on what I could be doing wrong?
Did you try a Defy+ specific CM? Like http://forum.xda-developers.com/showthread.php?t=1445259
It has been reported that custom ROMs don't always play well with Defy+, and development on Defy+ is not as great as on Defy (due to its age). This should get better with time, look for CM9 and beyond.
i have tried this out and it has been working with battery charging to100% and camera also working.no 720p video tho.also has a few problems with cellular network reception.
After installing the init 2nt you can enter the boot loader?
You did a wipe data / cache after installing the new ROM?
You can post the error? photo ...
Related
Hi,
I (foolishly) tried to upgrade to Telstra Defy (build #JRDNEM_U3_2.26.0) to Pays-Rom ([ROM] Pays-ROM Defy v5.1 Froyo with Ginger feeling [3.4.3-11 based!]). I played with it briefly, couldn't get Clockwork Recovery (defy version) to run, and so wanted to go back to the original Telstra soft (from http://and-developers.com/sbf:defy)
I've used RSD Lite to restore that telstra soft before (from Chinese froyo) and it worked fine. However, when I do it now (after having used RSD to apply the 3.4.3-11 Motorola SBF from this thread ) then I get a blank screen - not even a Moto logo - when I try to boot (like this guy I think).
I reflashed back to the 3.4.3-11 Motorola SBF and the phone is booting happily again. However, I don't really want to be stuck on this - particularly since I can't actually get System Recovery (i.e. Clockwork Recovery) to go so can't seem to install Pays-Rom.
The magic question is: by upgrading to 3.4.3-11 from the Pays-Rom pack, have I removed my ability to go back to my original rom? If not, can anyone think what I may be doing wrong with my downgrade to kill the phone?
Cheers.
Was asking why system recovery was not working - answer was because I had failed to disable USB debugging. Oops. Main problem remains though.
If you flashed a full SBF, then you can't go back to 2.1. It's not bad as you think, since 2.2 in every country is about to be released. When this happens you will need only a nandroid backup...
Sent from my MB525 using Tapatalk
I have done a similar thing, flashed 3.4.2_155-002 and now cant downgrade back to the default Telstra rom. Not to concerned at the moment as I am using Color ROM from here, http://forum.xda-developers.com/showthread.php?t=1021742. It is based on this SBF, 3.4.2-155-2 deblur. Just follow the installation instructions and you should have no trouble. Very fast and deblurred. every thing works fine on my Defy, including clockwork recovery.
Only problem I may have is not being able to downgrade to stock if the phone has to go back to telstra for anything.
Hope this helps.
Cheers.
Hi,
I was recently trying to get CyanogenMod 7 on my Defy. This is what happened...
rooted with z4root
installed ClockworkMod bootloader (using System Recovery apk)
performed a full backup
ran the update.zip for CM7 (from here)
wiped user data + cache (didn't wipe before running update.zip, because I didn't read it properly!)
got stuck in a "M" logo loop
flashed the UK T-Mobile 2.21.1 SBF file (from here) with RSD Lite
ended up with a completely dead Defy! (as described here)
the only ROM i can get to boot at all is the UK Orange 2.3.3 (from here)
i rooted using this method (here)
i've reinstalled the ClockworkMod recovery (using the same System Recovery apk)
when it reboots to the recovery, I just get a black screen
Does anyone know any way of reverting back to the stock T-Mobile ROM (or, ideally, move to CyanogenMod 7?), or does it look like I'm stuck in the Orange ROM?
Any help would be appreciated!
Thanks!
xnoruk said:
Hi,
I was recently trying to get CyanogenMod 7 on my Defy. This is what happened...
rooted with z4root
installed ClockworkMod bootloader (using System Recovery apk)
performed a full backup
ran the update.zip for CM7 (from here)
wiped user data + cache (didn't wipe before running update.zip, because I didn't read it properly!)
got stuck in a "M" logo loop
flashed the UK T-Mobile 2.21.1 SBF file (from here) with RSD Lite
ended up with a completely dead Defy! (as described here)
the only ROM i can get to boot at all is the UK Orange 2.3.3 (from here)
i rooted using this method (here)
i've reinstalled the ClockworkMod recovery (using the same System Recovery apk)
when it reboots to the recovery, I just get a black screen
Does anyone know any way of reverting back to the stock T-Mobile ROM (or, ideally, move to CyanogenMod 7?), or does it look like I'm stuck in the Orange ROM?
Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
Even for me CM7 Beta 6 didn't worked... well but I am happy to be on Leaked Orange GB 2.3.3 with Blur..
It's definitely an improvement on the original ROM! It supports proxy over wifi (although I haven't tried it yet), although GPS + android Market don't work... but I suppose it's much better than having a bricked phone!
I'm also on the leaked 2.3.3 orange rom and everything seems to work great so far (using it for 1 week now).
I've had a problem with the market too in the beginning. The market needs a google account to work and I couldn't add this account to motoblur from the beginning, where you setup motoblur, so the market wouldn't work for me. I did a wipe data/factory reset, rebooted and this time I could add the google account. Not a single bug, FC, reboot or anything like that so far (ok 1 "bug" to be honest, the signal bars stay empty but the 2g, 3g and hdspa indicators work). I've also used gps navigation without problems and the camera too without the fixes in the forum, but you may want to try the fix from walther79 for gps (http://forum.xda-developers.com/showpost.php?p=14046494&postcount=388).
I haven't tried myself but they say it can be downgraded. If you carefully follow this guide (http://forum.xda-developers.com/showthread.php?t=1054447) and use the sbf mentioned in that post you should be able to install cyanogenmod 7 succesfully. Use this guide for flashing: http://forum.xda-developers.com/showthread.php?t=853674
If you want to wipe data and cache before flashing (suggested) you could use clockwork OR the standard recovery (http://www.hardreset.eu/motorola_defy_hard_reset_soft_reset_en.html). Though you should hold volume up + volume down after you see the droid instead of tapping the touchscreen. There is also a chance clockworkmod will work after you've done a wipe data/factory reset.
Hello
I had a few problems with my Defy in Cyanogen : especially a reboot always resulted in the loss of new contacts and sms since last started... and the re-install of Cyano (including Nightly) not solved this problem.
So I decided to start from scratch by resuming from the beginning the installation of the Cyanogen: Full wipe, Flash FBS, and rom install.
Unfortunately, flash any SBF is now impossible: there are always checksum errors in RSDlite (in the code group 33, 39, 42,... only the code group 32 is ok).
Log in RDS systematically indicates: "ERROR: Phone [0000]: Error geting subscriber unit checksum".
So I only have access to the bootloader, which tells "code corrupt".... The recovery is impossible.
Fortunately I have a universal charger which allows me to recharge the battery. So I can do several tests.
I tried lots of SBF (Nordic, EEC, Stock), several versions of Rsdlite (5.0; 5.3.1), on several PC, with several cables.... and still the same error.
Do you know this problem? Is there a solution or telephone is bricked?
In the latter case, as only bootloader is active, do you think that after sales service will see previous fhash (Defy is still under warranty) ?
Any help for this problem is welcome!
Thanks in advance!
Use rsdlite 4.9 n try
Sent from My Mind using the Brainwaves...
Thanks for your answer.
Same problem with RSDlite 4.9 ...
Hey is you're problem solved?
Sent from my MB525 using CM7
Have you solved your problem? The same thing happened to me today. I cant get my defy to run
use only those full SBF version, which was installed at the time when u buy the phone.
Hi Developers,
I have a Defy (orginally came with Froyo, Green Lens). I am running CM10, Kernal Version "2.6.32.9-gbdd614e". Initially the problem started when I was upgrading to a ICS version by wiping my data and cache. I wasnt able to do that and for some reason I wasnt able to restore via RSD. Hence I used Defy+ SBF file. It worked. Now everything was fine but whenever I tried flashing Kernal (No matter what it is CM7, CM9 and Kernal-Froyo-222-179-4-signed), I was getting this error below :
Bootloader
09.10
Err:A5,70,00,00,23
Battery OK
OK to Program
Connect USB
Data Cable
The only way then was to again flash it with RSD defy+ stock ROM. I am running Jellybean by directly flashing the ROM and not flashing the Kernal. The camera has stopped working since then and no matter now what ROM I flash it with the camera wont work. I have tried ICS, GB, Froyo.
I dont know if the info is still enough or not but if you can help me that will be a great help.
You flashed Defy+ SBF on your Defy, no cam for you.
You'll never get your camera back. You should've never flashed a defy+ sbf on green lens defy. It's well documented in relevant threads.
andr0idfreak said:
You'll never get your camera back. You should've never flashed a defy+ sbf on green lens defy. It's well documented in relevant threads.
Click to expand...
Click to collapse
I didnt have any other option at that time as it was not accepting any SBF i try to flash it with. However when I first flashed the Defy+ stock ROM the camera was working. It stopped when when I flashed it with Jellybean ROM.
same problem partially solved
JadhavN said:
Hi Developers,
I have a Defy (orginally came with Froyo, Green Lens). I am running CM10, Kernal Version "2.6.32.9-gbdd614e". Initially the problem started when I was upgrading to a ICS version by wiping my data and cache. I wasnt able to do that and for some reason I wasnt able to restore via RSD. Hence I used Defy+ SBF file. It worked. Now everything was fine but whenever I tried flashing Kernal (No matter what it is CM7, CM9 and Kernal-Froyo-222-179-4-signed), I was getting this error below :
Bootloader
09.10
Err:A5,70,00,00,23
Battery OK
OK to Program
Connect USB
Data Cable
The only way then was to again flash it with RSD defy+ stock ROM. I am running Jellybean by directly flashing the ROM and not flashing the Kernal. The camera has stopped working since then and no matter now what ROM I flash it with the camera wont work. I have tried ICS, GB, Froyo.
Hello, well, same problem - same defy green lens - after many reflashes...I only made it work with defy+ sbf. In this way, the only rom that enabled camera was CM10 4.1.2 2.boot. So camera fully worked again, no problem. BUT when trying to get WIUI for better performance, I lost the functionality of the camera again. So - in my opinion - camera WILL NOT DIE - (burn) only it becomes not functional in some software environment. SO, this is a DEV' s problem to be solved.
Click to expand...
Click to collapse
Root BL7 - it need special instruction - it's in General or in Developement section - don't remember. Since you flash BL7 sbf on green lens - no hope with camera on stock roms, last hope is - 2ndboot based roms with custom kernel: WIUI 4, CM10/9/7(maniac last builds)..
Отправлено с моего MB526 через Tapatalk
New to the world of Custom ROMs. A week ago I installed CM 13 which took great courage on my part and wanted to share my experience, issues and discuss possible solutions.
My phone had the latest lollipop on it. And McCafee locked. The steps that worked for me where
1) Did a factory reset and bumped into mccafee.
2) Tried download mode but kill switch was enabled.
3) Rebooted the phone to face mccafee, tried 123465 pin which worked.
4) Disengaged McCafee but not before transferring ownership to my email.
5) Tried rooting didnt work with any method.
6) Rolled back to d software version stock lollipop.
7) Rooted with PurpleDrake
8) Replaced with CM recovery didnt work.
9) Replaced with TWRP and rebooted directly to recovery
10) Installed CM and gapps mini. Worked fine. Voila!
Issues:
1) No Custom recovery sticks, whenever I flash with a custom recovery like TWRP or Clockwork. I have to reboot into recovery immediately or the custom recovery is replaced by stock. It happens on every second reboot.
My concern is here if I get stuck into bootloop and dont have a custom recovery I might not have any other option than the stock ROM which does a full reset. How can make TWRP stick forever?
2) After installation of Custom ROM there have been random reboots, I suspect there is something here with phone app or voice. So far the reboots have been when I try to call using fb messenger, appear.in and phone app itself.
Is there a guide that tells me how to track this down?
Can I install a newer Nightly and hope this get fixed?
How can I retain my apps and data when installing a newer nightly? since all guides ask to wipe everything :S
I have a backup of system and data partitions, can I use that with other ROMs.
What ROMs have a better chance of fixing this issue?
Coudnt find Stock M for D850. Why arent those available?
Should an Official ROM be more reliable than CM for this?
3) Bad signal reception so far. It may be a generic g3 issue.
Can I hope that this issue be fixed with a different ROM or updates from Cynogen?
Someone said you may have to flash the radio partition. My question is where can I get a brief understanding of what partitions there are in android and which are risky. Which ones can be replaced, backedup and replaced back.
4) Whenever the phone reboots, it gets stuck into bootloop unless I remove the SIM card. Then I power off and install SIM Card and reboot and it boots fine.
I am already tracking CM changelog for something important. Cant post urls as of now :S