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
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 awesome XDA dudes
I've searched the forums, and even posted in the basic QA section to no avail. I may have just missed it somewhere, but here is the issue.
Tablet will work fine in Lightspeed 4.8 ROM. No issue there. But, when I try to get into the recovery (power and volume down) I get "booting recovery kernel image," forever.
I recently changed from the Clockwork to TWRP recovery and that is when the recovery function would no longer load.
How can I get back to Clockwork or smililar so that I can put a different ROM on my tab?
Thanks in advance!
Tom
Fixed this problem, only to find another.
So, since my tablet would still function normally (aside from recovery) I downloaded the Acer Recovery Installer App. And this did what everything else failed to do. It installed Clockwork Mod and I was actually able to get into the recovery. Whew!
So I went to install Flex shockwave ROM but the install froze at the Aroma 2.56 stage...forever. Tried again unsuccessfully and gave up. I did properly wipe and format beforehand. I then tried installing CM10 Rom, same exact problem.
So, I used Acer Recovery installer and loaded the TWRP recovery. Here is where things get interesting. I booted into recovery, wiped data and caches, and tried to install the aforementioned ROMs. Each time, Aroma installer worked fine and I was presented with all the install options, all the bells and whistles. After completing my selections, I was prompted to reboot.....
And each time the tablet hangs on the Acer spalsh screen.
So now my problem is reversed. I have access to recovery, but no ROM. :crying:
SOLVED !!
tfbielawski said:
So, since my tablet would still function normally (aside from recovery) I downloaded the Acer Recovery Installer App. And this did what everything else failed to do. It installed Clockwork Mod and I was actually able to get into the recovery. Whew!
So I went to install Flex shockwave ROM but the install froze at the Aroma 2.56 stage...forever. Tried again unsuccessfully and gave up. I did properly wipe and format beforehand. I then tried installing CM10 Rom, same exact problem.
So, I used Acer Recovery installer and loaded the TWRP recovery. Here is where things get interesting. I booted into recovery, wiped data and caches, and tried to install the aforementioned ROMs. Each time, Aroma installer worked fine and I was presented with all the install options, all the bells and whistles. After completing my selections, I was prompted to reboot.....
And each time the tablet hangs on the Acer spalsh screen.
So now my problem is reversed. I have access to recovery, but no ROM. :crying:
Click to expand...
Click to collapse
Ok, so I had a working ROM but my recovery was fried. So, using Acer Recovery Installer I was able to get a working recovery going.
Then the next problem was that I could not get CM10 to install. When I realized I needed to flash the bootloader (and yes fellow noobs this is different than the recovery) I was unsuccessful.
I tried the automated route using the Blackthund3r app, but the process would just hang at Entering bootloader.
I tried the manual NVFlash route provided by Dibbs and it would get past this point and then hang.
So Dibbs (thanks dude) helped me out via email and suggested I download babsector.rar
After I extracted the rar file, I saw the A501 A.bat file and flashed it. This provided me with hope as it flashed the tablet and the screen atcually read "PASS." But, I wasn't done yet as I still could not install CM10. So, back to APX mode and back into the babsector rar folder. I flashed the Tab with A501 B.bat and followed that immediately with flashing the v8.bat file. In the V8.bet file I chose the Thor 1.7.3 recovery (as suggested by Dibbs and others) and WOOHOOO.....PASS on the tablet again.
Feeling ever more confident, I booted into recovery and flashed the CM10 Rom....SUCCESS!!!!!!!!!!!!!!!
If you are having trouble....don't give up. Thanks again for the help to Dibbs and OKAstro!!
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?
Hey guys,
As I wrote in the title I ran into a problem when installing the new CM11 nightly build from Quarx on my Defy. Here's what I did:
1) Downloaded the recovery update: http://defy.bytekiste.de/cm11-nightly-defy+/update-recovery.zip
2) Downloaded this CM11 nightly build: http://quarx2k.ru/roms/defy-cm11.0/cm-11-20140501-NIGHTLY-mb526.zip
3) Rebooted into recovery and installed the recovery update. The install seems to have finished without problems, although after another reboot my recovery still read as "JB Recovery v5.7.0-jordan".
4) Did a data and cache wipe.
5) Tried installing CM11, but the installation was aborted by a "status 0" error right after the "installing update..." part.
What am I doing wrong? I assume this has something to do with the recovery update, but since as far as I can tell it was successfully installed I don't know what could I do to fix it.
Now that I got time I started reading Quarx's CM11 thread and apparently in these cases installing CM10.2 first may help (I was using CM10), as it also updates the recovery, which is TWRP in the case of the as of now latest CM10.2 nightly. After I did this I tried installing CM11 again and this time the install went without a hitch. So if anyone else runs into this issue try this first.
For the next time remember that you've to reboot the device after installing that recovery in order to TWRP do the actualization
MaicolS said:
For the next time remember that you've to reboot the device after installing that recovery in order to TWRP do the actualization
Click to expand...
Click to collapse
I did restart my phone after installing the recovery update, I just forgot to mention it.
Since my last post I realized that the problem was that the CM10 nightly build I used before still came with the CWM recovery, not with TWRP. The reason is that some of Quarx's old builds didn't play nice with TWRP at the time. Since Quarx didn't explicitly say in his thread that the recovery update was for TWRP I just assumed that it was for his old builds that came with CWM. That doesn't seem to be the case however.
Chawitsch said:
Now that I got time I started reading Quarx's CM11 thread and apparently in these cases installing CM10.2 first may help (I was using CM10), as it also updates the recovery, which is TWRP in the case of the as of now latest CM10.2 nightly. After I did this I tried installing CM11 again and this time the install went without a hitch. So if anyone else runs into this issue try this first.
Click to expand...
Click to collapse
Easier method: just flash defy_twrp_recovery_2.6.3.0.zip, as explained in the installation guide.
Thanks for the link Proverbs, I'll do that the next time I'll need to update TWRP. Like I said, I didn't realize that Quarx's recovery update was for TWRP. If I did, I would have flashed TWRP separately and then CM11. What matters is that everything turned out OK in the end.
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Mmmh, strange, I did a factory installation (latest 5.1.1 from Google) and started the same thing from scratch ... and guess what... the system is booting fine now.
No idea why it did not work on my first attempt .
Regards, mistersixt.
mistersixt said:
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Click to expand...
Click to collapse
Same here. Running stock until today, wanted to see a different ROM, flashed TWRP 3.0.0, it refused to boot anything else. Tried to flash DU, then tried Chroma. Did a full wipe, then an advanced wipe selecting everything, then a full format, same thing. Installed TWRP 2.8.7, same thing. Finally installed latest stock, it is now booting, optimizing apps. I don't know if installing a custom rom will work or not yet.
Edit: Yeap, after flashing stock 5.1.1 and installing TWRP 3 again, the phone is now booting into DU.
First time I did a wipe with TWRP, it complained that it couldn't mount /data. Since this is the first time doing it, I assumed it was normal. After going through a full format, it didn't complain about data anymore, but it did complain about something to do with /dev/zero and another file under /dev/. I assume it was trying to dd /dev/zero to a file under /dev/ that didn't exist.
+1
Done the whole process from scratch again and worked like a charm
Hello, same story here.
First I:
- unlocked bootloader
- flashed TWRP (last version)
- flashed Chroma and Gapps
- reboot
=> I consistently rebooted on TWRP. No way to properly install the ROM. No error message at all.
Then I found this thread, and did as described:
- flashed the latest stock ROM
- flashed TWRP again (took me ages to manage to do this: TWRP would not install. I don't know how I finally did it, but at some point it suddenly worked. Probably a driver problem)
- flashed Chroma and Gapps again
Bingo, this time it worked! I don't know why it didn't work the first time. Could it be linked to the bootloader unlock thing?