Hi, I'm hoping someone can help me. I'm running OSX Snow Leopard, using terminal and attempting to gain root access to my new Nexus One. I was able to quickly and easily unlock the boot loader, however, I have made multiple attempts to gain root access for model ERE27 using superboot, but while everything seems to appear normal, I can not flash the recovery-RA-nexus-v1.7.0.1-cyan.img. When I reboot the phone I attempt to run terminal app from market and find I am still denied permission. I've checked every site I could to correct this, but seem to be missing something every time. When attempting to root, I cd to applications/android-sdk-mac_86/tools/superboot. I press enter then chmod +x-install-superboot-mac.sh Then I press enter and key ./fastboot-mac. After processing in terminal and seeing a status bar briefly on the nexus upper right screen of the Nexus, terminal says Okay. I reboot and no root access. PLEASE HELP. Been at this for an embarrassingly long time now...
Have you installed a rooted rom? or just trying to see if you have root access on the stock rom?
Jeremy.Bentham said:
Hi, I'm hoping someone can help me. I'm running OSX Snow Leopard, using terminal and attempting to gain root access to my new Nexus One. I was able to quickly and easily unlock the boot loader, however, I have made multiple attempts to gain root access for model ERE27 using superboot, but while everything seems to appear normal, I can not flash the recovery-RA-nexus-v1.7.0.1-cyan.img. When I reboot the phone I attempt to run terminal app from market and find I am still denied permission. I've checked every site I could to correct this, but seem to be missing something every time. When attempting to root, I cd to applications/android-sdk-mac_86/tools/superboot. I press enter then chmod +x-install-superboot-mac.sh Then I press enter and key ./fastboot-mac. After processing in terminal and seeing a status bar briefly on the nexus upper right screen of the Nexus, terminal says Okay. I reboot and no root access. PLEASE HELP. Been at this for an embarrassingly long time now...
Click to expand...
Click to collapse
Try using the nexus-addon-0.1-signed.zip
http://forum.xda-developers.com/showthread.php?t=636795
Related
Hello everyone, I apologize in advance if I've posted this in the wrong section. Ok so here is my problem, I recently got Cyanogen 4.04 (Latest stable release) on my phone. I was gonna try out the overclock app from the App market but it doesn't let me open it because i'm not ROOT. I thought users are always ROOT in modded ROM, are they not? If not then what should I do to ROOT? I used the one click method for root at the begining (to install cyanogen) and Haykuro SPL Update. Thanks.
p.s I am a complete noob so please go slow.
If you have used the 1-Click-Root method, did you follow the steps to type in telnetd using a terminal app? If not then I would go back and re-trace your steps.
NeoBlade said:
If you have used the 1-Click-Root method, did you follow the steps to type in telnetd using a terminal app? If not then I would go back and re-trace your steps.
Click to expand...
Click to collapse
Yes I did the telnetd thing. After rebooting clicking on an emptyspace then RETURN, wait, RETURN then telnetd which took me to the contact list. Then Home. Then I went to the terminal app and did the 4 step thing. But I did all that before flashing the Cyanogen for the first time. Now that I have Cynogen installed, if I try to Connect in telnet it gives me an error and if I try to do the 4 step thing in Terminal emulator it says "permission denied. (are you root?)". Please tell me what should I do?
pooranimator said:
Yes I did the telnetd thing. After rebooting clicking on an emptyspace then RETURN, wait, RETURN then telnetd which took me to the contact list. Then Home. Then I went to the terminal app and did the 4 step thing. But I did all that before flashing the Cyanogen for the first time. Now that I have Cynogen installed, if I try to Connect in telnet it gives me an error and if I try to do the 4 step thing in Terminal emulator it says "permission denied. (are you root?)". Please tell me what should I do?
Click to expand...
Click to collapse
type su into the terminal emulator and see what is says. if you were able to flash a custom rom then your phone is rooted, you could've gotten a bad download.
Download Better Terminal from the Maket and as david mentioned, type in "su" then press enter to see if you have root access.
if nothing pops up upon entering su does that mean a new wipe and install is nessecary??
Reason i ask is i can't get the terminal emulator to work either that came with the build....is it the same thing as better terminal????. I used a one click install and everything is running fine on my 4.0.4 build but i tried earlier as well to install the "overclock" app from market and it wouldn't work. I decided to purchase SetCPU instead for a buck and it works no problem. By the way i have a my touch 3g..
mikespy said:
if nothing pops up upon entering su does that mean a new wipe and install is nessecary??
Reason i ask is i can't get the terminal emulator to work either that came with the build....is it the same thing as better terminal????. I used a one click install and everything is running fine on my 4.0.4 build but i tried earlier as well to install the "overclock" app from market and it wouldn't work. I decided to purchase SetCPU instead for a buck and it works no problem. By the way i have a my touch 3g..
Click to expand...
Click to collapse
dont think the terminal emulator works w/o a physical keyboard
better terminal will get the job done, but not the same app. You can just use that instead of terminal
but if terminal does work w/o a physical keyboard, when you type su, what does it do?
if it asks to allow or deny, click allow. if you hit always deny, go to the superuser app and erase all settings.
if it doesnt ask anything, when you type su, it should drop one line and have this symbol #
B-man007 said:
dont think the terminal emulator works w/o a physical keyboard
better terminal will get the job done, but not the same app. You can just use that instead of terminal
but if terminal does work w/o a physical keyboard, when you type su, what does it do?
if it asks to allow or deny, click allow. if you hit always deny, go to the superuser app and erase all settings.
if it doesnt ask anything, when you type su, it should drop one line and have this symbol #
Click to expand...
Click to collapse
Thanks for the help....
I actually did download better terminal and when i typed in su and hit enter. It went to the screen your talking about and since i had just installed SetCPU it asked if i wished to allow i clicked yes. So i asume i have rooted correctly and guess the "overclocking" program on the market might just not download on my phone correctly with the cyan 4.0.4.
Thanks
Thanks to all of you for your replies. I think I know what the problem was. The OverclockWidget is a Widget...duh silly me. I was trying to open it as a regular app and was failing. Added it as a widget on the first screen and now everything works. I have one quick unrelated question, while downloading the latest experimental release of Cyanogen I read at the bottom of the post in read that the users should not use any Apps2SD while using Cyaogen's latest release because the ROM does it by itself or something like that. What does that mean?
@mikespy- tap and hold for a sec on your screen and add the OverclockWidget widget on your screen then tap to open. That's how you open the OC util.
I can't seem to find out how to get into the fastboot on my n1. I searched and came out empty handed. This is my first android phone and I have had it for 4 days. I rooted the phone and got setCPU but apparently I need to get into fast boot in order to use it.
If you turn off you phone, then turn it back on while holding down the trackball, that will take you directly to fastboot. (use volume and power keys to navigate in fastboot)
Not sure why you need fastboot for setCPU. If you have a rooted rom, you should just be able to run it, you will need a modified kernel to overclock it though, that doesn't necessarily require fastboot either.
According to. Redmond pie I need. To enter some things in fastboot. My set CPU says that it cannot gain root access and that it needs to be added as a superuser program or something like that.
Are you sure you have root? Check, using a root access flashlight from the market...
Sent from my Nexus One using XDA App
I have the cm6 rom on my phone.
rez0469 said:
I have the cm6 rom on my phone.
Click to expand...
Click to collapse
It is your rom that gives you root priveleges, (not saying there isn't) but i can't think of anything you are going to put into fastboot that will change that.
I don't think flashlight needs root anymore, the simplest other method is to go to the terminal emulator app, and simply write "su" into it (without quotation marks, if it says permission denied, you don't have root, if "#" appears, you have root.
You can also check for a "superuser" app in your drawer, it also gives a list of apps you have given root permissions to, setCPU should be in there
To add to that:
When you try and run SetCPU, the SuperUser app should pop up with a message, asking if you want to grant superuser permission...
Sent from my Nexus One using XDA App
It sure doesn't do that.
liam.lah said:
It is your rom that gives you root priveleges, (not saying there isn't) but i can't think of anything you are going to put into fastboot that will change that.
I don't think flashlight needs root anymore, the simplest other method is to go to the terminal emulator app, and simply write "su" into it (without quotation marks, if it says permission denied, you don't have root, if "#" appears, you have root.
You can also check for a "superuser" app in your drawer, it also gives a list of apps you have given root permissions to, setCPU should be in there
Click to expand...
Click to collapse
It says it can't link su.
When I go here and download the 1.6.2 and try to root it says your device is alreadyrooted.
http://forum.xda-developers.com/showthread.php?t=747598
I've been trying to figure this out all day and I'm stumped.
My stock Droid recently failed to get past the bootloader.
I'm following the directions from the CM Wiki titled "Motorola Droid: Full Update Guide" (no direct link because of my new account, sorry) and others I've found and they all seem to be exactly the same.
I've got SPRecovery installed no problem and after I run the update.zip I get a successful install message, including "enjoy your root".
The problem is in the next step where I ADB it doesn't appear I actually have root access.
I think this may be because I'm connecting to my phone from the SPRecovery menu, but I'm not sure.
This is what my cmd screen looks like when I try to follow the steps under "Installing ClockworkMod Recovery" > "Second Method (manual method)".
Code:
C:\Users\XXXX>adb shell
/ # su
su
/system/bin/sh: su: not found
I noticed that in SPRecovery there are "mount options", so I tried mounting /system and trying again and I get basically the same thing, but without the "/" and without the directory
Code:
C:\Users\XXXX>adb shell
# su
su
su: not found
I'm not Linux savvy enough to know the difference unfortunately. I've tried 3 different update.zip from 3 different sources, but all appear to be the exact same thing.
Typing "busybox" in the ADB shell kicks back all the functions so it appears to be installed.
"adb devices" kicks back "040388990E0EDITED recovery"
Any ideas would be greatly appreciated, it's getting very frustrating.
Do you have the opportunity to root your phone from the Recovery-Menu?
I have OpenRecovery (OR) and when I boot in OR i can manually chose to root my phone.
----wrong----
Quinity said:
You can also simply download the SuperUser App from the market. This roots your phone.
Click to expand...
Click to collapse
I'm about 99% certain that is false. If it was that easy, I would have heard about it. Plus the only SU app on the market states " Grant and manage Superuser rights for your phone. This app requires that you already have root.."
Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.
Does nobody have an idea? Would be very sad if I couldn't use it anymore. Although I'm the only one to blame. Does someone have experience on sending it back to amazon for warranty? As far as I know rooted devices lose their warranty.. :-/
Karelian_ said:
Hey everyone,
first off, I have my Kindle for a few weeks now and it's my first Androit device. I started reading into rooting and adb commands only a few days ago, so please excuse me if I'm not writing accurately with some terms. Additionally, I could not find a similar problem via searching.
Here's my problem (I'll try to be as detailed as possible):
I rooted my KFSOWI running 11.3.1.0 yesterday using Moronigs rooting method. It went well and I had full root access (typing su in an adb shell resulted in an # and all that).
Today I wanted to edit the framework-res.apk to exchange some images. Stupid as I tend to be I wanted to rename the original file and then paste my modified one. The device started giving out various crashes, telling me that lots of apps stopped working. Only then I realised that the file is needed to run the system. Unfortunately the Kindle had shut down at some point and when I boot it now it only gives me a black screen (although the backlight is still on).
Here's what I tried so far:
1. I wanted to adb push the modified file to the system/framework folder, but it tells me that the folder is read-only.
2. So I wanted to change permissions but it seems I don't have root access anymore (I don't even get the # output in the adb-shell after typing su).
3. I tried installing the package via adb but it says "Error: COuld not access package manager. Is the system running?"
I guess it doesn't boot up the package manager and root access. You guys have any idea what I can do right now? Seems like a lost cause to me. And if so, can I try sending it back via warranty?
Any help is very much appreciated. And thanks for all the great work on these forums.
Click to expand...
Click to collapse
At this point, I would send it back to Amazon. all they will check for is physical damage and send it back to China. I hear some people bricking their tablet several times and getting a replacement. Thing is that Amazon's warranty questions are only water damage and did you drop it questions. So you don't even have to BS them to get a replacement.
If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app
braider said:
If you have a fast boot cable you might restore it. Now it's not the cable that came with Kindle, it's a special programming cable that will put it into fast boot mode.
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
There are no exploits for this boot loader yet. Don't think a fastboot cord will do much at the time.
Sent from Nexus 7 flo running SinLess ROM 4.2.2 using xda app-developers app
Did noone come up with a solution, because i did the same thing, with the framework-res.apk
i can make a fastboot cable if itll do any good without an unlocked bootloader. could i possibly push the most recent update.bin from amazon and restore the device to stock???
---------- Post added at 04:06 AM ---------- Previous post was at 03:10 AM ----------
i wouldnt take bricked for an answer and i found a fix
what i did was make sure the kindle was connected to adb and typed the following
adb reboot
adb wait-for-device shell su
the shell managed to snag the SU file and displayed # before the device looped thru all of the boot apps over and over, but then CMD froze.
so i tried this
adb reboot
adb wait-for-device shell su mount -o remount,rw -t ext4 /dev/block/platform/omap/omap.hsmmc.1/by-name/system /system
and in one line got root access and remounted the system as RW
my problem was that framework-res APK was replaced with ZIP so all i had to do was rename it
# cp /system/framework/framework-res.zip /system/framework/framework-res.apk
and success!!
# exit
$ exit
adb reboot
and she booted right up!!!!
First response so please be kind. My KFSOWI is stuck in the bootloop too. I have a factory cable and can get into fastboot but don't have any factory images to restore. Anyone have any ideas?
Do you get any adb access? I don't think casebook will be any help until someone unlocks the bootloader
Sent from my KFSOWI using XDA Premium 4 mobile app
I have rooted my phone successfully, and in the beginning apps that required root access would check for root, and request su access, but now that doesn't happen.
1. Anyone know what happened, and how do I get applications to request root access again?
2. How do I update the SuperSU binary, when it asks?
Rooted using SlapMyMoto, on Android 4.4 Stock.
Make sure you have the latest supersu from the play store but when it asks you to update the SU binary, it should show two options, normal and twrp, since i'm assuming you're locked (plus it's just easier), choose normal. Also, i'm not sure what the process is, but you might need to re-run whatever it is that you use to root (i'm unlocked so i'm not familiar with the process) because it sounds like you don't have system mounted as rw. If this is the result of an OTA, because people are losing rw from taking the verizon OTA, you might be out of luck until a new method is found.
-edit- another fix might be to re flash supersu if you have safestrap installed, and just clarification, it will not ask for root for the same app twice unless you tell it to ask again next prompt.
StATicxTW0T said:
Make sure you have the latest supersu from the play store but when it asks you to update the SU binary, it should show two options, normal and twrp, since i'm assuming you're locked (plus it's just easier), choose normal. Also, i'm not sure what the process is, but you might need to re-run whatever it is that you use to root (i'm unlocked so i'm not familiar with the process) because it sounds like you don't have system mounted as rw. If this is the result of an OTA, because people are losing rw from taking the verizon OTA, you might be out of luck until a new method is found.
-edit- another fix might be to re flash supersu if you have safestrap installed, and just clarification, it will not ask for root for the same app twice unless you tell it to ask again next prompt.
Click to expand...
Click to collapse
Thanks for the reply. I took the OTA to 4.4 from 4.2, and I was still rooted. Something happened with SuperSU, and now the phone is behaving as if it is not rooted, or it's half rooted (if that makes sense).
MyBackupPro would always ask for root access, and then SuperSU would grant it automatically. Now this doesn't happen. Also, I'm trying to use Helium backup as well, and when it tries to ask for root access, it fails. Any app that usually requests root access doesn't even ask.
Thanks.
akhenax said:
Thanks.
Click to expand...
Click to collapse
I wouldn't take my word for it, but i remember reading about a downgrade then upgrade process where you would downgrade to 4.2.2 post cam then root then upgrade again, it might help, no guarantee's though.
StATicxTW0T said:
I wouldn't take my word for it, but i remember reading about a downgrade then upgrade process where you would downgrade to 4.2.2 post cam then root then upgrade again, it might help, no guarantee's though.
Click to expand...
Click to collapse
I always thank replies whether it helps or not.
I am trying to retrace the steps I did to root, but not the entire process. Hope to save time from having to redo everything again.
I fixed it.
I did the following steps (not sure if this did anything but...):
uninstall SuperSU
adb reboot bootloader
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot reboot
adb push su /data/local/tmp/su
adb push install.sh /data/local/tmp/install.sh
adb push rec.sh /data/local/tmp/rec.sh
adb push install-recovery.sh /data/local/tmp/install-recovery.sh
adb push setup.sh /data/local/tmp/setup.sh
adb reboot
adb shell
echo "/data/local/tmp/rec.sh" > /sys/kernel/uevent_helper
<-- THIS FAILS, as expected. It worked when I first rooted the device, but doesn't work any longer, but this is OK.
it returns: /system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied
Once again, this is OK.
Install SuperSU
DO NOT OPEN IT. JUST INSTALL IT.
Apps now request root permission.
adb shell getprop ro.boot.write_protect
returns a value of:1 which means my bootloader is locked write protection is enabled, but I still have proper root access.
Hope this helps the next guy.
akhenax said:
adb shell getprop ro.boot.write_protect
returns a value of:1 which means my bootloader is locked, but I still have proper root access.
Click to expand...
Click to collapse
This actually means that write protection is enabled.
Did you try to reboot into"recovery" to set write protection off?
nhizzat said:
Did you try to reboot into"recovery" to set write protection off?
Click to expand...
Click to collapse
I don't think I'm versed enough in this to answer this question accurately, for the very reason you quoted "recovery". How would you accomplish such a feat, step by step?
akhenax said:
I don't think I'm versed enough in this to answer this question accurately, for the very reason you quoted "recovery". How would you accomplish such a feat, step by step?
Click to expand...
Click to collapse
power down, hold volume down and power, youll get a black screen with blue letters. use volume down button to naviagte and power to select.
xpsychox said:
power down, hold volume down and power, youll get a black screen with blue letters. use volume down button to naviagte and power to select.
Click to expand...
Click to collapse
The question was: Did you try to reboot into"recovery" to set write protection off?
Do your steps allow one to do this?
akhenax said:
The question was: Did you try to reboot into"recovery" to set write protection off?
Do your steps allow one to do this?
Click to expand...
Click to collapse
ahh, my bad miss read it.. lol... oops
akhenax said:
I don't think I'm versed enough in this to answer this question accurately, for the very reason you quoted "recovery". How would you accomplish such a feat, step by step?
Click to expand...
Click to collapse
When in Android, connect the phone to your PC USB port. I hope you've already installed the Android SDK and Moto drivers. Open a cmd prompt with admin privileges and type "adb devices" to check if your PC recognizes the phone. If so, then type "adb reboot recovery". The phone will reboot just as it normally would, only this time write protection is off. Or do the steps below or type "adb reboot bootloader".
xpsychox said:
power down, hold volume down and power, youll get a black screen with blue letters. use volume down button to naviagte and power to select.
Click to expand...
Click to collapse
Volume up to select, actually.