10 replies to this topic

[ozzie9-0]

im runnng ubuntu, and i installed the sdk and when i run the commands to root the phone i get this issue:
oscar@oscar-MM061:~$ cd sdk/tools
oscar@oscar-MM061:~/sdk/tools$ ./adb push rageagainstthecage-arm5.bin /data/local/tm
87 KB/s (5392 bytes in 0.059s)
oscar@oscar-MM061:~/sdk/tools$ ./adb shell
$ chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
/data/local/tmp/rageagainstthecage-arm5.bin$
[*] CVE-2010-EASY Android local root exploit © 2010 by 743C

[*] checking NPROC limit ...
[+] RLIMIT_NPROC={2048, 2048}
[*] Searching for adb ...
[+] Found adb as PID 11410
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
$
oscar@oscar-MM061:~/sdk/tools$ ./adb kill-server
oscar@oscar-MM061:~/sdk/tools$ ./adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
oscar@oscar-MM061:~/sdk/tools$ ./adb shell
$ mount -o remount,rw /dev/block/mtdblock1 /system
mount: Operation not permitted


can anyone please help me?? i do not know what im doing wrong i keep getting  operation not permitted and i have repeated the steps several times. i need to leave 1.5

[Turl]

You should get '#' (root prompt) and not '$' when you run adb shell the second time. You need to try again until you see #, then you can continue with the steps.

[ozzie9-0]

ive been trying all night and still havent been able to make the # show up. im extracting both folders that need to be downloaded to the platform-tools folder where adb is located. anyone have any advice?

<p> </p>
<div>oscar@oscar-MM061:~$ ./adb kill-server</div>
<div>bash: ./adb: No such file or directory</div>
<div>oscar@oscar-MM061:~$ cd sdk/platform-tools</div>
<div>oscar@oscar-MM061:~/sdk/platform-tools$ ./adb kill-server</div>
<div>oscar@oscar-MM061:~/sdk/platform-tools$ ./adb start-server</div>
<div>* daemon not running. starting it now on port 5037 *</div>
<div>* daemon started successfully *</div>
<div>oscar@oscar-MM061:~/sdk/platform-tools$ ./adb shell</div>
<div>$ mount -o remount,rw /dev/block/mtdblock1 /system</div>
<div>mount: Operation not permitted</div>
<div> </div>
<div>this is the message i keep getting</div>

[Turl]

Try doing it on your phone; the idea is basically the same but instead of adb shell you use Connectbot for instance. See here for a guide, it's for windows users but you'll notice the files are the same, the commands are the same, the only difference is that you use connectbot or so to run the exploit and get root.

http://modmymobile.c...om-windows.html

Edited by Turl, 28 July 2011 - 06:24 PM.

[ozzie9-0]

Thanks will try tonight

[samikrc]

I am in the exact same position as OP. I also followed the suggestion and used the steps in modmymobile and using ConnectBot. That helped me get the # prompt (which means I am technically rooted), but I can't do su. If I run the 'su' command, I get the following message:
bionic/linker/linker.c:1581 | ERROR: 1435 could not load 'libbinder.so'
bionic/linker/linker.c:1641 | ERROR: failed to link su
bionic/linker/linker.c:1741 | ERROR: CANNOT LINK EXECUTABLE 'su'

After some research, I found out that the package for su provided in the wiki is meant for 2.1, and not for Android 1.5, which is what I have on my phone right now when I am trying to root. I need the cupcake/donot version (cd version) of SuperUser.

I need to proceed on that, and might need some help, in which case I will post here.

[npiper]

Can you use superoneclick?

http://forum.xda-dev...ad.php?t=803682

[cbowley603]

I am pretty sure that I had this problem and flashing a recovery other than clockworkmod fixed it. Try that, you can reflash it again later after you flash a rooted rom.

[jenkinbr]

I'm running Mint and I had no problems gaining root. I (for the most part) followed the steps given here (again, aimed at windows users): http://theunlockr.co...cliq-xt-quench/

Note that for me, I had to do 'sudo ./adb start-server' on my machine so that the adb daemon was running as root.

Also, the files provided on that page worked for my CLIQ XT running 1.5 on the first try (after I resolved the permissions issue with adb)

Edited by jenkinbr, 11 October 2011 - 02:08 AM.

[baseballfanz]

I try a few methods and non seems to work, used One click root and got root in about 30 seconds

[snohio]

I had the same issue too.. I think it is due to the existing version of Android on it. One Click didn't work for me either.. I found this instruction set out there http://www.gomonews....ndset-to-froyo/ which worked for me. I used these files: http://theunlockr.co...to_MSM_Root.zip and followed the rest of the instruction set of #2. I used Terminal instead, but that is just a personal preference.

Once I finally got root, I went back to the wiki.cyanogenmod.com instruction set..

Good luck! Took me about 3 hours to get to this point.. I've rooted a G1 and G2 (mine) without nearly as much trouble. The wife is getting sick of her Cliq so she finally agreed to go to CyanogenMod. Thanks for the port guys!