Database Info

Never rooted before help?

I have finally received my OTA froyo 2.2 update. I am considering rooting to be able to use custom themes and such. I have a few questions.
What is the best and easiest method to root/unroot my 2.2 droid X?
What all do I need to download in order to successfully root?
What is deodexed? ( I keep seeing this as necessary for certain themes.)
What do I need to download to deodex my droid X?
Thanks in advance.

aplechaty said:
I have finally received my OTA froyo 2.2 update. I am considering rooting to be able to use custom themes and such. I have a few questions.
What is the best and easiest method to root/unroot my 2.2 droid X?
What all do I need to download in order to successfully root?
What is deodexed? ( I keep seeing this as necessary for certain themes.)
What do I need to download to deodex my droid X?
Thanks in advance.
Click to expand...
Click to collapse
Best way to root/unroot:
Answer: EE THIS LINK: http://www.droidforums.net/forum/droid-x-hacks/82584-droid-2-root-dx-ota-2-2-a.html
or Rootz wiki has some links if you search for it on google. I'm not sure that links are allowed here, or I would provide it.
ANSWER: There is a one click root/unroot made by Sil3ntkill (could have spelled wrong) over on alldroid.org. I have not used this method tho. I used the step by step process.
This also has the link for what you need to download as well! =)
DEODEXING:
Deodexing your phone modifies the .apk files on your phone (for the framework and services) I believe, which allows developers to then make custom themes, as these "deodexed" files can be easily modified and replaced.
How to Deodex:
I recommend just doing some searching. I think if you look in the themes/app sections of the Droid X forum here you can find an update.zip such as the following:
http://forum.xda-developers.com/showthread.php?t=793664
This is the black glass deodex method. You use the update.zip with koush's recovery and then use his back to stock method to remove the theme (black glass) that comes with the deodex process.
There are a lot of links out there that will tell you how to do the manual process. I did it manually myself, but have had a decent amount of experience with linux/command line. If you don't have a lot of experience, I might recommend using a method such as the black glass method I mentioned above.
If you are confident you can do a manual process, go for it! I think it's always more gratifying to try things the manual way... but that's just me! Hope this all helps =)

aplechaty said:
I have finally received my OTA froyo 2.2 update. I am considering rooting to be able to use custom themes and such. I have a few questions.
What is the best and easiest method to root/unroot my 2.2 droid X?
What all do I need to download in order to successfully root?
What is deodexed? ( I keep seeing this as necessary for certain themes.)
What do I need to download to deodex my droid X?
Thanks in advance.
Click to expand...
Click to collapse
Once you get rooted, check my thread out for easy deodexing... {Deodex OTA 2.2}

EASY ROOT WITHOUT ADB
you will need:
*rageagainstthecage-arm5.bin
*su
*Superuser.apk
*Some sort of terminal emulator in the market.
*enable USB debugging.
Settiings -> applications -> development -> USB debugging.
* EDIT: any line below that starts with a * is optional
- open up your favorite terminal emulator program
- cd /tmp
- cp /sdcard/rage*.bin /tmp/ (without "/tmp/" worked for me)
- chmod 777 rage*.bin
- ./rage*.bin
- ignore it's output, we are thinking outside of the box here, just wait for it to finish and return a $
- now go to settings -> applications -> manage applications -> running -> terminal and force close
- relaunch the terminal app and you should be greeted with the # symbol. you now have a root shell
- the rest is pretty much the same.
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
* cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
* chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
Once your all done, go ahead and reboot your phone.
*if you decide to unroot.
- open your terminal app
- you should see a $ symbol, now do the following
- su
- now you should see a # symbol
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- rm /system/app/Superuser.apk
- rm /system/bin/su
* rm /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- reboot your phone.

i5500 Rooted, BusyBox, But Where Can We Go From Here?

OK, so got a nice shiny new Europa/i5500 today...
Yea, as you can imagine the first thing on the list was rooting. Done.
Not much you can do with just a root so thought to hell with it time to start poking around.
ADB has issues, cant remount from command line so it needs doing by adb shell > su.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Code:
dd if=/sdcard/busybox of=/system/bin/busybox
chmod 4755 /system/bin/busybox
mkdir /data/busybox
/system/bin/busybox --install -s /system/bin/
Busybox sorted!
But now what is there?
Had a poke around and there seems to only be one thread regarding the phone (which tbh is quite nippy considering its size and has some potential).
Doe's anybody have any sort of information on building custom roms from AOSP for this? What kind of drivers need to be sorted?
I hate to think that the most we will ever do to this little gem is custom themes since for it's size it is a damn impressive bit of kit as far as my experience has been so far...

:Update:
I wasn't keen on the apps drawer not being alphabetised so tried pushing TouchWizz30Launcher.apk from Vibrant which was suggested for for the Fascinate and it works perfect, heads up for anyone else who has this niggle.
Apps2SD also works fine but had to partition SD using PC since no parted available on phone...
Strike that, Market Icon is now missing from AppDrawer... reverting back to stock lol

Missing something?

