Database Users

CM 6.1 Stable

Hey, question. Every single CM from 6.0 I have downloaded I have had issues with. I love the rom, but every time I get the same issue. When I install the rom all worked fine. I wipe all data, clear cache, and have to reinstall of course everything, my issue is that my phone will randomly freeze. Sometimes I get an error message saying the process process.android has failed, other times it just freezes. Does anybody have any ideas?

I loved CM 6.1 best Rom I've had yet. But after a week it started acting up and having problematic auto shutdowns like 8 times a day. I then searched for another stock Rom and tried skyraider vanilla, I hate it. It's basically skinned sense. That's it. I enjoy sense but it eats battery. My favorite roms so far are the desire Hd Rom and
CM but without the shutdowns is be perfect.
Sent from my ADR6300 using XDA App

only people
So this is the only other person I have run into with this problem. Everybody else I have talked to over other forums or IRC has never heard of these issues at all.

The only time I've ever had those shut down issues is when I start screwing with themes or when I start screwing with kernels or overclocking. I'm not sure what you've got going on there though

Well...
Well I have done some of that however I have reverted to "stock" several times. I have Hboot .92 installed also, i saw something online. The latest radio is also installed. I guess has anybody else seen any issues like this?

Try formatting the system in addition to wiping. CM does not format anything when you flash it. In CWM its under mount sd section.
Sent from my Htc Incredible using XDA App

This happened to me today, I am 99% sure it was the kernel I had installed though. I put back invisiblek's #18 and had no problems before or after.

okay I can mess around with that and see what happens then.

justinmburrous said:
okay I can mess around with that and see what happens then.
Click to expand...
Click to collapse
Let us know please.

This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!

neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
You need to be a little more specific but do this.
1. Click on the Cyanogen link in my signature and download it.
2. Download google apps
3. Reboot into recovery
4. Wipe Data/Factory Reset
5. Wipe Cache Partition
6. Wipe Dalvik Cache
7. Select install zip from SD card and choose the cyanogen ROM, let it install
8. Select install zip from SD card again and choose the google apps.
9. Reboot your phone and sign into your google account and let everything sync
This is the best way to do it. Not through ROM Manager.
If this doesn't work then I have absolutely no idea. That is the 100% correct way to flash a ROM.

neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
I had to revert back to #18 kernel working fine now!

neur0tk said:
I had to revert back to #18 kernel working fine now!
Click to expand...
Click to collapse
Yeah I mentioned it earlier in this thread. For some reason #21 and #22 do not like cyanogen.

I'm running #21 on my phone and I haven't had any issues yet.

Yeah IDK either... I had to revert now it's running like a champ! love the Inexus theme!

ok an update, I have everything working. I an using cm6.1, latest radio (on cm site), kernel 27, hoot .92, and the very latest clockwork that just came out. I know those last two should not matter, just letting you know. As of right now my phone is not freezing and everything works fine, even faster than before. When I first turned it on the phone did freezer and after that yet took a long time for 3g to start working. On reinstall I did a total revert to stock then did a factory reset and cleared all caches and everything on the phone there is to clear. It has been afew hours. I will update this if there are any more problems
Sent from my ADR6300 using Tapatalk

Keeps rebooting more and more time to switch roms
Justinmburrous
Justinmburrous.com

[Q] 2.3.3 OTA Rooted problem...

Hey I would have posted this on a different thread but i cant because i just made this account they want atleast 10 posts...
heres the deal... i have a rooted evo and running cm7 which i like, but i was dropping calls and where i live i should have good service. so i got the updated radio/wifi/ ect package and flashed it... it installed but did not help with the call issue... i heard many other having the same problem.
so i flashed the ota root update... which seemed like it did it really fast (wasnt watching the whole time) and the phone rebooted but gets stuck at the white htc evo screen, i let it sit there for 20 mins nothing, so right now i am recovering my old cm7... just wondering if anyone has that same problem or can help with getting better voice reception on cm7.. like i said i have tried the package for radio ect... and my prl was updated before i flashed to stable of cm7 so that should be in good standing i would imagine... thanks..

The obvious first question is, did you do a full and complete wipe of everything before you flashed the ROM?
As far as your signal, it may have been just in my area, but I know a few people that had problems texting and making calls, getting a "Network Is busy" error.

