Database Users

Tegra Note Discoveries

I wanted to create a thread so as to report any unique findings from the internet realm regarding the Nvidia Tegra Note OEM Tablet.
Please post your own discoveries and updates!!!
Bootloader Partition Images
WARNING ONLY ADJUST PARTITIONS IF YOUR DEVICE HAS A WORKING BOOTLOADER WITH FASTBOOT
(Some early devices have a limited bootloader with no menu and no fastboot mode. If this is so, do not modify your partitions unless certain of your actions. A bootloader is a special device starting partition that later starts the extended boot partition. The bootloader should give fastboot access allowing you to re-partition or correct mistakes.)
Buttons: Power-Button + Top-Volume. Release after a few second..
= Bootloader menu should show, allowing fastboot 'on' switch
= or Blank Screen Bootloader possibly with fastboot (read above warning)
To partition your device you do need it unlocked it. The command below should do this. You need a fastboot commandline service which is usually supplied from the bootloader level. The computer used to control the changes also needs its own ADB and FASTBOOT protocol utilities.
After the below command is issued your device will reboot and user data wiped! You device should then be open for partition changes.
Code:
fastboot oem unlock
Recovery Partition Images
TWRP Recovery (Team Win Recovery Project)
Shaky Builds and Source Code
{
"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"
}
You can Root your device by installing SuperSu from the recovery mode if the zip installer allows unsigned zips.
Vendor System Recovery Images
https://developer.nvidia.com/gameworksdownload
Vendor Released Over-The-Air Based Updates
Consider:Updates can remove apps that have been moved into system partition! Example AdAway, SuperSu, Link2SD, DroidWall, etc.
Files are ripped from the below directory once downloaded and before confirming an upgrade;
Code:
/sdcard/nvidia/app/ota/download/ROM/
or direct link;
Code:
/storage/sdcard0/nvidia/app/ota/download/ROM/
(July, 2015 OTA 5.1 Lollipop. EVGA Version 3.0) 446.3MB
tegra_note_7_system_update_3.0__5.1.zip
ERROR NOTICE. The first release of lollipop consumes most of the system folder. Those trying to install further items will experience an out of storage error. A remedy is to use a root mode utility like Link2sd to remove unwanted system apps.
Example
Code:
Filesystem Size Used Free Blksize
/dev 444.8M 40.0K 444.8M 4096
/sys/fs/cgroup 444.8M 12.0K 444.8M 4096
/mnt/asec 444.8M 0.0K 444.8M 4096
/mnt/obb 444.8M 0.0K 444.8M 4096
/system 755.9M 754.3M 1.6M 4096 <<<
/cache 755.9M 12.8M 743.2M 4096
/data 12.6G 1.0G 11.6G 4096
/mnt/factory 15.7M 4.0M 11.7M 4096
/lbh 252.0M 51.0M 201.0M 4096
USB
Device USB Coding
Code:
ID 0955:7535 Rev. 0102 NVidia Corp. APX
ID 0955:CF00 Rev. 0232 NVidia Tegra Note
Linux users are well supported for USB access. They also can easily install latest ADB and Fastboot from distribution repositories.
ADB and Fastboot (Client) Executables
XDA-Developers Thread
Microsoft Windows USB Drivers from Nvidia
NvidiaUSBDrivers_Rel20131017
UART Ability?
After an inspection I can't see any points to which one could easily tap into an 'exposed console' with a USB UART setup. This could indicate there is no allocation to access a terminal from a tapped in serial port or pins off the minute and well protected chipsets. Obviously those that want to software repair these tablets have access to NvFlash/APX mode, in dire situations.
NVFLASH/APX
NvFlash_v3p08p1700_RipV2 (Executables for; Linux, Mac, Microsoft)
Buttons: Power-Button + Top-Volume + Bottom-Volume. Release Power-Button only once you see branding. Release others after few seconds.
= Screen should remain black. USB connection should see Nvidia APX Device (USB ID 0955:7535).
Linux Users should copy their executable to the below directory so that it's globally available from all bash points
Code:
/usr/local/bin
NVFLASH/APX BASED RECOVERY (POSSIBLE FIX FOR BRICKED DEVICES)
Advent Computers APX Recovery
Linux users can add the nvflash executables shared above. Put the device in APX mode and issue the below command. You can replace the images in the folder to suit a different recovery or boot, etc.
Window's users can execute 'flash_signed.bat' from the command line to start the process. If you get ID errors, then perform the Linux command below without the 'sudo' section at front.
Unplug any other device. Do not use this unless your tablet is bricked as it will tailor the tablet to a particular brand and therefore hardware may not work correctly.
Code:
sudo nvflash --blob blob.bin --bct flash_signed.bct --setbct --odmdata 0x4069E000 --odm limitedpowermode --configfile flash_signed.cfg --create --bl bootloader_signed.bin --reset normal 0
Standard Blob Image (includes unpacked items)
TegraNote_blobrip_4p4rip.zip
TegraNote_blobrip_4p3p1p1.zip
Standard Boot Image (includes unpacked items)
TegraNote_bootimg_4p4rip.zip
TegraNote_bootimg_4p3p1rip.zip
RESTORE DEVICE WITH FASTBOOT IMAGES
Rootjunkysdl's Firmware Downloads
KERNEL SOURCE
http://nv-tegra.nvidia.com/gitweb/
Guides
Tomsgt has made various video tutorials on how to root-mode your device, among other topic. See here for videos..
Tom hosts his own array of core files;
Rootjunkysdl.com
ALTERNATIVE SYSTEMS
CHALLENGE CHALLENGE CHALLENGE CHALLENGE CHALLENGE
No one has yet customised another operating system for the Tegra Note 7.
* Ubuntu Touch
* Firefox OS
* Sailfish
* Plasma Active
* Tizen
Known Vendors of the Tegra Note Tablet
Advent Tegra Note 7 (http://www.adventcomputers.co.uk/)
Colorful Tegra Note 7 (http://en.colorful.cn/)
Colorfly T709 (?)
EVGA Tegra Note 7 (http://www.evga.com/)
Gigabyte Tegra Note 7(http://www.gigabyte.com.au/)
Gradiente Tegra Note 7(http://www.gradiente.com.br/)
Granville Flyone Homecare Tegra Note 7 P1640 (http://www.huiweipad.com/)
PNY Tegra Note 7 (http://www.pny.com/)
Oysters Tegra Note 7 (?)
XOLO Play Tegra Note 7 (http://www.xolo.in/xolo-play-tegra-note/)
Zotec Tegra Note 7 (http://www.zotac.com/)
***** POWER USERS *****
Install F-Doid App Store
F-droid is a safe repository of open source code Android Apps. Many Apps unavailable from Google's Store.
Recommend
~~~~~~~~~~
* AdAway (Removes Ads from Apps by blocking content)
* Hackers Keyboard
* AFWall (IPTable Firewall)
* VLC Player (official release) VideoLan
Xposed Installer
Xposed is a framework for modules that can change the behavior of the system and apps without touching any APKs. That's great because it means that modules can work for different versions and even ROMs without any changes (as long as the original code was not changed too much). It's also easy to undo. As all changes are done in the memory, you just need to deactivate the module and reboot to get your original system back. There are many other advantages, but here is just one more: Multiple modules can do changes to the same part of the system or app. With modified APKs, you to decide for one. No way to combine them, unless the author builds multiple APKs with different combinations.
.

Installing Google Play on Nvidia Tegra Note.
0. Get a powerful Recovery partition image on your Tablet.
1. Obtain a Google Apps pack, usually termed GAPPS suited to your Android version.
2. Use Recovery's install zip mode to install.

Lollipop Fresh Installation + Tweaking
(for those with basic knowledge of Android manipulation)
* Make sure your tablet is OEM unlocked. Then flash a sophisticated recover image version like TWRP. This will allow root-mode enabling via a patch.
To obtain fastboot-mode, you need another computer as the debugging/command platform via USB. Holding the POWER-BUTTON and UP-VOLUME on the boot and shortly after releasing the POWER-BUTTON and later the other, will bring up a bootloader menu that can deploy fastboot protocol/mode or get to recovery-mode. This is where you can flash, oem unlock, and erase partitions, with the data coming from your command-platform. You can't format nor erase partitions till you oem-unlock the device, noting an oem unlock clears your device's user data.
Your command-platform (controlling computer used to upgrade the Tegra Note) also needs its own version of ADB (Android Debugging Bridge) and FASTBOOT protocols so as to be able to talk and understand the conversation over the USB.
RootJunky also has versions of TWRP and other recovery image versions.
* Put the tablet into fastboot-mode and flash RootJunky's shared Lollipop restore image instead of the upgrade over the air (OTA). Good idea to erase particular partition before flashing.
* Boot to the recovery stage. Install latest SuperSu.zip using sideloader or having it already on a SD. This will enable root mode.
https://download.chainfire.eu/740/SuperSU (Get Beta if available.)
* Start system. Remove Apps from system partition unneeded, or that can be moved or installed to user directory instead. This frees up vital space. Example Lollipop only leaves a few megabytes left in the system partition after installation. Consider using Link2SD. Example get Google+, Google Play, Google Magazine, etc into the user partition and any other big App off your system partition. The system partition should only have important apps needed to be retained if a factory wipe is enacted.
* Then go through all your system settings make sure you tweak them to suit both power saving and your own desires.
* Use a start-up tool like ES Task Manager to remove apps starting that don't need to be running from system boot.
* Install all Google Apps wanted. This can help to configure the system how it's meant to be.
* You could install Google Now into the system partition and remove the Launcher3 App.
* The system should now run smooth and use little battery.
.

Nice bro....keep me posted... Pre ordered xolo tegra note
Edit : got my tegra note 7

Wow fantastic find! Seriously psyched for the recovery. One step closer to roms!

Very good
Enviado do meu Moto X usando Tapatalk

[RESERVED]
.

[RESERVED]

I can not download the files to install the Play store ... Somebody help me?
Enviado do meu Moto X usando Tapatalk

ezequielbsb said:
I can not download the files to install the Play store ... Somebody help me?
Enviado do meu Moto X usando Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2397942
Get 4.3 versions since still Jellybean.

The Cydia Impactor just successfully rooted my Slate 8 (Tegra 4 platform, v. similar to the Note)
Might be worth a go?
Discussed here:
http://forum.xda-developers.com/showthread.php?t=2386677

I am looking for the drivers for this device I am on windows and cant get the adb drivers installed. Please Help

Cydia Impactor
roustabout said:
The Cydia Impactor just successfully rooted my Slate 8 (Tegra 4 platform, v. similar to the Note)
Might be worth a go?
Discussed here:
http://forum.xda-developers.com/showthread.php?t=2386677
Click to expand...
Click to collapse
Worked within 20 seconds. Even loaded the USB drivers for me!

Tomsgt said:
I am looking for the drivers for this device I am on windows and cant get the adb drivers installed. Please Help
Click to expand...
Click to collapse
I had the same problem when I was trying to use Helium to restore some apps. Windows 7 64 bit was able to install two of the three component 'parts' of the tablet but not the final driver. After the device installer had finished in opened Control Panel on the PC and then the Device Manager. The Note should be listed in Device Manager with a yellow exclamation mark. Right click on it and select 'update driver'. In the next window choose to install the driver yourself, then opt to choose from a list of drivers manually. Next choose the entry called 'Android Phone', then select 'composite ADB device' from the list on the right. I'm saying this from memory I may have missed a step so tread carefully. I already had the desktop Helium app installed on my PC which installation ADB drivers (they'll appear under Clockwork Mod in the driver list I mentioned). I'm away from my PC for now so it'll be a while before I can refine these instructions.
These are just basic observations, but I've playing around with the Note connected to a TV and USB hub etc
http://forum.xda-developers.com/showthread.php?p=48416270#post48416270
I haven't tried wireless display yet. I hope to by a Miracast/DLNA compatible adapter for my TV soon so I can see what works. Full screen mirroring is what I'm aiming for.

becksvector said:
Worked within 20 seconds. Even loaded the USB drivers for me!
Click to expand...
Click to collapse
Did you already have the drivers downloaded and installed to your machine, or did it use its own drivers?
that'd be great if folks no longer need to get the drivers manually set up and override the crying about mismatches.

My Tegra Note Homecare Fly One does not connect on my PC ..
Does anyone have the drivers?
thank you

I made a discovery.....Battery drain issue.....battery drains really fast even when on power save settings with prism and running on 1 core..... Even when im not even using it like the memory is clean and cache is clear and everything.......After 100% charge it barely lasts me 6 hours of a day at college when im using it on and off....Like word processing and taking a couple of photos thats it.....
So after a few days since I got it the battery started getting better and better......So what was 6 hours of on and off usage of my tablet is not almost 24 hours of the same kinds of usage with still 45% ish of battery remainig!!!!! So I guess the way we charge our devices makes a difference as well....Batery doctor has a feature that charges the device in a specific way like as fast as possible to 80% then slows current down to prelong battery life. I want to see how long my battery will last and will upload screenshots while im doing so.....Right now it is 10:26 pm and battery is at 43% with 22 hours and 2 mins on battery.

Working with a Developer on CWM recovery for this device
Root video if anyone needs help
http://youtu.be/0521gm9ajz4

Been looking for a game stream apk or mod if anyone has it.

roustabout said:
Did you already have the drivers downloaded and installed to your machine, or did it use its own drivers?
that'd be great if folks no longer need to get the drivers manually set up and override the crying about mismatches.
Click to expand...
Click to collapse
I had some element of a connection as my computer could see the tablet for transferring media. But after pressing the USB button I had the lot!

[Recovery][kipper] Team Win Recovery Project for the Wileyfox Storm

Team Win Recovery Project 3.0.2
Notice: This is a test build as a start to becoming an official build, I am looking for feedback right now - do not consider this stable!
I am currently looking for users to test all the features and report back with what works.
Quote the 2nd post and put a pass or fail in each of the [ ] boxes!
Please, if you can, post your recovery.log after doing the tests that fail, as well as dmesg.log
Code:
adb shell cat /tmp/recovery.log > recovery.log
adb shell dmesg > dmesg.log
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
https://idlekernel.com/twrp/kipper/ (temporary! THESE ARE TEST BUILDS!)
Find instructions on how to unlock and root your device with fastboot here:
https://twrp.idlekernel.com/devices/wileyfoxstorm.html (temporary device page - do not download from here!)
CHANGES
v3.0.2-0 - See here for the changes.
FEATURES
MTP support
USB Mass Storage support
Micro SDcard support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Brightness node not set (unknown location, join #twrp to help!)
Battery status possibly unknown
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
Device tree: https://github.com/jcadduono/android_device_wileyfox_kipper
Kernel sources: https://github.com/jcadduono/android_kernel_cyanogen_msm8916/tree/twrp-6.0
TWRP: https://github.com/omnirom/android_bootable_recovery
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Wileyfox Storm, Tool/Utility for the Wileyfox Storm
Contributors
jcadduono, The Team Win Recovery Project team
Source Code: https://github.com/jcadduono/android_device_wileyfox_kipper
Version Information
Status: Testing
Current Beta Version: 3.0.2-0
Beta Release Date: 2016-04-27
Created 2016-04-28
Last Updated 2016-04-29

TWRP functional checklist
Code:
Blocking checks
[ ] - Correct screen/recovery size
[ ] - Working touchscreen
[ ] - Backup to internal/microSD
[ ] - Restore from internal/microSD
[ ] - Reboot to system
[ ] - ADB & ADB shell
[ ] - Flash zips in Install page
[ ] - Flash boot.img/recovery.img using Flash Image in Install page
Medium checks
[ ] - Flash zip with ADB sideload
[ ] - UI colors (red/blue inversions)
[ ] - Screen goes off (and back on :))
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[ ] - System, Data, Internal Storage, microSD card, and Firmware partitions listed in mount/backup choices
[ ] - Decrypt encrypted /data
[ ] - Correct date
[ ] - MTP read/write
[ ] - USB Mass Storage read/write
[ ] - Set brightness level
Minor checks
[ ] - Reboot to bootloader
[ ] - Reboot to recovery
[ ] - Power Off
[ ] - Battery level
[ ] - Temperature
[ ] - Encrypted backups
[ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition

jcadduono said:
Code:
Blocking checks
[Pass ] - Correct screen/recovery size
[ Pass] - Working touchscreen
[ ] - Backup to internal/microSD
[ ] - Restore from internal/microSD
[Pass] - Reboot to system
[ ] - ADB & ADB shell
[ ] - Flash zips in Install page
[ ] - Flash boot.img/recovery.img using Flash Image in Install page
Medium checks
[ ] - Flash zip with ADB sideload
[ ] - UI colors (red/blue inversions)
[ ] - Screen goes off (and back on :))
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[ ] - System, Data, Internal Storage, microSD card, and Firmware partitions listed in mount/backup choices
[ ] - Decrypt encrypted /data
[ ] - Correct date
[ ] - MTP read/write
[ ] - USB Mass Storage read/write
[ ] - Set brightness level
Minor checks
[ ] - Reboot to bootloader
[ ] - Reboot to recovery
[ ] - Power Off
[ ] - Battery level
[ ] - Temperature
[ ] - Encrypted backups
[ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition
Click to expand...
Click to collapse
I really want to see this get done but I don't have time to test everything right now. Done some basic tests, will edit with the rest whenever I have the time to do so.

Hi, I'm on CM13 and i cannot maount microsdcard and usbotg in TWRP, any solutions?

aciupapa said:
Hi, I'm on CM13 and i cannot maount microsdcard and usbotg in TWRP, any solutions?
Click to expand...
Click to collapse
Flashed twrp-3.0.2-0-test3-kipper.img and found unable to use mirco SD card as available storage.
Previously had TWRP-2.8.7.0-kipper-recovery on device, however after updating to CM13 this was unable to find/use micro SD card as available storage too.
Marshmallow issue or recovery one.

To acces microsd and otg, you need to flash COS12.1.1, then it magically works. To use it on cm13 you need to backup cm13 install COS12 and resrore cm13 (yeah, complicated)
Sent from my Wileyfox Storm using XDA Labs

aciupapa said:
To acces microsd and otg, you need to flash COS12.1.1, then it magically works. To use it on cm13 you need to backup cm13 install COS12 and resrore cm13 (yeah, complicated)
Click to expand...
Click to collapse
So create a TWRP backup, install cos12 then simple restore the back and should work?

Yes. I use it like this now
Sent from my Wileyfox Storm using XDA Labs
---------- Post added at 08:20 PM ---------- Previous post was at 08:20 PM ----------
But after flashing cos12 reboot into recovery ans check if partitons mount
Sent from my Wileyfox Storm using XDA Labs

aciupapa said:
Yes. I use it like this now
Sent from my Wileyfox Storm using XDA Labs
---------- Post added at 08:20 PM ---------- Previous post was at 08:20 PM ----------
But after flashing cos12 reboot into recovery ans check if partitons mount
Click to expand...
Click to collapse
I Google for a TWRP cos 12.1.1.zip however no joy.
Fail to install via a custom recovery users advised.
The issue only occurred after I installed CM13, that's when TWRP couldn't find microsd storage.

Go to cyngn.com/support and look for zip withouth fastboot in name
Sent from my Wileyfox Storm using XDA Labs

aciupapa said:
Go to cyngn.com/support and look for zip withouth fastboot in name
Click to expand...
Click to collapse
Installed the none fastboot cos 12.1.1 zip via recovery, then let it run the install build, however when I rebooted into recovery I was unable to get the external sdcard to be accessible still.
Thanks for suggested fix. :good:

Idk, why, but it always helps me. have you rebooted phone after COS12 flashing?

aciupapa said:
Idk, why, but it always helps me. have you rebooted phone after COS12 flashing?
Click to expand...
Click to collapse
I made TWRP backup of my current CM13 ROM, then wiped all partitions except internal and external SD card storage. Installed cos12.1.1 zip within TWRP, then rebooted to let stock lollipop ROM initialised. Then rebooted to TWRP to find external SD still not found.

Maybe try reflashing twrp

aciupapa said:
Maybe try reflashing twrp
Click to expand...
Click to collapse
I tried reflashing TWRP-2.8.7.0 recovery, then twrp-3.0.2-0-test3-kipper, cm-13.0-20160305-recovery and final cm-12.1-none-sign-recovery.
None of them could find the external SD card only internal storage. Would love to say it worked however sadly not. When on stock lollipop 5.0.1 all the recovery storage paths worked, so you would think installing cos 12.1.1 zip would restore things.
Have noticed that the original boot loader has returned, but not the battery charging while powered down image that you see getting fuller if you hit the power button. The original one was much larger under stock.
What's the function of the image file compared to the zip one please?
cm-12.1-YOG7DAS2FI-kipper-boot-debuggable-a7322d8c3a.img

Did a final version get abandoned after the test 3 release?

Probably to less tests?
I loved TWRP on my good old S2 (which seems to have NAND rw corruption since last week). Now I have the Storm I would love TWRP on my device too, but it needs proper testing.
I'm wondering: what are the risks of testing this? I might be able to help.

Well I have the test 3 one running on my storm, no issue's found.

Ok thanks. I'll try flashing it.

Blinkin89 said:
Ok thanks. I'll try flashing it.
Click to expand...
Click to collapse
Link updated in next post
None test version here

[Recovery][Exynos] Official TWRP for the Galaxy Note 7 (gracelte)

Team Win Recovery Project 3.0.2-1
This is for the International SM-N930F/X, Duos SM-N930FD, and Korean SM-N930K/L/S Exynos models only! Do not flash on Snapdragon models!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy Note 7 stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
WARNING #3: When using custom kernels on the Note 7, never turn off developer options or OEM unlock. If you do, you will lose all your data and have to flash a full stock firmware restore to use your device again!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxynote7exynos.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ to flash when possible.
You can find a zip containing Odin as well as Samsung's Mobile drivers here:
https://build.nethunter.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"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"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Do not ever turn off Developer Options or OEM unlock. Doing so will cause your device to refuse to boot and require a full factory restore.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for gracelte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] + [Power] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 6.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest Samsung Anti-Root Protection Removal zip.
Without exiting TWRP, transfer the samsung-antiroot-removal zip to your device over MTP* and flash it using [Install] in TWRP.
This zip will allow you to flash SuperSU versions earlier than 2.77 and use other rooting methods.
It uses a hex pattern (by Chainfire) replacement method in the kernel that simply disables the anti-rooting protection.
It will also disable the status bar notification about unauthorized changes.
It includes the functions of the no-verity-opt-encrypt zip.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-1 - Fix restoring of non-ext4 partitions, update f2fs drivers, update to BPID source & Linux 3.18.43, add 60% battery charging limiter
v3.0.2-0 - Official release on twrp.me
v3.0.2-0-b3 - Fix colors and use NTFS-3G
v3.0.2-0-b2 - Initialize new device tree based on Samsung OSRC N930FXXU1APGK kernel source.
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (International): https://github.com/TeamWin/android_device_samsung_gracelte (android-6.0)
Device tree (Korea): https://github.com/TeamWin/android_device_samsung_graceltekor (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_universal8890 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy Note 7, Tool/Utility for the Samsung Galaxy Note 7
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_gracelte
Version Information
Status: Stable
Current Stable Version: 3.0.2-1
Stable Release Date: 2016-10-15
Created 2016-08-23
Last Updated 2016-11-08

jcadduono said:
Team Win Recovery Project 3.0.2-0-b2
This is for the International SM-N930F/X, Duos SM-N930FD, and Korean SM-N930K/L/S Exynos models only! Do not flash on Snapdragon models!
snip
Click to expand...
Click to collapse
For the current note 7 series, @jcadduono will be the primary maintainer. I will subscribe to this thread however, I will be getting the n930fd. Good job @jcadduono!

Thank you very much sir and i try now
Sent from my SM-N930F using Tapatalk

I am away from PC but will try later tonight or tomorrow. Meanwhile any N930F users face any issue or got bootloop after testing here is stock recovery and kernel based on N930FXXU1BPH6 to fix bootloop
http://d-h.st/cHao
Flash it with Odin for AP tab
I have faced this y'day while modifying CF auto root and experienced that it may fail initially to flash soon after Odin log showing Initializing - Fail
Repeated attempt should work.

...on your mark, get set, go! Bye bye Samsung Pay... again...

Nice to see you here, Im using your rom on my note 4, s6, next is note 7, but my note 7 is 930FD, 2sim, so I have to wait more...
dr.ketan said:
I am away from PC but will try later tonight or tomorrow. Meanwhile any N930F users face any issue or got bootloop after testing here is stock recovery and kernel based on N930FXXU1BPH6 to fix bootloop
http://d-h.st/cHao
Flash it with Odin for AP tab
I have faced this y'day while modifying CF auto root and experienced that it may fail initially to flash soon after Odin log showing Initializing - Fail
Repeated attempt should work.
Click to expand...
Click to collapse

lehongwang said:
Nice to see you here, Im using your rom on my note 4, s6, next is note 7, but my note 7 is 930FD, 2sim, so I have to wait more...
Click to expand...
Click to collapse
Yeah Samsung has so far only released APGK and not FD's BPH6. I don't know if the S7 bootloader changed that happened in BPH6 on G930 also applies to N930FD though, so this might work for N930FD just the same as N930F.

It works!

Whats the status on Canada/US models?
I have an N930W8, waiting patiently for root ^.^
Also, I remember having pretty bad wakelock / deep sleep problems with the Note 5 root, has that issue been figured out for Note devices? I remember having to use a modified SU and Dr.Ketans deep sleep fix in order to have my Note 5 sleep properly. Just wondering if this is still a thing or not ^.^

i23u8 said:
It works!
Click to expand...
Click to collapse
Awesome! If you have the time, join #twrp on irc.freenode.net and upload recovery.log for us from the build. We need to make sure everything is detected and pointed to the right locations, as well as features working.
Here's a checklist if you want to go through it for us as well:
Code:
Blocking checks
[ ] - Correct screen/recovery size
[ ] - Working touchscreen
[ ] - Backup to internal/microSD
[ ] - Restore from internal/microSD
[ ] - Reboot to system
[ ] - ADB & ADB shell
[ ] - Flash zips in Install page
[ ] - Flash boot.img/recovery.img using Flash Image in Install page
Medium checks
[ ] - Flash zip with ADB sideload
[ ] - UI colors (red/blue inversions)
[ ] - Screen goes off (and back on :))
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[ ] - System, Data, Internal Storage, microSD card, and Modem/Firmware/EFS (if applicable) partitions listed in mount/backup choices
[ ] - Decrypt encrypted /data
[ ] - Correct date
[ ] - MTP read/write
[ ] - USB Mass Storage read/write
[ ] - Set brightness level
Minor checks
[ ] - Reboot to bootloader
[ ] - Reboot to recovery
[ ] - Power Off
[ ] - Battery level
[ ] - Temperature
[ ] - Encrypted backups
[ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition
Use pass or fail in each box.
Data encryption/decryption will most certainly not work.
imatts said:
Whats the status on Canada/US models?
I have an N930W8, waiting patiently for root ^.^
Also, I remember having pretty bad wakelock / deep sleep problems with the Note 5 root, has that issue been figured out for Note devices? I remember having to use a modified SU and Dr.Ketans deep sleep fix in order to have my Note 5 sleep properly. Just wondering if this is still a thing or not ^.^
Click to expand...
Click to collapse
They will never receive TWRP support and it's unlikely that they will ever see root either, unless an engineering boot image is leaked similar to what happened with the S7, but being stuck on an old kernel for the rest of your devices life just to root is kind of crappy. Do advise selling it and buying an F or FD Exynos model.

Ok I can confirm - TWRP works
Root - No
Root didn't work may be because of I have updated to latest base PH6 and believe this base have some changes and issue reported on S7 on this base as well
Before this Y'day I have modified CF auto root based on PH6 recovery and sent log to CF as well tested file from CF as well. According to @Chainfire he is aware of this and he will first fix S7 issue and probably this should fix for us as well.
So game started and have to wait till new magic from @Chainfire
Again thank to @jcadduono and @bigbiff for great work. Again Thank you very much to all involved to this project behalf of N7 community.
Here attached logs.
PS : Very busy today and just arrived from out, couldn't resist to test. Will report more details later
Regards
Dr.Ketan

dr.ketan said:
Again thank to @jcadduono and @bigbiff for great work. Again Thank you very much to all involved to
Dr.Ketan
Click to expand...
Click to collapse
+1
thanks to all for your help!

Do I have to flash both SuperSU and no-verity? Or SuperSU alone is fine?
Also tried this on both APG7 and BPH6 and they bootloop.
Here are the results of the testing so far:
Status Blocking checks
Pass [ ] - Correct screen/recovery size
Pass [ ] - Working touchscreen
Pass [ ] - Backup to internal/microSD
[ ] - Restore from internal/microSD
Pass [ ] - Reboot to system
Pass [ ] - ADB & ADB shell
Pass [ ] - Flash zips in Install page
Pass [ ] - Flash boot.img/recovery.img using Flash Image in Install page
Medium checks
[ ] - Flash zip with ADB sideload
Pass, yellow [ ] - UI colors (red/blue inversions)
Pass [ ] - Screen goes off (and back on )
Pass [ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
Pass [ ] - System, Data, Internal Storage, microSD card, and Modem/Firmware/EFS (if applicable) partitions listed in mount/backup choices
[ ] - Decrypt encrypted /data
Pass [ ] - Correct date
[ ] - MTP read/write
Pass [ ] - USB Mass Storage read/write
Pass [ ] - Set brightness level
Minor checks
Pass [ ] - Reboot to bootloader
Pass [ ] - Reboot to recovery
Pass [ ] - Power Off
Pass [ ] - Battery level
Pass [ ] - Temperature
[ ] - Encrypted backups
Pass [ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition

It's works but no root
Sent from my SM-N930F using Tapatalk

i23u8 said:
Do I have to flash both SuperSU and no-verity? Or SuperSU alone is fine?
Also tried this on both APG7 and BPH6 and they bootloop.
Click to expand...
Click to collapse
Flash supersu on apg7 and see if boot
If not
Flash stock files I have provided on prev page
Flash twrp
Flash dm verify disabler
Now device will boot

Fixing screen colors, yellow should not be normal lol.
Okay what I want to know is:
Does USB-OTG work?
Does mounting and writing to NTFS work?
Does mounting and writing to exFAT work?
Does mounting and writing to f2fs work?
Does MTP work (microSD card)?
Does MTP work (format internal storage to mount data unencrypted after flashing opt-encrypt zip)?
Does USB Mass Storage button work in Mount page (with external SDcard) - allows oldschool access to microSD from PC?
Output of following commands from terminal:
Code:
ls -l /dev/block/bootdevice/by-name/
cat /proc/partitions
ls /dev/block

dr.ketan said:
Flash supersu on apg7 and see if boot
If not
Flash stock files I have provided on prev page
Flash twrp
Flash dm verify disabler
Now device will boot
Click to expand...
Click to collapse
Hi Dr Ketan, I've flashed APG and SuperSU and it didn't boot, it loops.
I'm able to recover the phone.
Hi jcadduono,
Does USB-OTG work? Yes it works.
Does mounting and writing to NTFS work? Yes, my external HDD on NTFS works.
Does mounting and writing to exFAT work? Yes it works, my USB-OTG is exFat.
Does mounting and writing to f2fs work? I didn't convert any of my storage.
Does MTP work (microSD card)? Yes, it works.
Does MTP work (format internal storage to mount data unencrypted after flashing opt-encrypt zip)? Yes it works before I make my first boot to system.
Does USB Mass Storage button work in Mount page (with external SDcard) - allows oldschool access to microSD from PC? Yes this works.
Apart from those I havent tested, booting to system and then booting back to TWRP, I lose access to the data partition and it looks like I need to re-wipe and install no-verity.

i23u8 said:
Apart from those I havent tested, booting to system and then booting back to TWRP, I lose access to the data partition and it looks like I need to re-wipe and install no-verity.
Click to expand...
Click to collapse
Is it encrypting again after installing no-verity zip? This was an issue on Exynos 7870 and if it's happening on 8890 that would be terrible. (they made it impossible to disable encryption on 7870)
Also, see if the colors are fixed in https://idlekernel.com/twrp/gracelte/twrp-3.0.2-0-b3-gracelte.tar.md5
They should be blue and black and grey, no yellow!
And check NTFS again, I removed kernel driver for pure ntfs-3g to see if I could trim it down a little and make NTFS more stable.

Just two things to add to previous report
1.flashing from USB storage working
2.adb and and shell working from recovery

I kind of liked the yellow, it looked more like Parallax-y.
Confirmed that the colors are back to the normal blue, black, gray combo.
I'm not able to recheck NTFS because I stepped away from my bag to attend to work for a few minutes (then back to reflashing).

[ROM][WIP]Ubuntu Touch 16.04 for Xiaomi MI3[cancro]

Ubuntu Touch 16.04 For Xiaomi Mi3​
/*
* I'm not responsible for bricked devices, dead SD cards, ecc...
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
Click to expand...
Click to collapse
Hello everyone! Today i'm here to share with you a porting of ubuntu touch done by me, i used halium to develop it, so thanks to halium group and for their support.
Requirements
-You can use which operating system do you want
-Adb & Fastboot tools, you can download it here.
-The phone needs to be updated to android 6 or higher.
-Download all the files in this folder: folder.
-TWRP recovery, you can found it here.
Ok, let's start!
-Unzip my file
-Reboot your phone to recovery mode and connect it to the pc
-Open a terminal or cmd and run this commands: adb push system.img /data/system.img and adb push rootfs.img /data/rootfs.img
-Once it is done click on reboot and click on bootloader.
-When you are on fastboot mode run this command: fastboot flash boot halium-boot.img and fastboot reboot
-Done!
The default username is: phablet and password is: 12345
When the phone turns on run this command "echo manual > /etc/init/rsyslog.conf" and reboot so the process which uses all the cpu won't start up.
For audio you need to run "pulseaudio --start"
Wifi is buggy(sometimes work and sometimes no), when you turn on your phone you need to run this commands to turn on wifi
-sudo -i
-echo 1 > /dev/wcnss_wlan
-echo sta > /sys/module/wlan/parameters/fwpath
P.S Remember. It has some bugs, some apps crashing, audio not working and camera don't work! (GSM works, you can also use data but you can't call someone and you can't receive calls; SMS works).
If someone can help me he can send me a mail or comment below.
Try it and send me some feedbacks! Thank you!
Update
I see your comments and i tried myself. Halium-boot.img and system.img were corrupted so i uploaded all the file instead of zipping them.
With the latest update run these command to reduce the cpu usage:
- sudo -i
- mkdir /etc/system-image/config.d
- Reboot the phone

Reserved

Thanks Mattia!
I will try to understand it.
And after I will try to install too.
小米MIX标准版4GB128GB银色MIUI10中国开发者8.8.13.

halium-boot.img error
Hi Mattia990!
Thank you very much for your work!
The halium-boot.img file flash after an error:
Code:
target reported max download size of 805306368 bytes
sending 'boot' (12956 KB)...
OKAY [ 0.421s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.425s
Update:
I tried to install the boot image with TWRP. It will not start in 20 minutes.

rajen77 said:
Hi Mattia990!
Thank you very much for your work!
The halium-boot.img file flash after an error:
Code:
target reported max download size of 805306368 bytes
sending 'boot' (12956 KB)...
OKAY [ 0.421s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.425s
Update:
I tried to install the boot image with TWRP. It will not start in 20 minutes.
Click to expand...
Click to collapse
You have to unzip my file, go into "Ubuntu Mi3 Funz", open terminal app and do fastboot flash boot halium-boot.img

rajen77 said:
Hi Mattia990!
Thank you very much for your work!
The halium-boot.img file flash after an error:
Code:
target reported max download size of 805306368 bytes
sending 'boot' (12956 KB)...
OKAY [ 0.421s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.425s
Update:
I tried to install the boot image with TWRP. It will not start in 20 minutes.
Click to expand...
Click to collapse
CONFIRMED
target reported max download size of 805306368 bytes
sending 'boot' (12956 KB)...
OKAY [ 6.521s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 35.141s
of course all 3 files unzipped IMG
and I've followed correctly your tutorial step-by-step

I think we have to leave these unnecessary circles on how to install fastboot with something we know about it.
We're trying Windows with the latest fastboot components so far, all files have been installed on all phones, but that's not the case. I'm sorry, now I can not ask Linux to try it there, at most in a virtual machine.

Files uploaded

Mattia990 said:
Files uploaded
Click to expand...
Click to collapse
SUCCESS with NEW files !!! THANKS !!!!

@Mattia990
next problem, when I typed to Terminal
echo 1 > /dev/wcnss_wlan
I got: -bash: echo: write error: Bad address - message
What can I do? coz defaultly no Wi-Fi...

JulianJenner said:
@Mattia990
next problem, when I typed to Terminal
echo 1 > /dev/wcnss_wlan
I got: -bash: echo: write error: Bad address - message
What can I do? coz defaultly no Wi-Fi...
Click to expand...
Click to collapse
I know it's a known problem.
Try the other commands

Mattia990 said:
I know it's a known problem.
Try the other commands
Click to expand...
Click to collapse
Okay.
Solved.
You must ignore the error message after the third command and move on to the fourth command.
Ok. Now Wi-Fi working.
---------- Post added at 05:08 PM ---------- Previous post was at 04:50 PM ----------
Ok. Last, but MAIN issue...
It have no incoming and outgoing calling... GSM is not working... for me.
You wrote: "...It has some bugs, some apps crashing, audio not working and also the camera doesn't work..."
Okay no sound...but it is not able to receiving calls without sound, nothing happened on screen when I call my number...

JulianJenner said:
Okay.
Solved.
You must ignore the error message after the third command and move on to the fourth command.
Ok. Now Wi-Fi working.
---------- Post added at 05:08 PM ---------- Previous post was at 04:50 PM ----------
Ok. Last, but MAIN issue...
It have no incoming and outgoing calling... GSM is not working... for me.
You wrote: "...It has some bugs, some apps crashing, audio not working and also the camera doesn't work..."
Okay no sound...but it is not able to receiving calls without sound, nothing happened on screen when I call my number...
Click to expand...
Click to collapse
Sorry i haven't tested GSM because i haven't got a normal sim. I will resolve it. Sorry for the incovenience.

Mattia990 said:
Sorry i haven't tested GSM because i haven't got a normal sim. I will resolve it. Sorry for the incovenience.
Click to expand...
Click to collapse
No problemo! This is alpha test.

it need 15-20 minutes for boot?
Edit: i had aosp android 9, i wipe system,data, cache and install ubuntu touch with adb on recovery then with fastboot.Rebbot and it no boot, i wait 40 minutes...

harris123424 said:
it need 15-20 minutes for boot?
Edit: i had aosp android 9, i wipe system,data, cache and install ubuntu touch with adb on recovery then with fastboot.Rebbot and it no boot, i wait 40 minutes...
Click to expand...
Click to collapse
I think it is not normal.

Running it on top of Lineage OS 14.1 and it works great (despite having the WiFi issue from time to time).
However, is there any way to decrease dpi, i.e. making UI elements bigger?

harris123424 said:
it need 15-20 minutes for boot?
Edit: i had aosp android 9, i wipe system,data, cache and install ubuntu touch with adb on recovery then with fastboot.Rebbot and it no boot, i wait 40 minutes...
Click to expand...
Click to collapse
If you have followed correctly my instruction i think the problem is android 9. Try to install android oreo or lower

the_MUKe said:
Running it on top of Lineage OS 14.1 and it works great (despite having the WiFi issue from time to time).
However, is there any way to decrease dpi, i.e. making UI elements bigger?
Click to expand...
Click to collapse
For the moment i think no

Dear @Mattia990
BT, GPS, Developer options are not switchable. These can not be turned on.
GSM not working if I call my phonenumber, I hear that ringing on the other side. But nothing happened on Ubuntu Phone: no ringing, no picture incoming call feedback...
If I try to make call, Phone application exits itself after a few seconds.
Communication with Windows PC is not working. Or I am not able to find this function When I went home I will try with my Linux laptop
Thats all for now...
...I hope you have enough time, patience, and your ability to fix these issues.
I am very proud and grateful of your work and big thanks for you because of this ROM. We are waiting for patiently.

[ROM][9.0][OFFICIAL] LineageOS 16.0 for Wileyfox Storm

[ROM][9.0][OFFICIAL] LineageOS 16.0 for Wileyfox Storm
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* 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.
*/[/COLOR]
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on kipper
IF YOU ARE CURRENTLY RUNNING LINEAGE 15.1 w/ENCRYPTION A FULL DATA FORMAT WILL BE REQUIRED TO MOVE TO 16.0. AN ISSUE WITH ENCRYPTION WAS FOUND IN 15.1 THAT CANNOT BE CORRECTED WITHOUT A FULL FORMAT
Official Download link:
LineageOS Downloads
Recommended Google Apps package:
Open GApps (choose the variant you want)
Changelog:
Changes for kipper
Bug reports:
How to submit a bug report
Donate to support development:
Donate via PayPal to jrior001
Donate via PayPal to LineageOS
XDA:DevDB Information
LineageOS, ROM for the Wileyfox Storm
Contributors
jrior001, mikeioannina
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2019-04-15
Last Updated 2019-04-15

great job
i haven't seen any problem on the first build

Brievly tested first build and not very good performance, i've not tested all things cause was laggy.
HUGE THANKS to compile android 9 ;D
---------- Post added at 03:08 PM ---------- Previous post was at 03:07 PM ----------
RastHacker said:
Brievly tested first build and not very good performance, i've not tested all things cause was laggy.
HUGE THANKS to compile android 9 ;D
Click to expand...
Click to collapse
i'll continue to test and send feedback

I have testes android 9 on multiple devices like galaxy tab a, redmi 5 plus, one plus 5t and elderdriver's xposed work great but not on wileyfox storm. Someone can telle me why?
When i reboot with xposed installed it make a blackscreen but phone is booted.

RastHacker said:
I have testes android 9 on multiple devices like galaxy tab a, redmi 5 plus, one plus 5t and elderdriver's xposed work great but not on wileyfox storm. Someone can telle me why?
When i reboot with xposed installed it make a blackscreen but phone is booted.
Click to expand...
Click to collapse
did you Wipe and Format Data ?
Code:
Installing LineageOS from recovery
Wipe
Now tap Format Data and continue with the formatting process. This will remove encryption as well as delete all files stored on the internal storage.
Return to the previous menu and tap Advanced Wipe.
Select the Cache and System partitions to be wiped and then Swipe to Wipe.
https://wiki.lineageos.org/devices/kipper/install
---------- Post added at 09:39 PM ---------- Previous post was at 09:36 PM ----------
Changes included in lineage-16.0-20190507-nightly-kipper
Code:
RotationPolicy: Don't crash if configstore 1.1 isn't available
android_frameworks_base

I'll try

For some reasons, the /system partition is resized from ~2.5GB to ~1.5GB after install, so not even the nano-gapps fit (insufficient space).
The /system partition can be "resized" back to 2.5GB via TWRP (you have to do it twice(!) to see the result), but I think, this shouldn't be hard to fix...

ghertas said:
did you Wipe and Format Data ?
https://wiki.lineageos.org/devices/kipper/install
---------- Post added at 09:39 PM ---------- Previous post was at 09:36 PM ----------
Changes included in lineage-16.0-20190507-nightly-kipper
Click to expand...
Click to collapse
Magisk say my data is not encrypted, i really need to format data?

After updating to "lineage-16.0-20190513-nightly-kipper", the /system partition was against decreased to ~ 1.5GB and had to be increased to 2.5GB from TWRP!
Screenshots:
Original size, before installing (or after resizing)
{
"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"
}
After installing LOS 16:

ghertas said:
my device couldn't find my tv via the cast
Click to expand...
Click to collapse
You're not connected to internet it's normal. Connect before to same wifi network as your tv

RastHacker said:
You're not connected to internet it's normal. Connect before to same wifi network as your tv
Click to expand...
Click to collapse
nothing
I can't find a refresh button to refresh the cast page to find my tv
i think the cast is not in the lineage rom package (kipper)

ghertas said:
nothing
I can't find a refresh button to refresh the cast page to find my tv
i think the cast is not in the lineage rom package (kipper)
Click to expand...
Click to collapse
You're tv created an other network named by your tv, it's look like "Bravia-XXXX" for sony and other for other brands. Connect to this network and now you can cast

ghertas said:
nothing
I can't find a refresh button to refresh the cast page to find my tv
i think the cast is not in the lineage rom package (kipper)
Click to expand...
Click to collapse
Wifi-direct casting does not work at all in 16.0 for most legacy devices. You can still cast to Chromecast devices but that's about it. Unfortunately I don't see this getting fixed at all as the back end for WFD changed quite a bit in P and only newer devices (with at least stock O blobs) have been able to get this working.
Sent from my Mi MIX 2S using Tapatalk

RastHacker said:
I have testes android 9 on multiple devices like galaxy tab a, redmi 5 plus, one plus 5t and elderdriver's xposed work great but not on wileyfox storm. Someone can telle me why?
When i reboot with xposed installed it make a blackscreen but phone is booted.
Click to expand...
Click to collapse
Hi,
have the same problem on my Wileyfox Storm (arm64-v8a) with Pie (OS only - no other apps installed jet) I installed.
I have testet every up to now available pie version for Storm.
Magsik v19.1 with Magisk Manager v7.1.2 (also tried v18.1 and v7.1.1)
Riru core 18 (also tried v10, v11, 15, 16)
EDXposed v4.1.2 (also tried v3.1.2, v3.1.7 and v2.9.6)
EdXposedInstaller_v2.2.4 (also tried some other Versions)
I also tried different Lineage Pie versions.
The Problem: immediatly after the boot is finished the ui becomes black and freezes completly.
For a second I could see the message Smartphone ist starting, but then it becomes black screen.
About very 5 seconds the screen flashes very short the status bar and becomes black again - seems to be a loop.
one Time, after wiping all partitions and installing lineage from scratch Xposed seems to be running fine,
but after the first boot I have the same problem.
In all cases - after removing EDXposed via TWRP Pie works fine again, but I need Xposed.
Please anybody can help?
Thanks

hjr06 said:
Hi,
have the same problem on my Wileyfox Storm (arm64-v8a) with Pie (OS only - no other apps installed jet) I installed.
I have testet every up to now available pie version for Storm.
Magsik v19.1 with Magisk Manager v7.1.2 (also tried v18.1 and v7.1.1)
Riru core 18 (also tried v10, v11, 15, 16)
EDXposed v4.1.2 (also tried v3.1.2, v3.1.7 and v2.9.6)
EdXposedInstaller_v2.2.4 (also tried some other Versions)
I also tried different Lineage Pie versions.
The Problem: immediatly after the boot is finished the ui becomes black and freezes completly.
For a second I could see the message Smartphone ist starting, but then it becomes black screen.
About very 5 seconds the screen flashes very short the status bar and becomes black again - seems to be a loop.
one Time, after wiping all partitions and installing lineage from scratch Xposed seems to be running fine,
but after the first boot I have the same problem.
In all cases - after removing EDXposed via TWRP Pie works fine again, but I need Xposed.
Please anybody can help?
Thanks
Click to expand...
Click to collapse
There is news, i finally booted with xposed 4.x elderdriver version sandhook, edxposed manager say it's working and active but any modules seems to work, they say 'module not active' even if it is. :/ and phone is laggy. (sorry for my english)

I can't install TWRP.
When I try to flash the image I get:
fastboot flash recovery twrp-3.2.3-20190306-kipper.img
target reported max download size of 268435456 bytes
sending 'recovery' (30096 KB)...
OKAY [ 0.976s]
writing 'recovery'...
OKAY [ 0.385s]
finished. total time: 1.361s
Which seems far too quick to transfer 30 Meg.
Then when I do <fastboot boot twrp-3.2.3-20190306-kipper.img>:
I get:downloading 'boot.img'...
OKAY [ 0.981s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.244s
I'd be grateful for some hand-holding, please!
Jim

vel_tins said:
For some reasons, the /system partition is resized from ~2.5GB to ~1.5GB after install, so not even the nano-gapps fit (insufficient space).
The /system partition can be "resized" back to 2.5GB via TWRP (you have to do it twice(!) to see the result), but I think, this shouldn't be hard to fix...
Click to expand...
Click to collapse
This doesn't work for me. I'm on TWRP 3.2.1.0 and whenever I let /system be resized, nothing changes.
The image has been installed by ADB Sideload. I also have rebooted the device to recovery multiple times, but the resize-operation doesn't show any results.
Sent from my Redmi Note 4 using Tapatalk

EDIT

The Download-Link does not work any more? Where can i download the latest ROM?
I get that its not supported any more, but thats no reason to remove old downloads.