[ROOT] Universal Cliq and Dext rooting method (Safe: Won't break 3g)

[agarciajavier]

perfect, it was my error. I read the instructions wrong. Since I have root access and I'm ready to put android 2.1. Thank you very much

[tonymy01]

Anyway, I'm not being able to remount (adb remount) and replacing a recovery.img (using Flash the recovery: adb shell flash_image recovery /sdcard/recovery.img). Thats the only way I learned to make a ROM flash, but I can't remount or flash a recovery from the cmd.

And when I run getprop ro.secure at adb shell shows me "1", so is it rooted or not? I even tryed rooting it again, but still nothing.
Really sorry for the noob questions.

I think this doesn't change the ro.secure to 0 (as that would require altering the boot.img file and reflashing that file), it just temporarily makes the shell not realise this value was originally 1, so gives you temporary root access. This enables you to install the su application (as you can write to /system with temporary root access), which, when run after you have installed it, will give you root privs once you run su. You will probably find once you reboot the phone, you will get a $ prompt for adb until you type "su". So this is good enough anyway, as all apps that require root ask the operating system, and now the su app is installed, will grant or deny properly.

So adb remount will not work actually, to remount the system as rewritable. If you have adlxmod-2 running you can type rwsystem in adb shell, or go to adb shell and type:
su
mount (to have a look at how your system is mounted now, it may be a different mtdblock)
mount -o remount,rw /dev/block/mtdblock1 /system
<<make whatever /system changes here>>

flash_image recovery /sdcard/blah.img

In other words, you have to get into a adb shell, and then type su, and then run the various commands, rather than try to run privileged commands with adb shell blah.

Regards

[mgrobledo]

Im stucked... ive done everything its said without any problems...

I have # in the connectbot com line but when i try to do:

$ flash_image recovery /sdcard/xxxxx.img

it returns the next error:

error writing recovery: permission denied

both from comp or from phone, same problem.

i tryed to do an

adb shell
cd system
$ rm recovery.img

and got:
rm failed for recovery.img, Read-only file system


So i rly think this is not working on my motorola dext movistar at all.

Any suggestions?

[tonymy01]

You have the $ prompt, this is NOT root. You need to type "su" to get root from the $ prompt, assuming you installed the su app ok when you used this rooting method of running the rageagainstthecage exploit+subsequent superuser.apk install.
/system is never normally mounted as rw. You have to remount it to get it rw. Only su/root user can remount the drive. Either get root explorer (great file manager app that supports root access of the filesystem and remounting /system rw etc), or type:
adb shell
su
mount (this will show you current mounts, in case mdtblock1 is not what /system is mounted on)
mount -o remount,rw /dev/block/mtdblock1 /system

*then* you can make system changes (of course if you run a 3rd party rom that flashes a new boot.img, this will make ro.secure=0 and so adb will be proper root so commands like adb remount will work, and adb shell flash_image etc. Otherwise you will need to adb shell, su, then type the commands.
Regards

[mgrobledo]

I got # after su and mount showed that it is right, but still cant install any rom or do flash_image recovery ... im not usin any mod rom, its why i want to do this so i can use phone with something else than 1.5

If i try to:
# rm recovery.img it says i cant, read-only file system... tho flash_image recovery seems to work, just another # shell line to keep working, so please something that can help me install the 2.1 rom posted in this forum in my phone from what im stucked?

[tonymy01]

The system partition is *never* writeable unless you REMOUNT it as rw, I gave the instructions how to do this. Hint, it needs to be writeable to allow deleting too. Use the root explorer app to make the linux things a thing of the past for linux command line newbs.

As for 2.1, once u have a custom recovery on the phone, you can flash any new community provided fw if it is provided as a zip u flash from the custom recovery. So that is all u need to do, veify u can boot to the new recovery and flash your fave/chosen new fw zip.

Not all phones have a recovery.img file in /system btw, my old blur 1.2.7 didn't, the 1.5.10 ota update did.

[mgrobledo]

... thank for the newb compliment but i alrdy did the remount and its rw not ro and 0 0 after so it should work and it doesnt, so.. istll saying i have to use that app ill do so, just to prove its not a problem of me being unable to type or use a shell.

[tonymy01]

# rm /system/recovery.img
your post above doesn't appear you did that? Or were you in the system directory at the time?

# ls /system
shows u what is in there, it might not even exist... u will soon find out anyway, if it doesn't exist, you will maintain custom recovery, else u will end up back to stock recovery next reboot... no dramas to su and do the flash_image command again.

[mgrobledo]

Im now with the j_r0dd recovery alrdy working, thanks, i dont know but at comp i cant ever get adb shell to grant me su/root so i tested it again on phone and after cheking i didnt had any prev img in the system folder y installed it and im currently creating a nand backup (just in case).

[tonymy01]

Sweet. Yeah, I dunno what you lose by not having the ro.secure opened up in boot.img, as I have never run rooted without that b4. I assumed you can type su like at the terminal emulator, but maybe this isn't the normal non rooted adb behaviour. maybe it is locked down thru adb still. but on the phone with Su working that is all that matters at this point since once u get a custom recovery in u can flash any rooted Rom (avoid ones with radios unless u know the radio is ok 4 your region.

[zavulon]

I rooted my phone with this method, but I can't even use anything useful like Metamorph, because it requires BusyBox, which refuses to install, saying that my phone is not "nand unlocked" (no idea what that means), and I also can't use Barnacle Wifi for some reason, it keeps stopping when I start the tether thing (if anybody know how to get these 2 to work, let me know here or in inbox). Also, I have no idea how to put in a custom recovery to my phone, so I can start flashing ROMs, so please teach me how to do that. Pretty much I rooted my phone for no reason, since I can't move on from here. Please help, thanks.

[tonymy01]

custom recovery is simple.
1. transfer fave custom recovery .img file to your sdcard, using whatever method you prefer to transfer (mount card as drive, or do adb push blah /sdcard, or take sdcard out and put into pc).
2. run, from # prompt (won't work from $ prompt): flash_image recovery /sdcard/whateverTheRecoveryFileNameIs.img
3. Done!
4. Now when you reboot, hold down the camera key when the phone boots up, and choose volume down when asked, and be basked in all that custom recovery glory.

(5. If you boot up fully once flashing it, and next time find you have a stock recovery again, you either didn't type the command right above, or you have a recovery.img file in /system you need to remove to stop it overwriting the custom one on reboot, you can follow the posts above on how to mount as rw, or use root explorer).

The rooting the phone doesn't magically add stuff to it, all it does is opens the door to let you do things. If you are trying to use packages that have certain pre-requisites for things like busybox, and don't understand that from root, you can put your own busybox in now, then I think it best you take a nandroid backup (in case you want to roll back), and then install a custom ROM that has what you need.
Once you have a custom recovery running, you can simply install the custom ROMs by choosing to update/upgrade from a zip file from the custom recovery menu, and choose the custom ROM zip file that you have transferred to the zip file.

(for those wondering why this can't be done from a stock recovery, it is because the stock recovery is looking for update.zip files firstly, and secondly requiring the files to be signed with unobtainable motorola keys. The custom recovery allows the files to be signed with test keys, and this is how all custom roms have been signed. It also gives a nicer menu interface to let you choose any zip file from the /sdcard, so you can swap from one custom rom to another relatively easily from the custom recovery menu).
Regards

[zavulon]

custom recovery is simple.
1. transfer fave custom recovery .img file to your sdcard, using whatever method you prefer to transfer (mount card as drive, or do adb push blah /sdcard, or take sdcard out and put into pc).
2. run, from # prompt (won't work from $ prompt): flash_image recovery /sdcard/whateverTheRecoveryFileNameIs.img
3. Done!
4. Now when you reboot, hold down the camera key when the phone boots up, and choose volume down when asked, and be basked in all that custom recovery glory.

(5. If you boot up fully once flashing it, and next time find you have a stock recovery again, you either didn't type the command right above, or you have a recovery.img file in /system you need to remove to stop it overwriting the custom one on reboot, you can follow the posts above on how to mount as rw, or use root explorer).

The rooting the phone doesn't magically add stuff to it, all it does is opens the door to let you do things. If you are trying to use packages that have certain pre-requisites for things like busybox, and don't understand that from root, you can put your own busybox in now, then I think it best you take a nandroid backup (in case you want to roll back), and then install a custom ROM that has what you need.
Once you have a custom recovery running, you can simply install the custom ROMs by choosing to update/upgrade from a zip file from the custom recovery menu, and choose the custom ROM zip file that you have transferred to the zip file.

(for those wondering why this can't be done from a stock recovery, it is because the stock recovery is looking for update.zip files firstly, and secondly requiring the files to be signed with unobtainable motorola keys. The custom recovery allows the files to be signed with test keys, and this is how all custom roms have been signed. It also gives a nicer menu interface to let you choose any zip file from the /sdcard, so you can swap from one custom rom to another relatively easily from the custom recovery menu).
Regards

Thank you for a detailed guide, I honestly appreciate you using your time to help, but after a while I kind of got bored so I rooted my phone the old way its kind of funny, yet I feel bad for not posting an update here, so sorry about that. Anyway, after rooting it the old way, I flashed j_r0dd's recovery, and after that his latest ROM, and now, everything works perfectly, and I'm loving it. Barnacle and Metamorph work fine now, BusyBox doesn't give me crap anymore, and everything else is great. Sorry again for making you waste your time, I was just excited to test out the whole thing + I was the reinstalling my apps the old fashioned way. Anyway, do you any stable/problem-free ROMs that you could suggest? Now that I can, I want to try a bunch of cool ROMs before settling on my favorite one.

[tonymy01]

However, doing how you have done it, has its disadvantages.
1. You lose all your original data, system, boot (as you haven't backed it up with nandroid and the various upgrade processes wipe it)
2. Won't work for 850MHz 3G people, including Bell, Mexico, Brazil, Italy! and some other markets. In fact, it will appear to work but as the radio gets upgraded (when the orange.FR firmware is installed), the phone will no longer have 3G connectivity to 850MHz WCMDMA transmitters.

Luckily for 2, there is a solution now, which is to flash the Italian 5025 Radio into the phone, that only became an solution yesterday thanks to youbaoer: http://modmymobile.com/forums/403-mo...025-radio.html

I am telling everyone here, get root using this new method in this thread here, get a custom recovery on the phone with flash_image, and then they can take a full backup (to roll back if required) and also choose any custom rom (without radio, unless you understand the implications!!) they want, e.g. J_r0dds one.

Getting the custom recovery onto the phone is the key to open the door to allowing third party roms and patches to allow to be used. Rooting using this method http://modmymobile.com/forums/399-mo...-3g-bands.html is one way of allowing you to be able to get that recovery onto the phone, with relatively little "damage". Flashing with the Orange.FR firmware http://modmymobile.com/forums/399-mo...ootloader.html is another, but with some consequences that need to be understood.

Regards

[zavulon]

However, doing how you have done it, has its disadvantages.
1. You lose all your original data, system, boot (as you haven't backed it up with nandroid and the various upgrade processes wipe it)
2. Won't work for 850MHz 3G people, including Bell, Mexico, Brazil, Italy! and some other markets. In fact, it will appear to work but as the radio gets upgraded (when the orange.FR firmware is installed), the phone will no longer have 3G connectivity to 850MHz WCMDMA transmitters.

Luckily for 2, there is a solution now, which is to flash the Italian 5025 Radio into the phone, that only became an solution yesterday thanks to youbaoer: http://modmymobile.com/forums/403-mo...025-radio.html

I am telling everyone here, get root using this new method in this thread here, get a custom recovery on the phone with flash_image, and then they can take a full backup (to roll back if required) and also choose any custom rom (without radio, unless you understand the implications!!) they want, e.g. J_r0dds one.

Getting the custom recovery onto the phone is the key to open the door to allowing third party roms and patches to allow to be used. Rooting using this method http://modmymobile.com/forums/399-mo...-3g-bands.html is one way of allowing you to be able to get that recovery onto the phone, with relatively little "damage". Flashing with the Orange.FR firmware http://modmymobile.com/forums/399-mo...ootloader.html is another, but with some consequences that need to be understood.

Regards

So even if I live in New York and have T-Mobile, there is a chance that my 3G might be lost? Guess I should back it up and revert to non-root, and do it this way again. The problem with this way is that none of the rooted application worked properly for me, and after I reboot the phone, I open ConnectBot, and it has a "$" there, instead of "#". Doesn't that mean I'm not rooted? This method is so weird for me, although I am positive I did everything right, but none of the rooted apps work right for me, they all require BusyBox, which requires a "nand unlock", so I'm stuck there. Anyway, if you think I should revert and re-root, maybe you can PM me, and we can do it more privately and in detail instead of spamming. I would appreciate it if you helped me to get the most out of my Cliq. I'm getting bored with it, so I need more from it. I can't get a new phone yet, so yeah. Anyway, PM me, thanks.

Best,

zavulon