yea i did the wipe data/cache i wasnt dropping calls before the cm7 so im not sure right now im shootin to myns seeing how that is... cm7 was first flash i did
well as im trying to flash to the myns its looking like the samething... ill go through the steps...
have zip file in root of sd card
open up rom manager, have the newest clockwork thing installed
i goto flash from sd wipe data and cache are checked... i already have a backup so i skip that part
it installs.... says install is done and reboots itself... but seems to stay on that white bootscreen
if i take the battery out then i can reboot with recovery from the save file i have

blah i dont know... i got the ota installed... looked like it got a bit better reception.. i updated prl and came back to cm7 same probs... i dunno maybe ill just have to let go of cm7... really dont want to though its so sexy lol

I had the same weak signal issue with cm7 and had dropped calls and data dropping to 1x. I am on stock rooted 2.3.3 and reception is good again. Liked cm7 but need a phone I can use in the boonies.
Sent from my PC36100 using XDA Premium App

Dude, please, don't use ROM Manger.
Just boot to recovery, hopefully, you have Amon Ra, if not, search how to get it on your phone, it's not hard, do a FULL WIPE, full, wipe everything in recovery, then flash the ROM in recovery.
No offense to the Dev, I know he's a great guy, a smart guy, hard worker that makes a contribution, but Rom Manager is not the best way to do this.

Yea had to do it manually but nymph works now liking it so far

ok now i have different problem.... got the myn working liking it, but my market is completely different, not just the theme, but the apps i usually download... so tried to flash new market but it just open/closes quickly... any ideas for that?

Not sure by what you mean by the apps you usually d/l.
One thing about the Market in these newer ROMS is that sometimes, you just need to give it some time to fully sync before all your apps so up...
You should pull the market out of the zip file for the ROM and re-install that one, but you'll have to delete the one you have installed now, first.

umm usually download ninjump cant find that just some games that are usually on my phone the market on cm7 had them... ill give it a try though

look on the android market website

Random reboots/shutdowns with Aura and Atrix?

