{
"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"
}
attached is recovery log sir
Er. Aditya said:
attached is recovery log sir
Click to expand...
Click to collapse
The error you see in recovery is one we have seen already and I don't know how to fix it or why it's broken. I think it has something to do with Windows though. It seems the config directory in the rom is not getting extracted to /tmp. When it tries to run /tmp/configure.sh it does not exist. Then it tries to get info from /tmp/config which is also not there because configure.sh was never run to create it. The problem is that the zips appear to be the same with the same contents, same updater-script contents, etc. If built on Windows it does not work. If built on Linux it works. I am not a Windows guy (for these and many other reasons lol) so I have no idea what the difference is. If you have any ideas please let me know. Has anyone built a working flashable zip on Windows using this kitchen?
SuperR. said:
sepolicy-inject is not available for windows currently. I should have removed the option for Windows, and will in the next update. Is this a feature that still needs to stick around? I am not sure if I can get it working in Windows due to the pre-compiled Linux libs in the source. I am also not sure if you can compile libsepol on Windows. If you can get this source compiled for Windows, I can add the feature
The error you see in recovery is one we have seen already and I don't know how to fix it or why it's broken. I think it has something to do with Windows though. It seems the config directory in the rom is not getting extracted to /tmp. When it tries to run /tmp/configure.sh it does not exist. Then it tries to get info from /tmp/config which is also not there because configure.sh was never run to create it. The problem is that the zips appear to be the same with the same contents, same updater-script contents, etc. If built on Windows it does not work. If built on Linux it works. I am not a Windows guy (for these and many other reasons lol) so I have no idea what the difference is. If you have any ideas please let me know. Has anyone built a working flashable zip on Windows using this kitchen?
Click to expand...
Click to collapse
U can surely remove that feature if u like hardly used ....
I am gonna make a rom on linux too and see if that flashes...u need anything to compare or check sir ?
I remember last time too i had issue for mounting when rom created on linux..let me try one now and report back
edit :\ @SuperR. dev check this screenshot
it shows mounting error still rom flashed and booted good
Er. Aditya said:
U can surely remove that feature if u like hardly used ....
I am gonna make a rom on linux too and see if that flashes...u need anything to compare or check sir ?
I remember last time too i had issue for mounting when rom created on linux..let me try one now and report back
edit :\ @SuperR. dev check this screenshot
it shows mounting error still rom flashed and booted good
Click to expand...
Click to collapse
It may have already been mounted so it gave an error. We can deal with that later since it flashed and booted. Now we need to find out what the difference is between the Linux created ROM and the Windows created ROM. Were they both created using the same kitchen version, same firmware, same procedure? The ONLY difference is Windows vs. Linux, right? If so, can you send the updater-script from both so I can compare?
Using Windows for building android is kinda looking like someone taking square wheels to a skatepark and expecting fluid motion.. [emoji23] [emoji23]
Sent from my N9515 using Tapatalk
bcrichster said:
Using Windows for building android is kinda looking like someone taking square wheels to a skatepark and expecting fluid motion.. [emoji23] [emoji23]
Sent from my N9515 using Tapatalk
Click to expand...
Click to collapse
These wheels are rolling faster each day. We will ride
SuperR. said:
These wheels are rolling faster each day. We will ride
Click to expand...
Click to collapse
Lmao. Right on! If anyone can get this right, it's You and these guys helping here @SuperR. [emoji41] Catching some air!
Sent from my N9515 using Tapatalk
SuperR. said:
It may have already been mounted so it gave an error. We can deal with that later since it flashed and booted. Now we need to find out what the difference is between the Linux created ROM and the Windows created ROM. Were they both created using the same kitchen version, same firmware, same procedure? The ONLY difference is Windows vs. Linux, right? If so, can you send the updater-script from both so I can compare?
Click to expand...
Click to collapse
yes both were created using latest kitchen 3.0.1.4 , same firmware and procedure
here are the scripts sir
SuperR. said:
v3.0.1.8
Changes:
Windows: Use 7-zip (included) to extract img files instead of Imgextractor.
Windows: Fixed missing symlinks in updater-script.
Windows: Fixed many file contexts not being set correctly.
Windows/Linux: Fixed system/SYSTEM on devices that use SYSTEM.
Linux: Do not create metadata lines for symlinks.
I think this will fix most of the flashing problems. Let me know how it goes
WINDOWS NOTE: It is important that the tools get updated. The updater should take care of it, but if you get errors that 7z is not found, go to Misc tools > Reset tools.
IMPORTANT: Start your rom fresh and extract from system.img again. Make sure you delete 00_project_files directory if you are reusing an existing project.
Click to expand...
Click to collapse
i still got the error 7 even i clean cloned kitchen sir
Er. Aditya said:
i still got the error 7 even i clean cloned kitchen sir
Click to expand...
Click to collapse
Can you send the updater-script and recovery.log?
There is still one problem I need to solve for sure... file capabilities in Windows. Currently there is a file with capabilities listed and it is checked when creating an updater-script in Windows. In the case of your ROM, it is not accurate. The only non-standard capability in your firmware is /system/bin/run-as which is correct in your updater-script. However, the rest should all be 0x0 and there are a few that are not. You could try changing them to 0x0 and zip the ROM back up.
It has also crossed my mind that there may be something strange about the zip itself in Windows. I am not sure of this at all but in my tests of kitchen v3.0.1.8 and your firmware, the updater-script comes out nearly identical in Linux and Windows with only the above mentioned capability differences. Maybe the compression level of the zip is too high or low? You could try manually zipping the ROM to find out if the zip process is causing an issue.
It seems that not a single working flashable zip has come out of this kitchen running Windows so far and I am running out of ideas about what is causing it
edit: Attached below is a modified updater-script for your firmware with the capabilities corrected
SuperR. said:
Can you send the updater-script and recovery.log?
There is still one problem I need to solve for sure... file capabilities in Windows. Currently there is a file with capabilities listed and it is checked when creating an updater-script in Windows. In the case of your ROM, it is not accurate. The only non-standard capability in your firmware is /system/bin/run-as which is correct in your updater-script. However, the rest should all be 0x0 and there are a few that are not. You could try changing them to 0x0 and zip the ROM back up.
It has also crossed my mind that there may be something strange about the zip itself in Windows. I am not sure of this at all but in my tests of kitchen v3.0.1.8 and your firmware, the updater-script comes out nearly identical in Linux and Windows with only the above mentioned capability differences. Maybe the compression level of the zip is too high or low? You could try manually zipping the ROM to find out if the zip process is causing an issue.
It seems that not a single working flashable zip has come out of this kitchen running Windows so far and I am running out of ideas about what is causing it
edit: Attached below is a modified updater-script for your firmware with the capabilities corrected
Click to expand...
Click to collapse
u have been a rock and we are so glad ur trying to get this to work sir i am attaching a working script and supeR script with recovery log
edit : the modified one again gave that error
OMJ said:
Fyi, I was able to build & successfully flash a rom via Windows kitchen on the latest update
Click to expand...
Click to collapse
Woo hoooo!!!! That is great news...but also confusing lol. Now we need to figure out why @Er. Aditya is getting this:
Code:
Checking config ...
minzip: Extracted 1 file(s)
about to run program [/tmp/configure.sh] with 1 args
run_program: execv failed: No such file or directory
OMJ said:
Fyi, I was able to build & successfully flash a rom via Windows kitchen on the latest update
Click to expand...
Click to collapse
samsung device ?
SuperR. said:
v3.0.1.9
Changes:
Windows: Fixed b key press not being recognized.
Added a Back option to the root method options.
Only allow key presses that correspond to menu options.
Fixed project name adding an extra superr_ when creating new project from the project selection menu.
Set permissions of configure.sh to 777 instead of /tmp to 755.
@Er. Aditya - This includes the change I sent you in the PM. No clue if it will work for you, but worth a try. No need to extract the system.img again if you extracted using v3.0.1.8. Just change perm types to something else and then back to set_metadata and it will update the updater-script for you.
Click to expand...
Click to collapse
sadly it still dint worked :'(
i clean cloned again so no old kitchen leftovers
SuperR. said:
Woo hoooo!!!! That is great news...but also confusing lol. Now we need to figure out why @Er. Aditya is getting this:
Code:
Checking config ...
minzip: Extracted 1 file(s)
about to run program [/tmp/configure.sh] with 1 args
run_program: execv failed: No such file or directory
Click to expand...
Click to collapse
another fyi---I was getting the same but I usually rip out the config folder & code from updater-script, no need for it on my ROMs
Er. Aditya said:
samsung device ?
Click to expand...
Click to collapse
HTC
Er. Aditya said:
sadly it still dint worked :'(
i clean cloned again so no old kitchen leftovers
Click to expand...
Click to collapse
Do ROMs flash properly when created in kitchen v2.x ? If so, I am clueless about what is going on. If not, I clearly need to change how we mount/format.
OMJ said:
another fyi---I was getting the same but I usually rip out the config folder & code from updater-script, no need for it on my ROMs
Click to expand...
Click to collapse
At least that narrows the issue down to configure.sh, unless you manually zip your ROMs. If so, then it still could be the zip process which is handled by the Python zip() module currently. I could switch this over to 7-zip in Windows if needed now that it is included anyway.
SuperR. said:
Do ROMs flash properly when created in kitchen v2.x ? If so, I am clueless about what is going on. If not, I clearly need to change how we mount/format.
At least that narrows the issue down to configure.sh, unless you manually zip your ROMs. If so, then it still could be the zip process which is handled by the Python zip() module currently.
Click to expand...
Click to collapse
i have been having issues since this config.sh has been introduced sir
Er. Aditya said:
i have been having issues since this config.sh has been introduced sir
Click to expand...
Click to collapse
That is actually good news believe it or not It means that probably the kitchen is now producing working roms in Windows...just not in your device lol. We can work on getting it working for your device too I will need to figure out if we can get configure.sh to run on your device. I will put together some small flashable zips for testing if you don't mind. They won't change anything, just print on the screen so we can see if it works.
SuperR. said:
That is actually good news believe it or not It means that probably the kitchen is now producing working roms in Windows...just not in your device lol. We can work on getting it working for your device too I will need to figure out if we can get configure.sh to run on your device. I will put together some small flashable zips for testing if you don't mind. They won't change anything, just print on the screen so we can see if it works.
Click to expand...
Click to collapse
[emoji23] [emoji23] Nice!! [emoji41] [emoji41]
Sent from my N9515 using Tapatalk
Er. Aditya said:
I am ready!
Click to expand...
Click to collapse
Here are 3 to try. I may come up with some others if they don't work. When you flash it, we want to see the by-name path on the screen and not get errors. Let me know how it goes
Related
{
"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"
}
vlt96 said:
You shouldn't try it out when you have free time, it will give you free time
Click to expand...
Click to collapse
Features
FEATURES LISTImage
Install Image Tools: Install ImageMagick and/or PIL to use my Image Tools
Convert Image: Convert any image in given directory to given extension
Resize: Batch-resizes files found in given directory with given percent or given DPIs, or resizes an APK with given DPIs
Batch Theme: Applies a theme overlay (caclulated with luminosity values) to all images found in a given directory (e.g. THEME!)
Batch Rename: Batch renames all files found in a directory with a given pattern, and renames them to given out (for porting Themes)
CopyFrom: Copies images present in directory 1 FROM directory 2 (if present in dir 2) - for themers!
OptimizeImage: Optimizes Image, so that size will be smaller
Development
Prepare Building: Installs necessary build tools
Build from Source: Builds one from many sources and even choose a device (if available)
Add Governor: Add a governor to a kernel
Install Android SDK
Install Java JDK
APK
(De)Compile
Extract/Repackage APK
Sign APK with different keys
Zipalign APK
Install APK
Optimize Images INSIDE APK
Advanced
(Bak)Smali: Lets you edit the code inside classes.dex and compile back
ODEX: ODEX a ROM
DE-ODEX: DE-ODEX a ROM
Compile to an Exe: lets you compile Python scripts to an executable for your OS
Android
Configure ADB: Connect to devices over IP, enable/disable Network ADB on connected device
Logcat
Build.Prop: Pulls Build.prop from device and let you edit it
Backup / Restore: full backup of (all optional) apps, system apps, data, shared storage
ADB File Explorer
StudioAndroid options
Clean workspace and go back to before you used this tool the first time!
Debug: Includes printing the used commands before executing and testing the latest changes
Check the log in a scrollable window with selectable text
Report a bug: Opens a reply on this XDA thread with the content of your log in it
Changelog: See what's changed!
Update: Update StudioAndroid and choose between Stable en Nightly
Restart
About: shows information about the developer, contact info, profile image, twitter etc
Click to expand...
Click to collapse
SCALED PREVIEW: (Click to see full preview)
Click to expand...
Click to collapse
Instructions
Download the latest update OR one of the stable updates
Extract in your home directory
double-click StudioUnix
Click to expand...
Click to collapse
Preparation:
Download one of the stable updates
Extract in a path without spaces (e.g. NOT in "Documents and Settings")
Double-click StudioWindows.exe
Click to expand...
Click to collapse
OR
Download and run Python
Download and run PYGTK - 32-bits
Download the latest update OR one of the stable updates
Extract in a path without spaces (e.g. NOT in "Documents and Settings")
Right-click Studio.py > Open with > Python
Click to expand...
Click to collapse
Preparation:
install python2.7: 64-bit/32-bit x86-64/i386 / 32-bit i386/PPC
Install this (GTK+ and PyGTK)
Download THIS
Run StudioUnix
Click to expand...
Click to collapse
Click to expand...
Click to collapse
[Cross-Platform] StudioAndroid [GUI]
vlt96 said:
You shouldn't try it out when you have free time, it will give you free time
Click to expand...
Click to collapse
Translate?
LINUX
First navigate to StudioAndroid directory.
Then
xgettext -k_ -kN_ -o messages.pot Studio.py
msginit
Click to expand...
Click to collapse
A new file will be created (***.po)
Open that file with PoEdit and translate the right-column
When finished, save it and rename ***.po to Studio.po and put it in StudioAndroid/lang/yourlang_YOURLANG/LC_MESSAGES
afterwards, compile it:
msgfmt Studio.po -o yourlang_YOURLANG/LC_MESSAGES/Studio.mo
Click to expand...
Click to collapse
When I update it, merge the changes using:
xgettext -k_ -kN_ -o messages.pot Studio.py
msgmerge -U Studio.po messages.pot
Click to expand...
Click to collapse
and translate the new strings in PoEdit
The file I need is yourlang_YOURLANG/LC_MESSAGES/Studio.mo, but it's handy for you and me if you also include yourlang_YOURLANG/LC_MESSAGES/Studio.po
WINDOWS
Open lang/LanguageFiles/en_US.po in a text editor
msgid indicates the original string
msgstr indicates the string you need to translate.
So translate the msgstr strings.
Afterwards, send me en_US.po renamed to yourlanguage_YOURCOUNTRY.po
Thanks!
If you cant upload files anywhere, then past the content of SA.po in Pastebin and send me the link
THanks in advance
FULL CREDITS WILL BE GIVEN
Click to expand...
Click to collapse
Info
All info is now available at Github:
Git Source
Changelog
Bugs & Feature requests
BitLy Stats
Click to expand...
Click to collapse
Credits
Ablankzin : Contributor to StudioAndroid
Popdog123: He took the MAC side of the project
vlt96: Making a game to play while waiting
KeitlG: Compiled for windows!!!
KeitlG: Helped me testing the long-awaited ReCompile Fix!
Rookie407 : He compiled this tool for windows! AWESOME! You don't have to install Python and GTK anymore!!!
Lithid-CM : He was my messias on Python in general and GTK specific. Go and give him a "THANKS!"
KeitG: Gettext translation
WilliamCharles & Lycan: Windows testers - AWESOME, THANK THE GUYS!!
Click to expand...
Click to collapse
Hey, I looked through your post, but I don't see what this tool is supposed to do. could you maybe write a description in the op?
Sent from my SGH-I777 using Tapatalk
Waddle said:
Hey, I looked through your post, but I don't see what this tool is supposed to do. could you maybe write a description in the op?
Sent from my SGH-I777 using Tapatalk
Click to expand...
Click to collapse
Hmmn I'll make a screenshot
EDIT: OK NOW?
Greets!
Incoming:
Batch APK de- recompile
Change Animation speed
Text color
IMPORTANT: Porting APK MULTI-TOOL - Wich is for Windows only ATM.
I'll include it in my tool and ask the dev to pay $10 for it (joke ofcourse)
IMPORTANT: FINISHING the "build from source option
mDroidd said:
Incoming:
Batch APK de- recompile
Change Animation speed
Text color
IMPORTANT: Porting APK MULTI-TOOL - Wich is for Windows only ATM.
I'll include it in my tool and ask the dev to pay $10 for it (joke ofcourse)
IMPORTANT: FINISHING the "build from source option
Click to expand...
Click to collapse
So is this for windows or linux?
Sent From My Mecha
nativi said:
So is this for windows or linux?
Sent From My Mecha
Click to expand...
Click to collapse
This tool will stay for linux.
APK MULTI-TOOL is a great tool, but for windows only, so I am gonna port it
APK MUlti Tool:
888 Lines in ONLY the Start script.
But I AM porting it.
Updated this tool first, V1C2A
Changelog V1C2 & V1C1
#v1c1:
[^]Added copyright
[^]Updated Animation
[^]Added second section; looks better
[^]OOPS! I added CopieFrom under the option "c" wich is already changelog!
[^]Improved other than home directory - was not working
[^]ICS Blue characters <3
[^]Added BUILD FROM SOURCE option
[^]Custom animation speed
[>]To try if this works, please go into terminal and type:
cat --help
if it tells you the manual for "cat", then you are fine.
Option D from the main menu.
#v1c2:
[^] Added more comments
[^] Newer CM source - not MIK_OS but now stock CM, wich includes newest adfad
[^] Custom WaitTime
[^] New script version
[^] Fixed some bugs
Will it work on windows
Hey! will this app work on windows? How to batch resize using this? Can this handle transperency? And will it perfectly fit to MDPI from HDPI or it will have FC's???
bhaviksatra87 said:
Hey! will this app work on windows? How to batch resize using this? Can this handle transperency? And will it perfectly fit to MDPI from HDPI or it will have FC's???
Click to expand...
Click to collapse
fc has nothing to do with size, I think...
windows, not yet. How to resize: option resize and follow on screen notifications.can handle transparency.
But no windows yet
Greets!
Hey, I was just wondering what the build from source option does. (I'm not that amazing dev so this might help). Does it compile stuff Aosp, or cm7?
Sent from my GT-I9100 using Tapatalk
Waddle said:
Hey, I was just wondering what the build from source option does. (I'm not that amazing dev so this might help). Does it compile stuff Aosp, or cm7?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
yep IT does! It can prepare your PC for building, and compile AOSP GB, ICS, oxygen, cm7, and maybe another one I forgot... Wasn't it clear? I'll as more screens
Greets!
mDroidd said:
yep IT does! It can prepare your PC for building, and compile AOSP GB, ICS, oxygen, cm7, and maybe another one I forgot... Wasn't it clear? I'll as more screens
Greets!
Click to expand...
Click to collapse
Seems cool. This will really help me out with starting an Aosp rom. Thanks
Sent from my GT-I9100 using Tapatalk
Waddle said:
Seems cool. This will really help me out with starting an Aosp rom. Thanks
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
You're welcome.happy users, that's what I am doing it for!
Today ,I made a big update, and added the option batch theme. Also made the tool git, installer file (much smaller and better), new directories support, code cleanup, and some fixes. And also, Apk multi tool is not more then a weak away from release.
Greets!
Thanks man,
This is a pretty amazing program. I looked at the script code and i am really suprised by how long it is. Nice job! As i type this, i am downloading the source code for gingerbread.
Waddle said:
Thanks man,
This is a pretty amazing program. I looked at the script code and i am really suprised by how long it is. Nice job! As i type this, i am downloading the source code for gingerbread.
Click to expand...
Click to collapse
Nice
If you want to, I can learn you how to code it. If you look at the code of the dsixda kitchen inside the scripts directory, copy that and put it in the main menu, it's as longas my script is now. That's what I wanted: ONE script
Greets!
How do I resize?
Is saying values:
I Have to put the directory?
Can you make a quickly tutorial for me? I just need to resize and then I will give credits to you also.
hyztname said:
How do I resize?
Is saying values:
I Have to put the directory?
Can you make a quickly tutorial for me? I just need to resize and then I will give credits to you also.
Click to expand...
Click to collapse
If I am right, it says
Usage: SrcDir ext DestDir perc
Source dir contains the images you want to resize
Extension should be png
DestDir is where the resized images will be put
Perc is the percentage, from HDPI to MDPI IS 66%
Hope I helped.
Greets!
mDroidd said:
If I am right, it says
Usage: SrcDir ext DestDir perc
Source dir contains the images you want to resize
Extension should be png
DestDir is where the resized images will be put
Perc is the percentage, from HDPI to MDPI IS 66%
Hope I helped.
Greets!
Click to expand...
Click to collapse
Yes it says, Usage: SrcDir ext DestDir perc
But you have to type on the Value thing I said before.
I typed:
Code:
~/src 9.png ~/src/new 36
36 is ldpi(is that right?)
And says this is not a command.
hyztname said:
Yes it says, Usage: SrcDir ext DestDir perc
But you have to type on the Value thing I said before.
I typed:
Code:
~/src 9.png ~/src/new 36
36 is ldpi(is that right?)
And says this is not a command.
Click to expand...
Click to collapse
Gimme the screen res of LDPI and Ill calculate. Never resize .9.png
Greets!
I'm not a fake.
I prefer people to reply to me and give feedback instead of thanking me!
But thanking me does show if you apreciate my works.
This Tool has been replaced by - Junohttp://forum.xda-developers.com/showthread.php?p=45990300#post45990300
Please visit the new thread!
For older Thread click the button below.
{
"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"
}
Welcome To Sony System App Editor Ver.1.1Installation
Please follow the instructions carefully, cause this is very crucial to the programs working.
Step 1
Download the following resources :
Android SDK (drawPatch9)
Java SE Runtime Environment 7 (Java)
Step 2
Go to Advanced System Properties.
It should look like this:
Go to Environment Variables, then create a new System Variable, having name JAVA_HOME and value according to the path where you have installed the JRE(7).
It should look like this:
Now after creating the JAVA_HOME variable, search for Path system variable in the System Variables list. Now this is a bit tricky. Once found click on it and then on Edit. Now if your value is ending with ";" (without quotes) then just add the path to your JRE(7) bin folder. If the ";" is not present then just add it and follow the rest of instruction as given.
It should look like this:
Now just Save it. (Just keep on clicking OK it will be done automatically.)
Step 3
Download Ver.1.1.zip.
[*] Download
[*] Size: 17.85 MB (18714229 bytes)
Now Extract the zip where ever you want in your computer.
Step 4
Open the folder in which you have extracted the files and then the res directory in it.
Now make sure that the folder looks like this -
If you want you can add your modified resource files too.Note: If you are using any other ROM or PHONE of Sony (This program might be compatible with all types of Phones and Roms though!), then you should over-write the already present resource files in the res directory with your own ROM or PHONE resource files. (This is important!)
Now open the program by executing - Sony System App Editor.bat, like this -
Then type LOADRESOURCES, and let the program install the required resources. Once done add your APK file to this program's directory and get started, cause you are all done!
It should look like this:
How to use?
Step 1
Make sure you have the original version of the system apk. (This is important cause in other situations I cannot guarantee it's working as I haven't tested it. ) Copy it to the program's main directory.
Now open the Program by executing - Sony System App Editor.bat, and type only the name of the System app.
For eg.: If you want to edit UxpNxtLockScreen.apk, then copy it to the main directory, and then by executing the program type UxpNxtLockScreen. (Notice no .apk!)
Now press Enter and let the program handle the rest.
Still it should look like this:
Now check for any errors in the Apktool output screen, if none found you are good to go or else I don't know what to do?...p)
If everything went fine it should look like this -
Step 2
Edit your APK to your carnal needs! But still make sure everything you do is syntactically correct and there are no erroneous codes.
For editing APK's go to the working folder of the program, and look for the folder that is named after the file-name of your System Apk.
It should look like this:
Now open it and start editing.
Step 3
Now assuming you have finished editing the System app, execute the main program once again - Sony System App Editor.bat.
Type the APK's file-name (no exts.) which you where editing, and press enter.
It should look like this:
Make sure everything goes right and check for any errors in the APKTOOL output screen, cause program at the current stage will still produce a build even if there is any error with apktool! (Will be solved soon.)
Now assuming you have checked everything and nothing is wrong, then you are good to go! And still it should look like this -
Step 4
Assuming that everything has been fine till now, so then you can have your APK file in the build folder of the Program's main directory.
It should look like this:
Now copy it to a place where you can create a flash-able zip out of it! :laugh:
Note: If you want to start modification of the new apk file of the same name, first delete the folder in the working directory of the previous APK's file-name. (It's important.)
Condition of it's use
Please use this program at your own risk. It has only been tested to mod UxpNxtLockScreen.apk.
This program utilizes a technique that I learned while creating my first mods, and was not able to find a perfect tutorial.
The technique this program utilizes might not be applicable for all types of System Apps.
The program is just created by me today (23/9/13), so please bear with it's simple and non-wanting UI and features.
So start using it and start modding today! - Become a World-Class Developer! (.........:laugh:...............:laugh:........)
Download Ver.1.1Please wait till this program is completely face-lifted!Credits
Apktool developer for developing such a great tool.
Google for making such a wonderful OS!
Me for making it's modification so simple! (divinemamgai)
This Tool is gonna suffer from Face-Change! So please co-operate.
@divinemamgai
Awesome.
I just edited my lockscreen using this, removed the clock(as I requested in PM)
Thanks a lot.
heatseeker_x04 said:
@divinemamgai
Awesome.
I just edited my lockscreen using this, removed the clock(as I requested in PM)
Thanks a lot.
Click to expand...
Click to collapse
Hey dude use the latest version to be sure of not getting into any trouble! :laugh:
divinemamgai said:
Hey dude use the latest version to be sure of not getting into any trouble! :laugh:
Click to expand...
Click to collapse
sure, I will download it.
hey man i try use your tool this hopefully helping me,,, thanks so far so good as i use
Encang_Rojali said:
hey man i try use your tool this hopefully helping me,,, thanks so far so good as i use
Click to expand...
Click to collapse
Welcome but please try the new Tool! As it is the better than this one.
divinemamgai said:
Welcome but please try the new Tool! As it is the better than this one.
Click to expand...
Click to collapse
where is the NEW tool? cant u share ?
Encang_Rojali said:
where is the NEW tool? cant u share ?
Click to expand...
Click to collapse
Dude see the main post of this thread and you will get it, or just search for Juno! :laugh:
Can I use this in Fedora ?
Little Zed said:
Can I use this in Fedora ?
Click to expand...
Click to collapse
I guess but I'm not sure cause there maybe some functions used in this program which might not be available in Fedora. I have developed it in Windows, so I think you can try out and tell me what happens. But as far as I'm know it my not work.
divinemamgai said:
I guess but I'm not sure cause there maybe some functions used in this program which might not be available in Fedora. I have developed it in Windows, so I think you can try out and tell me what happens. But as far as I'm know it my not work.
Click to expand...
Click to collapse
So. You mean no linux support?
Sent from my ST25i using Tapatalk 2
Little Zed said:
So. You mean no linux support?
Sent from my ST25i using Tapatalk 2
Click to expand...
Click to collapse
Dude I don't have Linux system, so I can't test, all I'm asking you is to test it and tell me if it works or not?
divinemamgai said:
Dude I don't have Linux system, so I can't test, all I'm asking you is to test it and tell me if it works or not?
Click to expand...
Click to collapse
Will surely test with WINE software on linux.
Sent from my ST25i using Tapatalk 2
OK... Thanks bro...
Sent from my Xperia U using XDA Premium 4 mobile app
Little Zed said:
Will surely test with WINE software on linux.
Sent from my ST25i using Tapatalk 2
Click to expand...
Click to collapse
And he is not saying it metaphorically.... ...
divinemamgai said:
And he is not saying it metaphorically.... ...
Click to expand...
Click to collapse
Ok then ket's port this to linux.
Sent from my ST25i using Tapatalk 2
Little Zed said:
Ok then ket's port this to linux.
Sent from my ST25i using Tapatalk 2
Click to expand...
Click to collapse
Dude just so you know I was referring to the word WINE in your previous post. , and hey can you continue this discussion in the new thread please.
This is a beautiful black and yellow theme based off of DBZ's Super Saiya Jin. I hope all you fans truly enjoy it. Theme confirmed compatible with twrp 2.5.0.0 to most recent release of 2.6.3.0
{
"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"
}
How To install
1.Navigate to Internal Storage (if you are on a 4.3 rom it will be in "sdcard0) than open your TWRP Folder
2.Create a folder inside your TWRP folder named "theme" (do not capitalize the name of this folder or it wont work)
3.Paste UI.zip in your "theme" folder and reboot your recovery
Worked perfect, and looks great :good:
kopower said:
Worked perfect, and looks great :good:
Click to expand...
Click to collapse
glad you like it bud...still accepting requests for custom themes for free
REV3NT3CH said:
glad you like it bud...still accepting requests for custom themes for free
Click to expand...
Click to collapse
I'm looking forward to the htc beats guy.
Quantumrabbit said:
I'm looking forward to the htc beats guy.
Click to expand...
Click to collapse
HTC Beats theme done...just gonna make a few preview images for it and ill have it uploaded by tonight
I installed this theme and everything worked fine, however I wanted to try your raven theme so I removed the theme from the theme folder and I'm stuck in a bootloop. The phone phone starts to boot then goes back to the white HTC screen and just keep looping that screen. I've uninstalled trwp 2.6.3 and still the same thing. I can get into bootloader as well as recovery I can flash zips and preform back ups but all with the same outcome. Any suggestion???? thanks in advance.
ghostt021 said:
I installed this theme and everything worked fine, however I wanted to try your raven theme so I removed the theme from the theme folder and I'm stuck in a bootloop. The phone phone starts to boot then goes back to the white HTC screen and just keep looping that screen. I've uninstalled trwp 2.6.3 and still the same thing. I can get into bootloader as well as recovery I can flash zips and preform back ups but all with the same outcome. Any suggestion???? thanks in advance.
Click to expand...
Click to collapse
Are you s-on? If so try fastboot flashing your ROMs boot.img. I don't think it is theme error. Did you dumlock to recovery and forget to restore boot? If so, the fastboot flash will fix it.
Reason I suggest that is I have done that a few times before I finally just s-offed
Sent from my DNA using my mind.
Uzephi said:
Are you s-on? If so try fastboot flashing your ROMs boot.img. I don't think it is theme error. Did you dumlock to recovery and forget to restore boot? If so, the fastboot flash will fix it.
Reason I suggest that is I have done that a few times before I finally just s-offed
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Yes I am s-on, I'll give that a try. Thanks
ghostt021 said:
Yes I am s-on, I'll give that a try. Thanks
Click to expand...
Click to collapse
i also agree deleting or adding a twrp theme will and should not do this...its not flashing anything at all as its just overlapping images from the ui.zip really....i do also suggest if s-on flashing the boot image of your roms kernel...the only way i se anything messing up is an accidental deletion of the wrong file...only thing that should be removed is the ui file as posted in this or my other threads
REV3NT3CH said:
i also agree deleting or adding a twrp theme will and should not do this...its not flashing anything at all as its just overlapping images from the ui.zip really....i do also suggest if s-on flashing the boot image of your roms kernel...the only way i se anything messing up is an accidental deletion of the wrong file...only thing that should be removed is the ui file as posted in this or my other threads
Click to expand...
Click to collapse
Thanks, I don't think it's the theme either been reading post of people having same problem might just be the phone. Oh well I was planning on moving on to the moto x dev anyway:good::good::good: thanks
Hey REV3NT3CH, I finally got around to playing with this TWRP theming and, if you would be so kind, I have a question or two about the process... please. I have a pretty good grasp on the methodology -but- have you gotten the "curtain" splash image to work? I have looked around and tested some but with my first attempt, I keep getting the stock TWRP splash image. Maybe this is baked in by the TeamWin folks? Also, looking into your UI.zip. are some of the images "working images" that are not explicitly used? I know that some of the themes use the dual row larger square buttons and some use the single row more rectangular ones. Thanks for the thoughts! I am still learning as I go!
rgnicholas said:
Hey REV3NT3CH, I finally got around to playing with this TWRP theming and, if you would be so kind, I have a question or two about the process... please. I have a pretty good grasp on the methodology -but- have you gotten the "curtain" splash image to work? I have looked around and tested some but with my first attempt, I keep getting the stock TWRP splash image. Maybe this is baked in by the TeamWin folks? Also, looking into your UI.zip. are some of the images "working images" that are not explicitly used? I know that some of the themes use the dual row larger square buttons and some use the single row more rectangular ones. Thanks for the thoughts! I am still learning as I go!
Click to expand...
Click to collapse
i believe the curtain image is baked in...ive tried changing it via the ui.zip and just didnt work....all other images assign itself to somewhere except the preview image (shows what the theme looks like stock)....if youd like i can look into the curtain image a little more again
With curtain image you have to decompile than replace the image and recompile. I've also tried gif animation but gifs don't work lol
I could throw you one together if you want
Sent from my ADR6425LVW using xda app-developers app
bunchies said:
With curtain image you have to decompile than replace the image and recompile. I've also tried gif animation but gifs don't work lol
I could throw you one together if you want
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
your talking about the whole recovery itself right?
REV3NT3CH said:
your talking about the whole recovery itself right?
Click to expand...
Click to collapse
yeah. you have to take the recoery image than decompile it
EDIT: im gunna build a decompile and compile script right now
bunchies said:
yeah. you have to take the recoery image than decompile it
EDIT: im gunna build a decompile and compile script right now
Click to expand...
Click to collapse
thats what i thought....anybody have requests then i may do some soon
REV3NT3CH said:
i believe the curtain image is baked in...ive tried changing it via the ui.zip and just didnt work....all other images assign itself to somewhere except the preview image (shows what the theme looks like stock)....if youd like i can look into the curtain image a little more again
Click to expand...
Click to collapse
Thanks... you to bunchies! Don't worry about it. I just hoped that was a possibility. Yet, if you find a secret to make it work in an easy fashion, let me know. I appreciate your thoughts and I hope you don't mind if I use your xml file as a template
rgnicholas said:
Thanks... you to bunchies! Don't worry about it. I just hoped that was a possibility. Yet, if you find a secret to make it work in an easy fashion, let me know. I appreciate your thoughts and I hope you don't mind if I use your xml file as a template
Click to expand...
Click to collapse
im a high believer in what is open source should stay and remain open source just as long as the credibility is there....go ahead and have fun with it bud....if you need help you can pm me or hangouts me..... [email protected]
REV3NT3CH said:
im a high believer in what is open source should stay and remain open source just as long as the credibility is there....go ahead and have fun with it bud....if you need help you can pm me or hangouts me..... [email protected]
Click to expand...
Click to collapse
exactly.. also just threw this together for ya :good: this is how i edit recovery images.
Heres the tools - http://d-h.st/xJL
extract it to your ubuntu desktop and place the recovery.img you want to edit to the base of the new recovery folder
than open terminal and..
cd Desktop/Recovery
./unmkbootimg recovery.img > output.txt
mkdir ramdisk
cd ramdisk
gunzip -c ../initramfs.cpio.gz | cpio -i
Click to expand...
Click to collapse
hit enter in the terminal to execute the last line
Do Not Exit the terminal
than use your file explorer and go into ramdisk/res/images and delete the curtain.jpg and paste in the new curtain.xxx (i use a png image)
than go back to the terminal window and..
cd ..
tools/mkbootfs ramdisk | gzip > ramdisk-new.gz
./mkbootimg --kernel zImage --ramdisk ramdisk-new.gz --cmdline "console=ttyHSL3 androidboot.hardware=vigor no_console_suspend=1" --base 0x48800000 --pagesize 2048 -o recovery-new.img
Click to expand...
Click to collapse
hit enter in the terminal to execute the last line
and than flash the recovery-new.img in fastboot :angel:
bunchies said:
exactly.. also just threw this together for ya :good: this is how i edit recovery images.
Heres the tools - http://d-h.st/xJL
extract it to your ubuntu desktop and place the recovery.img you want to edit to the base of the new recovery folder
than open terminal and..
hit enter in the terminal to execute the last line
Do Not Exit the terminal
than use your file explorer and go into ramdisk/res/images and delete the curtain.jpg and paste in the new curtain.xxx (i use a png image)
than go back to the terminal window and..
hit enter in the terminal to execute the last line
and than flash the recovery-new.img in fastboot :angel:
Click to expand...
Click to collapse
thanks will definately be doing some stuff with this
Hi,
This kernel/rom lets you connect an RT8187 USB Wifi adapter to your GT-P5210 and run aircrack-ng/airmon-ng/airodump-ng through Linux on Android.
Mind the noobness, I just compiled my first kernel(ever) and stuck it in someones image and it worked.
{
"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"
}
(worked untill i enabled the builtin wifi, lol)
After i bought one of these tablets I can't say I'm not a bit dissapointed about the amount of dev work on the GT-5210, (words go unspoken for DutchDanny, Angel_666, trevd)
It's an x86 device, anything should be compileable and runable without any arm mods (i'm looking at you kali linux) this thing should be owning the Nexus 7.
Tested with TWRP 2.7 recovery
Its built using builduntu, and from the P5210UEUAMI8 source, with the toolchain recommended in the Kernel Readme.
I followed this tutorial to enable driver support
And this detailed guide to compile the kernel and create a proper boot.img
Replaced the boot.img in Mod57's rom with my modified one. (god fed up with fastboot and usb issues on Win 8.1 and just flashed it, it worked. Thats my testing)
Mod57 said:
This is built using the Samsung GT-P5210 P5210UEUAMI8 [4.2.2] Jelly Bean base.
ORIGINAL THREAD
This is not debloated it's fat and sassy like Samsung intended it.
If you would like to debloat I highly recommend using DutchDanny's debloater which can be found here:
http://forum.xda-developers.com/showthread.php?t=2482582
Jelly Bean P5210UEUAMI8
Fully Deodexed
Rooted
BusyBox
Zipaligned
Extended Power Menu (Wanam Xposed)
Will Not Delete Internal SD
Thanks to:
DutchDanny
Angel_666
Zidkijah
and everyone else who has contributed to this device.
Download:
http://www.androidfilehost.com/?fid=23189362627838229
MD5: 79f732fefbaf7882bc7c814d3ac1e998
Click to expand...
Click to collapse
Once you have downloaded and verified Mod57's rom, open up the zip and replace boot.img with this one:
https://www.dropbox.com/s/9gfucdzsadciy66/boot.zip
MD5: 4dd95a78c78550586cf3c2f7953978ab boot.img
You must have a rooted device (I used TWRP 2.7, http://nasirtech.blogspot.dk/2014/03/root-p5210xxuanb4-android-422-stock.html)
Code:
Put the modified rom onto the sdcard
Go to recovery
Wipe Cache and dalvik-cache
Install the ROM
Reboot and enjoy
Once you have installed the kernel and it boots up, you must follow these steps to chroot into an ubuntu image and compile / install aircrack.
Code:
Download this image: ubuntu-13.10.LARGE.x86.ext2.v1.zip
from [url]http://sourceforge.net/projects/linuxonandroid/files/Ubuntu/13.10/x86/[/url]
and copy it to your sdcard
Thanks to jorgen_gustavsson for his excellent work [url]http://forum.xda-developers.com/showthread.php?t=2573441[/url]
1. Install busybox [url]https://play.google.com/store/apps/details?id=stericson.busybox[/url]
2. Install a vnc viewer [url]https://play.google.com/store/apps/details?id=android.androidVNC[/url]
3. Install [url]https://play.google.com/store/apps/details?id=com.zpwebsites.linuxonandroid[/url]
(Not sure, but open and close it once to be safe)
4. Copy bootscript.sh [url=http://forum.xda-developers.com/showthread.php?t=2573441]link to bootscript thread[/url] to /data/data/com.zpwebsites.linuxonandroid/files/ overwrite the old file.
bootscript.sh
(Thanks to xdadev: jorgen_gustavsson)
5. Unpack and Copy the ubuntu-13.10.LARGE.x86.ext2.img and .md5 to a place of your choosing on either internal or external sdcard.
6. Make a Linux on Android widget and point it to the img file you copied to your sdcard (ubuntu-13.10.LARGE.x86.ext2.v1.img).
7. Now click on the LOA widget you made in 6 and let linux ”bootup”
8. Press 'y' to check MD5 checksum
9. Connect vnc to localhost:5900 password ubuntu
Now to install Aircrack
# Libraries
sudo updatedb
sudo apt-get install build-essential
sudo apt-get install gcc
sudo apt-get install zlibg-dev
sudo apt-get install libssl-dev (or libssl-dev depending on your distribution)
#airolib-ng optional sqlite=true
sudo apt-get install libsqlite3-devel
#libnl optional libnl=true
sudo apt-get install libnl-genl-3-dev libnl-3-dev
#Required Extras
sudo apt-get install wireless-tools
sudo apt-get install net-tools
sudo apt-get install wicd-curses (or wicd-cli)
sudo apt-get install usbutils
sudo apt-get install wpasupplicant
sudo apt-get install dbus
# Download & unpack (or replace link with latest trunk)
wget [url]http://download.aircrack-ng.org/aircrack-ng-1.2-beta3.tar.gz[/url]
tar -zxvf aircrack-ng-1.2-beta3.tar.gz
cd aircrack-ng-1.2-beta3
# Make
sudo make libnl=false sqlite=false
sudo make install libnl=false sqlite=false
# or
make libnl=true;make libnl=true install
make install libnl=true;make libnl=true install
# or Airolib-ng support
make sqlite=true;make sqlite=true install
make install sqlite=true;make sqlite=true install
# Add binaries to path
export PATH=$PATH:/usr/local/sbin
# add the above line to below file for include path on startup
vim /home/ubuntu/.bashrc
# Update MAC OUI
airodump-ng-oui-update
Reboot and disable your internal wifi, connect your dongle, and get cracking.
This is what I spent my easter (and then some) doing, I hope someone can make good use of it. I can
Maybe someone can come along and add bcmon for the bcm4334 chipset
(Just maybe https://code.google.com/p/bcmon/source/browse/trunk/bcm4330/driver/src/bcmdhd/Kconfig?r=4 )
Any feedback and questions are welcome:
why didn't you use the latest source? -couldn't find it
Will this kernel work with xx rom? -probably not
Why aren't more roms including this? -dno, its in the menuconfig, should be easy
I've tried to give thanks where ever possible, let me know if you feel left out.
Ill come back tomorrow and clean up my post.
Best Regards
You my dear friend are a LEGEND
I'm also yoing to build an own kernel... And I think I'll add this feature too...
Sent from my GT-P5210 using Tapatalk
Keep having error while compiling kernel :"(
Daniel-TAz00 said:
Once you have downloaded and verified Mod57's rom
Click to expand...
Click to collapse
Thank your for your work. This is what I've been looking a long time for.
Please, would you provide a flashable zip of the rom with your kernel? It looks like I'm doing something wrong.
After flashing the modified rom my P5210 just keeps showing the wird boot logo and wont boot up at all.
Thanks in regard!
@Max4000 Do you realize that what Daniel-TAz00 original article is about!
He is showing us a way to run Aircrack-ng in a Ubuntu VNC session with our TAB3 wifi turned off but with a external USB WIFI Dongle!!!!.
He also suggest it will be nice if somebody, created the modification on our own TAB3 10.1 driver sources and compiled it in a new kernel. It was just a suggestion. Then a few commented but no buddy gave the final answer.
I did not follow his steps. I do not even understood why he start with a new TAB3 rom! And a new boot.img. I guess he gave that as a reference as how he did it.
@Jacker31 What is what you are trying to compile, your sources and steps? And what is the exact error?
This is an interested topic to me. But I been sick for more than a week.
r2d23cpo said:
@Max4000 Do you realize that what Daniel-TAz00 original article is about!
He is showing us a way to run Aircrack-ng in a Ubuntu VNC session with our TAB3 wifi turned off but with a external USB WIFI Dongle!!!!.
He also suggest it will be nice if somebody, created the modification on our own TAB3 10.1 driver sources and compiled it in a new kernel. It was just a suggestion. Then a few commented but no buddy gave the final answer.
I did not follow his steps. I do not even understood why he start with a new TAB3 rom! And a new boot.img. I guess he gave that as a reference as how he did it.
@Jacker31 What is what you are trying to compile, your sources and steps? And what is the exact error?
This is an interested topic to me. But I been sick for more than a week.
Click to expand...
Click to collapse
Well it have been a long story, I posted a thread about my error, here : http://forum.xda-developers.com/general/help/question-error-2-error-compiling-x86-t3047439 but in the end i found out i used the wrong toolchain. So i redownloaded the correct version and try again. It works but another error popup, its about some Broadcom error. I can successfully compile it after i disabled it in menuconfig. But instead of getting a Zimage i got a Bzimage. So Idk what to do with it. I googled a tones of information but still have no idea what to do with that bzimage. I used Kali Linux to compile and those kernel files are from http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=p5220 GT-P5220_SEA_KK_Opensource. Now i am trying to install builduntu and try to compile it again. Any tips or helps? especially with that bzimage
Daniel-TAz00 said:
Hi,
This kernel/rom lets you connect an RT8187 USB Wifi adapter to your GT-P5210 and run aircrack-ng/airmon-ng/airodump-ng through Linux on Android.
[...]
Once you have downloaded and verified Mod57's rom, open up the zip and replace boot.img with this one:
https://www.dropbox.com/s/9gfucdzsadciy66/boot.zip
MD5: 4dd95a78c78550586cf3c2f7953978ab boot.img
Click to expand...
Click to collapse
r2d23cpo said:
@Max4000 Do you realize that what Daniel-TAz00 original article is about!
He is showing us a way to run Aircrack-ng in a Ubuntu VNC session with our TAB3 wifi turned off but with a external USB WIFI Dongle!!!!.
He also suggest it will be nice if somebody, created the modification on our own TAB3 10.1 driver sources and compiled it in a new kernel. It was just a suggestion. Then a few commented but no buddy gave the final answer.
I did not follow his steps. I do not even understood why he start with a new TAB3 rom! And a new boot.img. I guess he gave that as a reference as how he did it.
Click to expand...
Click to collapse
I get it. He offers a kernel and tells to place it in an flashable zip of an other firmware.
This is not a new firmware, it's just a kernel.
Maybe someone can create a flashable zip of the kernel he has linked to. So I would try to flash it separately.
Max4000 said:
Maybe someone can create a flashable zip of the kernel he has linked to. So I would try to flash it separately.
Click to expand...
Click to collapse
I'll upload a complete zip for you, it's just gonna take a little while ....
OHH BOY!
This is Daniel-TAz00 thread, so he know what he is finally offering you when he said.
Daniel-TAz00 said:
I'll upload a complete zip for you, it's just gonna take a little while ....
Click to expand...
Click to collapse
Now what will be this "complete zip" he is offering! I hope is your desired kernel.
Max4000 said:
I get it. He offers a kernel and tells to place it in an flashable zip of an other firmware.
This is not a new firmware, it's just a kernel...
Click to expand...
Click to collapse
Max4000 In your quote
This kernel/rom lets you connect an RT8187 USB Wifi adapter to your GT-P5210 and run aircrack-ng/airmon-ng/airodump-ng through Linux on Android.
Click to expand...
Click to collapse
You are just looking in "This kernel/rom" at the beginning. While I am trying to tell you to look at the end "through Linux on Android."
So yes that kernel may have the "external RT8187 USB Wifi adapter driver" but in order to run "aircrack-ng/airmon-ng/airodump-ng" you need to run it through Linux....
Clearly the best approach is to use our internal wifi and some how run "aircrack-ng/airmon-ng/airodump-ng" without the need of "Linux" chrooted on Android.
@ Jacker31 I answered in your thread
http://forum.xda-developers.com/showpost.php?p=59310924&postcount=2
Here: https://www.dropbox.com/s/q27inuf6jmnhvdm/P5210UEUAMI8-Custom.zip?dl=0 942MB
It's what has been running on my tablet since I made the topic. If your tablet turns into a magic mushroom, it wasnt my fault
@r2d23cpo Thanks it was helpful for that Android Kitchen part How do you create a flashable .zip out of boot.img? I am thinking of using philz to create a custom rom backup and replace the boot.img with the one i modded.
@ Jacker31 I answered in your thread
http://forum.xda-developers.com/show...24&postcount=2
Click to expand...
Click to collapse
@Daniel-TAz00 Do you just edit the zimage or you even edited ur ramdisk? Eg: copy .ko modules into lib/modules/?
Jacker31 said:
@r2d23cpo Thanks it was helpful for that Android Kitchen part How do you create a flashable .zip out of boot.img? I am thinking of using philz to create a custom rom backup and replace the boot.img with the one i modded.
Click to expand...
Click to collapse
I did it with 7zip, open zip, replace boot.img, save zip, flash zip
Jacker31 said:
[MENTION=5688554]r2d23cpo[/MENTION
@Daniel-TAz00 Do you just edit the zimage or you even edited ur ramdisk? Eg: copy .ko modules into lib/modules/?
Click to expand...
Click to collapse
I compiled my zimage, and that was pretty much it i think
@Daniel-TAz00 Didn't expect was that easy XD just 7zip haha, gotta try it out after my dinner XD hope it works. I will post it if it works with p5220 since your post is for p5210. I have to agree with you that there is really rare to see Galaxy tab 3 10.1 series (00, 10 or 20(LTE)) development going, guess maybe there is limited advanced users on tab 3 10.1 series.
Is it possible to make a update.zip? If so how?
Daniel-TAz00 said:
Here: https://www.dropbox.com/s/q27inuf6jmnhvdm/P5210UEUAMI8-Custom.zip?dl=0 942MB...
Click to expand...
Click to collapse
@Daniel-TAz00 First thanks. Nice work. But can you tell us if your "942MB" file is just the same
This kernel/rom lets you connect an RT8187 USB Wifi adapter to your GT-P5210 and run aircrack-ng/airmon-ng/airodump-ng through Linux on Android.
Click to expand...
Click to collapse
In particular it is VNC Linux on Android
Now I think @Jacker31 is here for the fun of learning kernel compile and finding a way to implement "aircrack-ng/airmon-ng/airodump-ng" with TAB3 10.1 own Wifi and without Linux VNC. That is what I guess from his post.
Jacker31 said:
... it was helpful for that Android Kitchen part...
Click to expand...
Click to collapse
Thanks goes to the Greatest creator @osm0sis. Last time he complains on me for saying it was another Kitchen. So NOOOO It is the best Kitchen in xda. I know all this nice applications get hidden on so many post. @moonbutt74 was the one to point me to use AIK.
Jacker31 said:
... How do you create a flashable .zip out of boot.img? I am thinking of using philz to create a custom rom backup and replace the boot.img with the one i modded. ...
Click to expand...
Click to collapse
I will answer down
Jacker31 said:
... Do you just edit the zimage or you even edited ur ramdisk? Eg: copy .ko modules into lib/modules/?
Click to expand...
Click to collapse
You see Jacker31 is trying to include the needed driver in a kernel. But that is only a step.
So, which modules Tab3 10.1 own wifi? If so you need to recall that first we need to modify our driver bcmdhd to allow promiscuous communication!
Jacker31 said:
@Daniel-TAz00 Didn't expect was that easy XD just 7zip haha, gotta try it out after my dinner XD hope it works. I will post it if it works with p5220 since your post is for p5210. I have to agree with you that there is really rare to see Galaxy tab 3 10.1 series (00, 10 or 20(LTE)) development going, guess maybe there is limited advanced users on tab 3 10.1 series.
Click to expand...
Click to collapse
So I guess once you read this is going to be late, I was going you suggest to backup your own boot.img first! I do still you are a bit confuse it is not just ZIP!! see below
Code:
dd if=/dev/block/mmcblk0p10 of=/sdcard/mmcblk0p10.img bs=4096
Jacker31 said:
Is it possible to make a update.zip? If so how?
Click to expand...
Click to collapse
Yes, you see it is not just zip. In fact you need to make your own update.zip.
@Jacker31
1) So here is what you need to read. In this forum just search for "Edify", "updater script" and see how the script is build.
2) Please keep in mind that every device is different, in particular the partitions are in different places and in our case we are nor ARM but x86 or more technical we belong to the i686 family.
So if you unpack recovery.img an look inside the ramdiskfs you can find "/etc/recovery.fstab". By doing "cat /etc/recovery.fstab"
you will see
Code:
# mount point fstype device [device2]
/config ext4 /dev/block/mmcblk0p3
/cache ext4 /dev/block/mmcblk0p6
/system ext4 /dev/block/mmcblk0p8
/data ext4 /dev/block/mmcblk0p9 length=-16384
/recovery emmc /dev/block/mmcblk0p11
/boot emmc /dev/block/mmcblk0p10
/external_sd vfat /dev/block/mmcblk1p1
This tells you that "boot" is at partition "/dev/block/mmcblk0p10" and "recovery" at "/dev/block/mmcblk0p11".
So a valid script to introduce your new boot.img may read
Code:
ui_print("+++++++++++++++++++++++");
ui_print(" Galaxy Tab 3 gt-p52xx ");
ui_print("+++++++++++++++++++++++");
#
ui_print("Flashing boot.img");
ui_print("+++++++++++++++++++++");
#
#
package_extract_file("[COLOR="Blue"]boot.img[/COLOR]", "[COLOR="Blue"]/dev/block/mmcblk0p10[/COLOR]");
#
ui_print("Done");
ui_print("+++++++++++++++++++++");
Now I am attaching a update.zip skeleton. The needed part is in "update.zip\META-INF\com\google\android". There you will find "update-binary" valid for our x86 device. Observe how it is about 521KB. The ARM one is just around 125KB! Easily to distinguish. This "update-binary" is the program that will interpret the Edify commands that are store in "updater-script". So the "updater-script" holds the instructions.
In it you will find also "update.zip\META-INF\com\android". With "metadata" holds signature information when signed. And "otacert" with in fact holds the signature for ota validation. This files are only required when the update.zip is signed!! But that another process meant for distribution that I am not going to explain. In general when we test we do not sign the updtate.zip instead we disable that in the recovery menu, so that recovery accepts update.zip packages that are not signed. So I had include those for you knowledge but you can delete them if you want.
So the last file is "update.zip\boot.img". This is the file you are going to substitute and that you want to program.
And yes making the package is as simple of zipping all. Here is the important detail. When you zip the file you need to be in the same directory as the boot.img file is. So that the update.zip created do not contain an extra folder. In other words, when you double click a good update.zip you find quickly boot.img and META-INF folder. No extra folders.
Now waitttttt. That is just for your general knowledge. If you do use this info it is at your own risk. It is easily to do something wrong and break the device.
Example, Make sure you have a FULL battery before doing any firmware programing. The Charging mechanism is in boot image. If you have a bad boot image programing, then your device will not charge and if you get out of juice then you end up with a nonchargeable devices. It will feel that the device is dead, since you only way to charge will be to open the device and charge the battery separately!!!
OHHHH BOYY.
Now I am confuse! I guess it is my fault in assuming and not waiting for answers!
I guess Master Jacker31 was in fact into the Linux, he just release How to run Kali Linux on Galaxy Tab 3 10.1 => http://forum.xda-developers.com/gal...-to-run-kali-linux-galaxy-tab-3-10-1-t3050203
In any case I hope that my last post in update.zip is useful to him and others.
r2d23cpo said:
OHHHH BOYY.
Now I am confuse! I guess it is my fault in assuming and not waiting for answers!
I guess Master Jacker31 was in fact into the Linux, he just release How to run Kali Linux on Galaxy Tab 3 10.1 => http://forum.xda-developers.com/gal...-to-run-kali-linux-galaxy-tab-3-10-1-t3050203
In any case I hope that my last post in update.zip is useful to him and others.
Click to expand...
Click to collapse
@r2d23cpo
thanks for that answer, i am akinda into the linux, but there is plentyof stuff to get confused because of this x86 device and limited support from google. You are right, thats what i am going to research next, implement aircrack into the device it self and trying to find out that i can use the usb wifi dongle without turn off the build in wifi. Maybe you can surf facebook while attacking your neighbor network *joking* *its illegal anyways*
Well, Everything work well (I meant the script, I made some minor changes), except got stuck on that samsung Galaxy Tab 3 logo screen... I am trying to figure out why... I am trying to get a stock Boot.img and compile it again, since I used boot.img from philz back up...ANNNNNNNNNNNNND great bricked my device... not the first time though.
Jacker31 said:
Well, Everything work well, except got stuck on that samsung Galaxy Tab 3 logo screen... I am trying to figure out why...
Click to expand...
Click to collapse
I've got still the same problem.
This is a Windows Batch Script/Tool to make any 4.4 based ROM to full F2FS compatibility !! This tool can convert any existing ROM from ext4 to Full F2FS Compatibility in a few clicks !! All tools necessary for conversion included in the batch file itself !!
Basic Info
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
What is All-F2FS?
We used F2FS only for /data. It was simply because we have only to flash a compatible Kernel and Format /data partition. With All-F2FS we use F2FS for all partitions and we need a compatible ROM
DISCLAIMER
Code:
*I am Not responsible for any bricked devices,SD cards or thermonuclear attacks.
*Please do some research about what you are doing before you use the tool.
*YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Current Device Compatibility
Code:
1. Nexus 4 ( Mako )
2. Nexus 7 2012 Edition ( Grouper)
3.Nexus 5 (HammerHead)
Prerequisites
Code:
1. A Hammerhead
2. Any 4.4 based ROM with [B][U]busybox [/U][/B]installed
3. Proper F2FS Compatible Recovery and Partition Zip from
[url]http://forum.xda-developers.com/google-nexus-5/orig-development/recovery-twrp-2-7-0-0-f2fs-support-t2746030[/url]
4. Any Windows version and my batch script
Features
Code:
1. One Click F2FS Conversion Process
2. All tools included in the Zip file itself
3. Changes only the relevant parts of your updater-script keeping the rest unmodified
4. Compatible boot.img included in the ROM itself
5. Now Scripts are Device Specific
6. Error conditions at many places so a noob cant go wrong
***Special note for CM /CM based ROM users***
Code:
I dont test the script since I dont own an HH !! This is the CM kernel by @kdh2834
If it does not work kindly post the detailed error on the thread . Will try my best to resolve it
***Special note for Stock ROM users***
Code:
The script requires busybox and since stock roms dont have busybox the repacked ROM wont boot up.
In such a case the best option is try out any other AOSP based ROM/or a Stock ROM with busdybox installed
Instructions
Code:
[LIST=1]
[*] Unpack the Zip file you downloaded from Link Below to a folder named F2FSROMConvetor (Dont Mess with the name).
[*] Take Care that the path you extract my Zip for eg in my case "C:\Users\Nabendu\Desktop\F2FSROMConvetor"
does not contain any blank spaces in between or else the script will not work as intended.
[*] Run F2FS Convertor.bat
[*] Select your device
[*] Place the Zip in the Extract /Input directory when prompted
[*] The script will Unpack your ROM
[*] Select option of boot.img based on your rom
[*] Repack your ROM
[*] A black window will open showing the Repacking progress. Dont close my Blue Window anytime during it the repacking process.
After 100% repacking is done the Black Window will close automatically and you can now press any key to Continue
[*] Check NEW F2FS ROM directory for the Repacked ROM
[*] Flash and Enjoy
[*] Cleanup the working directory cleanup.bat (Cleans everything including original input ROM.Only a copy of the Output ROM is maintained)
[/LIST]
***FAQ's***
Q. I get errors compiling the ROM on my XYZ Windows Version?
A. Read through my steps once again especially point 1 & 2. Hopefully u can get it to work.
If you think you are doing everything correctly post it on the thread and Ill try to reply within 24Hrs.
Q. I want to do it on Linux !! Why you no create bash scripts ?
A. Im not good at bash scripting !! Also dont own a Linux Distro so cant help you guys !! But look here @jolinnard has a script for Linux users
https://github.com/figue/f2fs-scripts/blob/master/convert_ROM_to_f2fs.sh and make necessary changes for Hammerhead updater script if any
Q. I can do the same with the Convert to F2FS apk on the Playstore ?
A. Sure you can. Converting on mobile is easier also. But only reservation is that it is paid.Not everyone can afford it.
Also time permitting Ill create a Android Terminal Script based on jolinnards script for Linux.
Q. Do you think I can convert it myself ?
A. Yes its just clicks . Read my steps and do it you wont go wrong.
Download Links
1. V1.1 OLD
2.V1.2 NEW
Changelog
Code:
V1.0 Intial Release
V1.1 : Add Device Support
1) Added Device Compatibility : Nexus 5
2) Scripts now will come seperate for each device.
3) Did some cleaning up on my messy script
V1.1 : Add more Boot.imgs for N5
Credits
Code:
@legolas93 For bringing F2FS to Nexus and also for providing the boot.img for the script
[user=4439521]@mikaole[/user] For the German Translations and extensive testing
[user=2002216]@jolinnard[/user] For the amazing F2FS kernels he is providing
[user=4544860]@osm0sis[/user] For his amazing Android Image Kitchen.The cleanup.bat script is taken from his tool.
[user=3325155]@fishears[/user] For helping out on the kernel side.
[user=5501864]@USBhost[/user] For being the lone tester for the N7 ( 2012 )
[user=4450732]@CallMeAldy[/user] For the CM trick and his compilation thread
[user=4851200]@Rohit02[/user] For being the beta tester
[user=14325584]@kdh2834[/user] For his AOSP Kernel
And all other beta testers !! Sorry if I forgot anyone from the list !!
Screenshots in the Next Post
Hit the Thanks button if you Like My Work
Screenies
Screenies atlast
{
"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"
}
Excellent test on
Big thanks
c-rom v6.4 Network Connectivity fail
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
belictony said:
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
Click to expand...
Click to collapse
I dont own a HH so not much I can help you with !! But try flashing a different kernel on top of it , think it should work !! And does c rom used the aosp kernel in the first place !! Look at the thread for modified Kernels , i guess flashing one should solve your problem !!
belictony said:
I converted c-rom v6.4 using the boot.img supplied with the script and network connectivity fails. Mobile networks doesnt open when tapped. No mobile network connectivty.
Click to expand...
Click to collapse
If C-rom is based on Cyanogen (CAF) then the stock F2FS boot.img (AOSP) that NABENDU1 provide inside his tool will not work with your rom.
c-rom is aosp based.
micr0g said:
If C-rom is based on Cyanogen (CAF) then the stock F2FS boot.img that NABENDU1 provide inside his tool (AOSP) will not work with your rom.
Click to expand...
Click to collapse
C-Rom is aosp based. Even c-rom v6.2 compiled by developer:callmeandy gives com.android.process.phone force closed. I also tried editing lines in updater-script and no change. Same problem prevailed.
hi ... but after this mod... if i update the rom i must repack again???????????? @NABENDU1
belictony said:
C-Rom is aosp based. Even c-rom v6.2 compiled by developer:callmeandy gives com.android.process.phone force closed. I also tried editing lines in updater-script and no change. Same problem prevailed.
Click to expand...
Click to collapse
Okay you have the com.androidprocess phone fc problem right !! If its only that Ill patch the kernel myself and get you a new one in a few mins and rest assured it will work for sure !!
rabbo3 said:
hi ... but after this mod... if i update the rom i must repack again???????????? @NABENDU1
Click to expand...
Click to collapse
Yup what kind of Rom u use !! If it has differential update like Mokee OS or xdelta ( I dont know xdelta/opendelta in detail ) like Omni I can create some kind of allied script for it too !! Put the same question in the N7 2012/N4 but dint get any responses for it mosly due to devs still use the traditional way !! Anyways if anyone wants patching for those im up for the task !!
EDIT: Version 1.2 for HH online ( Bigger Size due to 4 boot.imgs included in the script itself)
Dl Link : https://mega.co.nz/#!dxcVmQRS!5zv6RCqJs82rv5-aW3GqICW5YgCPuZtUhiH0F1vpVP8
Changelog:
Added CM boot.img ( Untested by me ) thx to @kdh2834
Added Purity boot.img ( Untested by me) thx to @kdh2834
Added AOSP com.android process phone fc boot.img ( Untested by me) thx to @me
Kindly post feedback on the thread !!
I will fix the screenies sometime later or tomm
I've used this tool to successfully switch over to f2fs-all with crDroid (a CM based rom). My biggest problem, however, is that I am completely unable to flash elementalx afterward because it freezes on boot. Anybody found a way to fix this?
Edit, I'm an idiot. I found out I have to manually mount /system before flashing ElementalX
fantastic job, works great with cm11-m6,very faster
Great!
Thanks! Working great using omnirom, tested with elementalx and bricked kernels.
tavocabe said:
Thanks! Working great using omnirom, tested with elementalx and bricked kernels.
Click to expand...
Click to collapse
Glad to hear everything works fine !! But im kindoff disappointed at the response for the thread !! I am thinking it this way "that a calm thread means everything is working as intended and no ones having any issues so far" !! But atleast some responses is needed to keep the thread in the right direction and im open to any suggestions about new features or stuff you guys want this ugly script to perform !!
My plans for the future for this tool would be
1) A Mobile Version of the Tool ( A bash script for the Mobile)
2) OTA/XDelta Updater-script changes
NABENDU1 said:
Glad to hear everything works fine !! But im kindoff disappointed at the response for the thread !! I am thinking it this way "that a calm thread means everything is working as intended and no ones having any issues so far" !! But atleast some responses is needed to keep the thread in the right direction and im open to any suggestions about new features or stuff you guys want this ugly script to perform !!
My plans for the future for this tool would be
1) A Mobile Version of the Tool ( A bash script for the Mobile)
2) OTA/XDelta Updater-script changes
Click to expand...
Click to collapse
Sorry to ask what might be a stupid question, but could this work for a ROM for a different phone (I have a Moto G)?
I would be using the CM11 version for my phone of course. : http://forum.xda-developers.com/showthread.php?t=2624111
Great work, and thanks!
callidus_ex_de_latebros said:
Sorry to ask what might be a stupid question, but could this work for a ROM for a different phone (I have a Moto G)?
I would be using the CM11 version for my phone of course. : http://forum.xda-developers.com/showthread.php?t=2624111
Great work, and thanks!
Click to expand...
Click to collapse
Moto G is infact already has /data partition in F2FS file format !! The only thing is making the cache and system full f2fs !! For this firstly your kernel dev should take a initiative to create a fully compatible f2fs kernel and also a f2fs recovery !! Once that is done I would be more than glad to help you guys out !! Anyways till then enjoy f2fs on /data !!
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Волк said:
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Click to expand...
Click to collapse
Works fine on my crDroid setup. Did it work for you before with Euroskank? Have you tried toggling from MTP to PTP and back? If you have a secure screen lock in place, are you ensuring that you have unlocked the phone after plugging it in? Are you waiting to plug the phone in until after it's booted up? Just trying to rule out the obvious troubleshooting steps
Sent from my Nexus 5 using Tapatalk
work in 4.4.3?
Волк said:
Used this to convert Euroskank CM 5/31 version, but MTP won't work. Has anyone else had this issue with other ROMs?
Click to expand...
Click to collapse
It works for me using omni-elementalx.
danielalonso said:
work in 4.4.3?
Click to expand...
Click to collapse
Yes
To @NABENDU1
Hi, so far everything is good, only complain is that most of the times when I reboot to recovery and flash any update to rom/kernel or when I add a new rom using multirom (tested and working good with omni, slim and paranoid), when finished and reboot the phone I see the boot screen many times. Like a bootloop but eventually it makes it to the rom or the multirom menu to select a rom. Is this because of my configuration of f2fs with multirom or maybe the kernel I use (elementalx shared with all the roms)?
@NABENDU1 thank you very much for this, it's quick and easy as well as educational (to me)