Database Info

[CM RECOVERY] Sources released, Private alpha testing stage

Hi All!
I pushed my fork back to GITHUB
I compiled CM recovery for Galaxy 3, it was long journey
I need some help. My development speed is very low, I'm not dev at all and my C knowledge is very limited. Also I can't invest many time in porting CM recovery.
Thing that worked for my setup (/system - rfs /data ext2 /cache - ext2):
1. it compiled!
2. partitioning SD card
3. making backup
4. restoring data partition (other parts and boot/recovery not tested)
5. wipe cache paritions
6. running fix_permissions scripts
7. running keypress test
I want You to help me choose that to do next: make update.zip worked or try to do backup/restore fully working?
Also I need link for update.zip that surely worked for JPM to test it.
recovery is in pre-alpha stage, I don't want do public alphas, because it simply not tested, and really may brick phones
Now recovery in private alpha testing stage, PM me if you brave, want to test alpha and accept risk of bricking you device

good job.
I don"t know if I can help you much but I will try if you need to.

FS supported by builds:
Build # /system /data /cache
26 rfs ext2 ext2
27 ext2 ext2 ext2
30 ext2 ext4 ext2

Good job
You can give it to some testers though willing to test even at the risk of bricking so that devs like you are motivated and get feedback
Testing really helps
I can help too

if you are porting cwm recovery latest version it uses newer scripting language and thus old update.zip files wont work anyway.

finally! SG3 is becoming a good phone lol ! thanks!

subscribed...
i´d suggest to make nandroid backup work first, then the danger of having a softbrick is much smaller.

That's fantastic news !
Backup/recovery should be top priority I think. Flashing update.zip is not something we could do before, so we won't miss that.

Bubble-be said:
That's fantastic news !
Backup/recovery should be top priority I think. Flashing update.zip is not something we could do before, so we won't miss that.
Click to expand...
Click to collapse
we could do it with eclair...

FadeFx said:
if you are porting cwm recovery latest version it uses newer scripting language and thus old update.zip files wont work anyway.
Click to expand...
Click to collapse
My developing speed is really slow, I start porting it ~1.5 months ago
Version is ClockworkMod Recovery v2.5.1.8 is it old or new version for update.zip ?

making everything to work would be awesome... i believe in you ppl! you will make it work! you have to make it work! because no one else is even close to being capable of doing the magic that you are doing!

the new script version is out for 3 or month or 4 so already...

Nice work
Do you know when you release the 1st beta?

its done when its done... dont ask dont tell...

deskjeti said:
Nice work
Do you know when you release the 1st beta?
Click to expand...
Click to collapse
dude read>
recovery is in pre-alpha stage, I don't want do public alphas, because it simply not tested, and really may brick phones

mumbozver said:
Hi All!
I compiled CM recovery for Galaxy 3, it was long journey
Click to expand...
Click to collapse
Maybe the best news concerning the g3 in a long time. Keep it up man! I am not able to do much but I'm eager to beta test!
sent from my kirillos' v.3 fugumod 2.2 BE oc'd JIT enabled nokia 3210

can you gine me workin fix_permissions scripts to use it from internal use ?> thanks in advance

You can test the recovery by using terminal.But there's a problem that u can't return to normal system.I think it 's because the video driver return to basic mode etc.(Just guess it)I sugggest u don't compile all parts of the cwm but a little part.For we just need a little function now.Test it in terminal.While I have a computer.I will try to help,but I can't promise anything...Haha
Sent from my GT-I5800 using XDA Premium App
WHEN I USING ENGLISH IN COMUNNICATING WITH OTHERS. SOMEONE WILL TELL ME:U CAN PASS THE CET-4 EASILY....

nikkpap said:
can you gine me workin fix_permissions scripts to use it from internal use ?> thanks in advance
Click to expand...
Click to collapse
"worked" mean it runs fine from recovery menu, and do its job.
It's unmodified, and I'm not sure it fully correct for our phone.
You may find it here: https://github.com/CyanogenMod/android_bootable_recovery/blob/froyo-stable/utilities/fix_permissions

instead of making update.zip work, u can complete the nandroid and backup\restore
i flashed cm7 in my friend's X8
the update.zip did not work properly so i extracted the rom files and made them as a backup and restored the rom with that backup-worked like a charm
we can install roms if the dev's provided it as a backup file(which is safer than using update.zip)

Multi Boot Menu for Xperia Z1 Compact

