When I was on the stock Verizon ROM I was able to simply run the Droid 2 Bootstrapper and it booted into recovery. From there I installed this Galnet MIUI ROM. I'd like to check out some other ROMS but I cannot get CWM to install.
In ROM Manager 3.0.1.4 I tap on Flash CWM and it says "An error occurred while downloading your recovery"
I tried installing the D2 bootstrapper and when I click on boot into recovery my device simply reboots back into MIUI and everything has been reset to default. I'm kind of new at all this and tried searching but didn't really come up with a solution. I've heard something about SBF but not sure what that is. Any help would be appreciated. Thanks.
Here, try this. CM7 is the best ROM for this phone anyways
http://wiki.cyanogenmod.com/wiki/Motorola_Droid_2:_Full_Update_Guide
Cool I will check it out. I figured out how to get back to stock using RSD Lite. Slowly but surely I'm getting all this Android stuff.
So now I'm running into another issue. Once I get the SBF installed and I'm back on stock 2.2 I can't seem to get any other ROM flashed. At all.
On 2.2 I root the device using z4root. Then I install the D2 bootstrapper and reboot into recovery. The standard CWM screen comes up. I wipe cache. Clear Davlik cache, etc, etc. I install the update.zip and everything seems fine. Says process is complete but when the phone is restarted I'm stuck in an endless boot loop of the white Motorola logo.
Did you only wipe the cache or did you wipe data/factory also?
I did both. When I got this device it was on 2.3.7 I think. It's not activated and I plan on using it as a PDA/MP3/WIFI device. Seems like I can't do any factory updates without cellular data so it's on 2.2.
I can't even get MIUI 2.2.10 back on there.
You need to be on GB not Froyo to run Galnet. There's an SBF for 2.3.7 posted here on the forums.
there is no 2.3.7
2.3.4/4.5.621 is latest and it is unrootable and can not flash older sbfs
use 2.3.3/4.5.601 aka 1FF-p2a_droid2_cdma_droid2-user-2.3.3-4.5.1_57_DR2-31-110719-release-keys-signed-Verizon-US.sbf
find here http://1kds.tk/
2.3.4; you knew what I meant =p
I got it all worked out. Are there any overclocking enabled kernels for the D2?
I recommend Milestone Overclock. It doesn't load on boot with all Roms, but it does on most and it's free and doesn't come with AirPush like some apps.
Related
Hi folks,
How can I make CM7 to work? Hate the stock rom.
I have followed step by step to unlock my atrix 2.3.4 bootloader and then install CWM recovery, then install CM7 ba2tf from recovery, then wipe data/factory reset, wipe cache, reboot.
But then my phone would not pass the moto dual core logo with "unlucked" on the top left corner.
I tried fastboot erase, use different CWM recoveries, tried both the ba2tf and nightly build, all turned out to be the same "stuck at moto dual core logo" problem.
Did I miss anything? Or my phone is just special that refuses custom ROMs...
I followed these instructions:
unlock bootloader: http://forum.xda-developers.com/showthread.php?t=1182871
install cm7: http://forum.xda-developers.com/showthread.php?t=1336232&highlight=install+cm7
Thanks in advance!
UPDATE: Just tried to flash the ASOP atrix rom and it works fine! This is weird, I noticed when I install ba2tf it's really fast even though the zip is around 90MB, but installing others is very slow, like ASOP rom at around 60MB. Does that make a difference?
sbf flash a stock rom using rsd lite.
Thanks for the suggestion. I can make stock rom work... but I just wanna avoid it.
Make sure to open rom manager and do the "flash clockworkmod recovery" for your atrix. then go down to "install rom from sdcard" and let cwm do its buisness.
That was the step i missed and doing this solved the issue of not getting passed that first screen for me.
wakkakai said:
Make sure to open rom manager and do the "flash clockworkmod recovery" for your atrix. then go down to "install rom from sdcard" and let cwm do its buisness.
That was the step i missed and doing this solved the issue of not getting passed that first screen for me.
Click to expand...
Click to collapse
Actually I did something similar to this. After I tried another ROM that flashed the CWM to a newer version for me, then I installed the ba2tf again with the latest version of CWM and everything started to work like a charm.
Thanks!
Nice! Glad it is working.
So on a wild hair i decided to try out the latest official firmware. Stupid i know.
Now when i SBF back to the old firmware as stated in the cyanogenmod full update guide, root and bootstrap i can get into CWM recovery but no matter what rom i use it just bootloops. Then if i try to go back into CWM i of course find its the stock 3e recovery.
Did i perma-bork my phone from having custom roms or is there a problem between the chair and monitor? lol
did you wipe data and cache?
http://forum.xda-developers.com/archive/index.php/t-914110.html
DX .605 ROOT
marculous said:
did you wipe data and cache?
http://forum.xda-developers.com/archive/index.php/t-914110.html
DX .605 ROOT
Click to expand...
Click to collapse
Yeah, after I got the first bootloop I tried with apex and liberty and on each attempt wiped data and cache 3x
wipe data and cache, factory reset, then sbf? idk, I've been where you are many times and i always have to go back to the guides to get the process right, in the correct order.
DX .605 ROOT
So is there no reason that the newest OTA* would ruin the ability to put custom roms on?
i wouldn't think so, but i know for cm7 to get on my phone i had to sbf back to 2.2 from the. 596 i was on. guess it depends on the rom. me personally, i just left cm7 for. 605, rooted because i like the blur camera and hdmi support. took off most of the bloat but not all, it jacked up my contacts.
DX .605 ROOT
just treid it again, SBF'd back, rooted, bootstrapped, wiped data and cache and installed Liberty to come to a boot loop. i think .605 has locked me out of custom roms
spockmeat said:
just treid it again, SBF'd back, rooted, bootstrapped, wiped data and cache and installed Liberty to come to a boot loop. i think .605 has locked me out of custom roms
Click to expand...
Click to collapse
can you sbf back to an earlier version?
DX .605 ROOT
Yes I can go back to the froyo SBF without any problem. The issue is, once i do that, then repeat the steps and flash a custom rom, no matter what rom i use, i get a bootloop. the stock SBF and OTA work fine, its just once a custom rom is installed.
spockmeat said:
just treid it again, SBF'd back, rooted, bootstrapped, wiped data and cache and installed Liberty to come to a boot loop. i think .605 has locked me out of custom roms
Click to expand...
Click to collapse
How long did you bootloop? Liberty 3 2.0 can take up to 10 mins to load first time around... I'm assuming you are just seeing the spinning eagle? I thought I was bootlooping too, luckily I got caught up doing something else set the phone down and 10 mins later I had liberty running
sent from my Droid X running Liberty 3
hootowlserenade said:
How long did you bootloop? Liberty 3 2.0 can take up to 10 mins to load first time around... I'm assuming you are just seeing the spinning eagle? I thought I was bootlooping too, luckily I got caught up doing something else set the phone down and 10 mins later I had liberty running
sent from my Droid X running Liberty 3
Click to expand...
Click to collapse
No, it bootloops at the M Logo screen.
the M logo comes up for like 2 seconds, then the phone reboots.
The only variance to this is when i flash the AIO APEX rom, then it just sits at the google logo indefinitely. But on any other rom including Cyanogenmod and Libery it bootloops at the "M" Logo.
There is no reason for this to happen. Sticking at the Motorola's logo shows that something didn't flash correctly.
My only guess is a md5sum mismatch on every rom you are trying to flash, either that or you are trying to flash Froyo roms while using the Gingerbread kernel.
What you should do is SBF again to .602. AFTER you SBF, format data and cache via stock recovery then reboot. If it asks you to update don't take it.
Go to Rootzwiki and download a rom such as Vortex, MIUI, or ICS. Make sure that the md5sum on the rom you select matches the one given in the thread.
Root your phone with Pete's Motorola's Root Tools. Then install ClockworkMod Recovery with Droid 2 Bootstrapper. After you install ClockworkMod Recovery download Rom Manager from the market. Set your device to 'Droid X', and it will download and update ClockworkMod Recovery to the latest version.
Once this is complete, reboot into the newly updated ClockworkMod Recovery (which should be blue), and install your chosen rom.
Once you have installed it wipe data and cache, as well as the dalbik cache. Then reboot your phone.
If you have followed my directions down to every last comma, then your phone should boot into your newly flashed rom. If this doesn't work then something is very wrong. Something beyond my understanding that probably won't be fixable.
Feel free to message me if you have any questions. Best of luck to you!
Sent from my DROIDX using XDA App
infazzdar said:
There is no reason for this to happen. Sticking at the Motorola's logo shows that something didn't flash correctly.
My only guess is a md5sum mismatch on every rom you are trying to flash, either that or you are trying to flash Froyo roms while using the Gingerbread kernel.
What you should do is SBF again to .602. AFTER you SBF, format data and cache via stock recovery then reboot. If it asks you to update don't take it.
Go to Rootzwiki and download a rom such as Vortex, MIUI, or ICS. Make sure that the md5sum on the rom you select matches the one given in the thread.
Root your phone with Pete's Motorola's Root Tools. Then install ClockworkMod Recovery with Droid 2 Bootstrapper. After you install ClockworkMod Recovery download Rom Manager from the market. Set your device to 'Droid X', and it will download and update ClockworkMod Recovery to the latest version.
Once this is complete, reboot into the newly updated ClockworkMod Recovery (which should be blue), and install your chosen rom.
Once you have installed it wipe data and cache, as well as the dalbik cache. Then reboot your phone.
If you have followed my directions down to every last comma, then your phone should boot into your newly flashed rom. If this doesn't work then something is very wrong. Something beyond my understanding that probably won't be fixable.
Feel free to message me if you have any questions. Best of luck to you!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
^This werk'd! I owe you vigorous oral.
spockmeat said:
^This werk'd! I owe you vigorous oral.
Click to expand...
Click to collapse
wow...........
I accidentaly installed the CM9 kernel when i should have installed the CM7 one with ICS. Then i made a nandroid restore of my previous CM7. Than... phone dead. Starting but no CWM no ROM booting.
As i have had CM7 with GB kernel( i think) i flashed ( not knowing) an old SBF than didn't booted. I tried the JORDN_U3_97.21.51 T-Mobile It boots, i can root it, install CWM.
But than when i try to install a CM7 nightly ( installed ok) it dies again. Starts but No CWM no Rom booting.
What to do? I don't know what SBF to flash or what method to install?
Problem update I red that the above SBF has a CG Version 3: SBF 2.51 (Éclair) (Defy) so i installed several CG Version 4: SBF 3.4.2 (Froyo) (Defy).
They don't work. RSD says PASS but phone is dead .No stock recovery no boot. Only way to get it back to life is if i flash the eclair again.
I red that if i get a back screen when booting i have installed a lower CG version. As i tested with version 4, version 5 GB is the only option. I didn't try it out because there are some issues. Froyo would have been much more easier.
i think many readers of your post are getting problems with understanding your problem ...
you got a stock defy, rooted it, installed 2ndinit via apk, booted into recovery (vol- at blue led) and installed CM7 zip ??? correct ???
after succesfull install of CM7 your phone doesn't turn on? Black screen?
black screen after zip is (i think) impossible ... but i can fail ...
i would like to help you, but first you have to give the detailed steps you did and what you wanted to do ...
To make it simplier
I installed the JORDN_U3_97.21.51 T-Mobile (which is 2.1 update1) It boots, i can root it, install 2nd-init > CWM. Set Normal boot.
Than in CWM nothing works.
Installing a CM7 nightly, or restoring a CWM backup.
I install a CM7 nightly like this> In CWM> Custom Recovery> Wipe data, wipe cache> install Cm7 zip, install Gaaps zip. After this, phone restarts, screen is on, logo appears and i wait and wait. Nothing happens.
Do i have to install a special CM7 build?
The CWM backup does not restore. It says that files are missing ( like android.secure..) I am not interested in keeping downgrade ability. i would like to try another SBF. I am not 100% sure what SBF to use from the wiki page.
I red that the SBF i installed has some special "problems" here> http://forum.xda-developers.com/showthread.php?t=905371. They are talking of a CWM revoery app by tenfair here> http://forum.xda-developers.com/showthread.php?t=875233
Maybe that works^. Will try it after the phone is fully charged.
so, ok ... thats detailed as i wish
ok, the problem is clear i think ... first of all eclair is not a nice system for a defy ... upgrade to froyo or even gingerbread ... (keep in mind, that GB has problems with green lens camera) ...
than you can root it with SuperOneClick e.g. ... if this is running correctly, you can install 2ndinit via apk ... then boot, vol- while blue led (i know, you know how ) ... in that clockworkmod recovery you can wipe the devices data and cache partition (even wipe dalvik cache in advanced menu) ... then install CM7.2-nightly-.... .zip ... you may have to flash an fixed sbf with the nessesary kernel for CM7 at this point to boot ...
if this is working fine, you can install the gapps.zip via recovery ...
also try to set boot to 2ndinit in boot-menu ... i don't think it's "normal" boot for CM7 ... but i can't try at the moment cause of my bricked defy ...
Thanks for the reply.
The problem is that i can't install other Froyo SBF's. Will try Gingerbread SBF. The last froyo didn't boot, will try a new one. Weird, i know. Maybe someone can tell me which CM7 to flash? An older one with Kernel ? I didn't think the install would be so tricky.
Froyo Full-SBF doesn't boot on your defy?
be aware of flashing Gingerbread then ... if GB doesn't boot, you will have a problem downgrading to froyo / eclair ...
it sonds crazy, that froyo isn't booting on your device ... have you done a full wipe after froyo sbf? it's important ...
I'm on the Eclair SBF right now. What should i do? Go into recovery and do a wipe or install a new Froyo SBF? It's about the CG value maybe. I understand the mechanism but don't know how to check the CG value. If i search for my current eclair SBF i get all sorts of weird stuff. Nevertheless i will try and try until i succeed. It took me a while to figure out the Rooting method. Superoneclick does not work. It's a special method for the 2.51.
The thing is that i wanted to go the my Nordic SBF( the one Quarx used during the first days of CM7) and it didn't booted. That's why i tried this one. Funny ho flashing the wrong kernel(CM9 instead of CM7) can brake things like this. What i don't understand is how my CWM backup didn't restore. It restored well, finished, then phone dead. No CWM.
edit: i just red: 2.51 is Not downgradable. But no downgrade to what??? Will try to some Froyo SBF's, see if works. But that does not solve my CM7 issues.
Tried a few Froyo SBF's. Wiped data/cache in Stock Recovery. RSD says PASS than phone does not boot. Only the 21.51 eclair works all the time.....Where next?
Update 2 got it to work with this>
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=cg
OMG i dn't understand what was going on with your defy, but i'm happy to know your on the road again
the only sbf that are running are the stock eclair you have (21.51) and the modded BL6 with Froyo Kernel ???
Glad it worked.
DJ_Synergy said:
OMG i dn't understand what was going on with your defy, but i'm happy to know your on the road again
the only sbf that are running are the stock eclair you have (21.51) and the modded BL6 with Froyo Kernel ???
Click to expand...
Click to collapse
Yes but now i am running CM9 flawlessly. So happy. The only thing that bothers me is the Chinese Boot screen )). But that can be changed. It's great that one SBF works, moded or not. I tried like 6,7 other Stock sbf's before. So a message to whom tries to install SBF's: Stay away from JORDN_U3_97.21.51 SBF. Even the Rooting method is awful (until you find it) .
HI Deonix, I have the similar problem. However I am unable to use RSDlite as it gives a failure messg when u click start. I tried JRDNEM_U3_3.4.3-36-1.7.sbf and JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B50AA028.0R_USAJORDANRTINT15_P003_A020_HWp3_Service1FF.sbf.
Both failed, I will try using the rsdlite after the cache and factory rest this time based on your suggestions. Can you tell, if your adb command was listing your device, as mine is not.
my CWM is also gone I get some old android recovery system 3e instead which fails after signature check.
Hi,
I think I know what is your problem.
I also installed the firmware JORDN_U3_97.21.51 and now I can only install any Custom ROM after installing the firmware fix for JORDN_U3_97.21.51.
I did upload it for you: http://www.4shared.com/rar/o02VEk_v/firmware.html?refurl=d1url
It is the following:
Install JORDN_U3_97.21.51;
Rootear;
Install the Recovery;
Install the fix;
enter the recovery and install any rom you want, remembering to delete the caches (data and Dalvik cache)
ps: have 100% of the battery before installing the SBF.
any problems let me know.
Sometimes you could get stuck in a bootloop and all you need to do is pull battery and reboot
Sent from my MB525 using xda premium
Same Problem, Please help!
Deonix said:
Yes but now i am running CM9 flawlessly. So happy. The only thing that bothers me is the Chinese Boot screen )). But that can be changed. It's great that one SBF works, moded or not. I tried like 6,7 other Stock sbf's before. So a message to whom tries to install SBF's: Stay away from JORDN_U3_97.21.51 SBF. Even the Rooting method is awful (until you find it) .
Click to expand...
Click to collapse
Hey bro.
Even i have got the Defy working, but its not detecting the device when connected to the computer, i have done all the basic troubleshooting, is it working for you??
is it bcoz this room is for ME525??
Hi all
I use to run cm-7.2 Jordan without any issues. Decided however to upgrade and test cm10 but since I didn't find it stable enough I decided to downgrade back to 7.2. The flash succeed without issues but when I reboot I get stuck with the Google logo and the os never boot up.
I tried to go through cm.7.1 but no luck there, same issue.
Any clue how i can resolve this?
llavsor said:
Hi all
I use to run cm-7.2 Jordan without any issues. Decided however to upgrade and test cm10 but since I didn't find it stable enough I decided to downgrade back to 7.2. The flash succeed without issues but when I reboot I get stuck with the Google logo and the os never boot up.
I tried to go through cm.7.1 but no luck there, same issue.
Any clue how i can resolve this?
Click to expand...
Click to collapse
Try to wipe all from stock recovery ----> Power+Vol dwn
Kayant said:
Try to wipe all from stock recovery ----> Power+Vol dwn
Click to expand...
Click to collapse
Thanks for quick reply. I tried that and the phone loaded a android character with a triangle and a exclamation mark. I don't have a good feeling about that
llavsor said:
Thanks for quick reply. I tried that and the phone loaded a android character with a triangle and a exclamation mark. I don't have a good feeling about that
Click to expand...
Click to collapse
That's good sorry forget to say you need to hold VOL dwn& Vol Up at the same time then wipe all...
Good luck
Exactly the same problem here, cannot downgrade to CM7.
Any good news?
Flash official froyo (I used ver 2.2.2)sbf via rsdlite. Root it using superoneclick and install 2init bootmenu 2.0. In custom recovery do full factory wipe follow with restore your nandroid 7.2 if you have them. If it booting hang at start screen, flash any froyo fixed sbf that contain the froyo kernel(optional). This way all your previous user data will still be intact.
Sent from my awesome rooted Defy: 2.3.6 XDA premium
So the recovery won't work and will have to start with SBF. Will wait until I have the computer environment to do so.
Thanks!
Kayant said:
Try to wipe all from stock recovery ----> Power+Vol dwn
Click to expand...
Click to collapse
farsight73 said:
Flash official froyo (I used ver 2.2.2)sbf via rsdlite. Root it using superoneclick and install 2init bootmenu 2.0. In custom recovery do full factory wipe follow with restore your nandroid 7.2 if you have them. If it booting hang at start screen, flash any froyo fixed sbf that contain the froyo kernel(optional). This way all your previous user data will still be intact.
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
llavsor said:
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
Click to expand...
Click to collapse
Wipe all from stock recovery that's you needed to do btw before installing cm7.... Sbf is not needed.
Go to stock recovery and wipe all your ROM should boot...
Let's Go ^_^
llavsor said:
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
Click to expand...
Click to collapse
Factory reset from stock bootmenu again. If it still hangs, flash sbf again with another factory reset afterwards just to be safe. BTW, I've had times where 3+ sbf flashes with factory resets were needed to get the phone to boot again.
One problem you might be having is if you formatted /data and /cache to ext4. Maybe it was just me, but I had to reinstall CM10, change back to ext3, flash sbf, then install CM7. Changing to ext3 and flashing CM7 didn't work -- same problem you're having. I wasn't sure if ext4 was the problem so I made sure I changed back to ext3 before sbf flashing. I'm not sure if the sbf reformats the partitions or just wipes them like a factory reset. If you've already flashed the sbf, then you can't install a CM10 rom to change back to ext3... Worse come to worse, you maybe able to install one of the custom sbf's with CM10 custom kernel preinstalled, change to ext3, flash official sbf, factory reset, then install CM7. I haven't looked into them because I make my own custom sbf's .
Bravo users are having this exact problem and my solution is to ensure that /data and /cache are ext3, flash the sbf and start from scratch -- the only guaranteed way I know of to fix this problem. Another Bravo user had the same problem and managed to fix it by changing some /data permissions over adb -- the user didn't specify the exact things done so I'm waiting on a reply with more details.
skeevy420 said:
Factory reset from stock bootmenu again. If it still hangs, flash sbf again with another factory reset afterwards just to be safe. BTW, I've had times where 3+ sbf flashes with factory resets were needed to get the phone to boot again.
One problem you might be having is if you formatted /data and /cache to ext4. Maybe it was just me, but I had to reinstall CM10, change back to ext3, flash sbf, then install CM7. Changing to ext3 and flashing CM7 didn't work -- same problem you're having. I wasn't sure if ext4 was the problem so I made sure I changed back to ext3 before sbf flashing. I'm not sure if the sbf reformats the partitions or just wipes them like a factory reset. If you've already flashed the sbf, then you can't install a CM10 rom to change back to ext3... Worse come to worse, you maybe able to install one of the custom sbf's with CM10 custom kernel preinstalled, change to ext3, flash official sbf, factory reset, then install CM7. I haven't looked into them because I make my own custom sbf's .
Bravo users are having this exact problem and my solution is to ensure that /data and /cache are ext3, flash the sbf and start from scratch -- the only guaranteed way I know of to fix this problem. Another Bravo user had the same problem and managed to fix it by changing some /data permissions over adb -- the user didn't specify the exact things done so I'm waiting on a reply with more details.
Click to expand...
Click to collapse
Okey good advice.
Here is where I am at now. I have flashed a number of different SFBs and I end up with the same situation every time. RSDLIte finish the process nicely but the phone get stuck with the flashing M. When I reboot manually I get passed the M and to the Android text/logo and there I get stuck.
I get advice to do a factory reset but how do I do that. The CW bootloader is gone and I can't get to the original boot loader either. I hit volume down and power, get to the triangle screen where I am supposed to hit the right bottom corner but nothing happens.
So I cant boot the phone to get into a menu where I can change to ext3 if this is a problem.
Please help, how can I get further?
Since I have no luck restoring stock rom I now have the following plan.
Install ClockWorkMod recovery with ADB.
Using recovery to do a factory reset and clear cache.
Flash a CM10 ROM (or any rom that will successfully boot up my phone).
From that start over to downgrade to CM9 to find a stable ROM.
The question I have now is if I will be able to use ADB with the USB connection mode I get from the bootloader (volume up+pwr button)? Or does ADB actually require that I can boot my phone and go into some other USB mode such as UMS or MTP.
Second question. Playing with restoring stock ROM i run out of battery and now my defy wont charge (only see a big question mark when loading). Seems like I get no power when USB is connected so is there a way for me to charge the battery or do I need to find another happy camper in town with a working defy that can power up my battery?
llavsor said:
Okey good advice.
Here is where I am at now. I have flashed a number of different SFBs and I end up with the same situation every time. RSDLIte finish the process nicely but the phone get stuck with the flashing M. When I reboot manually I get passed the M and to the Android text/logo and there I get stuck.
I get advice to do a factory reset but how do I do that. The CW bootloader is gone and I can't get to the original boot loader either. I hit volume down and power, get to the triangle screen where I am supposed to hit the right bottom corner but nothing happens.
So I cant boot the phone to get into a menu where I can change to ext3 if this is a problem.
Please help, how can I get further?
Click to expand...
Click to collapse
In froyo, you should hit vol up/down together to enter stock recovery.
If you have your cm7 nandroid or your gingerbread nandroid 2.3.6. In,custom recovery cm10, restore them. Your phone would not boot but you have your cm7 or gingerbread cwm by then, that you could format cache and total wipe back to ext.3 in the recovery menu, format/wipe follow with another nandroid restore and flash fix sbf from rsdlite.
But then the best way is go back totally clean by flashing stock froyo and root, install 2init with bootmenu 2.0. Then total wipe in recovery follow with restore your cm7 or gingerbread nandroids and flash the corresponding fix sbf via rsdlite.
Charging dead rom defy would need the MacGyver trick then. But some say if you leave it connected overnight in pc usb would charged it somehow but slow..
On 2nd thought.. you need to tell us yoyr defy model...green lense, red lense or the defy plus?? These models has their own characteristics in term of play around in cwm and way of flashing..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
farsight73 said:
In froyo, you should hit vol up/down together to enter stock recovery.
If you have your cm7 nandroid or your gingerbread nandroid 2.3.6. In,custom recovery cm10, restore them. Your phone would not boot but you have your cm7 or gingerbread cwm by then, that you could format cache and total wipe back to ext.3 in the recovery menu, format/wipe follow with another nandroid restore and flash fix sbf from rsdlite.
But then the best way is go back totally clean by flashing stock froyo and root, install 2init with bootmenu 2.0. Then total wipe in recovery follow with restore your cm7 or gingerbread nandroids and flash the corresponding fix sbf via rsdlite.
Charging dead rom defy would need the MacGyver trick then. But some say if you leave it connected overnight in pc usb would charged it somehow but slow..
On 2nd thought.. you need to tell us yoyr defy model...green lense, red lense or the defy plus?? These models has their own characteristics in term of play around in cwm and way of flashing..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
Thanks for very informative reply. I have a Defy 525 with red lens.
It's working.
I found a friend blessed with a defy and used that to charge the battery, tried to charge it over night with USB but it didn't work.
I then followed the steps from the last post and managed to flash a stock rom and then from there I rooted the phone with SuperOneClick, installed 2ndInit with ADB (guess you could use an apk installer from the phone as well ). I booted into recovery and flashed 7.2.0 Jordan from CM and now I am where I started a few weeks back.
Thank you all for your help.
That was the low battery problem.......
Since i had this i allways look for a full battery
If you think your defy is dead , a look for a empty battery won't be mad
Could anybody took a reminder info into beginners guide
MB525 red lense
Hi,
I have Defy+ running quarx's CM10 android 4.1.2.
What I want is to recover my phone as it was, with official gingerbread and no 2nd init or other software installed on it.
Is there any way to do that?
If yes I would appreciate some help with it.
Thanks!
That's quite easy, isn't it? Simply download one of the offical bilds (sbf files), copy it (i mean if needed thing you need for flash like safe wipe) on sd card, wipe everything, boot into stock recovery (well i believe dl-mode) and flash official rom.
I was thinking about doing that and thanks for confirming it. What I am not sure about is if everything else installed that does not run in android, like 2nd init and other stuff lets call them , pre os, get deleted and only the stock firmware will be left. I will do this though and we will see how it goes.
Now do any of you helpful people have an sbf for Europe without blur UI in it?
A link would be helpful if so.
Thanks again!
Sbf cannot be flashed from sdcard! It must be done thru RSDLite. 2ndinit, etc will get wiped. If stuck in a boot loop after flashing, wipe data after stock recovery
Sent from my MB526 using Tapatalk
Quite simple. Wipe Data / Cache first via Stock Motorola Recovery. Flash SBF for your region. Voila! your phone is all stock again.
If you want a good De-Blur ROM try WIUI or if you still dont want the customizations move to MS2Ginger ->
http://forum.xda-developers.com/showthread.php?t=1140839