I recently stumbled upon this native linux effort on the note 10.1 and it's already made decent progress. Given the hardware similarity to our beloved 8.0 it seems that this can be ported over without too much pain. I'll be giving a n8 boot image a go when I have some solid time to devote but interested in any thoughts.
Kali also released a boot image for use in recovery partition to "dual boot" android / linux.
http://forum.xda-developers.com/showpost.php?p=36916481&postcount=27
Related
Does anyone know if it would be possible to dual boot native ubuntu desktop and the stock rom just like it's possible to do it on the first nexus 7?
There was an indiegogo campaign that concluded a few weeks ago for this. It's apparently in the works.
Hello everyone,
Trying to find a port for Sailfish for Flo. Anyone seen one?
Screwedbyexisten
screwedbyexisten said:
Hello everyone,
Trying to find a port for Sailfish for Flo. Anyone seen one?
Screwedbyexisten
Click to expand...
Click to collapse
Yes, we do! https://plus.google.com/+VadimRutkovsky/posts/anfWQDB8vm4
Sailfish for Nexus 7 - Unable to flash bootable image
First and foremost, my thanks to the excellent work by Vadim Rutkovsky with his ported image of Sailfish OS to the flo Nexus 7. I am no developer, preferring to stand on the sidelines and holler team fighting songs (badly out-of-tune and in complete oblivion as to what is actually happening). Sadly, I am not a smart man and was unable to conquer this most recent challenge. Each time that I fail, however, I calmly and methodically assess the situation, and then I loudly blame anyone who is not around or somebody near me who is not big enough to hurt me.
Flashing the images was not the problem. Couldn't get past the Google splash screen on startup - tried the following:
- switched recovery versions (Philz, TWRP, Clockwork, and MultRom) - no joy
- switched kernels (needs a hard boot patch) - nuthin'
- flashed various CMod variations (KitKat and Jellybean)
- stepped away for a moment and returned to find my cat walking across my keyboard
- yelled at my cat, she didn't move
- tried sideloading via ADB, pushed cat away from keyboard
- got scratched by my cat, bled and felt sorry for myself
- tried loading via Wug - fizzled
- flashed back to KitKat stock and tried again, then to Jellybean... same-same
So, I'll let it rest for now and then attempt again later.
Dear XDA forum,
So I came from a galaxy note 3 where I did run linux but it was rooted. Since rooting gets rid of some functions on my galaxy note 7 I decided to use gnuroot debian which allows linus to run ontop of andriod via a P-root instead of a chroot. I have got blender running and it works (using Spen as a mouse/stylus). I have several hpc computing applications such as calculix, C++/Python IDE and compilers and scilab which all have arm based versions so It would run native on my SD820. So my question to those who have used this is:
Is it a full desktop variant of debian which is up to date?
How can I get a gui using x server and how do I give it access to device cpu/gpu, and sensors fully to be used with said applications?
Is this possible without root?
I just don't want to loose out on several note 7 features and knox features since I would loose them if I root.
Hi all,
First post, new member at this site. Thanks for all of your hard efforts and kind sharing of knowledge. I'm a US Navy sailor, and my rooted S5 (GP900) just bit the dust. I'm seeing if I can get this old dog (SGH-T989) going.
So far, I have bombed out on installing any ROM. I find myself without a stock T989UVMC6 file, as many file servers (in 2017) have understandably stopped serving this old image. I have the T-Mobile SGH-T989 (gen 1) phone. Clean IMEI.
Background: This phone was on stock firmware 2.3.x at the beginning of this ROM voyage, and had no service to do an OTA Jelly Bean push. This phone is in immaculate condition, gifted to me by my grandfather two weeks ago, after he finally upgraded. Known to work (just not in my hands).
Tools I have at my disposal (Windoze 7 machine):
Odin 3.10.7
PITmagic 1.3.10
T-Mobile_t989_GSII_ADB_Drivers (Samsung_USB_Driver_for_Mobile_Phones_v1_3_2200_0)
Tools I have at my disposal between my 5 linux machines:
Terminal
XTerm
Terminator
(terminal emulators, which is all Linux really needs )
MicroUSB 5-pin Cables I have tried
Anker Powerline Micro-USB **** I like this one a lot ****
Samsung OEM Micro-USB
Samsung OEM Tab 3 Micro-USB
Generic Micro-USB
ROMS and Zips I have tried pushing through TWRP 3.0.2, TWRP 2.8.4, and TWRP 3.1.0:
1) Validus (specifically Validus-LP-v8.0-2015-06-06-validus_hercules, a 2015 image, Android 5.1 Lollipop) + open_gapps-arm-5.1-stock-20170513
2) CyanogenMod 14.1 (specifically cm-14.1-20161031-UNOFFICIAL-celox, a 2016 image, Android 7.1 Nougat) + open_gapps-arm-7.1-stock-20170513
3) CyanogenMod 13.0 (specifically cm-13.0-20160327-UNOFFICIAL-celox, a 2016 image, Android 6.0 Marshmallow) + open_gapps-arm-6.0-aroma-20170513
4) LineageOS 14.1 (specifically lineage-14.1-20170314-UNOFFICIAL-celox, a 2017 image, Android 7.0 Nougat) + open_gapps-arm-7.1-stock-20170513
5) ParanoidAndroid 5.1 (specifically pa_hercules-5.1-20151011-vp, a 2015 image, Android 5.1 Lollipop + open_gapps-arm-5.1-stock-20170513
I have tried several versions of Odin (3.9.2 on), I have tried several versions of TWRP (2.8.4 on), I have tried flashing both modified and unmodified SGH-T989 PITs via both Odin and PITmagic. So far, I have been unsuccessful in all attempts of getting a stable OS on this thing, I have followed these old posts here at XDA to the 'T', and simply cannot for the life of me figure out why only Validus seems to do "anything" (as in optimize apps at bootup and then freeze at 64/105). Disheartening, but I'm an IT by trade, and a Linux fan by hobby, so I'm used to suffering for my art. I should also mention that I have used DARKSIDE.SUPER.WIPE / DARKSIDE.CACHE.WIPE by thederekjay and really feel this might be a PEBKAC (Problem Exists Between Keyboard And Chair) error.
Speaking of errors... what am I getting? Okay, so to answer on that: mostly it's Error 7, sometimes it's no error at all (as in a bootup screen that timelessly animates for a whole night, etc), other times it's an Encryption Unsuccessful. Depends on the ROM, depends on the GAPPS, and the stars and the moon on what error I get. -_-
However, I've been at this now for 2 weeks, off-and-on, and am now turning to you great minds to help this tired fellow out. I promise I will not be snarky (as other posters have been), and I greatly appreciate your pearls of wisdom in getting this SGSII up and running again.
:good:
-Gouda
[SOLVED] - Root issue
I feel so embarrassed. For anyone facing a similar issue, please triple check (read: distrust your instincts) and ensure the phone is unequivocally, unquestionably, absolutely rooted. SuperUser must be correctly installed via TWRP or CWM. Get past that, and your ROM + GAPPS procedure should allow you to access your OS/UI and get busy. Facepalming over this.
Gouda, out.
Hi all,
As we know MS has released and has been maintaining an ARM version of Windows for a while now, I was curious if anyone knew if it was possible to dual boot the ARM version? If dual booting isn't an option, what would be the best way to run it? I'm not worried about performance as such, as it's not something I plan to really use until KVM is supported for more than the pixel anyway, I was purely looking to test and see how it would look on such a device.
Any recommendations would be appreciated.
Dual booting is 99.999% won't work - the ARM image maintained by Microsoft is incredibly limited and lacks a lot of drivers, drivers that one would need to write from scratch, since they don't exist for Windows.
Virtualizing it would be possible on Android 13's new built in emulation stack, but you'd still need to root the phone for that, and beyond losing warranty in many places, you'd also lose access to a number of functions.
Has anybody on the Android 13/OneUi 5 Beta managed to root their device and try if the KVM feature works on the Z Fold 4?