Related
I decided to put together a nice, straightforward tutorial on how to root and unlock your device. I have recently joined the Android scene myself, and the XDA forums have been invaluable to my learning process. I did hit a few brick walls in the process (and nearly bricked my phone as well) before I finally achieved a 100% working, rooted, unlocked ROM installation. So, I just wanted to put together a short, easy to follow guide on rooting and unlocking, which will (hopefully) avoid you extra time / headache.
Note: It is quite possible (though not certain) that you may lose your current data after the unlock process, so make sure to make a backup before you proceed.
Pre-Requisites:
- Atrix 4G (AT&T)
- Any firmware up to 4.5.91 (which is currently the latest official - as of 8/4/11)
- A Windows PC
- Current Motorola drivers for your device installed on your PC
Required Files:
Android Root and Unlock (2011-08-04).zip
This archive contains Fastboot, ADB, Tenfar's ClockWorkMod, Pudding (v2), and RSD Lite 5.3.1 (which is all you'll need). I put it together into one package to save you a bit of time, but all the credit goes to the original devs / creators.
Step 1 - Unlock the Bootloader
Extract the provided archive into a folder on your PC. Let's assume this is "C:\Atrix\".
Install RSD Lite 5.3.1 program on your Windows machine.
Make sure the latest Motorola USB drivers for your Atrix are installed on your PC.
Run the RSD Lite program on your PC.
Power down your Atrix and connect to your PC via USB.
Power on your Atrix, and immediately hold the Volume Down button until you see a menu pop up. This will be a text menu which will appear at the top of your screen, and the first option you'll see will be "Fastboot". Cycle the menu by pressing the Volume Down button until you get to the "RSD" menu option. Press the Volume Up button to launch the RSD support on your Atrix.
You should now see the phone appear in the RSD Lite program interface on your PC (in the bottom menu). Click on it. You should see some data about your Atrix appear in the Device Properties pane.
Hit the "..." button in the RSD Lite program to bring up the file menu and select the "4547-fix-try2.sbf" (included in the archive above). This is Pudding. It will unlock your Atrix in just a moment.
Hit the "Start" button. RSD Lite will flash your phone. This process will be fairly quick, and your Atrix will reboot once or twice. After your Atrix boots back into Android, power down your phone and close the RSD Lite program on your PC (ignore the warning... the process is complete... if it wasn't complete, you would not be able to boot up into Android).
Power down your Atrix once again. Leave it connected to your PC via USB. Power it on again and hold the Volume Down key to get to the boot menu (as before). This time, select the "Fastboot" option by pressing the Volume Up button.
Open up the Command Prompt on your PC (Run 'cmd', or browse for it in your 'Accessories' application menu) and go to C:\Atrix\ (or the directory where you extracted the provided archive).
Type in the following command:
fastboot oem unlock
You will see a message pop up with a warning about unlocking your device. Assuming you are here, you don't care about this, so just make note of the device id that the message provides.
Type in the command again, this time with the device id:
fastboot oem unlock ### ,
where ### is the device id you noted above.
Type:
fastboot reboot
That's it! Your device now has an unlocked bootloader.
Step 2 - Flash the ClockWorkMod
ClockWorkMod ("CWM") will allow you to make backups of your current system, as well as install mods and ROMs.
Reboot your Atrix.
Hold the Volume Down button as the device powers up to get to the boot menu. (You should be familiar with this by now.)
Select the "Fastboot" option from the menu by pushing the Volume Up button.
Type the following command from the command prompt on your PC (assuming you're still in the C:\Atrix\ directory, or the directory where you extracted the provided archive):
fastboot flash recovery recovery-en-goapk-0630-1029.img
Type into the command prompt:
fastboot reboot
You're done. You will now be able to launch CWM from the boot menu by selecting the "Android Recovery" option. Again, the boot menu cycles with the Volume Down key, and you make a selection with the Volume Up key. If you selected the wrong option, just pull your battery and try again.
Step 3 - Root Your Device
Rooting will give you the "Superuser" program in Android and allow you to provide superuser permissions to apps.
Reboot your device. As it powers on, hold the Volume Down button to get into the boot menu. Select the "Fastboot" menu option using the Volume Up key.
Type the following commands into the command prompt on your PC (assuming you're still in the C:\Atrix\ directory, or where you extracted the provided archive):
fastboot flash preinstall preinstall.img
fastboot reboot
Wait until your device boots fully into Android.
On the command prompt on your PC, type in the following commands, sequentially (executing each one-by-one, i.e., hitting the enter key after each):
adb shell
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
Done! You should now see the "Superuser" program as one of your Android's apps.
You are now unlocked, rooted and have CWM installed! You are ready to mod / ROM your Atrix.
what if...? At step 4 always get permission denied after
/preinstall/dosu ?
Rgds
antoniolcrd said:
what if...? At step 4 always get permission denied after
/preinstall/dosu ?
Rgds
Click to expand...
Click to collapse
Keep typing commands. It'll look like an error but keep going.
Sent from my MB860 using XDA App
Maybe out of luck...
check this pls:
C:\tools>adb shell
$ /preinstall/su
/preinstall/su
Permission denied
$ /bin/mount /system -o remount,rw
/bin/mount /system -o remount,rw
/bin/mount: permission denied
$ cp /preinstall/su /system/bin/su
cp /preinstall/su /system/bin/su
cp: /system/bin/su: Read-only file system
$ chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
Unable to chmod /system/bin/su: Read-only file system
$
This is one of the most n00b friendly guides I ever read. I can picture each step in my head as I read the instructions.
EDIT: This can go either way. I find it easier just to flash a ROM that's pre-rooted after unlocking the BL and installing CWM when it comes to step 3.
Did you run through steps 1-3 as well?
The second command should be "/preinstall/dosu".
antoniolcrd said:
check this pls:
C:\tools>adb shell
$ /preinstall/su
/preinstall/su
Permission denied
$ /bin/mount /system -o remount,rw
/bin/mount /system -o remount,rw
/bin/mount: permission denied
$ cp /preinstall/su /system/bin/su
cp /preinstall/su /system/bin/su
cp: /system/bin/su: Read-only file system
$ chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
Unable to chmod /system/bin/su: Read-only file system
$
Click to expand...
Click to collapse
No way.
Nickel3ack said:
Did you run through steps 1-3 as well?
The second command should be "/preinstall/dosu".
Click to expand...
Click to collapse
I´ve tried this command also. Pls check:
C:\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# /bin/mount/system -o remount,rw
/bin/mount/system -o remount,rw
bash: /bin/mount/system: Not a directory
[email protected]:/# cp /preinstall/su /system/bin/su
cp /preinstall/su /system/bin/su
cp: cannot create '/system/bin/su': Read-only file system
[email protected]:/# chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
chmod: /system/bin/su: Read-only file system
[email protected]:/#
Holy Crap I Think I'm Bricked
Ok guy, I just knew this was gonna happen.
Step one, part 8. After my phone rebooted my Atrix says:
failed to boot 0x1000
No OS detected, going to RSD mode in 5 seconds
Okay, now what? LOL HELP!
Don't Panic
sonnyjame5902 said:
Ok guy, I just knew this was gonna happen.
Step one, part 8. After my phone rebooted my Atrix says:
failed to boot 0x1000
No OS detected, going to RSD mode in 5 seconds
Okay, now what? LOL HELP!
Click to expand...
Click to collapse
No... don't worry. It's not a brick. Worst case you can restore the stock ROM.
1st Thing to try:
Basically, just wait a bit after it says "failed to boot"... don't press anything... then a menu will pop up. Before it can go to RSD, press the Volume Down key to get to Fastboot. Press Volume Up to get into Fastboot. Continue with steps 11-15. If this unlocks the bootrom, your error should disappear and you'll have your fully functional Android back.
2nd thing to try:
Just wait a bit after it says "failed to boot"... don't press anything... then a menu will pop up. Let the phone go into RSD. Go back to the RSD Lite program on your PC and repeat the Unlock process. Hopefully this time it will work.
3rd thing to try:
If not.... go to the Firmwares Superthread here on XDA and download the ROM appropriate for your carrier. Flash it onto your device via RSD (same method for flashing as above, except select the SBF you downloaded from the thread). This will get your device back into operation at least (you will lose all your data tho, so I'd try the other 2 methods first).
Friggin Cheers Mate! Got it all set up with option 2, and now I'm rooted and SU! And they said it couldn't be done after the Gingerbread OTA update! Bollocks!
You should recheck your steps, cause I can't get CWM without being rooted. Cannot use root explorer to delete install.recovery. sh without superuser permission.
Dell2 said:
You should recheck your steps, cause I can't get CWM without being rooted. Cannot use root explorer to delete install.recovery. sh without superuser permission.
Click to expand...
Click to collapse
The method for CWM described here is to flash the CWM directly to your recovery partition. All it needs is for the device to have an unlocked bootloader. You don't need to be rooted for this. Rooting only affects the way your Android OS permissions apps. You'll definitely need to be rooted to install CWM via ROM Manager or Titanium Backup. This is not that method.
can i just root with step 3 or do i have to unlock first?
Just out of curiosity I see in the OP that this should not affect data - what evidence is there of this being the case with 4.5.91 OTA?
This unlock method modifies the boot sectors only. Your data is basically untouched. The method is actually well documented here on XDA. I just made this brief guide to be noob friendly. It actually summarizes a few working techniques. I unlocked and rooted by own, new AT&T Atrix using this method, which had the 4.5.91 OTA.
Anyway, not sure why people think they are bricking their phones. As long as the device turns on and you can get to the boot menu and back into RSD mode, you can always flash a stock ROM and be back to a functioning device. Only thing you risk losing is your data in any case.
Nickel3ack said:
This unlock method modifies the boot sectors only. Your data is basically untouched. The method is actually well documented here on XDA. I just made this brief guide to be noob friendly. It actually summarizes a few working techniques. I unlocked and rooted by own, new AT&T Atrix using this method, which had the 4.5.91 OTA.
Anyway, not sure why people think they are bricking their phones. As long as the device turns on and you can get to the boot menu and back into RSD mode, you can always flash a stock ROM and be back to a functioning device. Only thing you risk losing is your data in any case.
Click to expand...
Click to collapse
This is just the first time I've read about being able to work on 4.5.91 without wiping the user data, so I was curious how this method differed from the others that were out there (mrramirezusa and the original pudding). Thanks for the info.
Really dumb question, but before I start, do I want my USB connection to be USB Mass STorage, None, WIndows Media Sync, or Motorola Phone Portal?
im getting error when i click start button it gives error of failed flashing
jeffhwitz said:
Really dumb question, but before I start, do I want my USB connection to be USB Mass STorage, None, WIndows Media Sync, or Motorola Phone Portal?
Click to expand...
Click to collapse
For RSD, none.
EDIT
Now having done this I can say it doesn't make any difference because this is all done outside of the Android Operating System.
Well, I did it and I did irritatingly lose everything in my /data. Luckily I've got everything backed up. Came from the 4.5.91 OTA and other than rooted was totally stock. Did give me a failed to boot 0x1000, pulled batt, restarted and did fastboot, did the unlock successfully (i.e. didn't flash any additional files so per the posts no reason I should have lost everything but I still did).
So, it does seem like more often than not doing this from the real actual unmodified OTA will cause a loss of user data as has been stated even though sometimes it doesn't seem to.
Does GingerBreak work with this version of Gingerbread 4.5.601.A955.Verizon.en.us? My phone is currently rooted with Z4Root 1.3. Is there an easy way of doing this?
Sam
Use the d3 root method. Works fine.
CM7GB-601
The D3 one click didnt work for me. It tries to reboot and the phone sits at the "Battery OK OK to Program Transfer Mode: USB" mode.
I was rooted before the update. I never used ROMS or anything just rooted for wireless tether and T backup. Not sure how to proceed but Im pretty happy with the update, fixed a bunch of issues for me.
Anyone else not able to root after the ginger ota?
acavallini said:
The D3 one click didnt work for me. It tries to reboot and the phone sits at the "Battery OK OK to Program Transfer Mode: USB" mode.
I was rooted before the update. I never used ROMS or anything just rooted for wireless tether and T backup. Not sure how to proceed but Im pretty happy with the update, fixed a bunch of issues for me.
Anyone else not able to root after the ginger ota?
Click to expand...
Click to collapse
I have the phone in PC Mode (instead of Mass Storage.) I don't know if that makes a difference.
The D3 Method worked great for me and my wife's phone.
Hi everyone,
I have the same question as CSSZiegler, but want to expand on it a little bit...
I have a Droid 2 that was rooted with Z4Root 1.3 several months ago. I also have SetCPU, SuperUser and Titanium Backup. No custom ROMs installed. Big Red just pushed down GB, and of course, I've lost root access. I'd like to regain root again without losing any contacts, Handcent messages, etc. I've read on several forums that the D2 can be rooted just like the D3 with a simple "one-click" operation referenced by quarky42 earlier.
Any opinions or experience with this? I greatly appreciate any and all assistance!
update
My phone downloads the update, I click install now... it reboots and starts the install, then about 35% of the way through, it turns to a triangle with ! Inside. Phone reboots and displays message software update failed. Anyone know where to find a logfile or have any suggestions?
Droid2 android 2.2.. rooted. No custom rom.
Did you fully SBF to stock using RSDLite?
Also http://forum.xda-developers.com/showthread.php?t=1246673 has a flashable version.
I will as soon as I get a computer again, thanks for the link. Unfortunately my mobo died yesterday. So I was hoping for an alternative solution. It would also be nice to keep all my texts.. I'll google that one.
So any ideas on the logs or an alternative solution?
Ok... I have also used Z4root. I got the update, it failed. I unrooted with Z4root. Re-downloaded the update, it failed. I tried to reinstall the kindle and blockbuster app. Re-downloaded the update, it failed. I reset to factory. Re-downloaded the update, it failed. Downloaded root checker, ran root checker, it said that I am not rooted. Re-downloaded the update, it failed.
This is the Detailed Results I got from the Advanced Root Checker:
Root Access is not properly configured or was not granted.
Superuser.apk - is NOT installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your DROID2 device by Root Checker version 3.7 from joeykrim in the Android Market -
___________________________________________
Have I done something wrong??? I don`t understand why I can not get the update. Please help.
Ardalee said:
Ok... I have also used Z4root. I got the update, it failed. I unrooted with Z4root. Re-downloaded the update, it failed. I tried to reinstall the kindle and blockbuster app. Re-downloaded the update, it failed. I reset to factory. Re-downloaded the update, it failed. Downloaded root checker, ran root checker, it said that I am not rooted. Re-downloaded the update, it failed.
This is the Detailed Results I got from the Advanced Root Checker:
Root Access is not properly configured or was not granted.
Superuser.apk - is NOT installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your DROID2 device by Root Checker version 3.7 from joeykrim in the Android Market -
___________________________________________
Have I done something wrong??? I don`t understand why I can not get the update. Please help.
Click to expand...
Click to collapse
I answered the thread you started with the process to un root and put your phone back to stock.
acavallini said:
The D3 one click didnt work for me. It tries to reboot and the phone sits at the "Battery OK OK to Program Transfer Mode: USB" mode.
I was rooted before the update. I never used ROMS or anything just rooted for wireless tether and T backup. Not sure how to proceed but Im pretty happy with the update, fixed a bunch of issues for me.
Anyone else not able to root after the ginger ota?
Click to expand...
Click to collapse
I had the same problem, and I think it is is because we already had Superuser installed. To remove it, from the directory where you downloaded the one click root, open the command window, then type adb shell
when you hit enter, the next line should end with a #
if it's $, run the one click again, then start this over
once you have the # prompt, type
mount -oremount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
hitting enter after each line.
After doing this, run the one click, and it should be fine. Worked great for me.
808Bill said:
I had the same problem, and I think it is is because we already had Superuser installed. To remove it, from the directory where you downloaded the one click root, open the command window, then type adb shell
when you hit enter, the next line should end with a #
if it's $, run the one click again, then start this over
once you have the # prompt, type
mount -oremount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
hitting enter after each line.
After doing this, run the one click, and it should be fine. Worked great for me.
Click to expand...
Click to collapse
Awesome! That did the trick, thanks for the info
808Bill said:
I had the same problem, and I think it is is because we already had Superuser installed. To remove it, from the directory where you downloaded the one click root, open the command window, then type adb shell
when you hit enter, the next line should end with a #
if it's $, run the one click again, then start this over
once you have the # prompt, type
mount -oremount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
hitting enter after each line.
After doing this, run the one click, and it should be fine. Worked great for me.
Click to expand...
Click to collapse
I'm having the same problem as the original poster... Installed gingerbread with z4root... phone was already rooted.. Now I have superuser and can't get rid of it.. .Tried unrooting through z4 and it doesn't work... Tried gingerbreak and the one click root through windows... Neither of those worked...
I either want to root through gingerbread or just get rid of the superuser.
when I type adb shell in command prompt (in windows 7) it says adb is not recognized as an internal or external command, operable program or batch file.
Any ideas? Thanks.
droid888 said:
I'm having the same problem as the original poster... Installed gingerbread with z4root... phone was already rooted.. Now I have superuser and can't get rid of it.. .Tried unrooting through z4 and it doesn't work... Tried gingerbreak and the one click root through windows... Neither of those worked...
I either want to root through gingerbread or just get rid of the superuser.
when I type adb shell in command prompt (in windows 7) it says adb is not recognized as an internal or external command, operable program or batch file.
Any ideas? Thanks.
Click to expand...
Click to collapse
I would SBF back to Froyo with RSDLite and install the OTA GB from phone info updates. After that use the D3 one click root method and you're golden.
droid888 said:
I'm having the same problem as the original poster... Installed gingerbread with z4root... phone was already rooted.. Now I have superuser and can't get rid of it.. .Tried unrooting through z4 and it doesn't work... Tried gingerbreak and the one click root through windows... Neither of those worked...
I either want to root through gingerbread or just get rid of the superuser.
when I type adb shell in command prompt (in windows 7) it says adb is not recognized as an internal or external command, operable program or batch file.
Any ideas? Thanks.
Click to expand...
Click to collapse
That error is usually because your trying to run the program from the wrong directory. Make sure your command line is started from the folder that adb.exe is located in. You can do this by Shift and right mouse button and “open command window here”.
acavallini said:
That error is usually because your trying to run the program from the wrong directory. Make sure your command line is started from the folder that adb.exe is located in. You can do this by Shift and right mouse button and “open command window here”.
Click to expand...
Click to collapse
I searched the phone's sd card.. I couldn't find it... do you know where adb.exe is located?
The fact that he said to hold shift and the right mouse button should tell you he's talking about a folder on your computer and not on your SD card.
idefiler6 said:
The fact that he said to hold shift and the right mouse button should tell you he's talking about a folder on your computer and not on your SD card.
Click to expand...
Click to collapse
Finally got it to work... now.. I used motorola one click root.exe where you use the exe on the computer. Just out of curiosity, is there a one click method to unroot? Thanks!
As you may know, some Android games especially most Gameloft games are not compatible with the Kindle Fire. So in efforts to find a way to make certain Gameloft games to work such as Modern Combat 2 and Shrek Kart and others, I resorted to editing my build.prop in the systems folder to make my device compatible with the apps. So I copied the original build.prop file, renamed it, and saved it to my SD Card folder. I took the copy I made and I then replaced it with the build.prop from HTC Glacier. (I never knew what could possibly happen) So then to apply those settings you have to reboot the device. I rebooted the Kindle and now it won't boot up. It get's to the Kindle Fire screen when booting up but after several seconds it just shows a black screen. No physical damage has been incurred to it but I feel like my stupid mistake of modding the build.prop resulted in the Kindle Fire unable to boot up correctly. It also isn't recognized by the PC when I hook it up to a USB cable. So far I've found nothing that could help to solve this. I've seen a Factory Default Settings Cable which is a special cable to reverts the device to its factory default settings but I'm not too sure if that would work. I'm in desperate need of help as in I use my Kindle Fire for everyday work and play. Thanks.
EDIT: I've tried adb push and renaming and moving the build.prop into the /system/ but returns that it is a Read-File System Only. Also adb shell and su doesn't work as in it ends up with segmentation fault. I've tried to zergRush root it and permanently root it using KFU but it ends up with 'Cannot Access Package Manager. Is System running?' Also the mount -o rw,remount.....command doesn't work either as it says Permission Denied. All of this would be easy to accomplish if only it ADB allowed me to write onto the /system file.
EDIT**: The biggest issue I'm faced with is the permission settings that prevent my from editing anything. You cannot simply change it from RO to RW because apparently the ADB is not rooted. And I also can't root it because problems exist when accessing either Package Manager or Activity Manager. What I need is a way to access the /system files without a root (non-rooted). Either that or enable fastboot because I cannot access that either. On a reply on the second page is the resulting lines when changing bootmodes on the KFU.
Don't know how to fix your problem, but just wondering, did you just completely replace the kindle fire build.prop with the HTC glacier? Because you can't do that, it will, as you have learned, mess up your device.. Your supposed to edit the build.prop and just change a few things. Next time read up on the subject before deciding to mod the device you use everyday...
the cable you'r talking about is a "factory cable" it forces the kf to fastboot mode - it don't restore any settings !
you need fastboot mode to install fff (firefirefire - custom bootloader) and twrp (recovery)
do you allready have installed fff & twrp (or cwm) ?
if you have twrp installed and booted into then you have adb command available and can copy back the original build.prop
Did you remember to restore the read/write permissions to build.prop? It should be set to 644.
As already stated, your not supposed to replace the whole file, build.prop tells android which device you have, so now Android thought and configured itself to different hardware config. which is not available to it. Adb seems like the only option.
I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.
gococogo321 said:
I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.
Click to expand...
Click to collapse
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
You dont have access to recovery? Either TWRP or CWM?
daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.
gococogo321 said:
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.
Click to expand...
Click to collapse
Did you use the 'adb remount' command? Sometimes, when attempting to push a file to the system, I get the 'read-only file system' and I have to issue adb reboot followed by adb remount and then push the file again. It seems after a time the mount system as read write automatically goes back to read-only.
Sent from my ADR6400L using xda premium
Have you got TWRP or ClockworkMod?
Because you could flash a new rom then.
abd - root mode
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.
sum1nil said:
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.
Click to expand...
Click to collapse
Thanks but I have actually been running it from Administrator from the very beginning. I've used Kindle Fire Utility KFU and it says that ADB Server is Online and my Bootmode is 4000 but it says ADB root: No. And whenever I choose any bootmode whether it be Normal, Fastboot, or Recovery, it always shows this:
***********************************************
* Activating Normal (4000) *
***********************************************
Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC!
1393 KB/s (1164225 bytes in 0.816s)
Error: Could not access the Package Manager. Is the system running?
Activating BurritoRoot...
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system
running?
Elevating the Shell...
* daemon not running. starting it now *
* daemon started successfully *
/data/local/tmp/BurritoRoot3.bin: permission denied
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
<idme> Invalid permission
reboot: Operation not permitted
Same goes for the Temp Burrito Root and installing FFF and TWRP. It always shows something about cannot access Package manager. I have no clue what the Package Manager even does but apparently I cannot find a solution to that.
I think you need to get a factory programming cable like we talked about on gtalk. I'm confident that will fix this.
Sent from my DROIDX using Tapatalk
I used android commander for windows, mounted system in TWRP and used android commander to copy a new working build.prop to the right place.
With a cable from my htc desire.
would make a little test:
issue "adb shell"
if you get a error message your up to a factory cable because the system shell is messed up and you have no possibility to get to fastboot mode to install fff & twrp
if you get a $ or # prompt you can resume and try "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" to mount system in read/write mode
daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
hey, I've tried to remount my rooted galaxy y, fall in for same problem.but there show this message; "remount failed: Operation not permitted"
my device's usb debugging mode was off in last entire.
what I have to do now?
how did u edit build.prop in the first place if u don't have root and this might help
http://yaseminavcular.blogspot.com/2012/01/how-to-get-bricked-kindle-fire-back-to.html?m=1
Sent from my R800i using Tapatalk
FULL Disk ENCRYPTION + ROOT Easy steps >>> HOW TO root & encrypt entire device
How to encrypt your rooted device. I wrote these instructions based on my Note 4 (T-Mobile branded N910T3 ) BUT they will work for ANY device!
THE SHORT OF IT:
YOU SIMPLY NEED TO ECRYPT YOUR DEVICE FIRST PRIOR TO ROOTING. YOU CAN ROOT IT AFTER IT IS ENCRYPTED, NOT BEFORE.
tested on Android 4, 5, & 6.
Once you root or install various roms you lose the ability to encrypt your device. This issue manifests itself in the form of either hanging, rebooting, or the animation just sitting there but not actually doing anything when you try to use the full disk encryption feature built into all modern versions of android. Below are the steps on how to get this native encryption feature working while still maintaining your root & favorite rom.
Credit goes to chatty kathy, i mean bruzzy who graciously and verbosely provided instructions on how to encrypt my rooted 12.2" Samsung Galaxy Note Pro (AT&T branded SM-P907A) here: http://forum.xda-developers.com/showthread.php?t=2791587
McFood on androidforums.com also reiterated much of the same here: http://androidforums.com/threads/how-to-encrypt-a-rooted-device.866968/
As usual: Use this guide at your own risk!
Quick Overview:
Unroot if rooted. Encrypt. Reroot. The only thing special is that you have to manually kick start SuperSU when rooting after the encryption is in affect. See steps 12 & 13.
INSTRUCTIONS:
-------------------
0. Make a backup to your external SD card of your entire system FIRST such as a nandroid backup via a custom recovery (Philz Touch, TWRP, etc). I even do modem, etc. just in case you ever need.
1. Ensure your device is not rooted and also not encrypted (if already rooted, skip to step 3; if already encrypted, decrypt or do a factory-reset - don't try CF-Auto-Root on an encrypted device, it'll soft-brick)
2. Root the device (I used this sticky: http://forum.xda-developers.com/not...y-steps-n910t3-dofc-dog1-how-to-root-t3177225 )
3. Temporarily un-root the device (when using SuperSU: go to Settings and remove the tick at the option "Activate Superuser")
4. Reboot
5. Activate the device encryption (the battery must be at least at 80% and the device must be plugged in the wall charger)
6. The device will restart after a short period of time and start the encryption (this will take some time, but you should see a progress bar indicating how far it is)
7. After the encryption is finished the device will reboot and ask for the password, just log in
8. If not yet done, flash a custom recovery where you have console access or can use ADB as root (I used TWRP)
9. Boot into recovery. (POWER + VOLUME UP + HOME button together at the same time)
10. Mount /system (it's not mounted automatically, at least not in the version I used - TWRP 2.7.1.0).
11. Open a console or ADB shell to run the basic linux commands in red in the next two steps on the phone ((In TWRP it is under Advanced & then Terminal Command and start the console in any directory, it doesn't matter, i would choose the root directory / ))
11-continued: Laymans terms: go to Advanced in TWRP and then Terminal Command. Just press select to start shell in the root directory "/ ".
once you are at the prompt you simply type in the commands in red in steps 12 & 13.
12. Copy the su binary (if you use SuperSU you run this command: cp /system/xbin/daemonsu /system/xbin/su )
13. Execute the installation (if you use SuperSU run this command: /system/xbin/su --install )
14. Reboot
15. Send the NSA a message and tell them to lick your balls. Oh wait nevermind they have a backdoor in AES... FTP = Fukt The Police :cyclops:
OP space
The real trick here is disabling (step 3) and then manually re-enabling (steps 12 and 13) root which you manually re-enable after the encryption is complete. The order is key. You cannot encrypt the device while rooted.
go to Advanced in TWRP and then Terminal Command. Just press select to start shell in the root directory "/ ".
once you are at the prompt you simply type in those commands:
cp /system/xbin/daemonsu /system/xbin/su
::THEN PRESS ENTER TO EXECUTE THE COPY COMMAND::
Then type:
/system/xbin/su --install
:RESS ENTER TO EXECUTE THE su COMMAND running the installation.::
Now reboot and you are done!
If you don't have TWRP installed there are other options to be able to run the command. Most custom recoveries either allow you to bring up a console window like that or they allow you to run commands on your device through your PC using ADB, either way it will work, you are just copying files with the first command and executing one of them to install on the second.
? on steps 12 + 13
"12. Copy the su binary (if you use SuperSU you run this command: cp /system/xbin/daemonsu /system/xbin/su )
13. Execute the installation (if you use SuperSU run this command: /system/xbin/su --install )"
Where in TWRP do I do this?
Also, do I need to be in the rom I am choosing as my daily driver when i start this process? What do i do if I change roms?
?
Bueller?
V3racious said:
6. The device will restart after a short period of time and start the encryption (this will take some time, but you should see a progress bar indicating how far it is)
Click to expand...
Click to collapse
This part never happens for me, it just gets stuck on the boot animation. I've disabled superuser. What else can I do? This is really frustrating.
livejamie said:
This part never happens for me, it just gets stuck on the boot animation. I've disabled superuser. What else can I do? This is really frustrating.
Click to expand...
Click to collapse
Exactly. I tried this before and got the same results.
jrkart99 said:
Exactly. I tried this before and got the same results.
Click to expand...
Click to collapse
I just gave up on root for now.
Breakdown of steps 12 & 13
jrkart99 said:
"12. Copy the su binary (if you use SuperSU you run this command: cp /system/xbin/daemonsu /system/xbin/su )
13. Execute the installation (if you use SuperSU run this command: /system/xbin/su --install )"
Where in TWRP do I do this?
Also, do I need to be in the rom I am choosing as my daily driver when i start this process? What do i do if I change roms?
Click to expand...
Click to collapse
For steps 12 and 13 you go to Advanced in TWRP and then Terminal Command. Just press select to start shell in the root directory "/ ".
once you are at the prompt you simply type in those commands:
cp /system/xbin/daemonsu /system/xbin/su
::THEN PRESS ENTER TO EXECUTE THE COPY COMMAND::
Then type:
/system/xbin/su --install
:RESS ENTER TO EXECUTE THE su COMMAND running the installation.::
Now reboot and you are done!
If you don't have TWRP installed there are other options to be able to run the command. Most custom recoveries either allow you to bring up a console window like that or they allow you to run commands on your device through your PC using ADB, either way it will work, you are just copying files with the first command and executing one of them to install on the second.
To answer your other question: YES you need to choose your ROM first, otherwise you have to do this all over again. Install your ROM first, root it next if your rom doesn't come pre-rooted, manually disable root, and lastly encrypt the device.
livejamie said:
This part never happens for me, it just gets stuck on the boot animation. I've disabled superuser. What else can I do? This is really frustrating.
Click to expand...
Click to collapse
Can you verify that you have in fact disabled root first? You cannot encrypt a rooted device. Also what is the model number of your device? What version of Android are you using?
Try this method after SuperSU is installed.
http://forum.xda-developers.com/showthread.php?p=56037508
Good luck
Sent from my Nexus 7 using Tapatalk
Hello,
I have sprint note 4.. I have installed HybridX Android 5.1.1 on it.. which have root and everything ready.
I go to system apps, from there disable SuperSu and then reboot in safe mode and start encryption.. These are the steps I read on another page..
However, my phone gets stuck on the sprint spark yellow screen as soon as I say ok to encrypt.. it will restart and gets stuck on there.
I have tried without restarting in safe mode.. but the same result.
What can I do to encrypt my Sprint Note 4.
Thanks
Hello,
I am on Galaxy Note 3 with N7 Darklord ROM and both methods don't work.
Root is disabled, but when I run encryption, the phone restarts in 2-3 minutes
and nothing is encrypted
Please advise how to encrypt the device! Thanks!
5.0.1 Should be fine to root + encrypt
Hi all,
Just to confirm that the only version I managed to root and encrypt is 5.0.1.
I have a Note 4 910F and this worked;
- Flash stock via odin
- Root (chainfire via odin)
- Install Busybox
- Install Terminal Emulator, then run su -> pkill -KILL daemonsu (same as other instructions on this forum)
- Encrypt the phone
Again, this only worked on 5.0.1 (N910FXXU1BOC5_N910FBTU1BOB2_N910FXXU1BOC4_HOME.tar)
All other versions got stuck on encryption screen.
In short, all you have to do is ENCRYPT the device FIRST then ROOT it AFTERWARDS. It will not work once the device is rooted. I have not had a chance to try unrooting through SuperSU or disabling the daemonsu through a terminal emulator as mentioned so I am not sure if this works but it definitely works if you encrypt PRIOR to rooting. I can confirm it works on Marshmallow as I just did so on a Note 4.
Now has anyone had any luck making backup images of their encrypted devices? If so what custom recovery software and version are you running on your device?
Everyone please share your modified stock kernel for your Z5 series models with specifics here ...........
- Model
- ROOT working
- TWRP
- SuperSU
- Busybox
and so on....
As there is way to much ambiguous information out there right now for perfectly rooting the nougat on Z5 series and even one can achieve root with DRM fix there seems to be no R/W permission on SYSTEM partition !!!!
So please the people here who have successfully achieve ROOT with W/R SYSTEM, SU , DRM and other capabilities and are happy with them , please do upload your kernels here mentioning proper model and other things mentioned above.
Its for general good
try using this
https://forum.xda-developers.com/xperia-z5/general/ub-drm-fix-dm-verity-off-root-t3539999
I successfuly rooted my phone and have /system R/W permission, just make sure to flash SR5 SuperSu 2.78. PM me with results.
L33Tgod said:
try using this
https://forum.xda-developers.com/xperia-z5/general/ub-drm-fix-dm-verity-off-root-t3539999
I successfuly rooted my phone and have /system R/W permission, just make sure to flash SR5 SuperSu 2.78. PM me with results.
Click to expand...
Click to collapse
I did try that.
And all the other methods currently available to this point.
Created / patched several kernels and the best I could achieve is a fully rooted kernel with DRM and SU.
The only problem is when I delete some thing inside the system folder, it comes back after 1 sec like nothing ever happened to it in the first place.
Searched for the issue a bit more , find 2 possible cures and tried them too but no luck---- so I am now asking people to upload their kernel here so that I can find out which is which and so on............
I'm on the Au firmware on E6653. Used rootkernel and answered yes to all questions except for Su and xposed. Then I installed phh's superuser from recovery and the app from the play store. Everything is working fine.
I shared weeks ago..
download terminal on google play
open terminal
write "su" command and give root permission
then you will see "#"
after that, write this command:
Code:
echo 0 > /sys/kernel/security/sony_ric/enable
then you write this command:
Code:
mount -o rw,remount /system
if you see "#" again, it worked
but if you see "mount: Operation not permitted" it has not, sorry
@sceryavuz
My Phone
6653, flashed 32.3.A.0.372 AU, TWRP 3.0.2 and AndroPlusKernel v41. Root Checked.
Cannot get access to system obviously because of sony_ric....
ive tried following your steps on terminal but each time i try the code line " echo 0 > /sys/kernel/security/sony_ric/enable" it keeps saying cannot find that...
on terminal i typed :
SU Command ( which shows E6653:/data/data/com.termux/files/home #)
then i tried typing
echo 0 > /sys/kernel/security/sony_ric/enable (which shows sush: Echo: not found)
what am i doing wrong?
Gezzaman8 said:
@sceryavuz
My Phone
6653, flashed 32.3.A.0.372 AU, TWRP 3.0.2 and AndroPlusKernel v41. Root Checked.
Cannot get access to system obviously because of sony_ric....
ive tried following your steps on terminal but each time i try the code line " echo 0 > /sys/kernel/security/sony_ric/enable" it keeps saying cannot find that...
on terminal i typed :
SU Command ( which shows E6653:/data/data/com.termux/files/home #)
then i tried typing
echo 0 > /sys/kernel/security/sony_ric/enable (which shows sush: Echo: not found)
what am i doing wrong?
Click to expand...
Click to collapse
If you use AndroPlusKernel kernel, then you are not in stock.
Check a root browser "/sys/kernel/security/sony_ric/" folder is exist or not?