Thanks to you to

Sent from my MB525 using Xparent Cyan Tapatalk 2

Originally Posted by Christiancs1969

Here's hoping your prob solved mines holding connection 2days so far.

Thanks for the diagrams, however that did not solve the problem.

On further investigation it seems there may be some underlying fault with the phone itself. I reverted to the Motorola default software, and instead of going deaf, the phone just automatically reboots itself after a short period when I have enabled data over mobile network. Time to send it back I think.

Thanks very much for all your suggestions.

Originally Posted by leigh8904

Thanks for the diagrams, however that did not solve the problem.

On further investigation it seems there may be some underlying fault with the phone itself. I reverted to the Motorola default software, and instead of going deaf, the phone just automatically reboots itself after a short period when I have enabled data over mobile network. Time to send it back I think.

Thanks very much for all your suggestions.

IC for signal processing could be faulty if things are not being managed by baseband switcher..try to enable only 2G just to diagnose the problem. Report it

Sent from my MB526 using xda premium

same problem

---

I think my defy has the same problem, I am on cm9 (newest quarkx2k build 22th may) additionally I cant switch back from flight mode until I reboot my phone and the notification icon does not seem accurate too and the phone has trouble connecting to gps.

Replaced phone - all good.

---

Originally Posted by leigh8904

On further investigation it seems there may be some underlying fault with the phone itself. I reverted to the Motorola default software, and instead of going deaf, the phone just automatically reboots itself after a short period when I have enabled data over mobile network. Time to send it back I think.

I sent the phone back to supplier (after carefully removing any traces of custom ROM and un-rooting), they replaced Defy+ with a new one. It is working perfectly now with WhiteRabbitEdition-1.5.2. Pretty clearly it was a hardware fault with the original handset.

Hi Leigh,

I think my brandnew defy+ (cm9 newest quarkx2k build) has the same fault too -_-

Do you have a good guide for me how I remove traces of the custom rom?

Best,
Florian

Originally Posted by floriko

I think my brandnew defy+ (cm9 newest quarkx2k build) has the same fault too -_-

Do you have a good guide for me how I remove traces of the custom rom?

Here is what I did:
1. Restore NANDROID backup of Motorola ROM (you have a backup right?) using custom recovery. You may be able to restore with SBF, but I have not used those.
2. Reboot into Motorola
3. Reboot into Android boot menu (press volume down when blue LED appears).
4. Navigate options (can't remember exactly) to uninstall Android boot menu. If this fails, reboot into Motorola make sure you have Defy 2ndInit installed, try again.
5. Reboot into Motorola. Make sure blue LED does NOT appear, this verifies that Android boot menu has been removed.
6. Remove any root type apps (eg. RootExplorer, Defy 2ndInit, Titanium Backup, etc), including data.
7. Connect up USB cable so that you can connect with adb.
8. Run unrooting script from: http://forum.xda-developers.com/show....php?t=1312859. Note: I used DooMLoRD's Easy Rooting Toolkit to root initially, this might not work if you used another method.
9. Reboot phone again.
10. Perform some testing to confirm root no longer accessible, eg connect via adb, try to su, check busybox has been removed, etc.
11. Perform factory reset - this will wipe everything from /data, /cache and SDCARD.