yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Android Development] csendre:
Nope, I already deleted the sources to make room for another popular ROM not maintained by anyone any more.

This being said, you can use this forever. Oreo development is pretty much over at this point and all you'll only miss out on the latest security patches. Unless you are doing scratchy things on your phone these don't matter and if you do then they may not help you anyways :)
[Galaxy S 4 Mini Android Development] slukk1:
What firmware are you currently working on? Above the lineage?
[Galaxy S 4 Mini Android Development] csendre:
RR 6.2.1 Oreo

Here is a set of Resurrection Remix Oreo builds. Version is 6.2.1 and October security patches.

No updates planned.

- serranodsdd: https://www.androidfilehost.com/?fid=1322778262904028880

- serranoltexx: https://www.androidfilehost.com/?fid=1322778262904028878

- serrano3gxx: https://www.androidfilehost.com/?fid=1322778262904028879
[Galaxy S 4 Mini Android Development] slukk1:
Nice. Thank.
[Galaxy S 4 Mini Android Development] Arslan140:
[MENTION=5416372]csendre[/MENTION] any plan to make ?(pie) for

serranodsdd
[Galaxy S 4 Mini Android Development] Terraandroid:
Thank you

csendre

AICP 13.1 Oreo

I tested the two Gt I 9195 SERRANOLTEXX GT I 9192 SERRANODSDD perfect work excellent !! Thank you
[Galaxy S 4 Mini Android Development] flashnub:
One question, does the i9192 serranodsdd detect hidden Wifi network and connect to it ?
[Galaxy S 4 Mini Android Development] Terraandroid:
have not done this test yet.
[Galaxy S 4 Mini Android Development] kent999v:
firmware test

Samsung GT-I9192 Galaxy S4 Mini Duos wi-fi works well. no mobile networks. I can call and there is no internet with SIM cards.
[Galaxy S 4 Mini Android Development] flashnub:
Tested on i9192 duos, the ROM is smooth and Fast , but Does not detect hidden Wifi.
[Galaxy S 4 Mini Android Development] iamchriscool:
[MENTION=5416372]csendre[/MENTION] many thanks for building all these ROMs for us. I've tested the Resurrection Remix Oreo build (serranoltexx) and it runs very smooth. The only thing that I've found is that the settings for the hardware keys are missing. I can't swap the functionality of the left and middle key that I'm so much used to :crying:

I think it's only a compilation flag to include.

Is there any possibility to make another build including this feature?

Many many thanks in advance ...
[Galaxy S 4 Mini Android Development] csendre:
It is a flag in the overlay, since I am not part of their team I didn't know they use it as well. I deleted the sources, didn't plan on a new build, maybe around Christmas when I have some more time
[Galaxy S 4 Mini Android Development] diehengardt:
Hi

first thank you so much [MENTION=5416372]csendre[/MENTION] for providing us so up to date RR rom!

:good::good::good:

I've also installed your RR version for i915m, worked like a charm.

as said [MENTION=6821379]iamchriscool[/MENTION] only issue is to be able to swap or add functionnalties to left/right button.

I have another issue but it may be related to RR customization and/or Nova Launcher customization:

Power Button simply does not work when phone is on:

If I press (either short or long) on it no 'restart menu' pops on nor restart do happen albeit I've activated in my RR config to restart and to pops up a restart menu.

power buttons was working just before flashing your rom (was using stock rom), it still works to power on the phone and if i configure the rom to launch camera if i press on power button it works.

When I press the power button to switch off the phone something is happening in the phone cause it vibrates shortly then seems like frozen but if i press on home button it reactivates.

my guess is there is a conflict setup issue inside all RR customization parameters...

=> how can I revert to default config and restart step by step my customization?

Note: I use Nova Launcher but if switch to Trebuchet I still have the same issue

