Database Info

[ROM] CyanogenMod-6.1.1 for Desire (GSM/CDMA): V6.1.1 (16/12/2010)

CyanogenMod is a free, community built distribution of Android 2.2 (Froyo) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
cyanogen said:
This is an AOSP-based build with extra contributions from many people which you can use without any type of Google applications. I found a link from some other project that can be used to restore the Google parts, which can be found below or elsewhere in the thread. I've still included the various hardware-specific code, which seems to be slowly being open-sourced anyway.
Click to expand...
Click to collapse
Visit the CHANGELOG for a full list of changes and features!
All source code is available at the CyanogenMod Github!
If you'd like to to contribute to CyanogenMod, checkout our Gerrit instance (howto).
INSTRUCTIONS:
- First time flashing CM 6 to your Desire (or coming from another ROM)?
1. Root your device and install Clockwork Recovery (Unrevoked method is recommended).
2. Do a Nandroid backup!
3. Update your radio! New radio from 2.2 roms is required, see downloads below.
4. WIPE (wipe data/factory reset + wipe cache partition)
5. Install the ROM
5. Optionally install the Google Addon
- Upgrading from earlier CM6?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
HOW TO REPORT BUGS OR PROBLEMS?
- Was it a hard reboot? Go into recovery and dump the "/proc/last_kmsg" file.
- Was it a soft reboot or a "boot loop"? Run "adb logcat" and get send the full output.
- Pastebin links preferred
- Please use the issue tracker whenever possible!
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
This is the latest release candidate so any and all feedback is appreciated!
The preferred method of installation is via ROM Manager, or you can head over to the CM Forums for manual downloads.
GSM
Latest version: 6.1.1-Desire - 16/12/2010
Download: update-cm-6.1.1-Desire-signed.zip
Also available for download via ROM Manager
MD5Sum: e14b66d1e24f34603e2aaf071f20c5e2
CDMA
Latest version: 6.1.1-BravoC - 12/16/2010
Download: update-cm-6.1.1-BravoC-signed.zip
Also available for download via ROM Manager
MD5Sum: 5bd096950c505742e9e84fb6dc1da5e3
Google Addon: HDPI-20101114
Download: http://goo-inside.me/google-apps/
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!

Rooting Guide
http://forum.xda-developers.com/showthread.php?t=788044
Google Addon: latest HDPI-20101114
Other release http://goo-inside.me/google-apps/
Radio Firmware: 5.x radio required (GSM ONLY)
Desire GSM radio thread
Read/Write Access System Partition (S-OFF)? (GSM ONLY)
Thank's to AlphaRev [site] [xda]
Low storage for apps? (GSM ONLY)
Flash the AlphaRev HBOOT Bravo N1Table (Require S-OFF)
Follow this instrunction for update without data lost (aka no data wipe)
Still low storage for apps?
Install an A2SD solution: Firerat or Darktremor
i recommend the Firerat solution: CM specific, less space usage 25kb vs 6mb, bind mount, no boot loop, auto restore after cm rom update (from 1.35b)
No audio on FM Radio? (GSM ONLY)
http://forum.xda-developers.com/showpost.php?p=8992389&postcount=1280
Change Provider Name? (CDMA ONLY)
http://forum.cyanogenmod.com/topic/9101-guide-change-provider-name-in-cm6/
Adfree symlink instruction

can you post screes??

Woot, downloading now!!!

WAHEYYYYYYYYY! I'll flash asap. Do we have old school a2sd yet?
Sent from my HTC Desire using XDA App

GANJDROID said:
WAHEYYYYYYYYY! I'll flash asap. Do we have old school a2sd yet?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
No. Old school A2SD is aimed for CM 6.1. Just be happy with the ROM as it is atm. It's great. It's phenomenonal, marvellous, beautiful... amazing... [SteveJobsMode=off]

oleeeeeeee...thanks cyanogenmod team...

is the cyonegen mod soo good? or way are all so happy??
i flash it ... ext3 needed?

yasars said:
is the cyonegen mod soo good? or way are all so happy??
i flash it ... ext3 needed?
Click to expand...
Click to collapse
Besides JesusFreke, cyanogen is the godfather of Android.
CM exists since the G1/HTC Magic. After cyanogen got his Nexus, the project started to grow big. Atm it's (officially) available for 8 devices with many other unofficial ports for other devices.
No ext partition on the SD card is needed, it uses the Froyo A2SD implementation.

great man!!!!!

I just felt a little bit afraid...
I flashed all the things as you said ( Radio, wipe, CM, Gapps) then reboot...
I was stuck on a little Android robot just close to a white box and a yellow arrow going out the bof and going towards the robot..
Remove my battery 2 times than nothing...
Now, I wait a little bit more, then some stranges things happened ( going to HTC logo, reboot, the box and the android, reboot) and now, I have the boot animation...
All seem correct, but I was so afraid

profete162 said:
I was stuck on a little Android robot just close to a white box and a yellow arrow going out the bof and going towards the robot..
Remove my battery 2 times than nothing...
Click to expand...
Click to collapse
When you see that the radio is being flashed, it's a VERY bad idea to pull the battery at that point!

Ok, I didn't know that!
So I feel lucky, everything is fine!
Thank for the information, I won't do that again!

just flashing with a2sd.
Fingers crossed it still works
update: It works with a2sd!!
I hope it dont cause problems as that a2sd method was for the nightlys.
Has the bootimage been changed since the last nightly?

Screens please
Sent from my HTC Desire using XDA App

Restored nearly 30 apps and space is 102Mb to 69Mb. This is normal? İ checked apps and all of them on SD card.
Sent from my Desire using XDA App

Static IP with DHCP router
Hi
I still have problem with connecting wifi to a DHCP router. I tried Wifi Static to set statis ip which worked fine on the other rom, but i have never been able to use it in CM Rom
Besides, I have two APN on my 3 Network, but I can only choose 1 of them hence I cannot swap to the other one.
I'm looking for helps from everyone
Thank you.

I don't understand why you people want screenshots... it's stock Froyo in appearance, other than some blues swapped for cyans.
Can't wait to flash this. Kudos to the CyanogenMod team for all their hard work.