Im a seasoned flasher. When I originally flashed my G2x I read the entire wiki for CM on my device (http://wiki.cyanogenmod.com/wiki/LG_G2x:_Full_Update_Guide).
Anymore when I see people asking for howtos and guides to flashing their phone, members often reply a short set of steps...more or less
Flash CWM
Backup stock image
Download ROM
Boot into CMW recovery
Wipe
Flash zip
When I did it, i was using ADB to manually push downloaded files (su, psneuter, busybox) and set permissions as instructed by the wiki
Code:
adb push busybox /data/local/
adb push psneuter /data/local/
adb push su /data/local/
adb shell chmod 777 /data/local/busybox
adb shell chmod 777 /data/local/psneuter
adb shell
/data/local/psneuter
adb shell
mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
mkdir /system/xbin
/data/local/busybox cp /data/local/su /system/xbin/su
chown 0:0 /system/xbin/su
chmod 6755 /system/xbin/su
ln -s /system/xbin/su /system/bin/su
exit
adb push Superuser.apk /system/app/Superuser.apk
Etc etc...and quite a bit more.
Have i missed something?
Has the flashing process evolved to the point were these steps are no longer needed?
If so, why is the wiki not updated?
More importantly, if not, why are the steps as outlined on the wiki not being included as direction, or more simply, why is not the wiki referenced when people ask for directions?
Any benefit or drawbacks to one method over the other?
Im just asking out of curiosity. Thanks in advance.

I haven't a clue as to why the wiki even has those directions cause if you, say have a bad download, flash a rom get into a boot loop you will need then go back and flash CWM through NVflash as there will be no way to access recovery except through adb probably... So just ignore the wiki page, like I said I wonder why they have it like it that, maybe I'm not seeing something but that way just seems pointless and too much work lol...

Yeah... just read the sticky guide on these forums.

Looks like the steps you have are for rooting your device. The beauty of this device is that it ships with an unlocked bootloader and doesn't need to be rooted in order to flash a custom recovery image and start flashing ROMs. The only way I would think the long method should be used is if you really needed root before flashing new ROMs, such as to backup your apps from your stock ROM with Titanium Backup or a similar situation. But, in terms of just getting to the point of flashing ROMs, there is no reason to root this device.

As well, when I got mine the wiki said to flash CWM via ROM Manager, which is not the way to do it.

you are leaving /system as read write. Should return it to read.
mount -o remount,r -t ext3 /dev/block/mmcblk0p25 /system

[Q] roo Desire S without bootloader unlock?

Can it be done?
I tried de Superoneclick method and it did not worked.
But also i tried with another program "unclockroot 2.3.1" ad the thing is that after i run it and before i reboot phone i have shell root "#" but nothing of superuser or SU on the phone.
Could it be possible, after i have "#" to change R/W previligies on system folder and install superuser.apk and SU through adb commands?
which ones are the adb commands to perform?
And can anyone send superuser.apk and the proper su to install?
Many thx for all the help.
D_Saint

The method to root Desire S without unlocking bootloader is described at least in 5 places, in General and Development forums, and involves downgrading the firmware. Please read.

did not find any that suites my needs.
And believe me i searched, i have been reading about this in the past 2 weeks....
Can you please send me the links?
I found these commands:
# mount -o remount,rw -t rfs /dev/block/st19 /system
# exit
adb push busybox /system/bin
adb push su /system/bin
adb install Superuser.apk
adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
adb reboot
Are they correct?
Thx again.

what we are saying is that for now u cant root d latest hboot 2.0.0.xx u have to downgrade 1st or use d XClip hardware to permanently unlock n root ur desire s
cheers

No, the commands are incorrect, because the root you're seeing is only temporary, and the thing that protects /system from being written to is not just R/O mount. There is a HW protection that needs to be unlocked to be able to write to /system, otherwise everything you do will be gone after rebooting. I said - please read, and I meant it. If you want pointers - google "how S-OFF was achieved on G2" and then read.
Index of everything in Development:
http://forum.xda-developers.com/showthread.php?t=1443636
Look for "downgrade HBOOT without using HTCDev unlock". There are 3 guides there.

[Q] Impossible to use ls -t from BusyBox

Hi,
Sorry if it's not the good forum, I have looked for the good one but I'm not very easy with English.
I want to sort out files by date in directories to delete automatically oldest backup files with a script. I have Cyanogenmod 11 on a Samsung Galaxy S2. I have installed Busybox (Stephen Stericson) on my phone from the Playstore to use the command ls -t because in standard we have only ls and ls -l. But when I tape ls -t, I have an error message "Unknown option". I've tried with Cyanogenmod 12 but I have the same problem.
I would want to know if ls -t doesn't function in BusyBox or if I have another problem.
Thank you.

No response :crying: .
Can somebody tell me if he haves a BusyBox which enables to use the command and which is this BusyBox : ls -t?
Thank you .

Are you sure you are using busybox?
try running: busybox ls -t

Ok, I have to type "busybox" first. I will try it, thank you.

Ok, it works when I add "busybox" in the command . I'm just a little surprised, I had understood the busybox commands replaced the shell commands.

You can also add: busybox sh
to your script and after that you could easily use ls -t without busybox.

Ok, thank you but it's not annoying to add "busybox". I don't create a lot of scripts .
Now I try to solve the problem to move files to the sdcard. It worked fine in 4.1.2 but with Cyanogenmod 11, I have a cross device link. I tried also "cp -p" to keep initial attributes but I have "Operation not permitted".