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 Guys,
I own a defy +,
Here are some details
Android Version : 2.3.6
Kernel Version : 2.6.32.9-gbdd614e
Problem :
When i try i install any custom roms, i am getting boot loader err. But i was successful in installing CM7 but i am unable unable to install other custom roms.
Actually the roms gets installed but when i try to boot for the first time i always get bootloader error.
Did u Flash Kernel?
make fixed SBF From Ur Stock SBF.(moto andriod depacker-Delet CG31 And CG39)
and flash Fixed SBF With RsdLite.
Yes, it looks like sbf mismatch. See this guide for defy+. You can also try to flash a nandroid backup like this one
Thanks for your help guys, but i understand very little.
I have a nandroid backup, whenever i get bootloader error,i usually flash a Stock SBF then i will restore my phone using the nandroid backup.
Can you guys guide me how to install CM9 on my defy plus.
I flashed CM9 rom and i have also flashed CM9 kernel for gb but i am still getting bootloader error. Where i have went wrong
What is mean by SBF mismatch??
flash stock SBF.
Root
flash CM9 For DEFY+ .
DONT FLASH ANY KERNEL.
Just follow this instructions carefully. Common mistake is that you forget to wipe cache and data. So, wipe cache and data, and reboot. First boot takes longer (about 10 minutes). Good luck.
Thanks guys, i successfully installed CM9.
But , can one suggest me ROM for my defy plus, which gives good performance and also stable. ??
hi
i have a green lens defy.
i have already little experience on flashing cyanogen mod 7 and mod 9 and mod 10.
previously i have rooted stock, installed 2ndint and flashed cm7 over the stock like this..
bootmenu>recovery>custom recovery> factory reset>install zip>wipe cache>wipe dalvik cache>reboot.
i did not take the "backup all"(what u call it as NANDROID backup, isn't it?) of stock rom....ooops.
i did the same procedure to install cm9 and cm10..but this time i took backup of cm7 during cm9 installation and cm9 during cm10 intallation.
i did this all in custom recovery only.
In the bootmenu there were other options called stock recovery and stable recovery along with custom recovery.
and within custom recovery there was motorola recovery in advanced option.. But non of them brought the stock rom back on my device.
always shows exclamation in triangle and a androbot.
So i have finally tried the RSDlite and flashed my stock sbf.
AND NOW i am again on my way to install cm10 for defy. and this time with no mistakes....Please help me to do this.
0.why are the options stock recovery and motorola recovery not working....?what are they actually..when to enter/click that recoveries??
1.How do i take backup of stock so that i can go back at anytime?
2.is backing up stock rom also done through custom recovery and backup all? if that so then why are stock recovery and stable recovery and motorola recovery options present there?
3.did i install correctly first time?
Thanks for all your answers,
prax31 said:
hi
i have a green lens defy.
i have already little experience on flashing cyanogen mod 7 and mod 9 and mod 10.
previously i have rooted stock, installed 2ndint and flashed cm7 over the stock like this..
bootmenu>recovery>custom recovery> factory reset>install zip>wipe cache>wipe dalvik cache>reboot.
i did not take the "backup all"(what u call it as NANDROID backup, isn't it?) of stock rom....ooops.
i did the same procedure to install cm9 and cm10..but this time i took backup of cm7 during cm9 installation and cm9 during cm10 intallation.
i did this all in custom recovery only.
In the bootmenu there were other options called stock recovery and stable recovery along with custom recovery.
and within custom recovery there was motorola recovery in advanced option.. But non of them brought the stock rom back on my device.
always shows exclamation in triangle and a androbot.
So i have finally tried the RSDlite and flashed my stock sbf.
AND NOW i am again on my way to install cm10 for defy. and this time with no mistakes....Please help me to do this.
0.why are the options stock recovery and motorola recovery not working....?what are they actually..when to enter/click that recoveries??
1.How do i take backup of stock so that i can go back at anytime?
2.is backing up stock rom also done through custom recovery and backup all? if that so then why are stock recovery and stable recovery and motorola recovery options present there?
3.did i install correctly first time?
Thanks for all your answers,
Click to expand...
Click to collapse
Yes, you are very confused! :silly: You know, when you install a custom rom it totally replaces your stock rom. The stock recovery is not there to recover your stock rom/restore it (where would it restore it from?? I'll have to disappoint you, but your phone is not magic!). The stock recovery can only wipe user data and install updates by Motorola onto an already existing system! You will never be able to restore your system to its original state if you don't have a backup or some idea what retail version you were on. But you'll definitely find a similar sbf over at droid developers or Walter's sbf thread.
When you see the exclamation mark with the cute green guy, you have to press vol+ and vol- together to reveal the stock recovery.
Motorola recovery = stock recovery = the recovery made by Motorola. You can acces it buy pressing vol- while powering up, through bootmenu>recovery>stock/motorola recovery or bootmenu>recovery>custom/stable recovery>advanced>motorola recovery
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...
Ok so i want to put CM rom onto this S2 I have but trying to put a safe kernel on first so dont brick it with that wipe bug.
Problem is whenever I flash dream kernel, skfire etc. the device doesnt boot, only boots again when I flash cf-root back.
Its ICS 4.0.3
I am flashing via install frim zip file on CWM as instructions arent given on the kernel threads.
siyah flashed via odin, the logo appears very briefly at boot then black, nothing.
CWM with siyah logo in background works.
Ok I flashed cm9 now anyway.
It was confusing to me but incase anyone else is confused in the same way, cf-root is still safe as long as the stock isnt 4.0.4. I thought its possible cf-root used a 4.0.4 kernel on 4.0.3 and so was heistant.
I got no idea why none of the custom kernels would boot tho so that still has nme curious, CM has booted fine.