Related
My phone is rooted and i cannot enter the custom recovery menu. I can get to the dx recovery. Tried sbf but rsd lite nor my pc will recognize the phone. PC says that the driver cant be located in bootloader menu even tho i do have the moto drivers installed. any suggestions on how to get it to work to run the sbf. I've tried all delete options in recovery menu probably screwed myself.
Hey there,
I had something similar back when I tried to root my evo 4g the first time, what I did was go to the carrier store (in my case Sprint) and acted like one day just started to act weird and they replaced it for its "factory defects"
P.S. Some stuff I learned was that I damaged the usb port.
GOOD LUCK
Sent from my beloved EVO 4G
rpierce said:
My phone is rooted and i cannot enter the custom recovery menu. I can get to the dx recovery. Tried sbf but rsd lite nor my pc will recognize the phone. PC says that the driver cant be located in bootloader menu even tho i do have the moto drivers installed. any suggestions on how to get it to work to run the sbf. I've tried all delete options in recovery menu probably screwed myself.
Click to expand...
Click to collapse
a trick to get into clockworkmod recovery, turn the phone off and plug into the wall, try to turn on....well not really try, turning on the power button should boot to cwm
I have a paperweight and are in desperate need for help.
I was running 2.1 and rooted using the birdman method. So finally decided to upgrade to GB.
RSD Lite 4.9 - everything but text messaging was working on .602
Reflashed with .340 - text messaging not working but all apps worked fine.
Upgraded to RSD 5.4.4 and now my phone is a paperweight. SBF gets to the very last step and fails. Error switching phone to BP Pass through mode (0x70BE)
So go back to RSD 4.9 and try to flash sbf - same error
Created a linux cd to try and sbf GB.
Can't post links so world wide web dot droidxforums dot com slash droid-x-sbf slash 23638-linux-solution-your-windows-rsd-lite-problems dot html
It appears to complete with no errors, the flash completes, the cd boots into linux.
Now my phone is stuck at Bootloader 29.01. Can't do anything. I can access recovery but wipe, cache, factory reset just brings me back to the bootloader screen.
Bricked in need of help
heres the problem. i was running shuji rom on rooted gb.596. attempted to full sbf back to 3.3.340 after sbf completed successful i was unable to access recovery. i tried holding power and home button, but all i get is a android with exclamation point inside a box. tried holding search button as i usually do. but i can not wipe data or factory reset. Ran rsd lite 4.8 with full sbf 3.3.340 again and im still stuck at the sturdy click logo(custom boot logo). i would greatly appreciate any advice. or a link to wipe data from my computer.
Macificient said:
heres the problem. i was running shuji rom on rooted gb.596. attempted to full sbf back to 3.3.340 after sbf completed successful i was unable to access recovery. i tried holding power and home button, but all i get is a android with exclamation point inside a box. tried holding search button as i usually do. but i can not wipe data or factory reset. Ran rsd lite 4.8 with full sbf 3.3.340 again and im still stuck at the sturdy click logo(custom boot logo). i would greatly appreciate any advice. or a link to wipe data from my computer.
Click to expand...
Click to collapse
U might try pushing the power button instead of the search button when the droid and exclamation mark are on screen. Hope that helps
TappaTappaTappa
sanjeeva7 said:
I have a paperweight and are in desperate need for help.
I was running 2.1 and rooted using the birdman method. So finally decided to upgrade to GB.
RSD Lite 4.9 - everything but text messaging was working on .602
Reflashed with .340 - text messaging not working but all apps worked fine.
Upgraded to RSD 5.4.4 and now my phone is a paperweight. SBF gets to the very last step and fails. Error switching phone to BP Pass through mode (0x70BE)
So go back to RSD 4.9 and try to flash sbf - same error
Created a linux cd to try and sbf GB.
Can't post links so world wide web dot droidxforums dot com slash droid-x-sbf slash 23638-linux-solution-your-windows-rsd-lite-problems dot html
It appears to complete with no errors, the flash completes, the cd boots into linux.
Now my phone is stuck at Bootloader 29.01. Can't do anything. I can access recovery but wipe, cache, factory reset just brings me back to the bootloader screen.
Click to expand...
Click to collapse
U might have a corrupt file missing something... try downloading the sbf file from droidmodderx's website he's got sbf for froyo and gb
TappaTappaTappa
Did you upgrade through SBF, or OTA?
What is your bootloader version?
Sent from my DROIDX using XDA App
You can try the .602 sbf linux boot disk found HERE
It works every time for me and on any computer (that can boot from a cd)
D.
sounds like, judging by your bootloader version...you may be needing to find the 2.1 sbf, flash to that, take the OTA to gingerbread.... and you may have a little more luck with current roms once your bootloader is 30.0#
Just SBF. That will fix your trouble. Almost Impossible to "Brick" the DX.
good night friends!
I'm here asking for this help not for lack of looking for the solution, sorry my bad english, I'm from Brazil and I
defy caught in a bootloader, I tried almost everything I found here in the forum, but most of the problems is
reset solved by making the recovery, but in my defy the recovery does not open, the flash works only power + vol up, already
I spent several roms to no avail, could someone help me run my recovery? grateful heart
list of roms flashead
JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P011_A010_HWp3_Service1FFJORLA_U3_3.4.2_107-7_R02_SIGNED_USAJORDMR1B15CLABRLA019.0R_JORLAFROCLABRLA_P009_A008_M002_HWp3_Service1FF.sbfz
JORLA_U3_3.4.2_107-7_R02_SIGNED_USAJORDMR1B15CLABRLA019.0R_JORLAFROCLABRLA_P009_A008_M002_HWp3_Service1FF.sbf
JRDNEM_U3_2.34.1_DEBLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA02B.0R_USAJORDANRTCEE_P029_A019_HWp3_Service1FF.sbf
JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA030.0R_USAJORDANRTFR_P043_A010_HWp3_Service1FF.sbf
JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA035.0R_USAJORDANRTHKTW_P021_A015_HWp3_Service1FF.sbf
JRDNEM_U3_3.4.2_117-002_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB035.0R_USAJRDNFRYORTGB_P003_A002_HWp3_Service1FF
JRDNEM_U3_3.4.2_164-003_VFBLUR_SIGN_SIGNED_USAJRDNEMARAB1B8VFFR03A.0R_PDS03C_USAJRDNFRYOVFFR_P028_A014_M004_HWp3_Service1FF.sbf
Motorola_Defy_Nu___Android_2.2_FroYo
shadow_defy_2.3.3_85_Orange
If you turn it on while holding "dolume down" do you get the android+! screen? Some go into recovery if you touch the bottom right corner of the screen, but on some you have to hold volume up + down together. I had this problem today!
If you actually can't get to the screen with the android+! then I don't know what else you could do :-(
mmec2 said:
If you turn it on while holding "dolume down" do you get the android+! screen? Some go into recovery if you touch the bottom right corner of the screen, but on some you have to hold volume up + down together. I had this problem today!
If you actually can't get to the screen with the android+! then I don't know what else you could do :-(
Click to expand...
Click to collapse
I really can not, no way to go to the screen with the robot android! he goes right on the logo motorola M!
can it be hardware problem?
1) Did you use the correct flasher? rsd4.9 with motorola driver installed properly.
2) If (1) not working, you could use motorola own service update from their site.
farsight73 said:
1) Did you use the correct flasher? rsd4.9 with motorola driver installed properly.
2) If (1) not working, you could use motorola own service update from their site.
Click to expand...
Click to collapse
I'm using motorola rsd 4.9 with updated drivers, what happens is install the rom normal after reboot gets stuck in the Motorola M logo, the software update site does not recognize my phone, do all these roms that I would be no my phone?
im tried this roms now
JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA030.0R_USAJORDANRTFR_P043_A010_HWp3_Service1FF.sbf
JRDNEM_U3_3.4.2_117-002_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB035.0R_USAJRDNFRYORTGB_P003_A002_HWp3_Service1FF
JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_USAJORDANRTGB_P026_A007_HWp3_Service1FF
3.4.3_11-Stock.UKTmobile_BLUR
but no results!
don't worry about it, dude.
maybe you can try the way followed:
1.power off your defy;
2.remove the battery from the phone;
3.plug the usb cable into the phone without battery;
4.open RSD and chose one of the roms your listed, but 3.4.2-177-005 NORDIC prefered,
5.take the battery into your phone, now your can see the "connected" on RSD;
6.click the "start" button to flash;
7.wait the phone reboot completely, usually it'll reboot.
if not reboot, remove and on your battery, power on your phone, then press the "volume - and power" botton together, you can enter the robot screen, press volume up and down botton together, usually you can enter the recovery, then chose wipe 3 and 4, totally you can save your defy~~
Be sure to have enough battery while flashing..
Get the phone into bootloader (hold volume down when switch on) and flash an SBF like one from the list you've attached using RSD lite. Surely you have used RSD Lite before?
It seems you have the same issue I have on my Defy as per this thread: http://forum.xda-developers.com/showthread.php?t=1095444
I’m also unable to get into recovery or get to the Android Robot screen using “Power + Volume Down”. Hopefully we will be able to figure it out and get this issue fixed.
jdearauj said:
It seems you have the same issue I have on my Defy as per this thread: http://forum.xda-developers.com/showthread.php?t=1095444
I’m also unable to get into recovery or get to the Android Robot screen using “Power + Volume Down”. Hopefully we will be able to figure it out and get this issue fixed.
Click to expand...
Click to collapse
This same friend, I have the same problem, is this a hardware problem? I move the roms but not normal
Vol I login recovery - + Power key
http://forum.xda-developers.com/showthread.php?t=966537
Try flashing nordic, if fails arabic, if fails, 2.3.3, if fails probably corrupt nand broken hardware.
Before and after every flash always try to access recovery (volume down) and WIPE. reboot and wait crossing fingers, if it fails to boot flash next sbf, try to go recovery + wipe; reboot, cross more fingers; if fails to boot try next sbf and repeat.
The reason for this is that you can flash a lower version but it wont boot, so you have to flash a higher and higher version until you get one that works.
I tried to help someone with this problem before to no avail!
Everyone who is saying just wipe in recovery, or just flash with RSD blah blah blah, need to understand that he CAN NOT access recovery and HE HAS flashed multiple roms using RSD 4.9, read the OP. Im convinced this is physical hardware failure or similar. We all know the drill to recover our precious defy's in the event of semi-brick ie: bootloop or corrupt code. However this is more than a semi-brick. We are talking about successful flashing and still no access to recovery and infinite M logo!
I walked more than one person with this problem through every known procedure to bring these phones back. Even using sbf_flash for linux doesn't work as this is the only way I flash anymore I don't bother with RSD anymore. The thing is it DOES FLASH SUCCESSFULLY just no recovery or boot!
zyxwvut said:
I tried to help someone with this problem before to no avail!
Everyone who is saying just wipe in recovery, or just flash with RSD blah blah blah, need to understand that he CAN NOT access recovery and HE HAS flashed multiple roms using RSD 4.9, read the OP. Im convinced this is physical hardware failure or similar. We all know the drill to recover our precious defy's in the event of semi-brick ie: bootloop or corrupt code. However this is more than a semi-brick. We are talking about successful flashing and still no access to recovery and infinite M logo!
I walked more than one person with this problem through every known procedure to bring these phones back. Even using sbf_flash for linux doesn't work as this is the only way I flash anymore I don't bother with RSD anymore. The thing is it DOES FLASH SUCCESSFULLY just no recovery or boot!
Click to expand...
Click to collapse
OMG Exactly!!!! i have same problem and nobody seems to be able to tell me what to do, they keep saying same thing about trying various SBF's and Vol down + power method. No matter what SBF file I successfully flash with, i cannot get into boot recovery mode.
I have heard before from desperate users that they were able to revive their phone by flashing a full 2.3.4 sbf. This however comes with downsides of not being able to downgrade to froyo by flashing ANY froyo sbf's. There is a way to downgrade back to froyo but its a dirty method. Even after downgrade you can't just flash a sbf, you will always need to restore nandroid and flash fixed sbf
This is wife's phone. I was doing regular App Market updates for her installed apps. After they were complete got an error message, don't remember exactly what, but rebooted... Phone then went into a boot loop... It would boot all the way up to the lock screen then reboot again. I went in and wiped both cache's with no success. Went back into recovery and did a set factory defaults and now I am dead in the water...
I get to the Bootloader screen and it tells me Err:A5,69,35,00,27 and I have done everything but stand on my head to fix. I have re-SBF'd from multiple computers, using different SBF versions, driver versions, and RSD Lite versions including multiple bootable Linux CD's with embedded SBF. All resulted in getting the darn ERR:A5,69,35,00,27.
The only way I ever got anything different was to flash 1.13.604 and then I got an error message Err:A5,70,70,00,1F.
After that, if I SBF the newer version, I go right back to original error.
I tried a suggestion from another thread to download the system and full sbf files for 340. I flashed the full, got error... Then flashed system, still get error.
I am using RSD Lite 5.4 on Vista 32 with UAC disabled (full admin mode), latest Moto drivers as of this post. Again, I have tried all of the versions of bootable linux SBF's as well. All yield the same result.
Wife's phone, she is very unhappy with me, and if I don't get her back up and running, I guess I will be dropping $500 on a new phone, as she is still under contract. If Mama ain't happy, I sure ain't getting any! LOL!
It seems to me that you've tried everything possible.
Your best bet now would be to take it to Verizon, if it's still under warranty.
Sent from my DROIDX using XDA App
Out of warranty by 2 months.
I actually have two of these phones, and I was able to figure some information out here. I wanted to see if I could get my working Droid X into Stock Recovery, and low and behold it wouldn't go in either. I did some searching around and found that some ROM's were wiping out the stock recovery. I found this file dxgb_recovery_patch.zip and downloaded it and flashed it in Clockwork Recovery and that fixed the Stock Recovery on my working phone.
However, since my wife's Droid X is bootlooping, I can't access Stock Recovery or Clockwork Recovery. I feel like I am chasing my tail here. I need to wipe the data/factory reset, but I can't get there because I don't have Stock Recovery. I can reinstall Stock Recovery if I have Clockwork Recovery, but I don't have Stock Recovery to install Clockwork Recovery... Round and round I go...
There absolutely must be a way to get the Stock Recovery reinstalled from the state I am in.
what rom was the phone running when you had the original issue?
Apex 2.0 RC4
Good ROM, but it appears to torch stock recovery. I ended up having wife call and plead stupidity with Motorola. They are exchanging phone.
Still don't feel bad. Would have been able to fixed If they would unlock the damn billiard.
I have the same Problem with my Defy+ what can i do?
I have the exact same issue. Have tried all the sbf methods, still getting the error :A5,69,---, I was on MIUI prior to this. When I boot the phone back up I get the motorola M but then it brings me right back to bootloader and the error. I'm guessing stock recovery is gone.
Anybody find a fix to this yet. I am about to go back to Verizon, but wanted to fix it myself if at all possible, cause I have had my phone for a year and a half so I doubt they will help me out and don't have the money for a new phone right now.
Are you holding down Home and both volume buttons with power at boot to get to stock recovery?
*I have had several phones and don't remember exactly so you may have to hold Home and vol- only.
Jiggity Janx said:
Are you holding down Home and both volume buttons with power at boot to get to stock recovery?
*I have had several phones and don't remember exactly so you may have to hold Home and vol- only.
Click to expand...
Click to collapse
Yes, on the droid x its just home and the power button release the power button when you see the m and then you hit search once the droid pops up. Instead of seeing the droid it takes me to the bootloader screen with the above error message. The way to bootloader is volume button camera button and power. Which that still works and I have tried several sbf methods with none working. I didn't know if it was an issue that may have been mentioned above about the stock recovery being missing now since I was on MIUI 2.1 wizards verison. I didn't know if there was a way to get stock recovery back on the phone cause sbf doesn't seem to work. I really have no clue at this point. But full disclosure I have done quite a few sbf's and this is the first time I've ran into such an issue. Thanks again for any help.
Apologize ahead this is so long. I just wanted to update anyone just in case they ran into the same error that I did earlier. The Err:A5,69,35,00,27 on the bootloader 30.04 screen. I finally got an sbf to stick. About 30 sbf's later (no exaggeration) and 3 different nights of working on it. Honestly persistence just ended up paying off. Anyone else can chime in here if they know why it worked so its not so grueling for the next guy/gal and major props to 1kds who gave me a couple different suggestions and for making this awesome way to sbf. The linux disc didn't end up working for me in the end but it may have if I kept at it, because that is the way to go if you can (way easy to run), Also may have worked if I did the linux disc on a different computer. I started on MIUI 2.1 (Wizards vers) but previous to that the latest android vers I was on was 602, friday night my phone died and for some reason wouldn't charge in the morning or boot up. I had a spare battery with about 50% charge on it, so I used that to try and turn on the phone and I got the red M then the error message on the bootloader screen mentioned above. I ran the linux disc on my windows 7 (64bit) machine for all the currently downloadable files (froyo, 596, 602, 602root). Kept getting the err:a5,69...
Ran RSDLite on the Windows 7 machine (my current vers was 4.8, but then upgraded to 4.9) then 5.4.4 and also 5.6.4 (latest on the rsdlite motosbf site). I tried both froyo .340 and gingerbread 602 files on all these versions and even the .596 gingerbread which I had never been on. Nothing worked and I had gone through my second battery at this point. Then I figured I would try my Windows Vista 32 bit Laptop that never had rsd lite on it or the drivers. So Downloaded 5.4.4 (found this to be the one favorable for the 602 flash per the forums) and the motorola driver and sbf'd again both the froyo .340 and the gingerbread 602 file. Still getting the same error. Every third sbf or so I would even start getting a code corrupt error. The flashes actually failed every now and then and then sometimes they would show finished and the phone would still show the s/w update screen (I just did a battery pull and would sbf again at this point). After each sbf tried getting into stock recovery Volume down, home, and power button and each time I would get an error and/or go back to the bootloader screen. I also tried just home and the power button.
What worked!!! - Not sure why but my last sbf I did was the 602 still on the laptop running Windows Vista 32 bit since I thought that would work on the rsd lite 5.4.4 (credit here to droidmodderx and 1kds). It still showed the Err:A5,69,35,00,27 after the sbf finished and it tried to boot (i did get the red m, but then went to that error page again). Battery pull, turned back on and then error page on bootloader 30.04 again. I held the home, volume down, and power button for about 1-2 minutes = same result. Held Home and Power button = same result with error. Tried the home, volume down, and power one more time (still same result). Battery pull again, waited a few minutes and just tried to turn on and it got past the red m to the droid eye!!!! It did bootloop, but I battery pulled and tried to reboot since stock recovery hadn't been working. Same thing, bootloop, so I tried the stock recovery again (home, volume down, and the power button) and stock recovery came up. Hit the search button then did the factory reset. I couldn't believe it and like I said not sure why/how it worked (maybe the multiple attempts to get into stock recovery). All I know is 4 days later it works now and I thought all was lost!!! Of course again wouldn't have been able to do this without 1kds or these awesome forums! Thanks again and sorry so long, but hopefully this helps someone else!
Back on the X!
Hi,
I am using cynogenmod 7.1.0 RC 1.5 -jordan
I am stuck in Google logo why playing with recovery.
I read that I need to flash with sbf in boot to get back to normal
I have a problem since I am in 2.3.5 how can flash
with JRDNEM_U3_3.4.3-36-1.7.sbf
This isn't the above sbf is 2.3.4 ?? or I am missing something ?
I have got this sbf from defy wiki
http://forum.xda-developers.com/showthread.php?t=1093352
I have another question how can I CG version ?
sparkriver said:
Hi,
I am using cynogenmod 7.1.0 RC 1.5 -jordan
I am stuck in Google logo why playing with recovery.
Click to expand...
Click to collapse
Do these steps:
Auris 1.6 vvt-i said:
You are stuck in bootloop since you didn't do a clean wipe before flashing the SBF.
Press and hold Vol- and Power button. When you get to the android with yellow exclamation mark, press Vol- and Vol+ simultaneously and then wipe data/cache.
Done!
If I was getting a dime every time I have given this solution, I'd be driving a Ferrari by now
Click to expand...
Click to collapse
sparkriver said:
I have a problem since I am in 2.3.5 how can flash
with JRDNEM_U3_3.4.3-36-1.7.sbf
Click to expand...
Click to collapse
You can't. 2.3.5 is BL6 (I believe) and you want to go back to a BL4 sbf - no way.
did all you have said .
cleared cache and clear data still not booting beyond google logo
what to do now ?
"I have pressed stock recovery when I end up like this"
one more thing blue light appears and than all the below touch button flash once..
Since I can't go back and flash above sbf.
with what can I flash ??
Questions go in the Q&A section
sparkriver said:
one more thing blue light appears and than all the below touch button flash once..
Since I can't go back and flash above sbf.
with what can I flash ??
Click to expand...
Click to collapse
2.3.5 is Gingerbread kernel based and CM 7.1 - Froyo-based (as far as I can remember). Since you see the blue light, this means you have access to the boot menu and recovery mode, so just flash a GB kerne-based ROM and your phone will be fine. You can flash MS2Ginger by Walter79, for example, or you can flash Quarx's CM9 ICS builds (follow my tutorial in Defy General section)
Struck at the google logo. Nothing works after that. Tried with rsd but battery went down and unable to load Sbf.
Please help out
sunil_defy said:
Struck at the google logo. Nothing works after that. Tried with rsd but battery went down and unable to load Sbf.
Please help out
Click to expand...
Click to collapse
I too have this problem few weeks ago when I try about 6 ROMs.
I remember I forgot to wipe data and dalvik at the time of installing WIUI ROM and I have different recovery play with.
So just do one ... 1. In the recovery section go to the custom recovery and try wipe cache, and dalvik and them reboot.
2. If above step doesnt work them at the time when mobile starts .. then you see blue light glowing for some seconds ,,, when you see it press " volume down button ". you see again a stock recovery menu. In that do wipe cache and dalvik and then reboot.
In the 2nd method at the time of recovery if you see cant mount cache before wiping then may be you have to do RSD Lite procedure.
RSD lite and SBF :- http://forum.xda-developers.com/showthread.php?t=1093352
it a simple procedure. Just follow steps and you come with your official foryo 2.2.2
After that you can again install custom ROM.
Because it happens to me also. My phone shows me that there is no space in my mobile i.e phone memory is full.
So so RSD lite procedure and again back to froyo and then again install 4.1.1. jelly bean and now everything work good.
About a month ago I installed a clockwork based recovery app from the market. I tried restoring and this failed leaving the phone unbootable.
Since then I have tried flashing MANY other sbf`s using rsd lite but this has made the situation worse. I think that I even flashed one for the defy+
Now all I get is either a blank screen or a M logo when I switch on.
Pressing power & volume down doesn`t work so I can`t access the stock recovery menu
I can access the bootloader using power & volume up so i can flash more sbf`s but I`ve tried most of them but none will boot.
BTW the phone was running cm7.1 before I had all this trouble and the battery has been fully charged (in another defy)
Is there any way I can clear off all the stuff I`ve been installing and start from fresh? or can anyone tell me how to get the phone to boot?
I have searched for a solution in the forums but most of the replies involve clearing the cache which I cant do as I cant get to the recovery menu.
Any helpful comments will be gratefully received
many thanks
Jeff H
Your flashs complete with Finish/Pass, or just "please manually power up this phone"?
If it's the later, read this http://forum.xda-developers.com/showpost.php?p=38187413&postcount=2
Just stick to the most highest Defy+ sbf build, or just use DFP-231 build to be sure.
intemptesta said:
Your flashs complete with Finish/Pass, or just "please manually power up this phone"?
If it's the later, read this http://forum.xda-developers.com/showpost.php?p=38187413&postcount=2
Just stick to the most highest Defy+ sbf build, or just use DFP-231 build to be sure.
Click to expand...
Click to collapse
Thanks for the reply
I flashed the DFP-231 sbf file as you suggested but it wouldn`t boot any further than the M logo.
I did get the "please manually power up this phone" message and followed the procedure from the link you gave
I can`t wipe the as I cannot get to the recovery menu.
Is there any other way to wipe the cache?
JeffH
Nah, no other way than stock recovery for stock rom.
Just make sure your flash finished with Finish/pass, that'll make your stock recovery working again.
Wish you a best luck.
i flashed with this:
DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
but still no boot
Is this the correct rom?
cheers
JeffH
I wonder if the following might give someone a clue about whats wrong with my defy
If I flash gingerbread rom either defy or defy+ then rsd completes with PASS, and phone will boot as far as the M logo and I can access the menu with power+volume UP
If I flash below gingerbread then rsd doesnt complete but gives `manually reboot` message. If I then power off and plug in again then rsd completes with PASS but when I reboot there is NO M logo and no menu on power and volume up.
I`m keeping my fingers crossed that I will be able to revive my phone.
JeffH
With DFP-231 rom, how about power+volume down to boot into stock recovery? I think you're just one step away from reviving defy.
intemptesta said:
With DFP-231 rom, how about power+volume down to boot into stock recovery? I think you're just one step away from reviving defy.
Click to expand...
Click to collapse
No, Power + volume down doesn`t work, (ie nothing happens). Only power + volume up works.
Try this http://forum.xda-developers.com/showthread.php?t=1595013
Vicsa said:
Try this http://forum.xda-developers.com/showthread.php?t=1595013
Click to expand...
Click to collapse
Thanks, but it didn`t work. Still stuck at M logo. Obviously I couldn`t clear the cache before and between flashing
JeffH
Thank you all for your helpful advice.
I have now sent the phone away for repair.
I spoke to the technician on the phone and she reckons it needs dismantling and a jtag repair (whatever that is).
But beware an app on the market, I think it is called orange backup, as it was after installing this and trying to restore the backup that I screwed up my phone!
JeffH