Multiboot for Sony Xperia Z1 Compact
How its look -> http://i58.tinypic.com/35346bt.png
How to install boot menu
download bootmenu_amami.rar, extract folder "bootmenu" to the your internal storage
put boot.img or kernel.elf to the mainrom folder, make sure thats the same kernel like your primary rom (aka main rom)
download bootmenu.img from attachment, flash bootmenu.img using fastboot commnd: fastboot flash boot bootmenu.img
Click to expand...
Click to collapse
Since your bootmenu folder no contain settings.ini (you runing bootmenu at a first time), settings.ini will be created easily. You need to complete main step aka main rom creation:
(mainrom creation)
reboot into bootmenu, chose "patch rom package", navigate to the bootmenu folder on your internal storage, navigate to the mainrom folder, select mainrom.zip package (make sure boot.img or kernel.elf is the same like your current main rom kernel, and make sure boot.img is in folder mainrom), select mainrom.zip and click "yes". Main rom will be added into boot menu entry. Now reboot again into boot menu and you will see new menuentry, chose these menu to boot into your primary rom!
(other roms creation - you can do only if you completed main rom step)
reboot into bootmenu, chose "patch rom package", principe is a bit diferent than main rom step (we have 3 steps):
(step 1): make sure seccond rom package is on your external storage ...see this post -> http://forum.xda-developers.com/showpost.php?p=52830021&postcount=45
(step 2): chose rom zip you want to patch, patch them
(step 3): reboot again into boot menu (new rom entry will be displayed), select these rom to boot, on led blinking press to boot into cwm, now you are in cwm of these rom, now navigate to the same folder where is your package, you will find zip with appended name "patched.zip", chose these patched zip to install trought these recovery, you are done!
Click to expand...
Click to collapse
WARNING:
there is possibility for your partitions of the main rom to get overwriten if multiboot.sh fail to patch these rom you going to patch, just to let you know! Two click solution is in testing stage so there is probably a lot of bugs! I am not responsible if you lost your private data! So guys if you willing to help, I am waiting. Things need to be improved in multiboot.sh !
Click to expand...
Click to collapse
Source code of the my bootmenu project
https://github.com/munjeni/bootmenu_z1_and_z1c
Public License for BOOTMENU and for my Auxiliary Work
You can Distribute my source without my Permissions. Distribution should include my XDA name 'munjeni' and Link to this 'BOOTMENU' thread in your Credits sections/About sections and Properly Visible to Human Eyes. If you use our source and have them modified, you need to make them public to everyone!!! If you not propertly use my source and you not give proper credit, and you not share your modified source code which is based on my source code, I will find you and I will report your post!
Click to expand...
Click to collapse

No doubt, I'm really interested in multi boot,
I have tried it on my XU and it was awesome:laugh:

munjeni said:
Hallo, just to reserve our thread for something that you will like for sure! I have plan to port my old project to our device, more info you can see here -> http://www.xda-developers.com/android/xperia-boot-menu-ported-to-the-xperia-p-in-preview-form/
First thing - I will port them, thats for sure! Next thing - will try to integrate all things into boot menu (look into tutorial thread to see how it working) to make all things easy to all as possible, first of all I need to get more free time! Soon when I get one free day I will give you beta version! By now whant to see your opinions! Do you have interest in multiboot??? Let me know first!
Click to expand...
Click to collapse
I'm flashoholic,like to test everything, multiboot sounds nice
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app

Would this for example allow to have stock and cm11 both installed and easily switch between those 2? If yes then im totally up for it

Sounds definitely awesome!

Progress... Boot menu beta done, having problem with kexec, seems kexec not working. Will try with stock kernel since cm kernel probably have no working kexec.

Beta 1 is out! By now I have included 2 multiboot things, cwm and stock kitkat, will give you more (cm11...etc) when I get more free time! Enjoy!

munjeni said:
Beta 1 is out! By now I have included 2 multiboot things, cwm and stock kitkat, will give you more (cm11...etc) when I get more free time! Enjoy!
Click to expand...
Click to collapse
Can you not disable CABL and enable taptowake as any and all searching shows them to be kernel related?

XperienceD said:
Can you not disable CABL and enable taptowake as any and all searching shows them to be kernel related?
Click to expand...
Click to collapse
I'm sorry but I do not know what you're talking about! Plese be more clear!

munjeni said:
What? Plese be more clear
Click to expand...
Click to collapse
tap2wake
CABL

XperienceD said:
tap2wake
CABL
Click to expand...
Click to collapse
Sorry mate but our thread is related to the multiboot and not to the kernel things, you can open a new thread for your problem, sorry!

munjeni said:
Sorry mate but our thread is related to the multiboot and not to the kernel things
Click to expand...
Click to collapse
Oh, given that a boot.img is actually a kernel I thought it might be something you could implement whilst working on it.
munjeni said:
you can open a new thread for your problem, sorry!
Click to expand...
Click to collapse
They're not problems they are suggestions.

New version is out!
Changelog:
- all isues with kexeced kernel solved (missed modile data, wifi, bluetooth...etc)
- black theme
Enjoy!

I have trying to boot cm11 from sdcard whole day and have no idea why fail to boot! Anyone tried to boot cm11 from sdcard? What might be a problem?

munjeni said:
I have trying to boot cm11 from sdcard whole day and have no idea why fail to boot! Anyone tried to boot cm11 from sdcard? What might be a problem?
Click to expand...
Click to collapse
I'm planing on trying tomorrow, I'll try and give some feedback

Solved! Will give you soon cm11 in multiboot!

munjeni said:
Solved! Will give you soon cm11 in multiboot!
Click to expand...
Click to collapse
Well then I shall wait until you do so Thank you for your effort:fingers-crossed:

