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.
Related
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
I have the 2ndbootin thing, the stock moto recovery, and never ending boot animation. If I wipe the cache using the moto recovery, I can get it past the boot loop and then it gets stuck in "android is upgrading". I figured I can flash a custom recovery using RSD, the problem is I don't know, and googling the problem didn't came up with useful solutions. My top priority is to get the phone working again, and that it will have the data is got now (though I did a backup of the data before starting this failed upgrade).
Also relevant:
http://forum.xda-developers.com/showthread.php?p=48088388#post48088388
Achiron said:
I have the 2ndbootin thing, the stock moto recovery, and never ending boot animation. If I wipe the cache using the moto recovery, I can get it past the boot loop and then it gets stuck in "android is upgrading". I figured I can flash a custom recovery using RSD, the problem is I don't know, and googling the problem didn't came up with useful solutions. My top priority is to get the phone working again, and that it will have the data is got now (though I did a backup of the data before starting this failed upgrade).
Click to expand...
Click to collapse
Man, you need to start again from stock.
Install the stock SBF using RSD, root, install 2ndinit, install CM10, install CM10.2, install the updaterecovery.zip package, reboot (don't wipe), then install CM11 and Gapps. It worked for me, it worked for other defy users, it will work for you.
leandrolutz said:
Man, you need to start again from stock.
Install the stock SBF using RSD, root, install 2ndinit, install CM10, install CM10.2, install the updaterecovery.zip package, reboot (don't wipe), then install CM11 and Gapps. It worked for me, it worked for other defy users, it will work for you.
Click to expand...
Click to collapse
I gave up and went to the RSD, downloaded what I thought was he right SBF, flashed it in RSD, and after it finished the device is BRICKED. No lights, it doesn't turn on. :crying:
Achiron said:
I gave up and went to the RSD, downloaded what I thought was he right SBF, flashed it in RSD, and after it finished the device is BRICKED. No lights, it doesn't turn on. :crying:
Click to expand...
Click to collapse
The defy doesn't really brick, because the bootloader is locked.
It may be no charge in the battery...
You need to use an external charger, or McGyver method, because the defy won't charge by the usb or wall charger...
After you make it, try RSD again, and choose the right SBF, from your carrier.
Hope it helps... gogogo defy :victory:
So i was rooting my One Plus 2. While flashing the nee ROM i accidentally cleared the dalvik cache and the Internal storage too. this cleared my old ROM as well as new ROM. The phone went into bootloop. I somehow managed to flash OP2 Stock ROM
But now the problem is I cant reboot my phone into recovery, I tried flashing a new recovery but nothing happens. I lost my Volte update.
PLEASE HELP ?
atharva96 said:
So i was rooting my One Plus 2. While flashing the nee ROM i accidentally cleared the dalvik cache and the Internal storage too. this cleared my old ROM as well as new ROM. The phone went into bootloop. I somehow managed to flash OP2 Stock ROM
But now the problem is I cant reboot my phone into recovery, I tried flashing a new recovery but nothing happens. I lost my Volte update.
PLEASE HELP ?
Click to expand...
Click to collapse
If u have stock recovery then u shud load bootloader (fastboot) Redo the root procedure from scratch ,problem solbed ..
Sent from my ONE A2003 using Tapatalk
Hi. Can you please provide a link for the stock Rom? Did you copy it to your phone by sideload? Will it work on CM Recovery with unlocked bootloader? Mine always boot to CM recovery everytime I power on my phone.
Thank you!