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.
Related
I flashed a GB full sbf mistakenly while testing out an early build of CM9 on my green lens defy, I then followed the downgrade method listed here I forgot to wipe the cache before flashing the downgrade rom mentioned in the first step and after flashing the downgrade rom was left with no functioning google apps. I tried using the terminal emulator to install clockworkmod but am unable to enable read write because I can't type numbers. The phone rooted fine and I have tried wiping in the stock recovery several times and have also reflashed the downgrade rom several times to no avail. I was able to successfuly flash one of the 2.34 chinese roms and boot and root it fine but after flashing the downgrade rom experianced the same issue.
Current system information
system version Blur_version.0.0.1.MB525-nightly.T.Mobile.en.US
Firmware Version 2.1-update1
Baseband Version 3gsmepu93a_u_93.00.2bl
Kernel Version 2.6.29 [email protected] # 1
BPflex Version GM1CP1250JORDAN250AA031
APflex Version GAS_NA_JORDANTMO_P010
Build Number umts_jordan-eng 2.1-update1 Jordan_U3_97.21.51_GNPO 1307943892 test-keys
I am perfectly alright with a working 2.2 or anything with green lens camera support but I have been unsuccessful thus far, any help is greatly appreciated
Thanks
Sean
did you get any solution
i am also facing same problem
anantyende said:
did you get any solution
i am also facing same problem
Click to expand...
Click to collapse
May be it work you.
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade+froyo
Hey guys,
would-be first time rooter here. Couple of questions. Sorry if they answered somewhere, could not find where. Basebands and kernels are not covered for dummies in any guide.
1. My phone is X8, E15i, baseband M76XX-TSNCJOLYM-53404006, kernel 2.6.29, build version 2.0.1.A.0.47, 2.1-update1. PC companion does not want to update it any further and since in every rooting guide is stated i need the last version, i am not sure what to do. Here is stated that the last version is 2.0.2.A.0.24. But nowhere it's said if I would have to have in installed already or the flashing process does it for me. So do I just download Baseband 006 - kernel 2.0.2.A.0.24 and use it with flashtool?
2. Is 015 better / newer version than 006? Lots of custom stuff requires 015. Lots of threads refer to 015 as to the latest baseband and from what I've read if I flash 015 over a 006 device I will brick it or infinite loop it. Does this mean I am stuck forever with the 006 and cannot use GingerDX for example?
General explanation of basebands / kernel stuff will be GREATLY appreciated.
thanks in advance.
don
You need xxx015 baseband to run custom ROMS correctly. Download the latest firmware, unpack it to firmwares folder inside Flashtool installation folder (default C:/flashtool). Flash it and you should get newest baseband. This will erase all your data so, make a backup of important stuff. Then use toolbox to root your phone and obtain recoveries. Then pick your favorite ROM, unlock bootloader (if you don't worry about warranty, but read guides in general and android development section to avoid hard brick) flash required kernel and have fun If you have problem with bootloops perform a full-wipe in recovery.
To enter xRecovery tap back button repeatedly on Sony Ericsson's logo.
To enter ClockworkMod tap the screen. On custom kernels tap back button.
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
Hi Everyone,
Problem:
Unable to flash:
RSD Lite reports:
Failed Flashing Process.Failed Flashing Process. Unable To Retrieve Interface Handle. (0x7027)
Question(s):
How do I prevent this error from occuring so I can flash my phone?
Is there a problem with my SBF file?
Does the phone need to have more space? (the SD card only has about
Background:
I am trying to replace the stock OS on my Motorola Defy with CM7.
However the CM7 documentation says 2.2.2 Froyo is needed, and the phone currently has 2.1-update1 so I have to first flash the SBF to 2.2.2.
Phone Specs.
Technology: UMTS
Software Version: JRDNEM_U3_2.59.0EPU93ST2_U_03.0E.02
Flex Version: UCAJRDNEMARAB1B80AA035.0R
Bootloader Version: 0910
DRM Version: N/A
Baseband Version: EPU93ST2_U_03.0E.02
I believe this is the Green model, as I checked catlog to check the camera logs, there are a few entries starting with:
LibSOCCa....
I am following these instructions:
[GUIDE] All-in-One Defy Beginner's guide
Link: http://forum.xda-developers.com/showthread.php?t=1216982
I have rooted it some time ago, using ADB and verified with the superuser app and titanium backup that it works so I'm skipping the root step.After some digging I found the following SBF:
Official Froyo 2.2 (2.2.2) SBF for Telstra Australia.
Thread link:
http://forum.xda-developers.com/showthread.php?t=1179381The SBF file had a really long name, so I renamed it to Froyo2.sbf, and moved it into D:\
Next I downloaded and installed RSDLite 5.7.
It recognises the phone just fine when it is plugged in under the normal mode, but not if I boot it into bootloader mode manually (power + up).
So I figured I'd try using it in the normal mode.
When I hit: Start -the phone reboots into bootlauncher, but nothing happens for a while.
Then RSD Lite reports:
Failed Flashing Process.Failed Flashing Process. Unable To Retrieve Interface Handle. (0x7027) I'm not sure where I am going wrong.
The phone boots back into its normal operations afterwards, so I haven't got it stuck/bricked.
Apologies if I haven't given enough information to understand what is going wrong.
Please let me know and I'll be happy to add any extra screendumps etc.
I have done a search but couldn't find a similar issue in these forums for the Defy
Open rsdlite, then connect the phone in bootloader (volume up+power) mode. Select the file and then click start.
Sent from my MB526 using xda app-developers app
---------- Post added at 06:01 PM ---------- Previous post was at 06:00 PM ----------
Make sure you have the latest drivers and rsdlite. Get rsdlite 6.1.
Sent from my MB526 using xda app-developers app
Hey all,
Yes, i have read all the sticky Threads about this Theme, and also the Guide about this issue, but its doesnt work....
I have a Samstung GT-I9505
Android: 4.2.2
Basicversion: I9505XXUDMGG
Kernel: 3.4.0-1220396
[email protected] #1
Wed Jul 31 00:14:26 KST 2013
Buildnumber: JDQ39.I9595XXUDMGG
I flash yesterday my Note 8.0 with the same issue, but than i found a CWM Version for Odin and its works, but not here.
At first, i dont wipe my data before the install rom... thats the reason?
I install CWM_6_Touch from the board via Odin v3.09 and try to install this Customrom via recoveryboot (boot with keycommand) => cm-10.2-20130914-NIGHTLY-jfltexx but everytime i geht the "signature verification failed" error. I also try to install the ADAM Kernel, but i cant. I find only .zip files, and no file i can use with odin. I installed the ROM Manager from the Playstore but i also cant install anything with it.
1. At first, i want install the Infamous_S4_Kernel.v4.6_OC Kernal
2. Install the CM-10.2 ROM
Can anybody give me a detailed instruction (pleaes no gobbledygook) what i have to install or wich file i have to flush? You can also send me a PM in German or contact me at skype ([email protected]). I think its more easy at germen for me
Br Lex
Hi again,
So little update, for all other that find this thread via search function.
The Problem, its not possible to install a custom Rom, with the Samsung default Recovery-Mode. At fist i dont see a different and think i boot on CWM but there is a Problem on some phones. There is a bad script on /system/etc/insall-recovery.sh that overwrite your custom recoverymode.
Thats why, i cant install a ROM
Root your Phone, delete the .sh file and install the CWM again via Odin and install your CustomROM :good:
PS: sad, that nobody can write it easy that all can understand it. Everybody speak from e3, e2 and some other special shortwords.