Done and CM11 is booted sucesfully from sdcard By now have only one problem which I have experienced last year on my multiboot for Xperia Go, I have solved them on Xperia Go but unable to find a thread how I got fixed them solved, problem now on Z1C is these seccondary rom runing from sdcard is very slow like was a year ago on Xperia Go, if some one found my post where I have fixed that please give me a link. I don't know if there is something related to the tune2fs parameters since I forgot how I got them fixed. Every idea is welcome!

Maybe this
http://forum.xda-developers.com/showpost.php?p=44945343&postcount=24
http://forum.xda-developers.com/showpost.php?p=44969886&postcount=36
http://forum.xda-developers.com/showpost.php?p=44979190&postcount=47

Yes seems 3.th post related to tune2fs and journal_data_writeback to cache and data giving better performance. Stil noticed some lags, probably because my 8gb old sdcard is so slow Will try to boot from internal storage, maybe it will give better performance or at least maybe an 64gb class 10 sdcard can solve lag problems? What you think guys?

[Guide] Multi Boot Note 3 (Video Guide Added)

[Guide] Multi Boot Note 3 (Updated 24/07/2015)​
*** Hi Guys i no longer have a note 3 so i cant do any testing but our team member is here to give support for you all and even im here to give support except testing. please contact @[email protected] and @djnim for support.***
I am using this on SM-N9005 Snapdragon Variant of the Note 3; I believe this will work with other Note 3 Variants as well. Few of them are already tested and you can find them below. Others who have different variants which are not tested can try this and update us, and we will be here to help you out if you are ready to try this out.
@chenxiaolong is the one who made this happen to our beloved Note 3
Main advantage of this is you can try any new rom with out loosing or having any kind of trouble with your existing rom. This mod will not change anything in your primary rom, so any time you can go back to your normal state.
Disclaimer
1.I am not responsible for bricked devices, dead SD cards,etc.
2.Before going further! YOU are choosing to make these modifications.
supported Devices: ( Tested and confirmed working)
SM-N9005 (International Qualcomm): hlte (Tested by me )
SM-N900T (T-Mobile US): hltetmo (Tested by @MistaEast ) confirmation post
SM-N900R4 (US Cellular): hlteusc (Tested by @harshal10398 ) confirmation post
SM-N900 (International Exynos): ha3g (Tested by @mohnishkat ) confirmation post
SM-N900P (Sprint): hltespr (Tested by @lord dredd ) confirmation post
SM-N900K(Korean): (Tested by @Premananda_laishram) confirmation post
Requirements
* Read the full guide before Starting.
* Backup your phone if you are doing this first time. (Full Nandroid backup recommended for the new comers and it’s also recommended to others who don’t know what they are doing exactly even if they have multi booted several times)
* Rooted Note 3 with custom recovery (preferred TWRP or philz).
* free space in your internal SD (for example a Cm based roms take up to 2.5GB to 3.5GB and a TW roms take up to 5GB or more.)
* If you face any trouble please read the FAQ before doing something or asking for help. And if you want help please provide as much as details(device, roms, etc.) you can.
*
Instruction:
1.Download your desired Rom which you want to use for multi booting and the mods, addons, gapps, Kernel etc for the same. Keep the files in your internal memory.
2. Download the most recent snapshot release of Dual Boot Patcher and install it on your Note 3.
3. Open Dual Boot Patcher and grant SU permission. Then go to ROMS and you will see your Primary rom, press the 3dotmenu key and click "set kernel". If it fail to set kernal please read the FAQ.
4. Then In Dual Boot Patcher go to Patch Zip File and Choose hlte for snapdragon variant and ha3g for Exynos veriant (Samsung Galaxy Note 3) from the drop down menu.
5. In the second drop down menu select "Data Slot".
6. Below that you have to enter the ID of the secondary rom.(Example 1, 2, 3, etc. - it will take it as /data/multiboot/data-slot-1)
7.Now tap on the below button to choose the ROM's, Gapps, Kernel and mods to patch them and make them perfect for Multi booting.
8. Always remember to keep same slot ID for the Gapps, kernels and mods same as the rom. (Example: if you want to flash the gapps/kernel to the data-slot-1 rom then you have to select the same ID that’s 1 or if you want to flash the gapps/kernel to the data-slot-2 rom then you have to select the same ID that’s 2.)
9. When selecting the files except cm rom zip there will be a “preset” drop down menu, from that you have to select according to the file you are going to patch. (Examp: for roms, kernels, mods, addons – custom; for gapps – Google_Apps; for Su zip – other/SuperSu; For xposed-Other/Xposed)
10. Now press the tap to begin patching button to patch the file. And you will get a new patched zip file in the same location.
11. Now Boot into custom recovery and flash the new patched file and reboot.
12. And your device will boot into New Rom.
13.Install the Dual Boot Patcher app and set the kernel for your second ROM as well.
14. To switch between roms
•Open Dual Boot Patcher app/roms and click on primary or secondary rom as you like and reboot.
•Or Use Swap Roms to switch between Roms.
* Important things to keep in mind: while installing a rom or mod with Aroma installer don't reboot directly from the aroma.
You have to always uncheck the last option to reboot in aroma and click finish. So it can finish the final steps for multi booting.
And if you miss that it will only reboot to recovery. To boot back you have to flash your primary rom kernel or re-flash the patched rom.
Never update a secondary rom through OTA Update.
*. For other devices:
1. You have to download and install X-plore File Manager (which I am using) from play store.
2. Open X-plore File Manager from app drawer and navigate to the patched zip file and open it.
3. Now you will see a folder named multiboot inside that you will find info.prop, now open info.prop with the text editor which comes with the x-plore file manager.
• And then find and change mbtool.installer.ignore-codename=false to mbtool.installer.ignore-codename=true
Revert
To revert back or if you face any problem just flash my Multi Boot cleaner.zip which will wipe all the installation files from \system and restore the primary rom kernel.
As a backup keep a copy of your kernel flashable zip file.
FAQ
1. I can't set the primary rom kernel in xyz rom. And I can’t switch to other rom in primary rom.
Ans. Just download the set kernel fix as per your model and flash it in the recovery.
The above fix only work for primary rom. If you have trouble with any other roms just add ro.patcher.device=hlte(for other models add your model instead of hlte) to the bottom of build.prop of that rom and you are good to go.
If you don’t know how to do that just pm me and I will make a flash able zip to add it to your secondary rom.
if the above didnt work Read this post please
2. App sharing?
Ans. Until now no luck. (Still under testing)
3. This rom can’t be patched.
Ans. some roms are not supported its known, if the Dev have time may be he will consider including them.
Also read this
Credits/ Thanks:
@chenxiaolong
Original Thread: http://forum.xda-developers.com/showpost.php?p=45659284
Don't forget to thank him and if you can please consider a small donation for him because he really deserve it.
@aukhan & Team Emotroid
His Thread (Where I got the idea and help to make this guide): http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
@rlorange for the help and support.
His thread for Dual boot backup and restore app. http://forum.xda-developers.com/showthread.php?t=2491299, http://forum.xda-developers.com/not...-4-15-multi-boot-backup-restore-v1-0-t3087187
@AholicCert for helping me with some scripts
@ other XDAmembers
Video Guide
https://www.youtube.com/watch?v=upeSC65t5XQ