I've re-installed Atrix 4 times on my phone, each time doing a factory reset, clearing cache, and Dalvik cache. I've had random reboots/shutdowns on every install of Alien Build #4 and Aura 1.1.3.8. One running Atrix stock kernal, 2 using faux's kernal 0.1.6 (one non-oc, one oc), and one using faux's OC 0.1.7. Now I'm running Aura 1.1.3 Build #8 Deblurred. All with random reboots and shutdowns.
I've noticed I never get a random reboot while I'm charging, only while on battery. I've calibrated my battery several times so it's not lack of juice. Sometimes it just reboots, other times it shuts down and doesn't reboot so I have to turn on the phone, though most of the time the screen won't turn on and the phone won't shut off so I have to take out the battery to turn on the phone. I've tried uninstalling SetCPU, disabling profiles, and setting the max clock to 1000mhz. None of this helped.
On the last Alien install (now I'm running Aura) I was having even more problems but they only happened on that install:
1. I got an error when trying to boot in red: "Unrecoverable Bootloader error (0x00000004)" though I was able to turn the phone off and reboot normally.
2. I got an error about 5 times in a row while trying to boot, I forgot the exact text but something along the lines of "Unable to load radio module (0)". I had to take out the battery and try about 5 times till it would boot properly.
3. After this, I was unable to boot into Recovery through the volume buttons, I'd press down till I got the Android Recovery, then press up and it'd hang there. It works now for some reason.​
I installed Alien right when I got my phone so I'm unsure if random reboots happen stock. Also my phone gets really warm when I'm using it, I look in SetCPU and the CPU temp is anywhere from 42 to 57 C. Does anyone else's phone get this hot?
I would just take it back to Best Buy and get a new one cause I have a protection plan with them, but my phone is unlocked which voids the warranty.
Does anyone know what could be causing all of these issues and how to fix them?
Thanks for the help, XDA is great!

Im by no means a expert...but I'm currently running AURA 1.1.3#8 debloat and all is well on my phone....I would recommend performing a Ti backup on ur aps and doing a factory reset to see if the problem persists....if it does I would take it back...if not reinstall through CWM wiping devalk cache then a full data wipe then install AURA and reboot all in CWM ....btw I'm running Rom Racers CWM also. Hope you can get it figured out!

JRW 28 said:
Im by no means a expert...but I'm currently running AURA 1.1.3#8 debloat and all is well on my phone....I would recommend performing a Ti backup on ur aps and doing a factory reset to see if the problem persists....if it does I would take it back...if not reinstall through CWM wiping devalk cache then a full data wipe then install AURA and reboot all in CWM ....btw I'm running Rom Racers CWM also. Hope you can get it figured out!
Click to expand...
Click to collapse
I would have just taken it in but my phone is unlocked, rooted, and using Romracers CWM so I doubt Best But will accept it. I've tried all of this. I'm going to try CM7 Beta2, if the problem still persists I don't know what to do cause Best Buy won't accept it when they see the Unlocked at the top of the bootloader. It works fine when it's charging but so far no matter what I've tried I always got reboots. Does your phone get hot? Can you check what temps you get in SetCPU? Thanks for the suggestions btw.

My phone has never gotten over 33*....Try going back to stock gingerbread and see if the problems persist there and if not then u can proceed forward.....that way you can rule out if the problem is the phone or a certain build and a bug you have picked up

Sorry I meant 39* on phone temp

I went into my settings>widow and turned it off then rebooted, seemed to work, I also would get random reboots after a fresh install. Like at least 20x. But try that. Worked for me.
Sent from my MB860 using XDA App

JRW 28 said:
My phone has never gotten over 33*....Try going back to stock gingerbread and see if the problems persist there and if not then u can proceed forward.....that way you can rule out if the problem is the phone or a certain build and a bug you have picked up
Click to expand...
Click to collapse
33? Wow, my phone never goes below 42C, it's usually around 49-50C. How do you return to stock gingerbread like the phone came with? All I've found was flashing the SBF through RDA, is there any way to do it with CWM so it's safer? Sorry for the noobiness, I'm new to the Atrix, is there a way to completely restore the phone to stock (stock gingerbread, locked bootloader, no CWM)?
Edit: I just flashed CM7 pre-beta 2, going to see how this works, hopefully it fixes my problems.

performing a data wipe/factory reset in CWM should put you completely back to stock. It wont matter that you have a UL bootloader or rooted.

Ecstacy42 said:
I've re-installed Atrix 4 times on my phone, each time doing a factory reset, clearing cache, and Dalvik cache. I've had random reboots/shutdowns on every install of Alien Build #4 and Aura 1.1.3.8. One running Atrix stock kernal, 2 using faux's kernal 0.1.6 (one non-oc, one oc), and one using faux's OC 0.1.7. Now I'm running Aura 1.1.3 Build #8 Deblurred. All with random reboots and shutdowns.
I've noticed I never get a random reboot while I'm charging, only while on battery. I've calibrated my battery several times so it's not lack of juice. Sometimes it just reboots, other times it shuts down and doesn't reboot so I have to turn on the phone, though most of the time the screen won't turn on and the phone won't shut off so I have to take out the battery to turn on the phone. I've tried uninstalling SetCPU, disabling profiles, and setting the max clock to 1000mhz. None of this helped.
On the last Alien install (now I'm running Aura) I was having even more problems but they only happened on that install:
1. I got an error when trying to boot in red: "Unrecoverable Bootloader error (0x00000004)" though I was able to turn the phone off and reboot normally.
2. I got an error about 5 times in a row while trying to boot, I forgot the exact text but something along the lines of "Unable to load radio module (0)". I had to take out the battery and try about 5 times till it would boot properly.
3. After this, I was unable to boot into Recovery through the volume buttons, I'd press down till I got the Android Recovery, then press up and it'd hang there. It works now for some reason.​
I installed Alien right when I got my phone so I'm unsure if random reboots happen stock. Also my phone gets really warm when I'm using it, I look in SetCPU and the CPU temp is anywhere from 42 to 57 C. Does anyone else's phone get this hot?
I would just take it back to Best Buy and get a new one cause I have a protection plan with them, but my phone is unlocked which voids the warranty.
Does anyone know what could be causing all of these issues and how to fix them?
Thanks for the help, XDA is great!
Click to expand...
Click to collapse
Are you doing a factory data/reset wipe cache and wipe dalvik step after you install a new rom? Do the same wipe steps before and after rom flash. If you are doing this then it sounds like a hardware problem or your bl got thrashed unlocking it.
Sent from my MB860 using xda premium

Ecstacy42 said:
33? Wow, my phone never goes below 42C, it's usually around 49-50C. How do you return to stock gingerbread like the phone came with? All I've found was flashing the SBF through RDA, is there any way to do it with CWM so it's safer? Sorry for the noobiness, I'm new to the Atrix, is there a way to completely restore the phone to stock (stock gingerbread, locked bootloader, no CWM)?
Edit: I just flashed CM7 pre-beta 2, going to see how this works, hopefully it fixes my problems.
Click to expand...
Click to collapse
Go the fruitcakes thread in the developement section. Stock cwm flashable builds.
Sent from my MB860 using xda premium

JRW 28 said:
performing a data wipe/factory reset in CWM should put you completely back to stock. It wont matter that you have a UL bootloader or rooted.
Click to expand...
Click to collapse
It will only reset to the current rom defaults. If you have cm7 or alien flashed, It will revert back cm7 or alien. Doesn't effect root or bootloader. If the rom is pre rooted it stays rooted even after a full wipe.
Sent from my MB860 using xda premium

Dirtburgler said:
Are you doing a factory data/reset wipe cache and wipe dalvik step after you install a new rom? Do the same wipe steps before and after rom flash. If you are doing this then it sounds like a hardware problem or your bl got thrashed unlocking it.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
That sounds highly possible as it happens with each install and I am doing a factory reset, cache wipe, and dalvik cache wipe with each install. If ran the unlocking script again would it erase the bootloader and re-install it to fix that?
Edit: I just got another "Unrecoverable Bootloader error (0x00000004)" error, I'm going to re-run the script.

Ecstacy42 said:
That sounds highly possible as it happens with each install and I am doing a factory reset, cache wipe, and dalvik cache wipe with each install. If ran the unlocking script again would it erase the bootloader and re-install it to fix that?
Edit: I just got another "Unrecoverable Bootloader error (0x00000004)" error, I'm going to re-run the script.
Click to expand...
Click to collapse
No don't. The script doesn't update the boitloader I don't think. Did you use the ota to get gingerbread?
If the bl is fubared and your not on the legit ota you can rsd to 1.83 and start over. If you are on the ota update then all you can use is cwm(safely)
Sent from my MB860 using xda premium

when I was on Ninja SF I performed a factory reset and forgot to perform a backup and it took me back to completly stock gingerbread....sorry if I was misleading him

Dirtburgler said:
No don't. The script doesn't update the boitloader I don't think. Did you use the ota to get gingerbread?
If the bl is fubared and your not on the legit ota you can rsd to 1.83 and start over. If you are on the ota update then all you can use is cwm(safely)
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
My phone came shipped with 2.3.4 Gingerbread, I never used the OTA update. I re-ran the script and got another random reboot.
Edit: I'm flashing the official 2.3.4 SBF from here: http://forum.xda-developers.com/showthread.php?t=1125944
I'll let you all know how things went.

From what I understand ...once u are on 2.3.4 if u try to flashback to. 83 it will hard brick you...definitely flash back to stock gingerbread 2.3.4 and hopefully that will solve your problems ....good luck

I installed Aura 1.1.3 Debloat #7 two days ago and my phone rebooted by itself today. I had it in my pocket, then I took it out and it was loading. I thought I might have pushed something when moving, but maybe it is related to the rom.

Okay, I flashed 2.3.4 with pudding boot loader unlocked and Romracer CWM Recovery. I'm going to install Alien and faux's kernal, hope flashing 2.3.4 fixed this and it's not a hardware issue.

Did you experience any problems while you were on 2.3.4 or did you flash straight to alien afterwards ...hope you get your problems figured out! Make a backup of the 2.3.4 flash also so if you do experience any problems you can always flash back

JRW 28 said:
Did you experience any problems while you were on 2.3.4 or did you flash straight to alien afterwards ...hope you get your problems figured out! Make a backup of the 2.3.4 flash also so if you do experience any problems you can always flash back
Click to expand...
Click to collapse
I flashed straight to Alien when I got the phone so I'm not sure it stock Gingerbread had problems. I just flashed 2.3.4 with pudding unlocked bootloader, Romracer's CWM, and finished installing Atrix Build 4 and faux's kernal 0.1.7. I'm going to take the phone off the charger (I only get reboots and shutdowns while on battery), and start installing my apps, restoring contacts, messages, and see if I have any problems. I'm not going to install SetCPU and mess with profiles and undervolting till I know I'm good.
I'll report how it's going tomorrow morning (usually by that time I get at least 5 to 10 random reboots/shutdowns). If this doesn't fix it then I'm going to flash the stock 2.3.4 SBF so they don't know I messed around with the device and take it back to Best Buy to get a replacement.

[Q] update CM7 to CM10 after messing up with wrong sbf

Hi everyone,
some time ago I flashed a wrong sbf to my Defy and thanks to the All-in-One Defy Beginner's guide
Zephyrot said:
Installed full Gingerbread SBF and can’t go back to another rom: (!) aha! We have a issue here!, latest Stock Gingerbread full SBFs comes with a Version 5 of the CG, meaning until not long ago you were pretty much screwed. But wait, there is hope! A one kind Éclair has been found in China Defys that comes with Version 5 CG!.
How to fix it:
Method 1:
Download this SBF and Flash it
Root your Phone
Download 2nd Init 1.4.2 and Install ClockworkMod Recovery
Download and install this Nandroid Backup << File is Back, thanks Ichibanme again!>>
Enter Recovery, Wipe Data/Cache
After wiping, turn off your phone
Turn it on and get immediately into Bootloader mode
Flash this Fixed SBF
Delete Data/Cache again and reboot.
**NOTE*: I just rephrased the original post since it can be a bit confusing, it is linked as source below.
**NOTE2**: If you are using a non-Chinese defy, DO NOT USE THE CAMERA FLASH while on the Chinese rom, it WILL kill your LED.
Source: ((Original post here))[
Method 2: (BIG thanks to Jebrew again for this one)
NOTE: You are going to need CM7 for this one. CM7 Stable version recommended.
Download this SBF and Flash it.
Root your phone.
Download 2nd Init 1.4.2 and Install ClockworkMod Recovery.
Reboot to CMW recovery, and wipe Data/Cache.
Install CM7 then install Google Apps.
Reboot an go into Stock Recovery (using the vol- button, not from Bootmenu).
Do a Data/Cache Wipe or you won't have any space when you're done.
Flash this Fixed SBF
Reboot into your nice new rom.
Do not Wipe Data anymore or you will have to start again.
​
You WONT be able to install full SBFs of any Éclair or Froyo since these Androids have lower CG Versions.​
Click to expand...
Click to collapse
I'm running CM7 again with a version 5 CG, if I got it right.
So far so good. But now I need to update my ROM to be able to update some apps that won't run on CM7.
So what's the best tactic for updating this messed up phone? Just flashing any CM10+ ROM (I tried several ones) didn't seem to work. I always got stucked at the red Motorola 'M'.
Any ideas?
Thanks a lot!
Cheers,
Martin

smashedup said:
I always got stucked at the red Motorola 'M'
Click to expand...
Click to collapse
factory reset

Thanks for your reply.
Besides the fact that I can't go anywhere to do a factory reset as soon as I've updated to something like CM10, I do a lot of resets/wipes on my way to this state (see quoted guide above).

smashedup said:
Thanks for your reply.
Besides the fact that I can't go anywhere to do a factory reset as soon as I've updated to something like CM10, I do a lot of resets/wipes on my way to this state (see quoted guide above).
Click to expand...
Click to collapse
Use Defy full wiper/AROMA wiper to wipe system, data and cache with EXT4. Then immediately flash CM10 and gapps.

hotdog125 said:
Use Defy full wiper/AROMA wiper to wipe system, data and cache with EXT4. Then immediately flash CM10 and gapps.
Click to expand...
Click to collapse
Tried that, but now I always get a Status 7 error message when trying to install (no matter if I wipe with Aroma or in CWM). I found a lot of people with that same problem but no solution for me... I'm wondering why I did not have that status 7 thing before....

smashedup said:
Tried that, but now I always get a Status 7 error message when trying to install (no matter if I wipe with Aroma or in CWM). I found a lot of people with that same problem but no solution for me... I'm wondering why I did not have that status 7 thing before....
Click to expand...
Click to collapse
For some users flashing DFP-231 helped.
Sent from my Nexus 7 using Tapatalk

hotdog125 said:
For some users flashing DFP-231 helped.
Click to expand...
Click to collapse
Thanks for the hint!
But this is a Defy+ sbf and after flashing I might not be able to go back, or not?
From the thread [Q] defy bricked, not even JORDN_U3_97.21.51.sbf helps :
kirov1045 said:
what are the chances it will work? i'll scared i'll totally brick it. it's 100% not a defy+
Click to expand...
Click to collapse
thekguy said:
Zero percent chance of bricking
Only problem is that there may be problems in the stock rom, which can be fixed by installing cm10 or cm10.1
By problem I mean no camera or battery not charging to the full level but again these can be fixed by upgrading to cm10 or 10.1
Click to expand...
Click to collapse
If - for any reason - CM10+ does not work for me, I don't want to deal with these issues...
Or am I getting this wrong?

smashedup said:
Thanks for the hint!
But this is a Defy+ sbf and after flashing I might not be able to go back, or not?
From the thread [Q] defy bricked, not even JORDN_U3_97.21.51.sbf helps :
If - for any reason - CM10+ does not work for me, I don't want to deal with these issues...
Or am I getting this wrong?
Click to expand...
Click to collapse
Well, it helped some people. You can't go back to 2.2 after flashing GB.
Sent from my Nexus 7 using Tapatalk

hotdog125 said:
Well, it helped some people. You can't go back to 2.2 after flashing GB.
Click to expand...
Click to collapse
Thanks for clarifying.
But I just decided to not mess around another time and will stick to my well running CM7.2 for this device. I found a workaround for my app-prob anyway.
Thanks again for help!

Downgrade from CM11 to CM 7 or any other ROM

Hi
I have installed CM11 (4.4.2) on Defy and it is working fine except the battery.
This entailed installing TWRP
Earlier I had MIUI Pikachu edition.
Questions
1. How do I install or restore my MIUI backup again.
2. Also I would like to downgrade to CM 7/9 which is more stable
Any links or step by step suggestions would be appreciated
Thanks
Ninad

ninadb said:
Hi
I have installed CM11 (4.4.2) on Defy and it is working fine except the battery.
This entailed installing TWRP
Earlier I had MIUI Pikachu edition.
Questions
1. How do I install or restore my MIUI backup again.
2. Also I would like to downgrade to CM 7/9 which is more stable
Any links or step by step suggestions would be appreciated
Thanks
Ninad
Click to expand...
Click to collapse
please do not post questions in the development section
post moved to the Q&A

No reply for this? I Also want to chahge from CM11 to MIUI on Defy, but just flashing the zip in the TWRP does noting and the phone always start the CM11.
Thanks a lot!

evilinheaven said:
No reply for this? I Also want to chahge from CM11 to MIUI on Defy, but just flashing the zip in the TWRP does noting and the phone always start the CM11.
Thanks a lot!
Click to expand...
Click to collapse
Probably you need to flash sbf to get an old bootstrap.
Sent from my HTC One using Tapatalk

I wan to downgrade as well, preferrably w/o sbf. But I flashed so often by now, searching for the fastest way w/o: 1-sbf, 2-reroot, 3-custom recovery and 4-flashing cm7 would take more time, than the flashing process itself.
So that's what I'm gonna do. Hope it gets snappier then. CM11 with just about 9-10 apps (facebook, messenger, whatsapp, gmail, gcal, aero control, battery stats, es file explorer) is already torture for my defy.

erdnuesse said:
I wan to downgrade as well, preferrably w/o sbf. But I flashed so often by now, searching for the fastest way w/o: 1-sbf, 2-reroot, 3-custom recovery and 4-flashing cm7 would take more time, than the flashing process itself.
So that's what I'm gonna do. Hope it gets snappier then. CM11 with just about 9-10 apps (facebook, messenger, whatsapp, gmail, gcal, aero control, battery stats, es file explorer) is already torture for my defy.
Click to expand...
Click to collapse
I have an idea, and its a possibility for you. I have a Atrix 4G which also is on CM11, and like you guys on the Defy, has a bigpart mod. For us to downgrade, its flash an old recovery, boot to recovery, factory reset, wipe all partitions (system, data, cache, boot (that should be the ones you have too)), flash desired ROM/restore backup. Not sure if that will work for you, but its worth a shot. If it doesn't work, i'd try sbf'ing (someone posted an sbf lately if i remember correctly
Sent from my ATRIX HD using XDA Free mobile app

Unfortunately I don't know what sbf to take - it might be irrelevant, since i accidentally flashed to bl7 long ago and since I wanted to reroot again, twrp and cm7 it might not matter which one to flash. I am trying to speed things up a bit, and struggle with twrp atm, because safewipe.zip might no longer be safe (unable to enter twrp) or the version was not meant for my configuration.
Now i trimmed all part's and try amplifying services, but it's been a while since i tuned my defy.
OT: I switched to Moto G and E2 (but lost both ones - or they've been stolen) and now I want to reactivate my old pal before switching to anything new again. It's getting expensive...
So don't wait, maybe I'll get CM11 to work good enough again, but if not, I'll try to provide a checklist.
palmbeach05 said:
I have an idea, and its a possibility for you. I have a Atrix 4G which also is on CM11, and like you guys on the Defy, has a bigpart mod. For us to downgrade, its flash an old recovery, boot to recovery, factory reset, wipe all partitions (system, data, cache, boot (that should be the ones you have too)), flash desired ROM/restore backup. Not sure if that will work for you, but its worth a shot. If it doesn't work, i'd try sbf'ing (someone posted an sbf lately if i remember correctly
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse