[ROM][10][Q][flo][UNOFFICIAL][Resurrection Remix OS-Ten] -> 2020-01-21

Pranav-flo

Member
Aug 23, 2019
14
7
0
18
Bangalore


Resurrection Remix Ten

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.
 */



Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.

Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.





Rom : https://drive.google.com/open?id=1DOxRsEVmjpXm8dhEpbMQSWKX6h7NiosY

Gapps(ARM) : https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/

Root : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445



XDA Developers
LineageOs Team
Omni Team

Thanks to dev @followmsi for device sources and for his continous support, development and bug fixes:eek:

Thanks @lollyjay for testing the builds




Resurrection Remix Source

Kernel : https://github.com/followmsi/android_kernel_google_msm/tree/followmsi-10

Vendor : https://github.com/followmsi/android_vendor/tree/flo-deb-lineage-17.1

Device : https://github.com/Pranav-flo/android_device_asus_flo/tree/RR-Ten





 
Last edited:

JT1510365

Senior Member
Jan 7, 2014
2,797
2,121
193
25
South Lyon
Nice i ran a build too and it works fine i just haven't made my thread yet. You beat me to it. No problem hopefully i can make my thread sometime when i get time to do it. I also haven't uploaded my build yet.
 

Oirbsiu

Member
Jan 27, 2020
5
0
0
Kali?

Hi All,
I have a Nexus 7 2013 (Flo) with the following

TWRP 3.3.1-1 UA (<- updated)
RR-Ten-20200119-flo-Unofficial.zip
open_gapps-arm-10.0-nano-20200128
Magisk 20.3

From Magisk, i installed busybox for android NDK (ver 1.31.1) and KaliNethunter (Ver 8.2)

With Kali installed, I went to install the chroot using kalifs-armhf-minimal.tar.xz

So far no issues with the installation.

I then proceeded to perform an update / upgrade

I then did apt-get install kali-linux-full

Again no issues noted.

yet every time I run nmap,
e.g. nmap -sN 192.168.178.0/24

I see the banner telling me that nmap has started but about 5 seconds later my devices reboots.

I cant figure out if the issue is with Kali or with the custom ROM - ive tried to see if I could spot anything with MattLog but I couldnt see anything to suggest what causes the device to reboot.

Is anyone else using this ROM and Kali - what else did you do to get namp to stop the reboot.
Regards
Mark
 
Last edited:

Pranav-flo

Member
Aug 23, 2019
14
7
0
18
Bangalore
Hi All,
I have a Nexus 7 2013 (Flo) with the following

TWRP 1.21 /Build 34
RR-Ten-20200119-flo-Unofficial.zip
open_gapps-arm-10.0-nano-20200128
Magisk 20.3

From Magisk, i installed busybox for android NDK (ver 1.31.1) and KaliNethunter (Ver 8.2)

With Kali installed, I went to install the chroot using kalifs-armhf-minimal.tar.xz

So far no issues with the installation.

I then proceeded to perform an update / upgrade

I then did apt-get install kali-linux-full

Again no issues noted.

yet every time I run nmap,
e.g. nmap -sN 192.168.178.0/24

I see the banner telling me that nmap has started but about 5 seconds later my devices reboots.

I cant figure out if the issue is with Kali or with the custom ROM - ive tried to see if I could spot anything with MattLog but I couldnt see anything to suggest what causes the device to reboot.

Is anyone else using this ROM and Kali - what else did you do to get namp to stop the reboot.
Regards
Mark
Let me try. Will let you know soon. :eek:
 

Smartie36

Senior Member
Oct 4, 2011
206
24
0
Flashed this rom to my nexus 7 right before I sold it, as the buyer asked if I could upgrade it to android 10 & I've just been asked if it's possible to wake up the tablet by tapping the screen etc? Having done a quick search on Google I see certain kernels did have this feature, does anyone know if the kernel in this rom supports it.

Sent from my LYA-L09 using Tapatalk
 

amppcguru

Senior Member
Sep 11, 2012
294
34
28
Stowe, VT
Hi All,
I have a Nexus 7 2013 (Flo) with the following

