Related
In framework-res.apk, what controls the color of the text for the status bar, such as notifications and the digitial clock? Are these controlled independently by seperate apks?
I'm considering diving in and attempting to skin my android but I want to know what I'm getting into.
I've tried replacing framework.apk that I built from source on a real device and emulator. Only bad things came of it. Had to reflash. Let me know if you have better luck.
I'm pretty sure it failed because a lot of the stuff in framework.apk is stubbed closed source stuff.
Koush,
Have you looked at this post by Living_Sword?
I suggest you enter the following commands using adb, because its faster and reliable than telnet or any other method. If you do not have adb setup, read here, if you do, then just enter adb shell in the console while the phone is connected.
In simple words, you have to re-sign the framework-res.apk with your own key. You should know that you will loose all your data while doing this mod. Here are the steps,
1. Re-sign and re-upload all the .apk files in /system/app with your own key or the test-keys. The command used for signing is included in the readme file alongwith the signing jar here.
2. Take a backup of /system/framework/framework-res.apk. Now, you would want to edit some stuff in framework-res.apk, for that the easiest method is to rename the apk file to .jar/.zip, put in your own files(with same name as original png) and rename it back to .apk. You have to re-sign this apk with the same key like you did in the first step.
3 . Upload the apk file to /system/framework. The phone will hang, and in few secs it will most likely go back to the android robot screen.
4. Take out the battery, then do a data reset by going into recovery mode and pressing ALT+L to see the log text and then ALT+W to wipe out /data. Obviously, you will loose all your apps and settings and will have to re-activate the phone.
5. After the wipe is complete, press HOME + BACK to reboot. The phone should reboot normally now.
I know its a pain to loose all the data and apps, but this is the easiest method until we figure out something more elegant, and its required to be done only once. Also, there is no need to keep the png file size same. And in future, you will be able to replace the framework-res.apk without any hassles.
Also, since each stock app's icon is in its own apk, once you re-sign every apk in /system/app, you can easily replace their icons with your own.
Source: http://www.modmygphone.com/forums/showthread.php?p=16871#post16871
Ok, so I have successfully replaced framework-res.apk with my own build which includes custom icons and things like that. However, I am running into two problems:
1: I keep running out of room in my system folder. Everytime I replace framework-res.apk I am losing space somehow, eventually I have to do the mod rc30 update all over again to get my memory back so I can push this file over, where is this space going? Whats eating it up? Oh, and it isn't the file size growing, this will happen if I pull a file and directly try to push it back onto the phone.
2: I still don't know how to change the default color of the text. I assume it is in one of these xml files but I'm not sure, and I haven't found it yet. Could it be in /res/color/?
If anyone could help me on these two issues I would be so appreciative.
This is what I've done so far, see the status bar and the icons?
Stericson
Stericson said:
Koush,
Have you looked at this post by Living_Sword?
I suggest you enter the following commands using adb, because its faster and reliable than telnet or any other method. If you do not have adb setup, read here, if you do, then just enter adb shell in the console while the phone is connected.
In simple words, you have to re-sign the framework-res.apk with your own key. You should know that you will loose all your data while doing this mod. Here are the steps,
1. Re-sign and re-upload all the .apk files in /system/app with your own key or the test-keys. The command used for signing is included in the readme file alongwith the signing jar here.
2. Take a backup of /system/framework/framework-res.apk. Now, you would want to edit some stuff in framework-res.apk, for that the easiest method is to rename the apk file to .jar/.zip, put in your own files(with same name as original png) and rename it back to .apk. You have to re-sign this apk with the same key like you did in the first step.
3 . Upload the apk file to /system/framework. The phone will hang, and in few secs it will most likely go back to the android robot screen.
4. Take out the battery, then do a data reset by going into recovery mode and pressing ALT+L to see the log text and then ALT+W to wipe out /data. Obviously, you will loose all your apps and settings and will have to re-activate the phone.
5. After the wipe is complete, press HOME + BACK to reboot. The phone should reboot normally now.
I know its a pain to loose all the data and apps, but this is the easiest method until we figure out something more elegant, and its required to be done only once. Also, there is no need to keep the png file size same. And in future, you will be able to replace the framework-res.apk without any hassles.
Also, since each stock app's icon is in its own apk, once you re-sign every apk in /system/app, you can easily replace their icons with your own.
Source: http://www.modmygphone.com/forums/showthread.php?p=16871#post16871
Click to expand...
Click to collapse
framework-res.apk is just the resources. framework.apk contains the actual code used by every application in the system. Attempting to replace THAT file the result of the android build process will fail.
I think we're talking about two different files.
Oh yep, definetly we are...I thought you were talking about that but I figured you would clarify if you were indeed. Thanks.
so you guys are making progress on some themes... GOOD ****..
jzajzz said:
so you guys are making progress on some themes... GOOD ****..
Click to expand...
Click to collapse
Agreed. Once this process is mastered, and some polished themes, or a tool to make your own (or something) comes out, our G1's will look even sweeter.
jzajzz said:
so you guys are making progress on some themes... GOOD ****..
Click to expand...
Click to collapse
Well, I was making progress, but now my phone is bricked. Don't know how it happened. Was doing the same thing I've done over 20 30 times, suddenly started giving me problems, reflashe JF update and voila! bricked phone. So now I'm getting a new one sent to me and hoping that it comes pre-rc30. Sucks too because I am pretty sure I found out where the text color is set. Thats why I'm trying to get this to work under the emulator, but I can't get it to work. The dang emulator won't reboot or shutdown. So I can't see the changed made.
It sounds like it's too late to help now. But how was the phone bricked? Did it go into an infinite reboot cycle? Stay on the G1 screen?
Also, I assume you hadn't loaded the dev bootloader? That could have easily saved your phone from brickage
JesusFreke said:
It sounds like it's too late to help now. But how was the phone bricked? Did it go into an infinite reboot cycle? Stay on the G1 screen?
Also, I assume you hadn't loaded the dev bootloader? That could have easily saved your phone from brickage
Click to expand...
Click to collapse
My phone does have the dev bootloader on it. However, now it just stays on the boot splash screen and I can't do the update because it says the /dev file is gone! Can I reflash all of that and save my phone?
Btw, I actually think the entire folder /system is gone, because I can't abd with root, and when I did it in the update screen my system folder wasn't showing. So, I have no idea how this happened.
Is it possible to push that entire folder back on there and then recover or something?
Yes, you can reflash the recovery partition using the fastboot protocol, which the dev bootloader supports. There isn't a windows binary for it yet, but if you have a linux or mac handy, turn on the phone into bootloader mode, then plug in the USB cable. "Serial0" should change to "FASTBOOT". now you can use the fastboot binary on your computer to flash anything on the phone. You might try re-flashing the recovery image that's in my modified update. If that doesn't work, maybe try flashing the radio too.
If you have the dev bootloader, I'm almost positive your phone can be saved. Give me at IM if you want to talk about it.
I *think* the fastboot binary is in the sdk for linux/mac. I could be wrong though. There are copies of both floating around though, just ask if you need one.
I managed to repack framework-res.apk and resign all other packages without wiping. The problem is with the signatures in /data/system/packages.xml - they no longer match after resigning. The solution is to simply delete all <sigs> sections (and the <certs> within), and the PackageManager will automatically regenerate them as they are launched. I just now successfully booted, so can't say this is thoroughly tested, but I'll report back here if any problems crop up.
donniesmit said:
I managed to repack framework-res.apk and resign all other packages without wiping. The problem is with the signatures in /data/system/packages.xml - they no longer match after resigning. The solution is to simply delete all <sigs> sections (and the <certs> within), and the PackageManager will automatically regenerate them as they are launched. I just now successfully booted, so can't say this is thoroughly tested, but I'll report back here if any problems crop up.
Click to expand...
Click to collapse
A good check after doing something like this is to take a look at the call log, and actually receieve a call (call yourself from your home phone, or whatever). Both of these like to error out when messing around with resigning.
The original TPC v3 ROM only use power button to wake up the phone.
Here is the one I just did in case someone also needs use volume keys to wake up the phone.
Thanks for icenight89's direction and syc7090's tutorial
I installed it on my phone and tested. no side effects found.
Install:
simply copy the attached jar file into /system/framework to replace the original one (backup first of course
flashable zip
this is simply the file above ^^^ remade into a flashable zip you can use with cwm (clockworkmod), if you're unsure of how to replace it. Please make sure all thanks go to LeeC, he's the one that did the work, i simply assisted.
Got the modded Camera.apk from Here. I changed my hardkey Search button to function like a Menu key (my menu hardkey won't work properly). I liked the search key as a snapshot key for the camera but now with me changing 217 "SEARCH" to MENU" it doesn't work.
I downloaded APKTool and decompiled modded .apk. Now the only problem is I can't find where to change the key to take a snapshot with "MENU" pressed. I have been looking through the .smali files and not having any luck. Menu key as far as I have seen has no function in the camera app anyways so this shouldn't be a problem.
Last question I would have (which I could probably search) would be how to take the decompiled .apk and compile it back to .apk.
Is the code for the menu button 217 or is that independent of the button?
Sent from my SCH-I510 using xda premium
Within /system/usr/keylayout/qwerty.kl "key 217 SEARCH" I changed to "key 217 MENU" also I changed /system/usr/keylayout/s3c-keypad.kl "key 217 SEARCH" to "key 217 MENU".
That is how I got Search button to open Menu.
I'll take a look for you. It probably won't take too long.
Yeah it should just be changing the key event code from the search key to the menu key in a few places.
dwitherell said:
Yeah it should just be changing the key event code from the search key to the menu key in a few places.
Click to expand...
Click to collapse
The problem for me is I can't find those few places. lol Searching through all these .smali files I think I'm gonna need my search button back lol.
Edit: I opened all of the files in NotePad++ and did a search for "search" and found several items but I don't know what to change or leave.
I think what I need to change is in AbstractCameraActivity.smali
Enlightened_Rogue said:
The problem for me is I can't find those few places. lol Searching through all these .smali files I think I'm gonna need my search button back lol.
Click to expand...
Click to collapse
I'm sure substanceD will get it for ya, but camera.smali and camcorder.smali are 2 at least. It'll be in the onkeyup and onkeydown event methods (just looked at this, but memory is a bit sketchy...)
dwitherell said:
I'm sure substanceD will get it for ya
Click to expand...
Click to collapse
As you see I don't mind doing the leg work, I'm not one of these beggers out there that just want someone to build a app just for me. Thanks for giving me some pointers. I'm just trying to learn as I go. New to modding phones (trying to get better).
Enlightened_Rogue said:
As you see I don't mind doing the leg work, I'm not one of these beggers out there that just want someone to build a app just for me. Thanks for giving me some pointers. I'm just trying to learn as I go. New to modding phones (trying to get better).
Click to expand...
Click to collapse
All right, let's see if I can be helpful without doing the work for you. The Android key codes are published here: http://developer.android.com/reference/android/view/KeyEvent.html. The smali files have the hex values for these key events without the extraneous zeros. For example, you'll notice that KEYCODE_POWER is sprinkled throughout the code as 0x1a. Try to find a block of code that refers to the common keys (power, search, menu, etc.) and see how it delegates them.
OK I replaced 0x54(Search) with 0x52(Menu) [14 instances] and then Compiled with APKTool. Moved Camera.apk to /system/app/ and now phone doesn't recognize Camera.apk. I restarted, tryed setting permissions to rw-r--r-- then restarting as well and still not being recognized.
Edit: Noticed when I moved your modded the permissions where rwxrwxrw- and it still showed up without restarting.
Enlightened_Rogue said:
OK I replaced 0x54(Search) with 0x52(Menu) [14 instances] and then Compiled with APKTool. Moved Camera.apk to /system/app/ and now phone doesn't recognize Camera.apk. I restarted, tryed setting permissions to rw-r--r-- then restarting as well and still not being recognized.
Edit: Noticed when I moved your modded the permissions where rwxrwxrw- and it still showed up without restarting.
Click to expand...
Click to collapse
Did you sign it (don't)? Also, there are some sound files in /res/raw that need to stay UNcompressed for things to work properly.
All I did to compile was from Here.
Code:
apktool b <directory of decoded apk>
Never compiled any apk before. How do you not sign it and not compress some of the resource files?
Edit: Just seen this at the bottem, but I'm using APKTool 1.4.3
idroid84 said:
Issues;
I noticed that while the new version 1.2 works great on the framework-res.apk file, it seems to have issues with other System/app files like Settings.apk,Phone.apk, etc. For these files use version 1.1.1.
Click to expand...
Click to collapse
Enlightened_Rogue said:
All I did to compile was from Here.
Code:
apktool b <directory of decoded apk>
Never compiled any apk before. How do you not sign it and not compress some of the resource files?
Edit: Just seen this at the bottem, but I'm using APKTool 1.4.3
Click to expand...
Click to collapse
Well the first part shouldn't be an issue I don't think. For the second - an apk is similar to a zip file. I would use something like jzip or winrar to extract out those sound files, delete them from the apk, then drop them back in using store or storage (i.e. no) compression. Though I am doubtful not doing this would cause the phone to not recognize the apk to be honest.
I opened the Original Modded .apk with 7zip moved the res files over just playing around waiting for a response and still no luck. Also I noticed while doing that the Modded on had a META-INF folder which I moved over to my Mod and after all that moved to phone /system/app and restarted phone still no Camera in App Drawer.
Original Mod I decompile: Camera 5-14-12
My Decomipled and editied:Camera - Menu Button
I was messing around with my phone and decided to install PBJ Kernel 0524. After installing that now Root Manager won't allow Mount R/W so now I can't change system files. I guess I'm stuck with what I got for now.
Edit: Complete noob moment... Went into CWM -> Mounted System -> Installed SU again. Now works. Back to working on Camera
Enlightened_Rogue said:
I was messing around with my phone and decided to install PBJ Kernel 0524. After installing that now Root Manager won't allow Mount R/W so now I can't change system files. I guess I'm stuck with what I got for now.
Edit: Complete noob moment... Went into CWM -> Mounted System -> Installed SU again. Now works. Back to working on Camera
Click to expand...
Click to collapse
Yeah the lost root is just a permissions thing - a number of ways to fix it, and installing su is definitely one of them. Glad you got that figured out.
I looked into this more - you changed too many 0x54s... not all of those were relevant to what you wanted (only 6 were). On top of that, only two of them were changing 0x54 to 0x52 (CamcorderRecordingMenu.smali) - the other 4 (2 in Camcorder.smali and 2 in Camera.smali) were simply changing the :sswitch_ value associated w/ 0x52 to that associated w/ 0x54.
Anyhoo - end result should now be power, menu, and search take pics/start video. Here's the apk - just rename to Camera.apk and push. If it doesnt show up right away and a reboot doesnt fix it, you could try to push in recovery, or dump it in a cwm-flashable zip and flash it. Hope it works for ya!
Thank you. I figured I probably changed too many. I just opened notepad++ and find/replaced in files. I was looking through but was having a difficult time tracing what was needed and was not. How did you compile just like I posted earlier? And how did you get META-INF and not compressing resources?
Enlightened_Rogue said:
Thank you. I figured I probably changed too many. I just opened notepad++ and find/replaced in files. I was looking through but was having a difficult time tracing what was needed and was not. How did you compile just like I posted earlier? And how did you get META-INF and not compressing resources?
Click to expand...
Click to collapse
I was lazy and used one of the gui-ized apktool approaches (apkmultitool). It took care of keeping things in order. After recompiling, I opened the apk in jzip, pulled out the oggs in /res/raw, deleted them from the apk, then put them back in and set compression to store. It should be noted that you could go about things without dealing with any of this - just pull out the classes.dex from the apk, use baksmali to decompile and smali to recompile, and place new classes.dex into the apk.
I take it the apk worked for you then?
Yes it worked perfectly! Thank you. Instead of just getting what I want then not saying anything I was decompiling yours and seeing what needed to be changed. Hopefully soon I will be able to to much much more. Just a little time devotion patients and people like you to help. Thank you so much!
Hi all,
Here are the two files that you will need to have onscreen ICS buttons and disable the capacitive buttons on the bottom.
Directions and Disclaimer:
I have only used this on Alien ICS 4.0.4 Stock/DeOdexed/Zipalign/Root/Busybox
I am not responsible for your efforts/errors
- THE FILE BELOW IS NOT A FILE THAT CAN BE FLASHED.
- copy both files from the .zip file to /sdcard
- enable debugging on your phone, from a command prompt type the following
- from a command prompt, pull the two original files and save them as a backup!
adb pull /system/framework/framework-res.apk
adb pull /system/usr/keylayout/Generic.kl
- then do the following
adb shell
su
mount -o remount,rw /dev/blk/mmcblk0p24 /system
cp /sdcard/framework-res.apk /system/framework/framework-res.apk
chmod 644 /system/framework/framework-res.apk
cp /sdcard/Generic.kl /system/usr/keylayout/Generic.kl
chmod 644 /system/usr/keylayout/Generic.kl
reboot recovery
- from recovery, wipe cache and wipe dalvik under advanced
- after device reboots, I Highly recommend using Rom toolbox to change your DPI to 190
- you will need to download exDialer and CameraICS from the market
- also, the stock SMS app will NOT allow you to change your settings, so either turn off the notifications first and switch to a different SMS app that supports ICS or set it the way you want and then do this.
- I personally use Apex Launcher, but other Launchers that resize are fine. I believe that TouchwizUX is ok to use, but haven't tried that yet.
Hope this helps, and developers please use this, as I have taken from you all as well. Thanks to Evilisto for his tutorials.
Redd.
Skyrocket - UCLE2 Alien Stock with ICS onscreen keys and APEX launcher
Thanks for the work, this should be good! Can't wait to try this out!!!!!!
Is there anyway to do this on the t mobile galaxy s ii? I'm on aokp so even just disabling the capacitive buttons would be nice
CAYCE_VII said:
Is there anyway to do this on the t mobile galaxy s ii? I'm on aokp so even just disabling the capacitive buttons would be nice
Click to expand...
Click to collapse
+1
Interesting and I would love to try this, BUT the computers at the job have disabled the USB ports (except for charging) so no command prompts can be run
Does this mod add a "Menu" button with the on-screen keys like the Galaxy Nexus? So we can still do Menu>Settings and such?
I know I sound like an a for asking, but can you please make this flashable? My Mac does not like Su and always denies her.
That's great. thanks for share.
Responses to questions.
I will try to work on a flashable .zip file soon. As far as working on a SGS2, my recommendation would be to go into the /system/usr/keylayout/ and copy General.kl file. Make sure to have a backup of this file. Download Notepad++ to edit this file on a computer and look for the following
MENU
HOME
SEARCH
BACK
and put a # in front of each of those "key 103 (whatever number it is)" lines
then save the file and push it back to the /system/usr/keylayout directory like I mentioned in the directions and chmod 644 /system/usr/keylayout/General.kl to fix the permissions on it and make it the same as other system files. Also, reboot your device and clear dalvik and wipe cache.
As far as making a menu key, no, this will not do that. This is purely AOSP stock options that are enabled by decompiling and reverse engineering. The menu button will make itself available in the upper right corner of almost every app, with the exception of the stupid samsung sms, which i mentioned before.
Hope I answered everyone's questions!
Redd.
Skyrocket -- Alien UCLE2 Stock/Rooted/blah-blah
PS. Samsung shelved the Skyrocket HD and called it the Galaxy S3 because the quad-core didn't pass FCC in the united states. So make sure NOT to rush to your local stores to get a phone THAT YOU ALREADY HAVE! kthxbye.
Any update on this?
Sent from my SAMSUNG-SGH-I727 using XDA
Hi OP,
Any update on the progress at making a flashable zip ?
I recently installed the ICS Leak #2 and installed scv7, but there were several new features that annoyed me. I like to lie in bed to use my phone, so when I turn sideways, the screen turns from landscape mode to portrait mode, but the portrait mode is with the earpiece and camera at the bottom, and the buttons at the top. I have never had a problem with this with gingerbread/scv5. If anybody could tell me any way to disable it, that would be great, and I think the default launcher installed with scv7 is Holo Launcher, if I'm not mistaken.
One more thing, I had to install the Bootmenu manager when I was installing scv7, and everytime I hold the power button, then tap "Power off", I'm greeted with a list of options such as "Normal shutdown, reboot, and many other ones that I don't need, is there any way to disable this, and possibly add reboot back to the main list, like scv5?
Thanks.
CM9onmyMoPho said:
I recently installed the ICS Leak #2 and installed scv7, but there were several new features that annoyed me. I like to lie in bed to use my phone, so when I turn sideways, the screen turns from landscape mode to portrait mode, but the portrait mode is with the earpiece and camera at the bottom, and the buttons at the top. I have never had a problem with this with gingerbread/scv5. If anybody could tell me any way to disable it, that would be great, and I think the default launcher installed with scv7 is Holo Launcher, if I'm not mistaken.
One more thing, I had to install the Bootmenu manager when I was installing scv7, and everytime I hold the power button, then tap "Power off", I'm greeted with a list of options such as "Normal shutdown, reboot, and many other ones that I don't need, is there any way to disable this, and possibly add reboot back to the main list, like scv5?
Thanks.
Click to expand...
Click to collapse
Please don't re-post your issues, regardless of whether you feel you originally posted in an incorrect sub-forum. Ask one of the moderators to look at your post, and request it to be moved if necessary. You now have two posts with this issue (First one being HERE), and it clutters up the forum when people do this sort of thing.
As for the power menu found in the BootMenu app, that's just part of the application. You might find it very useful later on down the line. If you're just wanting to reboot, it only adds one additional click, so I wouldn't concern yourself too much over it. And, like I said, it may come in handy (and save your arse) at some point...
I think I may have just soft bricked my phone again. Stuck on the boot screen now, with the flashy scv7 thing. I edited framework-res.apk but must have improperly put it back.
CM9onmyMoPho said:
I think I may have just soft bricked my phone again. Stuck on the boot screen now, with the flashy scv7 thing. I edited framework-res.apk but must have improperly put it back.
Click to expand...
Click to collapse
you probably didnt set the permissions?
souljaboy said:
you probably didnt set the permissions?
Click to expand...
Click to collapse
yeah, i think. any way to fix this besides resetting the phone?
i can use project lense recovery right when the boot up occurs though.
did you try the fix permissions option in boot menu?
RoadToNever said:
did you try the fix permissions option in boot menu?
Click to expand...
Click to collapse
just tried it, still stuck on the scv7 screen
CM9onmyMoPho said:
just tried it, still stuck on the scv7 screen
Click to expand...
Click to collapse
It may be the edits, or how it was compiled.. Sometimes it's best to just do your edit, compile, then copy the edited files back to the original apk. In this case with the /values folder edits, they end up in the resources.arsc - move your newly compiled one back to the original apk with 7-zip/winrar. And actually with the framework-res.apk, you usually need to have no compression on the resources.arsc... copy that new resources.arsc somewhere next to the original apk, then add it to the archive in "store" mode - no compression with 7-zip.
alteredlikeness said:
It may be the edits, or how it was compiled.. Sometimes it's best to just do your edit, compile, then copy the edited files back to the original apk. In this case with the /values folder edits, they end up in the resources.arsc - move your newly compiled one back to the original apk with 7-zip/winrar. And actually with the framework-res.apk, you usually need to have no compression on the resources.arsc... copy that new resources.arsc somewhere next to the original apk, then add it to the archive in "store" mode - no compression with 7-zip.
Click to expand...
Click to collapse
How do I move it with winrar? I can't access anything besides the project lense recovery menu.
CM9onmyMoPho said:
How do I move it with winrar? I can't access anything besides the project lense recovery menu.
Click to expand...
Click to collapse
I meant on your computer.... how did you make the edits? framework-res.apk/res/values/bools.xml?
Well, you are probably going to have to restore a backup first. Unless you can make a flashable zip with a working version of the apk you edited, take out your sdcard and use a reader to access it on your comp - then flash that instead of an entire system restore.
alteredlikeness said:
I meant on your computer.... how did you make the edits? framework-res.apk/res/values/bools.xml?
Well, you are probably going to have to restore a backup first. Unless you can make a flashable zip with a working version of the apk you edited, take out your sdcard and use a reader to access it on your comp - then flash that instead of an entire system restore.
Click to expand...
Click to collapse
I made the edits with apktools on my computer, I sent the file on my phone to my computer, then the finished product from my computer back to my phone.
CM9onmyMoPho said:
I made the edits with apktools on my computer, I sent the file on my phone to my computer, then the finished product from my computer back to my phone.
Click to expand...
Click to collapse
Right. So you probably need to redo it. Is the original META-INF folder in your finished apk?
I would just decompile a fresh one..
Edit the bools only..
Compile..
Then move the new resources.arsc to the old apk in store mode..
Then use root explorer or a zip or adb.. but set proper permissions.
Sent from my phone's mind
So does that mean i have to do a reset on my phone again? Because I can't access root explorer right now.
CM9onmyMoPho said:
So does that mean i have to do a reset on my phone again? Because I can't access root explorer right now.
Click to expand...
Click to collapse
Are you still bootlooping? You need to go into recovery and restore, or flash a ROM again first..
Sent from my phone's mind
Not sure how well this would work, but worth a shot: https://play.google.com/store/apps/details?id=nl.fameit.rotate
Sent from my rooted Mayan Calendar