the original OP is VERY confusing. Take a look for credits sake though. I am putting a link to the download page below it.
I DIDN'T MAKE THIS ROM! All credit for the Droid Razr M build goes to elros34, also please thank vevgeniev for making the Photon Q port.
JBBL ONLY!!! -- I MIGHT be tempted to try and build a KKBL port if enough people are interested, but at the moment, JBBL works flawlessly, and a few KKBL users downgrading their Boot loaders is way easier than me building a whole new (most likely) barely functioning port just for KKBL, when we already have a great JBBL port
What works:
Camera
Wifi
GSM: Everything works, including calls, data, and text
CDMA: I don't use CDMA but as far as I know, only calls work.
Vibration
Audio and Video
>>*when using the YTPlayer app, turn off early video loading in Settings>Player>Early video loading = set it to "Never"*
USB MTP to both my PC and my Chromebook.
What doesn't work:
nothing, this is a ROCK SOLID PORT!
you have to first flash CM11, and then flash sailfish over it.
So I was browsing around the Photon Q xda page and saw this gem. I would have passed it over and just thought "neat" and moved on, but as I skimmed the page I saw that it is based on msm8960_jbbl sources, so it theoretically works on all unified msm8960 devices on jbbl. I actually read the OP and low and behold there is the RAZR M on the list of supported devices. I didn't make this (obviously) but definitely swing by the original thread and take a look.
NOTE: THE PHOTON Q PORT WON'T BOOT ON THE XT907 OR XT905 - Please use the elros34 build linked in the Direct Download links section.
https://forum.xda-developers.com/photon-q-4g-lte/general/sailfishos-2-0-motorola-photon-q-t3281262
http://www.vladislavonline.com/sailfishos-for-photon-q/
DIRECT DOWNLOAD LINKS
CM11 BASE [ https://archive.org/download/cmarch...626-SNAPSHOT-XNG3CAO1L8-moto_msm8960_jbbl.zip ]
Sailfish OS 2.1.3.7 alpha3 xt907 [ https://goo.gl/DJ8zre ] || Mirror [ https://onedrive.live.com/?cid=f188cb653189eae0&id=F188CB653189EAE0!403&authkey=!AGtl3flkGPJHaiE ]
rahimali AFH: [ https://androidfilehost.com/?w=files&flid=236124 ]
Headphone Jack fix for xt907 ---> HEADPHONE JACK FIXED IN ALPHA BUILD 3, THANKS elros34!!!
tested and working on the alpha 2 build, thank elros34 for this not me, he is the genius behind this one, think of me as a parrot.
You need to either use ssh on your computer, or the terminal app on your phone. You also need to set a root password in Settings -> Developer Options
devel-su
[input root password]
vim /etc/ohm/plugins.d/accessories.ini
*you'll see 4 lines, one of witch being Jack Match = /dev/input/event5 (or something similar, you'll see it, it should be the last line in the file)
*enter the letter "i" to edit
*replace "/dev/input/event5" with "/dev/input/event4"
*enter CTRL+C
*enter ":", and enter "write"
*now hit ":" again and enter "quit"
reboot your device and now headphone jack should work, hooray!
I DID NOT MAKE THIS!!! I AM SIMPLY LINKING IT FOR OTHER XT907 USERS TO ENJOY! CREDIT TO elros34 FOR THE PORT TO THE RAZR M, AND vevgeniev FOR MAKING THE PHOTON Q PORT!
The link doesn't seem to work. Says an error has occurred.
link is not working
faisala66 said:
link is not working
Click to expand...
Click to collapse
Ill update it :good:
The one drive links works fine on my chromebook, but Ill replace it with the direct one I find in the thread.
I've shared the files here
it is for kkbl?
faisala66 said:
it is for kkbl?
Click to expand...
Click to collapse
Nope. JBBL only.
rahimali said:
Nope. JBBL only.
Click to expand...
Click to collapse
but it says it is for kkbl and I have also installed in my phone in KKBL
faisala66 said:
but it says it is for kkbl and I have also installed in my phone in KKBL
Click to expand...
Click to collapse
Good for you! :good:
rahimali said:
Good for you! :good:
Click to expand...
Click to collapse
thanks but its not booting
faisala66 said:
thanks but its not booting
Click to expand...
Click to collapse
So what do you expect if you don't follow instructions?
rahimali said:
So what do you expect if you don't follow instructions?
Click to expand...
Click to collapse
sorry sorry i wlashed wrong CM11 snapshot (msm8960) it is for (msm8960jbbl) right:laugh::good:
its working great. but it is not android rom and i cant run apk
faisala66 said:
thanks but its not booting
Click to expand...
Click to collapse
then it's obviously only for jbbl, switch to jbbl if you want to use this, its a real quick 10 minute process, and since this is a GNU/Linux rom, the downgrade won't do much.
faisala66 said:
its working great. but it is not android rom and i cant run apk
Click to expand...
Click to collapse
well yeah, it isn't an android rom, so you won't be able to run android apps. It is a GNU/Linux based OS, the only way you will be able to run android apps is if you somehow hack in alien dalvik (edit platform manifest file, cross your fingers), or get one of the other android emulators set up. The reason you use Sailfish OS is because it is lightweight, fast, and a generally beautiful and fun to use OS.
It's stuck in the bootlogo here.
I used the CM11 mentioned in the OP (from here), SailfishOS 2.0.1.11 (from here) and ilichva's TWRP 3.0.2-1 (DiamondJohn's TWRP 3.1.1-1 failed with error 7). Both data and system partitions are ext4. Am I missing something? Thanks in advance.
hernandezjonathan21 said:
It's stuck in the bootlogo here.
I used the CM11 mentioned in the OP (from here), SailfishOS 2.0.1.11 (from here) and ilichva's TWRP 3.0.2-1 (DiamondJohn's TWRP 3.1.1-1 failed with error 7). Both data and system partitions are ext4. Am I missing something? Thanks in advance.
Click to expand...
Click to collapse
you are on JBBL right? I used that same zipe and rootfs and all is good.. you flashed the cm zip, then the sailfish zip on top without wiping anything right? and you wiped all your partitions (except internal and external sd of course) before hand?\
EDIT: You are using a photon Q build on xt907, no wonder it won't boot. grab the one from the bottom of the rahimali afh link or the xt907 one in the downloads section.
Galaxyninja66 said:
you are on JBBL right? I used that same zipe and rootfs and all is good.. you flashed the cm zip, then the sailfish zip on top without wiping anything right? and you wiped all your partitions (except internal and external sd of course) before hand?\
EDIT: You are using a photon Q build on xt907, no wonder it won't boot. grab the one from the bottom of the rahimali afh link or the xt907 one in the downloads section.
Click to expand...
Click to collapse
Alright, gotta try it ASAP (which means in a week or two :crying. Any fixes for the headphone jack?
EDIT: Nevermind, I just saw the updated OP. Now this is looking reaaaally good for a daily driver.
hernandezjonathan21 said:
Alright, gotta try it ASAP (which means in a week or two :crying. Any fixes for the headphone jack?
EDIT: Nevermind, I just saw the updated OP. Now this is looking reaaaally good for a daily driver.
Click to expand...
Click to collapse
headphone jack is being patched in the new update, elros34 should release it by tonight, he was messing with it on the IRC (it'll be based on the newest version of sail and have fixed headphone jack built in, hooray!!! )
I'm replying from Sailfish in my XT907! I tried to install the alpha 3 from @rahimali's folder and it didn't boot (I wasn't surprised though, as it said it was for XT897).
Battery seems to last waaay more than Android and it's really fun to use! I just need to find a way to use WhatsApp.
Related
For 4 weeks ive been looking at KK and playing with source... 4.4 images Build (ota zip fails)
4.4 images are building im coming here for developers help on getting this rom working
i will continually post here my sources (this is an awesome forum) and my progress as i go on.. been at this for over 4 weeks developing my first rom...
this post will get more colorful and easier to read over time:
Below is a quote from my google+ post on Xoom Community (join it.. its a great place)
STATUS UPDATE:
Xoom Wifi - LIFESTREAM ROM by LOGMD
Build 17 - Failed BUT we have:
-boot.img
-system.img
-kernel (supposedly)
I have managed to extract the system.img into a flashable Zip... but i KNOW the permissions are F*%#ked
I installed boot.img manually using fastboot but its left me in bootloops (not actually getting to the boot animation, looping on the moto logo)
i flashed the 4.2.2 EOS4 BigPart image because its compatible with the new partition layout and it doesnt bootloop... but it also doesnt get to bootanimation either...
BUT it did respond to ADB devices and came up as unauthorized device so obviously when i ADB SHELL it says device unauthorized...
I THINK that i need to build the boot.img with the BigPart patch but im not sure even if the kernel is just not working properly. if ive built it properly or whatever...
IF ANYONE knows any xoom developers or you are a xoom developer and know how to build kernels on a version of android thats not supported officially or if you think you could help me out then im all ears
Click to expand...
Click to collapse
BIG THANKS to the BigPart & 4.3/4.4 dev thread (will add links later) would have been stuck at one of the many roadblocks if it wasnt for these people!
we are getting closer to getting a rom working i can feel it! lets make it happen! loving how live the threads are in this forum for the xoom!
PROGRESS
I will update here the overall progress towards a working rom WHEN i get time as work can get very busy. I will not be selfish and steal peoples ideas if they are the ones who invented it then i will give credit where it is due, and it is possible that this rom could never be built or someone beats me to it. I may end up collaborating with someone with more experience on thier rom but ill do my best to get an edition of my own working.. IF all fails for now with 4.4 i will spend time on a 4.2 rom/kernel
DISCLAIMER
I (LOGMD) 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 the products you find here 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. Your warranty will be void if you tamper with any part of your device / software. In saying that Enjoy a respectful development environment, expect no ETA's and help me where necessary
REPARTITION
SYSTEM.IMG
BOOT.IMG (kernel, ramdisk etc)
THREADS OF LIFE (words stolen from Shadows Fall Album)
This is where you and I should use as a starting point for homework using the communities are a great way to learn the newest up to date developments! I do not read fiction books but I sure as hell read technology!
GOOGLE+
+LOGMD | +XDADevelopers | +XoomOwners
XDA-Forums
BLOG
OTHER (follow me)
Twitter | Facebook
I wish you luck. As your skill and luck is our luck.
Sent from my Xoom using XDA Premium HD app
subbed! anticipating great things!
way to be!! Super excited. Need guinea pigs? I'll help
sbeaber4 said:
way to be!! Super excited. Need guinea pigs? I'll help
Click to expand...
Click to collapse
ill start uploading some system img zips soon. see if i can take anything more out of android that is not essential to makeing it work i.e. NO BROWSER NO PLAY STORE everything gone, i was told by another developer they have managed to get the rom small enough for fastboot (~251MB) so ill try the same so it will be easier to flash!
I stupidly did not reserve posts so heres one more
boot.img
For the kernel, why don't ask to ElementalX ?
If we have a system.img but it's to large to flash through fastboot,
thinking out loud but could we get it connected via adb in recovery and do the dd if=/location/of/system/img of=/dev/block/mmcblkpXXX
would that work?
---------- Post added at 11:52 AM ---------- Previous post was at 11:48 AM ----------
Another thought on trying to get the img into a flashable zip, not sure if you've heard of dsixda kitchen! http://forum.xda-developers.com/showthread.php?t=633246
I've used it before in regard to the Xperia T and it's compatible with many devices and can turn system imgs into zips I believe
If using bigPart Kernel than you can not use fastboot as fastboot does not know the new partition layout.
Incredible news!!
Love to see KitKat on Motorola Xoom!
Sent from my Xoom using Tapatalk 4
Have you tried using Motorola's mfastboot.exe? I've had to use that instead of the regular fastboot to flash large system images to my Moto X, I'm curious if it would work for the repartitioned Xoom. Apparently it breaks the image down into two parts to get around size limitations with the regular fastboot.
I uploaded it here if you'd like to test it out
TWRP
So we partitioned the Tab with 1000 Mo for system, i'm not sure it's necessary, i read it's possible to reduce the size of the ROM under 256 Mo
I have a old Samsung Galaxy Ace and for this old tool on Jenkins the 4.4 cooper is compiled but not flashable because no recovery adapted to flash it.
I visit a lot of site like Mclaw studio and see for each ROM kitkat it's a special TWRP dedicate specialy to kitkat ROM.
So do you thing we need another TWRP or the TWRP big part is ok?
pots22 said:
So we partitioned the Tab with 1000 Mo for system, i'm not sure it's necessary, i read it's possible to reduce the size of the ROM under 256 Mo
I have a old Samsung Galaxy Ace and for this old tool on Jenkins the 4.4 cooper is compiled but not flashable because no recovery adapted to flash it.
I visit a lot of site like Mclaw studio and see for each ROM kitkat it's a special TWRP dedicate specialy to kitkat ROM.
So do you thing we need another TWRP or the TWRP big part is ok?
Click to expand...
Click to collapse
I managed to shrink to 209 MB which flashes =] it may not have anything but core android but thats all we care about right now i dont care about FC... next is kernel follow this link will be more active about kernel updates. im gonna post some nvidia drivers i just found
Elemental-X seems to have updated to beta with support for big partition.
4.4
hawkstorm said:
Elemental-X seems to have updated to beta with support for big partition.
Click to expand...
Click to collapse
Exactly, http://www.androidfilehost.com/?fid=23252070760974877
Now we have a bigpart partitioning, a bigpart Kernel
So what needed for start a 4.4 kitkat test build?
pots22 said:
Exactly, http://www.androidfilehost.com/?fid=23252070760974877
Now we have a bigpart partitioning, a bigpart Kernel
So what needed for start a 4.4 kitkat test build?
Click to expand...
Click to collapse
Technically we didn't even need the big part
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Cameron581 said:
Technically we didn't even need the big part
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Well, the dev said that he needed to remove a few things to get it to flash. Maybe now he can reinsert whatever he removed and check whether it can flash.
hawkstorm said:
Well, the dev said that he needed to remove a few things to get it to flash. Maybe now he can reinsert whatever he removed and check whether it can flash.
Click to expand...
Click to collapse
That makes no sense he removed apps and was on a parted kernel
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Experimental X was just updated to support Bigpart. It is not the update that Logmd is looking for to support KK 4.4. The new kernel needs a lot more upgrading involving drivers for the Tegra Chip.
They are probably trying to see if they can get KK 4.4 working without bigpart first. And if successful it can blossom from there with ROM developers taking advantage of BigPart to create more custimized ROMS.
4.4
Cyanogenmod launch from yesterday and today a lot of ROM CM11 4.4.2
http://download.cyanogenmod.org/
All ROM don't exceed 200 Mo, so i'm really not sure about the necessity of Bigpart.
Hello! I'll be posting pure AOSP builds whenever there are new versions of android released (providing I have the time).
If you choose to use these builds, please ensure you have unlocked your bootloader and have custom recovery installed. I have also noticed that TWRP seems a little wonky at this point, so in order for me to flash it correctly, I had to wipe, then restart recovery, then flash. Hope that's not the case for everyone else.
3/18/15
Added ability to change DPI.
3/15/15
No longer messes with recovery at all. Bluetooth working, data does not force encrypt.
3/13/15
Android 5.1.0_r1 (LMY47D)
This release will wipe your recovery. If anyone needs this changed let me know and I will build another.
1/3/2015
Android 5.0.2_r1 (LRX22G)
Data is now encryptable, meaning your unencrypted data should stick going forward.
Included my own build of stock kernel with Linaro 4.9.3 toolchain.
Fixed bluetooth (thanks Lollipopalooza/Craig)
No longer need to re-flash recovery.
12/6/2014
Android 5.0.1_r1 (LRX22C)
You will need to install separate gapps
You will need to re-flash your custom recovery after you install (you all let me know if I should change this or not, I think I will on future builds)
I am not responsible for anything that happens to your device or to you, yourself while flashing this.
Latest DL Links will be in post #2.
XDA:DevDB Information
Pure AOSP Flounder, ROM for the Nexus 9
Contributors
gchild320
ROM OS Version: 5.0.x Lollipop
Based On: AOSP
Version Information
Status: Stable
Created 2014-12-06
Last Updated 2015-01-03
Downloads
3/18/15
https://www.androidfilehost.com/?fid=95916177934543409
3/15/15
https://www.androidfilehost.com/?fid=95916177934541983
3/13/15
5.1 - https://www.androidfilehost.com/?fid=95916177934540786
1/3/14
Flounder Android 5.0.2_r1 build LRX22G https://www.androidfilehost.com/?fid=95864024717074545
Future FAQ if necessary (let's hope not).
Thank you!!!!
Will test it tomorow
I hope cm12 will build on arm64 soon
Just a few questions. What gapps do you recommend? What twrp ? There is the mainline version and the one @USBhost did. Thanks for the ROM!! Really appreciate seeing this show up.
mpmilestogo said:
Just a few questions. What gapps do you recommend? What twrp ? There is the mainline version and the one @USBhost did. Thanks for the ROM!! Really appreciate seeing this show up.
Click to expand...
Click to collapse
I didn't realize that there were two versions of twrp...I used the one from twrp website.
gchild320 said:
I didn't realize that there were two versions of twrp...I used the one from twrp website.
Click to expand...
Click to collapse
Yep
https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery
I fixed some things
in it
Factory reset will not encrypt data
fixed the device name
look bit better
custom built FIRE-ICE kernel for recovery
USBhost said:
Yep
https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery
I fixed some things
in it
Factory reset will not encrypt data
fixed the device name
look bit better
custom built FIRE-ICE kernel for recovery
Click to expand...
Click to collapse
Hell yes checking this out tomorrow.
build
Awesome !!!! Been waiting for this. How did u build? Last week since their are little options for roms decided to build one on my own and i did a repo sync to Google source but when i did lunch flounder wasn't listed in the build options ?
Flounder still isn't listed just lunch it anyway
Made a video running the ROM. Works very well!!
https://www.youtube.com/watch?v=kVQW-PMepn0
Hello,
can anyone provide a minimal gapps pack? I would like to avoid too much bloatware
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
This maybe what you are looking for.
Hiro Nakamura said:
Hello,
can anyone provide a minimal gapps pack? I would like to avoid too much bloatware
Click to expand...
Click to collapse
belair56 said:
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
This maybe what you are looking for.
Click to expand...
Click to collapse
Well i don't think it's 64bit version or is it ?
Hiro Nakamura said:
Well i don't think it's 64bit version or is it ?
Click to expand...
Click to collapse
From what I understand the apps themselves need to be optimized for 64 internally. These are all Google apps so they are if Google did so. As you update from the play store you don't choose if you're running 64bit or not.
As always I can be wrong.
Hiro Nakamura said:
Well i don't think it's 64bit version or is it ?
Click to expand...
Click to collapse
This is actually a great question.
Adaptive brightness doesn't work. Other than that everything seems to be working.
Edit: Okay so I used an app to look at which sensors were working and which ones weren't... The proximity sensor is not working at all.
omvir said:
Adaptive brightness doesn't work. Other than that everything seems to be working.
Edit: Okay so I used an app to look at which sensors were working and which ones weren't... The proximity sensor is not working at all.
Click to expand...
Click to collapse
Adaptive brightness is working flawlessly. Maybe you had a bad download or flash.
gchild320 said:
Flounder still isn't listed just lunch it anyway
Click to expand...
Click to collapse
I use USBhost's version of TWRP. I tried to flash the rom following directions in OP. It wouldn't flash. First it said for flounder and this device is flounder. Also said something about updater binary. I got this with the other rom also. I tried un-mounting and mounting system, but I still got the error messages. Any ideas?
jlokos said:
I use USBhost's version of TWRP. I tried to flash the rom following directions in OP. It wouldn't flash. First it said for flounder and this device is flounder. Also said something about updater binary. I got this with the other rom also. I tried un-mounting and mounting system, but I still got the error messages. Any ideas?
Click to expand...
Click to collapse
I manually changed it to work with official twrp... Not sure why twrp is calling it volantis instead of flounder but that's why. Also, to get anything to flash in twrp at the moment, I have to reboot recovery after wiping. Hope this helps.
This is a port of Jolla's Sailfish OS for h815.
Standard disclaimer applies:
I take no responsibility if anything happens to your phone, if your alarm doesn't work or if it reboots when you call emergency numbers. Flash at your own risk.
Don't flash this if you need a fully working phone.
Beta? 1.1
What works:
Wifi, 4G/LTE, sound, calls, vibration, SMS, Jolla Store, GPS, accelerometer,
What doesn't:
Camera, bluetooth, stock browser (use web pirate), wifi passwords need to be entered after a reboot, some video playback crashes (can be fixed by using software decoding, for example gstreamer10-libav on openrepos)
Possibly more, please report any issues
Install instructions:
Make sure you have a backup of anything you don't want to lose, preferably not on the device
Full wipe (might work without)
Flash LineageOS 14.1
Flash sailfishos-h815
Ignore any "no system installed" warnings from TWRP
Please note that this is not an Android ROM. Your Android apps will not work until someone gets sfdroid working.
Thanks to:
The friendly guys at #sailfishos-porters for helping me out a lot
Jolla for developing Sailfish OS
Download links: a few posts below
XDA:DevDB Information
[H815] Sailfish OS port, ROM for the LG G4
Contributors
kamnxt
ROM OS Version: 7.x Nougat
Based On: Sailfish OS
Version Information
Status: Beta
Current Beta Version: 11.02.18
Beta Release Date: 2018-02-11
Created 2017-07-29
Last Updated 2018-02-12
Downloads:
LineageOS 14.1:
I'm using the version from here right now:
https://www.lineageoslog.com/14.1/h815#201711070000
Sailfish OS: Latest here: https://androidfilehost.com/?w=files&flid=202570
All versions here: https://androidfilehost.com/?w=files&flid=202568
My sources:
https://github.com/kamnxt/droid-hal-h815
https://github.com/kamnxt/hybris-boot
https://github.com/kamnxt/android_kernel_lge_msm8992
Will try to upload everything soon
Changelog:
alpha 1 - 29.07.2017:
Initial release
Would be nice for someone to test. Also, formatting needs sorted for this first post along with source code links etc
OP, just make few 'reserved' posts, you need to have 10 posts to post a link
Sent from my LG-H815 using Tapatalk
Kye2000 said:
Would be nice for someone to test. Also, formatting needs sorted for this first post along with source code links etc
Click to expand...
Click to collapse
Minto107 said:
OP, just make few 'reserved' posts, you need to have 10 posts to post a link
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Done, will post links now
kamnxt said:
Done, will post links now
Click to expand...
Click to collapse
i flashed now but i am stuck here
gentr said:
i flashed now but i am stuck here
Click to expand...
Click to collapse
That's a part of the tutorial. If it doesn't work properly, you can try to skip it by tapping the corners of the screen from top left clockwise.
kamnxt said:
That's a part of the tutorial. If it doesn't work properly, you can try to skip it by tapping the corners of the screen from top left clockwise.
Click to expand...
Click to collapse
It's easy os system and very attractive to use them, hope for the new update very soon.
Great news!
When camera and browser will start working I'll try the port, till then... it's too much alpha for me
Thanks for the port!
Laghie said:
Great news!
When camera and browser will start working I'll try the port, till then... it's too much alpha for me
Thanks for the port!
Click to expand...
Click to collapse
You can use an unofficial browser like Webcat instead. Camera doesn't work yet though. I'll try to release a version with qtscenegraph-adaptation fixed soon (fixes black images).
Hello! Are you still working on this?
Laghie said:
Hello! Are you still working on this?
Click to expand...
Click to collapse
Hey! I've been kind of busy lately, but I was thinking about updating it recently. I can try to compile a new version if you want (hopefully including a fix for the pink screen issue).
That would be nice. Also a little status update is Glas
Thanks! But take your time, life's more important that alpha testing
BTW, is it possible to dual boot android and sailfish?
Laghie said:
Thanks! But take your time, life's more important that alpha testing
BTW, is it possible to dual boot android and sailfish?
Click to expand...
Click to collapse
You can dualboot by modifying fstab in the kernel and recovery to point the /data and /system to sdcard.
But you need quick sdcard to not be totally unusable.
Status update time!
I'm setting up the build environment on my new laptop (it's been a while since I last messed around with SFOS...) New version should be coming soon™ (hopefully within a few days). Trying to build with a newer version of LineageOS as well, so we'll see if that works.
Yes please. Would love to see this working. There isn't enough new stuff out there for the G4 and this would be awesome.
#ApolloLiteProblems said:
Yes please. Would love to see this working. There isn't enough new stuff out there for the G4 and this would be awesome.
Click to expand...
Click to collapse
Seems like I lost some of the files from the last time I got things working... I need to find out how I got sound working, since now it no longer works... I'll see if I can get it working again.
Awesome.
Before you get started,
i am not responsible for bricking device, dead sdcards,
muted alarm, or even thermonuclear war.
YOU chose to do this modification,
IF you point your finger to me to brick your device,
i will laugh at you.
This is GSI port from Official Havoc OS 2.9 by @vince31fr
Supported Devices
J701X
J730X
J600X
J530X
Details
Debloated /system 1037MB to 754MB
Pixel Launcher instead of Lawnchair
Includes SF-VENDOR 3.0 (Changelogs few days later)
Added M10 Fingerprint
Build.prop tweaks
No Gapps included, flash Open GApps ARM, 9.0, Pico
0.9GB /System with GApps Pico
Credits
Me for SF-VENDOR and Editing.
@vince31fr XDA for GSI
@ananjaser1211 for Cronos Kernel
Installation steps
You need Latest TWRP 3.4.0 or higher, or OFox 11.0
Flash Exynos7870_CreateVendor_2.0.zip
Flash HAVOC_REPARTITIONER.zip
Reboot recovery
Format data, Wipe Dalvik, Cache, System, Vendor, Data, Internal storage
And Flash Havoc-OS_2.9_J6-J5_J730_J701.zip
(Optional) Flash OpenGapps (Needed for Google Apps)
Reboot and Enjoy!
Bugs
HW Keys (Use NavBar instead)
Stretched Camera in J701 (Use 720p camera to fix this)
Downloads
GDrive
Mega
Telegram Support;
SF-GROUP
Everything Allowed but; Respect others. No NSFW/ Instant ban. No Ads. Enjoy
t.me
Contributors
@ichbinahmet
Source Code: https://github.com/ananjaser1211/Helios_7870
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Version Information
Status: Stable
Current Stable Version: 2.9
YY-DD-MM
Created 2021-30-09
Last Updated 2021-20-10
reserved
Thank you, but I've got bootloop. SM-J730F
Spargatorul said:
Thank you, but I've got bootloop. SM-J730F
Click to expand...
Click to collapse
Do you have /vendor partition?
You should flash Create Vendor from Project Spaget.
Im using same device, stable.
Yes, and it gives me error 7 now.
And also, I cannot get rid of "unable to mount preload". Not even with wipe.
Spargatorul said:
Yes, and it gives me error 7 now.
And also, I cannot get rid of "unable to mount preload". Not even with wipe.
Click to expand...
Click to collapse
You using wrong recovery.
Spargatorul said:
Yes, and it gives me error 7 now.
And also, I cannot get rid of "unable to mount preload". Not even with wipe.
Click to expand...
Click to collapse
Use TWRP 3.5.0
Releases · samsungexynos7870/android_device_samsung_j7y17lte
Contribute to samsungexynos7870/android_device_samsung_j7y17lte development by creating an account on GitHub.
github.com
Spargatorul said:
Yes, and it gives me error 7 now.
And also, I cannot get rid of "unable to mount preload". Not even with wipe.
Click to expand...
Click to collapse
Btw, ROM updated, read description, also use lastest TWRP .
Enjoy!
ichbinahmet said:
You using wrong recovery.
Click to expand...
Click to collapse
Indeed I was. I was using 3.3.0.
Can you pls post a link to the updated ROM?
https://forum.xda-developers.com/t/...android-q-10-0-for-galaxy-j5-j7-2017.4048917/
This one?
Spargatorul said:
Indeed I was. I was using 3.3.0.
Can you pls post a link to the updated ROM?
https://forum.xda-developers.com/t/...android-q-10-0-for-galaxy-j5-j7-2017.4048917/
This one?
Click to expand...
Click to collapse
Yes, inthread download links updated.
I tried both of them, the 3.8 and your 2.9, and I had 2 identical problems with them:
- The ROM starts well and works, but has random reboots
- After I flash Magisk, I get bootloop. The Magisk link from 3.8 post is not working...
how to fix no audio?, j701f
Spargatorul said:
I tried both of them, the 3.8 and your 2.9, and I had 2 identical problems with them:
- The ROM starts well and works, but has random reboots
- After I flash Magisk, I get bootloop. The Magisk link from 3.8 post is not working...
Click to expand...
Click to collapse
Probably you using custom kernel Kraken.
Flash latest from Magisk github
ichbinahmet said:
Probably you using custom kernel Kraken.
Flash latest from Magisk github
Click to expand...
Click to collapse
Ideed. I renounced Kraken kernel and they both worked well.
I don't have courage enough to try magisk, after a lot of attempts: latest version of magisk from github, the v17 magisk especially for havoc, even supersu... They all broke my OS.
And the TWRP backup didn't succeed to restore, either.
Another problem for which I didn't find a solution is the loudspeaker: I cannot use speaker for SIM 2 phone calls.
I tried replacing the SIM cards and a lot of settings, but no result: for SIM2 conversations, I cannot use loudspeaker.
Anyway, thank you thank you thank you for your helpful help.
Spargatorul said:
Ideed. I renounced Kraken kernel and they both worked well.
I don't have courage enough to try magisk, after a lot of attempts: latest version of magisk from github, the v17 magisk especially for havoc, even supersu... They all broke my OS.
And the TWRP backup didn't succeed to restore, either.
Another problem for which I didn't find a solution is the loudspeaker: I cannot use speaker for SIM 2 phone calls.
I tried replacing the SIM cards and a lot of settings, but no result: for SIM2 conversations, I cannot use loudspeaker.
Anyway, thank you thank you thank you for your helpful help.
Click to expand...
Click to collapse
Yes KRAKEN kernel breaks ROM on magisk flash, so you need to use Cronos kernel
Im trying to fix that broken loudspeaker bug.
Thanks for reporting
not sure if this is a noob question but i'm kinda new around this...
regarding this Havoc-OS_2.9_J6-J5_J730_J701.zip
Is this your latest Havoc-OS version based on android 9.0 (pie) ?
I'm testing it on my J730
and it runs alright and fast enough, good job on that man!
but I'm experiencing a few not listed bugs:
-recorded videos seem to have wrong a time-lapse making them "corrupted" and impossible to view\share (even recording directly trough whatsapp)
-keypad freezes (specially on whatsaap when you toggle for character type) making it very annoying to keep a conversation. Switching to browser to use keypad and going back some times unfreezes the keypad thought.
-loudspeaker (call sim1 or multimedia) doesn't work, all audio goes trough the call speaker only
thanks!
So7urno said:
not sure if this is a noob question but i'm kinda new around this...
regarding this Havoc-OS_2.9_J6-J5_J730_J701.zip
Is this your latest Havoc-OS version based on android 9.0 (pie) ?
I'm testing it on my J730
and it runs alright and fast enough, good job on that man!
but I'm experiencing a few not listed bugs:
-recorded videos seem to have wrong a time-lapse making them "corrupted" and impossible to view\share (even recording directly trough whatsapp)
-keypad freezes (specially on whatsaap when you toggle for character type) making it very annoying to keep a conversation. Switching to browser to use keypad and going back some times unfreezes the keypad thought.
-loudspeaker (call sim1 or multimedia) doesn't work, all audio goes trough the call speaker only
thanks!
Click to expand...
Click to collapse
Re download file and flash for loudspeaker fix
yes keypad shouldnt stop too, im using whatsapp all day
i dont know recorded videos but i will look, thanks for review
ichbinahmet said:
Re download file and flash for loudspeaker fix
yes keypad shouldnt stop too, im using whatsapp all day
i dont know recorded videos but i will look, thanks for review
Click to expand...
Click to collapse
thanks!
going to test asap!
-shouldn't you change the name of the file for havoc 2.9.2 or something?
(I just did that on my downloaded files so I don't get confused around my tested and untested rom's folder)
-TWRP version could have any impact on my bugs?
for some reason I can't use "TWRP 3.5 or 3.4 j7popltespr" (it doesn't boot),
but "TWRP 3.2.3 twrpbuilder" seems to works fine
PS. SD card got corrupted during this process
but after flashing phone back to stock ROM the SD was working again with no data loss
# you are welcome keep it up
So7urno said:
thanks!
going to test asap!
-shouldn't you change the name of the file for havoc 2.9.2 or something?
(I just did that on my downloaded files so I don't get confused around my tested and untested rom's folder)
-TWRP version could have any impact on my bugs?
for some reason I can't use "TWRP 3.5 or 3.4 j7popltespr" (it doesn't boot),
but "TWRP 3.2.3 twrpbuilder" seems to works fine
PS. SD card got corrupted during this process
but after flashing phone back to stock ROM the SD was working again with no data loss
# you are welcome keep it up
Click to expand...
Click to collapse
Releases · samsungexynos7870/android_device_samsung_j7y17lte
Contribute to samsungexynos7870/android_device_samsung_j7y17lte development by creating an account on GitHub.
github.com
You should use this TWRP. Thanks again
ichbinahmet said:
Releases · samsungexynos7870/android_device_samsung_j7y17lte
Contribute to samsungexynos7870/android_device_samsung_j7y17lte development by creating an account on GitHub.
github.com
You should use this TWRP. Thanks again
Click to expand...
Click to collapse
That fixed the problem! Thanks!
It seems I was using a wrong TWRP....
Most of the bugs I mentioned before are gone\fixed (loudspeaker, whatsapp keypad, sdcard).
except the video recording with the "opencamera" app (recorded videos are unplayable with messed up time lapse),
I tried also "HD camera" app from playstore with same problem.
But if I record video directly through whatsapp videos are ok.
Everything else seems working fine thought, stable and fast !
are you planning to work\fix the "(HW Keys (Use NavBar instead)" bug?
I Will keep using this rom for now, great job @ichbinahmet !
Hi folks
Since some of you asked me to make another thread for my TWRP build, here you go, the kernel is based on EWB5 (A13) but is compatible with all currenlty released Android versions.
WARNING/DISCLAIMER: Since the outer display isn't shut down this build can cause irreversible screen burns if used extensively. As such I take no responsabilities if you damage your device while using my TWRP build (and/or) other projects that may suffer from the same issues.
Edit: after some time the "screen burn" disappeared, so it seems that it's just a remanent image. In doubt stick to the warning.
TWRP Image
Sources:
Kernel
Device Tree (Forked from @shadow-of-leaf Z Flip 3 DT)
So just push it as the recovery to the active slot via adb?
Breaks dex? If Not its kompatible with latest one ui?
It doesn't break dex, you can backup your recovery partition, it should be compatible with latest Android, since recovery is contained
Mikowitsch said:
So just push it as the recovery to the active slot via adb?
Click to expand...
Click to collapse
Yes, the usual way works fine
is the link down.. i cant download it
miman04 said:
is the link down.. i cant download it
Click to expand...
Click to collapse
Fixed !
Azkali said:
Fixed !
Click to expand...
Click to collapse
Tq sir .. can i get a simple guide on how to get the TWRP works on my fold 3. im currently on a rooted fold 3 Android 13.
Should i use odin and put in AP then flash rite away or i use fastboot?
miman04 said:
Tq sir .. can i get a simple guide on how to get the TWRP works on my fold 3. im currently on a rooted fold 3 Android 13.
Should i use odin and put in AP then flash rite away or i use fastboot?
Click to expand...
Click to collapse
Yes in Odin putting recovery.tar in AP will work fine ^^
i cant download recovery and vbmeta
Azkali said:
Hi folks
Since some of you asked me to make another thread for my TWRP build, here you go, the kernel is based on EWB5 (A13) but is compatible with all currenlty released Android versions.
WARNING/DISCLAIMER: Since the outer display isn't shut down this build can cause irreversible screen burns if used extensively. As such I take no responsabilities if you damage your device while using my TWRP build (and/or) other projects that may suffer from the same issues.
Edit: after some time the "screen burn" disappeared, so it seems that it's just a remanent image. In doubt stick to the warning.
TWRP Image
Sources:
Kernel
Device Tree (Forked from @shadow-of-leaf Z Flip 3 DT)
Click to expand...
Click to collapse
404 page on TWRP and VBMETA
Using the DT from Azkali to build a new Release of TWRP, i'll make a new Thread for that
Thanks so much @Azkali for your Device Tree, i hope to help you soon
ROM-PacMe said:
Using the DT from Azkali to build a new Release of TWRP, i'll make a new Thread for that
Thanks so much @Azkali for your Device Tree, i hope to help you soon
Click to expand...
Click to collapse
I have a newer TWRP, maybe instead of a new build we could figure something out together
Join the discord and ping me there, I'll be available later
Release q2q-5337227142 · bm0x/twrp-actions-compiler
Recovery for q2q
github.com
based on minimal-twrp branch 12.1
and uses the DT from @Azkali
enjoy!
ROM-PacMe said:
Release q2q-5337227142 · bm0x/twrp-actions-compiler
Recovery for q2q
github.com
based on minimal-twrp branch 12.1
and uses the DT from @Azkali
enjoy!
Click to expand...
Click to collapse
is it compatible with SM-926B?
q2q is SM-926B?
google didnt know anything about "q2q samsung"
Can you try, If not working, only re install the recovery stock and vbmeta too
The other thread cites CVCA as a basis, but all I can find in the TWRP revision q2q-5337227142 in each. Is there an older build out that works better w/ BL 1, not 3?
thewayofwright said:
The other thread cites CVCA as a basis, but all I can find in the TWRP revision q2q-5337227142 in each. Is there an older build out that works better w/ BL 1, not 3?
Click to expand...
Click to collapse
the revision is a random number gived from Github Actions, nothing more my friend
thewayofwright said:
The other thread cites CVCA as a basis, but all I can find in the TWRP revision q2q-5337227142 in each. Is there an older build out that works better w/ BL 1, not 3?
Click to expand...
Click to collapse
only use the vbmeta and recovery tar of my own github releases, let me any update, ok?
i see soon any bug to help to fix