Database Develop

One click root after update: "We have root, but couldn't push busybox. Not sure why!"

One click root after update: "We have root, but couldn't push busybox. Not sure why!"
I just updated .890 which seemed to go fine with no errors (unfroze all bloat, but did not unroot), but I lost root, as expected.. but when I use Pete's one-click root tool (latest version), it gets to step 3 and gives me the error about not being able to push busybox...!? It says I "have root", but none of my apps recognize it.. I've pulled the battery, rebooted and retried like 10 times... still can't get it to re-root. I've made sure Debugging and Unknown Sources is enabled and tried in Charge Mode and Mass Storage mode... Am I going to have to stock flash this thing and re-update & re-root?
I THINK I have some type of root.. maybe... because Root Explorer will let me mount the System directory as R/W and I can TRY to manipulate files, but if I delete something (like su), it appears to delete successfully, but the file comes back if I refresh the directory.. but I also noticed when I go into the System directory, Root Explorer claims I only have 1MB of free space out of 318.00MB... how did that happen? If I try to run Superuser.apk, it force closes on me.
Any help or ideas are greatly appreciated...

there's an app on the android market that will push busybox if you have root. I'd look into that
edit: have you attempted to run the one-click root again? and if that doesn't work you can try to use the adb method if you're comfortable with it. And make sure that all of your drivers and everything are up-to-date

I have done battery pulls and like a dozen+ re-tries at the 1-click root, always get the same error.. I have been into the ADB shell to try and figure this out and I see the ADB Shell starts out by giving me a # prompt... that means writable/root, right? Any instructions on what I have to do from there?
I will look into that push busybox app, thanks.

http://wiki.rootzwiki.com/index.php/Motorola_Droid_3
This is where all the info about the adb and one-click stuff. The tough part about the adb method is manually pushing su to the (i think) system/xbin folder. Then i just used the app on the marketplace to push busybox. But there's a download link for both of those on the website

Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...

Kraxis said:
Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...
Click to expand...
Click to collapse
After temp ADB root, steps 18 and beyond should do it. You may want to check /system/bin and /system/xbin to remove the old su binaries before pushing the new one. Some folks have one in each location for some reason. Put it in xbin, but if it doesn't work, /system/bin will. Superuser wouldn't recognize xbin for me so I moved it to /system/bin and i'm good since.
Anyone have a thought on the xbin not always working? I think this is the 3rd topic i've seen with this issue, not including myself.
Sent from my DROID3 using XDA App