Going to try it mate tnx

a_prabhu7 said:
Going to try it mate tnx
Click to expand...
Click to collapse
Welcome try it and let us know.
Sent from my SM-N9005 using XDA Free mobile app

Has anyone tried this out on N900????

thetitanium said:
Has anyone tried this out on N900????
Click to expand...
Click to collapse
Try it your self and let us know. i will promise you that it will not touch your primary rom. Any time you can go back to normal.

54NJ41 said:
Try it your self and let us know. i will promise you that it will not touch your primary rom. Any time you can go back to normal.
Click to expand...
Click to collapse
tried on my 4.4.4 vn rom-set kernel-failed to set kernel..

vagenrider said:
tried on my 4.4.4 vn rom-set kernel-failed to set kernel..
Click to expand...
Click to collapse
1. First of all have you grant super user permission for Dual Boot Patcher. If not just reboot and try again.
2. Do you have enough space in your sdcard (internal) for the backup of the kernel.
3. Just check if there is sdcard/multiboot/primary/boot.img is their.
4. Try the 8.0.0.r1119.g9c51715 version of dual boot patcher if the above didn’t help.

54NJ41 said:
1. First of all have you grant super user permission for Dual Boot Patcher. If not just reboot and try again.
2. Do you have enough space in your sdcard (internal) for the backup of the kernel.
3. Just check if there is sdcard/multiboot/primary/boot.img is their.
4. Try the 8.0.0.r1119.g9c51715 version of dual boot patcher if the above didn’t help.
Click to expand...
Click to collapse
tried all mate but nothing..

vagenrider said:
tried all mate but nothing..
Click to expand...
Click to collapse
Hi bro can you please send me the link to the rom which you are using. I will try and let you know.

54NJ41 said:
Hi bro can you please send me the link to the rom which you are using. I will try and let you know.
Click to expand...
Click to collapse
here you go http://samsungviet.vn/threads/note-3-snapdragon-vn-team-vn-rom-v7-0-online.1034/
apreciate very much your time-effort etc thank you

vagenrider said:
here you go http://samsungviet.vn/threads/note-3-snapdragon-vn-team-vn-rom-v7-0-online.1034/
apreciate very much your time-effort etc thank you
Click to expand...
Click to collapse
Which version 7.2 or other

54NJ41 said:
Which version 7.2 or other
Click to expand...
Click to collapse
7.2

Here we go! I have complete dual Boot on my Note 3! It's awesome! My first Rom is Aryamod 5.3 and my Second Rom is temasek unoffical cm rom! Thanks to the Developers for your great Roms! And now Thanks to you 54NJ41! Your tutorial is great! I wait over 1 year for dual Boot on my Note 3 and now I have it!

