Develop Bugs

[CDMA]HTC desire adb root uscc

first time posting to these forums and would like to contribute my findings i was able to gain root on the uscc htc desire in adb using some other guides for the evo 4g unlock. but now i need some help on how to get the modified su in the right place to make this work for the apps. these are the steps i used to gain temporary root.
1) installed android sdk to get adb
2) set up the phone in debug mode
3) downloaded the rageagainstthecage-arm5.bin file(attached)
4) ran this from the sdk folder containing adb.exe
Code:
adb.exe push C:/PATH/TO/FILE/rageagainstthecage-arm5.bin /data/local/tmp
adb.exe shell
cd /data/local/tmp
chown 0755 rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin
5) adb shell will exit retype adb.exe shell and now you have root
this is as far as i have got so far now i need to know where to put su which i could not find in /system/xbin

also i am new to the android scene so sorry if this is a bad question, but if i were to flash a recovery image of the gsm desire to my cdma would this work to enter adb in recovery mode or would this brick my phone, i didnt know if the recovery affected that or if that was the rom.

I think you need to put su and Superuser.apk on you sdcard (adb push file /sdcard/)
Then
in your su shell prompt
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cat /sdcard/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/su > /system/bin/su
chmod 06755 /system/bin/su
Please let us know if this works.

I hope this works out!
Sent from my USCC HTC Desire using XDA App

i found out that this command doesnt actually make the system directory writeable
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
and running it a second time causes the device to reboot.
any sugetions to make it writable, im willing to work on this, but like i said i have no experience with android although i am very familiar linux.

You are aware that while booted into Android the /system is not writeable?
You have to boot into recovery mode to do this.

i am now, i tried the method for the incredible but it seems to not run adb on bootup at least after about 15 tries it didn't work, any suggestions? is there a way to flash the recovery without effecting the radio or rom because there isn't any roms for this phone as of yet, or could you point me in the right direction to start my research on how to write a rom? would it be the same as rolling your own linux distro?

also though this to be worth mentioning there seems to be no su file currently on the phone.

i got some time this morning to dig around in the payload-update.zip files for the incredible and was wondering if i could use this to install su because it looks like it doesn't flash anything (atleast looking at the script it looks like it doesn't, i cant say that for the binary file what does that do?) just wondering if there would be any adverse affects by applying this in recovery.

It might be worth talking to AmonRA, or Koush (I believe he works on Clockwork Mod) for a custom recovery. As for installing superuser, you could try the unrevoked team. (unrevoked.com) I wish I knew more in terms of development to help but I hope this leads you in the right direction.

blitz2190 - Here is a link to Superuser.apk and su. Link
I think you need to put su and Superuser.apk on you sdcard (adb push file /sdcard/)
Then
in your su shell prompt
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cat /sdcard/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/su > /system/bin/su
chmod 06755 /system/bin/su

I am very interested to know how this works out. If you need anyone else to help test things let me know. I am not a linux buff, but i can follow commands...

CreepingDeath said:
I am very interested to know how this works out. If you need anyone else to help test things let me know. I am not a linux buff, but i can follow commands...
Click to expand...
Click to collapse
Do you have a USCC Desire?

northmendo said:
Do you have a USCC Desire?
Click to expand...
Click to collapse
Yes I do, and I am willing to help out where I can.

CreepingDeath said:
Yes I do, and I am willing to help out where I can.
Click to expand...
Click to collapse
A couple q's fof you.
Do you have a Mac or PC?
Do you have adb installed?

I will help if I can. I have the phone and a Mac and don't have adb installed.
Sent from my USCC HTC Desire using the XDA App

dhh93 said:
I will help if I can. I have the phone and a Mac and don't have that apply.
Sent from my USCC HTC Desire using the XDA App
Click to expand...
Click to collapse
Cool first install adb. Follow these instructions to install it on Mac.
HERE

Ok doing that right now.

dhh93 said:
Ok doing that right now.
Click to expand...
Click to collapse
Great. I would start by trying the the method from the first post give me about 5 mins and I will post them in a mac friendly format.

Ok will wait on that

[GUIDE] How to Root the Motorola Xoom