Is wifi sleep issue fixed?
Is vpn issue fixed?

Is that definitely the correct md5 of the Radio image?
I get:
Code:
e75698d9341820818dc7f345f48717cf
Consistently, downloaded both on-device using wget and on my PC using Chrome and wget.

[ROM] AOSP 7.x for Galaxy S 4G

Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you
* and point my finger right back at you.
*/
Installation Instructions
It will wipe your entire SD card! In order to make things work better, I've set it up to use the entire SD card as /data as opposed to having two partitions. The advantage is that you don't have to pick a size of /data.
If on a BML rom (stock-based GB)...
Untested, but is setup to hopefully work. If it doesn't flash my 6.0 Omni first
1. Reboot to recovery
2. Make sure your version of CWM is at least 5.x
3. Install zip. First time will fail and let you know its repartionning. Second time it will reboot a couple of times, don't be worried.
4. If you want gapps, reboot to recovery, wipe data+cache and install gapps.
5. If you want root, flash according to instructions in Post #3
If on an MTD rom (CM7 and all ICS+)
1. Reboot to recovery
2. Wipe data, dalvik/art cache, system, and cache partitions
3. Install zip. First time will fail and let you know its repartionning. Second time it will reboot a couple of times, don't be worried.
4. If you want root or Gapps, install them now.
The first boot can take several minutes. Be patient. If it takes 20+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess.
If you're coming from either the last Lollipop build or the initial pre-release Marshmallow build, there is a bug in TWRP that will prevent flashing anything but the ROM. To get around this, please flash the Marshmallow zip, then reboot to recovery, and then follow the typical instructions.
If you decide to install gapps at a later date (ie after you've installed the ROM), you must do a factory reset first - otherwise you will get force-closes upon bootup
If you come across a bug, feel free to let me know by posting in this thread. I will not be working non-stop on this project, but will try to fix bugs that affect me as this is still my main phone (out of choice, not necessity).
This build is very close to the official AOSP source code. Recovery is TWRP but otherwise there aren't any added "features"
Gapps eat up about an extra 30MB of RAM so they slow down the device - tread carefully. Opengapps pico works on the latest 7.0 build, untested on 7.1 but should work just fine
Backup Backup Backup! I'm not responsible for you losing any data.
Working
Camera (built-in app needs workaround, see below)
RIL
SMS
Recovery
Bluetooth - first time it won't enable if enabling through settings, back out and then second time it will. Works just fine from status bar pulldown
Wifi
Vibration
Automatic Brightness
Compass
GPS on T959P, untested on T959V
Headset Buttons
SElinux in enforcing mode - this may have broken the T959V's gps...
Partially working
Camera and Browser apps need to have all their permissions manually enabled through settings for full functionality. This is because I've used the older Camera app (which hasn't been updated for dynamic permissions) and the older Browser app as the new one is simply a test shell with no features (thanks Google!)
What's been removed
TV-Out - It was removed upstream plus I think binary blobs would need a ton of shimming in Lollipop+
Everything else is not tested!!!
XDA:DevDB Information
AOSP 7.x for Galaxy S 4G, ROM for the Samsung Galaxy S 4G
Contributors
xc-racer99
Source Code: https://github.com/xc-racer99/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Beta
Created 2016-10-22
Last Updated 2016-10-21

Thanks Time!
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to FB and Dao for their work on the CM-11 device tree. I used several of their fixes.
Thanks to noiphonehere for his device trees and kernel, most of my work was based off of his.
Thanks to the OMAP4 AOSP team for their work on porting CMA to a 3.0 kernel.
Thanks to bhundven and the other members of teamacid for their work on the aries kernel.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P and without him I'd still be on stock...
Build your own!
Follow https://source.android.com/source/initializing.html. The branch you want when you run repo init is the latest tag from https://source.android.com/source/build-numbers.html#source-code-tags-and-builds for your desired android version (7.0 or 7.1). Before you run repo sync, from the WORKING_DIRECTORY/.repo folder, run "git clone https://github.com/xc-racer99/local_manifests -b BRANCH" where BRANCH is either aosp-7.0 or aosp-7.1. Continue on with the build guide, the device codename you want is "galaxys4gmtd".
If you want to build the kernel, follow the instructions in WORKING_DIRECTORY/kernel/samsung/aries/AOSP_README. Put the resulting arch/arm/boot/zImage in device/samsung/galaxys4gmtd-kernel
Other aries devices (captivate, i9000, i9000B, vibrant) should be fairly easy to do (ie the galaxysmtd on my github as well as the captivate trees work). The fascinate and p1 would need a fair bit of work.
Changelogs
Changelog for 2016-12-19
December security patches
goes back to the older graphics drivers so hardware recording works but has a kernel patch to prevent crashes
Tweaked the graphics drivers options so it seems a little bit faster
Tweaked the RIL a little bit for better stability
Other things I've forgotten about, see github for details
Changelog for 2016-12-19-V2
Kernel without slowdowns....
Changelog for 2017-1-19
selinux to enforcing - this may break the T959V's GPS - if it does, let me know and send me a dmesg and I'll fix it
Update to the interactive governor - should have less slowdowns if using the default governor
Slightly better RIL reliability (I think)
Better low memory killing - we now don't run out of memory as often
Hardware decoding re-enabled
Slightly less intensive background services
Based on 7.1.1_r13

