Related
As an experiment I am trying to rebuild some standard android applications and replace them in system/app on the G1. I have been through all the steps to get the source code and build for the dream platform and have built the various .apk files of interest (e.g. AlarmClock.apk, Browser.apk etc)
To put the files on the device I delete the old .apk and .odex files and copy my newly built .apk file on to the device. However when I try to run the application it crashes with the following message.
The application Alarm Clock (process com.android.alarmclock) has stopped unexpectedly. Please try again.
I know that replacing the applications like this is possible, because the AutoRotating Browser build works fine when copies over in this manner.
I'm using JF1.31 (RC8)
My initial reaction was that I was not signing the applications properly but having read some posts I think the default built .apk should have the right key already in it.
Another theory I have is that perhaps the applications from the head of the source tree are not compatible with the RC8 (or RC30) Android OS releases. Can anyone tell me how to get the source tree which corresponds to this baseline, I've done some reading around but cannot figure it out. I presume I need to do a repo init -u git://android.git.kernel.org/platofrm/manifest.git -b BASELINE but I can't figure out what BASELINE should be.
Many thanks in advance for any help you can give me!!!
There are some branches in android sources:
master
cupcake
release-1.0
Apps from the first two will not run on default G1, you need to reinstall a whole system. I think by default, following google docs you'll get master. So you need to download a release-1.0 sources.
I may be wrong, but that is what I'm see from my experience.
Thanks for that, I'll get the 1.0 branch downloaded and have a go with that.
Cheers for your help!
I was also trying to recompile some of the built-in apps, specifically the browser, but I can't even get it to build. I get a bunch of import errors, stating that it can't find some of the android libraries, such as android.net.http.AndroidHttpClient, android.os.AsyncTask, etc. I've got the android.jar from the SDK in my build path, and it finds some of them, such as android.webkit.URLUtil.
Can anyone shed some light on what I need to do to get it to see the missing libraries? Thanks.
UndeadCretin said:
Thanks for that, I'll get the 1.0 branch downloaded and have a go with that.
Cheers for your help!
Click to expand...
Click to collapse
There are around a dozen build breaks in release-1.0... all of them are due to missing header #includes in various .c and .h files. So, when it doesn't work, don't give up. Fix the breaks and everything will build properly.
Are you resigning the .apk files? Cuz you have to do that for them to work correctly.
Koush said:
There are around a dozen build breaks in release-1.0... all of them are due to missing header #includes in various .c and .h files. So, when it doesn't work, don't give up. Fix the breaks and everything will build properly.
Click to expand...
Click to collapse
Yep I fixed these problems but I have now hit upon the following problem:
(unknown): error 17: Field android.hardware.SensorManager.LIGHT_NO_MOON has changed value from 0.0010f to 0.001f
******************************
You have tried to change the API from what has been previously released in
an SDK. Please fix the errors listed above.
******************************
I've been in and modified SensorManager back to 0.0010f and that let me build get further but I hit the same error again later in the build.
Given that release-1.0 should be a stable branch is it normal to get all these build issues?
Managed to fix the java issue by modifying public_api.xml. Then hit several more C++ problems which I fixed and finally I can build the lot!
Just tried building the AlarmClock application and running on the G1 and it works fine. Thanks everyone for your help!
>Managed to fix the java issue by modifying public_api.xml. Then hit several more C++ problems which I fixed and finally I can build the lot!
Can you write, what did you fix?
^ Agreed, let us know which files need modifying and what needs doing, i've been trying to get my release-1.0 build root working too!
Alternatively, UndeadCretin, could you build the firmware (release-1.0) with a modified framework-res i can send you?
Ok, I managed to compile it without any editing of xml.
Just added stdlib, string, vector headers to dozen of cpp/h.
worry said:
>Managed to fix the java issue by modifying public_api.xml. Then hit several more C++ problems which I fixed and finally I can build the lot!
Can you write, what did you fix?
Click to expand...
Click to collapse
To fix the java issue, I modified frameworks/base/core/java/android/hardware/SensorManager to change the LIGHT_NO_MOON value to 0.0010f (from 0.001f) and in out/target/common/obj/PACKAGING I modified the <field name="LIGHT_NO_MOON" to have value-"0.0010f">
After this there were several other c++ files which were missing relevant includes. I'm afraid I didn't keep a note of these so cannot provide much detail but mostly they were missing one of the following
#include "stdlib.h"
#include "string.h"
#include "stdio.h"
I think one file needed the following include
#include <string>
and there were a couple of other files that needed other includes. The best way to find these is to google for the function name that isn't building and you should be able to find the appropriate include (that's how I did it).
Hope that helps a bit!
were you able to repo sync after adding the local_manifest.xml?
ximonx said:
were you able to repo sync after adding the local_manifest.xml?
Click to expand...
Click to collapse
I did try that previously but it didn't work. I don't think the relevant files for the dream build are available in the release-1.0 branch. This wasn't a problem for me since I'm only interested in building the applications which work fine with the generic build.
I would like to do the same for the mms application. Could you give me the steps or a link how to do it? I mean do I need the whole sources from android platform to do it? How can I just compile one application?
Phlogiston said:
I would like to do the same for the mms application. Could you give me the steps or a link how to do it? I mean do I need the whole sources from android platform to do it? How can I just compile one application?
Click to expand...
Click to collapse
I downloaded the whole Android source (the release-1.0 branch) and compiled the lot. It may be possible to just build the individual application but I do not know how. It is not vital to build for the dream platform if you only care about the applications since they will work fine with the generic build.
So the basic steps to start are:
Get yourself a Linux or Mac OS platform (I use Ubuntu running in VMWare on my XP box).
Follow the instructions here: http://source.android.com/download but when you come to repo init add the flag -b release-1.0
Fix various build problems
When recompiling individual apps to replace system apps is there a way of just building a single application or does the entire thing need making?
ximonx said:
When recompiling individual apps to replace system apps is there a way of just building a single application or does the entire thing need making?
Click to expand...
Click to collapse
My experience is that you have to do the whole thing if you are building from source. There is one way I know of to get around this, which is to use baksmali and smali.
Just to be clear, making the entire thing = build from source root?
ximonx said:
Just to be clear, making the entire thing = build from source root?
Click to expand...
Click to collapse
If you are asking me--yes, that's what I mean. Make sure to build for dream-open as the target (it's generic by default).
About
Android has being used in almost all type of devices from tiny smart watches to tablets , smart TVs and portable eboards like mk802 . It seems a complete operating system in term of games and useful applications but sth whichI think is a huge problem is that Android has very small parts of GNU, this makes Android not to be comfortable for advanced users , developers and programmers . also this would be a huge problem for users like me who do not access to their PCs but they want to have some capabilities in their phone . all this reasons made me to think about porting softwares from PC to my tiny Galaxy S Plus . but I had no PC and this was my huge problem in this road. finally I could get a small compiler and start porting more bigger softwares then I decided to make a project called GNU softwares on Android and gather all softwares under one project.
Click to expand...
Click to collapse
Features / list of Softwares
all softwares are :
* Fully compiled with GCC 4.8.1/4.8.2 with Hardware floating point abi for better performance even comparing to similar smaller ones in busybox !
* Staticly linked with Musl Libc which is a lot more faster than Android's bionic or GNU's glibc with smaller size which makes them be small a lot more.
* Updated to latest ones in official repositories.
list of available softwares in my repository :
-bash -> a shell
-dash (not official GNU software but licenced under GPL) -> a shell
-patch -> generating patch files
-pexec -> parralel executing
-sed -> non-interactive stream editor
-grep -> finding patterns in files/streams
-gzip -> gnu z77 compressions algorithm implementation
-make -> makefile handler for creating automated build systems
-tar -> gnu tar archive software
-inet-utils -> utils for working with net (some utils of thid software has not been included)
-gawk -> gnu awk implementation
-marst -> algorithm 2 c convertor
-wget -> downloading files trough many protocols with proxy support
-units -> convert many units to each other
Click to expand...
Click to collapse
Downloading & Installation
All softwares are stored in my public repository HERE
* For installing get softwares from their forlder in the repository , then unzip them and copy binaries to /system/xbin .
* For net related softwares there is also a reslov.conf which should be pushed to /etc/
Click to expand...
Click to collapse
Changelog
--------15/02/2014:
*gzip: added new utilities and updated to R2.
*gzip: added new documentations to public repository.
*dash: disabled builtin printf to let ROM's printf be used instead.
---------14/02/2014
*initial release.
Click to expand...
Click to collapse
Disclaimer
We distribute softwares in the hope that it will be useful, but without any warranty. No author or distributor of this software accepts responsibility to anyone for the consequences of using it or for whether it serves any particular purpose or works at all, unless they say so in writing. This is exactly the same warranty that proprietary software companies offer: none
Click to expand...
Click to collapse
Help the project
maintaining a project with 2 millon lines of a code on a mobile is too difficult. this makes compiling large softwares like gcc impossible so I strongly need a donated VPS/dedicated server.
Click to expand...
Click to collapse
.........................
reserved
Awesome Job alireza7991! Hope this project is successful in the future.
Great will try this
Sent from my Nexus 5 using Tapatalk
Edit : because of busyboy installed in system/xbin, so I have to put the binaries in system/bin. and what can I say, ITS WORKING GREAT!
aLNG said:
Great will try this
Sent from my Nexus 5 using Tapatalk
Edit : because of busyboy installed in system/xbin, so I have to put the binaries in system/bin. and what can I say, ITS WORKING GREAT!
Click to expand...
Click to collapse
Most GNU softwares has no similar ones in busybox software set. so you should not worry about conflicting issues.
I've tried to push this file to xbin grep, patch, sed, tar and wget, but I got this : destination file exists. Enter new name. (These files from busybox)
So, what I have to do? Should I overwrite the file?
Sent from my LT15i using Tapatalk
eimoc said:
I've tried to push this file to xbin grep, patch, sed, tar and wget, but I got this : destination file exists. Enter new name. (These files from busybox)
So, what I have to do? Should I overwrite the file?
Sent from my LT15i using Tapatalk
Click to expand...
Click to collapse
1- rename files to another thing , e.g. patch -> gnu.patch
or
2- remove busybox ones(/system/xbin/*) and replace GNU ones . It's completely safe .
don't forget to push resolv.conf to /etc/ for wget.
Project status update.
2 new softwares added (inetutils + dash).
OP updated for more information.
alireza7991 said:
1- rename files to another thing , e.g. patch -> gnu.patch
or
2- remove busybox ones(/system/xbin/*) and replace GNU ones . It's completely safe .
don't forget to push resolv.conf to /etc/ for wget.
Click to expand...
Click to collapse
When I pushed resolving.conf to system/etc, I'm also getting the msg that the same file name exist.
Is there any suggestions? Tq
Sent from my LT15i using Tapatalk
eimoc said:
When I pushed resolving.conf to system/etc, I'm also getting the msg that the same file name exist.
Is there any suggestions? Tq
Sent from my LT15i using Tapatalk
Click to expand...
Click to collapse
no , I think you understood my post incorrectly;
do this steps :
1- Copy GNU softwares to /system/xbin/ and replace them with busybox ones.
2- If you are installing a wget or inet-utils then also copy resolv.conf to /system/etc
Project updated;
see OP for changelog and check repository for latest binaries and documentations.
alireza7991 said:
no , I think you understood my post incorrectly;
do this steps :
1- Copy GNU softwares to /system/xbin/ and replace them with busybox ones.
2- If you are installing a wget or inet-utils then also copy resolv.conf to /system/etc
Click to expand...
Click to collapse
Thanks for the explanations. Now its working great
Sent from my LT15i using Tapatalk
Project's files has been moved to a new powerful server with 1 GB RAM which is about 3X faster than pervious server.
please use this url to get files in new server:
http://afn7991.tk/goa
Hi alireza7991,
I'm new to all this and I'm interested in trying it out. Does this work on Samsung Galaxy Note II LTE? And if it does, do I need to download all the files and use it on my device? :/
RayySP said:
Hi alireza7991,
I'm new to all this and I'm interested in trying it out. Does this work on Samsung Galaxy Note II LTE? And if it does, do I need to download all the files and use it on my device? :/
Click to expand...
Click to collapse
Hi
1- It works on almost all devices with linux kernel and an ARM processor.
2- no, This is like Google play, you have a set of softwares available and you can install any softwares you want.
alireza7991 said:
Hi
1- It works on almost all devices with linux kernel and an ARM processor.
2- no, This is like Google play, you have a set of softwares available and you can install any softwares you want.
Click to expand...
Click to collapse
Thanks for the help mate.
P.S: I'm not to sure which software to select as I'm not used to all this stuff.
testing
testing right now on my mokee kk build ...
will feed back.
RayySP said:
Thanks for the help mate.
P.S: I'm not to sure which software to select as I'm not used to all this stuff.
Click to expand...
Click to collapse
I 've made a small description in OP but you can also search trough google. they are well documented. also I put some documentation in folder of each software.
alireza7991 said:
I 've made a small description in OP but you can also search trough google. they are well documented. also I put some documentation in folder of each software.
Click to expand...
Click to collapse
Alright sure. Will do that later on. I'm sorry if I bother you too much. :/ And Thanks for the help alireza7991. Cheers!
kewl its working....
how about nano or vim? is it possible?
btw i already have wget installed, i think it come from busybox
https://github.com/JackpotClavin/Android-Blob-Utility
The purpose of this program is to help AOSP-based ROM developers quickly and easily find out which proprietary blobs need to be copied into the ROM's build, or built using source. How the program works is you do a /system dump into a folder on a Linux computer. Then you make the program using the 'make' command; then you can run it.
First off, the program will ask you what the sdk version of the /system dump you pulled happens to be. For example, if your /system dump is Android 4.3, and intend port a 4.3-based ROM, then enter 18 and press enter.
When it prompts you for location of the /system dump you pulled, if the location of the build.prop of the /system dump is under:
Code:
/home/user/backup/dump/system/build.prop
then just use:
Code:
/home/user/backup/dump/system
The program will now ask you for your device's manufacturer's name, and the device's name. For my Verizon LG G2, I entered "lge" and "vs980" respectively.
The utility then will ask you how many files you wish to run through the program. In the case of my LG G2, the KitKat build requires two main proprietary camera-related libraries to run (/system/bin/mm-qcamera-daemon and
/system/lib/hw/camera.msm8974.so).
So I typed in 2 and pressed enter (because I'm running two proprietary files through the program)
Then simply typed in:
Code:
/home/user/backup/dump/system/bin/mm-qcamera-daemon
and pressed enter and it printed out *every* file needed to get /system/bin/mm-qcamera-daemon running (the file might be proprietary, or it can be built from source).
Then it asked for the final proprietary file, so I simply typed in:
Code:
/home/user/backup/dump/system/lib/hw/camera.msm8974.so
and pressed enter and it printed out *every* file needed to get /system/lib/hw/camera.msm8974.so running (the file might be proprietary, or it can be built from source).
An example usage of this program can be found here: https://raw.githubusercontent.com/JackpotClavin/Android-Blob-Utility/master/Example_Usage.txt
That's 106 proprietary blobs done in a flash!
The beauty of this program is that it's recursive, so if proprietary file 'A' needs proprietary file 'B' to run, but proprietary file 'B' needs proprietary file 'C' to run, which in turn needs 'D' to run, then simply entering proprietary file A to run will print out all A, B, C, and D nicely formatted so that you can simply copy the output and place it in a file under vendor/manufacturer/codename/codename-vendor-blobs.mk file in your AOSP build source tree's root.
Another great thing about this program is that it doesn't just catch the libraries needed to satisfy the linker, but rather, it will also print out those libraries that are called within the actual code of the library itself, like:
Code:
dlopen("libfoo.so", RTLD_NOW);
libfoo.so is not marked as a shared library, so the linker won't complain that libfoo.so is missing, and there might be no sign that libfoo.so missing and needed, but when it's time for the daemon or library to run, it won't show any sign that something is wrong, until you see that it doesn't work. This program will catch and display that libfoo.so is needed.
So basically:
1. Extract /system dump image
2. Tell program the SDK version of your /system dump
3. Tell program the location of your /system dump
4. Tell the program your device's manufacturer's name
5. Tell the program your device's codename
6. Tell program how many files you wish to run through the utility
7. Tell program the location of the file(s) you wish to run through the program.
8. Copy the output of the utility to a text file under vendor/manufacturer/codename/codename-vendor-blobs.mk
reserve
Hi,
I'm a noob and don't worry about my silly question.
I'm trying to build my first cm-rom and tested your tool. Thanks a lot for your work, it worked for me.
I'm a little bit curios about your point 5. Where can I find all the files I need for my own source-tree/device?
It would be nice if you can give me a hint.
Thanks a lot and greetings from germany
Greetings from the US
Do you mean the device folder the ROM? You can look at similar devices to your device and see what they did and make the changes to build Android.
This is the device folder for the Nexus 5 -> https://android.googlesource.com/device/lge/hammerhead
This tool is under-recognized. I think it's a really great way to find which blobs are dependencies!
Codename13 said:
This tool is under-recognized. I think it's a really great way to find which blobs are dependencies!
Click to expand...
Click to collapse
Thanks! Are you developing a ROM? Let me know if it helps!
Sent from my LG-VS980 using XDA Free mobile app
Could this be updated to Lolipop?
2GigayteSD said:
Could this be updated to Lolipop?
Click to expand...
Click to collapse
What do you mean? I added support for SDK version 20 if that's what you're asking.
Sent from my LG-VS980 using XDA Free mobile app
Does that mean I can port AOSP to any device just by getting all the necessary blobs? I'm not sure but I'm trying to port Lollipop to my device but I don't really have a clue how to do it/what's needed to do it. Will this be useful for me? Thanks.
cikoleko said:
Does that mean I can port AOSP to any device just by getting all the necessary blobs? I'm not sure but I'm trying to port Lollipop to my device but I don't really have a clue how to do it/what's needed to do it. Will this be useful for me? Thanks.
Click to expand...
Click to collapse
It helps with making ROMs for devices that don't have support (either the model is brand new or the device never gained AOSP ROM support for whatever reason)
Basically, in the early stages of porting ROMs, certain things won't work (graphics, camera, radio) and this is mostly due to not having the correct proprietary files needed for the OS to interact with the hardware. The proprietary files have dependencies (they rely on other libraries, which in turn may rely on other libraries, and so on and so forth until all proprietary libraries are satisfied).
In the case of my LG G2, there were a total of 92 proprietary files that needed to be pushed to the device in order to get just camera working. Instead of pushing one library at a time and getting a logcat or strace dump of what the daemons are calling or depend on, I wrote this program to recursively search for all proprietary libraries needed to satisfy a proprietary library (or in the case of the camera for my G2, there were two proprietary libraries needed that required those said 90 other proprietary blobs).
So rather than pushing libraries, (then gathering logs and stracing) and hoping that the one you just pushed is the one that will get your camera, radio, etc to work, you run your known proprietary daemons or libraries through this program and it will print out the necessary libraries to get it working, in a fraction of a second
Can you go through the actual "porting" process because from what I understand you have done it? If I'm correct to port a ROM you need to have working ROM from other device? If yes, does that device have to be same manufacturer? Lets say I do have working AOSPA kitkat for my device so I need to get AOSPA lollipop and exchange the certain files and then I'll able to run it? Once again if it's like that then I use your tool and get necessary blobs? I don't have a clue about this stuff, I only build ROMs but now time has come that my device is unsupported so can you give me some tips, thanks.
This is interesting. Going to have to try this out tomorrow.
cikoleko said:
Can you go through the actual "porting" process because from what I understand you have done it? If I'm correct to port a ROM you need to have working ROM from other device? If yes, does that device have to be same manufacturer? Lets say I do have working AOSPA kitkat for my device so I need to get AOSPA lollipop and exchange the certain files and then I'll able to run it? Once again if it's like that then I use your tool and get necessary blobs? I don't have a clue about this stuff, I only build ROMs but now time has come that my device is unsupported so can you give me some tips, thanks.
Click to expand...
Click to collapse
If you don't have a clue then dont do it, please! Work your way up. First step in this hypothetical is to wait for aospa 5.0
Thanks a lot for this tool
just one thing.. i cant get the blobs for my wireless (wl12xx)
Rest all done
andynoob said:
Thanks a lot for this tool
just one thing.. i cant get the blobs for my wireless (wl12xx)
Rest all done
Click to expand...
Click to collapse
Is it possible that each wl12xx library only relies on AOSP libraries (has no dependencies?)
See if they can be built from source!
Sent from my LG-VS980 using XDA Free mobile app
JackpotClavin said:
Is it possible that each wl12xx library only relies on AOSP libraries (has no dependencies?)
See if they can be built from source!
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
Manufacturer hasnt provided the source code(Kernel) . Anyways thanks a lot for this tool :good: :good:
how to use it?
by reading the detailed instructions?
Sent from my LG-VS980 using XDA Free mobile app
JackpotClavin said:
by reading the detailed instructions?
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
should we adb pull /system first?
*edit
I did it! but where is the directory out?
J,
You are a life saver ! Subscribed. Will add link of thread to my signature. Will dance happily for some hours! :good:
Will seek therapy. :silly:
m
UAPM is an advanced tool designed for advanced users. UAPM is the only application
universally thought, addition to being the safest, never use shell to manage the
system partitions of your device.
Please, see all screenshots here to get a better sense of application.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this APP
* before installing it! 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.
*
* THIS APPLICATION WAS NOT MADE FOR BEGINNERS, IF YOU ARE A BEGINNER, USE ANOTHER APPLICATION
* FOR EXAMPLE RASHR OR FLASHIFY, THE MAIN OBJECTIVE OF THIS SOFTWARE IS MANAGING ALL PARTITIONS
* AND NOT JUST BOOT AND RECOVERY! AND YES, THIS APPLICATION USES THE GLORIOUS DD BINARY...
* THE REST OF THE SAME SOFTWARE CATEGORY!
*
*/
Features
Flash and Backup partitions.
Generate MD5 built-in partition.
Check MD5 of your files easily.
Get outputs processes with logging.
Set block size for writing partitions.
Quick Power Menu.
Auto reboot after flash.
Requirements
Any device running Android 4.1.2+
Device with root and busybox.
Partition layout of your device.
Changelog
Release v1.41 - CURRENT
Fixed critical issue on Flash.
Click to expand...
Click to collapse
Release v1.0
Initial release
Click to expand...
Click to collapse
Release v1.1
Added Strings (if you are willing to translate this, PM me)
Little change in method to create folders on the /sdcard to avoid I/O errors
Added option to clean logs:fingers-crossed:
Click to expand...
Click to collapse
Release v1.2
Implemented new logs messages for easy outputs indetification
Added Power menu feature(If you have a hardware problem or simply a quick option):fingers-crossed:
Added Auto Reboot feature(To save your time, now an optional to auto restart after flash):fingers-crossed:
Small fix on Strings(Wrong Strings:angel
Cleaned/Optimized code:good:
Click to expand...
Click to collapse
Release v1.21
Removed unused resources(Some unused .png and .db files):silly:
Fix Hardcoded Strings(Missing strings)
Enabled ZipAlign and ProGuard(Minify) for this build:fingers-crossed:
Fixed SharedPreferences commit issues:good:
Click to expand...
Click to collapse
Release v1.22
Optimized template.
Click to expand...
Click to collapse
Release v1.3
Now the application search for root at startup and not before operations.
Reduced the number of calls in operations.
Reduced the number of operations after the Runtime.exec call.
Added new logs to better error identification.
Added MD5 verification in your files.
Fixed runtime errors!
New dialogs to identify the exact exception.
Click to expand...
Click to collapse
Release v1.4 - CURRENT
Reduced the number of calls BufferredWrite() on Logger()
Now the BufferredWrite() is called only if input is valid.
Improved the accuracy of controls, now the result
comes from OnPostExecute() and not the catch block in AsyncTask.
Added the feature "Command Preferences", you can now
configure the write block size to increase performance.
Small FIX to delete the logs. Prior to erase written
log a new file was not created causing problems.
Implemented new md5sum algorithm, Now this is same to TWRP md5 checking!
Click to expand...
Click to collapse
Get it on DOWNLOAD page.
XDA:DevDB Information
UAPM, App for all devices (see above for details)
Contributors
ferreirawax
Version Information
Status: Stable
Created 2014-12-18
Last Updated 2015-01-07
Before you upgrade to v1.4, uninstall the previous version and delete the UAPM folder to not create problems!
To use MD5 is very easy, just put in the same directory the file with the md5
hash of the same name of the file you will use to flash, for example, Your file
is called "mypartition-12-15-15.img", The hash must be named "mypartition-12-15-15.img.md5".
The contents of the hash is like this:
Code:
63221739e3a5624583a31391a63b361c mypartition-12-15-15.img
Code:
This is MD5 hash This is file name
Recalling that the backups made using UAPM already have MD5 hash. It is not necessary
to have a md5 hash to flash using UAPM, but it is highly advisable.
I think the power of it scares alot of us lol. But great job!!
xsteven77x said:
I think the power of it scares alot of us lol. But great job!!
Click to expand...
Click to collapse
Thanks for the feedback! UAPM is a "Intelligent GUI" for those who frequently use the binary "dd", Using carefully certainly not will bring problems
Uh, sounds great! Must try.
Nice App
Very Useful
New release guys, Checkout changelog! :fingers-crossed:
Oooh yay! I have been trying to repartition my Find5 but couldnt get it to work so I put that project on ice a few days ago.
With this it might work!
Gonna try it tomorrow and will let you know how it goes.
Sent from my FIND7 using XDA Free mobile app
I got "error while phase package"…
Ps. I'm on ICS 4.0.3
Sorry for my bad English...
Sent from my HTC Desire 200 using XDA Premium 4 Mobile app
Maybe a simple reason for error.
ferreirawax said:
Requirements
Any device running Android 4.1.2+
Click to expand...
Click to collapse
dicks93277 said:
I got "error while phase package"…
Ps. I'm on ICS 4.0.3
Click to expand...
Click to collapse
Requirements state Android 4.1.2+ so that could be reason.
Interesting app. for that
dicks93277 said:
I got "error while phase package"…
Ps. I'm on ICS 4.0.3
Sorry for my bad English...
Sent from my HTC Desire 200 using XDA Premium 4 Mobile app
Click to expand...
Click to collapse
Later I've the possibility to work on 4.0+.
New update guys, with new features!
ferreirawax said:
Later I've the possibility to work on 4.0+.
Click to expand...
Click to collapse
Still not working…
Sorry for my bad English...
Sent from my HTC Desire 200 using XDA Premium 4 Mobile app
dicks93277 said:
Still not working…
Sorry for my bad English...
Sent from my HTC Desire 200 using XDA Premium 4 Mobile app
Click to expand...
Click to collapse
Currently only 4.1.2 or higher is supported, I am thinking of the possibility to support 4.0+.
New small update guys! To avoid losing the pace
New update v1.22
Hi @ferreirawax,
Is this safe to use (even if its just to take a BACKUP in case anything happens "other" than the use of your App, that could be used to RESTORE original partition layout...?) on Samsung Galaxy Note (N7000) which suffers from eMMC brickbug, that if used with wrong kernel could potentially corrupt/kill the device...??
ie: Will this be fine to use on N7000, that suffers from an eMMC bug....?
- Neat App, and GUI btw...
Thanks, Lister
Lister Of Smeg said:
Hi @ferreirawax,
Is this safe to use (even if its just to take a BACKUP in case anything happens "other" than the use of your App, that could be used to RESTORE original partition layout...?) on Samsung Galaxy Note (N7000) which suffers from eMMC brickbug, that if used with wrong kernel could potentially corrupt/kill the device...??
ie: Will this be fine to use on N7000, that suffers from an eMMC bug....?
- Neat App, and GUI btw...
Thanks, Lister
Click to expand...
Click to collapse
UAPM does not have the power to restore partitions (Repartition the device). You can only flash/backup all partitions.
It is safe to use with responsibility.
Can i make swap partition on external sdcard?
@ferreirawax
I've wrote a few months ago a function which automatically detects the recovery and boot partition of a device
http://pastebin.com/rddAAQNW
it does not work on all devices, but for the most ones.
You can use this link to find your model:
http://opensource.lge.com/osSch/list...ME&search=G710 <<< Find your model, you must use Linux to compile this code.
Models:
LMG710N - USA model (Carrier unlocked model)
LMG710PM - Pre-release codename Judy
LMG710PS - ?
LMG710AWM - Likely this was the AT&T model that was changed to the V35 ThinQ
LMG710TM - T-Mobile model
LMG710VM - Verizon model
The files are coded with R, P, & X which I am guessing is Release Candidate, Production, and scrapped version.
The readme files are really helpful in explaining how to compile the software.
Under the bootloader section:
This product includes cryptographic software written by "EDITED for Psuedo Privacy". This product includes software written by "EDITED for Psuedo Privacy".
I figured that we could either create a custom bootloader that's NOT encrypted, but still follows the same boot up process. If bootup requires an encryption, then we could set the the process to accept anything, for example: if encryption = 1 or 0 then proceed to bootup.
I hope this helps development on this phone in creating a kernel, custom roms, etc...
a) tar -xvzf LMG710TMP_Oreo_Android.tar.gz
- And, merge the source into the android source code
- Run following scripts to build android
a) source build/envsetup.sh
b) lunch 1
c) make -j4
When I get to this section of creating the ROM for the LMG710TM phone, and I run the make -j4 command, I get this error:
./frameworks/base/Android.mk:865: warning: FindEmulator: find: `frameworks/opt/telephony/src/java/android/provider': No such file or directory
./frameworks/base/Android.mk:874: warning: FindEmulator: find: `frameworks/opt/telephony/src/java/android/provider': No such file or directory
./frameworks/base/Android.mk:879: warning: FindEmulator: find: `frameworks/opt/telephony/src/java/android/provider': No such file or directory
./frameworks/base/Android.mk:884: warning: FindEmulator: find: `frameworks/opt/telephony/src/java/android/provider': No such file or directory
[720/988] including ./system/sepolicy/Android.mk ...
./system/sepolicy/Android.mk:107: warning: BOARD_SEPOLICY_VERS not specified, assuming current platform version
[978/988] including ./vendor/lge/external/android-clat-lg/Android.mk ...
build/core/base_rules.mk:238: error: vendor/lge/external/android-clat-lg: MODULE.TARGET.EXECUTABLES.clatd already defined by external/android-clat.
13:43:02 ckati failed with: exit status 1
build/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1
#### make failed to build some targets (53 seconds) ####
Also, when I am trying to make the Kernel for the same phone, based off of the open source files, I get this:
make[2]: *** [sub-make] Error 2
I have never built a ROM before. What am I doing wrong?
https://drive.google.com/open?id=1x0Bhn4qRnYOFdbI1BlghbNb6kS9N_Qy3 <<< Here is the READ ME file that comes with the OS for the LMG710TM.
bigjohnman said:
a) tar -xvzf LMG710TMP_Oreo_Android.tar.gz
- And, merge the source into the android source code
- Run following scripts to build android
a) source build/envsetup.sh
b) lunch 1
c) make -j4
When I get to this section of creating the ROM for the LMG710TM phone, and I run the make -j4 command, I get this error:
./frameworks/base/Android.mk:865: warning: FindEmulator: find: `frameworks/opt/telephony/src/java/android/provider': No such file or directory
./frameworks/base/Android.mk:874: warning: FindEmulator: find: `frameworks/opt/telephony/src/java/android/provider': No such file or directory
./frameworks/base/Android.mk:879: warning: FindEmulator: find: `frameworks/opt/telephony/src/java/android/provider': No such file or directory
./frameworks/base/Android.mk:884: warning: FindEmulator: find: `frameworks/opt/telephony/src/java/android/provider': No such file or directory
[720/988] including ./system/sepolicy/Android.mk ...
./system/sepolicy/Android.mk:107: warning: BOARD_SEPOLICY_VERS not specified, assuming current platform version
[978/988] including ./vendor/lge/external/android-clat-lg/Android.mk ...
build/core/base_rules.mk:238: error: vendor/lge/external/android-clat-lg: MODULE.TARGET.EXECUTABLES.clatd already defined by external/android-clat.
13:43:02 ckati failed with: exit status 1
build/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1
#### make failed to build some targets (53 seconds) ####
Also, when I am trying to make the Kernel for the same phone, based off of the open source files, I get this:
make[2]: *** [sub-make] Error 2
I have never built a ROM before. What am I doing wrong?
Click to expand...
Click to collapse
I've seen this error before. To fix it go to vendor/lge/external/android-clat-lg and find MODULE.TARGET.EXECUTABLES.clatd or something like that. Then just outline it but why are you making a rom for this phone? It supports project Treble
Basically it was just something I was trying to do to learn. If using project Treble has the framework that LG has so that I can use Quick Remote, LG Gallery, & LG Video, I may be set...
LameMonster82 said:
I've seen this error before. To fix it go to vendor/lge/external/android-clat-lg and find MODULE.TARGET.EXECUTABLES.clatd or something like that. Then just outline it but why are you making a rom for this phone? It supports project Treble
Click to expand...
Click to collapse
but treble aosp NEVER is as good as a normal rom
Did anybody managed to compile the kernel for G7?
I have managed to compile the kernel but so far was not able to make it work. I have a boot.img compiled and flashed to a/b partitions but phoen get stuck in fastboot mode. Any clue?
sign this petition to LG if you have a LG G7
https://www.change.org/p/lg-electro...share_options_more.control&utm_term=triggered
umminkug said:
https://www.change.org/p/lg-electro...share_options_more.control&utm_term=triggered
Click to expand...
Click to collapse
Done and shared to FB!
@LameMonster82 What did you mean by outline the MODULE.TARGET.EXECUTABLES.clatd ? I'm like @bigjohnman trying to learn, but Im not entirely hip to the what you mean. Any help would be appreciated!! thanks (I also have the T-mobile LG G7)
Dvalin21 said:
@LameMonster82 What did you mean by outline the MODULE.TARGET.EXECUTABLES.clatd ? I'm like @bigjohnman trying to learn, but Im not entirely hip to the what you mean. Any help would be appreciated!! thanks (I also have the T-mobile LG G7)
Click to expand...
Click to collapse
Hate to break it to you but the open source kinda doesn't work. I already tried it long time ago. Also I don't think you can test it at all with a non European model. If you still want to learn how to build a rom you can Google how to make GSI roms. You can start from here https://github.com/phhusson/treble_experimentations/wiki/How-to-build-a-GSI?
AWM is Canadian in case anyone is wondering
Any update on this?
LameMonster82 said:
Hate to break it to you but the open source kinda doesn't work.
Click to expand...
Click to collapse
Someone asked me to make a custom kernel for G7 so I took a look.
From what I can see it must be a snapshot of a very early development stage. It's not based on any CAF tag because it's actually older
than the very first CAF release for sdm845.
I read Pie might be out soon, maybe that source will be ok.
askermk2000 said:
Someone asked me to make a custom kernel for G7 so I took a look.
From what I can see it must be a snapshot of a very early development stage. It's not based on any CAF tag because it's actually older
than the very first CAF release for sdm845.
I read Pie might be out soon, maybe that source will be ok.
Click to expand...
Click to collapse
Do you think it's possible to merge the source with the latest CAF or at least the first official one? In case the pie source packs the same kernel source.
LameMonster82 said:
Do you think it's possible to merge the source with the latest CAF or at least the first official one? In case the pie source packs the same kernel source.
Click to expand...
Click to collapse
That might be possible, yes. Although there's no telling how far off LG's own code is from current and what effect that would have.
If they do the same with Pie then the best thing would be to simply e-mail them asking for current source drop.
I've done it before with the G5, they responded rather quickly as well. After all they are legally bound to.
I think they're just lazy about it in general. Probably don't expect anyone to care.
Edit: Well, not e-mail but send an inquiry. You'll find an icon next to the download links ("http://opensource.lge.com")
askermk2000 said:
That might be possible, yes. Although there's no telling how far off LG's own code is from current and what effect that would have.
If they do the same with Pie then the best thing would be to simply e-mail them asking for current source drop.
I've done it before with the G5, they responded rather quickly as well. After all they are legally bound to.
I think they're just lazy about it in general. Probably don't expect anyone to care.
Edit: Well, not e-mail but send an inquiry. You'll find an icon next to the download links ("http://opensource.lge.com")
Click to expand...
Click to collapse
Hi, unfortunately the pie kernel is also not working. J0sh1x tried it. I already send an email to LG but it takes so long for them to respond I got an automatic email reinsuring me that they will eventually respond.
Do you think that the pie kernel can run on Oreo?
LameMonster82 said:
Hi, unfortunately the pie kernel is also not working. J0sh1x tried it. I already send an email to LG but it takes so long for them to respond I got an automatic email reinsuring me that they will eventually respond.
Do you think that the pie kernel can run on Oreo?
Click to expand...
Click to collapse
What did he try exactly?
I'm building it now, there are many compilation errors and I have a slow pc, but I'm getting there.
I was imagining that after if successfully completes, it should work. This is considering I checked out the source beforehand,
and this time there's no pre-caf weirdness going on at least. It's based on LA.UM.7.3.r1-06100-sdm845.0
But ofc, if there is something else going on, like incomplete LG patchset...
Don't know about Oreo, or I don't know what kind of changes there are in Pie and if they can cause troubles.
Edit: Oh, I assume he tried it on Oreo then... I thought first someone could try it on Pie but only Korean variant has the beta ?
I don't have a G7 so...
The source seems ok. Probably doesn't work on Oreo because it's a Pie kernel, and/or changes done.
askermk2000 said:
What did he try exactly?
I'm building it now, there are many compilation errors and I have a slow pc, but I'm getting there.
I was imagining that after if successfully completes, it should work. This is considering I checked out the source beforehand,
and this time there's no pre-caf weirdness going on at least. It's based on LA.UM.7.3.r1-06100-sdm845.0
But ofc, if there is something else going on, like incomplete LG patchset...
Don't know about Oreo, or I don't know what kind of changes there are in Pie and if they can cause troubles.
Edit: Oh, I assume he tried it on Oreo then... I thought first someone could try it on Pie but only Korean variant has the beta ?
I don't have a G7 so...
The source seems ok. Probably doesn't work on Oreo because it's a Pie kernel, and/or changes done.
Click to expand...
Click to collapse
I also tried compiling it and it went buttery smooth. BTW any ideas of how to test it without opening the phone itself?
LameMonster82 said:
I also tried compiling it and it went buttery smooth.
Click to expand...
Click to collapse
Sure, if you use gcc 4.9... (or perhaps an older version of clang).
EDIT: I've built a test for anyone interested. (Just a stock kernel basically, sans exfat, for now)
I don't know how/what exactly LameMonster82 or J0sh1x did, but perhaps I've done something different...
Anyway, I did not really consider to build this for Oreo. For Pie it probably works, when that get's released.
This thing flashes modules as well (assumed to be /system/lib/modules), so if you test on Oreo you should back up those,
as it'll likely not work and then you'll be without working modules.
Finally; there's a lot of new stuff that's completely new to me now I see. Like vendor partition, dtbo, new ramdisk layout etc...
so maybe I've done something wrong, or did not do something necessary.