[Q] roo Desire S without bootloader unlock? - HTC Desire S

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.

Related

Rooting the Eris

Has anyone been able to root thier Erie yet? If so how did you do it? Or can anyone point me in the right direction to get started. Thanks for the help.
I think it'll be at least a few weeks. Someone needs to get the recovery image and mod it as they did with the Hero. I think.
so is anyone working on this? if you give me instuctions i will dump my phone and post it, if that will help? i would really just like to be able to tether over wifi when needed without having to pay out the ear for it.
Is it that different from the Sprint's Hero? Try the current method...
herzzreh said:
Is it that different from the Sprint's Hero? Try the current method...
Click to expand...
Click to collapse
I'm concerned that the image from the Hero will cause problems since it's different carrier etc
The method used to root isn't carrier dependent. You probably won't want to load MoDaCo's current ROM as it is Sprint specific, but assuming the kernel build is the same you may be able to gain root with the asroot2 script.
To clarify, 'rooting' is not the same as loading a custom ROM. One begets the other, but loading a custom ROM isn't a requirement, just a door that gets opened when you gain root access to your phone.
Assuming everything else is the same on the phone, the Amon_Ra recovery bootloader should work as well.
If asroot2 works then we can flash a new recovery image, you can dump your ROM, and I can do a MCR version.
P
would i still use the recovery image that is posted for the hero? or would i stop at that step when rooting?
binny1007 said:
would i still use the recovery image that is posted for the hero? or would i stop at that step when rooting?
Click to expand...
Click to collapse
If you use the recovery image for the hero and it doesn't work, it's not usually a big deal.
Just pull out the battery to restart your phone normally. Since the recovery image is separate from the rom, replacing the first does not affect the latter.
binny1007 said:
would i still use the recovery image that is posted for the hero? or would i stop at that step when rooting?
Click to expand...
Click to collapse
Follow the rooting instructions to the letter, all the way through. Just don't flash a new rom if successful.
You can use the recovery image posted for the Hero.
ok i am following the instructions and this is what i am getting? what is going wrong?
C:\AndroidSDK\tools>adb shell
$ chmod 0755 /data/local/asroot2
chmod 0755 /data/local/asroot2
$ /data/local/asroot2 /system/bin/sh
/data/local/asroot2 /system/bin/sh
[1] Killed /data/local/asro
$ mount -o remount,rw -t yaffs2 /dev/block/mtd
mount -o remount,rw -t yaffs2 /dev/block/mtdbl
mount: Operation not permitted
$ cd /system/bin
cd /system/bin
$ cat sh > su
cat sh > su
cannot create su: read-only file system
$ chmod 4755 su
chmod 4755 su
Unable to chmod su: No such file or directory
The eris and droid can't use that exploit unfortunately, you'll have to wait until there's another way in
binny1007 said:
ok i am following the instructions and this is what i am getting? what is going wrong?
C:\AndroidSDK\tools>adb shell
$ chmod 0755 /data/local/asroot2
chmod 0755 /data/local/asroot2
$ /data/local/asroot2 /system/bin/sh
/data/local/asroot2 /system/bin/sh
[1] Killed /data/local/asro
$ mount -o remount,rw -t yaffs2 /dev/block/mtd
mount -o remount,rw -t yaffs2 /dev/block/mtdbl
mount: Operation not permitted
$ cd /system/bin
cd /system/bin
$ cat sh > su
cat sh > su
cannot create su: read-only file system
$ chmod 4755 su
chmod 4755 su
Unable to chmod su: No such file or directory
Click to expand...
Click to collapse
You guys and Bell South...sounds like Sprint had the only vulnerable CDMA version.
You guys will have to wait for a new "asroot" type file...a new exploit to get you guys access.
well that sucks, so there is no other way around this right now? Or if anyone needs a ginnie pig i am more than happy to help.
thecodemonk said:
You guys and Bell South...sounds like Sprint had the only vulnerable CDMA version.
You guys will have to wait for a new "asroot" type file...a new exploit to get you guys access.
Click to expand...
Click to collapse
That's what I thought. Hopefully since the hardware is so similar it wont take long.
Unfortunately hardware is barely a glimmer in this equation - the expliots used to gain root are software, usually kernel bugs.
Something will turn up soon.hopefully.
binny1007 said:
well that sucks, so there is no other way around this right now? Or if anyone needs a ginnie pig i am more than happy to help.
Click to expand...
Click to collapse
Just remember, while it's unlikely, any of these actions could theoretically brick your phone...be aware of the risks!
Have you attempted the flashrec method?
Drop the Recovery Image from here onto your sd card
http://forum.xda-developers.com/showthread.php?t=581521
Download the apk from here and install it on your phone:
http://zenthought.org/content/project/flashrec (download it from your phone's webbrowser and open the file...if that doesn't work, download astro file explorer from the market and try again).
Once you open flashrec, click on the "backup" link and then type in the path to your recovery image (most likely: /sdcard/recovery-RA-heroc-v1.2.3.img)
Then flash and try to reboot into recovery mode (power off, then either home+power, volume down+power, or camera+power...depends on who you ask, one of those should get you into the recovery image where you'll see an option for nandroid, that's how you'll know it was a success).
If you reboot and it doesn't work or it freezes, pop out the battery and boot normally...shouldn't hurt anything (though if you want to be more safe, I'd wait until we got the RUU for whatever carrier you're on (Verizon/Telus/etc)). Currently the Sprint RUU is the "get out of jail" card that's saved a bunch of people.
Just remember, while it's unlikely, any of these actions could theoretically brick your phone...be aware of the risks!
thecodemonk said:
You guys and Bell South...sounds like Sprint had the only vulnerable CDMA version.
Click to expand...
Click to collapse
Cellular South
thecodemonk said:
Have you attempted the flashrec method?
Click to expand...
Click to collapse
It doesn't use the same exploit as asroot2?
markachee said:
Cellular South
It doesn't use the same exploit as asroot2?
Click to expand...
Click to collapse
Sorry, Cell South, Bell south...(can you tell I'm not from around there? )
I have no idea if it does...but I figured it can't hurt to try eh? Because if it works, wouldn't that be awesome?

how to unroot my nexus s pls help

hello,
i need help to remove superuser and lock my nexus s
+after doing that should i get official updates?
i did see this topic
http://forum.xda-developers.com/showthread.php?t=879041
and i try this solution
ryude said:
You need to use adb to go in the file system and delete all trace of superuser and busybox. That is the only things rooting does, places those files on your phone and changes file permissions. File permissions, they won't look for, but I've had best buy scroll through the app drawer on multiple occasions looking for superuser/rom manager.
I have attached a zip containing all the files needed for adb. Since they no longer package adb with the sdk. Just open command prompt and cd to the directory containing adb. Make sure your phone has Usb Debugging enabled, then connect your phone.
You might need to download usb drivers in order for windows to recognize the device, but probably not. Once your phone is connected, do the following.
Code:
adb devices
adb shell
su
rm /system/app/Superuser.apk
rm /system/bin/su
rm /system/bin/busybox
rm /system/bin/rootshell
reboot
Click to expand...
Click to collapse
but when i write rm /system/app/Superuser.apk it say
Read-only file system
so what should i do i only get my XS unlock then install superuser using
install-superboot-windows.bat
and i never do recovery!!!!!!
so any help
i need to get my nexus like new and i should then gt updates
You can have superuser and get updates. The update will remove root though. You could always wait for the cm nightly to include 2.3.3
Sent from my Nexus S using XDA App
You have to mount the /system partition as read/write.
Easiest way is use Root Explorer.
You can also try the following from adb or terminal on the phone:
Code:
su
mount -o rw,remount /dev/block/mtdblock3 /system
thanks for your reply
i used Root Explorer to mount the /system partition as read/write.
and then
i did write this codes
adb devices
adb shell
su
rm /system/app/Superuser.apk
and every thing was ok
but i have an error on those lines
rm /system/bin/su
rm /system/bin/busybox
rm /system/bin/rootshell
and every time i get file not found
so what i should do???
hello, tominater12 and thank you for reply
cold you tell me how i can remove superuser and root using the update??????
i want to get my nexus s like new no root no superuser
so any one can help?
hi guys,
this is my first post in the forums, but after reading and watching many videos on how to remove it i have found a solution...my nexus s is now unrooted with no superuser...
make sure u have android sdk installed, and have usb debugging on.
restart phone into recovery
open cmd and type -
cd c:/AndroidSDK/tools/
adb shell mount /system
adb shell rm /system/app/Superuser.apk
ALL CREDITS GO TO 'TheUltraLinx' ON YOUTUBE,
who has fixed my phone to factory settings
flash oem rom and fastboot oem unlock?

[i9003][Mod] Root XXKPM without CWM

Hi everyone,
this method helps you to achieve root in XXKPM without CWM (which will be available shortly). You will need the attached files and Linux with installed Android SDK. Credits go to ChainsDD for the Superuser binary and APK and to Skin1980 for his normalboot.img repack script. This method is more time consuming than flashing CWM and more risky. Beware!
Flash XXKPE followed by XXKPM via Odin.
Flash the modified normalboot.img as PDA via Odin and do a full wipe. This enables the adb shell to run as root on the device, allows debugging and mock locations.
Now start up Linux and hook up your device to your PC. Do not forget to activate USB debugging in the settings. Follow these directions very carefully, otherwise you might have to reflash or even loose your IMEI!
Run Terminal. In Terminal, gain root access and start adb:
Code:
su
adb start-server
To be sure adb is running and recognized your device, issue
Code:
adb devices
Now the delicate part: Mount /system read-write:
Code:
adb shell
su
At this point, the "$" at the beginning of each line should change to "#". Otherwise, you're not root and can not continue.
Code:
mount -o remount,rw -t yaffs2 /dev/block/stl9 /system
exit
And now push the Superuser files to the device (I am assuming they are lying in your home directory. Otherwise, adjust the path. For example, "su" could be in "/home/user/i9003/su"):
Code:
adb push su /system/bin/su
adb push Superuser.apk /system/app/Superuser.apk
And finally set the correct permissions and remount /system read-only:
Code:
adb shell
chmod 6755 /system/bin/su
sync
mount -o remount,ro -t yaffs2 /dev/block/stl9 /system
exit
Reboot.
After this, you will typically install busybox from the market. But this is up to you. Have fun!
Thanks for the info..r we really need this?coz I've no linux on my desk
Sent from my GT-I9003 using xda premium
AmirolAhmad said:
Thanks for the info..r we really need this?coz I've no linux on my desk
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
it can be done by using command prompt in windows with adb setuped in ur pc..
Anyone tried this method?
confirmed this method works
@g5abiera: I sure hope so
You mention an error in the OP. Can you specify?
Works!
Rooted and Deodexed...
i really don't know what went wrong the first try, i was getting an error telling me there isnt enough space in the partition where the su binary goes. then again, i simply reflashed kpm, and viola, it works.

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] Problems with ADB remount / pushing app

I've unlocked my phone via HTCDev, which to my understanding should give enough permissions and whatnot for adb to work on system files too.
I'm trying to push application to replace system application, I know the application works, I got both signed & unsigned versions of it but same thing with either one of them.
adb remount says "remount failed: operation not permitted" and adb push [file] /system/apps says "failed to copy '[file]' to '/system/apps/': read-only file system
--
What am I doing wrong, or do I really have to root the phone just to get one damn application replaced with modified one?
Bump
Have you rooted?
frazzeld said:
Have you rooted?
Click to expand...
Click to collapse
This^
You need to have SU# access, which be definition needs root permissions. If you haven't already, use the all in one tool kit to flash clockwork and root that beech. Then when in ADB you enter SU and you will get a prompt like this #, indicating you have root privileges.
Update, I have rooted, stock rom still though
If I use adb shell, I get $, but writing "su" in shell gives me #
still, I've tried both the adb remount and in shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
the latter seems to work, but however still when I try to push something to /system/app it still says permission denied
edit:
not quite sure what I did, but i finally got SUCCESS from installing from shell
how did you install through the shell

Categories

Resources