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 ?
Related
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 defy plus .2.3.6 rooted with 2ndinit recovery.
every ROM I've tried to flash makes the phone stuck in bootloader menu, so i had to flash SBF again.
am i do something wrong? I've flashed a lot of roms on defy mb525, and everything worked fine.
thanks and sorry for my terrible english.
Sow now you are stuck in bootloop or you can not flash a custom rom?
I just flash SBF and go back to stock rom.
try wiping data in stock recovery .
(if you access it)
No access to recovery. boot right to the bootloader.
Reply!
Firstly is your defy rooted? If yes, install 2ndint and go to recovery by switching off your phone and press volume+ and power on button.
The problem you are facing is because you are not clearing cache before flashing a custom rom. Happened to me once so i know! Follow this procedure to the line and you should be fine!
http://forum.xda-developers.com/showthread.php?t=1663613
Hmmmmm
What bootloader you have? I think... v7
Teoretically you can use any 2.3.6 ROM
Yup, V7.
The only rom I was able to install it is CM9.
I'd tried this:http://forum.xda-developers.com/showthread.php?t=1667536 with the same results.
Hi there,
I tried to go back from CM10.1 to CM7.2. I used Aroma Wiper to format to EXT3. Then I flashed CM7.2 and according to Recovery everything was okay. On boot attempt the phone keept stucking on the red Motorola logo. I couldn't access CWM anymore and had to flash JORDN_U3_97.21.51 via RSD Lite. I rooted the phone and installed 2ndInit.
I tried installing several CM7 mods. But they all keept stucking on Motorola logo. I decided to stay with CM10 then. When trying to flash CM10 I received following message (please see attachment)
symlink:some symlinks failed
E:Error in /sdcard/cm-10.1-20130709-NIGHTLY-mb520.zip
(status7)
Installation aborted.
What can I do to flash CM again. Thanks for any suggestions.
Regards
dutss
dutss said:
Hi there,
I tried to go back from CM10.1 to CM7.2. I used Aroma Wiper to format to EXT3. Then I flashed CM7.2 and according to Recovery everything was okay. On boot attempt the phone keept stucking on the red Motorola logo. I couldn't access CWM anymore and had to flash JORDN_U3_97.21.51 via RSD Lite. I rooted the phone and installed 2ndInit.
I tried installing several CM7 mods. But they all keept stucking on Motorola logo. I decided to stay with CM10 then. When trying to flash CM10 I received following message (please see attachment)
symlink:some symlinks failed
E:Error in /sdcard/cm-10.1-20130709-NIGHTLY-mb520.zip
(status7)
Installation aborted.
What can I do to flash CM again. Thanks for any suggestions.
Regards
dutss
Click to expand...
Click to collapse
If your phone is MB525/526, then why are you trying a MB520 ROM?
entelsp essence
hotdog125 said:
If your phone is MB525/526, then why are you trying a MB520 ROM?
Click to expand...
Click to collapse
You are right. I downloaded the wrong file. I downloaded cm-10.1-20130709-NIGHTLY_v2-mb526 but I get the same error message (I made another screenshot).
dutss said:
You are right. I downloaded the wrong file. I downloaded cm-10.1-20130709-NIGHTLY_v2-mb526 but I get the same error message (I made another screenshot).
Click to expand...
Click to collapse
Try starting again from SBF, root, 2ndinit. Then try installing.
If it still doesn't work, download an old CM10 build (maybe November/December builds), flash it, then flash dual recovery v3 (in the development section) and then try flashing the latest build.
Hi,
I installed this SBF using RSDLite: DEFYPLUS_U3_4.5.1-134_DFP-231_ND_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTNORD_P011_A013_Service1FF.sbf.gz, (GB Nordic SBF).
Then installed Framaroot 1.4.1, rooted the phone using Gimli exploit, said root successful.
Then installed 2ndInit 2.4, said install successful.
Rebooted two times, went to custom recovery, everything seemed ok. Wiped data/cache/system using AromaWiper.
Then installed the latest fixed CM7 (cm-7-20130710-UNOFFICIAL-jordan_plus-signed.zip).
Upon reboot, the phone is stuck in bootloop. I'm still able to enter the custom recovery, so I guess 2ndinit worked, but installing the aforementioned CM7 results in bootloop.
I tried scanning through the All-in-One guide here, but couldn't really pinpoint what exactly is my problem. Could someone help, what would be the steps to take to get my phone running CM7? I'm able to flash SBF and at least seemingly flash zips via custom recovery, but I suspect there is something wrong in there since the flashed zips don't seem to work.
EDIT: If anyone can help? Is it that 2ndinit was installed badly? Reinstall from SBF, re-root, pay more attention to 2ndinit install?
In the All-in-One guide I find some problems with 2ndInit and talk about GoAPK SystemRecovery? Would that help?
Hi,
I have Defy MB525 and I currently flashed JORDN_U3_97.21.51.sbf.
I read most of the guides here, but I'm still in the loop - cannot get working TWRP to install latest CM11.
I flashed Recovery BootStrap v4 (TWRP) but when the phone starts booting, it ends up with the following screen and I cannot go foward.
It doesn't matter, what I choose (Recovery or continue.). When I press the menu button (to choose Recovery), nothing happen, till the 3rd press - than the display goes black and thats all .
Maybe its related to the bootloader version, which is 09.10 or is there any prerequisite to successfully install TWRP?
Any idea where could be the problem or what I'm doing wrong?
Thank you in advance
Issue fixed
Even that nobody replied, I finally fixed this issue, so I will post here the solution, which may help to anybody else:
I finally found the sbf file, which is working with my Defy: http://motoroladefyall.nortol.info/motorola/joe30_236_DFP-231_Magyaritasa/DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf.gz
After flashing this, the phone finally booted and saying its MB526, but never mind...
Then I rooted the phone with Framaroot app and installed the TWRP recovery (bootstrap). This time SuperUser was asking for root permission, so I granted it, flashing recovery was finished and the phone was rebooted.
Then the recovery was finally working, so I flashed the resize.zip, latest CM11 and minimal GAPPS.
And hurray, my Defy is finally running with the latest KK