Related
Hi all, :
Ive owned a defy since january, and after a lot of lurking here decided to take the plunge and have a play with it.
It was a stock unbranded uk defy with 2.51 blur rom, it rooted no problem with super one click, i then installed thi version of recovery : http://forum.xda-developers.com/showthread.php?t=875233
I then botted it into recovey and am now stuck in a bootloop.
I can access stock recovery (vol down and power) then touch bottom right of screen. I wiped cache and user data from here.
I can enter bootloader (vol up and power) and rsd lite can detect the phone.
My question is what is the easiest way to bring my phone back to life ? Im not sure if i need to flash sbf or rom.
Not to fussed about having the latest roms or mods, just a working phone before the battery gives out.
Thanks in advance, Sam
This happened to me a few days ago the way you should do it is download the 2.51 uk sbf file and flash it over using rsd lite and it should boot straight back Into the operating system and by the way how come that version did that to your phone I've installed recovery on 2 defys and they both worked
One more question did it boot up into recovery or not ?
No it didnt boot into recovery, just the boot loop. Any idea where i can get the uk sbf ? the link here seems to be dead
So you installed system recovery and then once again in the program installed it and then you clicked boot into recovery right ?
http://and-developers.com/sbf:defy
This website has all the sbfs your one should be the second on the list
RSD lite that one into your phone and it should be good to go
so.. is the usb debugging on?
when tap install recovery button, you should turn off usb debugging.
memz180 said:
So you installed system recovery and then once again in the program installed it and then you clicked boot into recovery right ?
http://and-developers.com/sbf:defy
This website has all the sbfs your one should be the second on the list
RSD lite that one into your phone and it should be good to go
Click to expand...
Click to collapse
mannn you save my life, i was looking for a stock rom from Latin America, and i got it from that link.
Thanks for the link memz180. Downloaded sbf and flashed sbf and phone is now working. Next question is what is the idiot proof way to install recovery ?
You installed the correct recovery just make sure you click into the program and install the system recovery within the program and then click on boot to recovery make sure i would make sure superuser is allowing it so check that out to and also as stated above turn off your debugging in development and then click on recovery see if it works.
Goodluck
Rerooted phone and reinstalled recovery, no problems this time. Thanks all for your help.
Sam
No problem here at xda we do our best to help our fellow android mates lol
Another Noob with an almost bricked Defy!
sammitch said:
Hi all, :
Ive owned a defy since january, and after a lot of lurking here decided to take the plunge and have a play with it.
It was a stock unbranded uk defy with 2.51 blur rom, it rooted no problem with super one click, i then installed thi version of recovery : http://forum.xda-developers.com/showthread.php?t=875233
I then botted it into recovey and am now stuck in a bootloop.
I can access stock recovery (vol down and power) then touch bottom right of screen. I wiped cache and user data from here.
I can enter bootloader (vol up and power) and rsd lite can detect the phone.
My question is what is the easiest way to bring my phone back to life ? Im not sure if i need to flash sbf or rom.
Not to fussed about having the latest roms or mods, just a working phone before the battery gives out.
Thanks in advance, Sam
Click to expand...
Click to collapse
I have the same problem on my T-mobile US branded Defy + when I try to flash the sbf file, on RSDlite It gives me this error
"Failed flashing process. Failed flashing process. Error processing flash file. (0x700F); phone conected"
What am I doing wrong? I tried RSDlite ver 4.9 and 5.0 to no avail! Please help! Thank you!
SOLVED!
NrikeCalderon said:
I have the same problem on my T-mobile US branded Defy + when I try to flash the sbf file, on RSDlite It gives me this error
"Failed flashing process. Failed flashing process. Error processing flash file. (0x700F); phone conected"
What am I doing wrong? I tried RSDlite ver 4.9 and 5.0 to no avail! Please help! Thank you!
Click to expand...
Click to collapse
So, I was using my laptop with W7 to flash my Defy, I tried RSD lite 4.9 and 5.0 and kept getting the error message. I decided to give my desktop with Vista a shot and installed RSD lite 4.9 and the motorola drivers; i don't know why but immediately after plugging the phone in it started flashing! Awesome! After that I rooted again and installed 2ndInit (Wich is awesome!).
I backed up and flashed CM7 from the custom recovery mode. Everything started working excellent until I decided to re install 2ndInit!!! BIG MISTAKE! Never do that! I nearly bricked my phone again and couldn't load into recovery mode anymore! I had to re flash JRDNEM_U3_2.51.1. After that I had to repeat the whole process with the exemption of reinstalling 2ndInit after CM7.
Since 2ndinit is already installed you don't need to re install even if you don't have the app in your tray.
I'm in the same boat, my phone is in a reboot loop, and I can't seem to flash it...
RSD Lite 4.9 on win7
Error:
Failed flashing process. Failed flashing process. Unable to retrieve initialization values from INI file. (0x7029); phone connected
/me bangs head against the wall...
read somewhere else it has to do with where RSD Lite is installed, on my win 7 32bit that was c:\Program Files\Motorola\RSD Lite...
uninstalled, reinstalled in c:\Motorola\RSD Lite and copied the sbf to that dir too... seems to be working... hope this helps someone else!
NrikeCalderon said:
So, I was using my laptop with W7 to flash my Defy, I tried RSD lite 4.9 and 5.0 and kept getting the error message. I decided to give my desktop with Vista a shot and installed RSD lite 4.9 and the motorola drivers; i don't know why but immediately after plugging the phone in it started flashing! Awesome! After that I rooted again and installed 2ndInit (Wich is awesome!).
I backed up and flashed CM7 from the custom recovery mode. Everything started working excellent until I decided to re install 2ndInit!!! BIG MISTAKE! Never do that! I nearly bricked my phone again and couldn't load into recovery mode anymore! I had to re flash JRDNEM_U3_2.51.1. After that I had to repeat the whole process with the exemption of reinstalling 2ndInit after CM7.
Since 2ndinit is already installed you don't need to re install even if you don't have the app in your tray.
Click to expand...
Click to collapse
Yer cm7 comes with it pre installed it would flash blue at bootup you should of seen it I think on the installation instruction it's written dont install 2ndinit
just rename the .sbf file to smaller name and try again
If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.
I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..
Nikos_s3 said:
I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..
Click to expand...
Click to collapse
Yes, that will do nicely. Just need to get back to GRJ22 stock before you can flash the udpate. The updater-script does an assert and checks the md5 checksum of every system file before it allows the update to flash. If it doesn't find all stock files or checksums don't match what it is looking for, you get a status 7 error and the line above will show which file it stopped on. So you can look at those messages and keep restoring files it wants (if only a few) without having to flash completely back to stock.
I guess that would take much time, as almost all of my google apps are integrated into ROM...so I will try to follow the procedure I wrote earlier and if that won't work, I will try a ready stock,rooted ROM (Fireb33 has done it already)..
thanks mate..
Why so complicated?
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
Bexton said:
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
Click to expand...
Click to collapse
That's only for those who have the bootloader unlocked?
_raz_ said:
That's only for those who have the bootloader unlocked?
Click to expand...
Click to collapse
Well, yep. That method indicates your (phones) bootloader is unlocked. But as it's the N1, unlocking the bootloader is just 19 (up to 25) characters away -> "fastboot(-linux) oem unlock".
Edit: By the way, i looked up that post from an android platform engineer:
Code:
groups.google.com/group/android-platform/msg/b7d83992dd92accb?dmode=source
The N1 is just made for that.
tried superboot but wifi down
I flashed the update for 2.3.6 and then superboot but my wifi gives an error when I try to turn it on.
New Superboot file for GRK39F?
Is there a new Superboot file for the new OTA update?
jboxer said:
If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.
Click to expand...
Click to collapse
I want to update to gingerbread and looking for the proper guidance going forward. I've done some looking around the forums but i'm still unclear if i need to unroot or install a stock build, etc. What i know is the phone is rooted and sim unlocked. How can i check to see if the bootloader is open/locked?
Current specs:
android version 2.2.1
Baseband 32.41.00.32U_5.08.00.04
Kernal Version 2.6.35.9-cyanogenmod
Mod Version: Cyanogenmod-6.1.1-N1
Build: FRG83D
edit:
Please treat me like an idiot and walk me through this process. It's be utterly frustrating and I'm a stone's throw away from busting out my Nokia 3390 (equipped with led disco keypad).
If your bootloader is unlocked you will see an unlocked padlock on the boot up screen...
Hi all,
I am having difficulty installing CM 7.2.0-RC1 on my Droid 2. I have been using the official CyanogenMod wiki guide at
wiki.cyanogenmod. com/wiki/Motorola_Droid_2:_Full_Update_Guide
-phone was originally v2.3.3
-as per guide, downgraded to 2.3.2
-verified phone ok running android version 2.2
-successfully rooted with rageagainstthecage
-installed Droid 2 recovery bootstrap & ClockwordMod recovery
-verifed ClockworkMod recovery working - booted into CWM recovery and created backup
Then I tried to apply the CM7.2.0-RC1 zip update:
-put the .zips (CM7.2.0... and gapps) on my sdcard
-bootstrapped into clockworkmod via droid 2 bootstrapper
-apply update from .zip > choose zip on sdcard > chose update-cm-7.2.0-RC1-droid2-signed.zip
everything seems to go fine, then it pops the status 7 error:
Checking kernel version...
If install aborts here
make sure you are on
the OTA and not the
original GB leak!
assert failed: run_program("/tmp/check_kernel") == 0
E:Error in /sdcard/update-cm-7.2.0-RC1-droid2-signed.zip
(Status 7)
Installation aborted.
The part of the error message where it says "make sure you are on the OTA and not the original GB leak" has me confused... I was on the OTA as far as I knew, but then the wiki guide had me downgrade to 2.3.2. I assume that downgrade is a stock OTA update - am I right?
I've done quite a bit of searching, but can't figure out where I've gone wrong. Is there something else I've missed?
So are you on 2.2 or 2.3.3?
Where did you get your release candidate .zip? I would like to check the integrity of the file.
Sent from my DROID2 using xda premium
I keep banging my head against the exact same set of circumstances. I downloaded all of my files directly from the cyanogen wiki. I rooted my device first with SuperOneClick. Assuming that this might be the problem, I then SBFed it back to stock, and rerooted it verbatim per the instructions on the wiki and the cyano build... and continue to get the same results.
It took a bit of digging around in the CyanogenMod forums, but you have to be on the latest .sbf (2.3.3?). CyanogenMod 7.2 is based on the Gingerbread kernel and won't work over the top of a Froyo installation. Though I hear that you can't just flash nightlies (or any update, for that matter) over the top of it. You'll have to .sbf either way. This really sucks for me because I've got to re-flash my phone back to cricKet wireless (an hour process; manual flashing sucks) every time I .sbf as it sets everything back to the VZW defaults.
Sent from my DROID2 using xda premium
This phone is about to cause me to start mainlining some serious drugs. I just do not understand what I'm doing wrong.
I have read and read and read and downloaded and downloaded and downloaded. At one point I think I had about 10 Firefox tabs open, madly switching between them trying to figure this beast out. So, I have tried to do the necessary homework before posting here.
I received a Verizon Droid X (MB810 model) and was wanting to install a 2nd-init ROM. It came with .621, which I know has been problematic in the past, but seems not to be a terribly big obstacle anymore. Here are the steps I've taken:
o I rooted the phone via the Slitaz ISO.
o Via adb, I pushed the Droid 2 (D2) reboot recovery and ROM manager (RM) APKs.
o I choose boostrap recovery in the D2 application. Superuser grants the appropriate permission.
o Within RM, I download and flash the latest CWM (5.0.2.0) based on the 2nd-init Droid X option.
o RM says that the flash is successful and Superuser rights are granted.
o From within RM, I choose the reboot into recovery option.
o The phone reboots...right back into the operating system, completely bypassing CWM. Redoing the above steps and holding down the home key just boots into the stock recovery.
Now, I can reboot into CWM from the D2 application, but I'm then confronted with the old version of CWM. I've also read where this method will screw-up the boot process to the point that installing 2nd-init ROMs won't work. I've (somewhat) verified this by trying to install the latest AOKP with the D2 version of CWM, which just endlessly loops the unicorn animation. In fact, in a thread detailing this problem on another forum, it was advised to stay far, far away from the D2 application altogether and just use RM.
I've also had to SBF back to .621 on several occasions using RSDLite 4.9.
This has been nightmarish. I spent almost the entire weekend trying to get this phone to boot into the latest CWM. Do I have to SBF the Milestone ROM in order for this to work? Is that even necessary anymore?
Any help would be GREATLY appreciated, as I'm out of ideas at this point. Thanks a bunch.
- Fred
did you wipe data before/after flashing SBF?
if not, that could cause issues
sd_shadow said:
did you wipe data before/after flashing SBF?
if not, that could cause issues
Click to expand...
Click to collapse
Yes, I forgot to mention I did that in my OP.
I just don't understand what's going on. It's almost as if RM is lying to me about having successfully flashed the newest CWM. I say this because, when I immediately do the flash procedure after booting the phone, nothing shows up in /preinstall/recovery/ using Root Explorer (RE). It's only after I do the D2 bootstrap recovery option that /preinstall/recovery/ is populated with the CWM files. The problem is that these files represent the 2.0.5.8 version, not the 5.0.2.0 update.
To even deepen the mystery, after I did the above, I then went back into RM and reflashed to the latest CWM. I then looked at /preinstall/recovery/ again and all of the original 2.0.5.8 files were still there. There was no evidence that I could determine that RM installed anything anywhere.
I'm at a total loss.
did you try deleting NFS Shift or Madden from the preinstall, then reflash CWM in RM?
sd_shadow said:
did you try deleting NFS Shift or Madden from the preinstall, then reflash CWM in RM?
Click to expand...
Click to collapse
I just did that. RE is showing 244MB free, which I'm assuming is more than enough for RM to do its thing. I then redid the steps I outlined above and /preinstall/recovery/ still isn't populating with the 5.0.2.0 update.
This is beyond bizarre. How can RM state that it successfully flashed to the latest CWM when it doesn't appear to do anything? If RM runs into an error in the file creation process, does it report that to the user or just acts as if everything is normal?
i don't think you will get an error
have you tried redownloading D2 bootstrap and rom manager, from market?
have you read this? http://rootzwiki.com/topic/31737-root-droid-x-root-method-for-234-45621-does-not-require-milestone-sbf/page__st__20#entry878745
Maybe this is a dumb question, but I'm not familiar with the Slitaz ISO.
So does that install a 2nd-init ROM? Or have you installed a 2nd-init ROM manually?
If you haven't, you shouldn't be selecting the 2nd-init recovery. Use the regular Droid X recovery, install the 2nd-init recovery only after flashing a 2nd-init ROM.
the link was to a post that
someone was having trouble updating cwm to 5.0, and some possible fixes
as for the Slitaz ISO, is just a linux program used to run the magic md5 root method
fleggett said:
I just did that. RE is showing 244MB free, which I'm assuming is more than enough for RM to do its thing. I then redid the steps I outlined above and /preinstall/recovery/ still isn't populating with the 5.0.2.0 update.
This is beyond bizarre. How can RM state that it successfully flashed to the latest CWM when it doesn't appear to do anything? If RM runs into an error in the file creation process, does it report that to the user or just acts as if everything is normal?
Click to expand...
Click to collapse
found a great work around, or Tomsgt123 shows how in one of his youtube videos
If updating to 5.0.0 with Rom Manager fails
using a file manager/root browser with root access go to
/preinstall/recovery select recovery.zip rename recovery.zip.bak
then go to sd card>clockworkmod>downloads>recoveries> copy the recovery.zip that has ‘shadow.zip’ in properties
go back to /preinstall/recovery and paste recovery.zip
as described in [VIDEO] How to update CWM Recovery on the Droid 2-by Tomsgt123
test test test
blindmanpb said:
Maybe this is a dumb question, but I'm not familiar with the Slitaz ISO.
So does that install a 2nd-init ROM? Or have you installed a 2nd-init ROM manually?
If you haven't, you shouldn't be selecting the 2nd-init recovery. Use the regular Droid X recovery, install the 2nd-init recovery only after flashing a 2nd-init ROM.
Click to expand...
Click to collapse
Slitaz ISO, is just a linux program used to run the magic md5 root method
no it does not install a rom
you only need to update cwm if you want to restore a nandroid backup of a 2nd init rom,
most 2nd init roms come with their own bootstrap, found in the reboot options
you shouldn't install bootstrap or update cwm unless the rom does not install bootstrap
Sorry for the previous "test test test". The forum wasn't letting me post anything until I realized I'm under the ten post threshold and I was trying to quote text that had links.
Thanks, sd_shadow, for the extremely helpful pointers. Unfortunately, I no longer have the phone in my possession, but I might be getting another one to play with soon. I'll let you know if I run into the same problems after applying your potential fixes. Thanks again!
I'm ecstatic to report that the this alternative method by Tomsgt123 worked! Here is what I wound-up doing, from start to 5.0.2.0 finish.
First the facts, all taken from settings -> About phone
System version: 4.5.621.MB810.Verizon.en.US
Model number: DROIDX
Android version: 2.3.4
Baseband version: BP_C_01.09.15P
Kernel version: 2.6.32.9-g1282440 ([email protected] #1)
Build number: 4.5.1_57_DX8-51
ERI version: 5
PRL version: 58012
Bootloader: 30.04
1. Obtain SliTaz GNU/Linux (3.0) root ISO in preparation to root phone. File I used is named Droid2_D2G_DX_DX2-RootCD-2012.iso.
2. Burn SliTaz ISO to bootable media.
3. Enter Windows and boot phone normally.
4. Ensure USB debugging is enabled via the settings -> Application settings -> Development -> USB debugging checkbox.
5. Connect phone to computer via USB cable.
6. Drag from top of phone and select the USB connection -> Charge Only radio button.
7. Boot computer via SliTaz.
8. Choose option 3 (Root Droid X) and follow onscreen directions to the letter, including putting phone in bootloader mode.
9. Boot phone normally and invoke Superuser. Immediately exit Superuser. (This step probably isn't necessary.)
10. Install Droid 2 Bootstrapper (D2B), ROM Manager (RM), and Root Explorer (RE) on phone (I used adb).
11. Invoke D2B and choose Bootstrap Recovery. When done, exit D2B.
12. Make sure phone is connected to internet.
13. Invoke RM and choose Flash ClockworkMod Recovery. Current Recovery should be 5.0.2.0.
14. Choose 3rd option, Motorola Droid X (2nd-init).
15. Tap Flash ClockworkMod Recovery. Wait until recovery files are downloaded and flashed, then exit RM.
16. Invoke RE and navigate to /preinstall/recovery.
17. Rename recovery.zip to recovery.zip.bak.
18. Still within RE, navigate to /sdcard/clockworkmod/download/download2.clockworkmod.com/recoveries.
19. Press and hold on recovery-clockwork-5.0.2.0-shadow.zip and copy the file.
20. Navigate back to /preinstall/recovery and paste the above file.
21. Rename the above pasted file to recovery.zip.
22. Exit out of RE and return to RM. Tap Reboot into Recovery and hit OK at the "Are you sure...?" prompt.
23. Phone should reboot into the 5.0.2.0 version of CWM.
Thanks again, sd_shadow. Without the above "manual" method, I would never have gotten the 5.0.2.0 version of CWM onto this phone. Now, time to play!
- Fred
And guess what? All those previous steps I carefully and deliberately outlined have been rendered obsolete by one, small apk:
http://rootzwiki.com/topic/25017-ro...workmod-flashable-updates-by-ky/page__st__190
(Still can't post links...yet.)
This is the Droid X Bootstrapper 621 MOD (DXB621). Functionally, it is the same as the old D2B except for two huge and critical features:
1. It contains CWM 5.0.2.0 out-of-the-box.
2. It works without having to do the aforementioned file manipulation inside RE.
Because of the above, it negates the need for RM (and D2B) entirely. I immediately installed DXB621 on my freshly SBF'd and rooted Droid X (see previous stats) and it worked flawlessly.
After all this, I'm convinced there is something wrong with RM as it relates to the Droid X with .621 already installed, whether via the OTA update or via SBF.
As a big bonus, after some finagling, I was also able to install HijackedBootMenu 1.1.5 621 1.1, which is a real gift, since it allows booting into CWM (or RZR) without having to first boot the phone to use either D2B, RM, or DXB621 itself.
So, the moral of this long and windy story is to simply use DXB621 for your recovery needs, don't mess with D2B and RM, and don't look back.
- Fred
nice find
I had seen that thread before, too bad the modified bootstrap isn't noted in first post, but page 20 of 110
I tried it on my D2 a955, and was able to to boot to cwm 5.0
so I will add it to my list.
sd_shadow said:
nice find
I had seen that thread before, too bad the modified bootstrap isn't noted in first post, but page 20 of 110
I tried it on my D2 a955, and was able to to boot to cwm 5.0
so I will add it to my list.
Click to expand...
Click to collapse
Yeah, getting any bootstrap to work on a Droid is the first step (after rooting) in doing much of anything, and using the most recent CWM seems to be required for all the latest and greatest ROMs, so it really should be somewhere on page 1 of that monster thread. I only stumbled across it via dumb luck.
I've run into a bizarre issue, though. With the phone connected to a running computer via USB, it won't boot into either CWM or RZR from Hijacked BootMenu (HB). Once you hit either recovery option, it just goes to a (slightly lit) black screen and stays there. The power button doesn't work at that point, so it requires a battery pull.
A clue as to what's going on might be that Windows recognizes the device when HB runs. It's only when I disconnect the cable before booting the phone that either recoveries invoke normally. Very strange.
I currently have CMKang.b3 loaded on the phone. I was pleasantly surprised to see that both the Camera and Torch apps work just fine, as I thought both were inoperable under CM9. This specific build is 9-20130120-UNOFFICIAL-shadow.
- Fred
sd_shadow said:
found a great work around, or Tomsgt123 shows how in one of his youtube videos
If updating to 5.0.0 with Rom Manager fails
using a file manager/root browser with root access go to
/preinstall/recovery select recovery.zip rename recovery.zip.bak
then go to sd card>clockworkmod>downloads>recoveries> copy the recovery.zip that has ‘shadow.zip’ in properties
go back to /preinstall/recovery and paste recovery.zip
as described in [VIDEO] How to update CWM Recovery on the Droid 2-by Tomsgt123
Click to expand...
Click to collapse
THANK YOU! I was having a similar problem as the OP, and this FINALLY fixed it!
also take a look at the modified d2 bootstrap that has been upgraded to cwm 5.0
will save a few steps if you have to reinstall
edit: I have rewritten my instructions here
[HOW TO] Install/Use Droid 2 Bootstrap
The modified Bootstrap is the trick. Straight to CWM 5.0. Took me a long time to figure out that ROM manager appears to update CWM but does not work. I found ROM manager to be of no use or value at all to me and don't install it or delete it.
Got 11 Open
Looking for an answer myself. Currently trying to install using Rom Manager then using button presses to get into Recovery. Will post update shortly.
I eventually decided to flash Kitkat onto my Defy+.
Followed this guide here:-
http://forum.xda-developers.com/showthread.php?p=52342403#post52342403
Everything worked fine until I got to the actual flashing of the KK Rom. TWRP had loaded fine but insisted I had no OS installed and on exit suggested device was not rooted?
Phone kept saying failed and to re partition. So I tried the Resize.zip from another guide. This did nothing either , still the same.
It had also had the following error, "Error Executing Updater Binary In Zip".
So I tried the solution here:-
https://kalitutorials.wordpress.com/2015/06/19/solve-error-executing-updater-binary-in-zip/
Now I cannot boot into TWRP or Clockworkmod recovery. When I try to boot phone it just sits on Motorola Sign but doesn't progress and no led flashes to enter TWRP. Battery needs to be removed to switch off.
If I power up with Volume down pressed, I get picture of Android Green Robot standing up with an yellow exclamation in a white lined triangle. No options are shown.
Pressing Vol up and down I get me to Android System Recovery <3e>. Options there are, reboot system now, apply update from sdcard, wipe data/factory reset, wipe cache partition.
I can also enter bootloader using vol up and power.
Any ideas anyone, found this guide to try to fix but don't want to try anything else without some confidence it will work.
http://www.tech-zealots.com/tutorials/unbrick-motorola-defy-or-defy-100-working/
I have a nandroid backup created in normal recovery btw. I would prefer to flash back to it if possible.
Thanks
G
You need to download a sbf file https://mega.nz/#!915TCAAD!X7_f1t83lVPkK5p7jUdokeE4SQ8qTRqPnBWNvfgyxWA (this one is stock android 2.3.6), then you need to install drivers and rsd lite and connect your phone (must be already in bootloader mode) to your pc and then reflash the sbf file. After that, your phone will boot up to the stock firmware and you can install cm11 then. Basically you can follow up the the guide that you posted. Good Luck
dc239 said:
You need to download a sbf file https://mega.nz/#!915TCAAD!X7_f1t83lVPkK5p7jUdokeE4SQ8qTRqPnBWNvfgyxWA (this one is stock android 2.3.6), then you need to install drivers and rsd lite and connect your phone (must be already in bootloader mode) to your pc and then reflash the sbf file. After that, your phone will boot up to the stock firmware and you can install cm11 then. Basically you can follow up the the guide that you posted. Good Luck
Click to expand...
Click to collapse
Thanks for your reply.
Tried what you suggested but after flashing that sbf the phone tries to boot up but after logo drops back to bootloader 9.10 with ERR:a5,69,35,00,27 .
I managed to get the Retail UK sbf referred to here:-
http://forum.xda-developers.com/showthread.php?t=1421526
Tried flashing it but end up with a black screen bootloader and just white led lit. Reflashed the sbf u suggested and back to Bootloader with Err.
Googling seems to suggest I am just needing to get the right sbf for the phone.
I have the Nandroid backup made with Clockworkmod recovery. Is there anyway to flash it?
TIA
G
Sorted
After extensive digging and climbing the steep learning curve. Decided the problem was that the sbf file u suggested was DFP 231 and possibly my phone was DFP 2311. Found Firmwares here:-
https://firmware.center/firmware/Motorola/Defy+ (MB526)/Stock/
And downloaded the DPF 2311 Rom, only was one. (DEFYPLUS_U3_4.5.1-134_DFP-2311_BLUR_SIGN_USADEFYEMARAB1B8TFDE004.0R_PDS03C_USAJRDNGIBRO2DE_P020_A025_M002_Service1FF.sbf). Tried flashing it and voila system is back, albeit it started up in German.
Gonna try the rooting mehod here:-
http://forum.xda-developers.com/showthread.php?t=1820282
For anyone elses benefit, the links for Roms at Android Developers don't work. The retail EU Firmware mentioned in the rootong guide is available on the site referred to above. U can tell when you click the link to the Android Developers site as the browser URL shows the full file name as follows.
DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf.gz
The rooted one I think is the same one you linked me to and is still valid in the Rooting guide too.
Thanks for all help and I hope this is of use to someone else.
G
Minor question still remains.
If I am trying to install Kitkat rom. DO I still need to Root phone if the rooted 231 has been installed, I presume not?
G
Followed rooting guide and so now have a rooted 231. All good
Now for KK.
G