does anyone knows how i could get more system partition space?
I tried to use titanium backup to move some apps but it says my system is 2.38gb full

Rogers Note 3
Anyone can tell me if I can install it for the Canadian Rogers Galaxy Note 3 ?
Thank you

you said:
Download and keep your desired (Secondary Rom) CM or AOSP rom + Gapps zip files
the second must be CM or AOSP?
what about if i want to use Arya and Omega roms for example?

vagenrider said:
7.2
Click to expand...
Click to collapse
I have tried the rom but same result as yours. But don’t worry I have an alternative way to set the kernel for your primary rom.
First make folders in your SDCard, “MultiBoot” in it “Primary” it should be like: Sdcard/MultiBoot/Primary
Then extract the boot.img from your rom zip and copy it to Sdcard/MultiBoot/Primary
So the result will be Sdcard/MultiBoot/Primary/boot.img
It’s done.

NightForce said:
Here we go! I have complete dual Boot on my Note 3! It's awesome! My first Rom is Aryamod 5.3 and my Second Rom is temasek unoffical cm rom! Thanks to the Developers for your great Roms! And now Thanks to you 54NJ41! Your tutorial is great! I wait over 1 year for dual Boot on my Note 3 and now I have it!
Click to expand...
Click to collapse
Welcome bro

dream_catcher79 said:
does anyone knows how i could get more system partition space?
I tried to use titanium backup to move some apps but it says my system is 2.38gb full
Click to expand...
Click to collapse
To make space in your system partition.
1. Delete what ever apps you are not using from system/app and syatem/priv-app (Don’t delete if you don’t know what it is or what your are doing.)
Example: shealth, etc.
2. Move some google apps from /system/app to /data/app to make them user app using root explorer.
Example: maps, gmail, chrome, etc.

thermax04 said:
you said:
Download and keep your desired (Secondary Rom) CM or AOSP rom + Gapps zip files
the second must be CM or AOSP?
what about if i want to use Arya and Omega roms for example?
Click to expand...
Click to collapse
To dual boot two TW roms is very hard. Because there is not enough space to fit both system file in your system partition. Other wise you have to deboalt the primary rom and you have to deboalt secondary rom zip before flashing. And by doing so you will lose most of the features of your TW roms.
And if you want to use CM as primary and TW rom as secondary its possible but not recommended. Because you will have trouble with flashing mods etc for your TW rom.
The better option at the moment is to keep the TW rom as Primary and others a secondary.

[GUIDE][AOSP][7.1.2][HLTE][Rev11][11-Mar-18]Resurrection Remix - Rock Stable Setup

During the last few months I have been testing several Nougat rom/kernel/modem/su combinations for the hlte N9005 international.
I created this thread to share my setup, hoping it will help others to save the many hours of research, trial, error and frustration I had before reaching the jackpot.
I have 3 hlte phones at my disposal, two myself and one my wife. All three are running trouble free.
By using my setup you will get:
Absolutely no freezes, reboots or FCs
Stable root and Safetynet checks ok
GPS fast and stable fix - average 5 seconds worst 20 seconds
Low battery drain (of course actual drain depends heavily on your apps and usage)
Everything works (AFAIK - you tell me what does not)
Keep in mind my main goal is to provide a stable setup. I will do my best to update this thread regularly, but it is very unlikely I will be using the very latest builds available, mainly because before I adopt a new build it must be thoroughly tested.
If you're interested head to the guide in Post #2
Why Resurrection Remix?
RR has, IMHO, the best combination of features and stability. The RR team has been around for a long time without the ups and downs of other roms. For the Note 3 we are in a very fortunate time, with an official build and many unofficial builds to choose from.
Since RR is based on LineageOS, it is available for most devices. It is very likely when we finally retire our Note 3 and move to another flagship, RR will be there for it.
Why Not Oreo?
Well, thread title says it all.
Credits and Thanks:
@vidwhal for the current RR build
@gj86 for Synergy kernel
@Jairus980 for Xenial kernel
@Hereiwas and @jcadduono for modems and bootloaders
@topjohnwu for Magisk
@stangri and @kantjer for Magisk unofficial daily beta builds
@Deic for the Safetynet fix Magisk module and @NovelliJack for finding the module
@MastahF and all other contributors that made the Open GApps project possible
Special thanks to @tarkzim for the RRN build used in initial setups.
and everyone else I forgot to mention.
>>>>>>> I know - screenshots below are from a previous setup. I will update then sometime in the future.