OK, I got root back! I used steps 18+ for "ADB Method" (after using Pete's temp ADB root) and essentially replaced SU and Superuser.apk, CHMOD'd it rebooted and I had root! Thanks guys!!

Droid 4 Utility for Windows/Mac/Linux

Hey all! This is the new home of the Droid 4 Utility (NOW WITH SAFESTRAP THANKS TO HASHCODE) for Windows/Mac/Linux!
There are (still) no fastboot files as of writing this (2/28/2012) so use Safestrap at your own risk
Once they come out I will be making a full version that includes fastboot restore. For now, the utility is only a few MB compared to a GB+.
From this point forward I will be taking charge of updating the Droid 4 Utility for Windows/Mac/Linux
This way mattlgroff has a little less work on his hands and can focus more on IMPORTANT things like bootloaders, ICS, etc...
MAC/LINUX: Be sure to read the instructions below (or README file) if you are not familiar with using terminal as root or executing bash scripts!
-Changes
~~as of 2/18/ 11:30PM PST
Fixed bug where Superuser.apk was pushed to /data instead of /system/app/
Fixed unroot script to properly remove Superuser.apk
~~as of 2/19 4:30 PM PST
Fixed chmod in root method from 4775 to 6775
~~as of 2/28 6:15PM PST
Added Safestrap recovery!!
~~as of 3/2
fixed script to chmod +x ./files -R so that you can actually run the files on mac and linux (that would be important huh?)
DOWNLOADS
WINDOWS
Size: 7.75 MB
MD5: f82bf8d8a085ff95b696712b8caa0f1b
Link: http://tinyw.in/KKB8
MAC
Size: 7.19 MB
MD5: dc8468d051d59963914a0b8a054b83b8
Link: http://tinyw.in/vx2A
LINUX
Size: 7.26 MB
MD5: 0c082efbff48e614b9d8ebffc7eca3eb
Link: http://tinyw.in/tpt0
Here's how:
Windows:
Simply Unzip the files, and run Droid4Windows.bat as administrator (right click>run as administrator)
Mac/Linux:
Simply extract the zip then
Code:
su
Then enter the root password NOTE: This is not YOUR password, this is the ROOT password. If you dont know it, you can always use
Code:
sudo passwd
to reset the root password
Next run:
Code:
cd /the path to where you extracted the files/
for example, heres what I have to type:
Code:
cd /home/skylar/Desktop/Droid4UtilityLinux/
next run the appropriate bash script:
Code:
bash Droid4linux
OR
Code:
bash Droid4mac
I'm sorry to say I don't actually own a Droid 4, so I'm doing this blind. Please report any problems or bugs you have.
Have fun and I hope you enjoy! [/SIZE]
CLICK HERE TO DONATE
SCREENSHOTS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CLICK HERE TO DONATE

I can not get this to unroot.
---------------------------------------------------------------
Easy rooting toolkit (v1.0)
UNROOTING SCRIPT
created by DooMLoRD
based heavily on FlashTool scripts (by Bin4ry and Androxyde)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
Note: This removes superuser from both possible locations
So seeing one error of now finding Superuser is NORMAL!
---------------------------------------------------------------
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
The system cannot find the path specified.
--- TESTING FOR SU PERMISSIONS
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- cleaning
The system cannot find the path specified.
--- pushing busybox
The system cannot find the path specified.
--- correcting permissions
The system cannot find the path specified.
--- remounting /system
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- pushing unroot script
The system cannot find the path specified.
--- correcting permissions
The system cannot find the path specified.
--- executing unroot
MAKE SURE THAT THE SCREEN IS UNLOCKED
and if you get Superuser prompts ACCEPT/ALLOW THEM
ELSE THIS WILL NOT WORK
The system cannot find the path specified.
--- cleaning
The system cannot find the path specified.
--- rebooting
The system cannot find the path specified.
ALL DONE
Press any key to continue . . .
The system cannot find the path specified.
Please make a selection or hit ENTER to return:
Click to expand...
Click to collapse

prodigyweb said:
I can not get this to unroot.
Click to expand...
Click to collapse
Sounds like you aren't running this inside the folder that also contains the /files/ folder. If you have it by itself of course the path's won't find it...because you moved it or you aren't "cd" into the directory of the utility.

appears after a phone/computer reboot and canceling the ADB process in my tasks it now is rebooting the phone and working. Thanks!

prodigyweb said:
My setup is: http://i.imgur.com/Surbz.png
should it be within the adb package from android itself?
Click to expand...
Click to collapse
Is your USB Debugging Mode enabled and "Unknown Sources" in your application settings?

Hm, I turned on USB Debugging in the settings, but it's not starting up when I plug in a USB cable, and adb can't find the device. ???

highlandsun said:
Hm, I turned on USB Debugging in the settings, but it's not starting up when I plug in a USB cable, and adb can't find the device. ???
Click to expand...
Click to collapse
While your phone is plugged in, see what drivers are in device manager and remove them. Then restart your phone while its still connected through USB. See if that reinstalls all the necessary drivers and try again.

reigndropz said:
While your phone is plugged in, see what drivers are in device manager and remove them. Then restart your phone while its still connected through USB. See if that reinstalls all the necessary drivers and try again.
Click to expand...
Click to collapse
This is Linux, so no device manager. I think I needed to add the Motorola vendorID to my udev rules first, I got it working eventually. Rooted, great. Now to go and fix the character maps so I can fully use Connectbot.

highlandsun said:
This is Linux, so no device manager. I think I needed to add the Motorola vendorID to my udev rules first, I got it working eventually. Rooted, great. Now to go and fix the character maps so I can fully use Connectbot.
Click to expand...
Click to collapse
Ah ok.....how are you with deodexing? I have been trying to deodex the SystemUI but I am not having any success. I add the jars but it keeps going and going and doesnt seem to end. Soon as I get the SystemUI deodexed, I'll throw a battery percent icon here....

reigndropz said:
Ah ok.....how are you with deodexing? I have been trying to deodex the SystemUI but I am not having any success. I add the jars but it keeps going and going and doesnt seem to end. Soon as I get the SystemUI deodexed, I'll throw a battery percent icon here....
Click to expand...
Click to collapse
Hm, haven't done anything with theming tweaks. Dunno, sorry.
You need adb to be enabled at boot time, so you can adb logcat during the startup and see what failed.
By the way, the Linux archive is not immediately usable, you need to chmod +x everything under the files/ subdirectory to make them executable first.

highlandsun said:
Hm, haven't done anything with theming tweaks. Dunno, sorry.
You need adb to be enabled at boot time, so you can adb logcat during the startup and see what failed.
By the way, the Linux archive is not immediately usable, you need to chmod +x everything under the files/ subdirectory to make them executable first.
Click to expand...
Click to collapse
Hey thanks for pointing that out! I didnt notice because they were already executable on my computer. I added
Code:
chmod +x ./files -R
to the script on startup so no one should have to manually do it anymore, sorry about that

prodigyweb said:
I can not get this to unroot.
Click to expand...
Click to collapse
Make sure you have done all of the steps below
Prework
1. Plug in phone to computer.
2. Turn on USB Debugging. Menu -> Settings -> Application -> Development -> USB Debugging
3. Confirm latest Moto driver is installed. Go to Device Manager on Windows while the D4 is plugged into it and confirm you see ADB Interface listed with Mot Composite ADB Interface listed in the group. If you see that, skip #4 & #5. There are other ways to go about this, but this is the simplest and surefire way to confirm the driver is there and compatible.
4. Go get Moto driver and install it: USB and PC Charging Drivers - Motorola Mobility, Inc. USA It is an exe file that must be run and your computer has to restart when completed.
5. Go back into your Device Manager after reboot with the phone plugged in and confirm ADB Interface is there and no error exists.
Done.

I can't get this to root, it appeared to have rooted once since Superuser was installed but TBU said not root access. Now I get message " error more than one device and emulator" when I try to root again or unroot. any idea?

contemplating getting this through a client, any word on fastboot and unlocked updates?
or is the droid 4 destined to be like all other moto phones and lack a soul...
I really wanted the Photon, but dev on it was strangled to death!

Hammerfest said:
contemplating getting this through a client, any word on fastboot and unlocked updates?
or is the droid 4 destined to be like all other moto phones and lack a soul...
I really wanted the Photon, but dev on it was strangled to death!
Click to expand...
Click to collapse
The phone itself is great. Good build quality, fantastic keyboard, fast, etc. I have not heard any news on fastboot files yet. I assume it's just a matter of time but who really knows for sure. Unlock updates? As in unlock the bootloader? I don't ever expect to see that happen, personally.
Despite that, development seems to be coming along nicely with very usable AOSP CM9, AOKP, and Gummy ROMs. The relative ease with which Razr ROMs can be ported to the D4 (due to almost identical internal components) should help on that front as well as Razr development is seems very strong.

Does this Utility still work after the latest update?
I had previously rooted via this utility and had frozen a bit of bloatware w/ TB. I have since unfrozen the bloatware and unrooted. As soon as the install message pops up again I plan to run the update, but was wondering if I will be able to re-root the same way once I do that.

mancowmilitia said:
Does this Utility still work after the latest update?
I had previously rooted via this utility and had frozen a bit of bloatware w/ TB. I have since unfrozen the bloatware and unrooted. As soon as the install message pops up again I plan to run the update, but was wondering if I will be able to re-root the same way once I do that.
Click to expand...
Click to collapse
I've heard people having mixed results trying to re-root using the utility. Some seem to have no problem but others said they had to run the exploit directly. Not sure why.
I just used the Voodoo OTA Root Keeper app to hide root while the update was being applied and then restored root.

kwyrt said:
I've heard people having mixed results trying to re-root using the utility. Some seem to have no problem but others said they had to run the exploit directly. Not sure why.
I just used the Voodoo OTA Root Keeper app to hide root while the update was being applied and then restored root.
Click to expand...
Click to collapse
I installed the upgrade with no issues. I was able to re-root without complication as well. The only message I received was that the Superuser.apk installation "failed" because it was already there. Others have noted that unrooting doesn't delete the file. But, its presence did not stop my upgrade.
This time I installed Voodoo and will go that route for the next OTA.

Is there a mirror link for the Windows Utility? The download keeps timing out on me.

heres a link for an older copy
http://goo.im/apps/mattlgroff/Droid4Utility0.3.zip

[ROOT][10-29-13]How to Manually Root the Nvidia Shield

Introduction
The following procedure will walk you through the step-by-step process for gaining root access on the Nvidia Shield.
Note: You must have an unlocked bootloader before you can proceed with this tutorial!
A tutorial on how to unlock your Shield's bootloader can be found here.
This tutorial also assumes how have the correct ADB and Fastboot drivers installed for your device, for a tutorial on how to install the ADB and Fastboot drivers for the Shield please look here.
Due to the nature of modifying devices system files the standard XDA disclaimer applies: I take no responsibility for bricked devices due to the following rooting procedure, no warranty express or implied is given, I will not be held responsible if you mess up your device by following this procedure!
Procedure
Before you begin please make sure to read and re-read the whole procedure, making sure you understand the directions.
1. Download the "Superuser-su.zip" file and the "roth-insecure-boot-63.img" file that are attached to this post. After you have downloaded the files, extract the contents of the "Superuser-su.zip" file which contains Superuser.apk and the su binary, and move them to your ADB and Fastboot folder on your computer. Also transfer the "roth-insecure-boot-63.img" to your computer's ADB and Fastboot folder.
MD5 Checksum for "roth-insecure-boot-63.img": F8BA5C48D0323D99E2A748C77BF647F6
2. Connect your Shield to your computer using your USB cable. For maximum reliability please connect the USB cable to a USB 2.0 port directly connected to the motherboard as USB ports on the front of a case panel or USB 3.0 ports can sometimes be unreliable.
3. Now that your Shield is connected to your computer make sure that "USB debugging" is enabled under the Developer Options section in the system settings menu (If the Developer Options section is hidden, go to the About Phone/About Tablet section of the system settings and then tap on the item that lists the Build number 7 times or until it says "You are now a developer" and the Developer Options section becomes visible in the system settings).
4. Open a command prompt window (cmd) in your ADB and Fastboot folder on your computer and issue the following commands (If you are new to using ADB and Fastboot I would recommend checking out this excellent guide to get you up and running):
Code:
adb reboot bootloader
Now that you are in fastboot mode let's make sure that the computer see's our device:
Code:
fastboot devices
If the computer see's our device then we can proceed, if it doesn't see your device make sure you are in fastboot mode and have the correct ADB and Fastboot drivers installed for the Shield.
Now we will be booting an insecure boot.img (ro.secure = 0) to our device to allow us to gain root acess:
Code:
fastboot boot roth-insecure-boot-63.img
After the insecure boot.img finishes flashing the device will automatically boot up using the insecure boot.img.
5.First we need to mount the /system partition as read/write so we can modify it:
Code:
adb shell
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
exit
6. Now we need to run the following commands to push the Superuser.apk and su binary to there correct positions and set the proper file permissions:
Code:
adb push su /system/xbin
adb push Superuser.apk /system/app
adb shell
chmod 6755 /system/xbin/su
chmod 644 /system/app/Superuser.apk
mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
sync
reboot
7. After the device reboots and power on into the Android Operating System you should see Koush's Superuser app in your app-drawer and you should be rooted. If you would like to verify root access you can download and run Root Checker Basic from the Play Store here. Enjoy!
Credits: Koush for his open source Superuser.apk and the su binary (https://github.com/koush/Superuser)
If users would like me to create a 1-click root process of this please let me know and I will do so .
If you are stuck with the rooting procedures I would recommend checking out this great video tutorial by wwjoshdew.

Alternatively the following works in almost one click (one fast boot, actually): https://github.com/linux-shield/shield-root

Gnurou said:
Alternatively the following works in almost one click (one fast boot, actually): https://github.com/linux-shield/shield-root
Click to expand...
Click to collapse
It's just whole unlocking thing and giving up your devices warranty. NVIIDA being able to decline your RMA if your fan goes out and the unit overheats. Or if the scree dies (for example). I'll do it, just gotta grow a pair first.

wwjoshdew said:
It's just whole unlocking thing and giving up your devices warranty. NVIIDA being able to decline your RMA if your fan goes out and the unit overheats. Or if the scree dies (for example). I'll do it, just gotta grow a pair first.
Click to expand...
Click to collapse
I did my RMA and nvidia sent me a new 1. So you should get your new shield b4 you send it back if you happen to root it and the screen dies.

This is a pretty complicated way of rooting. All I did was unlock the bootloader, flashed Clockworkmod Recovery, and then flashed the SuperSu zip with that. Rooted! As easy as a Nexus.

dark42 said:
This is a pretty complicated way of rooting. All I did was unlock the bootloader, flashed Clockworkmod Recovery, and then flashed the SuperSu zip with that. Rooted! As easy as a Nexus.
Click to expand...
Click to collapse
I hear yeah, this procedure is meant for those that really want to understand how the basic rooting process works and who want to gain experience manually performing these types of procedures .
Sent from my SCH-I535 using xda premium

shimp208 said:
I hear yeah, this procedure is meant for those that really want to understand how the basic rooting process works and who want to gain experience manually performing these types of procedures .
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
This method is actually nearly the same. It's a bootable self-contained image (like recovery is) that mounts the correct partitions, installs the necessary bits, and is done.

I haven't done this yet ... but could you also provide instructions on how to revert? I ask this as it would be nice to know that there is a back-out plan.
Kris

i00 said:
I haven't done this yet ... but could you also provide instructions on how to revert? I ask this as it would be nice to know that there is a back-out plan.
Kris
Click to expand...
Click to collapse
To unroot your Shield since you are only temporarily booting an insecure boot image rather then flashing it, if you run the following commands in either ADB shell or terminal emulator will unroot your device:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
# rm -f /system/app/Superuser.apk
# rm -f /system/xbin/su
# mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Then after you have entered those commands reboot your device and you'll be unrooted.

shimp208 said:
To unroot your Shield since you are only temporarily booting an insecure boot image rather then flashing it, if you run the following commands in either ADB shell or terminal emulator will unroot your device:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
# rm -f /system/app/Superuser.apk
# rm -f /system/xbin/su
# mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Then after you have entered those commands reboot your device and you'll be unrooted.
Click to expand...
Click to collapse
OK ... well lets say after rooting we install an app that uses root access to stuff up your device ... how do you restore the original image?
Kris

i00 said:
OK ... well lets say after rooting we install an app that uses root access to stuff up your device ... how do you restore the original image?
Kris
Click to expand...
Click to collapse
The original factory restore image that you can be flashed to your shield to return it to stock can be downloaded from here, along with the factory image extraction instructions (Under the open source resources section), as well as the factory image flashing instructions.

Does anyone if the root stop you from updating the device like GS4?

Simply rooting does not. I was rooted and updated. You lose root but can just reroot it like the first time. I am not sure if you have a custom recovery installed though. I haven't used one on the shield.

I am using the window 8 and I can't get the command prompt to work either directly open or open it as administrator to type the command. Any idea what I am doing wrong?
Shimp208. Can you create a video on how to unlock and root the shield?
Sent from my SHIELD using Tapatalk 2

wrc1010 said:
I am using the window 8 and I can't get the command prompt to work either directly open or open it as administrator to type the command. Any idea what I am doing wrong?
Shimp208. Can you create a video on how to unlock and root the shield?
Sent from my SHIELD using Tapatalk 2
Click to expand...
Click to collapse
When you mean you can't get the command prompt to directly open what do you mean by that? Does command prompt not open or run at all when you open it? Do you have ADB and Fastboot installed and the files listed for this procedure in your ADB and Fastboot directory? The Shield I rooted was my friends and he's on vacation right now so I unfortunately can't make a video right now , but I'll still be happy to try and help you through the procedure.

Finally success root my shield

oh god
wrc1010 said:
Finally success root my shield
Click to expand...
Click to collapse
I want that feeling soooo bad. The drivers aren't installing on my computer correctly. I can boot my shield via command but when I enter adb devices nothing shows up even though in device manager the device shows up as Nvidia Shield ADB.
Sad times, its tough as its so new everyone is still trying to figure it out and if the drivers don't install first time there aren't any problem solving threads etc

gogul1 said:
I want that feeling soooo bad. The drivers aren't installing on my computer correctly. I can boot my shield via command but when I enter adb devices nothing shows up even though in device manager the device shows up as Nvidia Shield ADB.
Sad times, its tough as its so new everyone is still trying to figure it out and if the drivers don't install first time there aren't any problem solving threads etc
Click to expand...
Click to collapse
What drivers are you trying to install and which version of Windows are you running?

Drivers
shimp208 said:
What drivers are you trying to install and which version of Windows are you running?
Click to expand...
Click to collapse
The ADB drivers and I'm running windows 7 64bit
Been trying to install them all day but I can bootload into shield but it can't pick up devices so can't root it.

gogul1 said:
The ADB drivers and I'm running windows 7 64bit
Been trying to install them all day but I can bootload into shield but it can't pick up devices so can't root it.
Click to expand...
Click to collapse
Did you try and install these drivers? Make sure to uninstall your old driver installation first.

[HOW TO] Debrand boot animations without flashing new ROM

** Requires ROOT+Busybox and either Terminal or a capable File Manager
So you don't feel like flashing a new ROM and losing all your data, but your carrier's boot up and shutdown branding is getting on your nerves? Here is what you do, the basic idea is the same as putting on a new boot animation
I'll assume you're using a Terminal and bootsamsung.qmg for the rest of this, the other files follow the same method
Copy stock boot and shutdown animations onto your SD card, I'll call the path to this location %sd%. A copy of the stock files in the attached archive.
Open terminal and become root
Code:
su
You may need to remount your /system partition as writable, if you're connecting via ADB, adb.exe may crash here - that's fine, just re-connect the USB cable and you shouldn't need to repeat this step again
Code:
mount -o remount,rw [COLOR="RoyalBlue"]/system[/COLOR]
Copy bootsamsung.qmg from %sd% to /system/media/,
Code:
busybox cp -f "[COLOR="RoyalBlue"]%sd%[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]" "[COLOR="RoyalBlue"]/system/media/[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Set the permissions of the file to 644,
Code:
chmod [COLOR="red"]644[/COLOR] "[COLOR="RoyalBlue"]/system/media/[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Get rid of the SD card copy if you don't want it anymore,
Code:
rm -f "[COLOR="RoyalBlue"]%sd%[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Clean up any overriding animations, I had this happen for my shutdown animation where my carrier had a shutdown directory in /system/media/video/ which contained another copy of shutdown.qmg, so check for the existence of these and remove them, e.g.
Code:
if [ -f [COLOR="RoyalBlue"]/system/media/video/[/COLOR][B][COLOR="Purple"]bootsamsung[/COLOR]/[COLOR="Green"]bootsamsung.qmg[/COLOR][/B] ]; then
rm -f [COLOR="RoyalBlue"]/system/media/video/[/COLOR][B][COLOR="Purple"]bootsamsung[/COLOR]/[COLOR="Green"]bootsamsung.qmg[/COLOR][/B]
fi
Reboot and see what happens!
Extra notes: Always keep backups of original files. If you can't get past the boot animation, restore the backups.

paulie-uk said:
** Requires ROOT+Busybox and either Terminal or a capable File Manager
So you don't feel like flashing a new ROM and losing all your data, but your carrier's boot up and shutdown branding is getting on your nerves? Here is what you do, the basic idea is the same as putting on a new boot animation
I'll assume you're using a Terminal and bootsamsung.qmg for the rest of this, the other files follow the same method
Copy stock boot and shutdown animations onto your SD card, I'll call the path to this location %sd%. A copy of the stock files in the attached archive.
Open terminal and become root
Code:
su
You may need to remount your /system partition as writable, if you're connecting via ADB, adb.exe may crash here - that's fine, just re-connect the USB cable and you shouldn't need to repeat this step again
Code:
mount -o remount,rw [COLOR="RoyalBlue"]/system[/COLOR]
Copy bootsamsung.qmg from %sd% to /system/media/,
Code:
busybox cp -f "[COLOR="RoyalBlue"]%sd%[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]" "[COLOR="RoyalBlue"]/system/media/[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Set the permissions of the file to 644,
Code:
chmod [COLOR="red"]644[/COLOR] "[COLOR="RoyalBlue"]/system/media/[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Get rid of the SD card copy if you don't want it anymore,
Code:
rm -f "[COLOR="RoyalBlue"]%sd%[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Clean up any overriding animations, I had this happen for my shutdown animation where my carrier had a shutdown directory in /system/media/video/ which contained another copy of shutdown.qmg, so check for the existence of these and remove them, e.g.
Code:
if [ -f [COLOR="RoyalBlue"]/system/media/video/[/COLOR][B][COLOR="Purple"]bootsamsung[/COLOR]/[COLOR="Green"]bootsamsung.qmg[/COLOR][/B] ]; then
rm -f [COLOR="RoyalBlue"]/system/media/video/[/COLOR][B][COLOR="Purple"]bootsamsung[/COLOR]/[COLOR="Green"]bootsamsung.qmg[/COLOR][/B]
fi
Reboot and see what happens!
Extra notes: Always keep backups of original files. If you can't get past the boot animation, restore the backups.
Click to expand...
Click to collapse
Hello, I'm interested in debranding my verizon s5. I'd love to get rid of the Verizon screen at bootup. I read through your directions and it seems that you are suggesting overwriting the animation with the stock that you provided. All good. It is the use of the terminal that I am completely unfamiliar with. I tried using adb.exe in a command window inside of windows 7 and it didn't even like the first command 'su' My phone is rooted with a custom rom and busybox in developer mode. Could you help me out with what terminal to use and how to connect etc. to enter the commands? I have a decent filemanager installed but It doesn't let me write to system. Thanks for this post.

Eaglebiker said:
Hello, I'm interested in debranding my verizon s5. I'd love to get rid of the Verizon screen at bootup.
Click to expand...
Click to collapse
My first comment must be to say I have a G900F, the international version of the phone and it's using a stock ROM with a few tweaks, e.g. root. A custom ROM will have changed the system partition already so this method shouldn't be applicable there - if it shows a carrier logo on a custom ROM then it's in another partition, not system
Eaglebiker said:
I read through your directions and it seems that you are suggesting overwriting the animation with the stock that you provided. All good. It is the use of the terminal that I am completely unfamiliar with.
Click to expand...
Click to collapse
I gave terminal instructions so people could do it only using their phone but as you've noticed, it's not the only option
Eaglebiker said:
I tried using adb.exe in a command window inside of windows 7 and it didn't even like the first command 'su'
Click to expand...
Click to collapse
If you are using adb, make sure that adb can gain root - the flag should be somewhere in your superuser's settings - then with your USB connected launch adb into shell mode from your computer. This makes adb act as a terminal
Code:
adb shell
If you see a $ then you are not root and will need to gain root, i.e. run su
If you see a # then you are root and don't need to do that
Eaglebiker said:
My phone is rooted with a custom rom and busybox in developer mode.
Click to expand...
Click to collapse
All good things!
Eaglebiker said:
Could you help me out with what terminal to use and how to connect etc. to enter the commands?
Click to expand...
Click to collapse
The terminal I use is can be found here (though I used v1.0.65). Most custom ROMs already include it so you may find it in your apps already. It's all on your phone so you'd type on your phone's keyboard as normal. You shouldn't have to use this if you want to use ADB.
Every time I wrote a %path% you will need to enter the real path for what you have on your device, e.g. %sd% may be /extSdCard/
Eaglebiker said:
I have a decent filemanager installed but It doesn't let me write to system.
Click to expand...
Click to collapse
What doesn't let you do this? If it's "read only" then you may need to remount the /system partition (my step 3). File managers like the one you get with CM do let you do root things but it needs to be in root mode or prompt mode (see it's settings). To find /system in a file manager, the easiest way is to keep going up until you're at /, then you should be able to go down through [/B]/system[/B]
Eaglebiker said:
Thanks for this post.
Click to expand...
Click to collapse
Thank you for letting me give some meaningful answers in post 3!

The Rom I'm using would be better described as a stock lollipop rom for the 900v with a few tweaks.
I now understand that you can have a terminal on the s5. I've installed the terminal and greatly prefer it. Using a terminal on the s5 hadn't even occurred to me and it sounds much easier then hooking to a computer needlessly. Awesome.
I manage to get su access #. in step 2.
in step 3 I type in the mount command and nothing seems to happen. no errors
in step 4 it tells me the folder or file doesn't exist. I'm certain it does. I can see it in my file manager. in the folder /extSdCard/bootsamsung.qmg and the destination folder is /system/media as well. I've tried it with and without quotes and no joy. Any clue what is going on?

Navibar 3 -5 -7 buttons mod - android 5.0 air3g, air 2

Like in description
Navibar 3 -5 -7 buttons mod - android 5.0
air3g, air 2​
If you have my rom Lolipop ( mirek190 ) just plug USB and choose proper option.
On other rom make sure you have root and USB debugging on.
3 buttons navigation bar​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5 buttons navigation bar​
7 buttons navigation bar​
air 3g
https://drive.google.com/open?id=0B8BF9-TGlz-FY2tWZUVZa05FU00
air 2
https://drive.google.com/open?id=0B8BF9-TGlz-FTEhvUTl2clE3Z3M
Ps - NOT RUN IT AS ADMINISTRATOR !

Hi mirek.
Can you add systemui.apk with a clock in its original position with 3 buttons?

Nope - center clock stays in the center like buttons

delete

Great job Mirek!

Hi, can you do this for the Air III? Do you need the stock SystemUI.apk?
EDIT:
I found this post www[dot]tsochen[dot]com/blog/post/15 and nearly the same intructions works for Air III M5C5. But the status_bar_*xml fix as not needed. This is the diff of navigation_bar.xml for 3 buttons
gist[dot]github[dot]com/kazuoteramoto/c0730bb27d0fb8dc6332

The system cannot find the path specified
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?

Wow, thanks, teramoto--this is fantastic! I just modded the SystemUI.apk on my device based on the tsochen link you provided, and your diff. I didn't want the screenshot and volume +/- buttons, but I did want to keep the menu button. So I just modded as indicated, and left the @id/menu entries untouched. The result is a nicely centered, four button variant.
EDIT: Somebody requested that I post my modded SystemUI.apk for a 4-button nav bar for the Air 3/III 32GB (M5C5). At the link below, I have done this, but also included 3- and 5-button versions, as well as the original 7-button SystemUI.apk version from the M5C5 v1.04 stock rom. The various SystemUI.apk files are obviously named by an explicit filename extension as you'll see when you download the archive. Also, let me reiterate--these are specifically for an Air 3/III 32GB (M5C5) tablet. Make sure that file ownership/permission is set correctly on installation else you will run into errors with the UI, and you will have to go in via adb root for manual fixing. Finally, and most importantly, note that credit for this goes to teramoto and the tsochen blog posting he pointed out above, which I just followed to do this, and also to mirek190 for starting this thread, and for helping out so many X98 Air users. Here's the link:
https://mega.nz/#!Hw0jRKBJ!0omuxVQXFHjzdbMV1bg6yvBhtMT570-gBhnkKxw2A4o

irfaan92 said:
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?
Click to expand...
Click to collapse
Facing the same problem...

irfaan92 said:
Hi,
I'm getting the message: "The system cannot find the path specified."
I booted to mirek's rom, plugged the tablet to my laptop and ran the bat file. It was in debugging mode also.
Am I doing it wrong? Any help plz?
Click to expand...
Click to collapse
Have you installed drivers ?

It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work

irfaan92 said:
It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work
Click to expand...
Click to collapse
I did the same as you for whole day....thanks anyway.

irfaan92 said:
It worked actually.... I had been running it as admin when i shouldn't be...
But thanks for the reply mirek... Keep up the good work
Click to expand...
Click to collapse
Thanks for a clue - 1st post updated .

verbage said:
Make sure that file ownership/permission is set correctly on installation else you will run into errors with the UI, and you will have to go in via adb root for manual fixing.
Click to expand...
Click to collapse
Someone asked for some more details about how to "go in via adb root for manual fixing". The question did not provide a lot of details except that the person copied over the file, renamed it, and then the navbar disappeared. So I am assuming that the SystemUI.apk file is correctly named and in the right place on the filesystem, but there is an issue of file ownership/permissions that needs to be fixed manually. If you are in that situation, or the UI is in an endless FC loop because of the same issue, here is what to do.
First, you'll need a working adb (Android Debug Bridge) install. If you don't have one already, the simplest thing to do is to just use the core adb files that mirek190 provides in either one of his ~2MB button mod archives linked at the start of this thread. In particular, I am talking about the "data" directory that has the five exe/dll files. Anyway, extract that, and then open a DOS command window in that directory. To quickly open up a command window, shift-right click on a blank part of the Explorer window, and choose the "Open command window here" option.
Now plug in your tablet, and give the following six commands in the command window you opened:
adb root [this initializes adb in root mode]
adb shell [this spawns an actual adb shell so you'll see the command prompt change]
mount -o rw,remount /system [this makes the /system partition writeable so you can make changes]
cd /system/priv-app/SystemUI [this changes to the right directory to avoid loooonnnngggg command lines]
chown root.root SystemUI.apk && chmod 644 SystemUI.apk [this manually specifies the correct file ownership and permissions]
exit [this gets you back out of the adb shell]
Note again that the above six commands are what is needed if the issue is just one of file ownership and permissions, and the modded SystemUI.apk is already correctly named and in the right spot. It is also the barebones version of a manual fix--before you give any commands, you might want to do some exploration to make sure my assumptions in the previous sentence are correct... For example, if your SystemUI.apk file is incorrectly named, you'll have to fix that first (i.e. "mv INCORRECTLYNAMEDFILE SystemUI.apk"). And before exiting out of the adb shell, you might want to restart the UI on the tablet just to make sure things are working correctly in case you need more triage via adb.
Hope this helps!

verbage said:
Someone asked for some more details about how to "go in via adb root for manual fixing". The question did not provide a lot of details except that the person copied over the file, renamed it, and then the navbar disappeared. So I am assuming that the SystemUI.apk file is correctly named and in the right place on the filesystem, but there is an issue of file ownership/permissions that needs to be fixed manually. If you are in that situation, or the UI is in an endless FC loop because of the same issue, here is what to do.
First, you'll need a working adb (Android Debug Bridge) install. If you don't have one already, the simplest thing to do is to just use the core adb files that mirek190 provides in either one of his ~2MB button mod archives linked at the start of this thread. In particular, I am talking about the "data" directory that has the five exe/dll files. Anyway, extract that, and then open a DOS command window in that directory. To quickly open up a command window, shift-right click on a blank part of the Explorer window, and choose the "Open command window here" option.
Now plug in your tablet, and give the following six commands in the command window you opened:
adb root [this initializes adb in root mode]
adb shell [this spawns an actual adb shell so you'll see the command prompt change]
mount -o rw,remount /system [this makes the /system partition writeable so you can make changes]
cd /system/priv-app/SystemUI [this changes to the right directory to avoid loooonnnngggg command lines]
chown root.root SystemUI.apk && chmod 644 SystemUI.apk [this manually specifies the correct file ownership and permissions]
exit [this gets you back out of the adb shell]
Note again that the above six commands are what is needed if the issue is just one of file ownership and permissions, and the modded SystemUI.apk is already correctly named and in the right spot. It is also the barebones version of a manual fix--before you give any commands, you might want to do some exploration to make sure my assumptions in the previous sentence are correct... For example, if your SystemUI.apk file is incorrectly named, you'll have to fix that first (i.e. "mv INCORRECTLYNAMEDFILE SystemUI.apk"). And before exiting out of the adb shell, you might want to restart the UI on the tablet just to make sure things are working correctly in case you need more triage via adb.
Hope this helps!
Click to expand...
Click to collapse
Hi. first let me thank you for your effort.
I tried your solution but I'm still without the buttons and notification bar.
Code:
D:\@SUPPORT\TECLAST_X98\x98air3g-buttons-mod\data>adb root
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
D:\@SUPPORT\TECLAST_X98\x98air3g-buttons-mod\data>adb shell
[email protected]_m5c5:/ # mount -o rw,remount /system
mount -o rw,remount /system
[email protected]_m5c5:/ # cd /system/priv-app/SystemUI
cd /system/priv-app/SystemUI
[email protected]_m5c5:/system/priv-app/SystemUI # ls
ls
SystemUI.apk
x86
[email protected]_m5c5:/system/priv-app/SystemUI # ls -l SystemUI.apk
ls -l SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-13 01:11 SystemUI.apk
[email protected]_m5c5:/system/priv-app/SystemUI # chown root.root SystemUI.apk && chmod 644 SystemUI.apk
chown root.root SystemUI.apk && chmod 644 SystemUI.apk
<
[email protected]_m5c5:/system/priv-app/SystemUI # ls -l SystemUI.apk
ls -l SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-13 01:11 SystemUI.apk
[email protected]_m5c5:/system/priv-app/SystemUI #
Am I doing something wrong? Any other idea? Or can I put the original file back?
Thanks for any help with this
EDIT: I forgot to mention that I'm using now the sikke1's GoogleNow custom rom. That might be the reason?

wepecko said:
I tried your solution but I'm still without the buttons and notification bar...Am I doing something wrong? Any other idea? Or can I put the original file back?...EDIT: I forgot to mention that I'm using now the sikke1's GoogleNow custom rom. That might be the reason?
Click to expand...
Click to collapse
Hmmm, from your ls -l command, it appears that the file ownership and permission were already set correctly, and so there was no need to give the chown/chmod commands again, but doing so didn't hurt, and only confirmed things.
My M5C5 is also on sikke1's rom--I started with mirek190's v6.1 slim version for the Air 2/II even though I have an Air 3/III, and it worked pretty good except for some hiccups. And so that is why I ended up on sikke1's debloated M5C5 rom, too.
Have you rebooted? You may be nervous to do so, understandably, but adb is enabled by default in the sikke1 rom so even if the graphical UI does not pop up, you can still do manual triage via adb.
---------- Post added at 07:19 PM ---------- Previous post was at 06:53 PM ----------
One thought for the future--if you are going to do this manually, you should stage it appropriately to hopefully avoid issues. For example, copy the original to a backup with the -p option to preserve file properties while still leaving the in-use original completely intact (i.e. "cp -p SystemUI.apk SystemUI.apk.ORIGINAL)". Then copy your modded apk file(s) into the same directory, and make sure file ownership/permissions are set as per above. Then do another cp -p to replace the in-use original with the modded apk.
Here's my listing for the directory to show you what I mean. I have the original apk plus the 3-, 4-, and 5-button modded apks all in the same directory with the correct ownership/permissions set. I can quickly change to any config, for example, the 3-button config, with a single cp -p command, i.e. "cp -p SystemUI.apk.MODDED-3-BUTTON SystemUI.apk". And there is no downtime/hiccup because one file is immediately replaced by the other, and the ownership/permissions are already correctly set.
Code:
[email protected]_m5c5:/system/priv-app/SystemUI # ls -la
ls -la
-rw-r--r-- root root 3572761 2015-12-31 00:54 SystemUI.apk
-rw-r--r-- root root 3572757 2016-01-03 16:43 SystemUI.apk.MODDED-3-BUTTON
-rw-r--r-- root root 3572761 2015-12-31 00:54 SystemUI.apk.MODDED-4-BUTTON
-rw-r--r-- root root 3572764 2016-01-03 16:43 SystemUI.apk.MODDED-5-BUTTON
-rw-r--r-- root root 3604448 2015-12-31 00:21 SystemUI.apk.ORIGINAL
drwxr-xr-x root root 2015-08-26 23:06 x86
[email protected]_m5c5:/system/priv-app/SystemUI #
Again, since you have confirmed everything, I would suggest rebooting if you have not done that. As I said, even if the graphical UI does not come up, you can still get into adb for repairs. At the very worst, you might have to reflash the rom.
I'm not sure why you have had hiccups, but these modded apks are directly from the stock SystemUI.apk of a v1.04 M5C5 rom. I have the modded navigation_bar.xml files, and I can send those or just diffs vs. the original so you can see the few lines that I changed. But you'll see they are just like described by teramoto and the tsochen blog he pointed out.

Thanks verbage. I understand your backup procedure and admit it was a mistake to rewrite the file directly.
However im still trying to find solution to this. I did restart ofcourse, several times, but it didnt help at all. It was late yesterday so i didn't have much time to try different scenarios. Anyway tonight im going to try to update the file with 4 and 5 buttons versions and will see if I'll have any luck.
One more idea: would it be possible that the reason of this not working is that it might be in conflict with xposed apk already installed?
Sent from my XT890 using Tapatalk

wepecko said:
Anyway tonight im going to try to update the file with 4 and 5 buttons versions and will see if I'll have any luck... One more idea: would it be possible that the reason of this not working is that it might be in conflict with xposed apk already installed?Sent from my XT890 using Tapatalk
Click to expand...
Click to collapse
Hmmm, sorry to hear you are still having a problem. The 3-, 4-, and 5-button versions all work perfectly on my Air 3/III using sikke1's debloated M5C5 rom, and since you have the same device, any of the versions should also work for you.
Certainly, the 7-button stock original should work, too, and that is also included in the archive I posted.
Whether there may be a conflict with the xposed framework you have installed, I don't know as I do not have xposed installed on my Air 3/III.
Anyway, good luck with fix, and we'll wait to hear more.

I tried again from the start and everything is working perfect now. Tested succesfully all versions of SystemUI file.
I have no explanation on the troubles during the first try though. I did everything the same way as yesterday.
:victory:

wepecko said:
I tried again from the start and everything is working perfect now. Tested succesfully all versions of SystemUI file.
I have no explanation on the troubles during the first try though. I did everything the same way as yesterday.
:victory:
Click to expand...
Click to collapse
Great, glad to hear you have it working!