Related
Kali NetHunter for the Galaxy Note 3 (3.1.0)
Welcome to the thread on Kali NetHunter for the Samsung Galaxy Note 3.
If you don't know what Kali NetHunter is, well, it's the entire Kali Linux operating system in a chroot on your phone, plus a bunch of awesome apps for executing exploits, fixing things, doing cool things. It goes on, I suppose.
I'm gonna be honest guys, I'm not a security person. When it comes to security, I'm more of a Paul Blart.
What I do know though, is that there is apt-get, and apt-get is life.
Find much more information here: https://github.com/offensive-security/kali-nethunter/wiki
The answer to all your questions, generally the answer is YES, IT CAN DO THAT.
Most AOSP based ROMs should be supported!
The updater zip will add a few files to your /system partition, and install all of the NetHunter apps to your /data partition.
The chroot is located in /data/local, so you don't have to worry about your system partition being full. It's full read/write capable.
Understand that the zip will replace your current kernel with a completely different one.
This is necessary because most stock or custom kernels don't provide the drivers needed to operate most of Kali NetHunter's features.
DOWNLOAD
Current version: 3.15.3 (stable, 2016-12-17)
Please be careful to download the right version based on this table:
N9005: hlteeur
N900W8 & N900T: hltecan
N900P: hltespr
N900K, N900L, & N900S: hltekor
SC-01F: hltedcm
SCL22: hltekdi
CyanogenMod 12.1 & SlimRom 5.1: lollipop
CyanogenMod 13.0 & SlimRom 6.0: marshmallow
Nightly TWRP flashable zips are located at: https://build.nethunter.com/nightly/
BEFORE INSTALLING
Please make sure your phone boots fine and runs fine before flashing NetHunter. It's confusing when people report bugs that exist in CyanogenMod by itself.
The Kali chroot and apps are installed on your data partition (in /data/local for chroot). To initialize the chroot and install Kali Linux, you need to start the Kali NetHunter app.
The NetHunter installer will automatically install SuperSU in system mode, which I consider to be more stable. Since NetHunter already modifies your system partition, there is no need to use systemless SuperSU anyways.
FULL FRESH INSTALL STEPS
Optional: Flash CyanogenMod/SlimRom installer zip
Optional: Flash Gapps if you want them (preferably OpenGapps pico)
Boot into device
Complete setup wizard
Reboot into recovery
Flash kernel-nethunter-hlte* and nethunter-generic-armhf-kalifs-full-rolling zips in any order.
Boot into device
Open the NetHunter app
Use the Kali Chroot Manager to finish the installation
You're done!
UPDATING TO A NEWER BUILD
Going from 3.0.0 and up, all you have to do is flash the new build in recovery and wipe dalvik cache.
UPDATING YOUR ROM
To get all your NetHunter and SuperSU functions back after flashing a new ROM, just flash the ~60 MB update-nethunter-* zip again.
RUNNING WIFI PENETRATION TESTS
The internal WiFi chipset of the Galaxy Note 3 is not capable of running services which use monitor mode such as Wifite. For this, you will need to use a monitor mode capable WiFi adapter through a microUSB OTG adapter.
As for compatible adapters, I highly recommend the Alfa Networks AWUS036NEH (eBay) which uses the Ralink RT3070 chipset. There are currently no monitor mode supported Wireless-AC adapters available.
Once plugged in, you can run the command from Kali terminal to turn on your adapter:
[email protected]:~# ip link set wlan1 up
RAN INTO AN ISSUE OR BUG?
In order for me to help you, you have to at minimum reply with:
The link to the exact zip you downloaded
Your device model (hlte, hltecan, hltesovietrussia, etc.)
The name of the ROM you're flashing it on
The version and build date of the ROM you're flashing it on
A complete description of your problem
Optional: An audio recording of you reading this entire post
If your issue is with a specific app, it might be better to contact the developer of that app.
If your issue is during the installation (ex. flashing the NetHunter zip), then please collect a TWRP recovery.log for me.
If you found a problem and were able to fix it, and no one's mentioned it in the thread already, it would be kind to state the issue and your fix for others to make use of as well.
You can join me and the other NetHunter developers on IRC at the #nethunter room on freenode to more handily diagnose problems together.
I apologize, but I can't do house calls at this time.
You may be able to fix some bugs by updating to the latest bootloader and modem for your device.
See: (Direct Download) Latest Bootloaders & Modems
KNOWN ISSUES
USB Keyboard & VNC - Google Keyboard, AOSP Keyboard, CM Keyboard do not work due to a depth bug, use Hacker's Keyboard as a workaround.
Terminal App - Full screen programs like nano or vi are unusable unless you use the resize command. (always type resize when opening a new terminal window)
SCREENSHOTS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DEVELOPMENT
For the kernel included in NetHunter for the Samsung Galaxy Note 3, you can find the sources here: https://github.com/jcadduono/idleKernel-note3
See the Kali NetHunter installer source here: https://github.com/offensive-security/kali-nethunter
See the Kali NetHunter app source here: https://github.com/offensive-security/nethunter-app
It is powered by idleKernel, however none of the idleKernel scripts (ikconfig, usb control, kernel tweaks) are available by default. I recommend installing idleKernel zip (non-NetHunter) from the idleKernel thread and then flashing the NetHunter updater or kernel installer over idleKernel. You will then have all of idleKernel and Kali NetHunter's features at your disposal.
DISCLAIMER
I am not affiliated with Offensive Security. They seem like cool guys though.
I'm not even a novice when it comes to security and penetration. I'm just a simple system administrator with a passion for breaking Android.
Please restrain yourselves from asking me security related questions.
NOT SO MUCH AS SEEN ON MR. ROBOT, BUT PROBABLY EVEN BETTER
XDA:DevDB Information
Kali NetHunter for the Galaxy Note 3, Device Specific App for the Samsung Galaxy Note 3
Contributors
jcadduono, the Kali NetHunter team
Source Code: https://github.com/jcadduono/kali-nethunter
Version Information
Status: Stable
Current Stable Version: 3.15.3
Stable Release Date: 2016-12-17
Created 2016-01-07
Last Updated 2016-12-21
Reserved
first
great cant wait to try it out
What solution are you offering for Wifi devices, Are you going to compile kernel for compatable devices?
Or is this something the user is going to have to do.
I only mention this, as i have a Working version of Nethunter and have for over a year, But i refused to post release information due to the support required to get various wifi devices to work.
I did not want to get involved so the release never happened, Am happy compliling my own kernel for supported drivers, But i dont see your average joe doing this.
Also another snag i found was you can only have the one wifi device enabled at one time, so disabling the onboard to enable the external.
All issues by commands, but am just questioning if you have considered this or have support for this?
dave7802 said:
What solution are you offering for Wifi devices, Are you going to compile kernel for compatable devices?
Or is this something the user is going to have to do.
I only mention this, as i have a Working version of Nethunter and have for over a year, But i refused to post release information due to the support required to get various wifi devices to work.
I did not want to get involved so the release never happened, Am happy compliling my own kernel for supported drivers, But i dont see your average joe doing this.
Also another snag i found was you can only have the one wifi device enabled at one time, so disabling the onboard to enable the external.
All issues by commands, but am just questioning if you have considered this or have support for this?
Click to expand...
Click to collapse
I suppose multiple WiFi devices would be in the realm of Kali rather than the kernel. I can't imagine it being harder than using a powered USB hub to connect multiple radios and configure each of them using one of the network managers available in the Kali repository, while leaving your native Broadcom WiFi to Android to handle. All the popular / mac80211 injection capable WiFi drivers are compiled right into the kernel and enabled - not as modules. The Nethunter installer takes care of installing all the necessary firmware binaries to your system partition as well.
The compatible USB WiFi dongles should just be plug and play at this point.
I'm still waiting on my TP TL-WN822N to arrive from Amazon for testing.
Btw have you tried the Nethunter 3.0 app? It really is designed to make everything quick and easy, 1 step for whatever you're trying to do.
Considering swinging by the #nethunter room on freenode to ask questions and/or suggest ideas to make things easier.
I have not tried 3.0
Am still talking about 2.0 seems like they have added some additional support like network manager.
This was not present in my build so i just use a few bash scripts to enable and disable.
But ill give this version 3.0 a try thanks
dave7802 said:
I have not tried 3.0
Am still talking about 2.0 seems like they have added some additional support like network manager.
This was not present in my build so i just use a few bash scripts to enable and disable.
But ill give this version 3.0 a try thanks
Click to expand...
Click to collapse
Not a network manager in nethunter app, I mean install one in Kali chroot the same way you would on a Debian server.
Version 3.0.1 is now up and the changes are:
Tell SuperSU to install in system mode (not systemless)
Update SuperSU to version 2.66
Use SuperSU's supolicy binary to patch the sepolicy during install (fixes Marshmallow/CM13.0 unable to boot)
Inject init.superuser.rc into the ramdisk if it's not there already
SuperSU should no longer be broken with non-gzip compressed ramdisks
Find commits here: https://github.com/jcadduono/kali-nethunter/commits/master
Please note that it is still Kali Nethunter 3.0, and the .1 is just an update that improves flashing compatibility.
Y'know, I really thought you guys would be eating this stuff right up. <_<
please include flashing instructions - do we need to also flash gapps...which ones should we use. Thank you.
comptonhubbard said:
please include flashing instructions - do we need to also flash gapps...which ones should we use. Thank you.
Click to expand...
Click to collapse
It's not a ROM, it's an app, kernel, and environment. You have to flash it on an already set up CyanogenMod ROM from TWRP.
jcadduono said:
It's not a ROM, it's an app, kernel, and environment. You have to flash it on an already set up CyanogenMod ROM from TWRP.
Click to expand...
Click to collapse
After IdleKernel 6.6.5?
Gandicela said:
After IdleKernel 6.6.5?
Click to expand...
Click to collapse
Doesn't matter. If you flash idleKernel after, make sure it's the -kali version though. The only thing flashing idleKernel does is add ikconfig, /sbin/usb, and a few small kernel tweaks in the ramdisk.
jcadduono said:
Doesn't matter. If you flash idleKernel after, make sure it's the -kali version though. The only thing flashing idleKernel does is add ikconfig, /sbin/usb, and a few small kernel tweaks in the ramdisk.
Click to expand...
Click to collapse
I see. It's therefore like this: Running CM>>Kali Hunter>>Kali Hunter Kernel. Cheers, Mate!
I need to format SD-card?
amazing work.
tnx
Mx WaR HaBiB said:
I need to format SD-card?
amazing work.
tnx
Click to expand...
Click to collapse
No you dont have to format it
Sent from my SM-N9005 using Tapatalk
Gandicela said:
I see. It's therefore like this: Running CM>>Kali Hunter>>Kali Hunter Kernel. Cheers, Mate!
Click to expand...
Click to collapse
So, do we need to use version for CM 12.1 for OnePlus from here?
https://www.offensive-security.com/kali-linux-nethunter-download/
Ps
It works
First install kali kernel, after download Kali for oneplusone, reboot into recovery, install kali zip, and aftet again idle kali kernel.
I am on CM 12.1 nightly...
eseregin said:
So, do we need to use version for CM 12.1 for OnePlus from here?
https://www.offensive-security.com/kali-linux-nethunter-download/
Ps
It works
First install kali kernel, after download Kali for oneplusone, reboot into recovery, install kali zip, and aftet again idle kali kernel.
I am on CM 12.1 nightly...
Click to expand...
Click to collapse
Why are you doing this!!! You're bound to end up breaking something.
All you do is flash this after completing CM setup wizard and you're done. There's absolutely no reason to download any other Kali installer. This is the full version 3.0! Nethunter app now sets up your chroot for you.
Full steps:
Flash CyanogenMod installer zip
Flash Gapps (preferably opengapps pico)
Boot into device
Complete setup wizard
Reboot into recovery
Flash the Galaxy Note 3 Kali Nethunter installer zip from this thread
Boot into device
You're done!
If you absolutely need ikconfig or /sbin/usb, then you can install idleKernel-kali zip from the idleKernel thread later.
3.0.1_2016_01_10 build uploaded. Just a bug fix for Nethunter app.
Installation query
I have CM13 set up with superSU 2.46 and idleKernel 6.5.5 installed.
Do I have to install CM all over again? And follow your steps, or is there a way for me to keep my data and just flash it as is?
UnbracedTundra said:
I have CM13 set up with superSU 2.46 and idleKernel 6.5.5 installed.
Do I have to install CM all over again? And follow your steps, or is there a way for me to keep my data and just flash it as is?
Click to expand...
Click to collapse
Make a full backup in twrp first.
Wipe /system and dalvik and /cache. Install latest CM13 (or CM12.1 if thats what you meant) zip and gapps, then boot into system. Once boot is complete, reboot into recovery and flash nethunter then boot and you should be good to go without deleting your data.
jcadduono said:
Why are you doing this!!! You're bound to end up breaking something.
All you do is flash this after completing CM setup wizard and you're done. There's absolutely no reason to download any other Kali installer. This is the full version 3.0! Nethunter app now sets up your chroot for you.
Full steps:
Flash CyanogenMod installer zip
Flash Gapps (preferably opengapps pico)
Boot into device
Complete setup wizard
Reboot into recovery
Flash the Galaxy Note 3 Kali Nethunter installer zip from this thread
Boot into device
You're done!
If you absolutely need ikconfig or /sbin/usb, then you can install idleKernel-kali zip from the idleKernel thread later.
3.0.1_2016_01_10 build uploaded. Just a bug fix for Nethunter app.
Click to expand...
Click to collapse
Wow...
I am idiot!
Completely ignored the main link I needed -
https://idlekernel.com/nethunter/cm12.1
Now I understand that went dangerous way, lucky still with working phone
Tbh, most all utilities in Kali for now behind my knowlage of Linux so far
PS
I can see some scripts somehow survived even with full wipe, now my recovery provide some red lines doing job, something path missing in /data/...something/something
Though do the job.
I thought nothing can survive after full wipe...
Kali NET-HUNTER
This is the kali nethunter for the htc one m7 running on the latest android version (6.0 and 7.0 /NOUGAT/Marshmallow)
SCREENSHOTS
http://imgur.com/a/JEL0l
Steps To Install
1.-Download the latest cm 13,14 or LOS 13,14 and nethunter and the Gapps ( Just to obatin Google Playstore )
2.-Flash cm 13 or LOS 14 and Gapps/
3.-Now reboot and load cm 13,14 or LOS rom ( wait until the boot completes )
4.-Go back to recovery and install the nethunter zip
5.-Now reboot
5.-success !
Downloads
cm 13 = https://androidfilehost.com/?w=files&flid=23169
Net-Hunter = https://www.androidfilehost.com/?fid=24651430732236171
Net-Hunter for nougat =https://www.androidfilehost.com/?fid=745425885120725928
Update Big Thanks to @michael8t6 for making the kernel
androidhost are taking forever to approve my dev account so I've had to upload it to my G drive for now. This is the standard cm13 rom running on android 6.0, nothing has changed, I've just replaced the kernel with a patched one. You can download it here: https://drive.google.com/file/d/0B43...ew?usp=sharing
steps to install
Copy the zip and Gapps to your phone.
Reboot into recovery mode.
Wipe data, cache, dalvik.
Flash rom, then flash Gapps
If you're S-OFF then simply reboot and follow ZpanicZ instructions for installing net hunter.
If you're S-ON then reboot back into bootloader.
Extract boot.im from the zip onto your computer and into your fastboot directory.
Plug your phone into your computer and run the following command:
Code:
Code:
fastboot flash boot boot.img
Reboot and enjoy.
On the first reboot after flashing the rom, it can take up to ten mins for the phone to boot completely. Just be patient.
After you've finished installing nethunter, install the Xposed framework if you want to, not before, I fount this caused the phone to hang on the boot screen.
Once you've finished installing everything, run the nethunter app and grant it root permissions.
Close the app and re open the app, if you don't see any HID devices showing under the HID devices section. Open a new kali terminal and run the following command:
Code:
Code:
ls /dev/hidg*
You should see two HID devices come up, if you don't then post in this thread and I'll try to help you.
If you do see the devices, then nethunter isn't looking in root but the HID attacks should still work.
Lastly, if rubber ducky isn't working for you, then enable debugging mode via the developer options under settings and also connect your phone to your computer via MTP mode.
Known issues
▼BADUSB MITM isn't working, this isn't due to the kernel but is related to the nethunter install. I've been researching into this and need to look into the way it assigns the interfaces more.
▼I'm not sure if monitor mode is working for external wireless adapters. So basically, when building the kernel, I have to enable the relevant options to support the chipset drivers. The three main ones are obviously athros, ralink and realtek. When I was compiling, I hit an error regarding the realtek drivers, so for now I've not bothered enabling any support for wireless cards as compiling takes ages on my computer (she's a dinosaur). Once I'm not sick of staring at my monitor any more, I'm going to be looking into this feature as my first priority. That being said, if anyone does manage to enable monitor mode on a wireless adapter, please let me know in this thread, there's no point enabling athros drivers if they already work, it'll just make the kernel bulkier and slow down the phone overall.
▼You tell me.
Credits:
@9Lukas5 for allowing me to use his kernel source.
@ZpanicZ for creating the nethunter app and giving me the motivation to learn about compiling kernels. You may want to add all this to the OP buddy. Done
Click to expand...
Click to collapse
any screenshots?
nandhul30 said:
any screenshots?
Click to expand...
Click to collapse
i will upload some screenshots in a bit
Seem cool...... What features does it incl.?
-leo- said:
Seem cool...... What deatures does it incl.?
Click to expand...
Click to collapse
Here are some of the features from kali linux site https://www.kali.org/kali-linux-nethunter/
you can do a lot of things with nethunter because it includes all kali linux OS features .
What i found is the best of this rom is the vnc (virtual network computing), it's kali linux v 1.0 on a phone !
works zip on GPE?
Seems nice, how is the battery life in this?
nikola360 said:
works zip on GPE?
Click to expand...
Click to collapse
yes it should work in gpe as well
kala123 said:
Seems nice, how is the battery life in this?
Click to expand...
Click to collapse
Exactly the same as having cm 13, which is pretty standard
thx, it's fantastic!
Can i usw a cm 13 based Rom?
ZpanicZ said:
Kali NET-HUNTER
This is the kali nethunter for the htc one m7 running on the latest android version (6.0 Marshmallow)
SCREENSHOTS
http://imgur.com/a/JEL0l
Steps To Install
1.-Download the latest cm 13 and nethunter and the Gapps ( Just to obatin Google Playstore )
2.-Flash cm 13 and Gapps/
3.-Now reboot and load cm 13 rom ( wait until the boot completes )
4.-Go back to recovery and install the nethunter zip
5.-Now reboot
5.-success !
Downloads
cm 13 = https://androidfilehost.com/?w=files&flid=23169
Net-Hunter = https://www.androidfilehost.com/?fid=24651430732236171
Click to expand...
Click to collapse
Hi. Can use it in htc one m7 sprint ? Now I am using GSM in VietNam
Wlkchnbndgr said:
Can i usw a cm 13 based Rom?
Click to expand...
Click to collapse
Well it's 99% it will work without problems, ( but i do not recommend installing modified cm roms )
takaru said:
Hi. Can use it in htc one m7 sprint ? Now I am using GSM in VietNam
Click to expand...
Click to collapse
If the cm 13 rom supports sprint then yes it will work perfectly
Works on Aicp. :good: But i think i must flash it again, when i do update my rom once a week, right?
Wlkchnbndgr said:
Works on Aicp. :good: But i think i must flash it again, when i do update my rom once a week, right?
Click to expand...
Click to collapse
Most likely , yes
Whoa ... No way
ZpanicZ said:
Kali NET-HUNTER
This is the kali nethunter for the htc one m7 running on the latest android version (6.0 Marshmallow)
SCREENSHOTS
http://imgur.com/a/JEL0l
Steps To Install
1.-Download the latest cm 13 and nethunter and the Gapps ( Just to obatin Google Playstore )
2.-Flash cm 13 and Gapps/
3.-Now reboot and load cm 13 rom ( wait until the boot completes )
4.-Go back to recovery and install the nethunter zip
5.-Now reboot
5.-success !
Downloads
cm 13 = https://androidfilehost.com/?w=files&flid=23169
Net-Hunter = https://www.androidfilehost.com/?fid=24651430732236171
Click to expand...
Click to collapse
I never saw this coming!
Just lately I had decided to hop onto my old HTC One M7 phone to see what all I had left on it. ...
Then I figured, hey, perhaps there's something newer that I could flash onto it seeing as how is been well over a year since I'd used it at all.
WoW! ... and then I found this on here and my mind was blown!
I've been wanting to try Kali NET-HUNTER out for years now and this this is just awesome, thank you for sharing this with us.
?
starovdarkness said:
I never saw this coming!
Just lately I had decided to hop onto my old HTC One M7 phone to see what all I had left on it. ...
Then I figured, hey, perhaps there's something newer that I could flash onto it seeing as how is been well over a year since I'd used it at all.
WoW! ... and then I found this on here and my mind was blown!
I've been wanting to try Kali NET-HUNTER out for years now and this this is just awesome, thank you for sharing this with us.
��
Click to expand...
Click to collapse
Glad i wasn't the only one :b , i was kind of suprise there was no kali nethunter for this phone.
installation went smoothly..which is the preferred wireless card?
Sent from my MI NOTE LTE using Tapatalk
damn66 said:
installation went smoothly..which is the preferred wireless card?
Sent from my MI NOTE LTE using Tapatalk
Click to expand...
Click to collapse
well there are several cards that works perfectly, you may want to google that, also search for wireless cards that can do packet injection without problems.
This thread is about installing and using AOSP 7.x (Nougat) ROM for the ASUS Nexus 7 Grouper / Tilapia devices.
Asus - Model names
Grouper = Asus Nexus 7 2012 WiFi
Tilapia = Asus Nexus 7 2012 3G
Initial Setup Installation
Update Recovery to TWRP 3.6.2-9 for Grouper resp. TWRP 3.6.2-9 for Tilapia
Boot into Recovery
Factory Reset (only needed if you are not already on Android 7.x AOSP)
Install 7.1.2 Grouper OTA-Package (Build 20230418) (MD5: 3abdfef56c75cc171fce1c4ffd7a17a8)
or
Install 7.1.2 Tilapia OTA-Package (Build 20230418) (MD5: fc7a5bc81587dba848b37bd62e6166b9)
Reboot into recovery
Install Open GApps (arm/7.1/pico)
(if you have issues regarding the size of the GApps please refer to the next post)
[*]To get root access, I suggest to use either Magisk (V21.4) and Magsik Manager (V8.0.7) the "old" version of Magisk, or the new unified Magisk (V26.1) which can be flashed by TWRP, too. Probably you'll need to rename Magisk-v26.1.apk to Magisk-v26.1.zip
I was not able to flash Magisk 24.x by TWRP / direct install, nevertheless the patching boot.img method worked. For that you need to extract the boot.img from the OTA and transfer it to your devies. Then you need to patch the boot.img and transfer it back to your PC. Finally you can flash the patched boot.img using fastboot.
For detailed instructions please consult the Magisk threads here in XDA.
Do not install Magisk on initial setup as it might lead to issues. Start the ROM without having root access the first time and install Magisk in a second step.
If you are already on Android 7.x AOSP, it's sufficient to do the follwowing steps:
Update Installation
Boot into Recovery
Install 7.1.2 Grouper OTA-Package (Build 20230418) (MD5: 3abdfef56c75cc171fce1c4ffd7a17a8)
or
Install 7.1.2 Tilapia OTA-Package (Build 20230418) (MD5: fc7a5bc81587dba848b37bd62e6166b9)
Reboot into recovery
Install Open GApps (arm/7.1/pico)
(if you have issues regarding the size of the GApps please refer to the next post)
Wipe cache/dalvik-cache (optional, but suggested)
reboot
Important: For more detailed installation instructions please refer to the next post
Important: First boot after upgrading will take a bit longer (stays on ANDROID) because of art optimizations
flash and use on your own risk!
CREDITS,
AOSP/Google, LineageOS, Ziyann for setting up the Grouper-AOSP repository and his Unlegacy Android project, daniel_hk for some hints how to get the 3.1 kernel running with N, timduru for his work on the Asus Transformer, Timur Mehrvarz for his work on the tegra kernel, Francisco Franco for his kernel work in general
Bugs:
please report
Latest Changes
20230418(AOSP 7.1.2)
security fixes for January / February / March and April
Latest version with MicroG-patch applied to them:
aosp_grouper-7.1.2-mg-ota-20230418.eng.ds.zip (MD5: ccfd0b77ca5d2bc8bf98a530737158ba)
aosp_tilapia-7.1.2-mg-ota-20230418.eng.ds.zip (MD5: f91a7ac97aae3b724612980848fed342)
Changelog
Please refer to the changes found in the github repos
All ota packages can be found here:
AndDiSa ROM files repository
Sources
https://github.com/AndDiSa
If you would like to build from the sources, you can do so by cloning and build from repositories:
repo init -u https://github.com/AndDiSa/platform_manifest-Grouper-AOSP.git -b ads-7.1.0
repo sync (... and go out for lunch ...)
. build/envsetup.sh
lunch 7 / 8 / 9
make / make otapackage
but please take in mind that you need to have some free space (>= 100 GB) and some time ...
XDA:DevDB Information
Android 7.x AOSP, ROM for the Nexus 7
Contributors
AndDiSa
Source Code: https://github.com/AndDiSa?tab=repositories
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.1.x
Based On: AOSP
Version Information
Status: Stable
Created 2016-09-23
Last Updated 2021-12-09
Please note:
the system partition is already quite full which leads to the problem that gapps probably will not install correctly and that may lead to weired problems (apps closing / not showing up correctly / ...). I suggest to use the dynamic gapps package linked above. In addition I suggest you to erase the system partition completely before applying the OTA package
If you get "Error 7" when trying to flash the ROM directly after upgrading to TWRP 3.5.2-9, wipe the Boot, System and Cache partition and clean dalvik-cache, then re-boot to Recovery and try again (you will not loose any data as long as you do not wipe the Data partition).
If you get "Error 70" when installing GApps copy the attached gapps-config files into the same directory where the gapps installation packages is copiedI.e. something like
/sdcard/open_gapps-arm-7.1-pico-20210922.zip
/sdcard/gapps-config-tilapia.txt
/sdcard/gapps-config-grouper.txt
and then try to start the installation again. Error 70 should be fixed.
Some additional hints
If you are in a bootloop which shows to Google logo again and again, it's sufficient to hold vol- while booting. The next bootloop will boot into bootloader.
If you are in a bootloop which shows the ANDROID splash screen continuusly, connect your device to your PC and enter
Code:
adb reboot bootloader
After a few seconds the device should show up the bootloader screen
Anyone have a list of issues? Does video playback in YouTube work correctly on this rom or is it broken like the other 7.0 roms? Have the UI glitches been fixed? Does NFC work?
Nintonito said:
Anyone have a list of issues? Does video playback in YouTube work correctly on this rom or is it broken like the other 7.0 roms? Have the UI glitches been fixed? Does NFC work?
Click to expand...
Click to collapse
Why not figure it out by yourself?
If you flash this ROM you can create a list of what's working and what's not [emoji6]
Anyway, when I'm home, I gonna flash this ROM on my brother's Nexus 7 and give feedback. [emoji4]
Sent from my Nexus 5 using XDA-Developers mobile app
Wrong link in the post. Downloaded and flashed the last build on my device. After flashing ROM my device was getting cycle reboots and error with cache partition. Fixed that using ADB. ROM seems unstable and buggy. Getting error with Bluetooth share after booting. Navbar and top bar are always black. Old launcher isn't good. Replace it with any good launcher, please. I hope you'll keep work on it. Thank you, good job!
View attachment 3884176
View attachment 3884177
View attachment 3884178
Thanks, I'll correct the link
Nevertheless your problems I cannot reproduce ... probably because I've done an update installation. I'll have a look at it.
What was the ROM you have had installed before? Did you wipe?
When i get a chance this weekend I'm going to try this with Phh Superuser and Magisk. That combo is/was working great on your MM rom.
I flashed your ROM with TWRP 3.0.2-0 and after 'Patching system image uncondinionally' i get
Code:
Patching system image uncondinionally...
E:unknown command [log]
E:unknown command [log]
script succeeded: result was [1.000000]
Updating partition detail...
...done
I doublechecked the md5 of the file and reflashed but still no luck.
[Edit]
I rebooted and it seems to run....
[Edit2]
Flashing the plain ROM without the gapps seems to work - but after these gapps it doesnt start.
I wiped caches, system and data. I installed Android 7 rom, falls and SuperSU. But went into bootloop. I then just installed rom and SuperSU. But keep getting Bluetooth Share keeps stopping messages after boot up. Thanks.
Trued to get into recovery. Now I am keep on getting the following error messages:
E:Unknown fs_type "f2fs" for cache
E: Can't Mount /cache/recovery/last_locale
I cannot boot to Android or bootloader now. I removed battery and plugged it back in. But the same problem. It seems my device is bricked now.
Any suggestions to get out of this loop? Thx
tpuserhp said:
I wiped caches, system and data. I installed Android 7 rom, falls and SuperSU. But went into bootloop. I then just installed rom and SuperSU. But keep getting Bluetooth Share keeps stopping messages after boot up. Thanks.
Trued to get into recovery. Now I am keep on getting the following error messages:
E:Unknown fs_type "f2fs" for cache
E: Can't Mount /cache/recovery/last_locale
I cannot boot to Android or bootloader now. I removed battery and plugged it back in. But the same problem. It seems my device is bricked now.
Any suggestions to get out of this loop? Thx
Click to expand...
Click to collapse
I can connect my grouper to my PC and enter adb reboot bootloader command. But I'm not sure what to do next to fix the cache error in recovery. Any suggestions? Thx
---------- Post added at 04:34 PM ---------- Previous post was at 04:18 PM ----------
DSTear said:
Wrong link in the post. Downloaded and flashed the last build on my device. After flashing ROM my device was getting cycle reboots and error with cache partition. Fixed that using ADB. ROM seems unstable and buggy. Getting error with Bluetooth share after booting. Navbar and top bar are always black. Old launcher isn't good. Replace it with any good launcher, please. I hope you'll keep work on it. Thank you, good job!
View attachment 3884176
View attachment 3884177
View attachment 3884178
Click to expand...
Click to collapse
Hi @DSTear, I'm running into the same problem on the cache partition as you. I'd appreciate if you could share your method on fixing the cache error in advance. Thx
I was managed to restore the backup and install twrp again.
I think I will retire my grouper on MM now.
As I can see, there are two main problems you ran into:
- you are using f2fs for cache and / or data and the version of twrp you are using is not supporting that file type
- you are flashing gapps / SuperSU /... but the space on /system is not sufficient
I'll update the OP to make aware of those possible issues and give some hints how to prevent them.
Sent from my Nexus 7 using XDA-Developers mobile app
AndDiSa said:
As I can see, there are two main problems you ran into:
- you are using f2fs for cache and / or data and the version of twrp you are using is not supporting that file type
- you are flashing gapps / SuperSU /... but the space on /system is not sufficient
I'll update the OP to make aware of those possible issues and give some hints how to prevent them.
Sent from my Nexus 7 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm not using f2fs. I issued a mount command and did not find any f2fs hits. Not sure why I am getting those msgs. Odd.
I've updated the installation instructions in the OP / second post
I've added some hints, too, how to get out of bootloops, if you encounter such situations.
tpuserhp said:
I can connect my grouper to my PC and enter adb reboot bootloader command. But I'm not sure what to do next to fix the cache error in recovery. Any suggestions? Thx
---------- Post added at 04:34 PM ---------- Previous post was at 04:18 PM ----------
Hi @DSTear, I'm running into the same problem on the cache partition as you. I'd appreciate if you could share your method on fixing the cache error in advance. Thx
I was managed to restore the backup and install twrp again.
I think I will retire my grouper on MM now.
Click to expand...
Click to collapse
Hi. It's quite simple to fix that. Just connect your device to computer, then start bootloop. You will able to fix it using ADB:
Code:
adb reboot bootloader
And after that format your cache partition:
Code:
fastboot format cache
And reinstall TWRP just in case:
Code:
fastboot flash recovery [twrp img for your device]
Bluetooth is not working.
Could Restart be added to the shut down menu please?
Bluetooth will be fixed with the next release.
Sent from my Nexus 7 using XDA-Developers mobile app
difference to
http://forum.xda-developers.com/nexus-7/development/rom-naosprom-nexus-7-2012-t3467335
hanschke said:
difference to
http://forum.xda-developers.com/nexus-7/development/rom-naosprom-nexus-7-2012-t3467335
Click to expand...
Click to collapse
Bluetooth isn't working.
*SCNR*
I want Restart menu.
Next time
Please Support Restart menu.
AndDiSa said:
Some additional hints
If you are in a bootloop which shows to Google logo again and again, it's sufficient to hold vol- while booting. The next bootloop will boot into bootloader.
If you are in a bootloop which shows the ANDROID splash screen continuusly, connect your device to your PC and enter
Code:
adb reboot bootloader
After a few seconds the device should show up the bootloader screen
Click to expand...
Click to collapse
I'm having the same bootloop issues when trying to go to recovery after my rom is installed. After adb reboot bootloader I have to flash twrp to fix that.
Do you maybe know what can cause this issue?
For the bluetooth I saw you already applied the fix to your source
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
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
INSTRUCTIONS :
******* FULL WIPE IS REQUIRED, if you are coming from stock or Lineage 14.1 *****
******* You have to use adb commands in recovery (ex. adb push / adb shell twrp install) ******
Download the latest build and gapps
Boot to twrp ("fastboot boot recovery.img" - you can't flash twrp yet image is to big for partition)
Flash the latest build
To flash opengapps you need to put this txt file (https://androidfilehost.com/?fid=6006931924117891960) in the same directory (or you will get an error related to partition size)
this discard some apps from installation, but you can always install later from play store.... (Fixed with custom tvmini gapps)
Reboot
* If you are coming from stock rom you need to unlock your bootloader before flash twrp
** In Lineage Setup Wizard you can pair you Razer Serval or any other remote/gamepad device putting in discovery mode (autopair) or you can use an HDMI-CEC enabled TV.
BUGS:
- Secure L1 playback is broken (No Netflix, etc...)
- Remote App Voice search is broken (Fixed on 6/10 build + custom gapps)
- Some times the screen goes off and won't wake up with CEC, you can turn on the screen with your BT device or the ATV app.
- You tell me
TWRP: https://androidfilehost.com/?fid=6006931924117891945
Latest Build (October 6): https://androidfilehost.com/?w=files&flid=178900
Google Apps : https://androidfilehost.com/?w=files&flid=300260
XDA:DevDB Information
[ROM] [UNOFFICIAL] LineageOS 16.0 for Razer Forge TV (pearlyn), ROM for the Android Stick & Console Computers
Contributors
gabrielgagz, fgl27
Source Code: https://github.com/gabrielgagz/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Nightly
Created 2019-06-10
Last Updated 2019-06-11
Hi, thanks, all works great, only volume control not working, if you fix it, thats would be awesome.
Does Google Play Movies and TV work?
In the step "Boot to twrp ("fastboot boot recovery.img" - you can't flash twrp yet image is to big for partition)", my device stuck in boot screen or it'll boot into normal mode.
Could you give me more detailed instruction?
Thank you!
ClemmerC said:
Does Google Play Movies and TV work?
Click to expand...
Click to collapse
Yes, it's working
DHD said:
In the step "Boot to twrp ("fastboot boot recovery.img" - you can't flash twrp yet image is to big for partition)", my device stuck in boot screen or it'll boot into normal mode.
Could you give me more detailed instruction?
Thank you!
Click to expand...
Click to collapse
First of all you need to boot into fastboot mode (adb reboot fastbot), downoad the recovery file provided here: https://androidfilehost.com/?fid=6006931924117891945
While on fastboot, you have to execute the command "fastboot boot /path/to/recovery.img"
New build is up, remote voice search is fixed, please re install gapps with the custom provided in Google Apps link.
gabrielgagz said:
New build is up, remote voice search is fixed, please re install gapps with the custom provided in Google Apps link.
Click to expand...
Click to collapse
Would Netflix work through Chrome or a browser? Thinking I could turn my Forge into a little desktop running android.
skurtov said:
Would Netflix work through Chrome or a browser? Thinking I could turn my Forge into a little desktop running android.
Click to expand...
Click to collapse
No, You can't load Netflix trough Android Webview or browsers. User Agent and DRM stuff...
Enviado desde mi Mi A2 mediante Tapatalk
Hi gabrielgagz, thanks for the great work.
I try to compile it but get errors.
Code:
hardware/qcom/display-caf/apq8084/libhwcomposer/hwc_utils.cpp:2275:32: error: unused parameter 'ctx' [-Werror,-Wunused-parameter]
void setGPUHint(hwc_context_t* ctx, hwc_display_contents_1_t* list) {
^
hardware/qcom/display-caf/apq8084/libhwcomposer/hwc_utils.cpp:2275:63: error: unused parameter 'list' [-Werror,-Wunused-parameter]
void setGPUHint(hwc_context_t* ctx, hwc_display_contents_1_t* list) {
^
hardware/qcom/display-caf/apq8084/libhwcomposer/hwc_utils.cpp:2591:32: error: unused parameter 'ctx' [-Werror,-Wunused-parameter]
bool loadEglLib(hwc_context_t* ctx) {
^
What am I doing wrong ?
Think my forge is a brick now
I just installed the rom and it seemed to have skipped the initial setup so i couldn't sync my serval remote, but whatever i can use a usb mouse right? nope i cant use the android tv remote app either cant seem to adb into it but it seems to be in "device" mode my pc picks it up as android adb device but cant do anything any suggestions? i dont even have gapps installed yet.
stuck on boot logo
I followed the instructions use wipe in twrp first then install lineage zip and gapps zip both successfully in twrp. Cleared cache/dvlac. rebooted but stuck on boot logo, unplugged box several times and also let it run for over 60 minutes. I redownloaded and tried 2 times more. what could I have missed that would prevent Lineage from loading? do i have to do anything additional to the bootloader after reboot? Im using the 20191009 version any tips would be super swell
razorNoob said:
Hi gabrielgagz, thanks for the great work.
I try to compile it but get errors.
Code:
hardware/qcom/display-caf/apq8084/libhwcomposer/hwc_utils.cpp:2275:32: error: unused parameter 'ctx' [-Werror,-Wunused-parameter]
void setGPUHint(hwc_context_t* ctx, hwc_display_contents_1_t* list) {
^
hardware/qcom/display-caf/apq8084/libhwcomposer/hwc_utils.cpp:2275:63: error: unused parameter 'list' [-Werror,-Wunused-parameter]
void setGPUHint(hwc_context_t* ctx, hwc_display_contents_1_t* list) {
^
hardware/qcom/display-caf/apq8084/libhwcomposer/hwc_utils.cpp:2591:32: error: unused parameter 'ctx' [-Werror,-Wunused-parameter]
bool loadEglLib(hwc_context_t* ctx) {
^
What am I doing wrong ?
Click to expand...
Click to collapse
This come from Lineage sources, not from device/vendor tree. Are you trying to compile 16.0?
LOGICH4CK said:
I just installed the rom and it seemed to have skipped the initial setup so i couldn't sync my serval remote, but whatever i can use a usb mouse right? nope i cant use the android tv remote app either cant seem to adb into it but it seems to be in "device" mode my pc picks it up as android adb device but cant do anything any suggestions? i dont even have gapps installed yet.
Click to expand...
Click to collapse
Maybe a soft brick. Please provide a logcat "adb shell logcat"
finebf20 said:
I followed the instructions use wipe in twrp first then install lineage zip and gapps zip both successfully in twrp. Cleared cache/dvlac. rebooted but stuck on boot logo, unplugged box several times and also let it run for over 60 minutes. I redownloaded and tried 2 times more. what could I have missed that would prevent Lineage from loading? do i have to do anything additional to the bootloader after reboot? Im using the 20191009 version any tips would be super swell
Click to expand...
Click to collapse
Is your bootloader unlocked? If so, please provide a "adb shell logcat"
Success
Thanks for your response. Sorry for delay i was on vacation. I figured it out. The zip got corrupted durning download. Redownloaded and flashed, rebooted and loaded into Lineage. So far im very impressed with your build! I will post general steps i dit to get working since i got bits from several sites and pieced together what worked for me.
gabrielgagz said:
This come from Lineage sources, not from device/vendor tree. Are you trying to compile 16.0?
Click to expand...
Click to collapse
Yes LOS 16.0 source.
razorNoob said:
Yes LOS 16.0 source.
Click to expand...
Click to collapse
It's been a while since i don't sync or compile 16.0 (i'm mostly working on Android 10). Stupid question, are you using the correct branch for kernel (lineage-16.0)?
Thanks for the reply
gabrielgagz said:
Is your bootloader unlocked? If so, please provide a "adb shell logcat"
Click to expand...
Click to collapse
Hi sorry been busy I've tried the command but all it says in the terminal is no adb devices, my bootloader is unlocked. I've tried a different USB device in hopes of some control but so far nothing
Edit:
it seems I can use internet Via Ethernet
LOGICH4CK said:
Hi sorry been busy I've tried the command but all it says in the terminal is no adb devices, my bootloader is unlocked. I've tried a different USB device in hopes of some control but so far nothing
Edit:
it seems I can use internet Via Ethernet
Click to expand...
Click to collapse
You can always wipe your data/cache. Plug your Forge into fastboot mode (no hdmi cable, and usb cable connected to your pc) type "fastboot boot recovery.img" boot into twrp and do the wipe:
adb shell twrp wipe data/cache
Try to boot again, if that doesn't work, re-flash rom and opengapps