Develop Bugs

OpenRUU v1 for Linux & Mac - A Script to Update Your ROM [W/ OR W/O ROOT!]

OpenRUU - RUU Shell Script For Linux (See the post below for mac support)
This is a shell script to flash an official RUU from HTC.
I tested this on my device and it ran fine, it uses exactly the same commands as the RUU app.
You do not need root.
The script will:
Get your current ROM version
Get Your Current HBOOT Version
Get Your Battery %
Reboot into RUU Mode
Flash the ROM using fastboot
Reboot your phone
Enjoy!
DOWNLOADS:
2.73.405.5 Generic WWE (The one you need to root with flashrec)
TO INSTALL:
GUI Method:
Extract the zip > right click on the script > properties > permissions tab > Select 'Enable execution as a program' > OK > Double Click > Run in terminal
Terminal method:
Code:
Extract the zip
cd /path/to/files
chmod 755 OpenRUU-Hero-WWE-2.73.405.5.sh
./OpenRUU-Hero-WWE-2.73.405.5.sh
If you want me to add a ROM then please PM me with the rom.zip, see here for how to extract a rom.zip from an RUU.
If you can, please donate so I can afford better hosting, I also have some cool features to implement when I get proper hosting too. (If you can host a rom.zip, please PM me.)
- GBP
- Euro
- Dollars
Post here with any bugs/comments so my turkeys can get to work!
{
"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"
}

Mac Support
For Mac:
Download this,
Delete 'adb' & 'fastboot' from the folder you extracted the files too,
Rename 'fastboot-mac' to 'fastboot',
Copy it to the script folder,
Run the Script.
If you get errors then please put in a codebox the terminal output.

That's a nice idea. Something the community has been lacking for a while too
Hope it goes well

Reserved #2 - ^^ DOH! This 30secs thing really annoys me

(HELP) Can't sync correctly CM9 sources

Hi, I'm trying to sync CM9 sources. I've set up my Ubuntu 11.10 from differents pages of xda, like the guide of Rom2Maru.
So, all libs are intalled, jdk6 is also installed ,etc. So, yesteray I started to start to sync, using the instructions of the PecanCM's github:
Code:
repo init -u git://github.com/PecanCM/android.git -b ics
repo sync -j16
And I don't know why but after 4 hours it stucks. I have tried 3 times and in the 3 times it stucks at the final. I've got a lot of memory left on my hard drive so I don't know why it stucks.
I have run a log and nothing special, here you have a Screenshot:
{
"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"
}
In the first terminal, here is my sync stucked. In the second one, Here is the log. So, in the thirst I did a "repo sync", but it stucks too.
So, please, can anyone help me? I'm really interested in learn about android and can compile it.
Thanks a lot

hi, try this
from root of source
Code:
cd .repo
rm -rf manifest*
rm -rf repo
cd ..
mv .repo ../.repo
cd ..
rm -rf {name of source folder}
mkdir cm9
mv .repo cm9/.repo
cd cm9
repo init -u git://github.com/PecanCM/android.git -b ics
repo sync -f
hope this works for you

Thanks for your help, but it's stucked in:
Fetching projects: 100% (258/258), done.
I don't know what can I do. Do you have another idea?
And, Which version of ubuntu are you using? Are you using wubi? And what post do you use to set up your ubuntu (jdk, libs,etc)?
Thanks

Some time it happens with me too but i fix it by repo sync -f ! try only repo sync -f I hope it will work for you

Ok, I've done what you said, I restarted to sync again, and I have some news problems:
First, It stucks agains here:
Then, It said that I have to use repo sync -f --force-broken, so I did:
But It said that can't sync, and there isn't git in bootloader.
Any one can help me please? thanks

repo sync -f should work bro !

Compiling Custom Kernel for Samsung Galaxy S5 G900F Kernel

Hi guys,
I'm trying to compile a kernel, so far I have come upto generating the zimage, but now I'm stuck at this step.
Please help. Thanks a lot.
What do I do with the warning? and how can I repack the new zImage with the initframs extracted from the stock kernel.
{
"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"
}

Hve you tried asking @wanam and @ktoonsez they are kernel building experts

Sock12345 said:
Hve you tried asking @wanam and @ktoonsez they are kernel building experts
Click to expand...
Click to collapse
well I tried asking @wanam quite a few times, but could not get a reply
I will try speaking with @ktoonsez and @wanam

