DISCLAIMER: This guide works on any phone with Android 11 or newer. Previous versions do not have wireless debugging so this is not possible.
Hey all! In this short guide, I will be showing you how to give any app the permission "WRITE_SECURE_SETTINGS" without needing to connect to a computer.
For this guide, I will be using System UI Tuner by Zachary Wander as my example app.
First, download and install Shizuku. This is a wonderful app that allows system API access directly without needing to root your phone.
Once you've installed Shizuku, follow the steps to start it through the wireless debugging method. You will only need to pair once as long as you don't reinstall the app.
DISCLAIMER: Shizuku will need to be restarted if you restart your phone but it's just a matter of re-enabling wireless debugging and then clicking "Start" in the Shizuku app.
Next, we're going to install Termux by Fredrik Fornwall. Simply open the app once, wait for it to finish installing, then leave the app.
Now, re-enter Shizuku, and click the button that says "Use Shizuku in terminal apps".
{
"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"
}
Then click "Export files".
Afterwards, make a new folder, and call it "Shizuku".
Finally, click "Use this folder".
Almost there!
Head over to Termux, and type:
Code:
pkg install nano
This installs a text editor that we will use to edit our Shizuku config file.
While it's installing, go to Termux's app info, and change the permissions to allow it access to all files. This will allow it to see the folder we made earlier.
Go back to Termux, and after nano is done installing, type the following:
Code:
cd /sdcard/Shizuku
nano shizuku
Once inside the text editor, press the CTRL key on Termux's key bar, and press the "\" key on your keyboard.
Now, type "PKG", press Enter, then in the next field, type "com.termux".
Now, tap "a", tap Ctrl+X, tap "y", and you're done!
Whenever you want to authorize an app with "WRITE_SECURE_SETTINGS" simply open Termux, cd to "/sdcard/Shizuku", and type:
Code:
sh shizuku pm grant <package name here> android.permission.WRITE_SECURE_SETTINGS
You will only have to do this once per app as long as you do not uninstall it.
Have fun!
So this broke my brain just a bit (it's been one of those days) however if I am reading it correctly this will give some apps a pseudo root.
alarmdude9 said:
So this broke my brain just a bit (it's been one of those days) however if I am reading it correctly this will give some apps a pseudo root.
Click to expand...
Click to collapse
Sort of, it's the highest permission you can give an app without rooting your phone.
Does it allow you to say debloat the phone or things like that?
alarmdude9 said:
Does it allow you to say debloat the phone or things like that?
Click to expand...
Click to collapse
I'm not sure I haven't tested it that far but you can access all app data folders with it so maybe?
alarmdude9 said:
Does it allow you to say debloat the phone or things like that?
Click to expand...
Click to collapse
I'm not sure I haven't tested it that far but you can access all app data folders
Hmmm have to get some time to try this. Adulting sucks.
Hello, so I'm stuck on the /sdcard/
I dont have one is just on internal storage Shizuku folder... How do im supposed to type it
Does Shizuku still work with the N200 after the November update?
I was able to get everything setup to the last step where I grant packages write permissions, but every package I name returns 'pm: no such file or directory'.
If I use Termux to try to navigate to /SD card/Android/data i get 'cannot open directory: permission denied'. I'm wondering if Termux can even access the apps to give them elevated permissions?
Finnzz said:
Does Shizuku still work with the N200 after the November update?
I was able to get everything setup to the last step where I grant packages write permissions, but every package I name returns 'pm: no such file or directory'.
If I use Termux to try to navigate to /SD card/Android/data i get 'cannot open directory: permission denied'. I'm wondering if Termux can even access the apps to give them elevated permissions?
Click to expand...
Click to collapse
I have same error
Related
So I recently did 2 things on my Archos 32:
1) Installed the Android Market (link)
2) Did a permanent root on 2.3.26 (link)
Both worked great
My new query:
So Google Voice is missing in the Android Market for me, even when I get the link from Google: There are no matches in the Android Market for the search: pname:com.google.android.apps.googlevoice I'm pretty sure some other apps are missing as well (even after applying the fix in the link)
Is there any way (rooted options included) to get these missing apps in the Android Market? I've read some stuff about a market footprint
Any info would be helpful; thanks!
Take a look at the following thread.
Anyone have a Froyo Archos with full Market Protected App access
The market footprint you're referring to is in post 3. You have to edit the build.prop file and insert the described "footprint" so that the Market thinks your Archos is actually a Galaxy Tab. Word of warning though - even with this, I still couldn't see all apps in the Market. Plus, there have been reports that the Market fix doesn't work as well with the newer 2.3.26 firmware..
fisha21 said:
Take a look at the following thread.
Anyone have a Froyo Archos with full Market Protected App access
The market footprint you're referring to is in post 3. You have to edit the build.prop file and insert the described "footprint" so that the Market thinks your Archos is actually a Galaxy Tab. Word of warning though - even with this, I still couldn't see all apps in the Market. Plus, there have been reports that the Market fix doesn't work as well with the newer 2.3.26 firmware..
Click to expand...
Click to collapse
Thanks! Looks like I'll need to look at build.prop then.
I also tried MarketEnabler but it didn't seem to do anything on my Archos... maybe I was doing something wrong.
I tried going the SDK route to edit build.prop, but I couldn't get it setup; I might try it in Linux (x64) a little later; Windows 7 (x64) didn't get my anywhere
Thanks for the reply! I'll look into it
yellowsnow4free said:
So Google Voice is missing in the Android Market for me
Click to expand...
Click to collapse
Even if you get Google Voice installed, it won't get past the "Change call settings". Or that is what I found. Anyway, over in the Xoom forum they have an edited Voice apk you can install and I am using it.
http://forum.xda-developers.com/showpost.php?p=11955195&postcount=75
fisha21 said:
Take a look at the following thread.
Anyone have a Froyo Archos with full Market Protected App access
The market footprint you're referring to is in post 3. You have to edit the build.prop file and insert the described "footprint" so that the Market thinks your Archos is actually a Galaxy Tab. Word of warning though - even with this, I still couldn't see all apps in the Market. Plus, there have been reports that the Market fix doesn't work as well with the newer 2.3.26 firmware..
Click to expand...
Click to collapse
In my search for a tutorial, I found myself here
I've been able to do all of it, I just need help copying build.prop back over to my system directory. Here's my post from androidforums:
Step 4: Remount your phone's /system directory
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
This temporarily removes the restrictions on /system
Step 5: Overwrite build.prop
With adb shell open, type:
Code:
mv /sdcard/build.prop /system/build.prop
Click to expand...
Click to collapse
I'm stuck at Step 4. I keep getting a "permission denied" error:
{
"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"
}
In case it helps, I'm running Ubuntu 11.04 x64
Click to expand...
Click to collapse
here try this its much easier:
http://forum.xda-developers.com/showthread.php?p=14864470
yellowsnow4free said:
In my search for a tutorial, I found myself here
I've been able to do all of it, I just need help copying build.prop back over to my system directory. Here's my post from androidforums:
Click to expand...
Click to collapse
You aren't rooting correctly. After you type su and hit enter, the Archos should bring up a Super User request that you have to accept. Once you have rooted correctly, the cursor block will change from $ to #.
Did you get a new SGS II? And you want it rooted, but without loosing your factory warranty, or even getting the yellow triangle? Then you're lucky if you are reading this post. All you need, is a few things.
First you need a computer(which is pretty obvious, isn't it?)
Preferably a windows computer, but I can help you, if you've got a mac, aswell.
So, now you've made sure, that you've got these things, let's carry on with the tutorial...
You need Kies (which you use to transfer files, and contacts, to/from your computer and back...) and the android SDK*. If you haven't got these programs, then click on the links below...
Go to: developer.android.com/sdk/index.html (<-Download the SDK.zip)
Just extract the ZIP to your desktop, what you'll need will come in a second...
Now, for all you windows users;
Once you have extracted the SDK_zip to the desktop(or where ever you want to) click on sdk manager.exe, and download everything from google, and download the sdk-tools for your Android version (eg. 2.2, 2.3.x or 4.0.x) once you have downloaded all these tools, close the SDK* manager, and open the folder "Platform-Tools" in here, you wil find some files called "ADB", and two other files, called WinApi. Take these, and copy these into C:\Windows\System32\
Once you have done this, we can carry on...
(On your keyboard) press (and hold) Windows + R. Once the Run dialog has opened, you can release the keys.
Type in the Textbox cmd.exe and hit enter. In the command prompt (cmd) type in this command. "Adb" if some text appears, you have correctly installed ADB* on to your computer. You can now plug your SGS II in, and wait fir windows to determine the device and start installing additional drivers. Make sure you have set your device to allow USB debugging! (Now you can drink a cuppa coffee, and wait for about 5 minutes.)
Once this has been done, type in (in cmd) this command: adb devices And hit enter. If a set of numbers and letters appear(in hexadecimal order) and the word "Device" is written behind the hexadecimal* code, then you are ready to root!
Now for the rooting, itself. (If you want permanent root, skip this part, if you just want temporary root-permissions, then read this.)
First( to make sure that, if you break something in the OS*-Partition, you can repair your device(without flashing) type in the backup command: adb backup C:\MyAndroidBackup.ab -apk -system -shared -all
Check your phone, this is needed,incase you are prompted for permission. Once the backup is done, type in the following command, to gain root access.
Type in the command prompt-window " adb root"
Now, for permanent root access;
Type in the command prompt-window: adb backup -apk -system -shared -all
Check your phone, to see if you are prompted for permission... Wait for the backup to finish. Once it is done, type in the following command, to set your phone, into a type of "Download mode": adb remount
Now, you need to download the files beneath... (Superuser and BusyBox)
Download these files to your C Drive. Now, type in this command,: adb push C:\Superuser-1.apk /system/app
And again: adb push C:\stericson.busybox.apk system/app
Once you have done this, you should be able to use them, after one reboot. So, we will do a quick reboot. This installs the applications, and gets you one step further to being a "legal" root user! To do a reboot, type in: adb reboot
After your device has rebooted, and is ready-to-use, go to your app-drawer, and look for the apps: "Super User" and "BusyBox installer". If you have found these, then you have done the first steps correctly!
Now, type in the Command-Prompt Window: adb devices. And it should say the same hexadecimal code, with the caption "Device" next to it. If it says this, then type in the final command, to gain root access.: adb root
Once you have typed in the command above, you are an official root user!
I do not take responsibility if you break your device! I would gladly help you, but don't make me responsible. And just because I'm new here doesn't mean I'm completely new to android development/ rooting etc. .
If you found, that my tutorial was good, then please thanks me. If you have any ~questions, then please ask! If you have concerns, please let me know! Screenshots and video tutorial are following. I'm still looking for a way to do this on a mac, and I have yet only found one way. But we'll get to that in another thread, once I've proven it's effectiveness. Have a nice day, and have fun rooting!
P.S This works on nearly every android device!
Edit: P.S I forgot to mention =, what the stared words mean. SDK: Software Development Kit
ADB: Android Debugging Bridge
Hexadecimal: A string of combined letters and numbers.
Man u rock
But contact a mod and mave this to development section+ur bootloadter patch one...
familyguy59 said:
type in the following command, to gain root access.
Type in the command prompt-window " adb root"
Click to expand...
Click to collapse
I'm speechless.
{
"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"
}
sahibunlimited said:
Man u rock
But contact a mod and mave this to development section+ur bootloadter patch one...
Click to expand...
Click to collapse
Will do (at some time) but now, I've got get on developing my own Kernel. Which will make all this much easier!
familyguy59 said:
First( to make sure that, if you break something in the OS*-Partition, you can repair your device(without flashing) type in the backup command: adb backup C:\MyAndroidBackup.ab -apk -system -shared -all
Check your phone, this is needed,incase you are prompted for permission. Once the backup is done, type in the following command, to gain root access.
Type in the command prompt-window " adb root"
Click to expand...
Click to collapse
familyguy59,
I'm not sure what you're trying to do here, but "adb backup" requires ICS so, that and the fact this thread is redundant, I'm closing it.
Thanks
crachel
last week i tried to root my HTC and all sudden the camera turned black and white.
i tried to look for sitting, but i couldn't find anything help.
so i reset the phone to the defult and i still have the same problem.
and an application called " superuser " haven't been deleted.
also the software version is 2.2, and i tried to update but i couldn't!
anyone can help please ! i want the camera to work so badly !
Well it sounds like something messed up during root,
You can't remove SuperUser it's used for ROOT to grant root access to apps that require it.
Step by step for troubleshooting.
1)Download "Camera Fix 2.2.zip" (Attached File)
2)Extract contents (Two APK files) to the root of your SD card.
3)Mount SD to phone.
4)Use a application installer or file browser and find "Camera.apk, and Gallery3D.apk"
5)Install both programs
6)Reboot phone.
----------------------------
If this method doesn't work continue on with this.(DO NOT DO THIS UNLESS THE ABOVE FAILED)
1)Search Market for "ROM Toolbox"
2)Install this program
3)Open this program, A Dialog box will pop-up asking for ROOT.
4)Accept ROM Toolbox for ROOT.
5)Open "App Manager"
Here you will see a list of apps, along with category tabs. Swipe to the right till you are in the All Apps category, scroll down till you see "Camera"
6)Long Press/Click the Camera bar/app until a menu pops-up
7)You will see "Launch, Backup, Uninstall, Manage, etc...
Scroll down to "Zipalign", click it/press it. You will see a few things pop-up just saying it's zipaligning the app.
8)Now repeat step #6.
9)From this menu again, scroll down till you see "Fix Permissions" Click it/Press it.
10)Reboot phone, and hopefully that works!
redbaron2005 said:
Well it sounds like something messed up during root,
You can't remove SuperUser it's used for ROOT to grant root access to apps that require it.
Step by step for troubleshooting.
1)Download "Camera Fix 2.2.zip" (Attached File)
2)Extract contents (Two APK files) to the root of your SD card.
3)Mount SD to phone.
4)Use a application installer or file browser and find "Camera.apk, and Gallery3D.apk"
5)Install both programs
6)Reboot phone.
----------------------------
If this method doesn't work continue on with this.(DO NOT DO THIS UNLESS THE ABOVE FAILED)
1)Search Market for "ROM Toolbox"
2)Install this program
3)Open this program, A Dialog box will pop-up asking for ROOT.
4)Accept ROM Toolbox for ROOT.
5)Open "App Manager"
Here you will see a list of apps, along with category tabs. Swipe to the right till you are in the All Apps category, scroll down till you see "Camera"
6)Long Press/Click the Camera bar/app until a menu pops-up
7)You will see "Launch, Backup, Uninstall, Manage, etc...
Scroll down to "Zipalign", click it/press it. You will see a few things pop-up just saying it's zipaligning the app.
8)Now repeat step #6.
9)From this menu again, scroll down till you see "Fix Permissions" Click it/Press it.
10)Reboot phone, and hopefully that works!
Click to expand...
Click to collapse
really thanks for helping me, for the first method i tried to install the camera.apk and the gallery3d.apk but each time a message shows before the installations says " application not installed " .
and for the second method didn't work.
please can you tell me how to install the camera.apk and the gallery3d.apk?
EMZiq said:
really thanks for helping me, for the first method i tried to install the camera.apk and the gallery3d.apk but each time a message shows before the installations says " application not installed " .
and for the second method didn't work.
please can you tell me how to install the camera.apk and the gallery3d.apk?
Click to expand...
Click to collapse
Okay, lets download Android Commander this is the easiest way to use ADB. ADB is going to be what we use to fix your phone.
After its downloaded...
and Installed...
Lets do a test and see if your phone will show up...
1)Install Android Commander
2)Plug your phone in with the USB to your computer
3)Go to Settings > Development > USB Debugging we want this ON
4)Did your computer realize your phone is connected?
If not, I need to know what phone you have so I can further help you.
If it doesn't show up you need ADB Drivers for your phone...
If it does work....
5)Open Android Commander
6)You will see a pop-up
{
"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"
}
Hopefully you will also see something under "Select Device"
click OK, Android Commander will start.
7)In the right hand menu you will see your phone's system files among other things.
8)Look for the system folder, open it.
9)look for the "app" folder, open it.
10)Drag and drop the apk file I gave you into this folder (system/app)
11)Click the power button on Android commander and reboot phone. Or just reboot your phone.
I really hope that this is helping and I can help you out.
Let me know if Android Commander finds your phone or not.
HTC Desire right?
http://www.mediafire.com/?mhzhki52ntbmmiz
Download the drivers if you don't have them.
Extract them to the desktop or anywhere you like,
then Go into your Control panel... Start > Control Pannel > Device Manager
Then look under Android Phone, or Other Decises, right click your phone if you find it. Click Update Driver Software, Browse file from Computer, then point it to where ever you put the drivers
i really appreciate your work and time that you spending helping me
but it didn't work
the debugging worked fine and i followed each step, but it's still black and white !
is there any way i can reset it to the original ? i remember doing backup before in a MyBackup pro. but it's only restore the data and pictures and stuff and it wouldn't restore the camera to the default
please help
Firstly: I'm new here, but I'm sure this is a fresh thread. I doubt anyone else will have asked this yet.
So basically, CommBank Kachinghttps://play.google.com/store/apps/details?id=au.com.commbank.kaching is an online banking app, but the developers have decided that it can't be downloaded to or run from a rooted device. I think.
Basically, is there a filter that will allow Play to disallow rooted device from downloading, or is it the Device Status flag that does this? Also, if downloaded to a stock device which is later rooted, the app will fail to run, with a message saying "This device cannot be supported." I suppose this is the nice way of letting us down.
Is there anyway for me to check whether a particular "status" is preventing this from running?
There are a limited number of devices that are currently supported, but the I9300 is one of them. It requires 2.3 (GB) or above, which I'm running, technically. The app actually worked during the root process, right up until the device rebooted to complete the root process - I'm guessing that that's when the "Device Status" is updated? Would this be it?
tl;dr
Is there anyway to find out what is 'triggering' this app? (And how would I do this?)
If it is the Device Status = 'Modified', is there a way to change this?
Is there anyway to find out what is 'triggering' this app? (And how would I do this?)
Some apps refuse to run due to security risk of root . Fix font know but i would look in APPS section .
If it is the Device Status = 'Modified', is there a way to change this?
Unroot and flash a stock rom is all so far .
jje
hxxps://dl.dropbox.com/u/32917310/modded.commbank.kaching-p1xel8ted.rar (if you cant be bothered do the steps below.)
First off, you need to get "framework-res.apk" off your Rom, it can be found in /system/framework. Put it somewhere safe for now.
1. Get APKMultiTool from hxxp://apkmultitool.c0m/, when your run it for the first time, before selecting any options, copy your "framework-res.apk" into {apkmultifolder}/platform-tools.
After its copied, select option 2, then option 1. It may exit afterwards, if it does, re-run "setup.bat", found in the apkmulti install folder, and select option 3.
After that, run Apk Multi-Tool from the desktop.
2. On your phone, using a file explorer (Romtoolbox, esfile explorer etc) make a backup of CommBank and Kaching
3. Copy those backups as APKs to your computer
4. Place the apks in the "place-apk-here-for-modding" folder within the APKMultitool directory.
5. Run apkmultitool
6. Use option 23 (set project) and select commbank
7. Use option 9 (decompile)
8. Repeat step 6 and 7 for kaching
9. Open {apkmultifolder}\projects\au.com.commbank.kaching.apk\smali\au\com\vivant\util\deviceutils.smali
10. At line 32, replace and save
const-string v1, "test-keys"
with
const-string v1, "test-keysss"
11. at line 61, replace and save
const-string v2, "/system/app/Superuser.apk"
with
const-string v2, "/system/app/Superuser11.apk"
** Repeat steps 10 and 11, but with {apkmultifolder}\projects\CommBank_2.2.2.apk\smali\au\com\vivant\util\deviceutils.smali
12. Back into apkmultitool, again using option 23 (set project) select commbank
13. Use option 11 (compile), answer No to system app, and answer No to use other files
14. Use 12 (sign).
15. Repeat steps 12 to 14 but selecting kaching instead.
16. Go back into "place-apk-here-for-modding" and there will be two new files with "signed" in front of the names, copy those to your phone and install.
What we've done is basically "cracked" the check for your phone being rooted or custom rom'd/modified.
Why dont you just get an app that hides root? i did that and it works great!
although the app does suck. its a shoddy iClone
I am also rooted and use siyah kernal, which has the 'remove root' function. I leave the option 'restore root on reboot' ticked and once I've finished I just reboot the phone.
Edit: Just found a quicker way which doesn't require a reboot, as per Milz123's recommendations. And it wasn't that hard or messy.
I downloaded 'hide my root' from the play store. Then I selected 'hide su binary' then 'hide su app'. Logged on Kaching and worked perfect.
Logged out then restored su binary then su app and tested some apps which require root. They worked prefect. Then tried logging into Kaching again but couldn't.
Fyi, I use supersu, not superuser. When I selected to hide the su app it said it didn't exist, but in reality it still hid then restored the correct app. So worked 100% and took seconds.
Edit 2: Tested with just 'hide su app' and it worked. Phone is still rooted and app works.
{
"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"
}
Sent from my GT-I9300 using xda premium
I'm new here so couldn't reply to the post from http://forum.xda-developers.com/newreply.php?do=newreply&p=56767184
which I have quoted:
mtyler7807 said:
Here Is a Custom splash logo Consumercelluar and the other branded phones
Directions:
1. use es explorer and go to Cust/????/us/logo/oemlogo.mbn in the root (device) directory.
2. Rename the file in the Cust/????/us/logo folder to oemlogo.mbn1
3.Copy the supplied logo and paste it in your Cust/????/us/logo or get your own logo, just make sure that it 720x1280.
4. Then use Terminal explorer and type Su
5 then type load_oemlogo
6 restart and logo has changed.
{
"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"
}
oemlogo.mbn
https://drive.google.com/file/d/0BwnSk8BOQp3wb0RQOUphbjJMNFU/view?usp=sharing
Click to expand...
Click to collapse
HUAWEI Ascend Mate 2 MT2-L03 rooted.
I have changed the carrier logo to the one down loaded and tried to follow the instruction. "Terminal Explorer" search on play store brings up several "Terminal Emulator" apps but not "terminal explorer" . I tried a emulator but "Su" doesn't work. "su" changes the prompt to root. It wasn't clear whether enter was supposed to be used between Su and load or not. My boot screen hasn't changed after rebooting. Any suggestions?
Terminal Emulator for Android has a need for busybox
you has -busybox?
Coss83 said:
Terminal Emulator for Android has a need for busybox
you has -busybox?
Click to expand...
Click to collapse
yes, busy box installed
solved "Clarification on changing the boot screen please"
bhcv said:
I'm new here so couldn't reply to the post from http://forum.xda-developers.com/newreply.php?do=newreply&p=56767184
which I have quoted:
HUAWEI Ascend Mate 2 MT2-L03 rooted.
I have changed the carrier logo to the one down loaded and tried to follow the instruction. "Terminal Explorer" search on play store brings up several "Terminal Emulator" apps but not "terminal explorer" . I tried a emulator but "Su" doesn't work. "su" changes the prompt to root. It wasn't clear whether enter was supposed to be used between Su and load or not. My boot screen hasn't changed after rebooting. Any suggestions?
Click to expand...
Click to collapse
How to change boot logo
Quote:
Originally Posted by mtyler7807 (forum.xda-developers dot com/ascend-mate2/general/consumer-wireless-variant-t2888615/page7)
Post the steps. Thats all I need to complete the change. From Consumer Cellular.
Here is instruction to change boot logo for Consumer Cellular version:
1. root the phone, install ES File Explorer or Root Browser, and ConnectBot or any terminal app, and grant super user right to these apps
2. backup original boot logo at /cust/us/consumercellular/logo/oemlogo.mbn if you really like that ugly image
3. make a 720x1280 image then flip it vertically (if you forget to do this, you will find out soon...)
4. save the image as 24bit bitmap file (BMP format), any program should be fine as long as it can save file in this format without any additional tag, header, profile etc
5. use this "BMP header remover" (Windows only, but it should not be hard to write your own for Linux) to remove the 54 byet header from the BMP file:
http://karpolan.com/software/bmp-header-remover/
6. copy the modified BMP file to your phone as /cust/consumercellular/us/logo/oemlogo.mbn
7. make a backup copy of this file : /data/custom.bin
8. use ES File Explorer or Root Browser or terminal app to modify the text file /data/custom.bin, just add a few characters to the end of line, for example, anything will do, just change it, and save. Please don't ask me why, a few Chinese posters figured this out on their Chinese version, I have no idea why this works.
Code:
consumercellular/us
to
Code:
consumercellular/us-xyz
9. go to a terminal (eg ConnectBot) on your phone, type:
Code:
$ su
# load_oemlogo
you should see a line says something and it should take a second or two to execute. if you see nothing and it finishes in no time, then you did not do step 8 correctly
10. put the text file /data/custom.bin back to its original form, hope you did back it up!
Code:
consumercellular/us
11. reboot, and you should have your new boot logo.
Shutdown logo
The instructions worked for everything except the shutdown logo...its still that ugly consumer cellular logo...ideas?
That's a separate file. Just delete it. Or rename it something other than shutdownanimatiin.zip