Source Code, Downloads, Root Options
Main Source
https://android.googlesource.com/
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd for the device tree (see aosp-7.x branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see aosp-7.x branch).
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see aosp-7.x branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see aosp-7.x branch)
http://github.com/xc-racer99/android_patches for all the patches necessary for the device to work properly (see aosp-7.x branch)
Downloads!
All builds can be downloaded from AndroidFileHost at https://www.androidfilehost.com/?w=files&flid=58191
Gapps
The smallest http://opengapps.org/ package for 7.0 is known to work, but any small 7.0 gapps package should work. However, they will cause the device to slowdown significantly as they use a fair bit of RAM. Gapps are untested on 7.1
This ROM is compatible with MicroG (https://microg.org/ and http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616) gapps. This is an open-source reimplementation of Google Play Services that doesn't track you and uses way less battery than the original.
Root
Root is achieved via Magisk or SuperSU.
MagiskDue to our odd partition layout, you need to use my custom Magisk install zip (source code here) attached to this post and not the official install or the Magisk Manager install. Then follow the instructions on how to root/install other modules from http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 Also, don't try to use the official Magisk uninstall tool as it won't work.
SuperSU
Please note: I've been told this doesn't work any more, YMMV
Again, we need a custom SuperSU install zip for it to work due to our partition scheme. It should be an all-in-one zip so it's simplier than Magisk (but not open source). This is based off of the latest (at time of writing) 2.79SR1 release, the diff is below
Code:
diff --git a/META-INF/com/google/android/update-binary b/META-INF/com/google/android/update-binary
index d437f6f..3a312bf 100644
--- a/META-INF/com/google/android/update-binary
+++ b/META-INF/com/google/android/update-binary
@@ -642,16 +642,23 @@ detect_systemless_required() {
find_boot_image
CONTINUE=true
+if false ; then
if [ -z "$BOOTIMAGE" ]; then
# no boot image partition detected, abort
return
fi
+fi
# extract ramdisk from boot image
rm -rf /sutmp
mkdir /sutmp
+if false ; then
check_zero "" "" "" "LD_LIBRARY_PATH=$RAMDISKLIB $BIN/sukernel --bootimg-extract-ramdisk $BOOTIMAGE /sutmp/ramdisk.packed"
+else
+ mount /ramdisk
+ cp /ramdisk/ramdisk.img /sutmp/ramdisk.packed
+fi
check_zero "" "" "" "LD_LIBRARY_PATH=$RAMDISKLIB $BIN/sukernel --ungzip /sutmp/ramdisk.packed /sutmp/ramdisk"
if (! $CONTINUE); then return; fi
@@ -1331,6 +1338,8 @@ else
ui_print_always "Boot image patcher"
ui_print "******************"
+if false ; then
+ # SGS Modification - we don't have a "real" boot image
ui_print "- Finding boot image"
find_boot_image
@@ -1357,6 +1366,10 @@ else
fi
check_zero_def "- Extracting ramdisk" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --bootimg-extract-ramdisk $BOOTIMAGE /sutmp/ramdisk.packed"
+else
+ mount /ramdisk
+ cp /ramdisk/ramdisk.img /sutmp/ramdisk.packed
+fi
check_zero_def "- Decompressing ramdisk" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --ungzip /sutmp/ramdisk.packed /sutmp/ramdisk"
if ($CONTINUE); then
@@ -1545,6 +1558,7 @@ else
check_zero_def "- Calling user boot image patch script" "sh /data/custom_boot_image_patch.sh /sutmp/boot.img"
fi
+if false ; then
if ($CONTINUE); then
DEV=$(echo `resolve_link $BOOTIMAGE` | grep /dev/block/)
if [ $? -eq 0 ]; then
@@ -1564,6 +1578,10 @@ else
dd if=/sutmp/boot.img of=$BOOTIMAGE bs=4096
fi
+else
+ cp /sutmp/ramdisk.packed /ramdisk/ramdisk.img
+ umount /ramdisk
+fi
rm -rf /sutmp
fi

Link for the download ROM is not working... it is private... ?!?

Here is the link to the rom that is not private https://www.androidfilehost.com/?w=files&flid=58191

pickandrew said:
Link for the download ROM is not working... it is private... ?!?
Click to expand...
Click to collapse
Shaggy_thecat said:
Here is the link to the rom that is not private https://www.androidfilehost.com/?w=files&flid=58191
Click to expand...
Click to collapse
Thanks, I used the link that I would use if I was already logged in, my bad. OP is now updated.

It's been a while, no home internet and very busy life lately but the time I did get The 7.0 zip to flash (0930) it was running very well, no random reboots and limited freezes (just 1 really)
BUT. I always reinstall a new ROM to get the process down and- I haven't been able to get it running again. Let alone with root which I haven't managed to do. When I install the ROM now it gives me a quick first boot however it says encryption unsuccessful and asks me to reset. Resetting and factory resetting as well as formatting won't help it.
Excellent work ^_^ you're becoming the new SGS4G guru around here
As for a new setting in the dev options, labeled Consistent Logging-- if I turn this on is it A: Safe in terms of information vulnerability and B: Will it fill up my SD card quickly with a mass amount of logging data?

graycow9 said:
It's been a while, no home internet and very busy life lately but the time I did get The 7.0 zip to flash (0930) it was running very well, no random reboots and limited freezes (just 1 really)
BUT. I always reinstall a new ROM to get the process down and- I haven't been able to get it running again. Let alone with root which I haven't managed to do. When I install the ROM now it gives me a quick first boot however it says encryption unsuccessful and asks me to reset. Resetting and factory resetting as well as formatting won't help it.
Excellent work ^_^ you're becoming the new SGS4G guru around here
As for a new setting in the dev options, labeled Consistent Logging-- if I turn this on is it A: Safe in terms of information vulnerability and B: Will it fill up my SD card quickly with a mass amount of logging data?
Click to expand...
Click to collapse
Hmm, flash the ROM, go into recovery, change the filesystem of /data to ext4 or f2fs. The error sounds as if the sdcard is formatted as fat while it shouldn't be. If that doesn't work, please send me the contents of /sdcard/aries_mtd.log after you've installed it.
Hadn't noticed the new "persistent logging" section. I suspect that what it does it keep the logcat contents over a reboot. Since the logcat does have a max size, it is probably safe to enable it. I highly doubt it contains any more info than a regular logcat.

Thanks for keeping this device alive in this community! My kids wanted to use it for simple games so I dusted it off and came here to see if anything was still in development and sure enough there was!
I tested going from BML stock and it worked! I had to restart the install 5 times, but it ultimately took. The first two times installed TWRP, then it rebooted into TWRP. Then it took 3 additional times before it went through the whole install. It booted up fine, but I had messed up and forgot to do a full reset before install gapps. So it would boot the encryption screen telling me it was interrupted and I had to reset the phone. Unfortunately at that point no matter what I did it would always boot to that encryption error screen. So I wiped completed and started over but mistakenly flashed the 7.1 build. It went through but was stuck on a boot loop. So now i can't install 7.0 because it keeps telling me it can't install over newer builds. Is there anything I can do to fix this or do i have to start from stock all over again?
Edited* Update
I went ahead and started from scratch but still ran in to the same problem with the encryption. Didn't install gapps this time.

Domunus said:
Thanks for keeping this device alive in this community! My kids wanted to use it for simple games so I dusted it off and came here to see if anything was still in development and sure enough there was!
I tested going from BML stock and it worked! I had to restart the install 5 times, but it ultimately took. The first two times installed TWRP, then it rebooted into TWRP. Then it took 3 additional times before it went through the whole install. It booted up fine, but I had messed up and forgot to do a full reset before install gapps. So it would boot the encryption screen telling me it was interrupted and I had to reset the phone. Unfortunately at that point no matter what I did it would always boot to that encryption error screen. So I wiped completed and started over but mistakenly flashed the 7.1 build. It went through but was stuck on a boot loop. So now i can't install 7.0 because it keeps telling me it can't install over newer builds. Is there anything I can do to fix this or do i have to start from stock all over again?
Edited* Update
I went ahead and started from scratch but still ran in to the same problem with the encryption. Didn't install gapps this time.
Click to expand...
Click to collapse
Ok, sounds like a messed up somewhere. I'll do some testing and try to release an updated build. Could you please post the output of /sdcard/aries_bml.log and /sdcard/aries_mtd.log? The "Encryption Unsuccessful" message sounds as if the SD wasn't properly formatted to ext4/f2fs.

Hi xc-racerr99, I found what the issue was. Apparently I had an extra partition on the sdcard. After removing it and running the install script again everything booted up and i'm now using the ROM! It's awesome I have Nougat on this old Galaxy S. Without Gapps it's been running really stable and very responsive..
However, at this point, I've tried opengapps pico and TKgapps pico and neither work. The script runs and says update completed, but it's too fast. When I boot to the ROM no gapps were installed. Is there another gapps you would recommend trying?

Domunus said:
Hi xc-racerr99, I found what the issue was. Apparently I had an extra partition on the sdcard. After removing it and running the install script again everything booted up and i'm now using the ROM! It's awesome I have Nougat on this old Galaxy S. Without Gapps it's been running really stable and very responsive..
However, at this point, I've tried opengapps pico and TKgapps pico and neither work. The script runs and says update completed, but it's too fast. When I boot to the ROM no gapps were installed. Is there another gapps you would recommend trying?
Click to expand...
Click to collapse
Odd, I thought my install script removed the extra partition.
Anyways, it sounds as if there's some issue with recovery. You could try replacing the ramdisk-recovery.img in the ROM zip you downloaded with the one from https://www.androidfilehost.com/?fid=457095661767105384. Then reboot to recovery and flash your gapps package again.
Doesn't work....
I'll try to do some more testing with gapps and from stock with 1 or 2 partitions when I get a chance.

I figured out a sure fire way to boot 7.0, I'm running it as I respond with XDA app right now. But to keep it short if possible, I just fix permissions then factory wipe before I run the zip- do this while on CWM right after you heimdall to BML.
So to recap:
1- Flash to stock via heimdall
2- Fix permissions + factory wipe
3- Flash 7.0 zip
4- TWRP should boot- so flash ROM once more - wipe caches
5- Reboot and chew some nougat
Will follow up with a log next time I try to get the 7.1 rolling. ?
Oh! And when I add my email (hotmail) I get a bad handshake everytime. Do I need gapps to sync my contacts?
Sent from my SGH-T959V using XDA-Developers mobile app

graycow9 said:
I figured out a sure fire way to boot 7.0, I'm running it as I respond with XDA app right now. But to keep it short if possible, I just fix permissions then factory wipe before I run the zip- do this while on CWM right after you heimdall to BML.
So to recap:
1- Flash to stock via heimdall
2- Fix permissions + factory wipe
3- Flash 7.0 zip
4- TWRP should boot- so flash ROM once more - wipe caches
5- Reboot and chew some nougat
Will follow up with a log next time I try to get the 7.1 rolling.
Oh! And when I add my email (hotmail) I get a bad handshake everytime. Do I need gapps to sync my contacts?
Sent from my SGH-T959V using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah, I get a bad handshake as well. Only happens with hotmail/oulook accounts, my gmail and my other email work just fine.
I figured out what was causing the issues with install from BML - on TWRP boot, it wasn't setting up the sdcard properly. I've now fixed it so that it should work regardless (in the next build, obviously).

Anyways, it sounds as if there's some issue with recovery. You could try replacing the ramdisk-recovery.img in the ROM zip you downloaded with the one from https://www.androidfilehost.com/?fid=457095661767105384. Then reboot to recovery and flash your gapps package again.
Click to expand...
Click to collapse
Gave this a try and still no luck.
Update **
It actually killed the recovery. Recovery just keeps crashing and rebooting when trying to get in to it. Tried it from the a clean install and same results. Will wait for your next build. Thanks for putting time in to this!

Odd, it lets me add my gmail but only syncs my emails- no option for contacts still. I ought to keep a vcf from my other device jic.
The performance is even better than M and it doesn't have the weird battery glitch anymore ?? (I think the new partition layout helped a lot.)
Another thing I noticed, sometimes my SIM won't register or gives me a no signal indicator. I can't get root still either[emoji14]still poking around. Looking forward to the next build ?
Edit: Another bug I noticed is the inability to save files through the browser or Tumblr app for example.
(By the way, just wanted to add, I hope I'm still being more help than a nag or something. I aim to be helpful. So I look for things that seem astray. Heh)
Sent from my SGH-T959V using XDA-Developers mobile app

graycow9 said:
Odd, it lets me add my gmail but only syncs my emails- no option for contacts still. I ought to keep a vcf from my other device jic.
The performance is even better than M and it doesn't have the weird battery glitch anymore (I think the new partition layout helped a lot.)
Another thing I noticed, sometimes my SIM won't register or gives me a no signal indicator. I can't get root still either[emoji14]still poking around. Looking forward to the next build
Edit: Another bug I noticed is the inability to save files through the browser or Tumblr app for example.
(By the way, just wanted to add, I hope I'm still being more help than a nag or something. I aim to be helpful. So I look for things that seem astray. Heh)
Sent from my SGH-T959V using XDA-Developers mobile app
Click to expand...
Click to collapse
I've never used the contact sync.
With SIM not registering, it's because Google introduced a bug and the workaround the bug causes the SIM to occasionally not work. One of the problems with legacy devices I guess.
With the files not saving, manually grant the storage permission in Settings->Apps - it doesn't seem to automatically update for most apps.
With root, sounds like I should modify the SuperSU install zip as it's easier to use (but not open-source). For the PHH Superuser, you need
1) The Magisk-7-SGS.zip from my thread.
2) The phh-superuser-r259.zip from the Magisk root thread (link in OP)
3) The PHH Superuser app from the Play Store or FDroid
Even then, it only works for certain apps as it doesn't mount anything to /system/xbin/su which is what some apps look for
Edit: And I have no issues if you keep posting here with the problems you find, it's good to know.

bootloop
just tried to flash this 7.1 rom from your omnirom 6.0. Seemed to flash ok as described. couldn't get pico opengapps to flash but ignored it. Now it's stuck in a bootloop and I can't get into recovery using hardware buttons. Any guidance as to how I should proceed? As a relative novice, can I push a new recovery through ADB and try again?

asmalldharma said:
just tried to flash this 7.1 rom from your omnirom 6.0. Seemed to flash ok as described. couldn't get pico opengapps to flash but ignored it. Now it's stuck in a bootloop and I can't get into recovery using hardware buttons. Any guidance as to how I should proceed? As a relative novice, can I push a new recovery through ADB and try again?
Click to expand...
Click to collapse
Well, it depends on where you are bootlooping. If you're stuck at either of the first two splash screens, then you're out of luck with ADB as it isn't available yet. If you're bootlooping but getting to the bootanimation, then you can. To do so, run
Code:
$ adb root
$ adb shell mkdir /data/ramdisk
$ adb shell mount /dev/block/mtdblock5 /data/ramdisk
$ adb push ramdisk-recovery.img /data/ramdisk
$ adb reboot recovery
where ramdisk-recovery.img is from the AOSP 7.0 zip.
If you're stuck at the first or second splash screens, then you need Odin or Heimdall. With heimdall, you can do
Code:
$ heimdall flash --KERNEL boot.img
where the boot.img is the one from Omni 6.0, the one from 7.x won't work on its own as the recovery is not stored in it. You can use Odin to go back to stock.
I haven't tried gapps so I guess I should sometime and see what the issue with them is.

Gets to the second splash screen. I'll give that a shot when i have some free time. I'm really looking forward to getting this working as I'm amused by the idea of my oldest android phone running the newest OS before my other two.
Update: couldn't get it to work with my cheap laptop. Kept throwing up the libusb 12 error. Then when i finally gave up and pulled the battery, I noticed it was starting to bulge a little. I think I'm out for a while. I'm hoping i can come back to this soon.
Sent from my A0001 using XDA-Developers mobile app

[ROM][7.1.2] AOSPA Paranoid v7.3.1 for Honor 6x

Paranoid Android is a custom ROM aiming to extend the system, working on enhancing the already existing beauty of Android and following the same design philosophies that were set forward by Google for Android Open Source Project.
Code:
* Your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
Compatible device?:
Code:
[LIST]
[*]All devices that use hi6250 chipset and use kernel 4.1.
[/LIST]
Mandatory:
* hit thank buttons, it's free.
* want more roms for P8 Lite 2017/P9 Lite 2017, simply bring me up beers by the following button.
Requirements:
TWRP.
Unlocked bootloader.
Unlocked FRP.
vendor.img: you must be on stock one, so don't wipe it because with other custom vendor.img will never ever boot.
This ROM is provided by CodeOfHonor​
Installation Guide:
Make sure to the stock backup saved on pc, I'm not responsible for any bricked or damage.
Reboot to TWRP.
Go to Wipe.
Choose Advance Wipe.
Check on Data and change file system to EXT4, will not ever boot with F2FS.
Wipe cache, data, dalvik and system.
Flash the rom.
Reboot and have fun then.
Working:
Audio.
Bluetooth.
Camera: it's fully works with stock or other apps .
Display.
Graphis: both gralloc & hwcomposer.
Lights.
NFC.
RIL.
Sensors.
Storages.
Wifi
Bugs:
Dual sim might will not work all variants, so don't waste your time by asking me to fix it.
You don't like it?, easy revert to Emui 5.x.
Downloads:
**13/05/2018**
pa_hi6250-7.3.1-EOL-20180513.zip|500.4 MB
Changelogs:
**13/05/2018**
Boot with F2FS without problems.
Fix Magisk.
Source Code:
Device Tree:
https://github.com/codeofhonor-dev/android_device_huawei_hi6250
Kernel GPL:
https://github.com/codeofhonor-dev/android_kernel_huawei_hi6250
Vendors:
https://github.com/codeofhonor-dev/android_vendor_huawei_hi6250
XDA:DevDB Information
AOSPA Paranoid for Hi6250, ROM for the Honor 6X
Contributors
haky 86, HassanMirza01, felix-development
Source Code: https://github.com/codeofhonor-dev, Meticulus and the stuff of CodeOfHonor.
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: Emiui 5.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 7.3.1
Stable Release Date: 2018-04-27
Beta Release Date: 2018-04-27
Created 2018-04-27
Last Updated 2018-04-27

ROM stuck at animation boot?
this because you must change the file system from F2FS to EXT4 to done boot process
* reboot to TWRP.
* go to Wipe -> Advanced Wipe.
* check Data -> Change file system -> select EXT4.
* swipe the screen to wipe it .
How can I fix Sim?
* go to Settings -> Extras -> disable "Sim Card Slot2 " and reboot.
How can I enable Google Codecs
* go to Settings -> Extras -> enable "Use Google H264" (it's a bit laggy but better than nothing).
How to enable Double Touch To Wake?
* go to Settings -> Extras -> enable "Double Touch to Wake"
Should I reflash the vendor partition if come from other roms?
* if you coming from Emui 5.x, the answer is no because the custom rom are based on Emui 5.0 source code, so all you
have to is flashing your favorite custom rom
Audio and camera are not working?
* bring up a logcat to help us, instead of writing useless comments.
I got error 7, how can I fix that?
* use my own TWRP recovery. or you can simply remove the whole assert line in the updater-script file inside the META-INF folder save and re-flash.
How can I fix RIL Crashes
flash root.
Copy the phone.prop into /system/vendor and /vendor.
reboot, now you should able to do calls for more than 2 minuts
Calls still crash even with fix SIM
Run adb shell and type the following command xxd /sys/firmware/devicetree/base/hisi,modem_id .
the result will be something like the following out ( for single sim devices):
1|hi6250:/ $ xxd /sys/firmware/devicetree/base/hisi,modem_id
00000000: xxxx x000 ;xx.
Click to expand...
Click to collapse
Search for your xxxxx000, and setup the following flags .
ro.config.client_number=1
ro.config.modem_number=1
persist.dsds.enabled=false
persist.radio.multisim.config=dsds (remove it properly)
for dual sim devices just edit these 2 flags:
ro.config.client_number=1
ro.config.modem_number=1
Save and reboot.

I'm coming from EliteRom 7.5 and I love AOSPA but there are 2 little problems I have with this rom.
First of all fingerprint doesn't work correctly, no matter how often I press my finger on the sensor it stays at the ~10% mark.
The other problem is that I don't know how to root this rom. I tried installing magisk manager and flashing the zip but I get error 1 in TWRP.
Except this issues it's working very nicely on my device.
Thanks in advance for helping me out

MadMurl0c said:
I'm coming from EliteRom 7.5 and I love AOSPA but there are 2 little problems I have with this rom.
First of all fingerprint doesn't work correctly, no matter how often I press my finger on the sensor it stays at the ~10% mark.
The other problem is that I don't know how to root this rom. I tried installing magisk manager and flashing the zip but I get error 1 in TWRP.
Except this issues it's working very nicely on my device.
Thanks in advance for helping me out
Click to expand...
Click to collapse
10% mark?
Did you entirely remove all the fingerprints before flashing this Tom?
Go back to Elite or Stock, remove all fingerprints and reinstall the Rom
For Root, you can try changing recovery or using an older version of Magisk that worked for you

I am currently reverting back to stock and will try to flash the rom again, I guess I didn't remove the fingerprints before flashing.
I tried Magisk Version 15 and 16 which both worked on EliteRom, I even tried SuperSu which didn't gave me an error message in twrp but It didn't work tho. After flashing the zip there was no "SuperSu" App so I downloaded it from the playstore, the app told me "root not found". Do you know what the cause of this could be?
Edit: Fingerprints are working now But root still doesn't

After I downgrade from emui 8 to emui 5 in 5 minutes now I can fix this rom so expect a build within these days

hoping to try this rom , following for updates

Hey guys I just installed the rom, but I did notice that I don't have access to any Gapps. How to I install them? I'm using TWRP. I was just able to get my unlock code from Honor today, so I unlocked and rooted, and flashed your rom as the first thing, so I'm running a fresh flash of the latest version.

Flash package with Twrp: https://opengapps.org/

Thanks guys, I realized that yesterday right after I posted lol. So far I'm really loving the plain stock-ness of this rom, hopefully it give the device some more life so I won't have to upgrade soon.

MadMurl0c said:
I am currently reverting back to stock and will try to flash the rom again, I guess I didn't remove the fingerprints before flashing.
I tried Magisk Version 15 and 16 which both worked on EliteRom, I even tried SuperSu which didn't gave me an error message in twrp but It didn't work tho. After flashing the zip there was no "SuperSu" App so I downloaded it from the playstore, the app told me "root not found". Do you know what the cause of this could be?
Edit: Fingerprints are working now But root still doesn't
Click to expand...
Click to collapse
Yeah I'm having the same issue to, with no root.

Can someone tell me why this rom is different to all others ? Why is this one using stock vendor and can we easy revert to Emui ? Why don't all others ?
I'm on stock now.

How is the quality of the photos compared to stock rom? It is possible to install Emui camera or other huawei cameras?

** Note **
developments of hi6250 is end reason: switch to another phone, have phone.

** Note **
Developments for hi6250 has been resumed but just for this ROM, sorry for the inconvenience.
I'm already downloading the source for releasing new build but AOSPA will take a wile since have bigger source.

** Note **
Downloads:
**13/05/2018**
pa_hi6250-7.3.1-EOL-20180513.zip|500.4 MB
Changelogs:
**13/05/2018**
Boot with F2FS without problems.
Fix Magisk.

Had anyone tried installing Xposed yet?

Support BLL version? Honor 6X

The rom overall is great and smoorh, even F2FS works now
But somehow magisk still doesn't work. It says
Code:
! System installed root detected, mount rw :(
when I try to flash the magisk.zip file.

MadMurl0c said:
The rom overall is great and smoorh, even F2FS works now
But somehow magisk still doesn't work. It says
Code:
! System installed root detected, mount rw :(
when I try to flash the magisk.zip file.
Click to expand...
Click to collapse
Guys to flash magisk or superSU use Meticulus TWRP, other twrp like eliteTwrp show an error when it is recompilling the boot.img

LineageOS 14.1 for Samsung Galaxy Core Plus

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* DO NOT LEECH MY DOWNLOADS, PLEASE RE-DIRECT YOUR FORUM/PAGE
* TO THIS THREAD, IF YOU LIKE MY WORK, YOU CAN SAY THANKS
*/
Introduction
This is a UNOFFICIAL build of LineageOS for the Samsung Galaxy Core Plus.
It's not ready yet and has some bugs in it which could cause problems to some users.
The ROM will only work on the SM-G350 Version of the Phone (without any Numbers/Letters behind).
This ROM is not ready for daily use in all cases (look at the list of what doesn't work before flashing it).
Stuff that DOESN'T WORK
Video recording
Wi-Fi tethering
USB tethering
Probably some other stuff
Stuff that WASN'T TESTED
EMERGENCY CALLS
Bluetooth tethering
Installation Instructions
Special thanks to @Giovix92 for making this tutorial!
Requirements:
1: A computer with Windows.
2: An Internet connection.
3: A backup of your phone data (contacts, photo, music, videos, and other).
4: About 400 MB free space on your SD card.
5: Phone charged at least 80%.
Download links are below
I do NOT take any responsibility for bricked devices!
Let's start!
1: Download the Samsung USB Drivers.
2: Download the ODIN3. (Only for Windows)
3: Download the TWRP Odin package to your desktop and download the LineageOS 14.1 zip to your SD card.
4: Make a backup of your files, because the storage will be wiped. (External SD card will not be wiped)
5: Reboot your phone in to the Download mode (Volume Down- , Home- and Power button). Press the Volume Up button when asked. Then open the ODIN3 and connect your phone to your PC.
6: Press AP and choose the TWRP Odin package (recovery.tar) and make sure re-partition is NOT ticked. "Auto-Reboot" should not be ticked either, otherwise you will need to be quick to boot into the recovery immediately after flashing.
7: Press start! Wait a few seconds. Then your phone will be rebooted. Now you can disconnect the cable and power off your phone.
8: Boot your phone in to the TWRP Recovery (Volume Up-, Home- and Power button).
9: Go to Wipe, and Swipe to Factory Reset.
10. After wiping go to the home screen by pressing the home button.
11: Go to Install. Choose the "external_sd" from the top bar. (It says "Storage: Internal Storage (xxxxMB)" by default)
12: Choose the LineageOS 14.1 ZIP and Swipe to Confirm Flash. Make sure you don't power off while flashing!
13: After the zip has been flashed choose "Reboot System".
14: Wait 5-15 minutes to boot the phone. If the phone keeps booting take out the battery and do a Factory Reset again.
15: When the phone boots the first time, go through the Setup Wizard and you are ready to use your phone!
If there was something you didn't understand, please don't hesitate to ask
Changelog
2022-04-03:
Update Chromium WebView to 99.0.4844.73
Emulate missing sdiv/udiv instructions
2022-02-13:
Fix playing audio and system sounds
Fix offline charging
Update Chromium WebView to 97.0.4692.98
Removed the custom wpa_supplicant.conf file (this may solve the issues with some users not having Wi-Fi without deleting that file first)
2018-05-28:
Initial release
Downloads
Samsung USB Drivers
Odin v3.13.1
TWRP 3
lineage-14.1-20220403-UNOFFICIAL-cs02.zip
Source
Device tree
Kernel tree
Proprietary files
WebView
Thanks To/Credits
Thanks to ...
... androidlover5842, ishantvivek, SandPox, ZIM555 and everyone else working on Samsung's hawaii-Boards
... berkantkz and santeri3700 for teaching me the basics of ROM developing and their work on the SM-G350

The video codex work ?

HiR3x said:
The video codex work ?
Click to expand...
Click to collapse
No. Check the OP for what's working and what isn't.

Update?
A lineage 14 for the core plus?Amazing
Is possible to install(maybe ota updates) this rom from the older one (lineage 13)?

KevinSmith21 said:
A lineage 14 for the core plus?Amazing
Is possible to install(maybe ota updates) this rom from the older one (lineage 13)?
Click to expand...
Click to collapse
I didn't try it, but it should work (no guarantees though, I'm not responsible for any data loss). Make sure to do a backup anyways.

TimSchumi said:
I didn't try it, but it should work (no guarantees though, I'm not responsible for any data loss). Make sure to do a backup anyways.
Click to expand...
Click to collapse
Got it,thanks for the rom

The rom its super smoth and its mutch bater then LineageOS 13 but wifi dont work i dont know way

HiR3x said:
The rom its super smoth and its mutch bater then LineageOS 13 but wifi dont work i dont know way
Click to expand...
Click to collapse
Wi-Fi works for me out of the box. I guess you could try what people in the LineageOS 13.0 thread already tried and delete the wpa_supplicant.conf file (I think it is located in /data/misc/wifi/).

Very good rom, congrats @TimSchumi !

I just noticed that there is an incompatibility with GApps packages. If you flashed GApps and now your Keyboard constantly crashed, simply delete /system/lib/libjni_latinimegoogle.so from TWRP (make sure to mount /system first). I'll include the fix in the next build (whenever that may be).

SIM
For me everything is good but SIM card is not detected
Bt, wifi, flshlight, photos with flash... Only video recording and codecs...
It's fine when I can play music but not necessarily

Excellent
Great ROM for the old phone!
And with SD card as internal memory gives plenty of space for apps! Now the phone is usable again after cyanogenmod 13 before.

akagisan said:
Great ROM for the old phone!
And with SD card as internal memory gives plenty of space for apps! Now the phone is usable again after cyanogenmod 13 before.
Click to expand...
Click to collapse
Was LineageOS 13.0 really _that_ unusable? I assumed that the bugs that 14.1 has right now would be a huge deal breaker. Also, that SD-Card as Internal storage thing is just one buggy mess. Don't use it.

Hallo,
great work so far .
Any chance that it becomes official in foreseeable future?

PackElend said:
Hallo,
great work so far .
Any chance that it becomes official in foreseeable future?
Click to expand...
Click to collapse
It will probably never be official. There are a lot of serious bugs, my testing device is currently out of commission, the "official" 14.1 cycle won't last mich longer and I suspect that (if I manage to fix the previously mentioned bugs) the codecs are again near unfixable.

TimSchumi said:
the codecs are again near unfixable.
Click to expand...
Click to collapse
Sad to hear that switching to 15.1 isn't an option?

TimSchumi said:
It will probably never be official. There are a lot of serious bugs, my testing device is currently out of commission, the "official" 14.1 cycle won't last mich longer and I suspect that (if I manage to fix the previously mentioned bugs) the codecs are again near unfixable.
Click to expand...
Click to collapse
Well...every app with build-in(i think) codecs like VLC or mx player work...but can't watch memes on other apps:silly:

I installed this rom, its amazing way better than Lineage OS 13 However , when i play a youtube video it dosen't play at all but when i play a video in chrome it plays it completely fine
Any Fixes?

Apher said:
I installed this rom, its amazing way better than Lineage OS 13 However , when i play a youtube video it dosen't play at all but when i play a video in chrome it plays it completely fine
Any Fixes?
Click to expand...
Click to collapse
It seems that video codecs are buggy...for yt videos i download them and watch them with vlc(or any other app with integrated codecs)

Is there to fix that if the phone gets discharged to 0% it gets bricked?

[A11] [R] [ARM64] [A40] AndroidOpenSourceProject - AOSP - Vanilla - feel the pure Android

Code:
/* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What is AOSP?
AOSP (Android Open Source Project) is Android just as Google publishes, without any other modifications or additions. More or less AOSP is the Pixel devices stock ROM without gapps and proprietary additions. Check out the screenshots to know more!
What's working?
Boots
RIL (Calls, SMS)
Mobile data
Bluetooth
WiFi/hotspot
Media (audio/video)
Camera
Camcorder
GPS
Fingerprint
NFC
Sensors
etc.
Bugs?
BT CALLS/voWiFi/voLTE
How to install?
Wipe system, data, dalvik's cache and cache Do not wipe vendor
TWRP:Install > select Image > select if they ask "system" select System and then the AOSP_A40......Image > install
Ofox: Tap on the Image > As system image
Reboot recovery
Flash Gapps
reboot system
Enjoy the goodness of Android 11.
Downloads
ROM: AOSP_VANILLA_STOCK_A40_R [Systemimage only]
Screenshots
Attachment
Sources
https://github.com/aosp-mirror
NOTE: For reporting any bugs, describe the issue properly and make sure to accompany it with a logcat. Without a logcat, bugs cannot and will not be fixed.
Don't forget to hit the thanks button to show love and support my work.​
XDAevDB Information
AOSP 11.0, ROM for the Samsung Galaxy A40
Contributors
Kevios12
Source Code: Kernel Tree
ROM OS Version: 11.0.0
ROM Kernel: Linux 4.x
ROM Firmware Required: OneUI 2.0 or ALT+F4
Based On: AOSP
Version Information
Status: Stable
Created 2021-04-30
Last Updated xxxx-xx-xx

(Based On: AOSP) Roms unfortunately do not have the option to make sim2 passive while sim1 is active (or vice versa). Is there a solution to this?

I have installed the ROM with TWRP and my phone is now bricked, I cannot even get into TWRP anymore. Any idea what I could do now?
- Install order was: Unlocked bootloader, used Odin to install TWRP, flashed Multidisabler, reboot, then followed the instructions here
- Black screen followed the "reboot" button in TWRP
- I can reboot the phone by pressing all three buttons but this will only give me the Samsung warning I have to confirm and then black screen again
- this phone uses Exynos CPUs
- OneUI 3.1 was installed before. Is that the issue? I read "Firmware required" as "Minimum Firmware required"...
Edit: I can NOT reboot the phone while a USB cable is plugged in.

Yes OneUI 2.0 is required. OneUI3 FW is GAY! And you can go instand to twrp by pressing power + vol - then if restart hold power+vol+ if samsung logo come, release powerbutton and wait. Have u the A40 for sure? the rom is testet and works, nobody has a brick or whatever. Flash This image as system_image only no wipe vendor or everything btw. look in other treads for my custom vendor it will works.

kevios12 said:
Yes OneUI 2.0 is required. OneUI3 FW is GAY!
Click to expand...
Click to collapse
So I managed to flash OneUI 2.0 and then repeated the whole process and now your ROM boots. I can't connect to WIFI though (yes I made sure I used the correct password). It just says "connecting failed". Also, when I call someone, there is no call window. Is this ROM compatible with FlameGApps?
Also, yes, definitely the A40.

only u can Try gapps idk if flame works. did u use WPA2/3? combinied

My router uses WPA2/3 combined and Android does not give me an option.

I was now able to connect to another Wifi and tried to update my apps. It tells me I had not enough space. But I have over 50 GB free.
Edit: So, the Wifi problem depends on encryption. WPA+WPA2 works, WPA2+WPA3 does not work. I think that is a bug.
Also, I cannot get Play Store to install anything. It always complains about not enough space despite me having no apps installed and lots of free space on both internal and external memory. Cleaning cache did not help. This happens with both NikGapps and FlameGApps. FlameGApps works way better though.

Also explaine better, it should work maybe bug of gapps

I tried the rom , but it’s stuck on the android logo , any help?

Have u installed vendor? ... the custom one

kevios12 said:
Also explaine better, it should work maybe bug of gapps
Click to expand...
Click to collapse
Possible, but I do not know. Might also be partitioning. I did nothing but flash ROM and flash Gapps, then boot and run through the Gapps initial setup tool that automatically started (connect wifi etc). Then I tried to install any app from the Play Store. It always says I need to free up space before I can install an app. But I have lots of space, tens of GB.

hmm thats weird

It is weird indeed... also, are there known issues with phone calls with a Bluetooth headset? I couldn't use mine today, even though it was properly connected.

kevios12 said:
Have u installed vendor? ... the custom one
Click to expand...
Click to collapse
I did

CozmoGM said:
I did
Click to expand...
Click to collapse
Nevermind , i think i did something wrong , but i reflashed the rom and everything and now it works.

Konzertheld said:
It is weird indeed... also, are there known issues with phone calls with a Bluetooth headset? I couldn't use mine today, even though it was properly connected.
Click to expand...
Click to collapse
known bug, like voLTE/voWIFI/BT CALLS BUG/EXYNOS WONT WORK

kevios12 said:
known bug
Click to expand...
Click to collapse
So... please put that in your description above instead of stating "bugs: none". Other ROMs named the bug with Bluetooth etc and yours didn't, so I assumed it was not relevant. I would not have downloaded it if I knew.

Konzertheld said:
So... please put that in your description above instead of stating "bugs: none". Other ROMs named the bug with Bluetooth etc and yours didn't, so I assumed it was not relevant. I would not have downloaded it if I knew.
Click to expand...
Click to collapse
Well the problem is when you are developer & tester at the same time, because nobody feels like doing it, or you really do everything alone ... mistakes can happen!