Rock Stable Setup
Using Resurrection Remix
Revision 11 - 11-Mar-2018​
Phase 1 - Prepare for install
Here I am assuming you have a Windows PC. If not you will need to use google search to adapt my instructions to your available OS/hardware. The PC is only required for this phase.
1 - Samsung USB Driver:
Make sure you have the Samsung USB driver installed in your Windows PC.
If not download and install the latest driver:
- SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.65.0.exe
2 - Odin:
If you do not have Odin, get it here, unpack to any folder and create a shortcut pointing to Odin3 v3.09.exe.
There are newer versions of Odin, but they may have issues with our Note 3. Odin v3.09 is the one to use.
3 - TWRP
New to TWRP? Read this guide: TWRP: the complete guide to using Recovery on Android.
If you do not already have it, install TWRP 3.2.1-0. Download it from https://dl.twrp.me/hlte. More info here.
If you no not have TWRP installed download the .tar file and flash with Odin.
If you have an older version download the .img file and use your current TWRP to flash the image into recovery partition.
4 - Update Bootloader and Modem:
You have to install latest Nordic Countries Bootloader and Modem. I have prepared a "tar.md5" with both.
And yes, modem is not country or region dependent. Rest assured Nordic will work no matter where you are.
Get it from here: N9005_Nordic_XXUGPQB1-Modem_XXSGBQD1-Bootloader.tar.md5
Updating bootloader and modem is a must!
If you don't you may get the "SIM Card not detected" error and GPS fix will be slow or not work at all.
There are many sure ways to flash modem and bootloader so that they "stick". What always works for me is:
- Restart into Recovery (TWRP)
- Select Reboot->Power off
- Turn on directly into download mode by holding Down Arrow+Home+Power at the same time
- Connect phone to PC
- Flash with Odin using the AP slot
Now you should check if update was successful. The best way is to install the app Phone INFO, run it and select the Firmware tab. The correct Bootloader and Baseband (modem) above should be displayed. There is a screenshot in first post.
If the update did not work repeat the steps carefully until it does. You may, as a last resort, after powering off remove the battery, wait for about 30 seconds, reinsert the battery and then turn on directly into download mode.
Thanks to @Hereiwas for the files I have used in previous setups. Check out in his thread Bootloader and Baseband for SM-N9005.
If you need more info on flashing modems and bootloaders also take a look at @jcadduono thread [Direct Download] Latest Bootloaders & Modems.
PHASE 2 - Download the necessary installation files
1 - Resurrection Remix Nougat rom - thanks @vidwhal:
Download from here: RR-N-v5.8.5-20180101-hlte-Official-vidwhal.zip.
Please note that I am not the rom builder or developer. All credits go to @vidwhal and the RR Team.
This is the rom thread: [ROM][HLTE][UNOFFICIAL][OMS]Resurrection Remix N.
Please note this build may not be the latest available. The goal here is to have a stable rom that you will be able to use as a daily driver with no issues for a long time. Only after a lot of testing a new build makes into my setup.
I modified the zip to remove Magisk. This will make it easier to use newer or beta Magisk builds if necessary in the future. Remember Safetynet is a cat and mouse game and changes happen fast.
Special thanks to @tarkzim, who produced the RR builds used in earlier setups. He did a fantastic job of producing a very stable build without a Note 3 device for tests. His builds led me to create this thread.
2 - Magisk v16.0 Official - thanks @topjohnwu):
Magisk Installer: Magisk-v16.0.zip
Magisk Manager: MagiskManager-v5.6.1.apk (optional - you might need it in the future)
Magisk Uninstaller: Magisk-uninstaller-20180222.zip (optional - you might need it in the future)
if you decide to use newer builds do it at your own risk. I strongly recommend to keep these.
3 - Gapps:
Open Gapps Pico: open_gapps-arm-7.1-pico-20180311.zip
Not much to say here. Open GApps FTW.
Again the above build is the one I tested. Use this for a failproof installation, but feel free to use a newer build. Usually it will not be a problem.
I prefer Pico Gapps so I have the bare minimum as system apps. And I live by the KISS Principle. All other gapps I need are installed as user apps so I am allowed to use Titanium Backup to backup/restore them with data.
If you would rather use another Gapps package just pick the one you want. All packages should work but the Aroma. Aroma does not work in TWRP 3.
4 - Xenial Kernel - thanks @Jairus980:
Xenial Kernel: [Hlte][Xenial-b26x][02.01.18][N7.1-GSM].zip
Kernel thread: [Kernel][Xenial][Hlte].
With Xenial you have some fixes like the correct charging current in lock screen and working Gravity, Linear acceleration and Orientation sensors. Of course there is a lot more under the hood. If you plan to do some kernel tweaking Xenial offers more options.
If you do flash Xenial kernel do not report any bugs in RR thread. To report a bug you must first go back to stock kernel by dirty flashing RR and Magisk. If you are still able to reproduce the bug then you may post it in RR thread.
Even if there is a newer kernel release, you should keep using the build I posted here to have my tested stable setup.
Special thanks to @gj86 for his Synergy Kernel, used in my previous setup. It is also a great option.
5 - GPS Fix:
In this setup there is no need for a GPS fix. GPS is fast and rock stable as it should always have been.
But you really must update your modem to my recommend Nordic QB1 or GPS will be slow or not work at all.
Do not worry about your current location. The modem will work not matter where you are.
Latest RR builds somehow made GPS fix slower. I checked the gps.conf file and it is exactly the same as in previous builds.
I have my own optimized gps.conf, prepared originally for Marshmallow CM13, with a few more adjustments for Nougat.
After installing my gps.conf in latest RR build, gps fix is back to normal, taking only a few seconds.
I prepared a flashable zip to install my gps.conf. It saves existing gps.conf and put mine in its place.
Download it from here: Fix-GPS-for-hlte-la14.1-based-roms-v1.zip.
PHASE 3 - Backup!!
Now it is time to make backups of your current setup.
Use TWRP to make a nandroid backup. You will need it if something goes wrong. If you are paranoid like me make two and save them on your PC hard drive.
If you use Titanium make also a Titanium full backup. Remember that you should never restore system apps or settings. Use Titanium only to restore user apps and xml backups of wifi passwords, call log and sms messages.
The steps to install the new ROM will not erase your internal storage, but why not make a backup of everything to your PC or an OTG USB Drive.
PHASE 4: Install
- Make sure you have updated TWRP and your bootloader and modem as instructed in phase 1
- Make sure you have all files downloaded from phase 2 in your phone - preferably in external sdcard
- Make sure you have backups!!
- Reboot into Recovery (TWRP)
- Use advanced wipe to wipe System, Data and Cache
- Flash RR-N-v5.8.5-20180101-hlte-Official-vidwhal.zip
- DO NOT WIPE ANYTHING
- Reboot System (be patient - it will take a while, around 3-4 minutes)
- Pick your preferred launcher
- Check Settings->Date & Time and make sure it is ok
- Reboot into Recovery (TWRP)
- Flash [Hlte][Xenial-b26x][02.01.18][N7.1-GSM].zip
- Flash Magisk-v16.0.zip
- Flash open_gapps-arm-7.1-pico-20180311.zip (or the one you prefer)
- DO NOT WIPE ANYTHING
- Reboot System (this time it will be faster)
- Go to Settings->Accounts and add your google account
- Customize your other settings
- Run Magisk Manager and check if SafetyNet passes
- If not disable/reenable "Magisk Hide" option in Magisk Manager Settings and try again
- Restore/install apps/data
- PROFIT!

