So, I converted my Blade from gen 1 to gen 2, and now it will only ever boot into recovery. I have an update.zip on my sd card that I am trying to apply, but it just hangs on the same screen.
Is there anything I can do?
edit: I managed to run the update.zip (I used the stock orange ROM) but now it's just hanging on the green android.
edit2: Another update, now I can't access clockwork recovery at all.
edit3: Yep, another update. Through the method outlined here I managed to get it back to recovery. I tried to install Swedish Springs but it still boots into ClockworkMod Recovery.
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 ve done dozens of flashing with my Sony and Samsung phones with no problem. Today i decided to flash something fresh on my acer a500 tab. I did my first mistake Please help cause im reading threads for 3 hours now and i dont know how to proceed.
Heres the story:
I was on stock ics 4.0.3 rooted. I used successfully the AfterOTA tool and flashed Bootloader ics v3.14.8 + Recovery Ra v3.1.7 That gave me the Skrilacs Recovery V8.
Then i did all the usual wipes and flashed successfully RE-FLEX XX 40.4 Rom. After the first boot i noticed that my internal storage wasnt empty. It gave me only 14gb free. There were still stuff in like photos, some music and apps remainings. I desided to wipe again and reinstall the rom. I did it a couple of times and i got the same result (internal storage was still with the same stuff).
On my last try to install the rom again it stucked on rom booting screen (bootloop). I can still get into CWM but cant find a solution.
Thanks in advance for any help..
Update: just managed to get it boot back on stock. My heart is back to its place now.
Thanks
After hours of reading in this forum and testing a lot of possible solutions my x5 still doesn`t work.
Some days ago i had installed the 4.2.2 CM10-Rom. Today i want back to Aurora and i make the mistake to format boot in CWM Recovery 5.5.04
Tried to boot but only a bluescreen on the phone. I tried to install dload with external sd. (gingerbread 528). Update Step 1 & 2 were sucessfull, but on reboot the "firework"-logo loads again and again. CWM Recovery was now away and the original E3 was as Recovery. With the 528 it was possible to do pink screen and i replace original recovery.img with the 5.5.04 recovery.img. This works and i tried to install aurora. Installation is sucessful but on reboot it stands on the first huawei logo.
Then i remember that i had to install a new partition to use 4.2.2. With CWM Recovery i installed the original partition and tried again to install Aurora. Did not work, phone stands on Huawei Logo.
Where is my problem? What should i do to use my phone again?
Many thanks!
Update 1: Phone boots! I`ve installed this rom U8800V100R001C00B517G001 (Beta1.0)(Overseas Normal)(Gingerbread) from pinkscreen without battery. This ist the first rom which boots.
What should i do now to com back to Aurora?
Update 2: Everything is fine! Had to root again. Then install CWM Recovery. Then install Aurora. I`m happy now!
Wow. Sorry I'm late. It looks like you've already solved your problem.
Hi,
Guys I need your help on this one.
I sold my A500 almost a year ago to a friend of mine. At that time I flashed it with a HC ROM and Recovery 1.3.4.
Last week the new owner of the tabled asked me for help updating the ROM to JB. Since now I use a Samsung Galaxy I completely forgot on the correct procedures to update the Acer A500. I simply downloaded a 4.2.2 Rom and tried to flash it on recovery mode.
After that I'm stuck with an endless loop. The tabled boots, pass the Acer logo, shows the ROM logo screen and than boot again.
Since I can still acess the recovery screen (it still shows 1.3.4 recovery) I tried flashing other ROMs with no sucess. Every room that uses the Aurora installer freezes as soons as Aurora Installer message shows on the screen. So I wasn`t able to flash a new Rom or a new Recovery (since all the Roms and recovery that I have found uses the Autora installer).
I also tried to install an older room (Tried the Lightspeed 2.1 ROM) and although I was able to flash it and reboot from recovery, it stops on the boot screen after that (I waited for 4 hours).
Can you guys help me with this one? Also, do you guys know if I can install a new Recovery using Odin?
Thanks
Anyone?
Maybe you should try flashing stock rom. Download 》rename it to update.zip》install from sd card or use EUU roms.
poslato sa elmag radija