Database Users

[03 JAN]Rajko's CM 6.1[RMNET]

Almost stock CM6.1 with some usability apps
Kernel from latest git standard
Download: Link removed pending warez removal from ROM
This is the way to customize an official build to a hd2 nand build
No hackery, no tricks, the way its meant to be done
You can extract it alongside CM 6.1 for desire and do a folder diff to see how to adapt a desire ROM for the HD2
Basically what i used since 03. Oct for testing Magldr, continuously updated when a new CM release is out
Readme:
Code:
Rajko's CM 6.1 NAND ROM for HTC HD2
===========================
Based on CM 6.1 official stable for the HTC Desire.
This is a continuation of the NAND ROM i was making for earlier MAGLDR builds.
Very close to CM 6.1 stock, but added additional applications for convenience, these are:
- Wifi Manager
- Quadrant Benchmark Advanced
- TasKiller
- Network Speed
- Current Widget
- Market Enabler
All applications should be up to date as of 03.01.2010.
1. Installation
===============
MAGLDR 1.10 or newer is required on the device.
Before starting the installation process, enter "USB Flasher" mode on the device
by using the Volume rocker switch to select items and the green "Call" button as the Enter key.
2. Known issues
==============
Magnetometer left/right doesn't seem to be working. Don't know what broke this. Investigating.
Due to old QDSP, camera is still the stock 800x480 of HD2.
3. Post installation notes
==============
You can change the kernel to a newer/custom version by doing the following:
Connect via USB to your HD2 while Android is running.
Spawn an ADB shell
Do the following commands as superuser:
mkdir /tmp/boot
mount -t yaffs2 /dev/block/mtdblock0 /tmp/boot
After that, you can replace the zImage that's located in /tmp/boot
When you're done, you have to unmount the boot partition, like so:
umount /tmp/boot
Restart your device to use the new kernel.

well done Rajko, will try your build.
thanks!

please Screenshot Thanks

great! will try!

Oh, first one build for Jan 3
Downloading ....

I have try a bit.
Very fast build indeed
230 mb free storage
Mobile data ok
Wifi ok
Just see until now a issue, the phone dial, dont like i typing the numbers very fast, if i do that the dial freeze for a second and the call slow to start.
Aparte of that i like the build and Tomorrow will test more this baby.

awesome..will test it
but umm..hush..hush..you might wanna take out quadrant advance =P

the normal quadrant is useless because the cpu score varies so much, so the total score isnt really indicative of anything
with advanced people can compare the individual scores, the ones that matter like IO and 2D/3D

does this kernel include WiFi fix (dynamic mac address). what governer does it use?. What about after call 60mA issue?
just FYI, if you put quadrant advanced, the mods will remove links.

it's commit 4c31f2fb265ae68b82ed5e8ea4bec91208837011 so yes
60mA is because of too recent toolchain, that was never a problem with this as i used 2010q1 since forever
60mA may happen if GPS is on, turn it off using the power control widget when you don't need it

camcorder force close
anyone else having random force closes when running camcorder? camera itself runs ok when taking pictures though...
aside from above issue, the nand/build is running great
Also,
i seem to have forgotten how to enable volume control (when playing music) even when the screen is locked/turned off? I can't find it under cyanogenmod settings
thanks

rajkosto said:
Almost stock CM6.1 with some usability apps
Kernel from latest git standard
Download: http://rajko.info/cupcake/cm610_stable_hd2.7z
This is the way to customize an official build to a hd2 nand build
No hackery, no tricks, the way its meant to be done
You can extract it alongside CM 6.1 for desire and do a folder diff to see how to adapt a desire ROM for the HD2
Basically what i used since 03. Oct for testing Magldr, continuously updated when a new CM release is out
Readme:
Code:
Rajko's CM 6.1 NAND ROM for HTC HD2
===========================
Based on CM 6.1 official stable for the HTC Desire.
This is a continuation of the NAND ROM i was making for earlier MAGLDR builds.
Very close to CM 6.1 stock, but added additional applications for convenience, these are:
- Wifi Manager
- Quadrant Benchmark Advanced
- TasKiller
- Network Speed
- Current Widget
- Market Enabler
All applications should be up to date as of 03.01.2010.
1. Installation
===============
MAGLDR 1.10 or newer is required on the device.
Before starting the installation process, enter "USB Flasher" mode on the device
by using the Volume rocker switch to select items and the green "Call" button as the Enter key.
2. Known issues
==============
Magnetometer left/right doesn't seem to be working. Don't know what broke this. Investigating.
Due to old QDSP, camera is still the stock 800x480 of HD2.
3. Post installation notes
==============
You can change the kernel to a newer/custom version by doing the following:
Connect via USB to your HD2 while Android is running.
Spawn an ADB shell
Do the following commands as superuser:
mkdir /tmp/boot
mount -t yaffs2 /dev/block/mtdblock0 /tmp/boot
After that, you can replace the zImage that's located in /tmp/boot
When you're done, you have to unmount the boot partition, like so:
umount /tmp/boot
Restart your device to use the new kernel.
Click to expand...
Click to collapse
is step 3 necessary...wat does step 3 do??? and how do u perform step 3...i don't know "spawn an adb shell" means...and replace zimage in /tmp/boot with what???

Please can someone upload the CyanogenMod Wallpaper images of this Version ?
Or where I can find it with root explorer ?? Thanks

step3 is if you dont like my kernel, as it says in the readme.

is t-mobile US mms working?

rajkosto said:
step3 is if you dont like my kernel, as it says in the readme.
Click to expand...
Click to collapse
hahaha...i skipped that line...my bad...

is t-mobile US mms working?
Click to expand...
Click to collapse
does it work on cm6.1 on the bravo ? if so then it works here.

Yellowbrother said:
is step 3 necessary...wat does step 3 do??? and how do u perform step 3...i don't know "spawn an adb shell" means...and replace zimage in /tmp/boot with what???
Click to expand...
Click to collapse
Step 3 is for changing the kernel. This step is not required unless you are swapping kernels.

Upload is awfully slow compared to other nand build....I was getting avg of 1.5mbps.....with this build I get 400kbps...

cezzarmicu said:
anyone else having random force closes when running camcorder? camera itself runs ok when taking pictures though...
aside from above issue, the nand/build is running great
Also,
i seem to have forgotten how to enable volume control (when playing music) even when the screen is locked/turned off? I can't find it under cyanogenmod settings
thanks
Click to expand...
Click to collapse
Camera and camcorder ok....

Frequently Asked Question - SFE devices

