Related
Mod Edit: Unstickied, placed link in wiki:http://forum.xda-developers.com/wiki/index.php?title=Nexus_One Thanks
This is an alternative approach of rooting the Nexus without touching the bootloader.
-no downgrade neccessary
-no battery modification neccessary
-no messing around with SD card slot
-you don't even have to open your phone...
Working and confirmed for ALL ROMs, including European Vodafone EPF30/FRF91, Korean FRF91, AT&T/T-Mo Stock including FRF91
-------
Credits:
-------
- The Android Exploid Crew:
http://c-skills.blogspot.com/2010/07/android-trickery.html
- Amon_RA
- cyanogen
-------
Notes:
-------
- The exploit wasn't found by me (see credits), I just implemented it as a proof of concept for the Nexus One
- Basically this method should work on all currently known ROM versions.
- I tested it on EPF30, Korean FRF91, Vodafone FRF91, US Stock FRF91.
- As usual when doing this kind of stuff: DO THIS AT YOUR OWN RISK.
- It could even work on other Android devices as long as their system partition is at
/dev/block/mtdblock3/ with yaffs2 file system and there is still some space left on the system partition (without any changes).
-------
Prerequisites:
-------
- Locked Nexus One
- Latest Android SDK incl. USB drivers
- Working ADB
- The file "freenexus.zip"
edit:
get it here:
http://multiupload.com/MVT98F5HBY
or
http://dl.dropbox.com/u/1327667/freenexus.zip
MD5: 947C20222056D7C070733E7FCF85CF15
-------
Step-by-step guide:
-------
1. install android sdk & USB drivers
2. extract the content of the zip file into the tools directory of SDK (i.e. \android-sdk-windows\tools)
-> For all Newbies: Take care that you extract the files directly to the tools folder and don't create a new subdirectory freenexus within tools!!! If you did, delete the folder and extract again!!! Check twice that there is no FOLDER freenexus in your tools directory before you continue!!!
3. open a command prompt (Windows: Start, Run, "cmd", OK; Linux: Terminal)
4. change to SDK tools directory (i.e. cd \android-sdk-windows\tools)
5. connect Nexus to USB and check if debugging mode is activated
(Settings/Application/Development/USB Debugging)
6. run "adb devices" in shell and see if there is a device listed. if not back to step 5 or reinstall USB-drivers
7a. for Windows: run "freenexus.bat" in command shell (this copies the neccessary files to /data/local/tmp)
7b. for Linux or manual installation: run the following commands
Code:
adb push freenexus /data/local/tmp/freenexus
adb push Superuser.apk /data/local/tmp/Superuser.apk
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
adb shell chmod 755 /data/local/tmp/freenexus
adb shell chmod 755 /data/local/tmp/busybox
8. run the following commands:
Code:
adb shell
(you should see a "$" prompt now)
cd /data/local/tmp
9. on your phone go to a screen where you can easily toggle wifi (widget or settings/wireless)
10. be prepared to toggle wifi immediately after you execute the next step
11. run
Code:
./freenexus
12. toggle wifi on
13. you should see something like that:
[*] Android local root exploid (C) The Android Exploid Crew
[*] Modified by ak for HTC Nexus One
[+] Using basedir=/sqlite_stmt_journals, path=/data/local/tmp/freenexus
[+] opening NETLINK_KOBJECT_UEVENT socket
[+] sending add message ...
[*] Try to invoke hotplug now, clicking at the wireless
[*] settings, plugin USB key etc.
[*] You succeeded if you find /system/bin/rootshell.
[*] GUI might hang/restart meanwhile so be patient.
13b) if you get "permission denied" error, you have most likely not followed the big red newbie hint after point 2. check this by entering "ls -l", if you see a "drwxr-xr-x" and not "-rwxr-xr-x" in front of the line where freenexus is listed you did not follow properly. Search the posts in the thread on how to correct this.
14. run
Code:
rootshell
15. if you succeeded you will be asked for a password, if not try again from step 10
16. enter the password "freenexus"
17. now you should see a "#" as a prompt -> you are root now
18. run the following commands:
Code:
./busybox cp busybox /system/bin
chmod 4755 /system/bin/busybox
busybox cp Superuser.apk /system/app
busybox cp su /system/bin
chmod 4755 /system/bin/su
rm /system/bin/rootshell
exit
exit
19. Check if you keep root rights:
Code:
adb shell
su
20. after you executed the su command the Superuser app on your device should ask you for allowance
21. you should see the "#" prompt again, if you didn't get that try su again
22. done
-------
Comments:
-------
- General
If you are not planning to wipe your data partition (what you probably will do when installing CM6 first time) you should think about deleting all the temp files still lying in /data/local/tmp (for safety reasons and to have more space on /data):
Code:
adb shell
cd /data/local/tmp
rm busybox
rm su
rm Superuser.apk
rm freenexus
rm flash_image (will only exist if you executed the steps below in recovery section)
- Installation of Custom Recovery
If you only want root rights you are done here. If you want to install custom ROMs you have to install
a custom recovery first. Easiest way would be to download "ROM Manager" from the market. There are plenty of tutorials on how to install custom recovery/ROM at xda.
Edit: It is safer to install the recovery manually. In this case or for those of you running into problems with installing custom recovery with ROM Manager (doesn't stick) you can continue with
these steps (without remount of system partition, now tested successfully):
1) Download recovery-RA-nexus-v1.7.0.1.img to the root directory of your SD-Card
- Note: UnMount your SD-Card after copying these files, but keep your phone plugged in
- or don't mount SD-Card at all and push the file via adb to /sdcard
2) Save file "flash_image" to sdk tools directory:
3) In your terminal run
Code:
adb push flash_image /data/local/tmp/flash_image
adb shell
su
- At this point, it will hang until you choose "Allow" on your phone with the SuperUser app pop-up
- $ should now be replaced with #
5) run the following commands:
Code:
[COLOR="Red"]mount -o rw,remount /dev/block/mtdblock3 /system[/COLOR]
cd /data/local/tmp
chmod 755 flash_image
[COLOR="Red"]./flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.1.img[/COLOR]
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
(and if everything worked fine:)
rm flash_image
Alternatively you can continue with step 9 and then steps 16-24 from the old rooting method tutorial
to manually install Amon_RA's recovery. You will also need the file flash_image for that (link taken from HBOOT thread).
- HBOOT
If you rooted from a Korean Rom or have installed the latest Vodafone Rom via PASSIMG you probably have
HBOOT 0.35 which makes it currently difficult to install Cyanogenmod (there is an assertion failure in the install script, at least with CM6 RC1/2. Maybe future versions of CM6 will include HBOOT 0.35 in the script) or other custom ROMs. (You are still on 0.33 if you just installed the Vodafone OTA Update)
There is a tutorial to revert HBOOT here:
http://forum.xda-developers.com/showthread.php?t=726258
Instead of using the EPF30 image you can also use any other PASSIMG file (at least if it has HBOOT 0.33,
otherwise this step wouldn't make sense...)
Note that when flashing a PASSIMG with a different HBOOT version there is a reboot after the HBOOT has been flashed, then after reboot the PASSIMG will be loaded again and the rest of the image will be flashed.
To check HBOOT and Radio version: press and hold trackball while turning on the phone. To exit select Reboot with Vol+/- and press Power button.
Caution:
After you have reverted your HBOOT, you have lost your root rights and you are back on stock recovery.
But you can (or have to) repeat the above procedure to get root rights back.
Edit:
The downgrading also downgrades your radio!!! Before installing CM6 you have to flash a Froyo Radio!
Latest one can be found here:
http://forum.xda-developers.com/showthread.php?t=723839
-------
Troubleshooting:
-------
After trying to flash a custom ROM with ROM Manager one user wasn't able to boot the phone normally and also no longer able to boot to recovery. In this rare case try to download a compatible PASSIMG file:
For example EPF30 (Europe Vodafone 2.1)
http://shipped-roms.com/shipped/Pas...ogle_WWE_1.14.1700.1_EPF30_release_signed.zip
or FRF91 (Europe Vodafone 2.2):
http://shipped-roms.com/shipped/Pas...on_VF_2.15.151.5_R_FRF91_MFG_Shipment_ROM.zip (<-this one is currently a zip in zip. You have to extract it once to get the working PASSIMG.zip)
(Appropriate US-PASSIMGs can also be found on shipped-roms.com, most likely EPE76)
Rename the file to PASSIMG.zip (case sensitive, Windows users take care that the file isn't called PASSIMG.zip.zip hidden extension)
Copy it to main folder of SD card.
Boot phone into Bootloader mode (press and hold trackball when turning on the phone, until fastboot mode starts)
Select Bootloader mode by pressing power button.
The bootloader should then start to analyse the PASSIMG.zip and ask you afterwards to install it.
You're phone (not your SD) will be completely wiped after the procedure but should work again (and can be rooted again...)
sweet!! been waiting for this! will try it tomorrow as soon as i wake up! will report back then!
edit: i cant download freenexus.zip maybe use another hoster?
file section edited.
Great tutorial ! Waiting for some feedbacks
(file link doesn't work)
dolomiti7 said:
file section edited.
Click to expand...
Click to collapse
On the left I can see just an empty folder named "SmartDrive"
link doesn't work
dolomiti7 said:
-> after clicking on "Smartdrive Gastzugang starten" you might get an error message, but after klicking ok on the error message
you should be able to access the folder "nexus" on the left side of the window anyway
Click to expand...
Click to collapse
No way! Can't do anything even after i press ok on the error message
if you click on that there should be a subfolder "nexus" that should be clickable too. at least it works here... anyway. someone wants to upload the file to a hoster? rapidshare... contact me
for the early adaptors (will only work 10 times):
rapidshare.com/files/409266634/freenexus.zip
MD5: 947C20222056D7C070733E7FCF85CF15
multiple download sites!:
http://www.multiupload.com/MVT98F5HBY
or here:
http://dl.dropbox.com/u/1327667/freenexus.zip
thank you. added the link.
This worked flawlessly.
Massive thanks.
Hi, I have a Italian Vodafone Nexus One with FRF91, i have followed all the steps and now in my apps there is Superuser Permission with green light. It means that i have root rights? Can I install Cyanogen Mod now? Thanks, excuse my English.
Worked perfectly on a stock AT&T N1 with FRF91. Thanks!
Excellent tutorial step by step...great work!
Can i change the password at the end?
So once gaining root, I can flash a custom recovery with rom manager without braking/unlocking the boot loader?
@fc_themaster:
if the superuser app popped up at step 19/20 then you have root rights. you can try to install ROM Manager from the market and install a custom recovery with that porgram. it also needs root rights so superuser should pop up again at that point.
@PSeeCO: you don't need to change a password. the password was only used for the temporary rootshell which you (hopefully) deletetd with the command "rm /system/bin/rootshell" in step 18. From that point on root rights are controlled via the Superuser app. If you install an already rooted custom ROM it is obsolete anyway.
@jivemaster: yes, we can! just use ROM Manager from the market to install custom recovery.
dolomiti7 said:
@PSeeCO: you don't need to change a password. the password was only used for the temporary rootshell which you (hopefully) deletetd with the command "rm /system/bin/rootshell" in step 18. From that point on root rights are controlled via the Superuser app. If you install an already rooted custom ROM it is obsolete anyway.
Click to expand...
Click to collapse
Perfect, thank you so much!
Is the any of LG_IME.apk that works on "Joestone's Gingerbread 2.3.2".
I've had extracted LG_IME form "Lavero Burgos's data2system mod of AOSP Joestone Gingerbread" ROM and have installed it to "Joestone's Gingerbread 2.3.2"
The problem is, it says force close.
Thanks
use this http://gt540.co.cc/index.php?dir=&file=LG_IME_2.3.zip
I don't know what went wrong, I've installed the zip package via recovery but it seems that the problem remains.
When I select LG IME as the input method, It does still says force close.
But thanks anyway
heres what to do with my file:
TUTORIAL #7
- Dowload LG_IME_data2system and unzip in desktop
- Open System folder and copy the 3 folders: app, lib2 and usr folders to C:\*SDK\platform-tools\
- Plug your phone to the computer
- Open a CMD terminal and type:
Code:
cd C:\*SDK\platform-tools
adb devices
adb remount
adb push app /system/app
adb push lib2 /system/lib
adb push usr /system/usr
adb kill-server
exit
- Unplug your phone
- Go to ROM Manager application and run Fix Permissions (DO NOT avoid this step, so you dont get FC's)
DONE!
Veronica
Sent from my GT540 using XDA App
It works, thanks Veronica
I've followed your tutorial step by step and it works without any problem. No more FC ...
Thanks Veronica
Nearly There. . .
Followed your guide right through. Only problem I have is the T9 (predictive) won't work, the little T9 button is disabled..... no FC's though. Any thoughts ??
lavero.burgos said:
heres what to do with my file:
TUTORIAL #7
- Dowload and unzip in desktop
- Open System folder and copy the 3 folders: app, lib2 and usr folders to C:\*SDK\platform-tools\
- Plug your phone to the computer
- Open a CMD terminal and type:
Code:
cd C:\*SDK\platform-tools
adb devices
adb remount
adb push app /system/app
adb push lib2 /system/lib
adb push usr /system/usr
adb kill-server
exit
- Unplug your phone
- Go to ROM Manager application and run Fix Permissions (DO NOT avoid this step, so you dont get FC's)
DONE!
Veronica
Sent from my GT540 using XDA App
Click to expand...
Click to collapse
can someone tell me why this method is not working for me ?? i've followed the instructions but.. FC's...
Please help before installing and apply nvidia patch my games like plant vs zombie running without problem.
but after unsuccessful attempt of play nvidia games on my deivce Samsung SGSL i9003.
i uninstall this, set plugin to default and uninstall drivers.
But Still my games are no longer running.
I face problem with plant vs zombie. it crash as it start but before chainfire3d it run perfectly.
waiting for reply asap..
manrock111 said:
Please help before installing and apply nvidia patch my games like plant vs zombie running without problem.
but after unsuccessful attempt of play nvidia games on my deivce Samsung SGSL i9003.
i uninstall this, set plugin to default and uninstall drivers.
But Still my games are no longer running.
I face problem with plant vs zombie. it crash as it start but before chainfire3d it run perfectly.
waiting for reply asap..
Click to expand...
Click to collapse
bro the same problem happened to my phone so i reflashed my custom rom.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I have the same problem. Chainfire caused me many problems. I want to completely remove it, but I can't.
I put another ROM and whiped data, and it still makes problems. Please help!
manrock111 said:
Please help before installing and apply nvidia patch my games like plant vs zombie running without problem.
but after unsuccessful attempt of play nvidia games on my deivce Samsung SGSL i9003.
i uninstall this, set plugin to default and uninstall drivers.
But Still my games are no longer running.
I face problem with plant vs zombie. it crash as it start but before chainfire3d it run perfectly.
waiting for reply asap..
Click to expand...
Click to collapse
Hy i have same problem . Can you solve this problem? /clear completly chainfire3d/
Same problem, I used to be able to run The Settlers and other games, now I can't..
I uninstalled drivers, set plugin to default, then uninstalled the app, but still it doesn't work
Having root access from recovery is a must to solve problems if you run into them (run "/system/lib/cf3d_uninstall.sh" as root to remove the driver and restore the old one)
1. boot into jb recovery mode
2. run "adb devices" - to make sure the phone drivers are ok (should output a long hex string and "device")
3. run "adb shell" from command prompt
4. in shell prompt "sh system/lib"
5. still in shell "sh /cf3d_uninstall.sh"
phone will reboot and you have working jb system
- it worked for me but no guarantee it'll work for you!
hope it helps.
if sh /cf3d_uninstall.sh doesnt work , try 'sh /system/lib/cf3d_uninstall.sh" instead.
another solve
guys at first i tried to use adb
i got no permissions
so i thought i can use terminal emulator
first open terminal emulator
write SU and give terminal the superuser rights
now use the command
"/system/lib/cf3d_uninstall.sh"
or
"sh /cf3d_uninstall.sh"
after success
your phone will stop giving orders and responding
now you can remove the battery and you are done
ty i hope i helped
mido1122 said:
guys at first i tried to use adb
i got no permissions
so i thought i can use terminal emulator
first open terminal emulator
write SU and give terminal the superuser rights
now use the command
"/system/lib/cf3d_uninstall.sh"
or
"sh /cf3d_uninstall.sh"
after success
your phone will stop giving orders and responding
now you can remove the battery and you are done
ty i hope i helped
Click to expand...
Click to collapse
Under JB, I don't find any system/lib folder at all... Any idea where's the chainfire3D placed in it?
Same problem in my gt2 p3100
manrock111 said:
Please help before installing and apply nvidia patch my games like plant vs zombie running without problem.
but after unsuccessful attempt of play nvidia games on my deivce Samsung SGSL i9003.
i uninstall this, set plugin to default and uninstall drivers.
But Still my games are no longer running.
I face problem with plant vs zombie. it crash as it start but before chainfire3d it run perfectly.
waiting for reply asap..
Click to expand...
Click to collapse
please help chainfire3d has spoiled my android gaming life.
Terminal emulator displaying ''not found''
mido1122 said:
guys at first i tried to use adb
i got no permissions
so i thought i can use terminal emulator
first open terminal emulator
write SU and give terminal the superuser rights
now use the command
"/system/lib/cf3d_uninstall.sh"
or
"sh /cf3d_uninstall.sh"
after success
your phone will stop giving orders and responding
now you can remove the battery and you are done
ty i hope i helped
Click to expand...
Click to collapse
Terminal emulator displaying ''not found''
dailyuse17 said:
Terminal emulator displaying ''not found''
Click to expand...
Click to collapse
Below is my Logs:
######## Below was executed from Windows command prompt. I have "adb.exe" installed in the Desktop\404 ##########
C:\Users\Chu\Desktop\404>adb kill-server
C:\Users\Chu\Desktop\404>adb wait-for-device
* daemon not running. starting it now *
* daemon started successfully *
C:\Users\Chu\Desktop\404>adb shell
########## After you've executed 'adb shell', i will login to the phone as user shell ##########
[email protected]:/ $ su
########## You have to switchuser to root to gain full access, as seen below, you are "root" ##########
[email protected]:
# cd /system
cd /system
[email protected]:/system # cd lib
cd lib
########## Above, i change directory to /system/lib ##########
[email protected]:/system/lib # ls cf*
ls cf*
cf3d_uninstall.sh
########## Found the file to be cf3d_uninstall.sh and execute the shell script with the command below ##########
[email protected]:/system/lib # sh cf3d_uninstall.sh
sh cf3d_uninstall.sh
rm failed for /system/lib/cf3d_sh, No such file or directory
usage: reboot [-n] [-p] [rebootcommand]
########## There, the phone will restart, and you'll get back your phone. Just ignore the "no such file or directory" error above. It'll still work ##########
Good luck.
manchuks said:
Below is my Logs:
######## Below was executed from Windows command prompt. I have "adb.exe" installed in the Desktop\404 ##########
C:\Users\Chu\Desktop\404>adb kill-server
C:\Users\Chu\Desktop\404>adb wait-for-device
* daemon not running. starting it now *
* daemon started successfully *
C:\Users\Chu\Desktop\404>adb shell
########## After you've executed 'adb shell', i will login to the phone as user shell ##########
[email protected]:/ $ su
########## You have to switchuser to root to gain full access, as seen below, you are "root" ##########
[email protected]:
# cd /system
cd /system
[email protected]:/system # cd lib
cd lib
########## Above, i change directory to /system/lib ##########
[email protected]:/system/lib # ls cf*
ls cf*
cf3d_uninstall.sh
########## Found the file to be cf3d_uninstall.sh and execute the shell script with the command below ##########
[email protected]:/system/lib # sh cf3d_uninstall.sh
sh cf3d_uninstall.sh
rm failed for /system/lib/cf3d_sh, No such file or directory
usage: reboot [-n] [-p] [rebootcommand]
########## There, the phone will restart, and you'll get back your phone. Just ignore the "no such file or directory" error above. It'll still work ##########
Good luck.
Click to expand...
Click to collapse
my phone camera doesnot work well due to chainfire3d how to uninstall completely . at this time i m completely uninstall the chai fire 3d but camera does not work . my camera shows the blur photos when in the camera mode
How to do this when installed it by mistake on samsung gt-i9505 please? thanks.
---------- Post added at 02:36 AM ---------- Previous post was at 02:05 AM ----------
Ok, like i didn't see the file in the folders concerned, this saved me (applied it without looking or searching the file i didn't see). big up and thanks.
http://forum.xda-developers.com/showpost.php?p=39301435&postcount=8
Help me please...
bolibo said:
Having root access from recovery is a must to solve problems if you run into them (run "/system/lib/cf3d_uninstall.sh" as root to remove the driver and restore the old one)
1. boot into jb recovery mode
2. run "adb devices" - to make sure the phone drivers are ok (should output a long hex string and "device")
3. run "adb shell" from command prompt
4. in shell prompt "sh system/lib"
5. still in shell "sh /cf3d_uninstall.sh"
phone will reboot and you have working jb system
- it worked for me but no guarantee it'll work for you!
hope it helps.
Click to expand...
Click to collapse
Hi.. i tried what you have suggest but still not able to recover my phone...please help me
:crying::crying::crying::crying::crying::crying::crying:
:\android-sdk-windows\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\android-sdk-windows\platform-tools>adb shell
[email protected]:/ $ sh /system/lib/cf3d_uninstall.sh
sh /system/lib/cf3d_uninstall.sh
mount: Operation not permitted
/system/lib/cf3d_uninstall.sh[4]: can't create /system/lib/libGLESv1_CM.so: Read
-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chmod /system/lib/libGLESv1_CM.so: Read-only file system
/system/lib/cf3d_uninstall.sh[11]: can't create /system/lib/libGLESv2.so: Read-o
nly file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chmod /system/lib/libGLESv2.so: Read-only file system
rm failed for /system/lib/cf3d_uninstall.sh, Read-only file system
rm failed for /system/lib/cf3d_sh, No such file or directory
usage: reboot [-n] [-p] [rebootcommand]
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
1|[email protected]:/ $
Help
Hello, guyz. the solution for this problem is that you should unistalled the divers you have installed to reduce the graphics (which u have installed in chainfire 3d) unistalled it and you are ready play your game again with the same graphic which you have earlier
thanks!
manju_xda said:
Hi.. i tried what you have suggest but still not able to recover my phone...please help me
:crying::crying::crying::crying::crying::crying::crying:
:\android-sdk-windows\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\android-sdk-windows\platform-tools>adb shell
[email protected]:/ $ sh /system/lib/cf3d_uninstall.sh
sh /system/lib/cf3d_uninstall.sh
mount: Operation not permitted
/system/lib/cf3d_uninstall.sh[4]: can't create /system/lib/libGLESv1_CM.so: Read
-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chown /system/lib/libGLESv1_CM.so: Read-only file system
Unable to chmod /system/lib/libGLESv1_CM.so: Read-only file system
/system/lib/cf3d_uninstall.sh[11]: can't create /system/lib/libGLESv2.so: Read-o
nly file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chown /system/lib/libGLESv2.so: Read-only file system
Unable to chmod /system/lib/libGLESv2.so: Read-only file system
rm failed for /system/lib/cf3d_uninstall.sh, Read-only file system
rm failed for /system/lib/cf3d_sh, No such file or directory
usage: reboot [-n] [-p] [rebootcommand]
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
reboot: Operation not permitted
1|[email protected]:/ $
Click to expand...
Click to collapse
You must be rooted to do that.
Help!!
El_Dark said:
You must be rooted to do that.
Click to expand...
Click to collapse
Hi, i'm a boy from Finland. I have the same problem as "manju_xda" but i have the root permissions in my device..
The question is.. .. I'm stucked with chainfire 3d and my adb shell tells that "adbd cannot run as root in production builds" .. What to do?
And sorry for my bad english
For those who found this thread on Google, I found my solution in here: http://forum.xda-developers.com/showthread.php?t=2362873
So I'm an idiot. Anyway, I recently installed cyanogenmod with CWM recovery (on a Nexus 7) and decided to try one of the largest grids for the lock screen security. Needless to say it was soon forgotten. I've tried the gmail reset but it says the details are incorrect even though I can sign in with them on my PC. My guess is that it can't connect to gmail for authentication due to the firewall I'm using.
Edit: Solution
Factory reset from CWM, that's it.
RoberGalarga said:
Factory reset from CWM, that's it.
Click to expand...
Click to collapse
Not the solution I was aiming for.
Fortunately I found http://forum.xda-developers.com/showthread.php?t=1800799
However this does not work for cyanogenmod as they use an additional system. I had no knowledge of this beforehand but a comment on the above post led me to believe something was different. I decided to pull /data/system folder so I could investigate further. I found cm_gesture.key which after looking it up, I found out it's cyanogenmods additional key file.
I decided to remove this file using the same method as the above post and it worked perfectly. After a reboot the pattern screen is still there but any input is correct.
Mini Cyanogenmod 10.1.2 pattern unlocking guide:
If ADB won't work from android reboot into CWM recovery (other custom recoveries may work). Open a CMD (ADB will need to be installed and setup).
Enter the each of the following:
Code:
adb shell rm /data/system/gesture.key
Code:
adb shell rm /data/system/cm_gesture.key
Code:
adb reboot
It should reboot into android and now any pattern will be correct. You should now go into settings and reconfigure your lock screen.
This works if you only have/delete /gesture.key
works on 4.4.2
Trying to make this work on CWM 13. It doesnt, any tips? forgot my 6x6 lockscreen which is also invisible...
Revome the unlock pattern! [CM13.0 tested]
Cryorus said:
Trying to make this work on CWM 13. It doesnt, any tips? forgot my 6x6 lockscreen which is also invisible...
Click to expand...
Click to collapse
FINALLY I HAVE A SOLUTION!
Version 1 (Custom Recovery):
------------
Get the updated version of TWRP (twrp.me). Flash it via Odin or whatever you use and boot into it (Vol Up + Home + Power).
1) go to Advanced > File Manager
2) then go to '/data/system'
3) press on 'gatekeeper.password.key' > Delete > Swipe to Confirm
4) repeat 3) with 'gatekeeper.pattern.key'
5) Reboot & be happy!
Version 2 (Android Debugging Bridge - adb):
-------------------------------------------------------
Just follow these steps:
1) make sure your device shows up here:
Code:
adb devices
2) restart adb as root:
Code:
adb root
3) start the device-shell:
Code:
adb shell
4) make sure to have su access:
Code:
su
5) go to the 'system' directory in the 'data' folder:
Code:
cd /data/system
6) remove the pattern:
Code:
rm gatekeeper.password.key
7) remove the password sequence:
Code:
rm gatekeeper.pattern.key
8) exit the shell:
Code:
exit
9) reboot to be happy again:
Code:
adb reboot
That's it! Hope I was able to help you!
~ Kerskes ~
Awesome. Thanks for sharing your research.
Kerskes said:
FINALLY I HAVE A SOLUTION!
Version 1 (Custom Recovery):
------------
Get the updated version of TWRP (twrp.me). Flash it via Odin or whatever you use and boot into it (Vol Up + Home + Power).
1) go to Advanced > File Manager
2) then go to '/data/system'
3) press on 'gatekeeper.password.key' > Delete > Swipe to Confirm
4) repeat 3) with 'gatekeeper.pattern.key'
5) Reboot & be happy!
Version 2 (Android Debugging Bridge - adb):
-------------------------------------------------------
Just follow these steps:
1) make sure your device shows up here:
Code:
adb devices
2) restart adb as root:
Code:
adb root
3) start the device-shell:
Code:
adb shell
4) make sure to have su access:
Code:
su
5) go to the 'system' directory in the 'data' folder:
Code:
cd /data/system
6) remove the pattern:
Code:
rm gatekeeper.password.key
7) remove the password sequence:
Code:
rm gatekeeper.pattern.key
8) exit the shell:
Code:
exit
9) reboot to be happy again:
Code:
adb reboot
That's it! Hope I was able to help you!
~ Kerskes ~
Click to expand...
Click to collapse
Thanks a ton man !
Acrylate said:
Not the solution I was aiming for.
Fortunately I found http://forum.xda-developers.com/showthread.php?t=1800799
However this does not work for cyanogenmod as they use an additional system. I had no knowledge of this beforehand but a comment on the above post led me to believe something was different. I decided to pull /data/system folder so I could investigate further. I found cm_gesture.key which after looking it up, I found out it's cyanogenmods additional key file.
I decided to remove this file using the same method as the above post and it worked perfectly. After a reboot the pattern screen is still there but any input is correct.
Mini Cyanogenmod 10.1.2 pattern unlocking guide:
If ADB won't work from android reboot into CWM recovery (other custom recoveries may work). Open a CMD (ADB will need to be installed and setup).
Enter the each of the following:
Code:
adb shell rm /data/system/gesture.key
Code:
adb shell rm /data/system/cm_gesture.key
Code:
adb reboot
It should reboot into android and now any pattern will be correct. You should now go into settings and reconfigure your lock screen.
Click to expand...
Click to collapse
Thanks man i was wondering and worried that i would have to reset my phone again .
wajeehuzkhan said:
Thanks man i was wondering and worried that i would have to reset my phone again .
Click to expand...
Click to collapse
Too late for me, already reseted my phone
I'm on lineage
After a softbrick I deleted these two files.
not I can pass the lockscreen again! nice!
now I can't set a new lockpattern...
How can I fix this?
sejmand said:
I'm on lineage
After a softbrick I deleted these two files.
not I can pass the lockscreen again! nice!
now I can't set a new lockpattern...
How can I fix this?
Click to expand...
Click to collapse
Did you manage to find any solution? I'm on LG G5 and get an FC when I try to open Lock screen settings.
Hassaan Masroor said:
Did you manage to find any solution? I'm on LG G5 and get an FC when I try to open Lock screen settings.
Click to expand...
Click to collapse
Finally, I did a hardreset with wipe data partition. After that I use a pin and never had the problem again...
(Do not remove files, rename them... Remember to see beforehand "ls -l" - access permissions and owners.)
With Lineage OS 14.1-20170607-nightly I succeded with as root:
Code:
mv /data/system/locksettings.db /data/system/locksettings.db_disabled
+ two subsequent reboots.
Settings are available and functional after it.
P.S.
The following was done before the trick above, but I'm not sure final permissions should be exactly as below (I did certain moves before it, but finished with the following):
Code:
# chown system.system /data/system/gatekeeper.pa*
# chmod 660 /data/system/gatekeeper.pa*
# ls -l /data/system/gatekeeper.pa*
-rw-rw---- 1 system system 0 2017-06-13 20:40 /data/system/gatekeeper.password.key
-rw-rw---- 1 system system 58 2017-06-13 20:40 /data/system/gatekeeper.pattern.key
Removing-renaming of the files will remove the pattern and fully unlock screen... and will break Settings app functionality (not able to set up new lock of any type). If files are back with these permissions - the pattern is back.
The following is definitely so, sure:
Code:
# ls -lh /data/system/locksettings.db
-rw-rw---- 1 system system 20K 2017-06-13 12:26 /data/system/locksettings.db
P.S.S. Ideas have been found here - https://forum.xda-developers.com/showthread.php?t=1800799&page=15
Hi Kerskes,
Thanks for the solution. It does work also on my hlte phone with Linage 14.1.
But I am seeing only one problem which is addressed by others as well.
That is Settings crashes everytime I want to set new security setting for lockscreen.
Do you have any proposals or solutions?
Also I would request Admin to set this as unsolved or open detach to new thread for the above issue.
Kerskes said:
FINALLY I HAVE A SOLUTION!
~ Kerskes ~
Click to expand...
Click to collapse
---------- Post added at 08:50 AM ---------- Previous post was at 08:32 AM ----------
Thanks Anker,
Your solution did wonderfully worked on Linage 14.1 over HLTE Phone.
I restarted after renaming locksettings.db using SolidExplorer (With Root). Then I needed one restart and Settings did responded properly for Lock Screen Pattern setting. I also observed that the gatekeeper.pa* files which I had deleted were also created again but they has only 600 file permissions. Soon I modified the file properties in SolidExplorer with proper 660 file permissions. Once again thanks a lot.
I apologize for my stupid previous post which I posted without seeing your solution.
B Anker said:
(Do not remove files, rename them... Remember to see beforehand "ls -l" - access permissions and owners.)
Click to expand...
Click to collapse
Hi brothers
i really don't know what to do
I'm trying to run a script.sh and i think i did everything possible to run it, but yet
it says plz blah blah blah blah be rooted first ( and I'm already rooted )
cd /sdcard << here where is the script located
su
sh script.sh
[now I'm getting the msg about being root first]
..
I'm getting another error too, saying something about permission denied!!
now how to change the permission
I believe that i should use chmod +x script.sh OR chmod +x 755 script.sh OR chmod +x 777 script.sh << error error error
WHAT SHOULD I DO TO RUN THIS FU***** SCRIPT!!!!!!!!!!!!!
what is this .. nobody!!!!
i'll keep posting until somebody response
Me-Nex S said:
Hi brothers
i really don't know what to do
I'm trying to run a script.sh and i think i did everything possible to run it, but yet
it says plz blah blah blah blah be rooted first ( and I'm already rooted )
cd /sdcard << here where is the script located
su
sh script.sh
[now I'm getting the msg about being root first]
..
I'm getting another error too, saying something about permission denied!!
now how to change the permission
I believe that i should use chmod +x script.sh OR chmod +x 755 script.sh OR chmod +x 777 script.sh << error error error
WHAT SHOULD I DO TO RUN THIS FU***** SCRIPT!!!!!!!!!!!!!
Click to expand...
Click to collapse
can you please post that script?
as of changing permission use chmod 0755 script.sh
as android/busybox chmod binary does not uses the chmod +x or chmod a+x notation
and make sure that su binary is installed i.e phone is rooted
here is the script
https://www.dropbox.com/s/8atidhjswrts7qe/yamas.sh
Solution
You need to root your phone.
Also you must have Busy Box Installed.
Here is the link to Google Play of that busybox app: https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer
Don't install the few latest versions because it is in nightlies.
I use Samsung Galaxy Y and I use the version 1.18.2.
Reboot your phone after installation.
Also you must have script manager installed.
Here is the link to Google Play of that manager app: https://play.google.com/store/apps/details?id=os.tools.scriptmanager
Open Script Manager and give super user access.
Tap on Menu > Advanced Options > Config
Scroll down until you see Browse as Root
Tap on it and press the back button to save
Once again grant Script Manager SuperUser Access to save config
Exit Script Manager
Now again open Script Manager and browse for your script file (yamas.sh)
Tap on it and set properties to:
Favorites (Star Icon)
Root (Green Android Skull Icon)
After setting properties, tap on Run to execute the script installer.
When executed, it will do initial test, be patient and wait for it to complete its tasks.
Press thanks if I have helped.
I'm gettingthe same error .. i've done evrything u've said but still .. here is the error msg .. even if i give the script the root permission, still it ask for permission again i dont know why!!
Error resolving interpreter:/bin/sh does not exist
Using default shell
exec sh '/storage/emulated/legacy/yamas.sh'
[email protected]:/ # exec sh '/storage/emulated/legacy/yamas.sh'
You are not running this script as root.
Please become root (e.g. "su") before launching this script
Answer
Me-Nex S said:
I'm gettingthe same error .. i've done evrything u've said but still .. here is the error msg .. even if i give the script the root permission, still it ask for permission again i dont know why!!
Error resolving interpreter:/bin/sh does not exist
Using default shell
exec sh '/storage/emulated/legacy/yamas.sh'
[email protected]:/ # exec sh '/storage/emulated/legacy/yamas.sh'
You are not running this script as root.
Please become root (e.g. "su") before launching this script
Click to expand...
Click to collapse
Download a root checker app from the play store and check whether your phone is really rooted.
If no, try to root again by following tutorials on xda.
If yes, update su binaries.
Also go to settings / preferences of superuser app, and click automatic response and then select 'allow'.
That script was placed in sd card right?
Then it maybe the app which copies to a specified location before executing it.
---------- Post added at 07:21 AM ---------- Previous post was at 06:35 AM ----------
See the link again. I added more information.
http://forum.xda-developers.com/showthread.php?t=2620394