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
We have an incorrect SBF for Defy+ DEFYPLUS_4.5.1-134_DFP-125_45.0.1250.MB526.NonEFIGSRetail.en.EU which has incorrect bootloader.
And we have a correct SBF file Defy+ 4.5.1-134-DFP-125-CEE.
With MotoAndroidDepacker we can extract (or repack) sbf file and then we get some smg files.
The CG39.smg contains the "system". This CG39 file is a simple image file, we can mount it under linux: mount -o loop CG39.smg /mnt
Is it possible to modify SBF file, and get a working NonEFIGSRetail.en.EU?
i downloaded and i want to try because i have a sbf file where the wifi has very good signal+no market and one that is newer and has market but the wifi is terrible weak signal. pls help, what to switch?
Modding sbfs is impossible because the locked bootloader checks that every sbf that is flashed/booted is signed by Motorola. If we change anything in the sbf, then we break the signature and we won't be able to boot. That's the reason why we can't play around with the kernel, which is something we'd all love to do.
CM7 + CM9 double boot
crakeron said:
Modding sbfs is impossible because the locked bootloader checks that every sbf that is flashed/booted is signed by Motorola. If we change anything in the sbf, then we break the signature and we won't be able to boot. That's the reason why we can't play around with the kernel, which is something we'd all love to do.
CM7 + CM9 double boot
Click to expand...
Click to collapse
Just searching for a way to "mod" my Pro Plus, and i bumped into this discution.
I want to try a modify a sbf file to flash it via RDS Lite ( we have no modded recovery or so for the Motorola Pro Plus ).
My question is this: Can't you try and "fake" motorola's signature on the sbf file. Or can you try and bypass the check for the signature?
mereTz said:
Just searching for a way to "mod" my Pro Plus, and i bumped into this discution.
I want to try a modify a sbf file to flash it via RDS Lite ( we have no modded recovery or so for the Motorola Pro Plus ).
My question is this: Can't you try and "fake" motorola's signature on the sbf file. Or can you try and bypass the check for the signature?
Click to expand...
Click to collapse
Well, you can't fake or bypass the signature, but you CAN modify an SBF file to some extent without touching the signature. See this thread:
http://forum.xda-developers.com/showthread.php?t=1097754
I installed 2.3.6 sbf via rsd lite and didnt quite understand what i was doing from there i bricked my phone but managed to get it working, is there any way at all that i can go back to 2.2?
If you flashed fixed sbf the answer is yes. For more info on this see this thread
so which are the fixed sbf's?
MotorolaDefyLuke said:
so which are the fixed sbf's?
Click to expand...
Click to collapse
This is a copy/paste from thread I mentioned above:
DOWNGRADE
If you come from Android 2.1 and never flashed Android 2.2 you can use the fixed sbf-files method. With this method you will have a option to downgrade to you personal stock Android 2.1 via direct sbf flash.
- First download nandroid backup and normal sbf file of you favourite rom.
- build your own fixed sbf:
- depack sbf-file with MotoAndroidDepacker and delete cg31.smg and cg39.smg
- repack sbf-file (MotoAndroidDepacker)
- install nadroid backup
- flash repacked sbf-file (this one without cg31/cg39)
More information: http://forum.xda-developers.com/showthread.php?t=945035
This is how you can make a fixed sbf - that's how fixed sbf looks like. If you flashed a full sbf then you can't downgrade no more.
Advice: read read read
thanks for the help
So yeah, I tried rooting my Defy+ but it failed in every try I did:
First I tried the tutorial on the CM Forum (for installing CM7) but it didn't work.
Second I tried SuperOneKlick and similar tools but all failed.
Third I searched in Google very much but only found ways with Flashing the ROM.
My problem now is:
1. I don't want to flash another ROM
2. I wan't to root my Phone for apps e.g. AdBlocker
My Versions and Numbers:
System Version: 45.0.2310.MB526.Retail.en.DE
Baseband Version: EPU93_U_00.60.03
Kernel Version: 2.6.32.9-ge281 b6e [email protected] #1
Build Number: 4.5.1-134_DFP-231
(dunno what you need or not)
So is there any way that I may have overseen to root my Defy+? (Without flashing a different ROM?)
just here http://forum.xda-developers.com/showthread.php?t=1542956&highlight=root+231
Edit: Only way is to flash them 2 roms as you have chosen the 231 version which is the latest one with no downgrades so you have to only use that version or higher (when it comes out)
Try this stock rooted rom.Just flash it via rsd lite!
I send the download link because i cant post link directly!
maybe to add im not that advanced^^ have no idea what you are talking about
can i also directly flash CM7 via rsdlite?
ok i tried to flash those thingys but rsd lite was unable to open these things saying me invalid filetype
what are you trying to flash? if you are using the link I sent you use the CEE versions (second one) As the CN one you have to flash 3 files instead or the 2 on the CEE one.
I have flashed that may times and it always works you might have to extract the .SBF file out of the zip folder. The RSD lite I have will do it for you but not sure if the older versions do.
So I unlocked bootloader and rooted my phone with magisk using CMD.
Now I can not update it anymore, and flashing old boot file bricks it so it works only on magisk_boot.img file.
Is there any way to flash it back to original state and full stock?