[Reserved]

wow, nice to see that someone using and "sharing" my builds
but a little tip for you, maybe you can ask me first before you post something are modified from me, no offense and i saw that includes my name on it.
just remind you and i think i will keep building this when i'm free, anyway, thank you for posing this. all good.
EDIT: also i think there is no need for removing magisk separately, it's fine for flashing newer magisk over the older one.

tarkzim said:
wow, nice to see that someone using and "sharing" my builds
but a little tip for you, maybe you can ask me first before you post something are modified from me, no offense and i saw that includes my name on it.
just remind you and i think i will keep building this when i'm free, anyway, thank you for posing this. all good.
EDIT: also i think there is no need for removing magisk separately, it's fine for flashing newer magisk over the older one.
Click to expand...
Click to collapse
Sorry, you are absolutely right.
Thanks for being cool with it.
The main point in changing the rom zip is removing the magisk manager system app. It is a little tricky for noobs to remove the system app to be able to install the v5 beta Magisk Manager.
And thanks again for making your fantastic RR build available.

Thank's for your work. I installed all, but then I had a problem. When I try to open settings/apps, it crashes everytime....

sperug said:
Thank's for your work. I installed all, but then I had a problem. When I try to open settings/apps, it crashes everytime....
Click to expand...
Click to collapse
This does not happen in my phones.
In my work phone I have 600+ apps installed. It takes a while to open but no crashes.
If you post a logcat I may be able to help.

I reinstalled everything, and before made a full wipe, also of the internal storage. And the problem was no more present! Wow! And thank you again...

I checked AFH and have 30+ downloads of installation files.
Any more success or failure cases? Please let me know.

This might be a silly question: You wrote I should download the latest NORDIC COUNTRY Bootloader and Modem.
Is this also correct if im not living in an other region or should I download the one from my Country? Thanks.

BobbyKa said:
This might be a silly question: You wrote I should download the latest NORDIC COUNTRY Bootloader and Modem.
Is this also correct if im not living in an other region or should I download the one from my Country? Thanks.
Click to expand...
Click to collapse
AFAIK it should work for you no matter where you are.
I live in Rio de Janeiro, Brasil and use it.
If it does not work for you just flash another one.

I tried the Nordic ones and everything seems to work. Not a killer but would be great: is there a way to get SPen functions inclidung Air Command? Thanks for the help.

BobbyKa said:
I tried the Nordic ones and everything seems to work. Not a killer but would be great: is there a way to get SPen functions inclidung Air Command? Thanks for the help.
Click to expand...
Click to collapse
To use Sammy Spen apps/features you need a Touchwiz based stock rom.
There are some apps with similar features for AOSP roms.
Many users say the best is SPenCommand developed by @emandt. It is paid but users say that the app is well worth the price.
Check the SPenCommand Google+ Comunity.

Great post. I don't see google assistant working, any clue?
Sent from my Pixel using Tapatalk
---------- Post added at 09:22 PM ---------- Previous post was at 09:10 PM ----------
Please ignore, I installed nano gapps and it worked
Sent from my Pixel using Tapatalk

what about battery life ?