TWRP 1.21 /Build 34
RR-Ten-20200119-flo-Unofficial.zip
open_gapps-arm-10.0-nano-20200128
Magisk 20.3

From Magisk, i installed busybox for android NDK (ver 1.31.1) and KaliNethunter (Ver 8.2)

With Kali installed, I went to install the chroot using kalifs-armhf-minimal.tar.xz

So far no issues with the installation.

I then proceeded to perform an update / upgrade

I then did apt-get install kali-linux-full

Again no issues noted.

yet every time I run nmap,
e.g. nmap -sN 192.168.178.0/24

I see the banner telling me that nmap has started but about 5 seconds later my devices reboots.

I cant figure out if the issue is with Kali or with the custom ROM - ive tried to see if I could spot anything with MattLog but I couldnt see anything to suggest what causes the device to reboot.

Is anyone else using this ROM and Kali - what else did you do to get namp to stop the reboot.
Regards
Mark
TWRP you have is ancient. Latest version is 3.3.1

Sent from my Nexus 7 2013 using XDA-Developers Legacy app
 

Oirbsiu

Member
Jan 27, 2020
5
0
0
rtl8812au external wifi

I have an external Wi-Fi dongle - ALFA AWUS036ACH. this is based on rtl8812au chipset. I have been trying to get this working but failing.
THe tablet is seeing the device
Code:
kali:/ $ lsusb                                                                                                                      
Bus 001 Device 002: ID 0bda:8812
Bus 001 Device 001: ID 1d6b:0002
kali:/ $
and

Code:
[ 1550.675903] msm_hsusb_host msm_hsusb_host: Qualcomm On-Chip EHCI Host Controller
[ 1550.676635] SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts
[ 1550.676879] msm_hsusb_host msm_hsusb_host: new USB bus registered, assigned bus number 1
[ 1550.707305] msm_hsusb_host msm_hsusb_host: irq 132, io mem 0x12500000
[ 1550.727416] msm_hsusb_host msm_hsusb_host: USB 2.0 started, EHCI 1.00
[ 1550.727996] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1550.728424] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1550.728790] usb usb1: Product: Qualcomm On-Chip EHCI Host Controller
[ 1550.729003] usb usb1: Manufacturer: Linux 3.4.113-followmsi-g3acca97-07519-g58d618c ehci_hcd
[ 1550.729370] usb usb1: SerialNumber: msm_hsusb_host
[ 1550.742858] hub 1-0:1.0: USB hub found
[ 1550.743286] hub 1-0:1.0: 1 port detected
[ 1550.996002] portsc = 88001205
[ 1551.056304] usb 1-1: new high-speed USB device number 2 using msm_hsusb_host
[ 1551.115112] portsc = 88001205
[ 1551.177642] notifying plugin
[ 1551.211883] usb 1-1: New USB device found, idVendor=0bda, idProduct=8812
[ 1551.212249] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1551.212463] usb 1-1: Product: 802.11n NIC
[ 1551.212799] usb 1-1: Manufacturer: Realtek
[ 1551.213012] usb 1-1: SerialNumber: 123456
yet I only see the one WLAN interface - am I missing anything?

Kernel - flo-deb-followmsi-kernel-ten-20200117.zip
Thanks
Mark
 

Pete02

Senior Member
Dec 6, 2011
742
231
63
you dont have to use the ua version
Thanks. I gave it a go anyway but ended up with a twrp error. I think it was a 7 or something. I might've gotten a bad download. I'll wait till I can get to my desktop at this point so I can check the md5 and try again.

Edit: new download and formatted tablet.. still error 7 with twrp. Must be something else going on. Thx anyway for the help.
 
Last edited:

JT1510365

Senior Member
Jan 7, 2014
2,797
2,121
193
25
South Lyon
Thanks. I gave it a go anyway but ended up with a twrp error. I think it was a 7 or something. I might've gotten a bad download. I'll wait till I can get to my desktop at this point so I can check the md5 and try again.
Yeah you shouldn't be getting error 7 I don't use the UA version and I flashed this ROM a while ago and I never had any issues.
 
  • Like
Reactions: 2kpilgrim