Hi,
I'm trying to root my Nexus One but it doesn't appear to be working.
I can see that the 'Superuser Permission' application is installed but when I run it I don't see anything other than a black screen. Any application that asks for root (su request) just gives me a black screen too (where the buttons would normally appear it's just black).
Any ideas?
SC
try to reinstall the superuser app
melterx12 said:
try to reinstall the superuser app
Click to expand...
Click to collapse
is there an apk available?
SC
ScaredyCat said:
is there an apk available?
SC
Click to expand...
Click to collapse
You should be able to extract it from the file that you flashed to root.
i had this same problem. once i re-enabled USB debugging and rebooted, the superuser took off and ran. now N1 Torch works great! thanks xda!
Ok,
That did it. Looks like you need to turn on debugging before installing. Thanks for the help.
For anyone else having this issue here's what I did:
1)Settings->Applications->Development tick USB Debugging
2) Rebooted just to be sure
3) Used adb to copy the Superuser.apk to my mac :
./adb-mac pull /superboot/Supseruser.apk ./
4) Reinstalled the application:
./adb-mac install -r ./Superuser.apk
5) Rebooted the Nexus One.
6) Ran an app that wants permissions to check it worked.
SC
I solved this but installing another app...
seems to be ok after. I've replicated it twice!
ScaredyCat said:
Ok,
That did it. Looks like you need to turn on debugging before installing. Thanks for the help.
For anyone else having this issue here's what I did:
1)Settings->Applications->Development tick USB Debugging
2) Rebooted just to be sure
3) Used adb to copy the Superuser.apk to my mac :
./adb-mac pull /superboot/Supseruser.apk ./
4) Reinstalled the application:
./adb-mac install -r ./Superuser.apk
5) Rebooted the Nexus One.
6) Ran an app that wants permissions to check it worked.
SC
Click to expand...
Click to collapse
just did this, and its working 100% now
also installed N1 torch and almost had a seizure with the strobe feature lol
Related
Grrrrrrrr
I've been trying to sort this out for hours.....
Not sure what's happened, but whenever I try and run a root app, I get the SU Request screen, and it's blank....I can't allow or anything.
Anyone help ? please ?
Have you set debug mode ?
menu>setting>application>development>usb debugging (check)
Yup.
Health care reform just passed BTW. FTW
same here. I am trying to change my lockscreen. Running fresh 2.0b2
having the same problem all the sudden...I nandroided to a good one and its working fine again.
did you try and install Quickboot? that was where it went south for me.
I pushed the reboot zip to system/bin/ and the got the blank SU screen.
Chad
nimitz87 said:
having the same problem all the sudden...I nandroided to a good one and its working fine again.
did you try and install Quickboot? that was where it went south for me.
I pushed the reboot zip to system/bin/ and the got the blank SU screen.
Chad
Click to expand...
Click to collapse
hey dude with my sig
turn on usb debugging and it'll work again
regaw_leinad said:
hey dude with my sig
turn on usb debugging and it'll work again
Click to expand...
Click to collapse
whoops!
thanks it works magically again
quickboot ftw.
Chad
nimitz87 said:
whoops!
thanks it works magically again
quickboot ftw.
Chad
Click to expand...
Click to collapse
no problem
trying to delete lockscreen but is says the file system is read only.
marcusva79 said:
trying to delete lockscreen but is says the file system is read only.
Click to expand...
Click to collapse
which rom?
fresh rom 2.0b2
marcusva79 said:
fresh rom 2.0b2
Click to expand...
Click to collapse
to remove the lockscreen you go into command prompt and type this (but don't type the # sign, it just shows up.
Code:
cd <insert path to your android sdk here>
adb remount
adb shell
# cd /system/app/
# rm HtcLockScreen*
# reboot
is there an easier way.
back to having the issue again...usb debugging is on.
I'm having problems with the SuperUser Permissions included on the DamageLess 2.8 ROM. I've never been able to use it correctly, and now I really need to in order to utilize the DCUpdater. Can someone tell me how to work this app??
BTW, i've already tried to run the adb shell in my android sdk folder, but that doesn't work. It keeps telling me that the path syntax is not correct, or something along those lines.
dereklane said:
I'm having problems with the SuperUser Permissions included on the DamageLess 2.8 ROM. I've never been able to use it correctly, and now I really need to in order to utilize the DCUpdater. Can someone tell me how to work this app??
BTW, i've already tried to run the adb shell in my android sdk folder, but that doesn't work. It keeps telling me that the path syntax is not correct, or something along those lines.
Click to expand...
Click to collapse
Do you have debugging enabled?
Yeah, I enabled it after I plugged in my phone
Thread Moved. Not related to Development.
dereklane said:
I'm having problems with the SuperUser Permissions included on the DamageLess 2.8 ROM. I've never been able to use it correctly, and now I really need to in order to utilize the DCUpdater. Can someone tell me how to work this app??
BTW, i've already tried to run the adb shell in my android sdk folder, but that doesn't work. It keeps telling me that the path syntax is not correct, or something along those lines.
Click to expand...
Click to collapse
if you have debugging enabled, make sure you aren't connected to your computer, that will cause it to crash. other than that i don't know
As long as you have USB debugging enabled, when a program asks for superuser permission, it will prompt you.
-------------------------------------
Sent via the XDA Tapatalk App
I had the same problem but enabled usb debugging and disconected the phone from the computer and SU is working fine again.
I have USB debugging enabled, disconnected from the PC, but I can't get Superuser to prompt (for any apps) when trying to run Autokiller. I just flashed Fresh 2.1.2 coming from FreshToast. Any help?
what version should i use on my Xperia X10a?
hi
i rooted my X10a & have the Superuser Permission install lately. when i click on the icon, it shows a blank screen. i click the menu button > preferences , it shows Action Yap & Notification. there's no apps or anything else. could someone guide me how i get it work?
thanks
For anyone having issues with SU (no matter which ROM) check the permissions on the following two binaries:
/system/bin/su
/system/xbin/su
If they're not 755, connect to the shell via ADB and change them - that's worked for several users on Fresh, my guess is that it would probably work on other ROMs as well.
ok i have some issues...
I have a Moto Blur...
and when i checked the
/system/bin/su --- it only had -r-
/system/xbin/su -- didnt have this file
do you have an idea what's wrong?
thanks
mat
Hello All,
I would really appreciate help on this issue I have been having. I recently rooted then unlocked the bootloader of my device. I downloaded a root uninstaller and may have somehow killed the home process from running. Now, when i turn on the device, i get the error
The application Home (process com.motorola.home) has stopped unexpectedly
It does not go away and comes repeatedly back, not allowing me to change any settings whatsoever. I don't know what to do. I tried going into android recover mode and both wiped the device and cleared the cache, but the problem persists. I also tried putting a cyanogenmod version on the devices SD card but cant get it install because for some reason I can't get clockwork mod installed correctly. I cannot turn on USB debugging mode because I can't get into the settings. I tried using the .sbf to flash it but it is the .sbf I used to unlock the device so I am not sure that is the right one or if the right one would even do the trick, I fear that the system files that run the home application may be corrupt, deleted or permanently inactive. I would appreciate any ideas people may have to help me.
Also, becuase I factory reset the device, the bootloader is unlocked, but it is no longer rooted, and I cannot root it at this time becuase I cannot turn on USB debugging mode.
I was looking at the guide here;
http://forum.xda-developers.com/showthread.php?t=1302423
And was wondering why it didn't work when I tried to install CWM, then I noticed something I didnt see;
"DO NOT FORGET TO DO THIS PART: After the install of RomRacers recovery boot up your phone. Open up your favourite file browser (I used Astro file manager to do this ) and navigate to /system/etc/ and delete the file called 'install-recovery.sh'"
Is there a way to do this from the PC as I wouldn't be able to on my device? Or is the fact that it is not currently rooted going to stop me from doing anything?
Thanks,
heronpj said:
I was looking at the guide here;
http://forum.xda-developers.com/showthread.php?t=1302423
And was wondering why it didn't work when I tried to install CWM, then I noticed something I didnt see;
"DO NOT FORGET TO DO THIS PART: After the install of RomRacers recovery boot up your phone. Open up your favourite file browser (I used Astro file manager to do this ) and navigate to /system/etc/ and delete the file called 'install-recovery.sh'"
Is there a way to do this from the PC as I wouldn't be able to on my device? Or is the fact that it is not currently rooted going to stop me from doing anything?
Thanks,
Click to expand...
Click to collapse
If you are familiar with ADB, the basic commands would be:
Code:
adb remount rw
adb shell
While in the ADB shell:
cd /system/etc
rm install-recovery.sh
exit
that should cover it.
let me know if this works for ya.
Thanks for your response. The only problem is my phone isn't in USB debug mode, and I can't set it to be. Any idea of how to get that turned on without being able to get into the settings?
FaithCollapsing said:
If you are familiar with ADB, the basic commands would be:
Code:
adb remount rw
adb shell
While in the ADB shell:
cd /system/etc
rm install-recovery.sh
exit
that should cover it.
let me know if this works for ya.
Click to expand...
Click to collapse
heronpj said:
Thanks for your response. The only problem is my phone isn't in USB debug mode, and I can't set it to be. Any idea of how to get that turned on without being able to get into the settings?
Click to expand...
Click to collapse
can you boot into recovery?
FaithCollapsing said:
can you boot into recovery?
Click to expand...
Click to collapse
I can, and have down a wipe data as well as cleared the cache, problem persists.
Solved!!! I was able to basically button mash until somehow the screen to log into the play store came up. Download launcher pro and that got me back into my phone! Thanks for your help
Hey Guys,
I just made a big blunder.. darn! I uninstalled the Package Access Helper (thru the titanium backup app) on my G2 (D802 ver) and now I can't install any apps anymore from the PlayStore.
The phone is rooted though..
My question is... What's the best and easiest way to remedy this problem? should I go to all the hassle of reflashing back to Stock ROM? OR can I possibly get an apk for this "Package Access Helper" thingie? and where in God's world do I find this apk if ever asl well?
I'm in dire need here guys... pls help me out. .::
thank you.
There you go
bender_007 said:
There you go
Click to expand...
Click to collapse
Hey thanks bender.. I tried to download and install the apk file on my phone but I'm getting an error - "Package not installed"...
letters_to_cleo said:
Hey thanks bender.. I tried to download and install the apk file on my phone but I'm getting an error - "Package not installed"...
Click to expand...
Click to collapse
copy it to /system/app & reboot
Thanks, but I dont have have any root explorer app on my phone.
Already installed the adb shell on my laptop..
enabled USB debugging on my phone, checked device manager and saw "Androidnet Sooner Single ADB Interface: under Computer.
then on the command prompt with admin permission, I typed on where the adb libs are located
adb shell
su
adb remount
chmod 777 /system/apps
adb push DefaultContainerService.apk /system/app/
BUT.... I always end up with the errr message "device not found"
What's this error all about??
Thank you again for sharing some of your info... I highly appreciate your insights on this
Here you go x2
flashable
@error - you need adb drivers + usb debugging enabled.
I sent you back a message mate.
Unfortunately the flashable zip might not be of no good to me at all, as I did not install any custom recovery on my phone e.g. twrp, etc.
I guess the only route I can do is to really push the DefaultContainerService.apk to the /system/app but I'm always getting this err -'device not found''it
Should Androidnet Sooner Single Adb interface really be the one that appears under the Device manager? or should it be 'Android Composite ADB Interface'?
I'm having a tough luck on this
I guess the most I can do on this would be to just reflash it back to stock again and hope it'll work. *sigh
what does "adb devices" show ?
bender_007 said:
what does "adb devices" show ?
Click to expand...
Click to collapse
adb devices show nothing.
letters_to_cleo said:
adb devices show nothing.
Click to expand...
Click to collapse
you need a more recent adb.exe
try this one https://dl.dropboxusercontent.com/u/663851/adb.exe
darkobas said:
you need a more recent adb.exe
try this one https://dl.dropboxusercontent.com/u/663851/adb.exe
Click to expand...
Click to collapse
thanks man, I downloaded the adb tool from the android sdk website itself.
By the way, I tried as well booting up to stock recovery, and flashing the zip (on the earlier post), but since my phone system is not yet mounted, then the zip file didn't do anything at all.
any one please send me the Package Access helper to my gmail
Please help me I want to restore my package Access helper back please
For battery optimization obsessives, Do not delete or disable it. Apps from play store can not be installed without it. This what I ended up with after disabling the service.
I have moved this from here https://forum.xda-developers.com/pixel-2-xl/how-to/zero-day-vzw-pixel-2-xl-root-t3977851/
Hey everyone!
I am here to post some good news. I have made a set of scripts that can give you temporary root through Magisk. It persists until the next reboot, but setting it up after the initial setup is a lot easier.
The script requires that it be run as root, which means that you need to run the temproot binary provided earlier.
Big thank you to Elliwigy for walking me through the initial process and for providing the commands.
Source code for the "exploit" binary can be found here, and compiled from source if you so desire.
This script is provided with no warranty whatsoever. This script may brick your phone. YOU ARE RUNNING THIS AT YOUR OWN RISK. I ACCEPT NO RESPONSIBILITY FOR WHAT THIS SCRIPT DOES TO YOUR PHONE.
Click to expand...
Click to collapse
IF YOU DO NOT WANT TO RISK YOUR PHONE BEING BRICKED, DO NOT CONTINUE!
Requirements:
A Verizon Pixel 2 (XL) on the September 2019 Security Patch
A computer with ADB If you need ADB, it can be found here
A USB cable
Appropriate USB drivers USB drivers can be found here if needed
Some knowledge of how to use the terminal
The taimentempmagisk.zip file (attached)
The APK for Magisk Manager (included in the zip)
Hope
Magisk and MagiskManager can also be downloaded from here if you wish.
If Magisk Manager prompts you to perform additional setup, DO NOT ACCEPT. (unless you like having a bricked phone)
Install the Magisk Manager APK onto your phone
Use ADB to push the attached ZIP file (taimentempmagisk.zip) to /data/local/tmp
Open an ADB shell and navigate to /data/local/tmp
Extract the ZIP file with the unzip command
Navigate into the scripts folder
Run ./exploit (If this step fails, repeat until you have a root shell)
Run ./installtemproot.sh magiskinit64
After you have done this, you now have root!
If you reboot and want root back, just run /data/local/tmp/scripts/exploit in an adb shell, then run /data/local/tmp/scripts/temproot.sh
Enjoy your root!
Does not work
Hexlay said:
Does not work
Click to expand...
Click to collapse
I'm currently working on a solution, it seems some terminal emulators error out on the mount command.
EDIT: Instructions updated.
logan2611 said:
I'm currently working on a solution, it seems some terminal emulators error out on the mount command.
EDIT: Instructions updated.
Click to expand...
Click to collapse
I'v tried, everything went fine, however magisk still does not detect root
Hexlay said:
I'v tried, everything went fine, however magisk still does not detect root
Click to expand...
Click to collapse
did u install magisk manager? if u dont have it installed then u womt b able to grant su permissions.. it does work as we spent hours testing and ensuring it works before he posted it.. id triple check each instruction and make sure u have magisk apk installed.. if not then reboot and try again from the beginning
elliwigy said:
did u install magisk manager? if u dont have it installed then u womt b able to grant su permissions.. it does work as we spent hours testing and ensuring it works before he posted it.. id triple check each instruction and make sure u have magisk apk installed.. if not then reboot and try again from the beginning
Click to expand...
Click to collapse
Yep, i have it pre-installed, i did follow every step provided, but prompt is not showing up and afterwards it does not detect root... Well, i'v done it several times, i tried ./temproot.sh after install script, but still same...
Well, i guess i have to reboot
Edit: tried reboot, still same.... i'll write down what i have done exactly.
Rebooted dvice
Went into terminal emulator and executed ./taimen
After that went one step back with cd .. and executed chmod -R 777 scripts
Then went to pc and entered ADB shell and executed ./taimen there too, because otherwise i was getting This script must be run as root. Exiting. on install script
Then ran install script. Process did complete successfully, however no magisk prompt was fired and afterwards root was not detected
I'v tried chmod -R 777 . even from adb shell, tried opening magisk app and then doing these whole process... no luck
First, thanks for your supporting and your instruction
I just install October(6/10) update so any risk if i follow your instruction
Anyone know how to delete the update? I've downloaded and refuse to restart my device in the wake of these new development
enigma2446 said:
Anyone know how to delete the update? I've downloaded and refuse to restart my device in the wake of these new development
Click to expand...
Click to collapse
I also want to know this. I need to reboot but I don't want to move to the October patch.
Hexlay said:
Yep, i have it pre-installed, i did follow every step provided, but prompt is not showing up and afterwards it does not detect root... Well, i'v done it several times, i tried ./temproot.sh after install script, but still same...
Well, i guess i have to reboot
Edit: tried reboot, still same.... i'll write down what i have done exactly.
Rebooted dvice
Went into terminal emulator and executed ./taimen
After that went one step back with cd .. and executed chmod -R 777 scripts
Then went to pc and entered ADB shell and executed ./taimen there too, because otherwise i was getting This script must be run as root. Exiting. on install script
Then ran install script. Process did complete successfully, however no magisk prompt was fired and afterwards root was not detected
I'v tried chmod -R 777 . even from adb shell, tried opening magisk app and then doing these whole process... no luck
Click to expand...
Click to collapse
Can you post the output of the script?
logan2611 said:
Can you post the output of the script?
Click to expand...
Click to collapse
That's output every time, it finishes script successfully
Hexlay said:
That's output every time, it finishes script successfully
Click to expand...
Click to collapse
Sorry, screenshot didn't load the first time. Looks like all the files are already in place, try rebooting and running temproot.sh
running ./taimen just gives a "permission denied" error
Some1CP said:
running ./taimen just gives a "permission denied" error
Click to expand...
Click to collapse
If you are getting this on the phone, you need to use a terminal emulator with access to a directory in /data. I used Termux in my example.
If you want to use Termux, here is how to get taimen running:
Install Termux
Open Termux and let it install
Run termux-setup-storage
Push the ZIP to /sdcard/Download
On the phone, move the ZIP file from ~/storage/downloads to ~
Continue from step 4 in OP
logan2611 said:
If you are getting this on the phone, you need to use a terminal emulator with access to a directory in /data. I used Termux in my example.
If you want to use Termux, here is how to get taimen running:
Install Termux
Open Termux and let it install
Run termux-setup-storage
Push the ZIP to /sdcard/Download
On the phone, move the ZIP file from ~/storage/downloads to ~
Continue from step 4 in OP
Click to expand...
Click to collapse
How would I move it to ~ without root?
Edit: nevermind, got it to run.
Just need to figure out how to make the temproot work.
Some1CP said:
How would I move it to ~ without root?
Click to expand...
Click to collapse
In Linux ~ is a shortcut for the home directory, which is always owned by the current user. Root is not required to move the ZIP from ~/storage/downloads to ~ on Termux.
Ok I can't run installtemproot.sh in adb, and neither on the phone itself through termux. Is there something I'm missing? su can't be find on the phone.
Edit: It works if you use Jack Pal's terminal emulator and you cd into its directory on adb. Sadly magisk doesn't recognize it's installed.
I'm on October 5 2018 security update and should flash September 5 2019 try temp root?I know stay away October's 2019 that's patch,sean
logan2611 said:
Sorry, screenshot didn't load the first time. Looks like all the files are already in place, try rebooting and running temproot.sh
Click to expand...
Click to collapse
Sorry for wait time, literally had to wait for type-c to type-c connection -_- it's pain....
Anyway i did reboot and tried again with just temproot.sh, without repeating previous stuff. No prompt is fired, but output is success
Hexlay said:
Sorry for wait time, literally had to wait for type-c to type-c connection -_- it's pain....
Anyway i did reboot and tried again with just temproot.sh, without repeating previous stuff. No prompt is fired, but output is success
Click to expand...
Click to collapse
client: launching new main daemon process
Click to expand...
Click to collapse
The output suggests that Magisk started successfully. What does Magisk Manager look like after running that script?