Download the file below from my github @ https://github.com/ktoonsez/KTSGS5
1. mkbootfs (place in root folder of your kernel source)
Then execute these after zImage is made
Change the text "YOUR_RAMDISK_FOLDER" and "YOUR_PACKAGE_FOLDER" to proper folders.
cp arch/arm/boot/zImage YOUR_PACKAGE_FOLDER/zImage
./mkbootfs YOUR_RAMDISK_FOLDER | gzip > YOUR_PACKAGE_FOLDER/ramdisk.gz
tools/dtbTool -o arch/arm/boot/dt.img -s 2048 -p scripts/dtc/ arch/arm/boot/
chmod a+r arch/arm/boot/dt.img
tools/mkbootimg --cmdline 'console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3' --kernel YOUR_PACKAGE_FOLDER/zImage --ramdisk YOUR_PACKAGE_FOLDER/ramdisk.gz --base 0x00000000 --pagesize 2048 --ramdisk_offset 0x02000000 --tags_offset 0x01E00000 --dt arch/arm/boot/dt.img --output YOUR_PACKAGE_FOLDER/boot.img

ktoonsez said:
Download the file below from my github @ https://github.com/ktoonsez/KTSGS5
1. mkbootfs (place in root folder of your kernel source)
Then execute these after zImage is made
Change the text "YOUR_RAMDISK_FOLDER" and "YOUR_PACKAGE_FOLDER" to proper folders.
cp arch/arm/boot/zImage YOUR_PACKAGE_FOLDER/zImage
./mkbootfs YOUR_RAMDISK_FOLDER | gzip > YOUR_PACKAGE_FOLDER/ramdisk.gz
tools/dtbTool -o arch/arm/boot/dt.img -s 2048 -p scripts/dtc/ arch/arm/boot/
chmod a+r arch/arm/boot/dt.img
tools/mkbootimg --cmdline 'console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3' --kernel YOUR_PACKAGE_FOLDER/zImage --ramdisk YOUR_PACKAGE_FOLDER/ramdisk.gz --base 0x00000000 --pagesize 2048 --ramdisk_offset 0x02000000 --tags_offset 0x01E00000 --dt arch/arm/boot/dt.img --output YOUR_PACKAGE_FOLDER/boot.img
Click to expand...
Click to collapse
I have to say Ktoonez, I love your work, but where do you start building kernels for android?, ive been meaning to compile one for my NVidia shield for everyone to use, but I don't know where to start, also all the whole thread is dead in terms of development which is sad.

mudflap2.0 said:
I have to say Ktoonez, I love your work, but where do you start building kernels for android?, ive been meaning to compile one for my NVidia shield for everyone to use, but I don't know where to start, also all the whole thread is dead in terms of development which is sad.
Click to expand...
Click to collapse
Im already a developer for work so I already knew "C" code, all I did was search internet and follow github to see how it all worked. :good:

Nokia 7.1 stock rom flasher (Windows and Linux support)

Moderator Announcement: THREAD CLOSED as duplicate of https://forum.xda-developers.com/t/nokia-7-1-stock-rom-flasher-windows-and-linux-support.4196717/!​
Attention : All actions with your phone are performed at your own risk. The Creator of this SOFTWARE is not responsible for your further actions.
n_flasher is a powerfull application for Nokia 7.1 flashing written on D and GTK+ (GTKd)
{
"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"
}
Rom collection​
Android 10 with Google Secure Path 08.2020 : https://drive.google.com/file/d/1PuXsiY_OKojdUUYvmWbAWQ7AUDnOVrYg/view?usp=sharing
Android 10 with Googlse Secure Path 10.2020 (with vbmeta) : https://drive.google.com/file/d/1ED1_O9OYUFkJGygCCYgmDRzrFJEcz-CI/view?usp=sharing
How to use it on LINUX​
1. Install build dependencies
For Arch :
Code:
sudo pacman -S dlang meson ninja gtkd
For Ubuntu :
Code:
sudo apt install libgtkd-3-dev meson ninja-build ldc
2. Build and run application
Code:
git clone https://github.com/KonstantIMP/n_flasher.git
cd n_flasher
meson builddir
ninja -C builddir
3. Install android tools and set PATH to adb and fastboot
Note! You can install it by your package manager. n_flasher will automaticly try to find it in the PATH
4. Download ROM archive. Extract its and set root to the directory with .img files
5. Press the Flash button AND ENTER YOUR USER PASSWORD INTO THE TERMINAL WHERE THE PROGRAM WAS OPENED (it is necessary that fastboot has all the rights to the firmware)
Linux video tutorial
How to use it on Windows​
1. Download latest Release from my GitHub : https://github.com/KonstantIMP/n_flasher
2. Extract archive. Download ROM and android tools
3. Connect your phone. Reboot it to the bootloader and install driver from driver directory
4. Start the application. Set root to the ADB and ROM. Click Flash and wait
Windows video tutorial
Questions​
A. I have an error with vcruntime140.dll
Install .exe file from redist directory
B. Fastboot can't see my device
Try to reinstall driver. Remove all Android devices from DeviceManager and install it again.
It is instruction from 4pda.ru
We connect the phone on the screen of which "Download mode" hangs to the PC.
Now open the file "Phone_Nokia_USB_Driver_v.1.1.0.msi", click "Next" everywhere.
If an error occurs during installation, such as "Che is there in English, and access is denied", click "OK", complete the installation.
Open the "nokia_usb_drivers" archive, run the "setup" file in the only folder - something imperceptible should happen, wait a few minutes
Open "Control Panel" - "Device Manager" - And see a device named "Fastboot device"
Click to expand...
Click to collapse
A. Need I flash vbmeta?
In general, you don't need to do this. It is worth using this function if, after flashing, your phone refuses to update via the cloud. In some situations, this may solve your problem.
Note! You can only do this if your firmware archive contains vbmeta.img.
A. How the project will develop?
I hope, that I will add some new opportunities like non-stock ROM flashing, but I don't know what will really happen
A. Can I use It with Locked bootloader
NO
My GitHub : https://github.com/KonstantIMP/
XDA:DevDB Information
n_flasher, Tool/Utility for the Nokia 7.1
Contributors
KonstantIMP
Source Code: https://github.com/KonstantIMP/n_flasher
Version Information
Status: Stable
Current Stable Version: 0.1.1
Stable Release Date: 2020-11-30
Created 2020-11-30
Last Updated 2020-11-30

