I've been having problems with Fresh Rom not working right so I decided to try CM7, the newest nightly the other day which would have been number 12.
I flashed that then I flashed the "Google Apps" and poof, boot loop.
The phone would boot, I'd get to the screen with the Android guy on it that I think is a configuration screen for the Google Apps, and it would boot loop before I could do anything.
Thoughts?
This was on a fresh install of CM7 Nightly.
Try it again, but this time, do one thing at a time.
Wipe everything...TWICE.
Then load CM7, wait and let it boot up first time without gapps- then flash gapps.
Is it the Gingerbread Gapps?
Is it the NEWEST Gapps? The newest nightlies need the 3/7 Gapps.
Hi,
I am trying to put CM on my Defy+... and am having issues actually installing them thru 2ndInit.
It's 'stock' rom is Gingerbread 2.3.6 and rooted using SuperOneClick.
If I install the 'stable' version of 2ndInit (0.6), in the recovery when trying to flash the rom (and indeed when trying to clear cache), it returns errors relating to /tmp/
When trying to install the ROM it says: E: can't make /tmp/update_binary
and the install fails.
So, then I try the latest version of 2ndInit (v1.something), and in recovery, it doesn't error like this anymore - it seems to install CM sucessfully, with no error reports.
However then on reboot, it shows the M logo very briefly and then goes to Bootloader screen with the error:
Bootloader
09.10
Err:A5,70,00,0023
From here I cannot access custom recovery and stock recovery doesn't help, so I have to use RSD Lite with phone connected on this 'bootloader' screen and flash a stock SPF to start again. (note, I have only found one stock SPF which will actually work this way, which again is 2.3.6, Defy+ with Blur)
I have tried this with CM7.1 Jordan, CM7.1 Defy and also CM9 Defy+.
During the CM9 installation, I installed the CM9 kernel (2.3.3).
None make any difference, always the same issue.
The bootloader error makes me think CM (7 or 9) need a different bootloader version to that one the phone from stock... but I know very little (nothing) about kernels/bootloaders...
And I have no idea why on 2ndint v0.6 the /tmp/update_binary issue happens -- i've seen a fair few people have similar problems with no (afaik) solution (other than a suggestion to try 2ndint latest version which I did and resulted in bootloader error...)
Anything else worth trying would be most appreciated!
Is there an option to (somehow) obtain a Nandroid backup of someone's working CM on a defy+ and install that from 2ndInit recovery? Would that work?
Thanks
Rob
I have the exact same problem you have. Been banging my head against this thing for 3 days without a solution...
You have to install latest 2nd init from here: http://forum.xda-developers.com/showthread.php?t=1032212.
Follow instructions (like reboot twice...). Then flash a Defy+ rom without kernel. The CM7.2 DEFY+ nightly's don't contain the kernel so you won't have a problem. You can find a link in the first post of CM7 threat.
To get everything working, you might want to check the "100% battery and ..." threat in the Dev section.
For CM9, I thing you just need to install the latest nightly on gb kernel, don't know this one. If you search a bit, you'll find everything.
Yeah，I have the same question that drived me to die~！
rjbathgate said:
Hi,
I am trying to put CM on my Defy+... and am having issues actually installing them thru 2ndInit.
It's 'stock' rom is Gingerbread 2.3.6 and rooted using SuperOneClick.
If I install the 'stable' version of 2ndInit (0.6), in the recovery when trying to flash the rom (and indeed when trying to clear cache), it returns errors relating to /tmp/
When trying to install the ROM it says: E: can't make /tmp/update_binary
and the install fails.
So, then I try the latest version of 2ndInit (v1.something), and in recovery, it doesn't error like this anymore - it seems to install CM sucessfully, with no error reports.
However then on reboot, it shows the M logo very briefly and then goes to Bootloader screen with the error:
Bootloader
09.10
Err:A5,70,00,0023
From here I cannot access custom recovery and stock recovery doesn't help, so I have to use RSD Lite with phone connected on this 'bootloader' screen and flash a stock SPF to start again. (note, I have only found one stock SPF which will actually work this way, which again is 2.3.6, Defy+ with Blur)
I have tried this with CM7.1 Jordan, CM7.1 Defy and also CM9 Defy+.
During the CM9 installation, I installed the CM9 kernel (2.3.3).
None make any difference, always the same issue.
The bootloader error makes me think CM (7 or 9) need a different bootloader version to that one the phone from stock... but I know very little (nothing) about kernels/bootloaders...
And I have no idea why on 2ndint v0.6 the /tmp/update_binary issue happens -- i've seen a fair few people have similar problems with no (afaik) solution (other than a suggestion to try 2ndint latest version which I did and resulted in bootloader error...)
Anything else worth trying would be most appreciated!
Is there an option to (somehow) obtain a Nandroid backup of someone's working CM on a defy+ and install that from 2ndInit recovery? Would that work?
Thanks
Rob
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1382284
u will have to flash stock sbf file using rsdlite.it worked for me twice
check this link for sbf file of ur build
http://forum.xda-developers.com/showthread.php?t=966537
then download version 2.0 of 2nd init and select install 1.0.7.this should work
Stuck in bootloop with every os in install
rjbathgate said:
Hi,
I am trying to put CM on my Defy+... and am having issues actually installing them thru 2ndInit.
It's 'stock' rom is Gingerbread 2.3.6 and rooted using SuperOneClick.
If I install the 'stable' version of 2ndInit (0.6), in the recovery when trying to flash the rom (and indeed when trying to clear cache), it returns errors relating to /tmp/
When trying to install the ROM it says: E: can't make /tmp/update_binary
and the install fails.
So, then I try the latest version of 2ndInit (v1.something), and in recovery, it doesn't error like this anymore - it seems to install CM sucessfully, with no error reports.
However then on reboot, it shows the M logo very briefly and then goes to Bootloader screen with the error:
Bootloader
09.10
Err:A5,70,00,0023
From here I cannot access custom recovery and stock recovery doesn't help, so I have to use RSD Lite with phone connected on this 'bootloader' screen and flash a stock SPF to start again. (note, I have only found one stock SPF which will actually work this way, which again is 2.3.6, Defy+ with Blur)
I have tried this with CM7.1 Jordan, CM7.1 Defy and also CM9 Defy+.
During the CM9 installation, I installed the CM9 kernel (2.3.3).
None make any difference, always the same issue.
The bootloader error makes me think CM (7 or 9) need a different bootloader version to that one the phone from stock... but I know very little (nothing) about kernels/bootloaders...
And I have no idea why on 2ndint v0.6 the /tmp/update_binary issue happens -- i've seen a fair few people have similar problems with no (afaik) solution (other than a suggestion to try 2ndint latest version which I did and resulted in bootloader error...)
Anything else worth trying would be most appreciated!
Is there an option to (somehow) obtain a Nandroid backup of someone's working CM on a defy+ and install that from 2ndInit recovery? Would that work?
Thanks
Rob
Click to expand...
Click to collapse
I have the same problem as you .. but in "MOTOROLA DEFY" now to break this bootloop .. i flash this particular SBF > JORDN_U3_97.21.51.rar to work again .. n following the procedure, i tried to upgrade it with os {CM7.1 or CM 9 120416, 120613 / CM10 120904, 201220912, 20924, 20130307} i ended up in Bootloop .. the recovery software i installed is 2ndinit 2.0 and stable version 0.6 .. it works without error. The procedure i use is in recovery mode: first wipe data/ factory reset > wipe cache > wipe delvik cache .. then install the zip file .. but when i restart .. i stuck in the M" Motorola" GoMgle" logo please help me to provide .. stable sbf file and OS GB rom to flash on my defy ?
Hi! I just changed my rom from MIUI to CM9(ICS, 4.0.3) but after i install using recovery mod it stays on the booting screens and doesn't want to start normally. I noticed that clockwork mod has dissapeared and it will only show the "stock" recovery. Is there any chance to make my current rom work? or can I install another rom using the stock recovery?
Please help
Looks like i managed to make the phone work by full wiping from custom recovery. I'll definitely go back to CM 7.1...
kernel
i think u'll need to flash the cm9 kernel for CM9 work. otherwise flash the cm9 builds from Epsylon or Quarx - http://forum.xda-developers.com/showthread.php?t=1432100
Can someone explain why this happens:
1. I flash CM9 nightly or latest release
2. Phone goes into boot loop
3. I power the phone up into the yellow boot loader screen and flash the Semaphore ICS kernel with Heimdall
4. The phone boots and runs OK
Why does the phone go into a boot loop until I flash the Semaphore kernel? How can I stop this behaviour?
Sounds like a big error... don't sound good. You flashing cm9 or cm10? nightly builds are really good. i recommend getting a cm10 nightly build and try that. otherwise, try and find a way of flashing roms and kernels a different way...
Hey guys,
As I wrote in the title I ran into a problem when installing the new CM11 nightly build from Quarx on my Defy. Here's what I did:
1) Downloaded the recovery update: http://defy.bytekiste.de/cm11-nightly-defy+/update-recovery.zip
2) Downloaded this CM11 nightly build: http://quarx2k.ru/roms/defy-cm11.0/cm-11-20140501-NIGHTLY-mb526.zip
3) Rebooted into recovery and installed the recovery update. The install seems to have finished without problems, although after another reboot my recovery still read as "JB Recovery v5.7.0-jordan".
4) Did a data and cache wipe.
5) Tried installing CM11, but the installation was aborted by a "status 0" error right after the "installing update..." part.
What am I doing wrong? I assume this has something to do with the recovery update, but since as far as I can tell it was successfully installed I don't know what could I do to fix it.
Now that I got time I started reading Quarx's CM11 thread and apparently in these cases installing CM10.2 first may help (I was using CM10), as it also updates the recovery, which is TWRP in the case of the as of now latest CM10.2 nightly. After I did this I tried installing CM11 again and this time the install went without a hitch. So if anyone else runs into this issue try this first.
For the next time remember that you've to reboot the device after installing that recovery in order to TWRP do the actualization
MaicolS said:
For the next time remember that you've to reboot the device after installing that recovery in order to TWRP do the actualization
Click to expand...
Click to collapse
I did restart my phone after installing the recovery update, I just forgot to mention it.
Since my last post I realized that the problem was that the CM10 nightly build I used before still came with the CWM recovery, not with TWRP. The reason is that some of Quarx's old builds didn't play nice with TWRP at the time. Since Quarx didn't explicitly say in his thread that the recovery update was for TWRP I just assumed that it was for his old builds that came with CWM. That doesn't seem to be the case however.
Chawitsch said:
Now that I got time I started reading Quarx's CM11 thread and apparently in these cases installing CM10.2 first may help (I was using CM10), as it also updates the recovery, which is TWRP in the case of the as of now latest CM10.2 nightly. After I did this I tried installing CM11 again and this time the install went without a hitch. So if anyone else runs into this issue try this first.
Click to expand...
Click to collapse
Easier method: just flash defy_twrp_recovery_2.6.3.0.zip, as explained in the installation guide.
Thanks for the link Proverbs, I'll do that the next time I'll need to update TWRP. Like I said, I didn't realize that Quarx's recovery update was for TWRP. If I did, I would have flashed TWRP separately and then CM11. What matters is that everything turned out OK in the end.