Hi guys,
i've started a general Q&A thread for n4 and others. Everything related to sailfish and of course n4 can be posted here.
1. Which HW components are working?
A: take a look at the spreadsheet libhybris: https://wiki.merproject.org/wiki/Adaptations/libhybris
2. Can I run my android apps?
A: atm = no. due to licensing issues the dalvik runtime is not included in android ports. Join community efforts in this XDA thread. The jolla phone run android apps.
3. What about playing videos and music
A: new ports with gstreamer1.0 (Nexus 5) play MP3, MP4, H264 out-of-the-box.
Install gstreamer1.0-libav for more codecs.
For old gst0.10 ports:
MP3: install gst-fluendo-mp3-0.10.23-1.armv7hl.rpm via rpm -i fluendo
Video: Install gst streamer plugins and ultimate codec support. detailed instructions: http://forum.xda-developers.com/showpost.php?p=53552092&postcount=424
4. I'm able to install apps?
A: On Nexus 4 and Nexus 5 yes, soon on other devices too, always use Jolla Store for tested quality apps! Not there might still be scalability/stability issues on ported = non-official Sailfish OS devices.
As alternative and if you want to try many but NOT QUALITY-TESTED/POTENTIALLY DANGEROUS apps you can try Warehouse (openrepos.net):
* Navigate via your phone's browser to https://openrepos.net/content/basil/warehouse-sailfishos
* Download latest RPM
* In Terminal type `devel-su zypper in Downloads/harbour-warehouse*.rpm` and install
If you have Jolla Store also working on your ported device, you can install that app via UI instead of terminal:
* Ensure you have download at least one app from Jolla Store beforehand (which triggers `pkcon refresh`)
* Ensure Settings->System->Untrusted software is allowed
* Go to Settings->System->Transfers, click on downloaded file, and it will be installed
5. whatsapp?
A: Beware of WhatsApp temporary banning 3rd party app users. You can try WhatsUp: http://forum.xda-developers.com/showpost.php?p=60264278&postcount=137
Next Mitäkuuluu version is rumoured to be unbannable, lets all wayt
6. How to access the device?
A: Via ssh or sftp. Take a look on @Daycrawler thread: http://forum.xda-developers.com/jolla-sailfish/general/sailfish-android-devices-release-t2696409. He released the ea mail where everything is described.
7. How to install sailfish on my Android device ?
A: You will be able to install when an image is available. Check "Downloadable Image" column in https://wiki.merproject.org/wiki/Adaptations/libhybris .
Porting Sailfish OS by yourself is possible via following the HADK: https://sailfishos.org/hadk
For Nokia N9: http://wiki.maemo.org/Sailfish#Sailfish_Images
9. What about multirom?
A: MultiROM is supported on Nexus 4, Nexus 5, and OnePlus One (possibly Nexus 7 too)
10. Why I have to flash so much to get sailfish on my device?
mmmmmhhhh. Answer question by yourself and try
E.g. for Nexus 4 please do all steps you'll find in: http://forum.xda-developers.com/nexus-4/development/rom-sailfish-os-community-port-t2969823 . It's necessary to have the right baseband / modem firmware. Maybe wifi won't work if you haven't.
11. How to take a screenshot?
A1: Install screenshot app by lbt, from Jolla Store.
A2: do `zypper in lipstick-qt5-tools lipstick-qt5-tools-ui` - iconless Screenshot app will be among the App Grid
A3: This can be done on the phone via terminal and also on a remote SSH PC client.
grabscreen /home/nemo/Pictures/Test.png
If you need a times then use the 'sleep' command. e.g. below is a timer for 5 seconds.
sleep 5 && grabscreen /home/nemo/Pictures/Test.png
The picture can be accessed in the Gallery or via a file manager (question #17 below).
12. How to get files from/to device, if USB Mass Storage mode or SD card are not available ?
A1: ssh + scp combo (windows[putty] & linux)
This combo is a set of linux standard tools. You can connect to the phone via secure socket shell from your pc and transfer files to your phone and vice versa.
A2: sftp + filezilla (windows & linux)
You can access the files via filezilla. You can transfer files like you're doing with an ftp server.
A3: Gnome Desktop Environment
The gnome filemanager nautilus has an build in option for accessing sftp / ssh servers or devices easily.
A4: WinSCP (windows)
To connect via these methods, enable developer mode, set a new password and take a look what ip you've get. Behind the wlan symbol. Then choose one of the above methods:
username = nemo
password = the one you entered in developer mode section
[ssh]= ssh [email protected]_ip
[filezilla] = sftp://device_ip
[nautilus] = select: Connect to server (on the left side) and enter: ssh://device_ip
13. How can I use the Backup app when there's no (working) SD Card?
A: Launch Settings->System->Backup to save all the settings you want to preserve
Perform
Code:
tar cf $HOME/backup.tar -C $HOME .vault
scp backup.tar onto your PC (other ways of how pull files, see FAQ #12 above)
Install new Sailfish OS.zip, put the tarball back onto device (say at $HOME), then perform:
HTML:
cd $HOME && tar xpf backup.tar
Go to Settings->System->Backup and restore your content from a chosen backup
14. How can I provide another radio.img only for Sailfish OS?
Put radio.img onto Sailfish OS rootfs somewhere safe.
Edit /lib/systemd/system/firmware.mount and replace "What=/dev/mmcblk0p1" with "What=/path/to/firmware.img"
Be careful with that and always do backup (i.e. comment the first What out )
15. How can I skip tutorial?
On first screen, tap on corners in sequence: top-left, top-right, bottom-right, bottom-left
16. How can I mount android's virtual sdcard partition (Nexus4,5) with all my goodies?
Try:
Code:
devel-su
mkdir /android
mount /dev/mmcblk0p28 /android
# virtual sdcard content is then available in /android/media/0/
# enable nemo user to read/write the contents (use file manager for those):
usermod -aG media_rw nemo
# And for media to be tracked:
ln -s /android/media/0/DCIM /home/nemo/Pictures/Android
ln -s /android/media/0/Music /home/nemo/Music/Android
ln -s /android/media/0/Movies /home/nemo/Videos/Android
# To make this permanent, update your /etc/fstab file by adding the following line at the end:
/dev/mmcblk0p28 /android ext4 rw,relatime,data 0 0
17. Filemanager?
Install File Browser by Kari from Jolla Store.
For root access add on https://openrepos.net/content/schturman/startasroot-file-browser (See question #4 on how to access openrepos via Warehouse app)
18. OTA?
Over-the-air updates are not straightforwardly supported (it's possible to hack around via ssu release 1.x.y.z and version --dup commands but not been tested and breakages might happen).
Just do backup and restore via a backed up file (question #13), and reflash new .zip (which will overwrite the whole Sailfish OS partition), then restore backup
--
This thread should be a collection for sailfish on devices and I will update frequently if news or tipps & tricks are available.

Reserved

Sorry if I'm asking in a wrong thread.but this information was missing from QA.
Are there any information about android apps running in ART instead of Dalvik on Nexus4, or even on Jolla?

Morderen said:
Sorry if I'm asking in a wrong thread.but this information was missing from QA.
Are there any information about android apps running in ART instead of Dalvik on Nexus4, or even on Jolla?
Click to expand...
Click to collapse
on jolla art isn't available or usable. Almost every app is running under art.Titanium Backup, Whatsapp and a hand full of other was critical. But they updatet theire apps and everything is working fine.

carepack said:
Hi guys,
No. Please do all steps you'll find in the ea mail. It's necessary to have the right baseband / modem firmware. Maybe wifi won't work if you haven't. You will get this by flashing the google factory image:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
After this you have to flash a clean base. That's why you have to flash cm_10.1.3: http://get.cm/get/aWH
Now you've done the preperations and can flash sailfish.
Click to expand...
Click to collapse
Its not important to flash the factory image for the Nexus 4. All you need to do is flash the Radio from the 4.2.2. which can be available as a flashable zip for TWRP Recovery. The radio is called 0.48 availabe in one of the xda threads.
Thats what I did flashed this zip after I flashed CM 10.1.3 and EA2 worked as a charm. For reference my Nexus 4 was already on 4.4.3

DeepPurple15X said:
Its not important to flash the factory image for the Nexus 4. All you need to do is flash the Radio from the 4.2.2. which can be available as a flashable zip for TWRP Recovery. The radio is called 0.48 availabe in one of the xda threads.
Thats what I did flashed this zip after I flashed CM 10.1.3 and EA2 worked as a charm. For reference my Nexus 4 was already on 4.4.3
Click to expand...
Click to collapse
you're right. You have the choice. The important part is the right baseband / radio. But to keep it user friendly reading and simple I only described this way.

Looks like the next update is early june.
https://together.jolla.com/question/43464/next-os-update-in-early-june/
from
http://forum.xda-developers.com/nexus-4/general/sailfish-os-progress-nexus-4-t2667622/page36

i am not sure how to install warehouse.. can anyone help me please??i downloaded the harbour-warehouse-0.2-13.armv7hl.rpm what excatly do i have to type to make it work?

misal6666 said:
i am not sure how to install warehouse.. can anyone help me please??i downloaded the harbour-warehouse-0.2-13.armv7hl.rpm what excatly do i have to type to make it work?
Click to expand...
Click to collapse
If you have a file manger, like cargo dock, look for your file in download folder, simply click on it and you're done.
First be sure to have enabled, in settings,->system->untrusted software, otherwise you won't be able to install.
Inviato dal mio iPad utilizzando Tapatalk

misal6666 said:
i am not sure how to install warehouse.. can anyone help me please??i downloaded the harbour-warehouse-0.2-13.armv7hl.rpm what excatly do i have to type to make it work?
Click to expand...
Click to collapse
quote from first post. hope it helps
a.) Download warehouse from opnrepos.net: https://openrepos.net/content/basil/...use-sailfishos
transfer it to you're device and install it via: rpm -i package
After that you'll be able to install apps from openrepo
Click to expand...
Click to collapse

hello.
usually i dont use camera,gps and Bluetooth in my daily life, so can i say that every thing else in nexus 4 is working

Sobaro said:
hello.
usually i dont use camera,gps and Bluetooth in my daily life, so can i say that every thing else in nexus 4 is working
Click to expand...
Click to collapse
How is the call quality? I thought the volume was still rather low.

Darakian said:
How is the call quality? I thought the volume was still rather low.
Click to expand...
Click to collapse
Yes, it is very in version 5, let's hopes we will good in version 7..
Sent from my Nexus 4 using XDA Premium 4 mobile app

Would it work on Optimus G?

Darakian said:
How is the call quality? I thought the volume was still rather low.
Click to expand...
Click to collapse
mailyaseen said:
Yes, it is very in version 5, let's hopes we will good in version 7..
Click to expand...
Click to collapse
I messaged Stskeeps on #SailfishOS IRC channel, this is what he said.
wait for next update; it fixes all that and more.
we had a bug in float vs integer valeus
Click to expand...
Click to collapse
Here are the logs for that day.

DeepPurple15X said:
I messaged Stskeeps on #SailfishOS IRC channel, this is what he said.
Here are the logs for that day.
Click to expand...
Click to collapse
I don't see that particular message in the logs, but it's good to hear none the less

I found this thought it would be useful to share and maybe add to the list
How to take a Screenshot on the Nexus?
Code:
su-devel
grabscreen /home/nemo/Pictures/Test.png
This can be done on the phone via terminal and also on a remote SSH PC client.
If you need a times then use the 'sleep' command. e.g. below is a timer for 5 seconds.
The picture can be accessed in the Gallery or via Filetug.
Code:
sleep 5 && grabscreen /home/nemo/Pictures/Test.png

DeepPurple15X said:
I found this thought it would be useful to share and maybe add to the list
How to take a Screenshot on the Nexus?
Code:
su-devel
grabscreen /home/nemo/Pictures/Test.png
This can be done on the phone via terminal and also on a remote SSH PC client.
If you need a times then use the 'sleep' command. e.g. below is a timer for 5 seconds.
The picture can be accessed in the Gallery or via Filetug.
Code:
sleep 5 && grabscreen /home/nemo/Pictures/Test.png
Click to expand...
Click to collapse
added to list! thx

updated the thread with new hints. ea3 is coming soon! The version is more fluidly on mako devices. The resulotion fits better the screen. Had problems with mitäkuuluu because can't open chats. Working codec support is now easier to activate. Have fun guys!

carepack said:
updated the thread with new hints. ea3 is coming soon! The version is more fluidly on mako devices. The resulotion fits better the screen. Had problems with mitäkuuluu because can't open chats. Working codec support is now easier to activate. Have fun guys!
Click to expand...
Click to collapse
For mitakuuluu u need to install location and positioning packages..
Install pkcon qt5-qtdeclarative-import-location
Install pkcon qt5-qtdeclarative-import-postioning
Sent from my Nexus 4 using XDA Premium 4 mobile app

[unofficial][linux3.4][native][tarchive][multirom]ArchLinuxARM release for N7 2013

This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the flo (2013 Nexus 7) - Native Boot with MultiROM
This is only tested on the Wi-Fi version. With a kernel swap, it should work on the deb (LTE) tablet, though mobile data is highly unlikely to work.
Big thanks to crondog at github for the initial porting work. https://github.com/crondog/arch-flo
Working:
3D Acceleration (OpenGL ES 3.0, Mesa) - can be unstable, however.
Wi-Fi (with NetworkManager)
Bluetooth
Audio
Installation
MultiROM must already be installed, and you must already have a hardboot-capable kernel installed as well.
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_flo_20141210_multirom.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/file/d/0B4WUjKii92l2X1F1LVhsaG5DbUE/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_flo
Also available for:
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483

looks interesting will give it a crack and see how it goes

thanks for the work. it boots impressingly fast.
castrwilliam said:
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Click to expand...
Click to collapse
if I activate the onboard keyboard ist shows at the bottom of the login screen. login works without password. when beeing logged in the keyboard is gone. I can see the keyboard symbol on the left besinde the speaker symbol but tapping on it doesn't trigger anything. also changing any options in the control center -> onboard settings have no effects. logging in without keyboard activated and then control center -> onboard settings has no effects either.
I cannot "adb shell" due to lack of permissions
Code:
# adb devices
List of devices attached
???????????? no permissions
and I'm not owning a bluetooth keyboard. so right now I can only play minesweeper - oh wait, it's not installed...

is there any way to rotate the screen as its really annoying having it in portrait all the time

Toby0897 said:
is there any way to rotate the screen as its really annoying having it in portrait all the time
Click to expand...
Click to collapse
Yeah it is in the monitor options but it's worthless since Xorg crashes when changing the rotation

Great stuff!
I would remove the KDE plasma etc packages as that desktop seemed to unusable. (Due to broken hw acceleration?).
what's next?

Hi, I'm having a big trouble...
While I'm trying to do the installation (by adb shell or terminal emulator, both of them) and I enter the command posted in the OP it says:
127|[email protected]:/ # tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
tmp-mksh: tar: not found
What can I do to resolve this error? I really would like to install it on my Nexus 7
Thanks in advance!

hugomc92 said:
Hi, I'm having a big trouble...
While I'm trying to do the installation (by adb shell or terminal emulator, both of them) and I enter the command posted in the OP it says:
127|[email protected]:/ # tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
tmp-mksh: tar: not found
What can I do to resolve this error? I really would like to install it on my Nexus 7
Thanks in advance!
Click to expand...
Click to collapse
You will need to install busybox for tar to work

daringblaze said:
You will need to install busybox for tar to work
Click to expand...
Click to collapse
Thank you very much!! That make tar to work!!
Gonna try archLinux ASAP!!
Thanks!

updates
Hi, great stuff!
After installing it, I tried to update arch (
Code:
sudo pacman -Syu
) but this resulted in a blank screen upon boot. I assume that this is due to updated packages overwriting parts of the OS that were installed manually, but I don't know what or where. Would you have any ideas of what packages would be responsible for this, so that I know not to upgrade them?
Thanks!

computer-whisperer said:
this resulted in a blank screen upon boot. I assume that this is due to updated packages overwriting parts of the OS that were installed manually, but I don't know what or where. Would you have any ideas of what packages would be responsible for this, so that I know not to upgrade them?
Thanks!
Click to expand...
Click to collapse
Make sure you ignore xorg and mesa stuff. Add
Code:
IgnorePkg = glu mesa mesa-dri mesa-libgl xorg-server-common xorg-server-devel xorg-fonts-misc xproto libdrm
IgnoreGroup = xorg
to /etc/pacman.conf.
The list probably contains some extra entries, but works for me

It took xda 2 years, but they finally did it.
In all seriousness, props to you. I've been waiting for this for along time.

castrwilliam said:
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/......
Click to expand...
Click to collapse
Hi castrwilliam, would you mind sharing what step you went through to create arch_flo_20141210_multirom.tar.gz ?

Great work guys! I was looking for this for a really long time and i am writing this on my n7 with linux but i have a few questions:
1. is it possible to overclock(and how) because my n7 runs on 1.89ghz and 477mhz gpu in android with elementalx kernel and it would be nice to have some more power
2. can the screen be rotated so the hardware buttons are on top (i saw a post saying it chrashes but i cant even find the setting xD) because it would be alot easier to use the OTG cable
And thank you guys for making this happen, i love linux on the note 10.1 and im so glad to have this run it too(would be maaad if it can be overclocked )

Thank you for this wonderful package!
I recently updated all packages ) and iam trying to fix the issue without reinstall (challenge accepted)
It seems that the xorg-server 1.17 is the problem. I compiled. Freedreno and the freedreno mesa 10.3 and libdrn packages without success. The xserver is segfaulting when it loads libexa.so.
Now i try to downgrade to 1.16 . ive read that the xf86-video-freedreno-git package is not working with flo. Is that correct? Did youbuild this packages with modificationa?
I believe this is why i love arch. Its like lego for nerds or something

castrwilliam said:
This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the flo (2013 Nexus 7) - Native Boot with MultiROM
This is only tested on the Wi-Fi version. With a kernel swap, it should work on the deb (LTE) tablet, though mobile data is highly unlikely to work.
Big thanks to crondog at github for the initial porting work. https://github.com/crondog/arch-flo
Working:
3D Acceleration (OpenGL ES 3.0, Mesa) - can be unstable, however.
Wi-Fi (with NetworkManager)
Bluetooth
Audio
Installation
MultiROM must already be installed, and you must already have a hardboot-capable kernel installed as well.
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_flo_20141210_multirom.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/file/d/0B4WUjKii92l2X1F1LVhsaG5DbUE/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_flo
Also available for:
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483
Click to expand...
Click to collapse
What's NOT working

Hello, is there some instruction howto run (native) arch on nexus 4? I see only for n7, n10...

castrwilliam said:
This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the flo (2013 Nexus 7) - Native Boot with MultiROM
This is only tested on the Wi-Fi version. With a kernel swap, it should work on the deb (LTE) tablet, though mobile data is highly unlikely to work.
Big thanks to crondog at github for the initial porting work. https://github.com/crondog/arch-flo
Working:
3D Acceleration (OpenGL ES 3.0, Mesa) - can be unstable, however.
Wi-Fi (with NetworkManager)
Bluetooth
Audio
Installation
MultiROM must already be installed, and you must already have a hardboot-capable kernel installed as well.
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_flo_20141210_multirom.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/file/d/0B4WUjKii92l2X1F1LVhsaG5DbUE/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_flo
Also available for:
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483
Click to expand...
Click to collapse
Having my favourite distro on my pocket is very exciting so thank you very much...
I have to carry only a development lamp server so using a pacman tip I revert to a base, base-devel system removing everything about xorg and DE.
Now I connect using ssh but I've noticed that the tablet screen is simply blank: no tty, no text console.
There is a way to have a text only console at boot to make a login (may be using an usb keyboard) when device is not connected?

Hello, I have some trouble when I boot.
config: rastapop 5.1.1 (AOSP based) + last multirom v32A + Kernel w/ kexec-hardboot patch (Stock 5.1.1)
Installing archlinux correctly from the terminal emulator. Load it --> black screen (about 6seconds) --> Google Logo forever
Someone know what I can do for make it work ?

Cool I will give it a try.

A Noobs Guide to Verizon Galaxy Note 4 Hardware Repair,Root,Bootloader,Twrp,ROM's

A Noobs guide to Galaxy Note 4 Verizon Motherboard Hardware repair and replacement
and Other Samsung Galaxy Note 4 repair ( Att, Tmobile etc ) starting in thread 2 ( user input welcome ) ​
My Overheat Heat and flash problem issues leading to
OEM Motherboard replacement and acquiring ROOT again​
OP Note : read the whole guide or for that matter any OP​
Thanks to many XDA-Developers forums, if you are not quoted or mentioned here I will add you !!
Device : Samsung Galaxy Note 4 Verizon SM-910V this OP ONLY !!!
Code:
[COLOR=Red][B]Your warranty is now void.[/B][/COLOR]
*most likely you don't have a warranty because you broke it, ROM'd it, its old and past warranty anyway !**
So, There is no warranty anyway, not even if you did anything in this thread to it
We are not responsible for bricked devices, dead SD cards,
thermonuclear war, or your getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this guide
before flashing it! (thanks @hsbadr)
YOU are choosing to make these modifications, and if
you point the finger at anyone for messing up your device, we will laugh at you
Symptoms : ROMs not flashing/installing , crashing, High heat, low battery life on new battery hardware note working specifically fingerprint.
Problems : digging through many forums 2 years later to root and unlock the bootloader, it took DAYS
Solution: keep track of my progress and make a useful step by step NOOB guide for Everything !
Section 1: Repairs
Then the rest of the sections are for Rooting, Installing TWRP custom recovery, fixing bootloader , and installing ROMS
Section 2: Flashing via ODIN and the correct rootable OEM rom 5.1.1 on a windows PC
section 2a: Flashing via Heimdall on a Linux device --need comments
Section 3: Achieve temporary root to install bootloader fix
Section 4: Use of ADB to (windows and linux ) to copy over bootloader fix
Section 5: install TWRP custom recovery and your first rom
Section 1: Repairs
If you have to replace the motherboard, and you have any other futzy component, might as well order it at this point, your going through pretty much the same process. I am only doing the motherboard, but the cameras and USB board are right there as well on this repair
I have been running a rooted Verizon Galaxy note 4 since Cynogenmod crashed and switched to Lineageos 14 and then 15.
Here is the forum
https://forum.xda-developers.com/no...eo-8-1-0-unofficial-lineage-15-1-rom-t3760969​
After several suggestions and searches, many users hinted I may be getting a Bad internal memory,
which refuses to write anymore.
So I had to go to Walmart and buy a LG Straight talk phone to use as my daily driver,
Then I ordered a new motherboard from China, 29.00 on Aliexpress.
See OP thread #2 below!! It was not fun searching for it, but I saved $20 to $40 from buying on ebay
What I bought may not be available from this seller, but here is the link. Use a desktop browser, it will show "suggested" other devices...
Code:
[URL]https://www.aliexpress.com/item/with-Android-System-Original-unlocked-for-Samsung-Galaxy-Note-4-N910V-Motherboard-Good-Working-Free-Shipping/32802513232.html?spm=a2g0s.9042311.0.0.66e04c4dpohrQm[/URL]
When I received it , it was time to look for a repair procedure on YouTube.
Hardware needed: thin shim and 00 size phillips, AND a blank cheap SD card you don't mind losing. It may be unusable after we are done
Cell Phone repair tool kit really helps save your fingernails !
Complete note 4 teardown video:
Code:
[media=youtube]ZND9Q73wjr8[/media]
Just the Motherboard video
Code:
[media=youtube]5KpT755hNpM[/media]
In the second video, you can see the phone booting up as a test to see if you have all the connections correct.
Because it came from china, its a good idea to setup your user and
download the app CPUz before you put all the screws back in,
and check to see if you have a real or fake chipset.
Yaayyyy mine was real . Thanks Aliexpress.
Button it up and do a factory reset (it booted up set up as a no user) so I wanted a fresh install oem with my user.
Section 2: Installing the Correct rootable OEM rom so we can install Anything else.
FIRST check to see if you have the emmc brickbug or you will BRICK it !!
1. Google play store install eMMC Brickbug
If your long number starts with 15xxxxxxxxxxxxxxxxx, YOU are Golden ! if not STOP, get another board ! or you are going to waste time , and get another board !
The Galaxy Note 4 Verizon had a special custom locked bootloader installed after the 4.4.4 release to 5.0.1 and made it very difficult to get
root access to your device.
I saw the notice
DON'T UPDATE YOUR BOOTLOADER TO ANYTHING AFTER THE LATEST BUILD AS OF 4/19/16
warning about a week to late. So I finished out my 2 year contract and watched the forums.
Seriously noobs, don't update your new motherboard ...
The rom pre-installed on my replacement motherboard was already setup booted to a running 5.0.1 oem rom, I could not root it.. with any method I remember downgrading my 6.x.x to 5.1.1 in one of the many forums listed here at XDA
This one was the one I used back then, and It turned out that is where I started..
Only a Verizon Samsung Galaxy note 4 Developer Edition has the ability to install custom roms, and most likely the motherboard you bought or have is NOT a developer edition
IF you have a eMMC that starts with 15 we can reprogram it a developer edition
Thanks to @hsbadr
Here are most of the downloads we need:
Code:
[URL]https://forum.xda-developers.com/devdb/project/?id=15720#downloads[/URL]
2. Download Odin, Download TWRP, and Samsung_unlock_n4-fix
3. On your windows PC, create a folder c:/Odin and extract the Odin zip file there, and copy the TWRP image there
4. Download the following OEM root able ROM to your c:/Odin folder
Code:
[URL]https://forum.xda-developers.com/devdb/project/dl/?id=18880[/URL]
5. Plug your phone into a USB port on your Windows PC
6. Install the necessary drivers if they don't automatically install from Samsung
Code:
[URL]https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows[/URL]
7. Set up your phone for flashing ROM and communicating
Settings - Security - Unknown sources- : check allow
settings - system -about phone - build number : click several times until you activate developer options
settings - system -about phone - developer options : Android Debugging : enable android debug bridge
settings - security - reactivation lock : Turn OFF or you will brick your device ( may vary where this is at . Important to turn off )
Power Off phone
Enter Download Mode - press and hold in this order <down arrow> <home> <power> until screen comes on. release buttons.
press up arrow to enter download mode
8. Open windows explorer and go to your c:/Odin folder. You should have an odin exe file, and the twrp file, and the large rom file.
a. right click odin exe and open as administrator
b. check to see if your connected to your phone. you should see a blue box in upper left with a com under it.
If you unplug your phone, you should hear the disconnect notice and the com and blue bar will go off, and when you connect, the com and blue bar and reconnect noise should appear.
9. click the AP button box, select the ROM file that you downloaded above.
NOTE : this ROM will disable WIFI so you wont be able to use the play store unless you have cellular connection.
you will have to transfer other files via usb cable !
Click start, do not unplug! until it stops.
10. Device will reboot. Remove cable, and battery before boot completes
11. Enter recovery mode . Press in order ,<volume up><home><power>
wait for the little android dude to do his thing, then there will be a menu. select factory reset, and reset and let it reboot
Set up minimal user or as a new phone with no user and check the settings in step 7
Set up your phone for flashing roms and communicating
Settings - Security - Unknown sources- : check allow
settings - system -about phone - build number : click several times until you activate developer options
settings - system -about phone - developer options : Android Debugging : enable android debug bridge
settings - security - reactivation lock : Turn OFF or you will brick your device ( may vary where this is at . Important to turn off )
Yayy, you now have a rootable device
Section 3 Achieve temporary root to install bootloader fix
In my try to obtain temporary root, I tried every method in all the forums ( go ahead and look and try )
The only 2 programs that reported to work is Kingroot, and Kingoroot. These are APK's that are NOT in the play store
you will have to download them and install them as unknown sources. I was only able to install kingroot . Kingoroot apk would not install
in both my 5.0.1 original on my motherboard, as well as what we just installed 5.1.1 I was unsucessful at obtaining root with these programs
Then I remembered Kingoroot has a windows version that installs on the PC <dangerous dont install yet>
On your PC you will need AVG antivirus to catch the malware ( other antivirus may work but this is what I had ) my PC is windows 7 ultimate
Advanced Users only :Recommend running a virtual machine with windows so as to keep your PC completely malware free. just delete the VM after this process !
This section you will need on your Note 4 from the Play Store : root checker
You will need a throw away SD card
You will need read through section 4 and 5 and get all files and programs there ready to install use and or transfer
0.5 update your AVG
1. With AVG installed on my PC, and my phone connected as a mtp with usb I downloaded and installed Kingoroot for windows.
https://www.kingoapp.com/
NOTE after not being able to install forum recommended kingoroot apk's i dint want wast time install the newest kingoroot apk from the website. Maybe it will work for you. If you do get kingoroot apk to work on your Note 4 let me know.
2. In the install process for kingoroot windows version AVG will quarantine a file.
there will be a couple popups .. close them
when its installed it will open and start talking to your phone.
3. press the root button.
It will take 30 sec to a minute to install some files on your phone and achieve root, there will be a new floating toolbar on the phone. root will disappear after a reboot, but not the resident programs this root is pretty stable, but i was not able to install SuperSUME (paid version ) as recommended in a XDA guide to obtain permanent root for this 5.1.1 rom. If your successful with super SUme with this let me know.
4. Open root checker to verify ! yayy.
5. Cleanup instructions when finished with this guide below
Section 4: Use of ADB to (windows and Linux ) to copy over bootloader fix
1. Your Note4 phone should be running with root, make sure phone is connected
Explanation : ADB is a Google provided tool for the android platform. It communicates with your phones operating system , transfers files , and actuates programs remotely in the background. totally necessary for development of ROM's, TWRP, and programs for every android device
You may or may not know that your android device is running a Linux kernel, with some Linux programs, with custom folders and custom files and settings, and the touch screen is the GUI graphical user interface touch input.
ADB is a command line user interface, when you turned this on in Developer settings, the kernel is listening constantly on the USB com port and some times on the WiFi com port for commands. if you don't need it turn it off, it could be a security hole, but we need it on.
It works great on windows, mac, or Linux varieties
2. Install on your computer
Code:
[URL]https://developer.android.com/studio/releases/platform-tools[/URL]
If you have linux, your distribution may have a package you can install from your distribution. Then it will be in your path as a command
3. Windows users , extract or install into c:/ADB and add that to your PATH variable if you want to use it all the time as a command
4. Open a command prompt window (search command or cmd , right click open as administrator)
5. If you have ADB folder in your path or are running Linux change directories to the folder where you downloaded the Samsung n4 fix file
6. You should still have root
type
Code:
adb devices
The ADB daemon ( little server program ) will start and return some information.
your phone will have a popup screen and should ask for permission, click allow
again type
Code:
adb devices
7. You should see something like this
Code:
List of devices attached
123a12ab device
The 123a12ab is made up. Yours will be specific to your device.
If you see something listed like the above adb is working. Now on to the next command to move the Samsung_unlock_n4-fix to the phone.
type dir ( or ls -al for Linux users ) to verify Samsung_unlock_n4-fix is in your directory
8. Send Unlocker to Phone with adb
Type or copy and paste the following command:
Code:
adb push samsung_unlock_n4-fix /data/local/tmp/
You should see successful output .
If you don't, check your PATH, check if your in the right folder, or make sure samsung_unlock_n4-fix is in your adb folder
9. Activate the unlocker. This requires root and a reboot. After the reboot you have to go and reactivate root in Section 3.3 above
type the following
Code:
adb shell
Congratulations you are now looking at the linux command line interface on your phone . the $ prompt means you are in the shell
10. activate superuser mode ( kind of like administrator in windows but more powerful )
type
Code:
su
then press enter key
YOU SHOUD NOW SEE a # prompt
This means you succeed in root. If you dont see a # you missed a step above somewhere , or your root was unstable and took too long to get to this point,that is why I said read thru this section and get ready..
Ok at this point we have the file we needed transfered, we have root, now we need to upgrade the permissions on the file so #root level of the operating system can use it !
The next command does all that then executes the command to upgrade your phone to developer edition !
Copy and paste the following command series and press enter.the && joins each command
Code:
cd /data/local/tmp/ && chmod 777 samsung_unlock_n4-fix && chown root.root samsung_unlock_n4-fix && ./samsung_unlock_n4-fix
The device will reboot and flash the developer code.
You should see some sort of progress in the window.
When done ,unplug the cable and pull the battery to shut down phone.
11. Make sure you have a cheap throwaway SD card installed !
One More Time to unlock the boot loader !! section 3 and 4 short version
Put the battery and cable back in and turn the phone back on and make sure its plugged in your PC.
Now repeat the kingoroot PC to gain temp root
open a command prompt or shell
type or copy paste the following to verify its connected
Code:
adb devices
transfer the fix
Code:
adb push samsung_unlock_n4-fix /data/local/tmp/ && a
open the shell on your phone
Code:
adb shell
gain super user rights
Code:
su
unlock the boot loader
same command series
Code:
cd /data/local/tmp/ && chmod 777 samsung_unlock_n4-fix && chown root.root samsung_unlock_n4-fix && ./samsung_unlock_n4-fix
You will see your phone do a series of outputs then reboot. when it reboots, disconnect the cable.
If this step is sucessful your phone will keep rebooting. This is NORMAL . after the first or second reboot, pull the battery and pull the sd card, and set the sdcard aside. It will need to be thrown out or repartititioned to be usable. or you can keep it as a memento on your charm bracelet.
Your bootloader is NOW UNLOCKED . keep phone off until you read the next section
Section 5a: install TWRP custom recovery
Currently right now you have 5.1.1 installed with some Chinese malware on your phone and PC,
A custom developer edition and an unlocked boot loader. Lets fix them all.
Turn on phone download mode . <down volume><home><power> then volume up to enter download mode
Open Odin again ( see above )
Connect phone ( look for com and blue bar )
Select AP button, and browse to TWRP file
Press start. when finished phone will restart.
Don't let it boot all the way back up! , pull battery, and install good SD card, and if you read this section you downloaded what you needed for a new ROM onto your sdcard
Turn off the automatic rebooting in the custom tab, DO NOT select the PIT tab
Press start
Once it finishes it will say Success or FAILED
IF it says FAILED start the whole process over! you didn't unlock the bootloader !
If success, Power off the phone with the pull battery method and disconnect your cable
Press and hold these buttons immediately to enter TWRP ,
<volume up> <home> <power>.
Swipe to allow changes in TWRP.
Select backup , change to SD card, You can also plug in a memory device into the USB port. If it sees it you will be able to use that for backup space
BACKUP everything . You now have a custom recovery installed, a unlocked bootloader, and a rootable ROM Backed UP !
If you feel you want to do this all over again if you flash the OEM Samsung ROM via Odin by accident like I did, ha ha skip the next steps
Select the backup button, select all the partitions, select the source, where you want to store it.
Name the backup rooted-backup-everything-5.1.1
Select start and go make some coffee or a sandwich. its about 4 gigabytes compression, so it may take about 5 to 10 minutes
Clean up -
uninstall windows kingoroot PC and do a virus check
check for hidden folders and registry entries
Section 5b. Install your first ROM
Cleanup : After your backup WIPE your phone twice
THIS IS TO guarantee, no Kingoroot or kingroot stuff is in the phone !!!
WIPE IT TWICE !!!
Some guides (listed below ) say to adb sideload over a root file , then install an older rom. I haven tried this. Let me know if you did and are successful.
Whatever ROM you use, please post a success story in the reply's. I am interested in how you all do.
I have tried every note 4 ROM and this is the most succesful for me and most stable
I have been using this ROM for a while, and the lineageos 14 version too
Code:
[URL]https://forum.xda-developers.com/note-4/snapdragon-dev/oreo-8-1-0-unofficial-lineage-15-1-rom-t3760969[/URL]
In most all ROMS, you can update the bootloader (TWRP) by TWRP app if rooted
you can update the modem ( a partition that contains original Samsung code to run the cell and wireless ) via ODIN
Roms and patches and other goodies can be installed via TWRP by downloading to your device or transfering them to your sd card
Oem ROMS must be installed via ODIN, and will WIPE all you just accomplished. so unless your selling your device, or giving it to grandma DONT.
If you copied the rom ( usually a zip file ) and the necessary files, and have upgraded your bootloader and modem to the newest,
Now install your ROM, and after your initial setup, come back to TWRP and do a full backup !
every time you try a new rom, and get it set up, do a backup. that way you can switch and test to your hearts desire till you run out of SD memory.
The cool thing is you can backup to an external memory device ! more room !
Follow the directions in the OP of your ROM to install. Enjoy
All the above info was gleaned from the following pages
Thanks to @beaups for discovering exploit !!!
Thanks to @hsbadr [HOWTO] Bootloader Unlock and Upgrade to Marshmallow [N910VVRU2CQL1]
Code:
[URL]https://forum.xda-developers.com/note-4-verizon/development/howto-bootloader-unlock-upgrade-to-t3398144[/URL]
and his files
Code:
[URL]https://forum.xda-developers.com/devdb/project/?id=15720#downloads[/URL]
Thanks to @ryanbg [Official] Note 4 Verizon Bootloader Unlock
Code:
[URL]https://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913[/URL]
and @urgodfather
Code:
[URL]https://forum.xda-developers.com/showpost.php?p=66381707&postcount=342[/URL]
Thanks to @chriskader [HOWTO] Converting your Retail Note 4 to a Developer Edition Note 4
and @Mickey387 for discovering how to compile the note 4 32bit hardware drivers into Oreo !!
and @_mone @ripee
for maintaining and working hard on
[ROM][UNOFFICIAL][8.1.0] LineageOS 15.1 [trlte][trlteduos]
Code:
[URL]https://forum.xda-developers.com/note-4/snapdragon-dev/oreo-8-1-0-unofficial-lineage-15-1-rom-t3760969[/URL]
Information Sources: felixtaf, ryanbg, kingroot, twrp, emotion, ibowtoandroid, shimp208, & urgodfather
some of this was also posted on reddit. https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked

Update:
Looking for a motherboard for a 910 that's not a v?
Thanks to user @maralexbar I need to update some info
Method 1 use eBay. Find your correct motherboard easily.
Method 2. Save some money use Ali Express ( China )
If you use Ali, and don't find your motherboard on a direct search, keep digging.
I forgot to mention this.
Looking for my Verizon motherboard, I found lots of parts like the USB internal connector etc. But no mobo. I had to go thru the store listing of the seller of the USB connector to find a vendor that had a mobo. Then I tried comparing different vendors. So do some digging. There is a billion people on Ali express selling stuff. Don't give up.
Plus Ali wants happy international buyers. So if you get a bogus item, you get your money back.

reserved #2
reserved #2

reserved #3
Reserved #3

reserved #4
Reserved #4

Thank you very much for this!!! The phone is running beautifully, smooth and fast. I ended up installing this ROM:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-resurrection-remix-6-0-0-t3768963
BJ

b1ggjoe said:
Thank you very much for this!!! The phone is running beautifully, smooth and fast. I ended up installing this ROM:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-resurrection-remix-6-0-0-t3768963
BJ
Click to expand...
Click to collapse
Your more than welcome

Announcement:
Thanks to @ripee
The lineage-17.1 thread is up!
[ROM][UNOFFICIAL][10] LineageOS 17.1 [tblte][trlte][trlteduos]
If you don't mind not having a working fingerprint sensor, or audio through the headphone jack, then Q is stable enough for daily use. As always when coming from an older rom version, it is highly recommended not to waste your time dirty flashing and just clean flash.
Q is still a work in progress, so I will still be releasing Pie builds, though maybe not as often. As in years past, once the Q bugs have been fixed up to the current Pie level, I will post about when my last Pie build will be. I will upload it to the Downloads tab located at the top of each page of this thread, and link it in the OP.

[GUIDE] HavocOS 4.1 With GApps and Root (magisk)

I got bored so I made a HavocOS guide. Enjoy!
I am not responsible for any bad things happening to your device/angry parents because YOU messed your phone up. If it somehow broke after you did this, it's not my problem.
oh yea also I didnt make the OS. this is just a guide.
Downloads in video description.
I wanted to make this quick and simple so here's a video:
----------------------------------------------------------
Written guide:
-
Pt. 0: quick prerequisites that i forgor to write before
-
consider reading through the guide before you do it
make sure oem unlocking is enabled on your phone. if you dont know how to do that uhh here's how:
1. go to settings
2. scroll down to about
3. tap the build number until it asks for your screen lock
4. go to system
5. go to developer options
6. enable oem unlocking.
7. if its grayed out its because your phone is cringe, sorry.
-
Pt. 1: Downloads
-
Download all of these files
Google USB driver Extract with 7z or WinRar.
Platform Tools Click "Download for Windows" and extract with 7z or WinRar.
Stock Firmware Extract with 7z or WinRar.
TWRP/Kernel Don't extract this.
HavocOS Don't extract this.
-
Pt. 2: Drivers
-
How to install Android drivers:
1. Put your phone in fastboot mode (turn off your phone and turn it back on with power button and vol down.)
2. Open Device Manager on your PC.
3. Click on the dropdown for "Other Devices"
4. Find "Android"
5. Double click on "Android"
6. Click on "Update Driver"
7. Click on "Browse my computer for drivers"
8. Click on "Let me pick from a list of available drivers on my computer"
9. Double click on "Show all devices"
10. Click on "Have Disk"
11. Click on "Browse"
12. Find the usb_driver folder that you extracted earlier and in that folder, select android_winusb.inf and hit "Open"
13. Select "Android Bootloader Interface" and it "Next"
14. If there are any warnings, just press "Yes"
Drivers have been installed.
-
Pt. 3: Installing command line tools
-
How to install platform-tools systemwide.
1. Find your platform-tools folder and move it to somewhere where it can stay there forever, E.g. the root folder in your C drive (C:\). I don't recommend putting it on your desktop because that will add useless clutter.
2. Go to your start menu and look up "Environment Variables"
3. Click on "Environment Variables"
4. Scroll down on the bottom; "System Variables" section, find "Path", and double click on it
5. Click on "New"
6. Click on "Browse"
7. Navigate to your "platform-tools" folder
8. Click on platform-tools
9. Click "Ok."
10. Click "Ok."
11. Click "Ok."
12. Click "Ok."
(lol)
oh also i forgot to mention, unlock your bootloader now
steps to do that here:
1. open cmd
2. enter fastboot flashing unlock
3. hit yes on the prompt that appears on your phone
4. you might need to enter fastboot flashing unlock_critical (if cmd gives you an error saying it doesn't exist or something just kinda ignore it, i'm only putting it here just in case)
5. you should be good to continue
-
Pt. 4: The Installation.
-
Installing HavocOS
1. MAKE SURE THAT YOUR PHONE IS IN FASTBOOT MODE.
2. Open aura-p-release-3201
3. Run flash_all.bat (double click on it)
4. Wait until it finishes running.
5. As soon as it closes and your phone screen turns black, immediately hold the power and volume down buttons and enter fastboot mode.
6. Open Command Prompt (CMD)
7. Flash the Kernel by typing fastboot flash boot <boot.img> and replace <boot.img> with the file path to your boot.img file. (Tip: you can drag the file into CMD to put in the file path.)
8. Flash HavocOS by typing fastboot flash system <HavocOS PHH.img> and replace <HavocOS PHH.img> with the file path to the HavocOS PHH.img file. Ignore the errors.
9. Wait until everything finishes and unplug your phone (if you want to)
10. Use volume buttons to go down to "Recovery Mode"
11. Select "Recovery Mode" with your power button. (Tip: double tap the power button to get past the bootloader unlocked warning screen)
12. Swipe to allow modifications
13. Tap on wipe > format data > type "yes" > press "OK"
14. Press back until you get to the TWRP home screen
15. Tap "Reboot" > tap "Recovery" > then tap "Do not install"
16. Wait until it reboots back into recovery.
17. Follow steps 12-14, then hit "Reboot" > then hit "System"
If it doesn't boot into the setup screen, open fastboot mode and format the data once more, then reboot into system.
----------------------------------------------------------
and here are the easiest and also some of the dumbest GSI root instructions ever:
Download Magisk-v21.4.zip
1. Open TWRP and mount everything. (except for USB storage. micro sd card is optional.)
2. Put Magisk-v21.4.zip on your phone (in file explorer)
3. Open the TWRP file manager (advanced > file manager)
4. Navigate to /system/system/bin
5. Find resetprop and tap on it
6. Rename resetprop to phh-resetprop
7. tap on install
8. install Magisk-v21.4.zip
9. Boot up your phone, open magisk, and update everything.
10. Turn on MagiskHide in the settings of magisk manager.
11. Profit$ (lol)
SafetyNet should pass if you did it properly (I would find it kinda funny if you managed to mess up those easy instructions)
Alright guys, have a nice day!
p.s: I might begin work on a user-friendly auto-installer soon.

Thank you OP, finally got Android 11 fully working including SafetyNet, camera/flashlight, Bluetooth and SD card. The only tricky part was the Bluetooth - got help from this comment - needed to delete both APKs before first boot.

pigjr said:
Thank you OP, finally got Android 11 fully working including SafetyNet, camera/flashlight, Bluetooth and SD card. The only tricky part was the Bluetooth - got help from this comment - needed to delete both APKs before first boot.
Click to expand...
Click to collapse
yea i forgot to include that part. I thought you didn't need to do that before boot tho. I managed to get BT working by deleting BluetoothResCommon.apk and renaming RazerAuraBluetoothRes.apk to BluetoothResCommon.apk.

all the links for 4.1 are dead you got any bro?

Cylow333 said:
all the links for 4.1 are dead you got any bro?
Click to expand...
Click to collapse
There is a mirror in the description of the video.

Dude you are a different type of god thank you so much I can finally sleep now.

Quick question: is this version of Havoc have no issues with receiving SMS? Previous versions of it cause this annoying issue that after few minutes from restart SMS stop arriving to phone and the only fix at that time was just to restart it. Tried some patches from telegram but basically end up with no fix.

drumiec said:
Quick question: is this version of Havoc have no issues with receiving SMS? Previous versions of it cause this annoying issue that after few minutes from restart SMS stop arriving to phone and the only fix at that time was just to restart it. Tried some patches from telegram but basically end up with no fix.
Click to expand...
Click to collapse
not that i know of

Uhh is there anyway to edit the buildprop without getting a bootloop? I tried with buildprop editor and i vant see any of the info if i change something and when i restart it goes in a loop.

Cylow333 said:
Uhh is there anyway to edit the buildprop without getting a bootloop? I tried with buildprop editor and i vant see any of the info if i change something and when i restart it goes in a loop.
Click to expand...
Click to collapse
I have never tried editing the buildprop so I don't know, sorry.

Marcos8760 said:
yea i forgot to include that part. I thought you didn't need to do that before boot tho. I managed to get BT working by deleting BluetoothResCommon.apk and renaming RazerAuraBluetoothRes.apk to BluetoothResCommon.apk.
Click to expand...
Click to collapse
So do I have to reflash in order to fix Bluetooth?
Sadly my main reason for losing is that I'm running into a mako issue with HavocOS. systenUI keeps crashing whenever the on-screen keyboard is displayed. This happens with the default installed gBoard and SwiftKey beta. It also crashes when the screen goes to sleep. I followed all the steps from the video. Only thing I did besides that was restore a backup from Google Drive so I didn't have to manually install everything. I'm sadly out of ideas and might have to switch to normal GSI or back to LineageOS so the device is stable enough to use.

gumbyx84 said:
So do I have to reflash in order to fix Bluetooth?
Sadly my main reason for losing is that I'm running into a mako issue with HavocOS. systenUI keeps crashing whenever the on-screen keyboard is displayed. This happens with the default installed gBoard and SwiftKey beta. It also crashes when the screen goes to sleep. I followed all the steps from the video. Only thing I did besides that was restore a backup from Google Drive so I didn't have to manually install everything. I'm sadly out of ideas and might have to switch to normal GSI or back to LineageOS so the device is stable enough to use.
Click to expand...
Click to collapse
I have never had to fix BT before first boot.
And also, that's kinda weird. I've never had any systemUI crashes with the keyboard, although i have had a weird bug where the entire OS crashes and it reboots into a state where its impossible to use. however, to fix that, i just reflashed and i never encountered the bug again. your install might have been a lemon. maybe install again?

Marcos8760 said:
I have never had to fix BT before first boot.
And also, that's kinda weird. I've never had any systemUI crashes with the keyboard, although i have had a weird bug where the entire OS crashes and it reboots into a state where its impossible to use. however, to fix that, i just reflashed and i never encountered the bug again. your install might have been a lemon. maybe install again?
Click to expand...
Click to collapse
Do I need to flash back to stock or can I do a "dirty" reflash?

gumbyx84 said:
Do I need to flash back to stock or can I do a "dirty" reflash?
Click to expand...
Click to collapse
Eh. I think flashing back to stock might be better.

Marcos8760 said:
Eh. I think flashing back to stock might be better.
Click to expand...
Click to collapse
Trying out now. I'm at work so I don't have my laptop with me. Trying it work a live CD image lol
Update: It's been sitting on the "Powered by Android" screen for 20+ minutes. I already tried a data wipe from the bootloader. I can get into TWRP. I'm going to give it another 10 minutes then try flashing HavocOS again.
Update 2: I've made progress. Now it's stick on the HavocOS loading screen. It's been like that for 20+ minutes. Tried the bootloader data format.
Update 3: I was finally able to flash HavocOS at home without issue. I flashed Magisk before even booting into the OS and it seems to be working ok. After it rebooted to complete the setup/install, the issue came back. I'm just flashing HavocOS without Magisk for now.

Hello,
Thank you for the guide, i have installed the android 11 successfully, but i got a startup loup when i tried to restart the phone (in a normal way ), the havoc logo started up then the password, but it just louping between them..
Please help

Hello I did exactly what you said for magisk I updated everything but the problem is that I don't have access to superuser and nor to the module in magisk in my razer phone 2 with havocOS.
Do you have a solution to this problem thank you ?