[Q] Alternatives ROMs to Orange 2.3.3?? - Defy General

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.

Related

[Q] Gapps Issue

So after flashing CM7 RC2 on my desire, i decided to flash Gapps for the market, google maps, etc.But after flashing Gapps, the phone reboots and gets stuck on the boot screen ( the blue arrow keeps on going in circles ).I did a restore and got everything back though but how am i suppose to use market now ?
solidsnake_devil said:
So after flashing CM7 RC2 on my desire, i decided to flash Gapps for the market, google maps, etc.But after flashing Gapps, the phone reboots and gets stuck on the boot screen ( the blue arrow keeps on going in circles ).I did a restore and got everything back though but how am i suppose to use market now ?
Click to expand...
Click to collapse
I have the same problem.
I tried using Gapps version 20110117 first, then wiped data and partition and installed Gapps version 20110120 and that seemed to work for me.
My problem now is that I cannot access the market, it just hangs
I know it's not a complete fix but at least it's a step in the right direction (I hope!)
The thread below reccomends "20110120 Universal"
http://forum.xda-developers.com/showthread.php?t=957344
solidsnake_devil said:
So after flashing CM7 RC2 on my desire, i decided to flash Gapps for the market, google maps, etc.But after flashing Gapps, the phone reboots and gets stuck on the boot screen ( the blue arrow keeps on going in circles ).I did a restore and got everything back though but how am i suppose to use market now ?
Click to expand...
Click to collapse
I have the same problem.
I tried using Gapps version 20110117 first, then wiped data and partition and installed Gapps version 20110120 and that seemed to work for me.
My problem now is that I cannot access the market, it just hangs
I know it's not a complete fix but at least it's a step in the right direction (I hope!)
The thread below reccomends "20110120 Universal"
http://forum.xda-developers.com/showthread.php?t=957344
Hmm .. can you please link me to the file? I'm probably considering shifting to ginger villain

[Q] Downgrade after Pays-Rom to Telstra JRDNEM_U3_2.26.0

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.

[Q] [Help] phone crashes when (mobile) data is enabled

Hi.
I'm running CyanogenMod7.1.0 on my Moto Defy, and recently, when I turn on mobile data the phone crashes (restarts) within a few seconds.
After restarting, the phone boots regularly, and then reboots every few seconds.
The last lines (before the crash) taken from adb are at: gist(dot)github(dot)com/1134269
a much longer logfile is at gist(dot)github(dot)com/1134231 (new user, can't post urls..)
each crash is marked (by me) with '=======================' and some newlines.
any help would be greatly appreciated.
As this works for almost everyone running CM7 (not seen any other reports of mobile data crashing/causing instability) it would seem sensible to clear cache/dalvik cache from Recovery (reboot, 'vol -' when the blue light shows) then Recovery - Clear Dalvik cache is under Advanced....
Also, if you're overclocking, reset to stock clocks/voltages and see if that fixes it..
You could also try the latest nightly builds - I'm using 'cm7-110809-0713-NIGHTLY-Jordan' without any issues (think I've tried almost every nightly build they guys have created!) and would strongly recommend it over your version.
Working brilliantly so far. THANKS russtyd.
And thank you for the detailed explanation, I didn't know about this recovery in cm7.
Sent from my MB525 using XDA App
I'm glad it was that easy to fix
As it turns out, I spoke too soon..
clearing the dalvik cache worked for about an hour, but than the problem came back.
Here's what I know so far:
using 2G network (with data) is OK.
Installing the 2 latest nightlies (110809 and 110806) - does not crash the phone when data is enabled, but it does kill all 2G/3G network connectivity.
Right now, I'm afraid of a hardware issue, so I'm gonna flush some stock sbf (any recommendations? would love a good tutorial, since it's my first time going back..) to check if it works there.
Anything else I might be missing?
If you want to go back to a 2.2 froyo then the CM7 FAQ is helpful for links to the sbf and drivers etc:
http://forum.xda-developers.com/showthread.php?t=1065798
Just download the following two files (links are in the FAQ):
- RSD Lite and Motorola Drivers (updated)
- SBF 3.4.2-177-005 NORDIC
Install Motorola drivers and run RSDLite, and then follow the first 2 steps of "2) How can I install CM7 RC0?", ie
- Power your phone with Volume Down pressed to enter Stock Recovery, then do "Wipe data/Factory reset" and "Wipe cache"
- Reboot from Stock Recovery with Volume Up pressed to enter Bootloader Mode, then open RSD Lite and flash Nordic
There are more sbfs here http://forum.xda-developers.com/showthread.php?t=966537 but having needed to do a clean install myself of CM7 last week (stuck on 'M' logo after a messed-up nightly install) I know this one works and gets you back to 2.2.2....

[Q] Update I9300 with 5.1.1 rom lost root

Hi,
I was on the paranoid 4.4.4 rom on my I9300, everything worked fine.
I did the last update with paranoid 5.1.1 but it didn't worked well, i have multiple error and Google service won't work anymore.
The thing is, i can't do anything at all, like restore my last backup because i lost the root access with the update.
I can't load in recovery mode, i tried the HOME+VOLUME DOWN (or up) + POWER, it won't work.
I can't fine the debug mode on this version, so i really don't know how i can at least restore my last backup to go back to the 4.4.4 version.
Any help is appreciated, thaks for your time.
Root doesn't ship with any 5.x build of paranoid android. To reset you need to boot into recovery and restore your backup or flash a different ROM.
You don't need root access for that.
It sounds like you installed an incompatible gapps....
Thanks for your reply,
I managed to boot in recovery, using a method i found on the web, i pull the battery then hold the combination keys when i put it back, and it load in recovery just fine.
I think i couldn't install the proper gapps because i was in clockwork recovery, i installed the latest TWRP, but i still can't manage to install the latest paranoid rom prpoperly.
here's what i did so far:
- wipe all/ factory reset , install Paranoid5.1.1 + Gapps 5.1 mini => paranoid load but Black screen once it's loaded with the message "Android.phone interrupted" (gross traduction) popping every 2 sec, it disapear if i put the phone on airplane mode => make me think the Google service can't connect.
- Restore my last 4.4.4 backup then => wipe cache/dalvik=>install Paranoid 5.1.1 + gapps => same as the previous problem, but this time i have my old app and i can call and receive sms.
My guess so far is a problem with the Google service who can't synchronize, the Gapps i try to use are the pa_gapps-modular-pico-5.1-20150315-signed.zip
Any guess ?
Yeah. The problem is you are using old gapps. Use banks gapps
I had trouble with a clean install of PA 5.1 + Gapps on my S3 (i9300) and similar issues to yours, not sure why but I found that if I used th full fat "Stock" 5.1 Gapps the phone was fine and has been for a day or 2 now, the pico/mini/full seemed to be problematic (at least for me). Also moved to Philz Recovery using the "Rashr" app as my old CWM kept throwing an error of status 6 on any Gapps I downloaded... Must admit though that once stable PA Lollipop runs well on the S3 and battery seems better over the past couple of days too...

LG G3 with cm-13.0-20161002-NIGHTLY-d850. Issues faced, guidance required.

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

Categories

Resources