To install Sailfish OS you flash it over a CM or AOSP base. So a whole android rom is there unused when you're using Sailfish. So I thought why not make use of it, since Sailfish isn't using the android services like zygote, media, netd, or surfaceflinger they are disabled by default in init.rc, by re-enabling them and turning off Sailfish's Wayland Compositor and turning on Surfaceflinger I was able to boot into CM (for my device the Nexus 5, it's CM11) without input. Today I've finally managed to get input working by changing the usergroup of /dev/input/eventX from video to input. But although I'm able to navigate Android, and use the stock browser it's still quite unstable. Here is a logcat dump of the first few times I've booted into CM from Sailfish now that input is working, and I have no idea how to fix those errors.
If I connect to WiFi from Sailfish and then boot into CM then the Stock browser can use the internet connection and browse websites (although WiFi is off on Android), same goes for mobile data. But If I flash gapps and then try to login to my google account, Android doesn't see the internet connection and tries to make me connect again, at which point Surfaceflinger crashes and doesn't restart.
I made a basic guide of how to get to the same stage, if you would like to test it out once Sailfish is installed. So we can progress with the project.
Instructions of how to get to boot into CM from Sailfish OS
Related
Hi,
I am new in the Android world and I want to know if they are any ways to automate deployment of rom.
Let me explain :
I have 5 asus Z380KL, I have configured 1 tablet with all app, settings (android and apps), account... and I want to know, if they are any ways to completly backup this android and deploy to 4 another tablet, WITH ANDROID SYSTEM settings, app settings, account. I've tried TWRP complete backup, but the img is not recognized by other tablet (with chmod 755 like I see in another thread). I've tried Titanium Backup in pro mod but android system settings and some app are not backuped (and Yes, the tablet is rooted).
Actually, I have 5 tablets, but in some days, I could get 60. And I don't want to take many times to deploy each tablet with all configuration.
So, is there a possibility, with fastboot and adb shell and others things, without touching the tablet (only to boot in bootloader) to install/flash/backup each tablet. Only in command line ?
And what is for you the best/fatest way to accomplished that ? I have to create my custom ROM based on cyanogenmod or offical rom ? (If yes, can I add gapps, and others apps with config and android system conf and already account configured ?).
The best way for me is to branch the tablet, boot in bootloader, and launch script on my computer to install completly (with android system settings and app settings) the tablet, and loop for each tablet.
Have a nice day
So I got twrp 3.0.2_2016-04-17 p1 multirom working. I installed a few roms in primary and have moved to secondary but can only boot while in primary slot (kexec issue I assume) Really trying to get kali up and running and not so much kexec (will move back and forth for now) . found a lots of readme which looked good but diddn't quite work out. when kali would boot the nethunter terninal app would fail saying it couldn't find bootkali_login and I could never really uninstall changeroot. from twrp file manager I deleted /data/local/nhunter* and did complete reinstalls and still same results. I installed nh-op1-kali3.0 over cm13 and also found all in one 7.1 lineageos vers 14.0-20170101-unoffical and same results. I cannot find a cm11 or cm12 compatible with kali3.0 should I step down to kali2.0? any help or direction is greatly appreciated.
@seanwlk
Why dual boot? What do you need multirom for?
You can flash LineageOS 14.1 root it, and install busybox.
Then you need the nethunter apk and install chroot from there. (Chose either minimal or full doesn't matter)
The "issue" comes now basically I've tried multiple times to make the nethunter terminal work but it doesn't connect to Kali. So I managed to find a workaround which is basically using Kali over SSH and I suggest you JuiceSSH (but every SSH client will work) just connect to 127.0.0.1 (which is localhost, where Kali runs) but since the SSH service doesn't start on boot you will need to start it manually on each reboot through the nethunter app by creating a custom command that will be sent to Kali
Code:
service ssh start
Now you'll be able to connect and use Kali terminal.
It may not be perfect but I use it on daily bases.
I do this since COS 13 days.
Here I add some useful material.
Thanks for the responses. I found flashing the cm 13.1.2 original image when my phone would keep failing installs helped when I kept getting failed installs. got it and running on cm12 5.1.1 works great.... except for when it suddenly and randomly freezes the whole system with the screen on. I ran the Y-cable service and tried it out and it worked great. wifite as normal. I will give lineage14.1 a try. thanks for the heads up. as far as using multirom..... I found it copies the files from secondary to primary faster than a nandroid restore. I think its because the partitions are not zipped. 64gb is more than enough space that speed vs disk space wins. I have been using an lg g3 for years now and I really do like opo. got my tempered screen and tpu case yesterday so it's now traveling safely with me . My only concerns with lineage14.1 is that it might not support the wifi adapters in the kernel for external wifi adapters.
seanwlk said:
Why dual boot? What do you need multirom for?
You can flash LineageOS 14.1 root it, and install busybox.
Then you need the nethunter apk and install chroot from there. (Chose either minimal or full doesn't matter)
The "issue" comes now basically I've tried multiple times to make the nethunter terminal work but it doesn't connect to Kali. So I managed to find a workaround which is basically using Kali over SSH and I suggest you JuiceSSH (but every SSH client will work) just connect to 127.0.0.1 (which is localhost, where Kali runs) but since the SSH service doesn't start on boot you will need to start it manually on each reboot through the nethunter app by creating a custom command that will be sent to Kali
Code:
service ssh start
Now you'll be able to connect and use Kali terminal.
It may not be perfect but I use it on daily bases.
I do this since COS 13 days.
Click to expand...
Click to collapse
Nice!
I was having the same issue when I was running it on cm13. every time I tried to run android terminal in chroot kali it would fail cause it couldn't find bootkali. I thought it was just a chroot issue but if it works through ssh than that works for me! come to think of it. I never even tried vnc'ing cause I assumed it was not working. ssh much better than vnc for cpu overhead for sure.
rp201 said:
Nice!
I was having the same issue when I was running it on cm13. every time I tried to run android terminal in chroot kali it would fail cause it couldn't find bootkali. I thought it was just a chroot issue but if it works through ssh than that works for me! come to think of it. I never even tried vnc'ing cause I assumed it was not working. ssh much better than vnc for cpu overhead for sure.
Click to expand...
Click to collapse
I've tried VNC for the sake of curiosity. I installed xrdp but I can't login for some reason it gets stuck on the login form. But no big deal I don't need UI.
I hope I helped somebody, not sure if this method I use got ever published on the Internet ?
I installed latest nightly of lineage14.1 5/29/2017. Debug is enable and allowed over adb. (root priv for apps not built into lineage) then after inital boot twrp install of superSUv2.82 then your busybox and your nethunter. its not working for me. ssh service wont start. chroot is installed but not working. I'm obviously doing something wrong here. I can SU in terminal but cannot run "bootkali" or "bootkali_login" which is the error nethunter app is giving me.
rp201 said:
I installed latest nightly of lineage14.1 5/29/2017. Debug is enable and allowed over adb. (root priv for apps not built into lineage) then after inital boot twrp install of superSUv2.82 then your busybox and your nethunter. its not working for me. ssh service wont start. chroot is installed but not working. I'm obviously doing something wrong here. I can SU in terminal but cannot run "bootkali" or "bootkali_login" which is the error nethunter app is giving me.
Click to expand...
Click to collapse
Are you sure that the chroot is correctly installed?
Should be mounted here
Code:
/data/local/nhsystem/kali-armhf
Also when you boot the phone does the nethunter notification popup saying the boot went all OK?
How are you starting the SSH service?
Here check these screenshots: https://imgur.com/a/TYqoc
Also remember that Kali has an user and password so connect to SSH with the following credentials:
Code:
Host: 127.0.0.1
User: root
Pass: toor
seanwik,
yes to all of that I got everything the same. I was connecting as root to 127.0.0.1 but I was also thinking sshd.conf needed to be set to allow for root access possibly? but I never had to before so I have to guess sshd did not launch at start up. are you using a thrid party kernel?
rp201 said:
seanwik,
yes to all of that I got everything the same. I was connecting as root to 127.0.0.1 but I was also thinking sshd.conf needed to be set to allow for root access possibly? but I never had to before so I have to guess sshd did not launch at start up. are you using a thrid party kernel?
Click to expand...
Click to collapse
None of those commands start at startup, for the same reason nethunter terminal doesn't work, to have to run that custom command from within the app, only that way works. Also I don't use SuperSU but the root enabler for LineageOS so I used privacy guard as root manager. Don't think that's the issue, was just saying.
I'm currently running LineageOS kernel, but this method worked even with Boeffla
Look:
(sorry for my ****ty voice ? )
I fully clean reinstalled my ROM like 2 days ago and did this as usual and works.
thanks for the video and your time. did a new install. stilll same results. ssh service wont start.
thanks!
rp201 said:
thanks for the video and your time. did a new install. stilll same results. ssh service wont start. is privacy guard an app or settings in lineageOS?
thanks!
Click to expand...
Click to collapse
Developer options > manage root access. (Screenshot attached)
But it doesn't matter, I used Kali with SuperSU and magisk and it worked.
Does it tell you something when you tap on RUN on the custom command ?
Quick recap:
1-Flash Lineage
2-root
3-boot and install BusyBox and nethunter app
3-through nethunter app install Kali chroot (it will download the image and mount it in /data/local/nhsystem)
4-Reboot
5-Create custom command to start SSH service
6-Run SSH service
7-Connect to SSH with a client
I also just remembered you can see if the service is up from the nethunter app, check attachments.
LineageOS just updated to 5th june I updated and the chroot still works.
okay so I reinstalled and enabled the use of privacy guard in lineageOS first boot setup. when I go under privacy I dont see any settings to give busybox installer root access. dev-options only has settings to give root access to "enable root adb only" it does not have the usual "enable root adb and apps" any help would be great.
in my previous installs nethunter full not miniimal is installed. I have the ablility to install chroot and remove it. after reboot I would get status bar message like you saying nh service system is up and running. created entry like you the same. Thank you for helping. trying to figure out how to enable root without installing supersu in twrp like you.
rp201 said:
okay so I reinstalled and enabled the use of privacy guard in lineageOS first boot setup. when I go under privacy I dont see any settings to give busybox installer root access. dev-options only has settings to give root access to "enable root adb only" it does not have the usual "enable root adb and apps" any help would be great.
Click to expand...
Click to collapse
Because you didn't root with the LineageOS root zip
But as I said I don't think that's the issue.
I attach you the needed zips, the installer and the remover. Just flash through TWRP instead of using SuperSU.
Then go to developer options and in that menu it will appear more options select apps and ADB (check screenshot in the attachments)
This is just to put you in my same conditions but I don't believe it will fix the issue.
After much help from seanwik and 24 nhinstall.logs...its up and running connecting over ssh. I didn't stop there. After a little playing I got nhterm to work with Kali term instead of suandroid. Found a setting in dev options. Still does not launch within nethunter but I'm working on it.
I remember reading you have to uninstall nhterm.apk nh.apk vnc.apk and install nhterm vnc then nh in that order. Some of my playing included manually installing all the nh.apks from the nh.zip using xplore .
Nhterm
rp201 said:
Nhterm
Click to expand...
Click to collapse
Glad it works, but I'll stick to JuiceSSH because I love the interface and it's features. And since I use for remote accessing my servers it's much easier for me to have everything in the same library ?
Hi,
Have installed two different Pie ROMs on my Nexus 5, first crDroid and now Resurrection Remix.
I use my device extensively for app development, however I am encountering the same problem with both ROMs which suggests it might be an issue with Pie and the Nexus 5 in general. I didn't get the problem previously (was running LineageOS 14.1 on the Nexus 5, however I wanted to upgrade as that was no longer getting security updates).
When using Android Studio, it more often than not hangs at the 'Install' stage.
Similarly, using adb from the command line (adb install path/to/APK) also hangs.
Looking at Stack Overflow various fixes involving turning USB debugging off and on, or specifying auto-connect to debugger in the settings, are offered as a fix - in addition to the common Studio fixes of cleaning the project or invalidating the caches and restarting. None of the suggested fixes work reliably. Indeed, the fact that adb also hangs suggests it's an adb problem, not a Studio problem. FWIW my laptop os is Ubuntu (was 16.04, just upgraded to 18.04, same problem with each).
Anyone else using their device for development and encountering these problems? Any reliable solutions? Have a backup of the old Lineage install but don't really want to go back to that due to the lack of updates, and don't really want to buy a new device if I can help it... apart from this the Nexus is still working fine.
Thanks,
Nick
I'm still running Lineage 14.1 on my N5
Do you have the same issues with wireless ADB?
I found out that bluetooth is not always working in Bliss Roms. It can be solved by searching a Android x86 rom like 9.0 R2 that works good with bluetooth
And then upgrade to Bliss OS 11.1 by going to the advanced option and choose upgrade to Bliss OS 11.1 what normally not working with bluetooth if you just install Bliss OS 11.1
It seems that there is a connection between de Android x86 roms and the Bliss OS rom if they are the same version of android that can fix problems like wifi and bluetooth problems.
ServanSchreiber said:
I found out that bluetooth is not always working in Bliss Roms. It can be solved by searching a Android x86 rom like 9.0 R2 that works good with bluetooth
And then upgrade to Bliss OS 11.1 by going to the advanced option and choose upgrade to Bliss OS 11.1 what normally not working with bluetooth if you just install Bliss OS 11.1
It seems that there is a connection between de Android x86 roms and the Bliss OS rom if they are the same version of android that can fix problems like wifi and bluetooth problems.
Click to expand...
Click to collapse
Yo, this is probably the best advice/option I've heard regarding non-working WiFi/BT modules in Bliss OS to date. Seems no streamer/tutorial has covered this route to solve these hardware issues when installing the OS, specially on the latest versions. I'll definitely be trying this on my HP Stream 11 laptop which has a Realtek 8822be WiFi/BT module. Now just gotta figure out how to make a clean install iso of the latest Bliss OS with the drivers working.
hugoBOSS1981 said:
Yo, this is probably the best advice/option I've heard regarding non-working WiFi/BT modules in Bliss OS to date. Seems no streamer/tutorial has covered this route to solve these hardware issues when installing the OS, specially on the latest versions. I'll definitely be trying this on my HP Stream 11 laptop which has a Realtek 8822be WiFi/BT module. Now just gotta figure out how to make a clean install iso of the latest Bliss OS with the drivers working.
Click to expand...
Click to collapse
I don't get the
"going to the advanced option and choose upgrade" bit
the advanced option where, i've tried going from 9.0r2 installed and then booting a USB with bliss11 and there is not upgrade option, or am I just being thick.....(probably)
jonallwright said:
I don't get the
"going to the advanced option and choose upgrade" bit
the advanced option where, i've tried going from 9.0r2 installed and then booting a USB with bliss11 and there is not upgrade option, or am I just being thick.....(probably)
Click to expand...
Click to collapse
Upon usb boot and selecting the Bliss OS 11 iso from your USB, you should be greeted with several sub menu options. Amongst them, is the normal Bliss-os USB live option and several other debug options. At the bottom, there is a menu stating "Advanced options - >"; select it. On the next page to display there should be a few more boot options for "vulkan support, no setup wizard, and no hardware support". Next should be an option to upgrade or update Bliss-OS to the iso version you want (which you selected to boot from earlier). This will update the existing OS directory as if you did a fresh install in my experience using said option. I'd recommend saving a copy of your data.img file from your existing os's root directory so you can replace the fresh default data.img file with the one that has your apps and credentials for accounts, etc already on it. Otherwise you'll have to reconfigure the OS all over again and who wants that, right? The other option I'm aware of is the built in bliss updater utility within the system, but if you're on bliss os 11.13/14, it fails to connect to servers for updates to the OS to move up to 12, 14, or 15. In bliss os 14.3 though, I haven't had a chance to test it to see if it works as far as connecting to servers to update from within the OS to preserve your apps, accounts, etc.
Thanks for a comprehensive response, appreciate it
jonallwright said:
Thanks for a comprehensive response, appreciate it
Click to expand...
Click to collapse
No problem bud. I hate it when others do that to me when stuff like this is hella' technical to understand/follow and most of the time it's just some snarky comment telling you to look it up in the forum(s) or Google; yet a direct answer would be much faster and save everyone else time responding and such and the issue can be tagged as solved,
hi, i have managed to install BlissOS 11.13 (Android 9) with Windows Installer : https://docs.blissos.org/install-bliss-os/install-from-windows-uefi-esp-64-bit, combine it with grub2win and i got working dual-boot win11 and BlissOS without the need to usb boot or make ext4 partition separately. The BlissOS work awesome, the Wifi/Bluetooth working fine, but i loved the BlissOS 14, it's slightly faster in my device (Lenovo Ideapad D330). So i tried "upgrading" by following docs here : https://docs.blissos.org/install-bliss-os/updating-bliss-os-ag-builds. Again, the upgrade went success, until i try to turn on bluetooth, which is failed . Any clue how to resolve this?
hi, i have Ericsson f3507g mobile broadband hardware, how do i make it work in bliss os for call and internet connection. Thank you
So I installed Kali NetHunter to use the Wifite command. Long story short, I find out that I need an external wifi card for programs like Wifite to ACTUALLY run, so I find a tutorial to use Wifite WITHOUT a WiFi card. I installed Hijacker and went through the initial setup process (installing Nexmon). But then, I realised that I can no longer connect to any WiFi networks, despite my phone detecting them. I figured it had to do something with my management utility path for the Nexmon installation not existing at all (the default was /product/bin, which does not exist for my phone). So I reinstalled it, only this time setting the path as /system/bin). Still, it didn’t work. I fugured it has to do something with the bcmdhd_sta.bin file inside of the WiFi folder (/system/vendor/etc/wifi). No luck deleting it (I used amaze file manager). Can anyone pls help me, I just want my phone back, preferably without a hard reset. The device chipset that the Nexmon installation window is showing is 4339a0.
Details of my phone:
Samsung Galaxy Note 3 SM-9005
Android 11, running LineageOS 18.1