Develop Bugs

[TOOL][Windows/Theming] BatchAPKTool

As seen on the front page: http://www.xda-developers.com/android/streamline-your-app-theming-with-batchapktool/ (Thanks nikwen and Will!)
I never was overly happy with available solutions/tools/scripts for theming. So, over time my collection of homegrown batch scripts grew... and now I made a menu interface for them to collect them in a (for me, at least) logical manner. I'm gonna put them up here, maybe some people might find them useful.
BatchAPKTool differs from other Apktool/Smali-manager scripts in a few ways. It doesn't do everything everybody might find useful in a script, but it gets basic things done really fast and really neat. Where it makes sense, several working steps are combined into one command. BatchAPKTool is not a monolithic script. You can use the main menu script (!0-batchapktool-menu.bat), or you can simply click the various single scripts to get stuff done, which is usually the fastest option. There aren't a lot of folders to keep track of - everything is basically done in the root folder of the script. Just drop some APKs there and get going. BatchAPKTool automatically makes backups of the original files. And, of course, the name of the script comes from the fact that you don't select a single APK file to work with, but everything is done in batch (it's the user's responsibility to not mix system and user apps when signing/pushing/installing APKs).
On first startup the script checks if Java is installed on the computer, and sends you to the Java website if not. It also pulls the framework from your device and installs it for Apktool. After that you're good to go. The frameworks are tagged, so one can easily switch when developing for different devices.
The main menu (orange font) shows everything in order that's needed for theming system APKs. Basically, just go from option 1 to option 6 (or 7) and be done. The additional options (red font) contain features one might need as well - options 1 to 3 for non-system apps - but not as often as the main menu ones. Options 4 to 6 are just some 'internals'. It's all pretty self-explanatory, methinks:
{
"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"
}
Prerequisites are - besides Java - a custom recovery like TWRP that can mount partitions (for pushing system apps), and of course USB debugging enabled, ie. a working ADB connection.
I probably packed some safety checks in the scripts that might break operation on certain systems. Bug reports are welcome.
Tools included:
7za v9.20
aapt v0.2
adb v1.0.31
apktool v1.5.2
DeflOpt v2.07
jpegoptim v1.2.2
OptiPNG v0.7.4
signapk [?]
Stripper v1.5.5.60
zipalign
(I didn't include PNGOut for optimizing images, since it is extremely demanding, even on modern hardware... but one can easily add it to the toolchain.)
Changelog:
v1.01 Streamlined some functions, more (in)sanity checks, better integration of framework switching function
v1.00 Initial release

Cool.
Suggested it for the portal.

Awesome - thanks a lot!
A slightly updated version is coming sometime soon.

New v1.01 in first post.
Changelog: Streamlined some functions, more (in)sanity checks, better integration of framework switching function.

dfkt_ said:
New v1.01 in first post.
Changelog: Streamlined some functions, more (in)sanity checks, better integration of framework switching function.
Click to expand...
Click to collapse
Not really into cooking ROMs these days, but this tool will definately help if I enter the kitchen again and try my hand at themimg.
Thanks a lot :good:

Thanks for this, it's really productive

Thanks for this tool, Really useful & helpful!

Thanks bro, it makes so much things easier

Thanks mate. I'll give a try asap
I saw your thread from the portal and this is worth cuz it looks very useful on paper :good:

Glad you guys find it useful.
Don't hesitate to report eventual bugs, or illogical combinations of options, etc.

dfkt_ said:
On first startup the script checks if Java is installed on the computer, and sends you to the Java website if not.
Click to expand...
Click to collapse
Thanks for putting this together, but I think the download Java links in your script should point to the JRE download page instead of the main page for Java:
Java JRE download page

dfkt_ said:
As seen on the front page: http://www.xda-developers.com/android/streamline-your-app-theming-with-batchapktool/ (Thanks nikwen and Will!)
I never was overly happy with available solutions/tools/scripts for theming. So, over time my collection of homegrown batch scripts grew... and now I made a menu interface for them to collect them in a (for me, at least) logical manner. I'm gonna put them up here, maybe some people might find them useful.
BatchAPKTool differs from other Apktool/Smali-manager scripts in a few ways. It doesn't do everything everybody might find useful in a script, but it gets basic things done really fast and really neat. Where it makes sense, several working steps are combined into one command. BatchAPKTool is not a monolithic script. You can use the main menu script (!0-batchapktool-menu.bat), or you can simply click the various single scripts to get stuff done, which is usually the fastest option. There aren't a lot of folders to keep track of - everything is basically done in the root folder of the script. Just drop some APKs there and get going. BatchAPKTool automatically makes backups of the original files. And, of course, the name of the script comes from the fact that you don't select a single APK file to work with, but everything is done in batch (it's the user's responsibility to not mix system and user apps when signing/pushing/installing APKs).
On first startup the script checks if Java is installed on the computer, and sends you to the Java website if not. It also pulls the framework from your device and installs it for Apktool. After that you're good to go. The frameworks are tagged, so one can easily switch when developing for different devices.
The main menu (orange font) shows everything in order that's needed for theming system APKs. Basically, just go from option 1 to option 6 (or 7) and be done. The additional options (red font) contain features one might need as well - options 1 to 3 for non-system apps - but not as often as the main menu ones. Options 4 to 6 are just some 'internals'. It's all pretty self-explanatory, methinks:
Prerequisites are - besides Java - a custom recovery like TWRP that can mount partitions (for pushing system apps), and of course USB debugging enabled, ie. a working ADB connection.
I probably packed some safety checks in the scripts that might break operation on certain systems. Bug reports are welcome.
Tools included:
7za v9.20
aapt v0.2
adb v1.0.31
apktool v1.5.2
DeflOpt v2.07
jpegoptim v1.2.2
OptiPNG v0.7.4
signapk [?]
Stripper v1.5.5.60
zipalign
(I didn't include PNGOut for optimizing images, since it is extremely demanding, even on modern hardware... but one can easily add it to the toolchain.)
Changelog:
v1.01 Streamlined some functions, more (in)sanity checks, better integration of framework switching function
v1.00 Initial release
Click to expand...
Click to collapse
Now this will come in handy very very much! Keep up the good work and keep adding features to it
Sent from my Galaxy Nexus using Tapatalk 4

Not sure that your quote is useful.

8notime said:
Thanks for putting this together, but I think the download Java links in your script should point to the JRE download page instead of the main page for Java:
Java JRE download page
Click to expand...
Click to collapse
Yeah, that's a dilemma - the URL for the JRE direct download link is dynamic (the "1880261" part), changes with each new version. So the script would have to be constantly updated (or some really sophisticated URL crawler implemented). The lazy-but-safe way of linking to the index page is probably the best I can offer. Or maybe it's safe to link to the root JDK/JRE download page (which seems to have a fixed URL), and tell people that the JRE is enough, no need to get the JDK.

THANK YOU
Great tool. Im currently working on my dialpad theme. Great find! :good:

[How to]Root Project Astoria

Root section #​Hello guys,
after 45564564165 hours of research (joke but this took me about 1 week ._.) I finally rooted Project Astoria
Images
{
"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"
}
Current issues​Apps can't request root because of limit of project astoria. I'm working on it.
Procedure​Perform an Hard reset first.
After settings up, deploy Root Tool.
Go to Lumia Registry Editor, click on navbar > templates and then select all.
Close the app and go to settings > Update and security > For developers.
Enable developer mode and click on Discovery. It should show to you the pin.
Download Astoria Tools.rar
Extract it.
Open that extracted folder.
You should see wconnect and so on.
On the "void" area, make SHIFT + Right click, and then click to "Open Command prompts here".
Write wconnect usb and write the pin.
After this, download AOW shortcut.7z in the attachment, extract it, copy that in your phone, example "Phone\Documents"
Now, go to your phone and open File Explorer. Open Documents and click on Aow shortcut
Go to RootFS directory and delete the file init.
Warning, there are 2 files, you need to delete "init.rc", it has about 20-19 KB.
Restart now your phone.
Keep it plugged on computer and wait about 5 minutes. it should you show "Windows Phone" device connection.
Open it and go to: Data\Users\DefApps\APPDATA\Local\Aow\RootFS
Download from Astoria folder link, the latest Rootkit & Gapps version.
Extract it.
Copy ALL Files to the phone (Data\Users\DefApps\APPDATA\Local\Aow\RootFS).
It ask you if you want to replace/merge files. Say Yes.
Press yes if it show this to you:
After you finished you need to set MTP to the standard path.
Download CustomPFD and deploy it.
Open that app.
Navigate to TWEAKS PAGE and click to General tweaks.
Navigate to UTILITIES: check FULL FS ACCESS and uncheck again.
Restart your phone.
Download Superuser.rar and extract it on Astoria tools folder.
After boot, connect to your pc and install superuser.apk (adb install superuser.apk)
After installation, you can launch the command "adb shell" and as you can see you are a root user
I'm really destroyed but at the same time happy
THANKS​djamol and ngame for his Interop Unlock method/app.
Marocco2 for his help.
snickler for his help.
Pasqui industry for making CustomPFD.
(I forgot someone?)
And all member of XDA and the world itself
Download​
Astoria Folder (Astoria Tools - AOW shortcut - Rootkit & gapps): http://astoriafolder.adeltax.com (Redirect to mediafire)
Attached some files because of problem with mediafire (stupid block)
-- EDIT --
If you have problem with installing APK after root, go to your phone and delete packageinstaller.odex using Aow shortcut and going to RootFS > System > app folder (The lowest size, approx 153 KB)

GAPPS Section​
Not yet, still working on it.

Here will be my "research"

Changelog:
v0.72
First version.

I will make GUI Installer/Package manager or something like this.

You are a monster, on fire!

\o/.

U are my hero o/

Happy rooting

Ah so you actually have to delete the init.rc files and wait for them to reproduce? That's why! Awesome job. I can't wait to test this out @ADeltaX

Hello there,
I can then the Google Play Store etc. properly use and also
Install Android applications on the Store from Google?

HannHenne said:
Hello there,
I can then the Google Play Store etc. properly use and also
Install Android applications on the Store from Google?
Click to expand...
Click to collapse
Not yet. For now it's very hard to resolve an "issue".

@ADeltaX, have you tried Insecure root or insecure su binary? The su binary that doesn't rely on a root management app like SuperSU? Because we can get direct root access on an app instantly if it requests for root with that...
Sent from Ponyville

Can we get a custom android with root now?

Got to final Stage now im getting an error code 14 Problem booting Astoria
Using Lumia Icon (929) on OS 10166

Lanex777 said:
Can we get a custom android with root now?
Click to expand...
Click to collapse
Nope, you need to edit Hyper-v library (and this is impossible)

darkcroc said:
Got to final Stage now im getting an error code 14 Problem booting Astoria
Using Lumia Icon (929) on OS 10166
Click to expand...
Click to collapse
Some files are missing on AOW folder.
Retry and replace the folder again.

mrchezco1995 said:
@ADeltaX, have you tried Insecure root or insecure su binary? The su binary that doesn't rely on a root management app like SuperSU? Because we can get direct root access on an app instantly if it requests for root with that...
Sent from Ponyville
Click to expand...
Click to collapse
Nope, Sincerely I never heard about insecure SU binary.
The SU version is a modded one, because if I use the SuperSU version, on invoking SU it say "segmentation fault" --> mean something doesn't work like shared object (library aka .so).

Someone can compile strace binary for armeabi/armeabi-v7a?
At this time Virtual Box doesn't want to start (I have Linux Mint in VM with AOSP source).

ADeltaX said:
Nope, Sincerely I never heard about insecure SU binary.
The SU version is a modded one, because if I use the SuperSU version, on invoking SU it say "segmentation fault" --> mean something doesn't work like shared object (library aka .so).
Click to expand...
Click to collapse
Some Chinese tablets I fix had insecure su... How did I know? When I adb shell it's already # . Or those only work with adb and not apps requiring su permission?
Sent from Ponyville

[TOOL] Lx Multi Tool v1.3.2 [WIN/LIN/MAC][Unlock/Recovery/Stock/Kernel/More]

{
"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"
}
​It has LINUX/UNIX and MAC support!
​
Because there is another tool for Android called Android Multi Tools, I renamed this one to Lx Multi Tool, future releases will go under this name.
​ Features: ​
Fastboot​​- Unlock/Lock Bootloader​- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.2 Included​- Flash any partition (Flashing submenu)​- Flash full Stock images (you can choose and add images)​- Erase partitions (you can choose which of the partitions)​- Reboot (you can choose again...)​​Adb​​- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.56 (Systemless!) included​- Backup (you can choose the name and place for your backup)​- Restore (you can choose your backup)​- Version (it just shows the version of your adb binaries) - platform-tools 23.0.1 included​- Logs (DMESG and Logcat)​- Screenshots (you can directly take screenshots to your PC with no Root)​- Reboot (lots of choices)​​Others​​- Refresh and delete files/folders from menus (Right-click or key F5 and Del)​- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)​- Tab key support for easier keyboard navigation​- Tool-tips for all buttons​- Check for updates​- Link to xda-thread (here)​​​ Download links: ​
Windows x86|x64 - Linux x64 - MAC x64​​All released versions can be found here.​​
​
(The latest versions are always on the bottom.)​​[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.​​
​ Known bugs/limitations: ​
- For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)​- For the return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)​​
​ Changelog: ​
​Check the changelog for each release here.​​​ Tutorials/FAQ: ​
​Q: How do I get in bootloader/fastboot mode?​Turn off the phone and turn it on by using Volume down + Power key.​​Q: How do I check for updates on your tool?​Follow the instructions on the screen below.​
​Q: Where can I find the device driver to install it for windows?​Click here, download the driver, and run the setup.​​Q: How do I root my stock phone?​- Unlock bootloader.​- Flash recovery.​- Use SuperSU 2.62 systemless or higher from here.​(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)​​Q: I get an error "Cannot open file" on MAC, what should I do?​Open the terminal, go to your application path and paste this command:​
Code:
chmod +x LxMultiTool.app/contents/macos/*
​Q: What do I need to do in order to be in Fastboot or in ADB mode.​Fastboot mode will be detected only while being in bootloader.​ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.​Refresh button needs to be used in order to check for what mode you are in.​​Q: Are there any other software that I need to install in order to run this tool?​On Windows and MAC everything is bundled, so nothing needs to be installed, just run.​On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.​If it's not enough, use ldd LxMultiTool in the terminal to find out what you're missing from your environment.​​Q: I have a yellow/orange/red text screen during boot, what's that?​When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.​​Q: Hey, my device is not detected, why?​On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.​Also, make sure you click the connection Refresh button after connecting the device to your PC.​​Q: What do I need to do in order to install a custom ROM?​1. Unlock Bootloader.​2. Flash a custom recovery of your choice.​3. Flash an insecure kernel (boot).​4. Flash custom ROM with no problems via recovery.​All those things are found and can be done via this tool.​​Q: Hi, I just downloaded this tool, how do i use it?​First, extract the folder somewhere.​After that, run LxMultiTool.exe on windows by double-clicking it, LxMultiTool on Linux, and the same on mac.​​Q: Do I need android-sdk installed or something else?​No! This tool uses its own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyway.​This tool is fully portable and stand-alone.​​Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?​Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:​- Enable Developer options​- Enable USB Debugging​- Look for the ‘OEM Unlock’ Option and toggle it.​​Q: How do I use the return to stock feature?​First, download the latest package from here, then extract the contents (there is an archive in the archive) until you get to a folder like angler-mda89d​that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.​​Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.​
​Q: How do I enable Developer options?​- Launch the Settings​- Scroll Down and Tap on About Phone(or About Device)​- Locate the Build Number Section​- Tap on the Build Number Option 7 Times​- Go Back to the Main Settings Page​- Scroll Down and Tap on Developer Options​​Q: Hi, I just bought a phone what should I do now?​Well, you firstly need to unlock your bootloader...​​Q: What is logcat?​Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.​It is usually used for debugging and entertainment(?).​When you report an error/bug to somebody, it will be a blessing to provide a logcat (log file)!​​Q: What is a Custom Recovery and why do I need one?​A custom recovery is that thingy that lets you flash .zip files, use your logic, and you will get it why you need one.​​Q: There are other guides/tutorials out there. Should I check them instead of this?​If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...​​Q: What is sideload and how do I use it?​Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.​Please note that you need to be in sideload mode on your recovery before doing this.​To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload​
​ Sources: ​
The official and original repository can be found here.​​
​ Bug reports/feature requests: ​
If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on GitHub for more traceability here.​​
​ Licensing: ​
Please note that this tool is open source and released under the GPL v3 license, which can be read here.​Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.​​
​ Tech and stuff: ​
Some additional marketing for stuff used in this tool​​Qt - An awesome cross-platform IDE​Vmware - For letting me test this tool on all platforms (Linux and MAC).​Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)​UnixUtils - For the sed utility for Windows.​AndroidFileHost - For the awesome file-management platform for developers.​​
​ Donations: ​
Even though this tool is provided free of charge, fully open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.​​This section will also include the hall of fame for donors and on the github repository.​​Special thanks for donations:​- @john7760​​
​ Disclaimer: ​
I will not be responsible for smashed screens, bricked phones, or any other things that you can accuse me of, I've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.​Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A, or useless posts, please read the FAQ section upside, it's like a Mini-Guide!
XDA:DevDB Information
Lx Multi Tool, Tool/Utility for the Huawei Nexus 6P
Contributors
Lexmazter
Source Code: https://github.com/lexmazter/LxMultiTool
Version Information
Status: Stable
Created 2016-01-01
Last Updated 2016-01-16

Already tool kit?
*Damn, nexus dev support is amazing
I feel so bad for buying galaxy s6, 0 aosp roms, Mod edit: Profanity removed dev support and all because of stupid exynos ;C

You da man! Can't wait for my phone to show up.

That was quick!! Waiting for this phone to be launched in India.

It works great thanks.I mean Tool

Wow. Can't wait to get my 6P and use this
Sent from my A0001 using Tapatalk

Add to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P

Haven't even received my device yet, just wanted to say Thanks in advance!

Showing so much promise
I can't say more for this kind of support.

Great to see this already in the forum. Waiting on my 6P 128 Gig MONSTER.

wilbarger said:
Great to see this already in the forum. Waiting on my 6P 128 Gig MONSTER.
Click to expand...
Click to collapse
Got the 128gb monster on the way myself.

Thanks for this. Making it easy for everyone is a great thing I'm so excited to get back on a nexus

Thanks for this tool, I need to start from scratch because I don't have a Nexus since Nexus One

Thanks for this. Will be a first time user for the nexus generation. Just ordered the 6P so will definitely be doing this .

Great seeing this already. Coming from an S4 to the 64GB 6P. Will it be possible to relock the bootloader after installing a custom recovery or is the stock recovery required for the lock?
Sent from my SPH-L720 using Tapatalk

C4PO said:
Great seeing this already. Coming from an S4 to the 64GB 6P. Will it be possible to relock the bootloader after installing a custom recovery or is the stock recovery required for the lock?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
AFAIK, locking bootloader has nothing to do with the recovery, but then again, I never locked a bootloader...

Pretty sure you'd need to flash stock recovery. It won't hurt anything to try it without stock recovery, but if it doesn't work then you'll know for sure why.

I'm not planning to mess around with it too much until a stock system file is available. I need a Plan B. Lol

Doesn't run for me. (Mac User)
Heres the terminal error
sh [Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh
[Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh: line 3: [Path to location]/6PMultiTool.v0.2/simple_curses.sh: No such file or directory
There doesn't seem to be a "simple_curses.sh" file in the tool directory that I can find. Hope you can get it figured out! Thanks for the awesome tool as well!

ryman222 said:
Doesn't run for me. (Mac User)
Heres the terminal error
sh [Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh
[Path to location]/6PMultiTool.v0.2/6PMultiToolv0.2-M.sh: line 3: [Path to location]/6PMultiTool.v0.2/simple_curses.sh: No such file or directory
There doesn't seem to be a "simple_curses.sh" file in the tool directory that I can find. Hope you can get it figured out! Thanks for the awesome tool as well!
Click to expand...
Click to collapse
Unfortunately I never got the chance to test the MAC version, finally I have a tester
From what I can see at a first look is that this simple_curses.sh is some leftover from when I experimented with some UI tricks for bash to try to simulate the looks of the batch version..
Can you please check this temporary version from here -> 6PMultiTool.v0.2.1.zip

[Tool][Guide] LeeDrOiD and ICE svnZipper | Windows | Linux | Mac

svnZipper​
As you may know developers like @LeeDroid and @baadnewz use Subversion so users can get the latest changes quickly. Although this results in users checking out the Subversion repository and zipping the ROM themselves. This doesn't sound too difficult and it isn't, but to make things easier I made a tool I like to call "svnZipper". It is a pre-built binary with all the dependencies to build a nightly ROM from @LeeDroid and @baadnewz repositories, this has support for Windows, Linux and Mac.
As we are not all perfect the tools does face issues, be it bugs or user issues, I am finding it hard to keep track of all these issues popping up in each thread. Therefore I made this thread to get the latest svnZipper, follow guides and report any issues for me to answers and solve (although it is in HTC 10 thread you can post HTC One M9 and HTC One M8).
The Guide​
Step 1
Download the latest svnZipper:
LeeDrOiD get it here
ICE get it here
Put the svnZipper anywhere you like on your PC, I would recommend a folder you can easily access.
Step 2 (Only Required for Mac and Linux)
For Mac and Linux you will need to set the permissions of the binary to be executable. You are probably be familiar with this process if you are a Linux and Mac user but if you don't know the process I will explain it for you. Open up a terminal and change to the directory of the location of your svnZipper, then type the following command:
Mac:
chmod 0755 macSvnZipper followed by enter
Linux:
chmod 0755 linuxSvnZipper followed by enter
Step 3
Execute the svnZipper
Windows:
Double click the svnZipper.exe or open up command prompt in the location of the .exe and type:
svnZipper.exe followed by enter.
Mac:
With the terminal still open from Step 2, type the following command:
./macSvnZipper followed by enter
Linux:
With the terminal still open from Step 2, type the following command:
./linuxSvnZipper followed by enter
Once you have execute the screen you will be presented with a image as shown 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"
}
Step 4
Type the corresponding number next to the device you would like to build for and press enter. This will start the process of checking out files or updating the files that already exist if you have checked out before. This process will vary time consuming depending on how many files are needed to be download from the remote repository.
This process will complete the following steps:
1. Checkout/Update files from the remote repository for your device
2. Make a nightly .zip for your device
3. Make a md5 checksum file for .zip
All checked out files will be stored in the same directory of executable in the following paths:
LeeDrOiD:
HTC 10 it will be /LeeDrOiD_PME
HTC M9 it will be /LeeDrOiD_HIMA
HTC M8 it will be /LeeDrOiD_M8
ICE:
HTC 10 it will be /ice_pme
HTC M9 it will be /ice_hima
HTC M8 it will be /ice_m8
Once completed you will be presented with a screen shot similar to the ones below.
All nightly .zip and .md5 files will be stored in the same directory of executable in the following paths:
LeeDrOiD:
HTC 10 it will be /LeeDrOiD_PME/Builds
HTC M9 it will be /LeeDrOiD_HIMA/Builds
HTC M8 it will be /LeeDrOiD_M8/Builds
ICE:
HTC 10 it will be /ice_pme/Builds
HTC M9 it will be /ice_hima/Builds
HTC M8 it will be /ice_m8/Builds
The builds will be named in the following format:
LeeDrOiD:
HTC 10 it will be LeeDrOiD_PME_RXX.zip
HTC M9 it will be LeeDrOiD_HIMA_RXX.zip
HTC M8 it will be LeeDrOiD_M8_RXX.zip
ICE:
HTC 10 it will be ice_pme_nightly_rXX.zip
HTC M9 it will be ice_hima_nightly_rXX.zip
HTC M8 it will be ice_m8_nightly_rXX.zip
Step 5
If a update comes out and you would like to rebuild the ROM again, follow Step 3 and Step 4
FAQ
QUESTION: The build zip is extremely small and has missing files?
ANSWER: Delete the checked out files and execute the steps above again
QUESTION: The revision checked out by the tool is out of date and doesn't get the latest revision from the remote repository?
ANSWER: Delete the checked out files and execute the steps above again
Note: The FAQ will increase as I get more user experience.
Reporting a Issue
Take screen shot of the errors raised from the tool and post it in this thread. If I don't get as much information as possible I can not help you.
Note: Windows will automatically close is a issue arises, therefore I recommend that you execute the .exe in command prompt instead of double clicking.
XDA:DevDB Information
svnZipper, Tool/Utility for the HTC 10
Contributors
~clumsy~
Source Code: https://github.com/clumsy1991/svnZipper
Version Information
Status: Beta
Current Stable Version: 1.0.4
Stable Release Date: 2016-06-06
Created 2016-06-07
Last Updated 2016-06-07

Changelog
Changelog
V1.0.5
Set locale so SVN doesn't report errors handling non ascii file names.
Thanks to @coolberry for reporting the bug
V1.0.4
Considered as initial revision

Brillant.... Much easier to follow in the future with this dedicated thread.
Not to forget to mention that it's never been easier to update nightlies ?????
Sent from my HTC 10 using XDA-Developers mobile app

The Great Dane said:
Brillant.... Much easier to follow in the future with this dedicated thread.
Not to forget to mention that it's never been easier to update nightlies ?????
Click to expand...
Click to collapse
And press 1 to build

~clumsy~ said:
And press 1 to build
Click to expand...
Click to collapse
Shut up LMFAO [emoji12]

Different filesize
Hi @~clumsy~,
I already posted this in @LeeDroid thread but he told me to ask you about this.
been playing around with the svnZipper but I don't fully trust it. I have a fast NAS server where I made a folder for this. Added the zipper and executed it. Works well and downloaded (as far as I can tell, all the available files).
When the zip file is made during the process, the NAS seems to be slower so I made a local folder on my i7 32GB Windows 10 pro powered machine with raid SSD to this should work super fast.
Ran svnZipper and yes, it is fast but after the script was finished, I checked the file size of the created zip and it was about 300MB smaller then the one on the NAS. Turned out the only folder that was downloaded by the zipper is the system folder. The created MD5 "tells" me the zip is correct in filesize but as this is created based on the downloaded files, it is easy to get a corrupted/incomplete flashable rom file that can f*ck up you HTC 10.
Please see the attached printscreens. A local version and a nas version.
Is this something I'm doing wrong?
Thanks for your reply!

twistednl said:
Hi @~clumsy~,
I already posted this in @LeeDroid thread but he told me to ask you about this.
been playing around with the svnZipper but I don't fully trust it. I have a fast NAS server where I made a folder for this. Added the zipper and executed it. Works well and downloaded (as far as I can tell, all the available files).
When the zip file is made during the process, the NAS seems to be slower so I made a local folder on my i7 32GB Windows 10 pro powered machine with raid SSD to this should work super fast.
Ran svnZipper and yes, it is fast but after the script was finished, I checked the file size of the created zip and it was about 300MB smaller then the one on the NAS. Turned out the only folder that was downloaded by the zipper is the system folder. The created MD5 "tells" me the zip is correct in filesize but as this is created based on the downloaded files, it is easy to get a corrupted/incomplete flashable rom file that can f*ck up you HTC 10.
Please see the attached printscreens. A local version and a nas version.
Is this something I'm doing wrong?
Thanks for your reply!
Click to expand...
Click to collapse
One thing to note and I will add this to the OP. The MD5 is the MD5 of the zip created on your machine, so it will only check for corruption when transferring from your PC to you Phone, not from SVN to your machine.
Did you transfer the repository from your NAS to your i7 machine? Or rechecked the files out on your local machine?

~clumsy~ said:
One thing to note and I will add this to the OP. The MD5 is the MD5 of the zip created on your machine, so it will only check for corruption when transferring from your PC to you Phone, not from SVN to your machine.
Did you transfer the repository from your NAS to your i7 machine? Or rechecked the files out on your local machine?
Click to expand...
Click to collapse
No I did not move the file to my local machine but opened the zip.
Inside the zip you can see why the size is different. I'll add printscreens of the several versions I have. I use the svnZipper.exe version 1.04 FYI.
Everytime I run the zipper it just seems to grab some files and not all. My connection is a 100MB fiber and my local network is 1GB.
I could runs something like Wireshark during the execution of the zipper to see if there are any errors.
Regards Ralph

twistednl said:
No I did not move the file to my local machine but opened the zip.
Inside the zip you can see why the size is different. I'll add printscreens of the several versions I have. I use the svnZipper.exe version 1.04 FYI.
Everytime I run the zipper it just seems to grab some files and not all. My connection is a 100MB fiber and my local network is 1GB.
I could runs something like Wireshark during the execution of the zipper to see if there are any errors.
Regards Ralph
Click to expand...
Click to collapse
Yeah it needs to determine some errors, it's quite simple at the moment. I execute the svn checkout on a different thread it seems like errors are missed. So the local repo thinks it is upto date. It seems like a common bug and something I need to work. For now the only solution is to delete the local repo including the .SVN directory and run the process again. It isn't the best solution for now but I will fix it, I just need time.

~clumsy~ said:
Yeah it needs to determine some errors, it's quite simple at the moment. I execute the svn checkout on a different thread it seems like errors are missed. So the local repo thinks it is upto date. It seems like a common bug and something I need to work. For now the only solution is to delete the local repo including the .SVN directory and run the process again. It isn't the best solution for now but I will fix it, I just need time.
Click to expand...
Click to collapse
Good luck with that. If you need any help testing, just PM me and I will try to help you out.
Please bear in mind I only reported this to warn you and not because of any complains about your work
Cheers!

twistednl said:
Good luck with that. If you need any help testing, just PM me and I will try to help you out.
Please bear in mind I only reported this to warn you and not because of any complains about your work
Cheers!
Click to expand...
Click to collapse
I know! Much appreciated! This why I made the thread so i can capture bugs and peoples experiences.

Thank you!
Though resume download is broken in this SVN tool, it will see the files downloaded as complete and will not give an option to resume or force resume

great job,thanks!

~clumsy~ said:
Yeah it needs to determine some errors, it's quite simple at the moment. I execute the svn checkout on a different thread it seems like errors are missed. So the local repo thinks it is upto date. It seems like a common bug and something I need to work. For now the only solution is to delete the local repo including the .SVN directory and run the process again. It isn't the best solution for now but I will fix it, I just need time.
Click to expand...
Click to collapse
Thanks for the heads up....
Sent from my HTC 10 using XDA-Developers mobile app

Just a minor fix, only 1 report case of the bug.
Changelog
V1.0.5
Set locale so SVN doesn't report errors handling non ascii file names.
Thanks to @coolberry for reporting the bug

Quite nice of a tool to use. But me I just highlight the 4-5 folders I need and right click send to folder and zip is created in few minutes.

Ndaoud360 said:
Quite nice of a tool to use. But me I just highlight the 4-5 folders I need and right click send to folder and zip is created in few minutes.
Click to expand...
Click to collapse
The tool is made for its ease of use and is independent so user don't have to install anything. It was requested by the devs. You can still use a manual solution.

Hi clumsy ...lovin your back-end work , kernel is smooth n functional , svnzipper windows works great ..
Now a nice request (challenge if you like) ..
Can we have a svnzipper for Android ..even shell based would be great, ...
Cheers
Sent from my HTC 10 using XDA-Developers mobile app

I have the same problem as mentioned on the first page. The program does not work correctly if I run it from a network share. It finishes downloading prematurely and it creates a partial ROM which does not work.
I took clumsy's script, stripped some parts in order to create a minimal example and to see what it does (I removed the multiprocess operations). The result: each time I run it, it works for several minutes, then it ends with the following error:
pysvn._pysvn_3_5.ClientError: ra_serf: The server sent a truncated HTTP response body.
It happens each time.

kfasheldon said:
Hi clumsy ...lovin your back-end work , kernel is smooth n functional , svnzipper windows works great ..
Now a nice request (challenge if you like) ..
Can we have a svnzipper for Android ..even shell based would be great, ...
Cheers
Click to expand...
Click to collapse
Sorry man, that will too much work as it wouldn't be possible with my current method.

[Guide] Build Your Own [UNOFFICIAL][9] LineageOS4Microg 16.0 (by Bernie_nix)

In the spirit of open-source, if there's one ROM that deserves to be "home-brewed" in addition to AOSP and Lineage, it's LineageOS4Microg. This guide will explain how to do so using Docker. LineageOS and Microg are explained below followed by the guide.
{
"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"
}
Code:
/*
* I'm not responsible for bricked devices, damage, loss of Google services, you getting fired because the alarm app failed, etc. Do this at your own risk.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications.
* Your warranty may/will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS4MicroG & LineageOS
LineageOS unofficial fork with built-in microG gapps implementation.
Full Play Services compatibility [Well-almost...YMMV]
Our ROM has built-in microG free-as-in-freedom re-implementation of Google's proprietary Android user space apps and libraries. This enables you to use every Google service you need without keeping another closed-source binary blob in your Android system.
Native F-Droid support
LineageOS for microG comes with F-Droid already installed. You can use it to access plenty of FOSS applications or even a Play Store bridge repository like Playmaker or GPlayWeb.
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Learn more at:
LineageOS: https://lineageos.org/
LineageOS4MicroG: https://lineage.microg.org/​
Click to expand...
Click to collapse
Rom Built by Bernie_nix​Known issues:
USB-C headphones work for music, watching videos, etc. They don't work in the phone app...yet. (working on this)
Some users report VOIP calls don't work properly. YMMV. Skype, Whatsapp, Nextcloud Talk, working great for me.
Automatic updates not yet implemented but will be in a future build.
You tell me.
Building Requirements
1. A fast PC or VPS account such as Google Compute Engine. Minimum PC recommended requirements are Intel i5 or equivalent, 4 cores 8 threads minimum (more cores and better CPU recommended), 16GB ram, SSD and 300GB free drive space minimum, fast internet connection (you will download over 30GB of sources).
2. Ubuntu 18.04 is supported here. If you use Windows or another version of Linux, let others know of your tweaks and workarounds.
3. Patience and time. Downloading sources, setting up and building a rom will take hours if not days (depending on your PC hardware and internet speed).
Environment Setup & Build​1. Install Docker on Ubuntu (run each command once in terminal)
Code:
sudo apt-get update
sudo apt install docker.io
sudo systemctl start docker
sudo systemctl enable docker
2. Test that docker is running (run command in terminal)
Code:
docker run hello-world
You should see something like this, "docker run hello-world Unable to find image 'hello-world:latest' locally latest: Pulling from library/hello-world ca4f61b1923c: Pull complete Digest: sha256:ca0eeb6fb05351dfc8759c20733c91def84cb8007aa89a5bf606bc8b315b9fc7 Status: Downloaded newer image for hello-world:latest Hello from Docker! This message shows that your installation appears to be working correctly. ..."
3. Pull lineageos4microg docker onto your pc (run command in terminal)
Code:
docker pull lineageos4microg/docker-lineage-cicd
4. After pull is complete, create the following directories in your home/YOURUSERNAME directory
lineageos4microg
lineageos4microg/src
lineageos4microg/ccache
lineageos4microg/local_manifests
lineageos4microg/keys
lineageos4microg/logs
lineageos4microg/zips
So it might look something like this: home/JoeAndroid/lineageos4microg
5. Copy the 4 attached xml files (bottom of this post) to your local_manifests folder
These are: ocean.xml, include_proprietary.xml, proprietary.xml, and custom_packages.xml
6. In terminal, cd into the lineage4microg folder, and copy and paste the following commands all at once after changing YOURUSERNAME to your username in ubuntu. For an explanation of options, see the link at bottom of post. This code will download sources, sync your repos with newest updates and start your build. This step could take hours. It is downloading sources, syncing repos and building your rom!
Code:
sudo docker run \
-e "BRANCH_NAME=lineage-16.0" \
-e "DEVICE_LIST=ocean" \
-e "SIGN_BUILDS=true" \
-e "SIGNATURE_SPOOFING=restricted" \
-e "WITH_SU=true" \
-e "CUSTOM_PACKAGES=GmsCore GsfProxy FakeStore MozillaNlpBackend NominatimNlpBackend com.google.android.maps.jar FDroid FDroidPrivilegedExtension " \
-e "INCLUDE_PROPRIETARY=false" \
-v "/home/YOURUSERNAME/lineageos4microg/lineage:/srv/src" \
-v "/home/YOURUSERNAME/lineageos4microg/zips:/srv/zips" \
-v "/home/YOURUSERNAME/lineageos4microg/logs:/srv/logs" \
-v "/home/YOURUSERNAME/lineageos4microg/cache:/srv/ccache" \
-v "/home/YOURUSERNAME/lineageos4microg/keys:/srv/keys" \
-v "/home/YOURUSERNAME/lineageos4microg/manifests:/srv/local_manifests" \
lineageos4microg/docker-lineage-cicd
7. Your build should be in the zips folder when complete! Flash in twrp/ofox.
8. If your build fails, check the log in lineageos4microg/logs/ocean folder. If you receive the following error, "Can not locate config makefile for product "lineage_ocean"" you will need to copy the 4 xmls from lineageos4microg/local_manifests to lineageos4microg/manifests.​
References and links:
https://phoenixnap.com/kb/how-to-install-docker-on-ubuntu-18-04
https://github.com/lineageos4microg/docker-lineage-cicd
Telegram group for additional ROMS, files and support: https://t.me/mG7Power
Thanks to Dark98, Electimon, Barry and many others for initial help and repos when building this rom.

Reserved #1

Reserved #2

Thanks, been wanting to try to build this.
I tried am running this on ubuntu 18.04 vm, followed all the instructions.
after I type in the docker commands get this after a few minutes:
sed:can't read build/core/version_defaults.mk:no such file or directory
can't detect the android version.
Any suggestions?

skalnas said:
Thanks, been wanting to try to build this.
I tried am running this on ubuntu 18.04 vm, followed all the instructions.
after I type in the docker commands get this after a few minutes:
sed:can't read build/core/version_defaults.mk:no such file or directory
can't detect the android version.
Any suggestions?
Click to expand...
Click to collapse
Can you take a picture of the screenshot including how you typed in the commands? Need a bit more info

I just pasted the code changing username screenshot attached

skalnas said:
I just pasted the code changing username screenshot attached
Click to expand...
Click to collapse
I wonder if it's related to "steve" in your build commands but your username is Steven on the VM?

Bernie_nix said:
I wonder if it's related to "steve" in your build commands but your username is Steven on the VM?
Click to expand...
Click to collapse
I did rerun the script with the username steven and it appeared to be working.
went to bed and when i woke up I was excited to see it said build completed. however i could not
find the zip file in the zips folder. looking at the logs error: Can not locate config makefile for product "lineage_ocean".
I saw in the op to move the 4 xml files to manifests dir, however I had gotten permission denied when trying to
copy to the manifests dir. i deleted the dir, recreated the dir and moved the files.
I am going to try building again.

skalnas said:
I did rerun the script with the username steven and it appeared to be working.
went to bed and when i woke up I was excited to see it said build completed. however i could not
find the zip file in the zips folder. looking at the logs error: Can not locate config makefile for product "lineage_ocean".
I saw in the op to move the 4 xml files to manifests dir, however I had gotten permission denied when trying to
copy to the manifests dir. i deleted the dir, recreated the dir and moved the files.
I am going to try building again.
Click to expand...
Click to collapse
You need to sudo cp -R (drag 4 files to terminal here) /YOURUSERNAME/lineageos4microg/manifests. Then re run script

Bernie_nix said:
You need to sudo cp -R (drag 4 files to terminal here) /YOURUSERNAME/lineageos4microg/manifests. Then re run script
Click to expand...
Click to collapse
Thanks for the assistance, I am new to linux, hence the vm. My PC is amd fx8350 chip 8 core, 16 gb ram on win10 pro 64 bit on
PNY 480 gb ssd drive.
Just a few questions: The vm i set up to build this I set at 150gb. Prior to syncing the repos and running
the build script again i had about 135 gb free. It's been on starting build for ocean lineage-16.0 branch
for about 5 hours.
Should it have completed or thrown an error by now?
Also, lineageos4microg folder states it's using 57gb, I now have 32 gb free space 5 hours into build.
Not sure if I should keep waiting to see if build completes?
I have attached the log which i think is for the build in progress.
Thanks again

skalnas said:
Thanks for the assistance, I am new to linux, hence the vm. My PC is amd fx8350 chip 8 core, 16 gb ram on win10 pro 64 bit on
PNY 480 gb ssd drive.
Just a few questions: The vm i set up to build this I set at 150gb. Prior to syncing the repos and running
the build script again i had about 135 gb free. It's been on starting build for ocean lineage-16.0 branch
for about 5 hours.
Should it have completed or thrown an error by now?
Also, lineageos4microg folder states it's using 57gb, I now have 32 gb free space 5 hours into build.
Not sure if I should keep waiting to see if build completes?
I have attached the log which i think is for the build in progress.
Thanks again
Click to expand...
Click to collapse
Not recommended to run in a VM as it will take considerably longer to build but if you have the time (hours, days). As far as hard drive space, 150gb is cutting it very close. Better to have 250gb minimum. Don't know if you'll have enough. As far as your log and actual build, it's building! Congrats. If you scroll down to the bottom of your log, you'll see it's at 23%.

Bernie_nix said:
Not recommended to run in a VM as it will take considerably longer to build but if you have the time (hours, days). As far as hard drive space, 150gb is cutting it very close. Better to have 250gb minimum. Don't know if you'll have enough. As far as your log and actual build, it's building! Congrats. If you scroll down to the bottom of your log, you'll see it's at 23%.
Click to expand...
Click to collapse
Yes, as I feared i did run out space, but at least I know it was building. I may try to install ubuntu in a dual boot.
Thanks

skalnas said:
Yes, as I feared i did run out space, but at least I know it was building. I may try to install ubuntu in a dual boot.
Thanks
Click to expand...
Click to collapse
Awww... Well I had that happen before. Even if you have an old platter hdd (not ssd) as long as it's got the GBs of space it will take a little longer to build but for these purposes will do just fine. I use both SSD and hdds to build.

Got my dual boot set up. First tried Ubuntu but it kept locking up, went with Linux mint. Got a 250 GB partition, going to give it another go tommorow.

View attachment 4980819well, after switching from VM to dual boot, I gave it another go, and i got a msg in linux mint that i ran out of space about 3 1/2 hrs into build. I had set up 250gb partition as you suggested. I did 30gb root, 220 GB home,4 GB swap.
Can you take a look at the logs, i'm not clear looking at logs how much of build completed.
There was the zip file about 604 mb in the zips folder, which I could open(along with an sha and md5 files, which i dont know anything about.) I'm thinking possibly the build completed despite the warning in linux about running of free space.
I shrank the /root partition in gparted to 20gb and tried to extend the extra 10gb to home, but i couldn't.
Is it possible to specify 25gb ccache in the docker script somehow so that instead of the 50 it seems to allocate, maybe that will solve the space issue?
Thanks again, looks like progress.

Freed up some more space for build, now when trying to sync repos i get this msg Missing "vendor/lineage", aborting.
suggestions?

skalnas said:
Freed up some more space for build, now when trying to sync repos i get this msg Missing "vendor/lineage", aborting.
suggestions?
Click to expand...
Click to collapse
I looked at the last lines in your log... it looks like it built. Did you check your zips folder?
boot.img already exists, no need to overwrite...
dtbo.img already exists, no need to overwrite...
system.img already exists, no need to overwrite...
vendor.img already exists, no need to overwrite...
Total of 704512 4096-byte output blocks in 23 input chunks.
Total of 147456 4096-byte output blocks in 13 input chunks.
done.
Click to expand...
Click to collapse
Where is "Missing "vendor/lineage", aborting." appearing?

Bernie_nix said:
I looked at the last lines in your log... it looks like it built. Did you check your zips folder?
Where is "Missing "vendor/lineage", aborting." appearing?
Click to expand...
Click to collapse
Thanks, yes there was a zip there, wasnt sure if it was safe to flash, with the error space ran out ,but figured build did complete, as the zip wasnt corrupted.
As far as repo error:
"OSError: [Errno 17] File exists: '/srv/src/LINEAGE_16_0/device/generic/mini-emulator-arm64/.git.tmp'
error: Cannot checkout bernie-nix/android_device_motorola_sdm632-common-1: ManifestInvalidRevisionError: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found
error: in `sync -c --force-sync`: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found.
I did switch to the ocean.xml listed in your other thread posted by dark98 and the repo did sync., but I didn't proceed with the build.
Thanks again for all your help, think i will try to dirty flash my succesful build over yours, unless i should clean flash.

skalnas said:
Thanks, yes there was a zip there, wasnt sure if it was safe to flash, with the error space ran out ,but figured build did complete, as the zip wasnt corrupted.
As far as repo error:
"OSError: [Errno 17] File exists: '/srv/src/LINEAGE_16_0/device/generic/mini-emulator-arm64/.git.tmp'
error: Cannot checkout bernie-nix/android_device_motorola_sdm632-common-1: ManifestInvalidRevisionError: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found
error: in `sync -c --force-sync`: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found.
I did switch to the ocean.xml listed in your other thread posted by dark98 and the repo did sync., but I didn't proceed with the build.
Thanks again for all your help, think i will try to dirty flash my succesful build over yours, unless i should clean flash.
Click to expand...
Click to collapse
Yes, use the other xml if you want. They should both be about the same...you might even get updated sources, you might not...but it should build. I looked at the error above. The only suggestion I would make in your current xml if you want to continue using it is to remove revision="lineage-16.0" on the bernie-nix/android_device_motorola_sdm632-common-1 entry. As far as the zip that completed, how big is it?

Bernie_nix said:
Yes, use the other xml if you want. They should both be about the same...you might even get updated sources, you might not...but it should build. I looked at the error above. The only suggestion I would make in your current xml if you want to continue using it is to remove revision="lineage-16.0" on the bernie-nix/android_device_motorola_sdm632-common-1 entry. As far as the zip that completed, how big is it?
Click to expand...
Click to collapse
The zip was 604mb, i did successfully flash it, thanks again for your help and guide building my first rom!
so the xml file should be edited to:
<project name="bernie-nix/android_device_motorola_sdm632-common-1" path="device/motorola/sdm632-common" remote="github"/>
?
btw, i don't see your repos on github anymore.