has anyone tried this on Sprint Note 3 sm-n900p ?

svbarbosa said:
Check the SPenCommand Google+ Comunity[/URL].
Click to expand...
Click to collapse
I installed SPenCommand but the App doesn't open. When clicking the Icon nothing happens. Anyone knows about this Problem or knows another app for this?
Beside that everything (incl. Batterylife) seems great on this first day of testing.

I have followed your step to instal, wipe dalvik/art, system, data & chache. Flash ROM then reboot.
I got 'Could not do normal boot'.
Enter TWRP again and instal synergy kernel and reboot, I still got 'Could not do normal boot'.
My phone:
Samsung Galaxy Note 3 SM-N900S (Korea)
TWRP 2.8.7.0 hlteskt
CP N900SKSU0GPC5
BL N900SKSU0GPB1
sent from my Galaxy Note 3 using XDA Labs

BobbyKa said:
I installed SPenCommand but the App doesn't open. When clicking the Icon nothing happens. Anyone knows about this Problem or knows another app for this?
Beside that everything (incl. Batterylife) seems great on this first day of testing.
Click to expand...
Click to collapse
I have never used SPenCommand myself. Just read good things about it many times in other threads. Try to search and get help from people who are using it.
You may also check these apps: Note Buddy (S Pen Helper) and CM S Pen Add-on(ROOT).
And this guide on them: The Ultimate S Pen Customization Tool for Your Galaxy Note 3.
But be advised that I have no experience using these apps. Just found them using google.
opexblue said:
I have followed your step to instal, wipe dalvik/art, system, data & chache. Flash ROM then reboot.
I got 'Could not do normal boot'.
Enter TWRP again and instal synergy kernel and reboot, I still got 'Could not do normal boot'.
My phone:
Samsung Galaxy Note 3 SM-N900S (Korea)
TWRP 2.8.7.0 hlteskt
CP N900SKSU0GPC5
BL N900SKSU0GPB1
sent from my Galaxy Note 3 using XDA Labs
Click to expand...
Click to collapse
Sorry I can not be of help here. I only have the hlte N9005 international Note 3.
Maybe you could replace Synergy RC9 by a kernel that you are sure works with your N900S.

svbarbosa said:
Sorry I can not be of help here. I only have the hlte N9005 international Note 3.
Maybe you could replace Synergy RC9 by a kernel that you are sure works with your N900S.
Click to expand...
Click to collapse
Thank you for fast response. I will try other kernel.

Problems with flashing Oreo 8.x check this:

If you're having problems flashing Oreo 8.x:
1) Assure you have the latest TWRP (they are backward compatible) - earlier TWRPS do not play nice with Oreo. .
squid2: twrp-osprey-3.2.1-r1.img
https://forum.xda-developers.com/devdb/project/dl/?id=27954
official: twrp-3.2.1-0-osprey.img
https://dl.twrp.me/osprey/twrp-3.2.1-0-osprey.img.html
PLEASE note - if you use the official, you will be presented with an option about installing the TWRP app when you boot. DON'T. i.e. tap the button that says "DO NOT etc" and it will boot without installing the app. You can turn this off in settings. (I have had serious problems with the twrp app. Use flashify instead.)
2) make sure you're flashing the latest ROM - some old ROMs are bad. With these early Oreo builds each increment can be a HUGE milestone!!!
3) assure you don't flash a gapps if one is included in the ROM as it is with most of the 8.x ROMs like PE, PEGo, COS, etc.
4) tap "set up as new" during install.
5) assure SDcard is NOT exfat - use fat32. Oreo and exfat don't play well together.
6) system should be ext4, data should be f2fs, cache should be ext4.
7) check your google login/password.
8) When WIPEing before flash be sure to do all 4 in advanced: Dalvik/ART, system, data, cache. Otherwise you get old gapps and other junk. Do not wipe internal storage or SDcard.

KrisM22 said:
Assure you have the latest TWRP
squid2: twrp-osprey-3.2.1-r1.img
https://forum.xda-developers.com/devdb/project/dl/?id=27954
official: twrp-3.2.1-0-osprey.img
https://dl.twrp.me/osprey/twrp-3.2.1-0-osprey.img.html.
...
Click to expand...
Click to collapse
before deciding to upgrade to twrp 3.2.1, can we know what is/are better in squid2 twrp than the official one? thanks.

m0han said:
before deciding to upgrade to twrp 3.2.1, can we know what is/are better in squid2 twrp than the official one? thanks.
Click to expand...
Click to collapse
Read op in squid2 thread, you'll see diference

green2005 said:
Read op in squid2 thread, you'll see diference
Click to expand...
Click to collapse
Right. My purpose in this little list was to briefly give you a bunch of things to look at - in one place. It's just a start point for folks having trouble getting 8x up and running. It's made up of items that I found myself and others offering one at a time. - save time and avoid repetition! It is hardly a final/full compendium.
To me it doesn't matter which one I use - as a practice, I grab the latest one out simply to test it so I can warn others if I run into problems. Earlier ones just don't play nice with 8.x .