There is an update for Terminal Emulator in the market I am wondering how you can uninstall it from JF 1.41 RC33 in order to get the update
you can use in terminal
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock03 /system
rm /system/app/com.android.term.apk
or navigate to system/app
rm com.android.term.apk
It will close the terminal right away for obvious reasons and then you can load the one from the market.
Just tested it and it works and doesn't seem to have any adverse affects. Mine is still working
I dont see any difference in the app to me looks the same no changes that I can tell.
savethechicken said:
you can use in terminal
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock03 /system
and the navigate to system/app or you can you use
rm system/app/com.android.term.apk
It will close the terminal right away for obvious reasons and then you can load the one from the market.
Just tested it and it works and doesn't seem to have any adverse affects. Mine is still working
I dont see any difference in the app to me looks the same no changes that I can tell.
Click to expand...
Click to collapse
I keep getting permission denied
are you type su first before mounting the image to get full superuser access.
The only difference we have if your signature is right is that im running the 1.41 RC33 but i was able to remove any apks i wanted this same way when i was on RC30
Yeah I typed su and got the superuser going... Maybe I am just oo much of a noob at this I am running the new JF RC33 update too
make sure that you are not typing anything in quotes "quotes just to show spaces" this is where i had the most problems when i started using this code
su
mount "space" -o "space" rw,remount "space" -t "space" yaffs2 "space" /dev/block/mtdblock03 "space" /system
then the long way
cd system
cd app
rm com.android.term.apk
that might help
Sweet I got it working thanks a million
Is there any reason why the new version is better than the one we have already?
not a problem.
I personally dont see any difference in it but everything still seems to be working
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?
Ok so there doesnt seem to be much work being done on the little gem that is the Samsung GT-i5500/Europa.
So i've done a rummage around and tracked down a few useful things that can be done for any users of the phone.
Since we have no dedicated forum category yet if anyone finds any more details of useful modifications being done on the device then dont hesitate to drop me a PM and i'll add it to the original post.
Flashing and Firmware Updates
-----------------------------
ODIN + Firmware Packages - http://forum.xda-developers.com/showthread.php?t=781149
Rooting
-------
Rooting can be done using UniversalAndroot, works like a dream without any problems even after flashing the latest firmware.
Busybox
-------
Busybox - http://www.codeplex.com/Project/Download/FileDownload.aspx?ProjectName=de&DownloadId=96485
Ok so I found numerous different reports on Busybox stating different mount commands some of which didn't work so well for me.
So here is how I personally got busybox installed and working.
First off grab a copy of busybox from the above link and place it in the root of your SDCard.
The do the following from a command line:
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
dd if=/sdcard/busybox of=/system/bin/busybox
chmod 4755 /system/bin/busybox
mkdir /data/busybox
/system/bin/busybox --install -s /system/bin/
This differs from the /system/xbin instructions I mostly found however works fine and i've yet to find any issues with it.
Market Patch
------------
Market Patch Guide - http://forum.xda-developers.com/showthread.php?t=834959
The above market patch removes the issue of not being able to see all app's on the market.
Apps2SD
-------
Apps2SD Guide - http://forum.xda-developers.com/showthread.php?p=9087708
Works fine however it requires partitioning to be done from linux since we currently don't have a modified recovery.img with parted available.
I was never successful using SuperOneClick for the Optimus V. hangs at wating for device.
THOUGH...
I believe I did finally get it rooted using adb and push psneuter, busybox, su and Superuser.apk...via Ubuntu 10.10 Maverick...
I rebooted the device twice...downloaded terminal from the market and sure enough I can su to a # prompt...I take this to confirm I have successfully rooted my Optimus V.
Now to the question....
I found several post most of which included this command in adb shell:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
However I was successful based on a post found here by (Endur):
http://forum.xda-developers.com/showthread.php?p=12076877
with the command
mount -o rw,remount /dev/block/stl9 /system
What is the difference? Have I done something horribly wrong?
And Thank you for all your work here...This is a lot of fun prying into the technologies of today and tomorrow.
Any answer or pointing me in the direction to research on my own would be much appreciated.
Jim
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