Database Info

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 Un-root?

I just rooted the A2, lets say something breaks on the phone and I have to take it back to AT&T. How can you unroot? Not that I will but just in case.

They really cannot tell if the phone is rooted. It's when the device has Bootloader unlocked that they can notice easier. Although I have taken back two OG Atrixes with bootloaders unlocked and Just returned an Atrix 2 Rooted with No issues from anyone. Although I would like to know regardless anyway as I am having issues with my root at the moment.

Not sure, but if you find out let us know.

Its also so I can receive over the air updates down the road.

OTA updates weren't affected by root on my backflip and actually the update unrooted the phone. Idt theres anything to worry about there.

1) all you really need to do is remove the SU apk from the /system/app folder and thats it. (i have not rooted this phone yet, myself. but thats all you should have to do)
2) rooting should not affect OTA updates BUT it I think it depends on the root method. If rooting requires you to flash a new kernel (like on the SGS2), it may break OTA updates. There's no definitive answer to that question.

Thank you for the answers. Just wanna stay up to date on software without having to manually do everything.
Sent from my MB865 using xda premium

To completely un-root, one would need to do the following:
adb shell
su
cd /system/xbin
mkdir tmp
mv * tmp
cd tmp
mv ssmgrd ../
mv run_restore ../
mv run_backup ../
mv backup ../
mv dexdump ../
mv drm1_func_test ../
cd ..
rm -rf tmp
cd /
rm /system/bin/busybox
rm /system/app/Superuser.apk
rm /data/local/tmp/*
rm /data/local/zerg
rm /data/local/su
rm /data/local/Superuser.apk
rm /system/xbin/su
exit
adb reboot
If you then wipe data / factory reset, PROVIDED you followed the root thread in the dev forum and haven't messed with anything else, you will be back to a bone stock device.

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

Help: Good For Eterprise on a previously rooted phone

Trying to install GFE on a previously rooted but now unrooted phone. It's failing because it thinks I'm still rooted.
I have unrooted, removed Superuser (the apk and from the App list), etc.
What the hell is it finding?

Maybe su or busybox in the xbin folder?

wewoapsiak said:
Maybe su or busybox in the xbin folder?
Click to expand...
Click to collapse
Yes. They are both there. But how do I get rid of them now that I'm not rooted? ADB shell errors out with read only file system. If I re-root and delete them, then how do I make the file system read only again?
Also, do I need to get rid of /system/bin/su or is that part of stock Android?
Thanks so much for any help.

So all you did was delete the .apk? Download Super 1-click, re-root, then use it to unroot.
http://forum.xda-developers.com/showthread.php?t=803682

wewoapsiak said:
So all you did was delete the .apk? Download Super 1-click, re-root, then use it to unroot.
http://forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
I rooted by flashing the update.zip and then unrooted by removing the Superuser app and then changing the file system to read only.
I thought SuperOneClick only worked with FroYo on the G2X and not with Gingerbread.

Success!!!!!!!! Many thanks to jboxer and others that pointed me in the right direction.
Here's what you need to do for anyone else facing this issue:
1. Boot into Clockwordmod Recovery and then connect your phone to the computer. CWM Recovery will be seen on ADB with root permissions.
2. Before issuing the following commands, after your phone is connected, use the menu in CWM Recovery to mount the system. If you don't mount the system you are seeing CWM's mini Android system and not the phone's.
3. Issue the following commands from your computer:
#adb uninstall com.noshufou.android.su
#adb shell rm /system/app/Superuser.apk
#adb shell rm /system/bin/su
#adb shell rm /system/xbin/su
#adb shell rm /data/local/tmp/psneuter
#adb shell "find /system/xbin -type l | xargs rm"
#adb shell rm /system/xbin/busybox
4. Use the CWM Recovery menu to unmount system.
5. Reboot your phone.
Before you attempt to re-run the Good setup, check one last time to make sure that su is gone from /system/bin and /system/xbin and that Superuser does not show up either in your Apps or when you go to Settings->Manage Apps. If any of this is still present you need to redo what is written above as the Good setup will fail.
I also recommend doing a Nandroid before unrooting, a second Nandroid after unrooting but before installing Good, and then a third Nandroid immediately after successfully installing Good.

[GUIDE] Root LG AS730 Root for Revol Wireless 4.0.4 Kernel 3.0.8 IMM76L AS73012a

MODIFIED LG AS730 Root for Revol Wireless Android Version 4.0.4 Kernel 3.0.8 Build IMM76L SW Version AS73012a
March 22, 2013
By: Ruckman
---------------------------------------------------------------
##ENABLE USB DEBUGGING UNDER SETTINGS > DEVELOPMENT > USB Debugging
##PLUG IN USB CORD TO COMPUTER
##PLACE PHONE INTO LG software mode
######(Download lg-as730-4.0.4-root.zip)
######Extract ZIP, and run adb from that folder.
adb shell
######(while in adb shell)
rm /data/local/tmp/profile_calib_m
ln -s /data/local.prop /data/local/tmp/profile_calib_m
exit
adb reboot
######(Wait for FULL phone reboot)
adb shell
######(once in the adb shell again)
echo 'ro.kernel.qemu=1' > /data/local.prop
rm /data/local/tmp/profile_calib_m
exit
adb reboot
######(Wait for FULL phone reboot)
adb remount
adb push su /system/bin/su
adb shell "chmod 6755 /system/bin/su"
adb shell "ln -s /system/bin/su /system/xbin/su 2>/dev/null"
adb push busybox /system/xbin/busybox
adb shell "chmod 755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install /system/xbin"
adb push Superuser.apk /system/app/Superuser.apk
adb shell rm /data/local.prop
adb reboot
######(You are now ROOTED!)

Sweet. Before this I was just using that scrappy unlock root program.
Sent from my LG-AS730 using xda premium

NomadCF said:
Sweet. Before this I was just using that scrappy unlock root program.
Sent from my LG-AS730 using xda premium
Click to expand...
Click to collapse
I saw that program but it seemed a little spyware laden. So I decided to try and find another way, and after about 6 hours of messing around succeeded. Glad someone else benefited from it as well.

RuckmanXDA said:
I saw that program but it seemed a little spyware laden. So I decided to try and find another way, and after about 6 hours of messing around succeeded. Glad someone else benefited from it as well.
Click to expand...
Click to collapse
Oh it is a POS program with ALLOT of spyware. But since i was using on my virtual PC I didn't really care
But yea thanks again !
PS. What have you really done to yours since you rooted it ? I've been slowly removing the bloat-ware.

NomadCF said:
Oh it is a POS program with ALLOT of spyware. But since i was using on my virtual PC I didn't really care
But yea thanks again !
PS. What have you really done to yours since you rooted it ? I've been slowly removing the bloat-ware.
Click to expand...
Click to collapse
I want to compile clockwork recovery but that is a lot more work and i risk perma-bricking my phone, but I have been using titanium backup and root explorer. Be careful of what programs you remove, the phone may have root but it still has a locked bootloader that freaks if you remove the wrong app.

So what apps have you removed safely. I've gone and removed the normal ones (Facebook, exchange, etc).
Sent from my LG-AS730 using xda premium