Article found on BriefMobile!
1. Download the Motorola Xoom Root Zip file and unzip it. Download
2. Place the files in the SDK Tools folder.
3. adb reboot bootloader (You can skip the next 3 steps if you’ve unlocked with fastboot previously)
5. fastboot oem unlock (wait for reboot)
6. adb reboot bootloader
7. fastboot flash boot rootboot.img
7. fastboot reboot (wait for reboot)
8. adb remount
9. adb shell push su /system/bin
10. adb shell ln –s /system/bin/su /system/xbin/su
11. adb shell chmod 4755 /system/bin/su
12. adb push Superuser.apk /system/app
Thanks for the hard work Koush! His website

Awesome. Let's get a boot image to make roms
Sent from my DROIDX using Tapatalk

Are we gonna be able to undo this when we send them back for the upgrade?

Ok I have rooted a few times via ADB and have no idea what steps 5-7 mean. What does fastboot oem unlock mean? And what does number 7 mean,,,in english for us dummys please LOL
5. fastboot oem unlock (wait for reboot)
6. adb reboot bootloader
7. fastboot flash boot rootboot.img
7. fastboot reboot (wait for reboot)

camblue said:
Ok I have rooted a few times via ADB and have no idea what steps 5-7 mean. What does fastboot oem unlock mean? And what does number 7 mean,,,in english for us dummys please LOL
5. fastboot oem unlock (wait for reboot)
6. adb reboot bootloader
7. fastboot flash boot rootboot.img
7. fastboot reboot (wait for reboot)
Click to expand...
Click to collapse
You have to type those commands in your adb command window.

yes, fastboot is a tool included with the android sdk just like adb
it has somewhat different functions though

smaskell said:
yes, fastboot is a tool included with the android sdk just like adb
it has somewhat different functions though
Click to expand...
Click to collapse
Ok so question,,,, i downloaded the files, should i take them out of the xoomroot folder and place in the sdk tools folder or the folder itself?
also do i unzip the rootboot zip?

camblue said:
Ok so question,,,, i downloaded the files, should i take them out of the xoomroot folder and place in the sdk tools folder or the folder itself?
also do i unzip the rootboot zip?
Click to expand...
Click to collapse
put those files with the sdk tools. rootboot shows a disc image to me. i would leave that alone

socomdark said:
put those files with the sdk tools.
Click to expand...
Click to collapse
Ok i dont mean to be difficult but does that mean take them out of the xoomroot folder and place all three of them individually into the sdk tools folder? thank you!

everytime i try
adb shell ln –s /system/bin/su /system/xbin/su
i always get a link failed no such file or directory but i just pushed su to the system/bin folder... any ideas on whats going on?

http://www.koushikdutta.com/2011/02/motorola-xoom-rooted.html
It's from Koush!

Update: I dont think that the command shell should be in step 12?
2 things. Fastboot was not included in my fresh download of the 3.0 SDK tools.
I grabbed it here:
http://developer.htc.com/adp.html#s2
And second, with the newest Android 3.0 SDK, at step 12, pushing the su file, I recieve:
push: not found
If I go into adb-shell and type "push" I recieve the same error?

I got the moto dev drivers & 3.0 sdk and can do push / pull.

lasphyxial said:
everytime i try
adb shell ln –s /system/bin/su /system/xbin/su
i always get a link failed no such file or directory but i just pushed su to the system/bin folder... any ideas on whats going on?
Click to expand...
Click to collapse
On same step...even looked and su is in the first folder.

camblue said:
Ok i dont mean to be difficult but does that mean take them out of the xoomroot folder and place all three of them individually into the sdk tools folder? thank you!
Click to expand...
Click to collapse
oh sorry, yes take them out of xoom root folder and into sdk tools individually.
koush made a mistake on one of the instructions and had fix it so the op wont be entirely accurate. use instructions from koush's site

This is what i did, and i just deleted the 2 games that come with the tablet.
1. # Download the XOOM root zip.
2. # Unzip the package.
3. # Put your junk in the box.
4. adb reboot bootloader (skip the next 3 steps if you have already unlocked via fastboot)
5. fastboot oem unlock
6. # wait for reboot
7. adb reboot bootloader
8. fastboot flash boot rootboot.img
9. fastboot reboot
10. # wait for reboot
11. adb remount
12. adb push su /system/bin
13. adb shell ln –s /system/bin/su /system/xbin/su <<i didnt do this step, instead i did 13. adb push su /system/xbin
14. adb shell chmod 4755 /system/bin/su
15. adb push Superuser.apk /system/app

Here you go

thank you very much! Has anyone did this with success yet?

