Related
I bricked my phone while installing Jakebites Mod and was wondering what do I do next?? I was running the lastest CM7 GB nightly (112) and installed v12 jakebites mod and then my phone got stuck in a bootloop. I'm still not sure why my phone got stuck in a bootloop.
My phone settings said I was on Android 2.3.7. Which version do I SBF back to??
Also, the last nightly I was on was CM7 nightly 78, which was froyo. I wiped cache/dalvik and directly flashed 112 without any problems. I never did any OTA GB update or anything when I was on 2.3.340. Did I skip a crucial step??
deviations said:
I bricked my phone while installing Jakebites Mod and was wondering what do I do next?? I was running the lastest CM7 GB nightly (112) and installed v12 jakebites mod and then my phone got stuck in a bootloop. I'm still not sure why my phone got stuck in a bootloop.
My phone settings said I was on Android 2.3.7. Which version do I SBF back to??
Also, the last nightly I was on was CM7 nightly 78, which was froyo. I wiped cache/dalvik and directly flashed 112 without any problems. I never did any OTA GB update or anything when I was on 2.3.340. Did I skip a crucial step??
Click to expand...
Click to collapse
Did you wipe data/factory reset? If not do that first then wipe cache data partition, then dalvik.
Also sometimes you can go into a bootloop if you have your phone connected to a charger while installing a new rom and then unplug it. If you didn't do this then just try the above step.
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 come with a maybe unusual problem. Every other rom works with me Defy (T-mobile) except the CMX by Quarx. I tried different versions (6-8), and all of them give this:
-Wipe factory, cache, dalvik
-Install CM10, Gapps
-Reboot
-Phone hangs with black screen with the red led (which is normal at 2nd boot right?)
After that, if I want to downgrade to CM9, or CM7.2 I can't wipe dalvik cache. When I click on the option in CWM, it does not give me the no no no no yes no no options. Nothing happens. The screen refreshes itself like I just entered the advanced menu in CWM. I have to restore Éclair, than go to Froyo, then to Gingerbread etc. with RSD lite, then reroot, all of the stuff to get my phone working after this. I've got tired of this, and i don't know why this bug happens. I followed the instructions well -as far as i know-. I tried to install it from CM7.2, and from CM9.
The strange thing is, if it means something: It looks like my phone is losing permission for system (?), because if i try to revert back from CM10 to CM9, and reboot, it gives: Error. Encryption unsuccessful for CM9, and CM7 does not even boot. If i reboot to CWM, I can't wipe dalvik cache again. What could cause the glitch in not being able to wipe dalvik cache?
My previous CM7.2 is Euroskank gigglebread, which is a pretty good ROM.
BAYER camera, MB525.
gyorgyszemok said:
Hi,
I come with a maybe unusual problem. Every other rom works with me Defy (T-mobile) except the CMX by Quarx. I tried different versions (6-8), and all of them give this:
-Wipe factory, cache, dalvik
-Install CM10, Gapps
-Reboot
-Phone hangs with black screen with the red led (which is normal at 2nd boot right?)
After that, if I want to downgrade to CM9, or CM7.2 I can't wipe dalvik cache. When I click on the option in CWM, it does not give me the no no no no yes no no options. Nothing happens. The screen refreshes itself like I just entered the advanced menu in CWM. I have to restore Éclair, than go to Froyo, then to Gingerbread etc. with RSD lite, then reroot, all of the stuff to get my phone working after this. I've got tired of this, and i don't know why this bug happens. I followed the instructions well -as far as i know-. I tried to install it from CM7.2, and from CM9.
The strange thing is, if it means something: It looks like my phone is losing permission for system (?), because if i try to revert back from CM10 to CM9, and reboot, it gives: Error. Encryption unsuccessful for CM9, and CM7 does not even boot. If i reboot to CWM, I can't wipe dalvik cache again. What could cause the glitch in not being able to wipe dalvik cache?
My previous CM7.2 is Euroskank gigglebread, which is a pretty good ROM.
BAYER camera, MB525.
Click to expand...
Click to collapse
Hi Buddy,
I had the same problem while trying CM10, The only solution worked for me is to flash back to Stock ROM. Once you have the stock ROM back.. You can root it again.. with CM7 or 9..
I should work.. as It worked for me.. I am on CM9 on my moto defy plus
Cheers
Smit
Because no one can count what you has done in the device I suggest to start from beginning and in correct order. (flash sbf., root, install 2ndinit....
gyorgyszemok said:
Hi,
I come with a maybe unusual problem. Every other rom works with me Defy (T-mobile) except the CMX by Quarx. I tried different versions (6-8), and all of them give this:
-Wipe factory, cache, dalvik
-Install CM10, Gapps
-Reboot
-Phone hangs with black screen with the red led (which is normal at 2nd boot right?)
After that, if I want to downgrade to CM9, or CM7.2 I can't wipe dalvik cache. When I click on the option in CWM, it does not give me the no no no no yes no no options. Nothing happens. The screen refreshes itself like I just entered the advanced menu in CWM. I have to restore Éclair, than go to Froyo, then to Gingerbread etc. with RSD lite, then reroot, all of the stuff to get my phone working after this. I've got tired of this, and i don't know why this bug happens. I followed the instructions well -as far as i know-. I tried to install it from CM7.2, and from CM9.
The strange thing is, if it means something: It looks like my phone is losing permission for system (?), because if i try to revert back from CM10 to CM9, and reboot, it gives: Error. Encryption unsuccessful for CM9, and CM7 does not even boot. If i reboot to CWM, I can't wipe dalvik cache again. What could cause the glitch in not being able to wipe dalvik cache?
My previous CM7.2 is Euroskank gigglebread, which is a pretty good ROM.
BAYER camera, MB525.
Click to expand...
Click to collapse
Why do u flash eclair?..start from froyo 2.2 deblur sbf...
nilesg19 said:
Why do u flash eclair?..start from froyo 2.2 deblur sbf...
Click to expand...
Click to collapse
I flash Éclair when all fails, because if I flash Froyo with RSDLite over any newer ROM then Gingerbread the device goes bootloop and the rsdlite can't repair it, but with Éclair I can.. I'm still waiting for some answer about why can't I just simply flash CM10 over CM7 or CM9? Why does it gives me bootloop and red led freeze? It also loses permission to wipe dalvik cache, which, imo is a very important information, and someone probably knows why, but I don't..
So, Questions are here:
-Is it connected to BL version? (The redled freeze/bootloop with 2nd-boot CM10 only)
-How do I check BL version? (Now i have CM9 Epsylon, if it matters)
-How come the phone freezes on red led (2nd-boot) and restarts, when I had no problem installing any other ROM?
-What can cause 2nd-boot not to work?
-How can I roll back to Éclair, but not Froyo/ICS (stock froyo flash with RSD Lite -> gives bootloop, CM7 won't start/CM9 Encryption unsuccesful)
Notes:
-After failed CM10 installation I can't wipe Dalvik cache, reinstalling ( without flashing Éclair -> Froyo -> GB -> root etc.and CM7/CM9.) CM9 gives the "Encryption unsuccesful" error, CM7 won't start (ever), I still can't wipe Dalvik!
-Every other GB, ICS ROM except CM10 (JB) works perfectly fine
-I can only repair it with starting all over again from Éclair (an issue with something about you can't rollback from GB to Froyo cancels other options)
---
edit: no ideas so far?
I've been trying to upgrade from CM 7.2 to CM 10.{0,1,2}, but my phone keeps getting stuck with the red LED after the Motorola. My understanding is that this means that there is not a viable OS installed. When I flash the appropriate zip the recovery is updated (e.g., TWRP 2.5.0 is installed with CM 10.1). I've tried wiping cache, data, Dalvik cache before and after install, but it doesn't help.
Can anyone suggest what might be happening?
Here's the full story:
I've been running CM 7.2 for a long time and it's been great and stable. But, I saw that CM 10.2 was available a while ago and wanted to give it a try. I originally tried flashing straight to CM 10.2 from CM 7.2 but the installation aborted (status(0)). I posted on the CM 10.2 thread and _mak_V_ suggested that I needed to install TWRP or go through 10.1 first.
I installed Defy TWRP version 2.1.1 from the TeamWin webpage, but was still unable to install CM 10.2. Same problem, and I'm guessing that the recovery is still too old.
So, I decided to go through CM 10.1. I flashed this using TWRP 2.1.1 along with gapps-jb-20130812-signed.zip and the installation seemed to go smoothly. However, I was stuck at the red LED.
I reverted my TWRP backup to CM7.2 and then tried CM 10 with gapps-jb-20121011-signed.zip -- same thing.
To make sure I wasn't completely losing it I installed CM 9 which I tried before. This worked perfectly, but I still can't upgrade to CM10 or above.
Apologies if this question has been answered already. I'm sure that I'm missing something simple, but I've combed the Bravo and Defy threads and can't find anything to help. Can anyone suggest anything?
Thanks for your help!
still no answer?
sjbonner said:
I've been trying to upgrade from CM 7.2 to CM 10.{0,1,2}, but my phone keeps getting stuck with the red LED after the Motorola. My understanding is that this means that there is not a viable OS installed. When I flash the appropriate zip the recovery is updated (e.g., TWRP 2.5.0 is installed with CM 10.1). I've tried wiping cache, data, Dalvik cache before and after install, but it doesn't help.
Can anyone suggest what might be happening?
Here's the full story:
I've been running CM 7.2 for a long time and it's been great and stable. But, I saw that CM 10.2 was available a while ago and wanted to give it a try. I originally tried flashing straight to CM 10.2 from CM 7.2 but the installation aborted (status(0)). I posted on the CM 10.2 thread and _mak_V_ suggested that I needed to install TWRP or go through 10.1 first.
I installed Defy TWRP version 2.1.1 from the TeamWin webpage, but was still unable to install CM 10.2. Same problem, and I'm guessing that the recovery is still too old.
So, I decided to go through CM 10.1. I flashed this using TWRP 2.1.1 along with gapps-jb-20130812-signed.zip and the installation seemed to go smoothly. However, I was stuck at the red LED.
I reverted my TWRP backup to CM7.2 and then tried CM 10 with gapps-jb-20121011-signed.zip -- same thing.
To make sure I wasn't completely losing it I installed CM 9 which I tried before. This worked perfectly, but I still can't upgrade to CM10 or above.
Apologies if this question has been answered already. I'm sure that I'm missing something simple, but I've combed the Bravo and Defy threads and can't find anything to help. Can anyone suggest anything?
Thanks for your help!
Click to expand...
Click to collapse
Oc someone's going to tell you to use search or Google it but I'm not that person shortly I'm going to install cm10 on mine so I'll go through the steps and let you know what to do or might have happened I'll keep you posted.
just made the same mistake
Try updating the recovery and when you wipe you have to do it in ext3 if you want to revert to gingerbread and ext4 for jb as far as I know