Stuck when building LOS17.1, what is $(PATH_OVERRIDE_SOONG)

Hello everyone!
I am quite a newbie to build the LineageOS, earlier this week I was trying to write my own device tree files, I had prepared most of the files needed and was managed to add my device to the lunch menu.
However when I was trying to building my twrp recovery image following peter9811's tutorial(link), the compilation was always failed with
Code:
[100% 140/140] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
FAILED: out/soong/build.ninja
out/soong/.bootstrap/bin/soong_build -t -l out/.module_paths/Android.bp.list -b out/soong -n out -d out/soong/build.ninja.d -globFile out/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja Android.bp
error: vendor/lineage/build/soong/Android.bp:30:8: module "generated_kernel_includes": cmd: unknown variable '$(PATH_OVERRIDE_SOONG)'
16:47:35 soong bootstrap failed with: exit status 1
1.I looked up the 'vendor/lineage/build/soong/Android.bp' and found $(PATH_OVERRIDE_SOONG) is defined somewhere else, possibly in my Android.mk.
2.I tried google the problem but got nothing except an unresolved post.
3.I tried to lunch aosp_arm-eng or aosp_arm64-eng and it gives the same error, however, lineage_arm64-userdebug works just fine.
As far as I know the aosp is switch from makefile to soong, my wild guess is this process makes some of those tutorials outdated, if that so, could somebody post some up-to-date instructions?
Could anyone please tell me what is going on there, which file should I modify to avoid this kind of problems.
Thanks for reading my post, and any possible solution will be much appreciated.
{
"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"
}

hi man!
not sure if you still interested in solving this. This occurs because the config files inside vendor/lineage isn't being included in some build/*.mk files. This is weird because you're using LOS repo, so it should already have the commit where it does this inclusion. Repo sync might help you in there.
If it doesn't, take a look at this commit. It's a lineage-18.1 commit, but you should compare it and see what still needed on your side.

Did you find any solution to this? i am facing similar issue while building cafex and still cant find any solution. M from sources is up to date.

akshatpro said:
Did you find any solution to this? i am facing similar issue while building cafex and still cant find any solution. M from sources is up to date.
Click to expand...
Click to collapse
I had the same issue and solved it by using the breakfast command before building rom. No extra editing required.
Relevant XDA post/thread
Source

eatmyriceboi69420 said:
I had the same issue and solved it by using the breakfast command before building rom. No extra editing required.
Click to expand...
Click to collapse
Ohhh how I wish that fixed it for me. Lunch, bacon, refreshmod, clobber. Nothing works
Vinnom said:
If it doesn't, take a look at this commit. It's a lineage-18.1 commit, but you should compare it and see what still needed on your side.
Click to expand...
Click to collapse
Thank you sir! These look exactly like the droids I have been looking for!
EDIT: soooo that just created new errors (vendor/lineage/build/soong/soong_config.mk doesn't exist)
Had a brain spark, deleted the entire local/working folder. (not .repo of course).
Then a simple repo sync -l and now I'm at least building.
Fingers crossed