Related
I had a mod done to my widgetlocker apk , but i cant adb push it. Can someone please sign it for me so i can install using root explorer? Im not sure how difficult it is , so if its insanely hard or something im sorry for asking haha . Thanks .
Get apkmanager and it will sign it for you. Plus apk manager will let you decompile and recompile then sign so you can mod anything and it's a whole lot easier.
Sent from my Incognito Droid using Tapatalk
1. Add your JDK Directory to the Path variable (Right click on My Computer, Properties, Advanced, Environment Variables)
2. At the command prompt, navigate to the containing folder
3. keytool -genkeypair
4. jarsigner -verbose APPNAME.apk mykey
5. Push the signed app
sorry guys but im not real sure what a JDK directory is or anything. I didnt do the mod myself. i made a donation and had it done by someone on here. Once they returned it to me via email they told me to adb push it.. but i do not have any exp doing that and was hoping someone could help me out... there would be a nicely themed widgetlocker.apk in it for you haha
Different problem, same answer.
I have been trying to install a custom framework res for a while now. I am on a Mac. I simply have been changing ext to zip, unzipping, making changes, rezipping, using mv command in terminal to change to apk, and pushing to phone. It hasn't even kind of worked. Could someone please help? Are there any steps I'm missing? Do I need to sign the framework res apk?
Please help
lucas.scott said:
I had a mod done to my widgetlocker apk , but i cant adb push it. Can someone please sign it for me so i can install using root explorer? Im not sure how difficult it is , so if its insanely hard or something im sorry for asking haha . Thanks .
Click to expand...
Click to collapse
Post it or post a link to it and I'll sign it.
That said, if you modify one apk it is highly unlikely you will not modify others (which is a good thing). Therefore, I would highly recommend getting acquainted with the proper tools.
First you will need to install the Android SDK on your computer. Here is the link:
http://developer.android.com/sdk/index.html Bear in mind that to use it you will also need to install the JDK (Java Developers Kit) on your computer but the links are in the instructions so it is very easy.
In addition to the SDK download 7zip if you do not already have it. It is a free archive utility that enables opening and editing the contents of archives without extracting them.
Lastly, if you just plan on editing images download Stericson's autosign tool so that once you finish changing images you can resign the apk which is necessary to install. However, if you want to delve a little deeper into apps I highly recommend Apk Manager. Not only does it include a signing tool but can also decompile apks so that you can do deeper editing.
dkdude36 said:
I have been trying to install a custom framework res for a while now. I am on a Mac. I simply have been changing ext to zip, unzipping, making changes, rezipping, using mv command in terminal to change to apk, and pushing to phone. It hasn't even kind of worked. Could someone please help? Are there any steps I'm missing? Do I need to sign the framework res apk?
Please help
Click to expand...
Click to collapse
The framework-res.apk does not need to be resigned. In fact, there are few, if any, reasons why any system app would need to be resigned. Therefore, that should not be your issue.
That said, in the steps you listed above I see several areas which could problems so, it would be beneficial if you provided more information. Here are my initial comments:
1)When you are rezipping the apk are you recompressing the folder created when you unzipped the apk OR, are you selecting the contents of the folder (e.g. AndroidManifest.xml, res folder, etc. ) and compressing them? It is important to do it the second way I described.
2)No need to bother with the mv command as you are using it. Once you've rezipped the apk (it will likely be named Archive.zip) you will need to rename it "framework-res.apk" at which point you should only need to push the apk back to the phone. The process would go like this:
a)put modified framework-res.apk into the tools folder (located in the SDK folder)
b)open up terminal.app
c)type "cd " (without the quotes) and drag the tools folder located in the sdk folder into the terminal terminal window, and press Enter
d)type "./adb remount" (without the quotes) and press Enter
e)type "./adb push framework-res.apk /system/framework/" (without the quotes) and press Enter
f)type "./adb reboot" (without the quotes) and press Enter. (The phone will reboot which is necessary to see your changes)
g)Marvel at your accomplishment
Obviously, you should make a nandroid backup of your phone first so that in case you mess anything up you can restore it as if nothing happened.
If you have any more questions simply post them and I'd be happy to answer them. I bought and rooted my EVO the day it first came out which was before there were any Mac tutorials and have since become fluent in adb due to lots of trial and error.
could you possibly help me with my widgetlocker apk? i have adb pushed ( finally learned how to do that on mac) and it still wont install . have contacted ultralynx (he did the mod) but im not getting a response...thank you .
lucas.scott said:
could you possibly help me with my widgetlocker apk? i have adb pushed ( finally learned how to do that on mac) and it still wont install . have contacted ultralynx (he did the mod) but im not getting a response...thank you .
Click to expand...
Click to collapse
Hmmm... If ultralynx did the mod for you it is probably already signed. I've seen some of his threads and he clearly knows what he is doing. And, signing is apk-modding-101.
Where did you ./adb push the widget locker to? /system/app/ or /data/app/? Adb push does not install the apk if you push to /data/app/
My recommendation would be to do the following:
1)Using root explorer, find and delete the widgetlocker.apk from wherever you adb pushed it on your phone. Exit out of Root Explorer.
2)Reboot phone
3)Confirm that you don't have any previously installed versions of WIdget Locker on your phone. From your home screen press the menu button and navigate to Settings-->Applications-->Manage Applications-->All and look for Widget Locker. If you find it select and uninstall it.
4)Assuming the modified widget locker.apk was signed you should not need to mess with adb. You certainly can but it is not necessary and I'd hate to confuse you with the commands. So... Instead, connect the EVO to your computer and mount as disk drive. Put the widget locker.apk you want to install on your sdcard. Personally, I would recommend creating a folder named Apps and putting it in there.
5)Unmount phone as disk drive and unplug phone from computer
6) Using any file manager (Root explorer is fine) navigate to the apk on your sdcard and select install.
If that doesn't work let me know
Found problem, need answer
okolowicz said:
The framework-res.apk does not need to be resigned. In fact, there are few, if any, reasons why any system app would need to be resigned. Therefore, that should not be your issue.
That said, in the steps you listed above I see several areas which could problems so, it would be beneficial if you provided more information. Here are my initial comments:
1)When you are rezipping the apk are you recompressing the folder created when you unzipped the apk OR, are you selecting the contents of the folder (e.g. AndroidManifest.xml, res folder, etc. ) and compressing them? It is important to do it the second way I described.
2)No need to bother with the mv command as you are using it. Once you've rezipped the apk (it will likely be named Archive.zip) you will need to rename it "framework-res.apk" at which point you should only need to push the apk back to the phone. The process would go like this:
a)put modified framework-res.apk into the tools folder (located in the SDK folder)
b)open up terminal.app
c)type "cd " (without the quotes) and drag the tools folder located in the sdk folder into the terminal terminal window, and press Enter
d)type "./adb remount" (without the quotes) and press Enter
e)type "./adb push framework-res.apk /system/framework/" (without the quotes) and press Enter
f)type "./adb reboot" (without the quotes) and press Enter. (The phone will reboot which is necessary to see your changes)
g)Marvel at your accomplishment
Obviously, you should make a nandroid backup of your phone first so that in case you mess anything up you can restore it as if nothing happened.
If you have any more questions simply post them and I'd be happy to answer them. I bought and rooted my EVO the day it first came out which was before there were any Mac tutorials and have since become fluent in adb due to lots of trial and error.
Click to expand...
Click to collapse
Thanks for the help okolwoiz. I am fluent in adb and have been hacking for a while. I think I know the problem. The mod I was trying to theme (drop down notifications bar) is a .9.png, which means it is automatically resized to fit the phone. These are different than normal .png files. I know i need to use a draw9 something file in the sdk, but I don't know how. Any help would be great. Thanks
Dk
yeah i have tried all of that . It always just says "Application not installed" . No matter how i get it on the phone . ore than happy to send it to you to see if its the file or my phone .
Thanks this thread has helped me and I was just wondering through aimlessly.. And stumbled upon tis thread.
Sent from my netarchy_toast, froyo beast of a machine evo!
glad it helped someone haha
Hey all, I installed chainfire 3d to my rooted CM7 running Thunderbolt, and I was playing around with night mode and drug the sliders all the way down...
My screen is now black and I can't find a way to reset it!
Many thanks,
Logan
Tried to remove app through ADB shell, but to no avail, screen is still black after reset!!
Restore a backup? Screen should work in recovery right?
I was silly and didn't have a backup of CM7 to flash yet.
What I did was go through adb and went into system>lib> and ran the cf3d_uninstall.sh script. It rebooted the phone and fixed the issue, but every time I reinstall chainfire 3d driver through the application, the screen is black again! I tried going through manage applications>chainfire 3d>clear data, and then trying to install, but to no avail.
The color file for the nightmode are stored in /data/property/persist.cf3d.nightmode
I used that method to fix the problem
Code:
adb pull /data/property/persist.cf3d.nightmode
now edit that file and change [COLOR="Blue"]custom:0:0:0[/COLOR] to [COLOR="Blue"]custom:255:255:255[/COLOR]
adb push persist.cf3d.nightmode /data/property/
Reboot!
Done!
Sorry for bumping, but how do I access the filesystem without turning it on?
EDIT:
Have no idea how to do it on another way, but I did it. I guessed where all the buttons were (even my pin code!) and the dropdown menu and everything to be able to get access to my phone. From there on I used the post above for instructions. Thanks a LOT!
Fox-Warrior said:
The color file for the nightmode are stored in /data/property/persist.cf3d.nightmode
I used that method to fix the problem
Code:
adb pull /data/property/persist.cf3d.nightmode
now edit that file and change [COLOR="Blue"]custom:0:0:0[/COLOR] to [COLOR="Blue"]custom:255:255:255[/COLOR]
adb push persist.cf3d.nightmode /data/property/
Reboot!
Done!
Click to expand...
Click to collapse
Old post, but saved my day nevertheless. Thanks!!!
HELP
Fox-Warrior said:
The color file for the nightmode are stored in /data/property/persist.cf3d.nightmode
I used that method to fix the problem
Code:
adb pull /data/property/persist.cf3d.nightmode
now edit that file and change [COLOR="Blue"]custom:0:0:0[/COLOR] to [COLOR="Blue"]custom:255:255:255[/COLOR]
adb push persist.cf3d.nightmode /data/property/
Reboot!
Done!
Click to expand...
Click to collapse
I have the same problem, but this didn't seem to work!!! I wanna use my phone
Alternative
Cheechoy said:
I have the same problem, but this didn't seem to work!!! I wanna use my phone
Click to expand...
Click to collapse
*NOTE: USB Debugging must be enabled and your Android Device plugged in to your PC
1. Install QtADB for windows with the binary files (PC) ( please google it, this is my first post and xda won't allow new users to embed links )
2. Extract to desktop
3. Open QtADB ( it will ask for the binary files that you've downloaded)
4. After locating the folder, it will open the program. On the sidebar click Files ( it will show two columns )
5. On the right side click the data folder
6. open property and search for the persist.cf3d.nightmode
7. select that file and press F8 ( or right-click then delete it)
8. Reboot your phone and wait for it to load.
It should work without any problem. That's it! Hope that helps.
Help Me guys plz..
PLz help guys.....I got same problem...!!! plz help me guys...
Above method ADB pull & Push Doesn't seem to help me it says remote file does not exist..
I can do any thing...Can play music but the color of my screen is gone black...
plz help me bro...
Fox-Warrior said:
The color file for the nightmode are stored in /data/property/persist.cf3d.nightmode
I used that method to fix the problem
Code:
adb pull /data/property/persist.cf3d.nightmode
now edit that file and change [COLOR="Blue"]custom:0:0:0[/COLOR] to [COLOR="Blue"]custom:255:255:255[/COLOR]
adb push persist.cf3d.nightmode /data/property/
Reboot!
Done!
Click to expand...
Click to collapse
hi
I did the same as said but stuck at boot-screen please help me...
hello .....I have the same problem ..... I do if I have enabled debugging mode to activate it somehow or perform a hard reset
Chainfire created an automated uninstall script that is put in /system/lib when you install the driver(s)
Just use adb and execute
Code:
su
./system/lib/cf3d_uninstall.sh
Permissions are already set for execution!
Cheers.
Its not a repost guys. I created this thred only for quick view for new android users.
1. You must have java runtime enviornment installed on your computer.
2. You must have a rooted froyo or gingerbread firmware.
3. When we use xultimate 2.2 we must have our phone into USB debugging mode.
4. First u do xutimate procedure as kkrazzy has said.
-Run option 1. After option 1 is done, run option 2.
-Now these well take a while. Run option 3.
-IMPORTANT: After you have run option 3
-Now run option 4, and wait.
-Exit xUltimate, and put the phone in USB mass storage.
-Go back into the xUltimate folder and copy "done_frame", and "done_app",
and move them to the root of the internal sdcard not in the external sd.
-Now again connect phone into usb debugging mode.
5. I suggest that if anybody dont have SDK on their system then dont worry. Insted of SDK simply use adb.exe file which is in the superoneclick folder.
Go into SuperOneClick-->ADB folder. There u will get adb.exe file.
6. Take that whole adb folder & copy it to C drive path (U can keep it anywhere) including other files inside that folder.
Means u will get path of adb file as C:\adb\adb.exe
7. Now enter into command promp.
8. There u will see a path like C:\document and settings> (This path may be different for someone else. Thats not important)
9. This is very impotant step. Simply write there as
cd C:\adb\
Then in next line write adb shell.
You will see a msg on screen demon started successfully.
10. Thats it. You have entered into adb command mode.
11. Now remember by default # sign is always there at start of each line when u enter into adb command mode. Dont write it again in any command command...!!!
12. Now one by one run command
$ su
# stop
# mount -o remount rw /system
# rm /system/app/*.odex
# rm /system/framework/*.odex
# cp /sdcard/done_app/* /system/app/
# cp /sdcard/done_frame/* /system/framework/
# mount -o remount ro /system
# reboot
13. You will observe that after writing second command # stop your device will get hang. It will not at all respond. If that happens then u r going in right direction. Phone will hang till end of command.
14. Last command # reboot will restar ur device. But sometimes it will not. U will see a msg on computer screen as reboot returned. Dont worry. Simply Disconnect & restart phone.
15. Thats it guys. U will get a deodexed phone.
16. To check whether it is deodexed or not simply go into system->app folder. There u will see only .apk files. U will not at all observe .odex files there.
THIS IS SIMPLEST WAY I HAVE EXPLAINED. HOPE NOW NO ONE WILL FACE DIFFICULTIES IN DEODEXING.
PRESS THANKS IF THIS IS HELPFUL FOR YOU
Good job! But about XXKB3 fw you are wrong. Deodexing can be with any fw. We need only rooted phone
what the problem with the cmd???
i dont know why my cmd cant run ><
not recognized as an internal or external command, operable program or batch file
....
Dude why you have made a similar thread
falex007 said:
Good job! But about XXKB3 fw you are wrong. Deodexing can be with any fw. We need only rooted phone
Click to expand...
Click to collapse
Yep thats right, better update your post vishal.
please dont post similar threads..
updated post
vishal24387 said:
updated post
Click to expand...
Click to collapse
Thanx buddy for your valuable explanation..
Tbh, this does have what kkrraazzyy's thread lacked
Misledz said:
Tbh, this does have what kkrraazzyy's thread lacked
Click to expand...
Click to collapse
Sure yes! It is a lot more simpler for noobs ( like me ) to understand....I did it through kkrraaxxyy's post...But it helped ma friend thouhg
kkrraazzyy said:
Dude why you have made a similar thread
Click to expand...
Click to collapse
sorry kkrazy. I dont wanted to post this as saperate thread. Actually I wanted to post this in ur thread but I thought people will feel difficult to find a particular post through lots of pages. Hope u will understand my intention.
dude, thanks for the info about the adb.exe.. never thought of that before.. i went through hell downloading the needed files when yet there was a simple method.. thanks alot.! Liked the OP bdw..
ephraim033 said:
dude, thanks for the info about the adb.exe.. never thought of that before.. i went through hell downloading the needed files when yet there was a simple method.. thanks alot.! Liked the OP bdw..
Click to expand...
Click to collapse
Its my pleasre to help u. Actually I was also facing problem related to adb.exe. I also dont like to download big files. what about OP bro? I dont understand.
vishal24387 said:
Its my pleasre to help u. Actually I was also facing problem related to adb.exe. I also dont like to download big files. what about OP bro? I dont understand.
Click to expand...
Click to collapse
OP means original post bro.. .. i already pressed the thanks button
Oh...I really dont know about OP. Anyway thanx bro for telling me.
vishal24387 said:
Oh...I really dont know about OP. Anyway thanx bro for telling me.
Click to expand...
Click to collapse
no problem dude.. glad to help
vishal24387 said:
5. I suggest that if anybody dont have SDK on their system then dont worry. Insted of SDK simply use adb.exe file which is in the superoneclick folder.
Go into SuperOneClick-->ADB folder. there u will get adb.exe file.
6. Take that adb.exe file & keep in C drive path (U can keep it anywhere). I will tell u that make a new folder. Give it name as 'adb folder'. Then in this folder keep your adb.exe file.
Means u will get path of adb file as as C:\adb folder\adb.exe
Click to expand...
Click to collapse
Bro, i suggest you edit your post.. tell them to copy the whole adb folder not just the adb.exe.. the .exe needs the other program to work.. just my opinion.. i tried just copying the .exe but to no avail.. once i copied the whole folder it works..
ya I think u r rite bro. I will quickly update my post. Thanks bro.
vishal24387 said:
ya I think u r rite bro. I will quickly update my post. Thanks bro.
Click to expand...
Click to collapse
No problem dude
I updated post bro. Check it plz. If there is any problem in post plz inform me.
***MUNKY-TOOL***
IS AN ONBOARD ANDROID UTILITY
FEATURES
[*]Copy system.img
[*]Copy boot.img
[*]Backup efs
[*]Logcat
[*]Backup and Restore Contacts
[*]Out For A Rip
Munky-tool will locate and copy most partitions without you having to track down paths. This is convenient if you use a ROM kitchen, or just want to make a backup of your system without using custom recovery. Some devices do have weird partition names, and munky-tool will not find them. If this happens to you, run the following command in terminal emulator
Code:
ls /dev/block/platform/*/by-name
Paste the output and your device name in the comments, and I will work your device in if possible.
INSTRUCTIONS
Download zip or clone git
Place extracted munky-tool folder in system partition (must be able to set permissions)
Set permissions of munky-tool script (not the directory) to at least 775 (rwx rwx rw)
Open terminal emulator and key in 'su' for root permissions
cd to the munky-tool directory
Type ./munky-tool to execute the script and start the utility
DOWNLOAD
github
Dude once again you're creativity and hard work is paying off. Great job man
Style point for the rip bud!
Sounds very helpfull and as markbencze already replyed I gues it's working on the O+O too. Have to try it in the next days.
thx markbencze for sharing.
SaschaKH said:
Sounds very helpfull and as markbencze already replyed I gues it's working on the O+O too. Have to try it in the next days.
thx markbencze for sharing.
Click to expand...
Click to collapse
Yes. I tested it on my OPO. It went out for a rip. It will run on any device, and it will find the partitions on most.
Where's the download link dude, i'm not find download link from github ?
itsnie said:
Where's the download link dude, i'm not find download link from github ?
Click to expand...
Click to collapse
On the right side of page near the clone url, there should be a button that says download as zip.
Just realized you have to be in desktop view to see the download as zip button. I will post an additional link a little later.
Just added backup and restore contacts.
N-i-c-e!
Thank you.
I've been working on the same sort of thing, and trying to figure out how to get adb connected to the phone with debugging off, for those people (I won't use the word I'm thinking of) who don't make backups, then break the screen, or bootloop the phone. Your script makes finding the data partition trivial, but I'm still working on the "force debugging on from outside" part.
But munky is going to be part of my phone from now on.
Rukbat said:
N-i-c-e!
Thank you.
I've been working on the same sort of thing, and trying to figure out how to get adb connected to the phone with debugging off, for those people (I won't use the word I'm thinking of) who don't make backups, then break the screen, or bootloop the phone. Your script makes finding the data partition trivial, but I'm still working on the "force debugging on from outside" part.
But munky is going to be part of my phone from now on.
Click to expand...
Click to collapse
Thanks, man. Glad to hear you like it.
mike the inkman said:
***MUNKY-TOOL***
IS AN ONBOARD ANDROID UTILITY
FEATURES
[*]Copy system.img
[*]Copy boot.img
[*]Backup efs
[*]Logcat
[*]Backup and Restore Contacts
[*]Out For A Rip
Munky-tool will locate and copy most partitions without you having to track down paths. This is convenient if you use a ROM kitchen, or just want to make a backup of your system without using custom recovery. Some devices do have weird partition names, and munky-tool will not find them. If this happens to you, run the following command in terminal emulator
Code:
ls /dev/block/platform/*/by-name
Paste the output and your device name in the comments, and I will work your device in if possible.
INSTRUCTIONS
Download zip or clone git
Place extracted munky-tool folder in system partition (must be able to set permissions)
Set permissions of munky-tool script (not the directory) to at least 775 (rwx rwx rw)
Open terminal emulator and key in 'su' for root permissions
cd to the munky-tool directory
Type ./munky-tool to execute the script and start the utility
DOWNLOAD
github
Click to expand...
Click to collapse
Good Tool, do you already plan to support restore EFS? which make a full loop of running time change the EFS setting without a PC,
this can help to me to control the modem band preset selections for network testing purpose.
Azlun said:
Good Tool, do you already plan to support restore EFS? which make a full loop of running time change the EFS setting without a PC,
this can help to me to control the modem band preset selections for network testing purpose.
Click to expand...
Click to collapse
It is usually done in bootloader, but I am pretty sure I can make it work. Just need to test it before I release it. I am also going to release this as an apk soon. (Don't know how soon, but I probably won't have time for a few weeks)
An app that we can point new users to that will back up their userdata partition? Fantastic!
Rukbat said:
An app that we can point new users to that will back up their userdata partition? Fantastic!
Click to expand...
Click to collapse
Yeah, I think it will fill a need. I am going to do an APK to do the things from this script, and a corresponding GUI Linux package for APK modding, and maybe do something for Windows as I get time. In the process of moving somewhat unexpectedly, so it is taking longer than I would have liked.
Hi,
So my screen broke yesterday and I needed to check my phone for missed important calls. I know there is lots of solutions out there, but I needed a way access your screen without the installation of any software on your phone. I was lucky because my digitizer still works so I can still use the touch feature and figure out on my screen where to press . I figured i would post it, might save someone someday....
Note: Works on Android 4.0 +
You need to have have developper options enabled so this can work. So first of all, I need to enable ADB from recovery. There is lots of post on the forum and google, so I will not cover this part.
Once I had ADB enabled, I wrote a small batch file that would take a screenshot from my phone, then pull it to my pc, wait 1 sec, then restart. After I used chrome and a auto-refresh extension to refresh the image every second. I will assume that you have ADB installed and all drivers for adb working. Here it goes
1. You will need to create a batch file. Open notepad and paste this into it.
Code:
:start
adb shell screencap -p /sdcard/screen.png
adb pull /sdcard/screen.png
timeout 1
goto start
Save it as ss.txt, or whatever you like. Then go to desktop and rename ss.bat or "whatever you like.bat"
This may vary a bit if you do not have an SDcard, or if your directory is not named the same way, So change SDcard to the name of your storage folder.
Copy it to your adb directory.
2. Open a Command Prompt as Admin change directories to ADB folder. Once you are there, just type ss and the batch should start.
3. Open chrome and install an auto-refresh extension. I used this one:
HTML:
https://chrome.google.com/webstore/detail/easy-auto-refresh/aabcgdmkeabbnleenpncegpcngjpnjkc?hl=en
4.Then open your c:\ drive in chrome (type in the address bar file:///C: ). Navigate to your adb folder and open screen.png.
5. Start auto refresh on screen.png opened in chrome and set to 1 second.
Now you will have a screenshot of your phone being refreshed every second! I agree its slow, but its an easy way to get on your phone and configure other applications such as vnc or other stuff or just to get the phone number of that hot date you had last night.
Other thoughts: I your digitizer is broken, you can always just get a USB on the go adapter and plug-in a mouse and use ADB over wifi.
I guess you can also use an usb micro to hdmi adapter and plug it in to a monitor, they have them at bestbuy for 20$ if you dont want to make your life complicated.
Have Fun!
Need busybox do you not? screencap is not in my /system/xbin nor /system/bin folder
kirito9 said:
Need busybox do you not? screencap is not in my /system/xbin nor /system/bin folder
Click to expand...
Click to collapse
What phone and what rom are you using? What I read is that some vendors do not include screencap in their stock rom. ..
Steph_D said:
What phone and what rom are you using? What I read is that some vendors do not include screencap in their stock rom. ..
Click to expand...
Click to collapse
Using Blu Dash Jr D140a, stock ROM ( Gingerbread 2.3.6)
kirito9 said:
Using Blu Dash Jr D140a, stock ROM ( Gingerbread 2.3.6)
Click to expand...
Click to collapse
Should of mentionned, dosen't work with gingerbread, you need 4.0+ if i recall correctly. Maybe, if your lucky, the manufacturer may have included their version instead of screencap since it did not exist back, i would take a look in the bin folder to try to find an equivalent if not you are out of luck with this method.
Steph_D said:
Should of mentionned, dosen't work with gingerbread, you need 4.0+ if i recall correctly. Maybe, if your lucky, the manufacturer may have included their version instead of screencap since it did not exist back, i would take a look in the bin folder to try to find an equivalent if not you are out of luck with this method.
Click to expand...
Click to collapse
OP should be updated then and here's my bin folder.
kirito9 said:
OP should be updated then and here's my bin folder.
Click to expand...
Click to collapse
Ya, I don't believe it will be possible for you using this method. :/ Sorry Will update original post...
Steph_D said:
Ya, I don't believe it will be possible for you using this method. :/ Sorry Will update original post...
Click to expand...
Click to collapse
No problem, I will try on my 4.2.2 device.
EDIT: It works bro. Nice little guide of doing it manually