camblue said:
thank you very much! Has anyone did this with success yet?
Click to expand...
Click to collapse
I think the real question is once the bootloader is unlocked and system rooted, will unrooting and re-locking the bootloader be detected by motorola when sending it in for the 4glte upgrade???

camblue said:
thank you very much! Has anyone did this with success yet?
Click to expand...
Click to collapse
I did, but i changed one step...look up 2 post.

[GUIDE] How to Unroot Bell Desire Z

Hello,
I've had a few requests for help unrooting the Bell Desire Z for warranty purposes.
If you've noticed, there isn't a specific guide for us Bell users, while T-Mobile customers have like a dozen guides scattered around. I figured this out and I should share it.
The really tricky part was figuring out how to get rid of superuser.apk and also get s-on and Bell's CID in the right order, but it turns out it's simple haha. Unfortunately there was not guide for me, so I had to figure this out trial and error and piecing it together from other random posts. I'm not a dev/hacker (well, maybe now I am a novice hacker), so it was a big deal for me (lol) and I can relate to the frustration that comes from not having a good resource.
The exact build my phone shipped with was 1.34.666.5 and other phones may have shipped with other builds, but I've determined that the way Bell operates is that they send their phones to a 3rd party repair facility, and they don't check this (or don't care). However, they may still check whether or not the phone is rooted. So let's unroot it.
DISCLAIMER: Do your own research. I am not responsible for anything bad that happens to your phone after this point (but I will take credit for your success!! ). I used this method successfully and everything worked great. But proceed with caution. If you are unsure, do some looking around. CHECK YOUR MD5 SUMS! Easy MD5 is in the market, and is great.
0. If you have flashed a new radio, flash the old radio back. This one:
http://www.mediafire.com/?9cb8a7jwxob8o6r
NOTE: I'm leaving specific details out of this because if you don't know how to do this, that means you haven't done it before, and you don't need to do this step, and should probably avoid flashing new radios anyway.
1. Download this file:
https://rcpt.yousendit.com/1317004046/ea1de40db3968b867573327c903231bf
-unzip it, and place the folders in /sdcard/clockworkmod/backup/
(recovery will check the md5 sums for you)
2. Reboot into recovery (assuming you have the clockworkmod recovery).
-Do a factory reset (yes, you will lose all your apps etc if you didn't back up)
-Choose Backup/Restore, Advanced Restore, Stock DZ System, System.img
-Choose Backup/Restore, Advanced Restore, Stock DZ Boot, Boot.img
-Reboot
3. Download
http://dl.dropbox.com/u/15272013/Flash Recovery Files.zip
Unzip those files to the root of your sdcard.
PLEASE CHECK THE MD5 of recovery.img AFTER you have unzipped it and placed it on your sdcard!! Sometimes if you check an md5 on your pc and then copy it over, you could still have an error, and then you'll be in a bit of trouble!
md5 of recovery.img: id5d280af717f9afd7ce1c3285c129bc
4. Download the following file:
http://cmw.22aaf3.com/common/gfree_07.zip
md5 (of entire folder): 6916cf05b0805aeac9effdc1725aaa12
unzip and place the file gfree on the root of your sdcard
3. Install Terminal Emulator from the Market. This all needs to be done in the same Terminal Session. Type
$su
#mount -o remount, rw /system
#cp /sdcard/flash_image /system/bin/
#chmod 777 /system/bin/flash_image
#/system/bin/flash_image recovery /sdcard/recovery.img
#cp /sdcard/gfree /data/local/tmp/
#chmod 777 /data/local/tmp/gfree
#rm /system/app/superuser.apk
#/data/local/tmp/gfree -s on -c BM___001
Now when you reboot your phone, you will have an unrooted phone, stock. For clarity, you have:
-Stock, Unrooted Bell ROM 1.34.666.5
-Stock, Matching Radio
-S-Off HBoot
-Proper Bell CID
-Superuser.apk nowhere to be found
The only loose ends are that flash_image will still be in your /system/bin and if you flashed the eng hboot, your hboot number may not match. I'm 99.9% certain nobody at the repair facility will look or care about it. Also, I'd prefer you avoid flashing your hboot, since that is singly the most risky thing you can do with your phone.
If anybody knows whether the flash_image binary works in /data/local/tmp, let me know and I'll edit the post.
Note: when you get your phone back, it will have the latest GB RUU on it. This will give you a bit of trouble re-rooting it. There is no way around having them flash the latest firmware on it, since it's the very first thing they do before they diagnose your phone.
Thanks to Football for information on shipped builds and mxpxboi for his rooted 1.34.666.5 nandroid files.
Cheers!
JT

jontornblom said:
3. Install Terminal Emulator from the Market. This all needs to be done in the same Terminal Session. Type
$su
#mount -o remount, rw /system
#cp /sdcard/flash_image /system/bin/
#chmod 777 /system/bin/flash_image
#/system/bin/flash_image recovery /sdcard/recovery.img
#cp /sdcard/gfree /data/local/tmp/
#chmod777 /system/bin/gfree
#rm /system/app/superuser.apk
#/data/local/tmp/gfree -s on -c BM___001
Click to expand...
Click to collapse
Thanks for the help jontornblom. Quick question:
I am receiving the error message saying /system/bin/gfree no such directory.
Any Tips?

Merzennary said:
Thanks for the help jontornblom. Quick question:
I am receiving the error message saying /system/bin/gfree no such directory.
Any Tips?
Click to expand...
Click to collapse
Did you accidentally type a "/" after gfree?
Sent from my Nexus 6 like tears in rain.

good job - thx for this guide

jontornblom said:
$su
#mount -o remount, rw /system
#cp /sdcard/flash_image /system/bin/
#chmod 777 /system/bin/flash_image
#/system/bin/flash_image recovery /sdcard/recovery.img
#cp /sdcard/gfree /data/local/tmp/
#chmod777 /system/bin/gfree
#rm /system/app/superuser.apk
#/data/local/tmp/gfree -s on -c BM___001
Click to expand...
Click to collapse
There are a couple of small typos in this code. In the second chmod there should be a space between "chmod" and "777". More importantly though, that second chmod should be on "/data/local/tmp/gfree" since that's where it's been copied
Sent from my Desire Z running CM7.

steviewevie said:
There are a couple of small typos in this code. In the second chmod there should be a space between "chmod" and "777". More importantly though, that second chmod should be on "/data/local/tmp/gfree" since that's where it's been copied
Sent from my Desire Z running CM7.
Click to expand...
Click to collapse
Thanks! Sorry about that =( I will edit the OP
Edit: okay, typos fixed. My apologies to anyone who ran into trouble because of this.
Sent from my Nexus 6 like tears in rain.

jontornblom said:
Hello,
1. Download this file:
...yousendit.com/1317004046/....3968b867573327c903231bf
-unzip it, and place the folders in /sdcard/clockworkmod/backup/
(recovery will check the md5 sums for you)
Click to expand...
Click to collapse
Could someone re-upload file from step 1?

Hi,
I too could use the file from Step 1. And there is a little urgency as I need to get my DZ back to stock as soon as possible.
Your help is appreciated...greatly!
Thanks.

[Q] Root gn gsm 4.0.4

Hey guys,
I flashed the 4.0.4 factory image today and was wondering how i can get root access without flashing a custom recovery since i want to stay stock atm.
I already tried the method i usually used (on 4.0.1 & 4.0.2)
Sorry can't post links... it's the normal method with fastboot and adb
and another method where you fastboot cwm recovery and then use adb commands but both didn't work for me
I can't post links so that's what i did there:
Temporarily boot into the Clockwork Mod Reovery using fastboot (on the computer)
fastboot boot cwmt-recovery-5.8.0.2.maguro.img (or whatever version you are using)
Mount /system using Clockwork Mod (on the phone):
mounts and storage -> mount /system
Chmod su using adb to turn on the setuid bit (on the computer)
adb shell chmod 6755 /system/bin/su
adb shell chown root:root /system/bin/su
adb shell ls -l /system/bin/su (permissions should now be -rwsr-xr-x)
Reboot. Super user should be working as expected (and your stock recovery is still intact)
Anyway,
I already spent much time to search on this forum and google so i was wondering if anyone knows any method which i could use.

You can root using this toolkit http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my GNex {GSM} T-Mobile

Mojochief said:
Hey guys,
I flashed the 4.0.4 factory image today and was wondering how i can get root access without flashing a custom recovery since i want to stay stock atm.
I already tried the method i usually used (on 4.0.1 & 4.0.2)
Sorry can't post links... it's the normal method with fastboot and adb
and another method where you fastboot cwm recovery and then use adb commands but both didn't work for me
I can't post links so that's what i did there:
Temporarily boot into the Clockwork Mod Reovery using fastboot (on the computer)
fastboot boot cwmt-recovery-5.8.0.2.maguro.img (or whatever version you are using)
Mount /system using Clockwork Mod (on the phone):
mounts and storage -> mount /system
Chmod su using adb to turn on the setuid bit (on the computer)
adb shell chmod 6755 /system/bin/su
adb shell chown root:root /system/bin/su
adb shell ls -l /system/bin/su (permissions should now be -rwsr-xr-x)
Reboot. Super user should be working as expected (and your stock recovery is still intact)
Anyway,
I already spent much time to search on this forum and google so i was wondering if anyone knows any method which i could use.
Click to expand...
Click to collapse
Download this file to /sdcard, boot CWM like you posted, and then, once in CWM, flash the file you downloaded. Done.
EDIT: All that file does, is copy su and Superuser.apk to your device and set the appropriate permissions.

You can root using this toolkit http://forum.xda-developers.com/show....php?t=1392310
Sent from my GNex {GSM} T-Mobile
Click to expand...
Click to collapse
Thanks I'll try it, but I'm actually not a big fan of one click thingies where you don't know what you're doing.

Download this file to /sdcard, boot CWM like you posted, and then, once in CWM, flash the file you downloaded. Done.
Click to expand...
Click to collapse
Thank you I really prefer that over toolkits!

Mojochief said:
Thank you I really prefer that over toolkits!
Click to expand...
Click to collapse
This is what that file does:
Mounts the system parition
Copies Superuser.apk to /system/app
Copies su to /system/xbin
Sets permission on Superuser.apk to 0644
Sets permission on su to 06755
Sets a symlink for /system/xbin/su to /system/bin/su
Unmounts the system partition.

This is what that file does:
Mounts the system parition
Copies Superuser.apk to /system/app
Copies su to /system/xbin
Sets permission on Superuser.apk to 0644
Sets permission on su to 06755
Sets a symlink for /system/xbin/su to /system/bin/su
Unmounts the system partition.
Click to expand...
Click to collapse
Just tried it and it worked just fine
And thank you for the explanation!
So actually you could do it w/out booting cwm just with fastboot+adb right?

Mojochief said:
[snip]
So actually you could do it w/out booting cwm just with fastboot+adb right?
Click to expand...
Click to collapse
No. You need root access on boot to execute those commands. CWM boots android with root access by default, so this allows you to execute the commands. If you do not use CWM, you can use any other boot image that gives you root access on boot.

No. You need root access on boot to execute those commands. CWM boots android with root access by default, so this allows you to execute the commands. If you do not use CWM, you can use any other boot image that gives you root access on boot.
Click to expand...
Click to collapse
Yeah i meant with another boot image which gives you root access, like the one i used to root the earlier builds.

Mojochief said:
Yeah i meant with another boot image which gives you root access, like the one i used to root the earlier builds.
Click to expand...
Click to collapse
Yes, you can use another insecure boot image, but it needs to be a 4.0.4 compatible kernel. Older ones won't work.
Sent from my Galaxy Nexus using Tapatalk

Made a horrebile mistake while changing permissions.

Hi guys, as I wanted to change a permissions in my /system/lib directory, I accidentally disabled the "Execute"-Permission for my /system/lib folder. I know, im stupid as ****. I usually am not that dumb.
Currently, my G3 (855, 32gb) is only booting in recovery. I'm looking for a solution to change the permissions of the /system/lib folder, but it seems impossible.
Thanks for every single advise!

Use adb with recovery booted and then:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 644 /system/lib
It should work

oposiasty said:
Use adb with recovery booted and then:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 644 /system/lib
It should work
Click to expand...
Click to collapse
Thank you for your answer, but I think I'm not able to configure it via ADB. It isn't recognized in recovery, and when I'm putting it into that ADB Update mode, ADB just says "error: closed"...

RichiN said:
Thank you for your answer, but I think I'm not able to configure it via ADB. It isn't recognized in recovery, and when I'm putting it into that ADB Update mode, ADB just says "error: closed"...
Click to expand...
Click to collapse
wich recovery do you have? TWRP or stock?

KingOfDope said:
wich recovery do you have? TWRP or stock?
Click to expand...
Click to collapse
Thank you too. I had stock recovery installed. I had BusyBox installed and could have changed the permissions via script, but I decided to
flash stock and unlock my bootloader afterwards. Everything went fine, so we can consider this thread as solved.