One thing that I have found to be very annoying is adjusting the build.prop file after making edits to the my ROM projects. Because of this I wrote a simple little script to update the build.prop to reflect changes before I build a new flashable.zip
This tool allows you to:
* rename your ROM
* change the product model /device
* update build date, build date UTC, and build incremental version
Place the file bptool in your ~/bin directory or a directory that is in your path and make sure it is executable.
Navigate to your ROM working directory system folder (ex: ~/working_directory/system) and from the terminal execute "bptool"
{
"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"
}
you can get the latest version here: https://github.com/OldSoldier/bptool
For your convenience I've attached the latest version of the script
I realize that this is not a "high volume" tool, but if anyone that has tried it has any feedback or suggestions please feel free to post and I'll see about making it better and more useful.
oldsoldier2003 said:
I realize that this is not a "high volume" tool, but if anyone that has tried it has any feedback or suggestions please feel free to post and I'll see about making it better and more useful.
Click to expand...
Click to collapse
If you could make it for OS X too that'd be awesome. I cannot test on Debian but only in Ubuntu but I really prefer OSX instead. Thanks
cascio97 said:
If you could make it for OS X too that'd be awesome. I cannot test on Debian but only in Ubuntu but I really prefer OSX instead. Thanks
Click to expand...
Click to collapse
It is a BASH script not a binary so I'm pretty sure it will run perfectly fine on OS X. It will run on Debian, RHEL, Fedora Ubuntu, or any other version of Linux that allows you to run the Bourne Again Shell (BASH).
I don't use OS X but from what I understand OS X has the Bourne Again Shell and sed so it *should* run fine (it may require minor tweaks for syntax)
oldsoldier2003 said:
It is a BASH script not a binary so I'm pretty sure it will run perfectly fine on OS X. It will run on Debian, RHEL, Fedora Ubuntu, or any other version of Linux that allows you to run the Bourne Again Shell (BASH).
I don't use OS X but from what I understand OS X has the Bourne Again Shell and sed so it *should* run fine (it may require minor tweaks for syntax)
Click to expand...
Click to collapse
It works. Sorry for not trying before leaving a comment. :crying: Thank you for your work.
updated to include the option to change productmodel / device name and fixed bug where the file was not properly updated if you run the same option more than once in a session.
v2.0 released
Cleaned up and commented code
added view prop settings option
added error handling
Related
http://www.nickbetcher.com/~nbetcher/SimpleRoot-v1.5-Linux.tar.gzHere you can find the revised version of SimpleRoot. It has somewhat major changes that blend in the combination of Wes and Eugene's findings together and separate from one another. As Wes has silently left the community for the Vibrant (as I understand it - please clarify if you want Wes) I have been unable to contact him.
Consequently I am posting revised version of SimpleRoot for the people whom are new to the community or people who want a more streamlined process that uses Eugene's Clockwork update.zip and Wes' SimpleRoot package. Using Eugene's update.zip fixes problems with gaining root access once you have flashed your ROM (SuperUser APK was apparently missing in Wes').
It's been generally accepted that SimpleRoot is fairly unnecessary once you flash the ENG nbh. There was controversy over the ENG nbh, but Eugene has disproven those opinions. For those of you who still want to use SimpleRoot, here it is.
Download: For Linux v1.5 (4shared).
Download: For Windows v1.5 (4shared).
Changes (for v1.5), they are as follows:
Switched from Wes' update.zip to Eugene's update.zip to eliminate problems gaining root access (SuperUser APK was apparently missing in Wes') after the ROM was flashed.
Changes (for v1.4.1 - WINDOWS ONLY), they are as follows:
Apparently the usb_driver package I had from the Android SDK didn't have the HTC Espresso's hardware IDs present. Added those so it will allow you to use the packaged drivers for device installation.
Added @ECHO off into rootme2.bat.
These changes do not affect the Linux package since the Linux scripts work and Linux doesn't need a special driver.
Changes (for v1.4), they are as follows:
Changed a lot of the text formatting for the Windows scripts, including fixing line feeds, quotation marks, command echoing, and grammatical changes.
Added the most recent copy of the Android SDK's Windows USB driver since users who have never installed the driver need an easier way to get it. (Especially if they are on limited broadband)
Added the USB driver as a requirement in the Windows script since it is a fairly important requirement.
{
"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"
}
Added a .sh extention to the Linux script filenames.
Added a ./ in front of "adb" in the loop.sh script so it uses the adb in the local directory of the SimpleRoot extracted archive versus erroring out in a loop (in the likely event the user doesn't have adb installed system-wide). This preserves the consistency already in the other scripts.
Packaged the Linux files into a subdirectory in the tar.gz file versus extracting the files into the current directory (which is highly irritating
).
Bumped version number to 1.4.
Added myself into the credits.
Modified the Windows Readme file to reflect the directions provided from the script.
Thanks nbetcher!
As I understand it Wes is working for both devices now, not sure though.
Quick question this worked perfect the first time but when i tried to put a rom on my sd card from clockwork it wouldnt see it when i clicked install from sd so i rebooted and i saw superuser on stock and i couldnt get back into clockwork since then and now i cant re root again it keeps saying device not found any ideas
{
"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"
}
So, this is my new project so far. I'm trying to build a tool to help all Android Wear devices with simple tasks. At the moment, this is the initial release and I'll keep it updated.
What's inside the package?
Java Application: you can run it from any platform, Windows, Mac, Linux,...
A folder called "lib" including adb,fastboot for Windows & Mac. If using Linux, you need to find your own adb and put it under "Other" folder
I'm looking forward for your feedback and suggestion. Thanks!
K thanks for this tool we want simple tool for control android touch if the touchpad is broken or damaged...
sureshsoori1 said:
K thanks for this tool we want simple tool for control android touch if the touchpad is broken or damaged...
Click to expand...
Click to collapse
Any features suggestion will be welcome I'll take more times for the next release:
Threading: not blocking main UI anymore
More fastboot & recovery functions
How about a one click unlock bootloader/root watch!? :good:
So, this is my new project so far. I'm trying to build a tool to help all Android Wear devices with simple tasks. At the moment, this is the initial release and I'll keep it updated.
What's inside the package?
Java Application: you can run it from any platform, Windows, Mac, Linux,...
A folder called "lib" including adb,fastboot for Windows & Mac. If using Linux, you need to find your own adb and put it under "Other" folder
I'm looking forward for your feedback and suggestion. Thanks![/QUOTE]
very good thank you
thank u
thank u pro......................
Hi tdiddy.2, i'm trying to enable adb over wifi on android wear. I have managed to make it work, but theres a lot of steps because you need to connect over bluetooth first. I know thats probably a way to enable adb over wifi direct over adb shell, but i dont know how to use adb shell well. Maybe you want to contribute? Thanks in advance.
Heres the link
AD Tools - Linux
Android Development Tools for Linux
{
"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"
}
Well, I just found my self needing a tool for Linux wich could help me to decompile/recompile my files (apks, dex, jars... etc) so I looked for it but had no luck. Then I said: Ok, if I need it then I'm going to do it! I has been REALLY usefull to me, I hope it can also be usefull to all of you.
Introduction
AD Tools is a very simple but usefull tool to help you with everything related to apks, dex or jars modifications. It includes every function needed: decompiling, compiling, signing... etc.
Usage
Here are some simple instructions to correctly use AD Tools:
Open AD Tools folder in Terminal and execute the 'ADTools' script.
To execute a script in terminal run this command:
Code:
./script
In our case it would be:
Code:
./ADTools
If you can't execute 'ADTools' file run this command and try again.
Code:
chmod +x ADTools
Take into account AD Tools always uses 'builded', 'decompiled', 'input' and 'signed' folders. Avoid creating more folders to do not get confused.
'input' folder to place the files wich are going to be used. Eg: an apk to be decompiled or classes.dex to be baksmalied.
All decompiled/baksmalied files are found in 'decompiled' folder.
Every builded/recomiled/smalied folder is found in 'builded' folder.
Features
Apktool
Signapk
Smali
Baksmali
Autoscanning files to avoid writting file names
Downloads
AD Tools v1.0.0
Older versions:
AD Tools - AndroidFileHost
Credits
@SuperR. I used his ROM Kitchen script as reference for AD Tools
XDA:DevDB Information
AD Tools, Tool/Utility for the Chef Central
Contributors
sebastiandg7
Version Information
Status: Beta
Created 2016-05-09
Last Updated 2016-05-09
FAQ and TIPS
PD: I want to hear you about bugs, function requests, improvements you may like... etc. The idea is to have a tool for users made by users. Hope you enjoy it.
nice tool thanks a lot , so far working good
#suggestions
1. adding work spaces and the ability to switch between them
Im using a Sony Vaio Y series VPCYB15AG
1366x768 resolution
i got just ubuntu 16 installed, nothing else
so ive followed everything on this guide http://forum.xda-developers.com/remix/remix-os/guide-remix-os-3-0-alongside-grub2-t3487578, i installed remix os using usb flash drive
i clicked remix os on the grub and this messages shows up
error: cant find command `linuxefi';
error: cant find command `initrdefi'.
Press any key to continue.....
Click to expand...
Click to collapse
and everytime i edited etc/grub.d/40_custom file, it always dissapeared on the next reboot, so i use Grub-Customizer, still no luck
any ide on what should i do now? http://imgur.com/a/yz4xs
{
"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"
}
oh great, now i just dont understand what to do anymore, im really new to linux os
You need to change "initrdefi" to "initrd" and "linuxefi" to "linux" in the grub customizer.
For future, do NOT post the same thing in multiple threads please.
Also there is a Linux Installer (Ubuntu compatible) available - in beta but I heard it works OK with Ubuntu. Check here:http://forum.xda-developers.com/showthread.php?t=3496934
Vioner said:
You need to change "initrdefi" to "initrd" and "linuxefi" to "linux" in the grub customizer.
For future, do NOT post the same thing in multiple threads please.
Also there is a Linux Installer (Ubuntu compatible) available - in beta but I heard it works OK with Ubuntu. Check here:http://forum.xda-developers.com/showthread.php?t=3496934
Click to expand...
Click to collapse
all right im sorry, i changed that, it can boot, so there is bunch of text going on, and then the
A N D R O I D [email protected] x64 text appeared
and after that, black screen, nothing happen, no cursor, what happen now?
i downloaded and use the newest version from the remix website.
ill download and try the ubuntu version, thanks for the link
umm btw, when i download the ubuntu version, what to do with .deb extension ? i mean usually is .iso. sorry, im not familiar with linux
@Ravagioli
I don't know your entire grub configuration so I can't say if black screen means problems with graphics or problem with system image or something else.
Installing with the .deb package is unlikely to help, but at least we'll know you used the installation method we know, so we might know what to expect.
I'm not experienced in Ubuntu either but installing should be as simple as opening the .deb file. Can't help with that sorry.
If installing from Ubuntu won't help, then boot Remix OS in Verbose Mode and then share your problem with logfiles here:
https://github.com/JideTechnology/Remix-OS-For-PC/wiki
The link also gives info on how to boot in Verbose Mode and post Issues on Github.
With the log files we will know more about your device and we'll have the error data indicating where the problem is.
And lastly:
Currently most effective and failproof installation method is using .exe installer made for Windows. We are working on both Linux installer and a bootable installer.
repo for Android!
Just go to the point.
Why did i make this?
Well, i don't have any laptop, so i try to find a way, to do repo sync without any laptop, and then i move the files to my PC, and then build it!
Requirements
1. Termux App
2. Internet Connection
How to Install
Manual way
- Install some binaries
Code:
apt update
apt install python2
apt install curl
apt install git
- Setup git
Please refer to here
- Install repo
Code:
mkdir ~/bin
curl [url]http://github.com/Rendyindo/repo-installer/raw/master/repo[/url] > ~/bin
curl [url]http://github.com/Rendyindo/repo-installer/raw/master/shrepo[/url] > /data/data/com.termux/files/usr/bin/repo
chmod +x ~/bin/repo
chmod +x /data/data/com.termux/files/usr/bin/repo
- Done!
Automatic way
- Download this
- Run that script on Termux via:
Code:
./installer-android.sh
The script will automatically download all binaries needed and install it.
And you are ready to go! have fun with repo!
Here are some screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note:
This is NOT for compiling! Through some binaries doesn't support at Termux, lol, and our phone will explode if it can
Credits:
- Fredrick Fornwall
- Google
RendyAK said:
repo for Android!
Click to expand...
Click to collapse
If we can't compile , there is no use of downloading GB's of data. [emoji14]
gopinaidu77 said:
If we can't compile , there is no use of downloading GB's if data. [emoji14]
Click to expand...
Click to collapse
You didn't get the main thing, huh?
This thing only for syncing! and you can move the files to your PC easily, this helps you when you have limited bandwith, and you find a free WiFi, but you didn't bring your PC
So, this help me much.
PS: Do not quote whole post plz.
RendyAK said:
You didn't get the main thing, huh?
This thing only for syncing! and you can move the files to your PC easily, this helps you when you have limited bandwith, and you find a free WiFi, but you didn't bring your PC
So, this help me much.
PS: Do not quote whole post plz.
Click to expand...
Click to collapse
Thanks,Edited my first post. :highfive:
Hi. My install seems correct and files seem present but repo command will not execute. I've tried from storage, storage/, and su. Any help?
Wow,, great work brother,, this fully helped me because i have problem to turn on my pc like a day for syncing,, but mobile not worry, love you sir
All links are dead. Could you re-share the project, please?