yeah, root works

hii devs i need ur help!!!! rooted my defy plus as u mentioned in first post...then installed 2nd init 2.0 apk...but my defy plus nt going cyanogen mod boot logo, so i again flashed gb kernel zip ...but phone showing bootloader error....plz need ur urgent solutionn..

CM7.2 maniac103 nightly
Problem solvedd

better

---

hi friends,

I can not get to see defy the rsd lite version 3.9, however, sees only when running the flash tells me I FAIL I installed the driver 5.1 and 5.2 same thing that you can not do the root?There is another way to build 231?

thanks

hi.
u must use RSD Lite 4.4 or higher .
thats work .

Is it possible to return the stock defy+ rom from this rooted one? Because of the possible guarantee problems.

Originally Posted by Sigray

Is it possible to return the stock defy+ rom from this rooted one? Because of the possible guarantee problems.

You can always flash your stock BL7 SBF to unroot it..

Doesn't matter from where I send it, what matters is written above

It works! THX a lot!

root any BL7

---

I'm a courious reader of the developer section and got a lot of ideas and mods for my defy+
Thanks to all that share their wisdom with us.
Now is my turn to share my improvements in rooting a BL7 image.

Acctually I just wanted my own stock image (german) to be rooted too.

What you need:
1. an already rooted Defy (the CN or CEE 4.5.1-134 DFP-231) with Custom Recovery (take the latest that does .tar backups e.g. use SndInit Defy 2.3) [to do a backup of your running system]
2. MotoAndroidDepacker - [to extract the system CM39.smg of your prefered SBF and more ]
3. a running linux (e.g. knoppix might do) - I prefer a virtual machine with opensuse - [to extract the system and recompress]
4. get SuperOneClick for the su, busybox binaries and Superonclick.apk
5. MD5 hash calculator

Steps:
I now just explain the steps in short to get the system (CM39.smg) rooted and on your phone.
1. do a backup of your rooted phone with custom recovery (I personally did a factory reset from within custom recovery before i did the backup - not shure if you need to do it to prevent crappy data to interfere with your upcomming firmware)
2. use MotoAndroidDepacker (there is a windows .Net and a linux Mono version) to extract CM39.SMG (system image) of your prefered SBF (I used the german 4.5.1-134 DFP-231 retail en.DE)
3. mount the CM39.SMG

sudo mount -o loop /tmp/cm39.smg /mnt/defy

4. copy all files to a temporary folder - the name must be system

cp --preserve=all -r /mnt/defy /tmp/system

5. copy busybox and su to /tmp/system/bin - set permissions (I think it was chmod 755 su + chown root:10001 su)
6. copy Superuser.apk to /tmp/system/app - set permissions (chmod 755 Superuser.apk + chown root:root Superuser.apk)
7. create an tar archive of your work

cd /tmp
tar cvf system.ext3.tar system

8. genarate MD5 hash of the tar file
9. copy the system.ext3.tar to your custom recovery folder with the backup, edit the nandroid.md5 file and replace the system.ext3.tar hash with the new one
10. recover the backup
-> enjoy

To get all stuff out of the prefered SBF just depack the SBF with MotoAndroidDepacker, delete cm39.smg, recompile the folder to an SBF and flash the SBF with RSDlite - actually i did this task before making the backup of my old system

Can I do it ?

---

Hi,
so I red all the topic ( yes, all 6 pages ) and I downloaded all files from the dropbox folder of Auris 1.6 vvt-i ( thanks a lot for reup ).

I'll tell you what I did previously, so you can know which is my situation:
Yesterday, before finding this awsome forum I tryed to root my device with no success
I tried in theese three different ways:

1) Using All-in-One Defy Beginner's guide ( I followed the part titled Rooting )
2) Using DooMLoRD's Easy Rooting Toolkit [v4.0] ( I used version 4 )
3) Going to shortfuse.org & using SuperOneClick 2.3.3

I fell to say that I'm quite lucky that the phone didn't brick, dye or others ( at least, a friend told me I was ).


To not risk anymore I want to ask: Can I root my device with the following specs ?
System Ver: 45.0.2310.MB526.Retail.en.IT
Modem Ver: EPU93_U_00.60.03
Kernel Ver: 2.6.32.9-ge281b6e hudsoncm@il93lnxdroid80 #1
Build Number: 4.5.1-134_DFP-231
( Model: MB256, Android Ver: 2.3.6 )




Thanks a lot for the help, & forgive me for the long post.


Edit: I almost forgot to ask: I assume that it would be better to backup everything I'm using before following this procedure, because with wiping passages I'ld throw away my stuff. Am I right ?

Sorry for bumping the topic, but it's kind of important for me to know exactly if the procedure will work on my device as it is set now, or if I'll risk to/shurely brick it.

Thanks again for your help & comprehansion.