Note2: currently my phone has no SIM card (I get back my daughter's phone when she got a S7, preparing the S4 mini for my second daughter). could it be a side effect issue?
[Galaxy S 4 Mini Android Development] faizankhalifa:
Has anyone check this? Resurrection Remix 7.0 Pie is out. Expecting this rom in few months, as the devs are busy.

https://github.com/ResurrectionRemix
[Galaxy S 4 Mini Android Development] csendre:
Resurrection Remix Pie builds (RR 7.0.2)

RR pie builds below. June security patch level, selinux enforcing. I built them with SU but root doesn't work in RR either, so you will need Magisk.

Serranodsdd - 9192

Serranoltexx - 9195

Serrano3gxx - 9190
[Galaxy S 4 Mini Android Development] Anewkine:
Many thanks !! :good:
[Galaxy S 4 Mini Android Development] LicorneT:
Works very well. I tested it shortly on serranoltexx without root and without gapps and haven't come across any problem. And I'm amazed how many customizations are offered. Many thanks for that!
[Galaxy S 4 Mini Android Development] faizankhalifa:
Almost 99. 9% bugless. Magisk Edxposed working. Few performance lags but I think they're bound to happen. You should've made a main thread for this, coz I don't think it requires any major update. Thanks again for this build. ??
[Galaxy S 4 Mini Android Development] soulreaver13mejia:
You could check if flat style keyboard works with edxposed.
[Galaxy S 4 Mini Android Development] kamikaze702k:
Tested on serranoltexx, works flawless, only issue is in rr settings interface misc, when pressing that option it fc, regardless overall very good.

Would love to see havoc Rom on s4 device

Unfortunately I have no skills to build our compile or port, tried learning but I just couldn't grasp it.

Big props to everyone who have compiled roms
[Galaxy S 4 Mini Android Development] kamikaze702k:
This is a very good build, fast and smooth, tested several over the past few days, will stay on this, thanks for making.
[Galaxy S 4 Mini Android Development] giannis athlos:
I just installed this AICP on my i9195 but i can't access recent apps with menu button or homescreen button even if i keep press them for long time, i can't find harware buttons settigs and menu button is opening menu, back button is going back, homescreen is going on homescreen but they don't even light up, only if i enable navigation bar can access recents, is that a bug or i am missing something here? This rom is good but this problem doesn't let me use it. Thanks in advance for help.
[Galaxy S 4 Mini Android Development] helium314:
Would it be possible for you to update RR Pie?

There were some relevant changes in Lineage OS since June, like expanded quick setting menus for data and WiFi, SU is now working, and a fix for a serious bluetooth vulnerability.

If you decide to do so, could you also add some kernel extras like voltage control, overclocking and maybe the wireguard kernel module (if this is actually possible for S4 mini)?

And there is one more thing I really miss when comparing to AOKP: the long press time for home and capacitive buttons is really high. Is there a way to change it (without building with the desired setting)?
[Galaxy S 4 Mini Android Development] ripee:
I came across your post randomly while scrolling through my participated threads. Take a look:

android_device_samsung_serranoltexx

android_device_samsung_serrano-common

android_device_samsung_msm8930-common

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="android_packages_services_Telecomm" />
<project name="LineageOS/android_kernel_samsung_msm8930-common" path="kernel/samsung/msm8930-common" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-16.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="lineage-16.0" />
<project name="ripee/android_device_samsung_msm8930-common" path="device/samsung/msm8930-common" remote="github" revision="havoc-pie" />
<project name="ripee/android_device_samsung_serrano-common" path="device/samsung/serrano-common" remote="github" revision="havoc-pie" />
<project name="ripee/android_device_samsung_serranoltexx" path="device/samsung/serranoltexx" remote="github" revision="havoc-pie" />
<project name="triplr-dev/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="havoc-pie" />
<project name="triplr-dev/android_hardware_samsung" path="hardware/samsung" remote="github" revision="havoc-pie" />
<project name="triplr-dev/android_packages_services_Telecomm" path="packages/services/Telecomm" remote="github" revision="havoc-pie" />
</manifest>

This should build Havoc. I know this all looks intimidating, but it took me a long while to learn the steps to put this together. Once you get the hang of it, you will know how to arrange the pieces. I always say that rom development is like Lego for adults. If you wanna learn how I came up with these commits and roomservice, feel free to ask.
[Galaxy S 4 Mini Android Development] kamikaze702k:
Man I wish I could but honestly I don't have the resources for it, I won't ask you to build it but if u ever feel free to play about with building this in your spare time I'll be happy to test it, although I have a serranoltexx as a backup device, that lil beast was my daily driver for years
[Galaxy S 4 Mini Android Development] ripee:
Ya I posted the sources necessary to build it rather than a finished build since the build server on which I have Havoc synced has a backlog of building other devices lol, but I will attempt serranoltexx and make any adjustments to the commits for anyone who wants to them.

A backup device is perfect for learning this stuff. You'd want to keep it updated but still willing to break and fix it over and over.
[Galaxy S 4 Mini Android Development] kamikaze702k:
Thank you for all your contributions to the rom scene, appreciate your work, I have a note 4 also (amazing work you've done for that device) and recently got a oneplus 7 pro
[Galaxy S 4 Mini Android Development] helium314:
Havoc seems to have all the extras over LineageOS I want from RR, so I can go with this as well... I have a (useless because simlocked) 9195 to test, and sometimes access to a computer that should be good enough for building.

So now I have a VirtualBox Ubuntu on that computer and tried to understand how to build using this guide, but I still need quite a bit of help...

What should I use as url and branch for

repo init -u <url of manifest repo>.git -b <branch you want to build>
repo sync

Then I copy your <manifest> stuff into <android source>/.repo/local_manifests/9195.xml and run repo sync again.

At last I need to run "source build/envsetup.sh" and "brunch <rom>_<device model>-userdebug" (Havoc is rom and serranoletxx is model?).

Will this work, or did I miss a lot?

And what do I need to build for my 9192?
[Galaxy S 4 Mini Android Development] ripee:
With all due respect to ThePiGuy, I prefer to follow the automatically generated build guide for serranoltexx on Lineage's website for all of their officially supported devices. Your build environment will be the same for Havoc as for Lineage anyway.

See my scripts repo on my GitHub. Once you have Linux set up, run the build_environment.sh script and it will install the proper packages and set up a rudimentary folder structure. Then paste the following into a new file to automate the syncing of Havoc's codebase:

#!/bin/bash

mkdir -p ~/android/havoc-pie
cd ~/android/havoc-pie
repo init --depth=1 -u https://github.com/Havoc-OS/android_manifest.git -b pie
repo sync -c --force-sync --no-clone-bundle --no-tags
mkdir -p .repo/local_manifests
cd

Now create another script to run the build:

#!/bin/bash

cd ~/android/havoc-pie
make clean
wget -O .repo/local_manifests/roomservice.xml https://raw.githubusercontent.com/samsung-msm8930/local_manifests/havoc-pie/serranoltexx.xml
repo sync -c --force-sync --no-clone-bundle --no-tags
. build/envsetup.sh
brunch serranoltexx
mv $OUT/*-serranoltexx-*.zip $HOME
make clean

As for I9192, you would need to replace all instances of serranoltexx for serranodsdd, that is in the roomservice and build script. You could add the line for the serranodsdd repo in the serranoltexx roomservice and have a combo roomservice, if you will.

Sources: https://github.com/samsung-msm8930
[Galaxy S 4 Mini Android Development] helium314:
Thank you!

First repo sync is finished, will do the rest next week.
[Galaxy S 4 Mini Android Development] ripee:
I'll Havoc-ify serrano3gxx and serranodsdd as well later. I'll run builds for all 3 when I can, but if someone beats me to it, please post logs if they don't boot. If they don't boot, it'll be 90% likely that it's some Lineage HAL that needs to be removed.

Edit: builds are up: tiny.cc/triplr
[Galaxy S 4 Mini Android Development] csendre:
I will build some updates in a couple of weeks, I am quite busy until then. Won't mess with the kernel though, unfortunately I have no time for that
[Galaxy S 4 Mini Android Development] helium314:
[MENTION=6005084]ripee[/MENTION]

Nice! Unfortunately with your build my 9195 just shows "android" and does nothing, does not even get warm (waited for ~10-15 minutes).

Attached are log files for havoc and lineage (october build, working, for comparison in case it helps).

I noticed that your files are only ~330 MB, compared to ~370 MB of LineageOS. Could there be anything missing?
[Galaxy S 4 Mini Android Development] ripee:
Thank you for the logs. Havoc builds are generally smaller than Lineage builds for all devices.
[Galaxy S 4 Mini Android Development] Arslan140:
[MENTION=6005084]ripee[/MENTION] Bootloop on I9192 too

Here is the log

I enable adb status on kernel and repack it

Logcat actually stops at this line

"ServiceManagement: Waited one second for android.hardware.power@1.0::IPower/default... Waiting another"
[Galaxy S 4 Mini Android Development] helium314:
I finally had the opportunity to build on my own, even though I didn't expect it to work.

My build is a few MB larger and does not even boot... how can I see what went wrong?

When flashing, Havoc shows security patch from September, while LineageOS has November patch. Not sure if this is relevant though...
[Galaxy S 4 Mini Android Development] ripee:
When exactly did you sync the sources? I mean day and time? I did some work on the sources about 13 hours before this post and I will run another set of builds later today.
[Galaxy S 4 Mini Android Development] helium314:
About 5-6 hours ago. I only ran the build script you posted, this should do the sync as far as I understand.
[Galaxy S 4 Mini Android Development] ripee:
Ok, so you synced down my latest changes. Can you get logs? I fear it has to do with Lineage's own HALs, which are highly customized for Lineage but completely useless for most other roms because other roms' codebases do not have the appropriate repos.
[Galaxy S 4 Mini Android Development] helium314:
Sorry, there were no logs. When booting I only saw the Samsung Galaxy logo over and over again.

To test whether the problem is on my side, I tried to build lineage using your scripts (replacing the entries in your manifest file) and there everything works as expected.

I saw you made some updates yesterday, so I tried to build havoc again. But again I only see the Samsung logo and then get reboots.
[Galaxy S 4 Mini Android Development] ripee:
Running a build for all 3 variants: tiny.cc/triplr They should be up in around a couple hours from this post.

If and when they boot, I will create a separate thread.
[Galaxy S 4 Mini Android Development] birarvindersingh:
I tried i9192 (serranosdd) build, and it boots ?
[Galaxy S 4 Mini Android Development] birarvindersingh:
I am posting a picture below
[Galaxy S 4 Mini Android Development] birarvindersingh:
And If possible can you compile a Android Q build of LOS or AEX?
[Galaxy S 4 Mini Android Development] ripee:
Is lineage-17.0 stable enough yet? I doubt it, so any derivative rom will be just as unstable.
[Galaxy S 4 Mini Android Development] ripee:
Yay! Ok I'll make my own thread later tonight. Can I use that photo in my thread?

Edit: [ROM][UNOFFICIAL][9] Havoc-OS 2.9 [serrano3gxx][serranodsdd][serranoltexx]
[Galaxy S 4 Mini Android Development] birarvindersingh:
I just want to test it though ?

---------- Post added at 06:46 PM ---------- Previous post was at 06:46 PM ----------

Yeah, sure
[Galaxy S 4 Mini Android Development] csendre:
Just an update; wanted to build some updated RR builds but they have not updated their sources since early September so it is completely out of sync with Lineage. As I have no time to make local updates unfortunately it will not happen.
[Galaxy S 4 Mini Android Development] ripee:
Your previous work helped inspire me to port RR myself: [ROM][UNOFFICIAL][9] Resurrection Remix OS 7.0.2 [I9190][I9192][I9195]
[Galaxy S 4 Mini Android Development] csendre:
I just noticed your thread after I made that post. Once you synced sources, did you bring the RR team forked repos up to date with the Lineage upstream? I noticed that the RR team did not update their repos in a long time. For example the last commit in their fw_base is going back to Sept . This is what got on my nerves with AOKP as well, I was the only one left tio sync with teh upstream Lineage sources and it is a pain in the b... to do it
[Galaxy S 4 Mini Android Development] Ala Ghanmi:
Guys I wanna suggest something

Could any body make any other rom build for our devices maybe like AOSP Extended Pie or Pixel Experience or anything else and there is a Lineage OS 17 beta build but u need to contact the building teams to get the zip file
[Galaxy S 4 Mini Android Development] ripee:
I went ahead and made AEX builds, tiny.cc/triplr, but I don't want to create a thread because I have no intention of maintaining yet another rom. I can explore PE as well but if you want lineage 17, why don't you ask the build teams yourself.
[Galaxy S 4 Mini Android Development] Ala Ghanmi:
First when u will make a thread for the AEX

Second the lineage 17 is buggy too much and I'm not sure that I want to try it I just said that if there's any one want to try it

---------- Post added at 11:33 PM ---------- Previous post was at 11:28 PM ----------

Well I think I'll try ur AEX build now if I can and I wish that it doesn't have bugs
[Galaxy S 4 Mini Android Development] ripee:
There is no reason to create an AEX thread if my build doesn't work, which is why this thread was created.
[Galaxy S 4 Mini Android Development] Ala Ghanmi:
Get it but not that much xD

---------- Post added at 11:50 PM ---------- Previous post was at 11:49 PM ----------

Anyway I'm going to flash the AEX more to try it
[Galaxy S 4 Mini Android Development] ripee:
I'm building Pixel Experience, the simplified one, not PE-Plus. It'll have its own folders, PIXEL-EXPERIENCE_SERRANO.................
[Galaxy S 4 Mini Android Development] Ala Ghanmi:
Well I just booted up on AEX without gapps and it look a bit smoother than Havoc and have some options that are missing in Havoc IK it's based on the rom source

---------- Post added at 12:21 AM ---------- Previous post was at 12:15 AM ----------

BTW wanna ask what is the deference between PE and PE-Plus :confused::confused:
[XDA Assist] Skygg:
My tablet got hardbricked after a wrong firmware update, and now it does not boot anymore neither recovery mode and nor adb. Is there a way to recuperate it? Or somehow boot it via sd card?

there are informations about it:

CPU: via wm8880 Cortex A9 DUAL CORE 1.5GHz / DUAL GPU: 400MHz

RAM: 512MB

STORAGE: 8GB but I had access to only 4GB

this tablet is Genesis GT-7304

as far as I know this tablet boots from eeprom memory.
[XDA Assist] xanthrax:
Hi !

Unfortunately I couldn`t find anything related to your tablet here on xda , try a deeper search on google or post your issue here

https://xdaforums.com/android/help

Good luck !
[Verizon Galaxy Note 4 General] kevintm78:
This is just a safe upgrade to the latest CQA1 firmware for the SM-N910V. If you are already on 6.0 with an unlocked bootloader you can flash this to update. It will not lock your bootloader or overwrite your custom recovery. I slightly debloated it but other than that it's completely stock and still odexed.

INSTRUCTIONS

- Boot to recovery and do a complete wipe (everything except your internal and external sd card)

- Power off device and pull battery for at least 3 seconds

- Boot into Download mode and connect phone to your computer

-Start Odin and place the tar file in the AP slot

-Once Odin says it's ready just press start and let it do it's thing

CQA1 FIRMWARE DOWNLOAD

If you would like to run stock you can download and flash SuperSu for root and also Busybox by Osmosis
[Verizon Galaxy Note 4 General] Bren123:
Thanks will try later!
[Verizon Galaxy Note 4 General] Android.Ninja:
Thanks, I'll give it a look over.

Developers don't need no stinkin' signature! If I've been able to help you, please hit the "Thanks" button. ;)
[Verizon Galaxy Note 4 General] Android.Ninja:
Absolutely flawless!

Developers don't need no stinkin' signature! If I've been able to help you, please hit the "Thanks" button. ;)
[Verizon Galaxy Note 4 General] Rahul721:
What's the changes?
[Verizon Galaxy Note 4 General] kevintm78:
Just some security patches and minor bug fixes.
[Verizon Galaxy Note 4 General] the Doctor:
THREAD MOVED

Since this thread doesn't involve any development, it has been moved to the General section which is appropriate for guides/how-to threads. Please review the sticky in the development section titled "RULES for posting in Development" if you have any questions.

Sent from a government terminal using my sonic screwdriver
[Verizon Galaxy Note 4 General] machhho:
[MENTION=5285430]kevintm78[/MENTION]

is there any safe upgrade from KK ( unlocked bootloader ) to MM without locking bootloader
[Verizon Galaxy Note 4 General] kevintm78:
No buddy there isn't. The issues you'll have will vary when trying to upgrade the firmware without updating the bootloader. Mostly wifi related and brightness issues. All of the safe upgrades remove the aboot so it wouldn't update your bootloader.
[Verizon Galaxy Note 4 General] kevintm78:
Delete - double post
[Verizon Galaxy Note 4 General] kerfex:
OK, I am on BPA1. Lollipop - Marshmallow combo. Bootloader unlocked, root, etc. Running the 05/24/2016 Hsbadr CM 13.1 build. Can, I flash this and keep the unlocked bootloader or do I have to go through the whole downgrade to the BPA1 firmware, re-root and all that jazz? I just can't believe there is not an easier way to get to Marshmallow-Marshmallow since the bootloader is unlocked.
[Verizon Galaxy Note 4 General] mojoswagger1980:
Yes . doesn't contain aboot :victory: but the bootloader didn't change it isn't necessary or particularly useful unless you wanted to builds a touchwiz based ROM and wanted to use the most recent base .

---------- Post added at 11:04 PM ---------- Previous post was at 11:00 PM ----------

And no lol if you took the safe upgrade from 5.1.1 to 6.0.1 (via the lollipop ROM on marshmallow toolchain) you are currently on an up to date bootloader it is unneccesarry to repeat the unlock procedure and no this doesn't lock your bootloader . it isn't rooted however you would need to flash that but it is a one and done via twrp . kingroot wasn't needed.
[Verizon Galaxy Note 4 General] abrarakram19:
successfully​ unlocked on 910V but want to know

Can I flash 910F stock firmware via odin on my unlocked verizon 910V note 4. I want to convert it to GSM phone. Should I need to install custom recovery or permanent root before for this. Or is it possible and safe to convert without loosing sim connectivity. Please help.
[Verizon Galaxy Note 4 General] stajam:
Hello everyone! Been quite a while since I've been on here. I have been on the Kyubi ROM since the BL unlock was achieved on our Note4. IMO, it has been a pretty stellar ROM. Been using it ever since. Now, I have decided to upgrade the device.

I want to upgrade to at least a 6.0 ROM and I am on 5.1.1 BL version is BPA1, PDA version is BOK3 and Baseband Version is BPA1 as well, rooted and BL is unlocked.

My question is can I do this "CQA1 Firmware *safe upgrade* SM-N910V" in the OP without any problems?

Thanks in advance for any and all help with this...