Related
so here is the new edition with uk kernel, basically pretty much the same as before with correct sensor drivers now.
Changelog v1.3 (Android v2.2.1 edition) Download nandroid image here or mirror
- xavwanted's libOMX and MediaGallery.apk which seems to fix HD recording and playback
- Riley600's interactive governor fix
- callwaiting fix
- kousik's mount-o typo fix
- Mioze7Ae move /oc to /system/oc
- bootanim by helmi666
- Email.apk replacement
Changelog v1.2b (Android v2.2.1 edition) Download patch here
- fixes problems with callwaiting functionality.
Changelog v1.2a (Android v2.2.1 edition) Download nandroid image here
- 720P recording fix
- re-added old MediaGallery as Camera app requires it.
- there can be possible hickups with mediascanning (so you know)If you do see many FC's its a symptom of not having done factory reset, so this should indicate whether you need to do it or not.
Changelog v1.2 (Android v2.2.1 edition) Download nandroid image here
- fixed mediascanner issue
- removed old mediagallery (not supported) , now only Gallery3D available.
- removed VoiceCommands app, cpu intensive and taking much storage.
Note, due to the bug in mediascanner and decoding and on top ext2sd support, quadrant benchmarks drastically drops when ext2 is enabled, if the sdcard is not a class6 or higher.. but media decoding bug alone caused incorrect reportings, so dont be surprised when you test now.
Its a full nandroid for new and existing users. if you're using 1.1+ you do not need to WIPE settings, just restore nandroid and reboot, signatures will be recalculated and bootup takes maybe little more, but it works fine.
Patch update Changelog v1.1b (Android v2.2.1 edition) Download patch here
- HDMI added to settings menu, let me know how it works (not tested)
- different proximity sensor module (tested with z-devicetester seems better)
- facebook fix still included.
- Support for loading overclock module at startup.
- apps2ext partition support , will mount at startup if a 2nd partition is found.
its not advanced, so you need ext2/ext3 partition for now.
NOTE: Patches goes into /OpenRecovery/updates and is applied in openrecovery menu "apply update".
Changelog v1.1a (Android v2.2.1 edition) Download nandroid v1.1a link
- Based on 2.2.1 milestone framework leak
- Sync facebook is working
- Lockscreen is new (Blur like)
- see this link for framework theme's.
Changelog v1.1 (Android v2.2 edition) Download v1.1 link
- fixed: OCR camera function currently FC (crash) (Mobireader.apk added)
- fixed: Contacts apk will be replaced in next update.
- fixed: HDMI through media player
- fixed: /mnt/sdcard mount issue
If you want stock korean 2.2 with just english language and working sensors, download this nandroid dump, if you will probably need the 1.1 including recovery.apk to install this the easy way.
but else follow instructions in my other releases, and put nandroid backup into the /nandroid/openrecovery folder and restore using OpenRecovery.
See this post, if you wish to restore a stock rom, or to enable apps2sd filesystem on sdcard
Install instructions:
Make sure sdcard is visible, when you get to step 6 of instructions, or it all fails, same with restore..
A: users with stock 2.1 can proceed to step 1 in instructions.
B: users with stock SBF korean 2.2 rom , need to flash stock 2.1 and goto step 1
C: Users with 1.1+ of rom with OpenRecovery , can skip WIPE and factory reset, and a restore of the new nandroid backup included in the download link, and goto step 8 (and skip step 9 for factory reset)
root it (SuperOneClick ) - included with zip
install OpenRecovery , use included apk.
reboot phone once
copy the folder "nandroid" to root directory of your sdcard.
Make sure sdcard is not attached to pc using "mass storage share" to pc.
Run OpenRecovery app and "install Recovery".
Press Boot recovery
restore the backup "stock22xxxx"
wipe / factory reset in OpenRecovery
reboot
Issues reported by users in v1.2a:
- Radio FM volume cannot change.
- MediaGallery does not do videoplayback
Issues reported by users in v1.0:
- Radio FM volume cannot change.
- Sync account option for facebook / Twitter is not added in settings when account is configured.
- Camera language not going to change (its korean app, so not support for other langs)
- LEDS do work, its sensors that makes them go off/on (no need to report this anymore)
STATEMENT:
Please don't keep asking the following question directed to me, public or via PM;
- Can you include language XXXXXXXX .
Answer: NO
- Can you teach me how to do custom roms
Answer: NO
- will you include RTL for hebrew
Answer: NO
- will you make other roms like cyanogen,htc etc..
Answer: NO
for new users unable to write in public forums, i cannot answer all your PM's personally, as that gets to be a quite a few per day and many monthly...i am not a support central for xt720 community..i simply don't have that kind of time available.
Dexter_nlb said:
if i press camera button here (1-2 sec) it opens?
media button (the small one becide the cam button?) ? yes i see its not doing any action
from what i read now, the known accelerator driver issue + led,hdmi is 2 majors, im not sure about other issues becides the extra languages which for some seem to cause issue..
the way the launcher works is a matter of taste (seeing like 20+ android devices)
- if you're coming from stock 2.1 there is differences and more functions, but if you tweaked alot maybe less features are here, like dalvik.
- rotation is a problem if you plan alot of games with acc. functionality..
- I personally dont experience problems, except the buttons which personally i would love to fix now..
I think overall there is a positive feel about the first working release.
Click to expand...
Click to collapse
I am still unable to sync with facebook contacts, anyone else?
-->settings ---> accounts add the facebook account successfully but then not in the accounts list and then contacts in phone do not sync.
Dexter_nlb said:
It seems that many not being experienced users, still try to install and here is the instruction for installing the rom.
Install instructions (based on korean sbf):
1. Install korean sbf (STSKT_N_79.33.50R) using RSDLite ( link here )
- boot your xt720 into bootloader (press power up while holding VOL+ + and shutter button during bootup)
- when RSDLite application on pc says "connected" , your ready to flash
- select the SBF
- press start
2a. Set language to english, set usb mode into Charge Only and USB debugging on in the Settings->Apllications->Development menu.
2b. root it (using SuperOneClick) - ( link here )
3. install OpenRecovery , follow instructions on ( http://bit.ly/gIPoXo ) files included (OpenRecovery & OpenRecovery.zip )
5. copy the folder "nandroid" to root directory of your sdcard.
6. boot into OpenRecovery (adb shell reboot openrecovery)
7. restore the backup "stock22" in openrecovery
8. wipe / factory reset in OpenRecovery
9. reboot
Download here
APK for easy installation and rebooting into OpenRecovery is in the works (based on previous CWM recovery app)
Click to expand...
Click to collapse
Added a rule for people who do not know how to use SuperOneClick
hellmonger said:
I am still unable to sync with facebook contacts, anyone else?
-->settings ---> accounts add the facebook account successfully but then not in the accounts list and then contacts in phone do not sync.
Click to expand...
Click to collapse
deleted.. i misunderstood the q here
hi there ! is it the final version of 2.2 or still in testing process?
nice job and thank you all...
FM RADIO also missing.....
@Dexter, thank you for contacts.apk. But how to install it? After replace in /system/app it's says - It's not installed, and when i try to install it - it says: I can't be installed.
For more issues: how about light sensor, that detects when you speak on your phone?
On 2.1 when you speak touchscreen goes off and you cant press it errorly.
Thank you very much.
FM RADIO also missing.....
Click to expand...
Click to collapse
That from 2.1
Facebook account missing.
Dexter_nlb said:
deleted.. i misunderstood the q here
Click to expand...
Click to collapse
After full flash and all instructions followed corectly i can boot into 2.2 without any problems.
i set up my account with google, go to the market, download "facebook for android" install is succesfull, i then go to ==> settings menu ==> Accounts menu, add account, choose facebook, am successfull at login in to facebook, return to accounts menu = Facebook account is not there.
And my phone contacts do not sync with facebook.
Thank you
And my phone contacts do not sync with facebook.
Click to expand...
Click to collapse
Did you set your FB freinds to sync in the FB app?
joe206hdi said:
Just flashed korean sbf ... maybe due to i´d used launcherpro in stock rom i can´t get into the rom background and apps are still there in korean rom.
going back to european rom and do a wipe/reset before flashing again the korean one...
later more
@dexter can´t we use universal androot instead of super one click
Click to expand...
Click to collapse
finally fixed it
1.flashed again german stock rom sbf file
2. do a factory reset in stock recovery
3. flash korean sbf file while reboot unplug the usb - when rsd lite shows massage "reboot manualy" - phone is still in reboot ( when i don´t do this it won´t work ?!?!
4. go on with dexters xt720-2.zip nandroid procedure
@dexter unversalandroot won´t work - just tested before superoneclick - adb install worked fine but no root....
-------
bugs
camera options are still in english - i´m on german
more within tomorrow
Joe - thanks great work
anyone else get a Installation error Unknown reason -18 when trying to install battle bears. i loved that game. worked on 2.1 even tho it said it didnt
3rdstring said:
Did you set your FB freinds to sync in the FB app?
Click to expand...
Click to collapse
Is yours working?
Where are those settings please? not in the accounts menu cause facebook is not there, i am able to add it from that menu but then it disapeares, when i clic add again facebook option is availible but just clics to nowhere and returns to the add account page....
smurfb said:
I been following this thread, very intresting! I thought, would it not be possible to use the kernel from XT720 (2.1), beause its the same kernel version? Or is too much changed?
Click to expand...
Click to collapse
ok, i went back once more and flashed just 2.1 kernels from uk rom, and indeed all sensors work now.. but,but,but... no 3D accelerator is currently activated, so screen lags really alot..
but yes, with that kernel it still boot up fine, with a few changes.
edit: update - ITS WORKING!!! running with 2.1 uk release kernel , its working now, all sensors activated..
Where are those settings please? not in the accounts menu cause facebook is not there, i am able to add it from that menu but then it disapeares, when i clic add again facebook option is availible but just clics to nowhere and returns to the add account page....
Click to expand...
Click to collapse
In the facebook app if you tap on "Facebook" at the top you go to the page to navigate to news feeds, friends, etc. If you hit your options button there there is a settings screen that includes preferences for how contacts are sync'd.
HTH
3rdstring said:
In the facebook app if you tap on "Facebook" at the top you go to the page to navigate to news feeds, friends, etc. If you hit your options button there there is a settings screen that includes preferences for how contacts are sync'd.
HTH
Click to expand...
Click to collapse
Yes i saw those settings, unfortunately they have no effect or bearing on the accounts.
I believe this is a bug, yet no one has confirmed or denied being able to reproduce it.
All sensors activated!!
I think smurfb deserve a little thanks, for pushing the request/idea just to try loading the old uk kernel once more, so i did and this time i fixed the problems with loading the old kernel and lib/bin required, its not much and most (2.2) korean state is kept intact..
ill do some testing after the new nandroid backup and start uploading v1.0
Dexter_nlb said:
I think smurfb deserve a little thanks, for pushing the request/idea just to try loading the old uk kernel once more, so i did and this time i fixed the problems with loading the old kernel and lib/bin required, its not much and most (2.2) korean state is kept intact..
ill do some testing after the new nandroid backup and start uploading v1.0
Click to expand...
Click to collapse
does that mean u activated the 3d accelerator. and would replacing the settings.apk from 2.2 from motoroi enable hdmi since the settings arnt even there anymore in this version the hdmi libs and everything is still there jus no hdmi.
khalpowers said:
other way u can install terminal su on your phone after flash to froyo..then u can su from there...
Click to expand...
Click to collapse
IT WORKED!!!!!!!!!!!!!!! THANK YOU SO MUCH!!!!!!!!!!!
AND DEXTER!!!!!!!!! THANK YOU!!!!!!!!!!! You're amazing.
Ill be up to any testing you guys need me to do
easye420 said:
does that mean u activated the 3d accelerator. and would replacing the settings.apk from 2.2 from motoroi enable hdmi since the settings arnt even there anymore in this version the hdmi libs and everything is still there jus no hdmi.
Click to expand...
Click to collapse
yes, 3d is fully functional now. I dont think it will work, but i will find a way to add the functionality..
the korean rom has only english, which im sure not many appreciate, although camera as one is used from that rom so only english is enabled.
but i will for sure try and get HDMI working..
I got FMRadio app added, does it help?
Thank you so much for making this, Dexter. We are hungry of froyo, asking for more. But you deserve to take a break
which languages does it have?
I will install it soon. can someone upload a video of it?
I am on stock marshmallow, rooted.
My phone is unlocking with Swipe right now and i would like to set up a pattern/password, but I can't access "Screen lock type" because it requires me to enter a password. WHAT PASSWORD? It says "enter current password"......i have no clue...
please help me out with this problem...
PS:
I have no encription
I have no SD card
I have no Device Administrators on
"Clear credentials(Remove all certificates)" option is GREYED OUT
I have no VPN accounts
Thanks!
simple. just download some 3rd party lockscreen apps if you dont want to factory reset your phone just to set up a password
note: i still suggest not to use 3rd party lockscreen apps since most of them are bloat. but if you dont want to reset your phone, this is the only choice
Well hell yeah..i dont wanna install a 3rd party app for lockscreen
So you're telling me that the only reasonable solution is to flash stock again?
Damn, i hate flashing stock because it only works and wont give me a bootloop if i follow these steps: 1. Reflash 5.1.1 first // 2. Flash 6.0.1 ....... flashing 6.0.1 1st will give me bootloop
Ok, so i would suggest you to go in twrp mode(if you have one), then mount the system/go to twrp's file manager/ data/system find :
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
and delete them, reboot, set up the lockscreen. Not sure if it will work for you , though it worked for me.
Ok. Thanks
So i tried your method. I only found the "locksettings" files. I deleted the files.
Now i can enter the menu to select my lockscreen method, BUT it seems none of the options are effective. I set a pattern/password/pin but my lockscreen is still on swipe....
Any idea?
PS: maybe i might have deleted some necessary files/apks when i debloated my phone. my phone is very light now . I only have a few necessary apps
Lawr3nce said:
Ok. Thanks
So i tried your method. I only found the "locksettings" files. I deleted the files.
Now i can enter the menu to select my lockscreen method, BUT it seems none of the options are effective. I set a pattern/password/pin but my lockscreen is still on swipe....
Any idea?
PS: maybe i might have deleted some necessary files/apks when i debloated my phone. my phone is very light now . I only have a few necessary apps
Click to expand...
Click to collapse
I missed a word, that's why you didn't find the other files, the right name should be 'gesture.password.key' and 'gesture.pattern.key' , try deleting these 2 followed by the other 3 you deleted earlier.
Since this method didn't work you either deleted a necessary file manually, or the script you used for debloating deleted that file.
No other idea though, but you might trying flashing the system.img file using odin( if the trick above doesn't do the job, or if you are too lazy to flash the whole firmware) ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to the NitrogenOS Q&A Megathread. Here you can find answers for the most popular problems and questions about NitrogenOS. I started this thread, so that new users don't repeatedly ask the same questions multiple times. While I am fairly new to coding in Java, I can definitely say I know a lot about Android phones and NitrogenOS, but you'll have to trust me on that. If you need any more help, you can even PM me and I'll try to reply as soon as I can.
You can find the original NitrogenOS thread here.
ROM info
Developer: xyyx
Latest Android version: 8.1 Oreo
NOS Download (latest): https://sourceforge.net/projects/nitrogen-project/files/kenzo/kenzo_test/8.1/
Bugs and updates
- A (very) small amount of users reported Google Dialer not working properly while installed through OpenGapps or the Play Store, you can still use stock dialer
1. Test or stable?!?!
Test in this case doesn't mean less stable. xyyx named the two versions a little confusingly.
Test means Oreo (Android 8.0 and 8.1) and Stable means Nougat (Android 7.1.2).
So let's make this a little less confusing:
Oreo (8.0) builds -> Download from here
Oreo (8.1) builds -> Download from here
Nougat (7.1.2) builds -> Download from here
2. Youtube PiP (Picture in Picture mode)
Google has patched PiP a long time ago, so it doesn't work with the latest Youtube releases. The last official release working with PiP is 12.34.55, which you can download from ApkMirror.
My preferred option however is iYTBP (injected YouTube Background Playback), a modified version of Youtube, but it gets a little confusing as there are multiple options.
You can download it from this thread.
Now the tricky part - choosing the right version. I always prefer the Vanced version, which can be found in the 2nd post. Again you have multiple options, but I will not go through all of them since they are explained pretty good in the post itself. While iYTBP enables PiP, it also blocks ads and adds a lot of useful settings and new updates come very frequently. There are multiple installation methods, but I prefer the Magisk one, since it offers options like detaching the Youtube app from Play Store. What this means is, that you don't have to disable auto-updates and it will not bug you to constantly update it.
You can try these methods:
Magisk Module (Easiest):
1. Open Magisk Manager
2. Go to Downloads
3. In the search bar type "Youtube", you should see two results
4. Choose either the normal or the black theme (I personally prefer the black one)
5. Press the download arrow and then "Install"
6. Wait for a while (it's a big package to download and unpack)
7. Reboot
This is by far the easiest option and the module is updated fairly often.
Manual:
1. Delete or uninstall any previous release of Youtube. If you installed it as a system app, disable it or delete the /system/app/YouTube folder. If you had to delete the folder, reboot.
2. Download the Youtube apk
3. Make a folder called YouTube (watch the caps!)
4. Move the apk to this folder and rename it as YouTube (again with the caps)
5. Copy/move the folder to /system/app (The directory should look like this: /system/app/YouTube/YouTube.apk)
6. Reboot
Magisk (manual):
1. Download the Youtube apk, the iYTBP universal installer and the use_this_settings.sh file. Check that they are in the downloads folder.
2. Edit the use_this_settings.sh file if you want. Since we're installing from Magisk, you'll need to set MAGINSTALL to YES (MAGINSTALL="YES"). I usually also enable detach (DETACH="YES"). This will make the Play Store think Youtube isn't installed and it will not bug you for updates.
3. Open Magisk Manager, go to Modules and press the + button. Now select the universal installer zip and flash it in Magisk.
4. Reboot
Recovery method:
Same as for Magisk, but MAGINSTALL is set to NO (MAGINSTALL="NO"). In case you didn't read the Magisk method, here is the recovery method...
1. Download the Youtube apk, the iYTBP universal installer and the use_this_settings.sh file. Check that they are in the downloads folder.
2. Edit the use_this_settings.sh file if you want. I usually enable detach (DETACH="YES"). This will make the Play Store think Youtube isn't installed and it will not bug you for updates.
3. Reboot to recovery, go to Install and choose the universal installer zip, flash it.
4. Reboot
If you open a video in fullscreen mode and press the home button, it should open it in PiP mode. If you want to change some advanced settings, you can go to your Account (the round icon with your profile picture) -> Settings -> iYTBP Settings
3. Goodix & FPC - What are they
Goodix and FPC are two different types of fingerprint sensors (or rather sensor manufacturers). They both work in Android 8.1 builds. Custom kernels or mods may break the fingerprint sensor functionality.
4. Rooting
tl;dr: rooting NitrogenOS is the same as rooting any other custom rom, just flash Magisk, SuperSU, phh's superuser or anything else.
Now for the extended version.
Magisk:
Magisk is a great open-source root manager, developed by topjohnwu. It features a feature rich app, but most people prefer it because of it's "modules", packages which can do a bunch of things, from installing apps like Viper4AndroidFX or Dolby Atmos, to modifying system settings, like the volume steps increase. Magisk also features an option called "Magisk Hide", which can bypass Android's SafetyNet.
Check out the Magisk thread.
You can directly download the latest version of Magisk from https://tiny.cc/latestmagisk
SuperSU:
SuperSU is an alternative root manager. It used to be developed by Chainfire, but has recently been purchased by another company. I still prefer Magisk, but SuperSU is a great alternative for new users. My problem with it though is, that it is not open-source and the new buyer is pretty secretive so I don't really trust them.
Check out the SuperSU website for the download link.
phh's SuperUser:
Another open-source root manager, but the great thing about this one is, that it's very minimalistic and very small in size.
Check out the SuperUser thread and phh's Build Bot.
5. Google Apps (gapps)
Google apps are a vital part of custom roms. You might not know this, but AOSP and CM based roms are made from Google source code. Google actually makes Android open-source, but the Play Store and other Google apps are not. That's why roms like NitrogenOS do not come with the Play Store preinstalled. That is where Open Gapps come in. They are prepackaged apps, updated almost daily. They come in various sizes and versions, but they can all be flashed in TWRP like a normal zip file.
Platform: arm/arm64/x86/x86_64 - RN3 has an arm64 processor (Think of it as a 64-bit CPU for phones)
Android: 8.0/7.1/7.0... - This is the android version, NOS is Oreo based so choose 8.0 (Or 7.1 for Nougat) [Check below for OpenGapps 8.1]
Variant: This is where it gets complicated. There are a LOT of versions to choose from. For more in-depth resources check the OpenGapps' package comparison.
But OpenGapps are a lot more customisable, to the level where you can choose individual apps you want installed. The easiest way to do this, is to flash the Aroma package, which enables you to choose exactly which packages you want installed. Another option is to configure any of the selected packages using a gapps-config.txt file. You can learn more about that in the Advanced Features and Options section.
You can download daily builds for any Android version from https://opengapps.org/
6. TWRP (Recovery)
A recovery is a partition, used to flash files like ROMs, gapps and any other modifications. You do (in most cases) need an unlocked bootloader to use it. Unlocking your bootloader will not be described on this thread, as there are a lot of resources for our device.
Official TWRP - This is the official TWRP (Team Win Recovery Project) for our device
You can find the latest updates for TWRP on their website.
Red Wolf - This is a modified version of TWRP, my absolute favourite because of it's custom features.
Flashing TWRP:
If you don't have a custom recovery installed and you have unlocked your bootloader, then download the latest version of your preferred recovery and follow these steps:
1. Download Minimal ADB and Fastboot on Windows, or use sudo apt install android-tools-adb android-tools-fastboot if you're on Linux.
2. Enable USB Debugging (Settings -> About phone -> Press "Build number" 7 times to enable Developer options). You should find the Developer options in settings above "About Device". Find USB Debugging and enable it.
3. Connect your PC to the phone via a cable. Open Minimal ADB and Fastboot (which will open CMD) or Terminal on Linux and type this (same for both OSs): adb devices. Select "Always allow on this computer" and confirm access on your phone.
4. Reboot your phone to fastboot/bootloader (By holding Power and Vol-, releasing the power button after a vibration and holding the Vol- button until you see the Xiaomi mascot).
5. Type (In CMD/Terminal): fastboot devices, to confirm if the phone has been recognised, then fastboot flash recovery /path/to/recovery.img
6. After it has succesfully finished, remove the cable and reboot directly to recovery (Power and Vol+, release power after vibration, but keep holding the Vol+ button until you see the TWRP or RedWolf logo).
If you do already have a custom recovery installed and just want to update it, flash the .img or .zip file in your already installed recovery and select "Reboot to recovery".
7. NOS asks me for a password after flashing?!!?!?
This is actually not NitrogenOS's fault, it's a byproduct of your previous rom, most often MIUI. What this means is, that your internal storage is encrypted and the only way to fix this, is to backup everything on your internal storage, which you can do by connecting your phone to your pc while in recovery. You should be able to access the phone's storage and move the files from there. If you for some reason can't do that, you can still put in an sdcard and copy the files to it in TWRP. Bottom line, backup the files and then go to "Wipe" and find the "Format data" button. You might see a "wipe data" button, but this is not the same. When you "wipe data" you are wiping your system, cache, dalvik cache and data partitions, but formatting data will format your internal partition as well and thus remove the encryption.
You can finally reflash NOS and gapps or whatever other modification you want.
8. Firmwares
Check out this link to download the latest firmware for our device.
What is firmware? - It's what connects hardware to software (don't confuse it with a kernel). It's what, for example, makes the camera work.
Do I really need firmware - Yes (but it's already installed, even after completely wiping the stock rom, since it's on separate partitions).
Do I need the most up-to-date firmware - Actually no, the only difference you will notice is in the signal and WiFi strength. If yours are good enough, you don't need to update, otherwise feel free to download the newest version from the link above.
What is emmc_appsboot.mbn? - It's a bootloader update. Bootloader or fastboot is the partition in which you have unlocked your bootloader and flashed the recovery. If you have officially unlocked your bootloader, then you can flash firmware with emmc_appsboot.mbn, but if you have unofficially unlocked your bootloader, do not flash these files as they will re-lock it. But you can still flash the version without emmc_appsboot.mbn.
Kenzo? Kate? - Kate devices are the same as kenzo ones but are a little bigger.
Some comparisons:
Kenzo
Size: 150 * 76 * 6.85 mm
Weight: 164g
Kate
Size: 152 * 76 * 6.85 mm
Weight: 167g
Model numbers:
Kenzo: 2015116
Kate: 2015161
Kate devices are 32/3 GB, and some kenzo devices are as well (some are 16/2 GB), not really sure about this part.
Global stable or developer? - Most people use developer roms, but again, this is not the actual ROM, just the firmware extracted from the rom, it doesn't really matter which one you choose.
When do I need to flash firmware? - If you're coming from MIUI8 (or 9), then you probably have the newest firmware. In this case you don't need to flash it, because MIUI roms already have firmware included in the update. If you're coming from a CM or AOSP based rom you also probably don't have to flash it, but I suggest you update it just in case. If your signal is good enough though, there really is no need.
9. How to flash the rom
Flashing is pretty straight forward. Just go to the Install section of TWRP and flash it like any normal zip, nothing special.
If you're coming from MIUI, then the full procedure is this:
1. Unlock your bootloader (google it, useless explaining it here)
2. Flash TWRP
3. Make a full device backup (Nandroid backup)
4. Copy or move all important files from the internal storage to an sdcard or your pc
5. Format data, or in other words, wipe EVERYTHING (excluding external storage) - This will delete all your photos and anything else in internal storage
6. Flash the latest NOS "test" build (Oreo)
7. Flash gapps (I recommend opengapps.org, check above)
8. Reboot to system
10. OTA?
What is OTA? - OTA means Over The Air (Update)
Does NOS have OTA? - Actually yes and no, newer updates (from March 2018 on) do have partial OTA (it does check for updates and notify you, while also giving a direct download link to SourceForge, but you will have to manually flash every update in your recovery.
What about incremental updates? - Sorry, but no. You'll have to download full packages every time. If you have a bandwidth cap then just download an update every week or two, you can check the changelog to see if you think it's worth updating to.
11. Google Camera
If you're having problems with the official Google Camera or just want some added features then look no further than modded camera apps. Check out this thread by emime12, it's very frequently updated and features a lot of different camera mods, including Google Camera, MIUI Camera, MOTO Camera and many more.
Recommended settings:
3x3 Grid - For better photos
I usually disable "Save location" and "Camera sounds"
Model: Pixel XL (corr) - default
Config camera HDR+: NEXUS 6
HDR+ parameters: Default
Panorama resolution: High
Advanced: Enable both
Experimental: I usually leave this disabled but it's your choice.
Back camera video resolution: UHD 4K (30 fps)
In case your camera doesn't work check if you have these two files and delete them:
/System/framework/com.google.android.camera.experimental2016.jar
and
/System/etc/permissions/com.google.android.camera.experimental2016.xml
Credits go to: @emime12 and Njaiker.
You can find more info about problems and updates on emime12's thread.
Settings may differ a lot, so check emime12's recommended or just test until you find ones that work for you
12. RAM Management - Low free RAM
Android's RAM (Read Only Memory) management doesn't work like Windows'. Android manages RAM very well, "Free RAM is wasted RAM" is a very common expression on XDA. Android loads the first couple of apps into the RAM and priorities the open one. More used ram means more apps loaded in ram which means faster load times. Don't worry about it too much and just enjoy the fast loading speeds.
13. VoLTE?
VoLTE should work on Android 8.1. Magisk, Viper or any other mods may break it.
14. Custom kernels
While there are a lot of custom kernels, I suggest you stick with the stock one, as it is made specifically for NOS and thus it is the most stable. If you still want a custom kernel, you can try Radon or Agni but they might break VoLTE or your fingerprint sensor.
Agni XDA Thread - By psndna88
Radon XDA Thread - By Umang96
15. Daily driver or not?
Yes, NitrogenOS Oreo is very stable, definitely enough for a daily driver. It is the best Oreo rom for our device (in my opinion), as it offers just the right amount of customization and stability.
15. GPS
Some users have reported low accuracy, but you should be fine if you turn on High Accuracy mode and/or install Faster GPS.
Update: In recent updates GPS shouldn't be a problem anymore as xyyx has fixed it, but some users have still reported low accuracy.
16. Viper4Android FX
(There may be other ways, but I haven't tested them yet so I can't confirm if they work) By far the easiest way to install Viper4Android FX is using Magisk. There is Magisk module called ViPER4Android FX Materialized. Download and install that module from the Magisk repo, choose your preferred installation option (By pressing Vol+ or Vol- to select which version you want installed and if you want it materialized - for newest materialized version press Vol+ 2 times) and finally reboot. Try playing some music and open the Viper app. Turn on the "Master Power" switch and the "Playback Gain Control" (the easiest way to tell if it worked). If after a little time the volume increases, it means that Viper4Android FX works. If not, press the three dots and choose "Exit" (without turning off the master power or gain control). Now open the app again and it should work. You can also check that in the side menu under "Driver status", if it's enabled and processing, then everything works.
You may or may not have to exit and re-enter the app after reboot to enable processing (in my case I had to).
I would show you my recommended settings (as requested), but to be honest I only use:
Headset
Viper Bass (Natural bass, 40 HZ frequency, 8 dB)
Viper Clarity (Natural, 6 dB)
Sometimes I use Field surround with default settings
Phone speakers
eXtra loud (Slight, 4x max gain, -1.9 dB max output)
Bluetooth device
Playback gain control (Moderate, 6x max gain, -1.9 dB max output)
If I'm at a party with my bluetooth speaker I pump it up to Extreme and 8x max gain
Viper Bass (Natural, 40 HZ frequency, 8 dB), 17 dB for parties
Viper Clarity (Natural, 3.5 dB)
I don't use equalizers or if I do, they are song-specific. I also don't USB/Dock, so I can't recommend anything there.
Of course these settings can vary depending on the song, so choose those, which you like the most and don't stick with just those I chose, try all the functions to see which you prefer.
17. AdAway (Root)
AdAway is a great open-source root ad blocker, which can automatically download and update sources and works by adding those to the hosts file. It work well on the internet, but also inside apps (most of the time).
Check out the official AdAway website. You can also download it from F-Droid.
Adaway v3.2 (60) (direct download link)
Adding custom host sources:
Go to "Host sources" and add your own sources or check out these: AdAway's host sources
Be careful when adding all of them, since some can block legitimate links like goo.gl.
AdAway also offers an option to scan for Adware, which can be found under "Scan for adware". This will bring up a new window, press "Start scanning". If you don't need/want the mentioned apps you can uninstall them, but AdAway can't block their ads.
You can also check out my recommended settings:
wow,really appreciated that sir., it is very helpful specially for those who wanted to try, flashing rom or any mods on their device like me. thanks and keep up the good work sir God bless!
i think i can add up little bit here.
1) u r on miui & u want to flash nitrogen so u go to recovery and backup ur current rom in case if u dont like nitrogen u can restore back to miui with all ur setting & app. now assume u r on nitrogen, after 4-5 days u dont like nitroge & u decided to come back to miui, so u go to recovery and restore yr backup that u have taken earlier. after success booting the screen with pin or password will appear. so u would enter/guess any previous password, pin u used earlier but it will not open. here the real problem come. i have also faced same issue & got upset searching endless solution on google . u will get mad on u. security bypass will also not work. after spending endless hour i come with solution. download aroma zip search on net. flash it through recovery this will help u to get in system its ike file manager. then head to data, system and delete all file u see below
locksettings.db, locksettings.db-shm, locksettings.db-wal, gatekeeper.password.key, gatekeeper.pattern.key
and then restart, yr problem would be solve.
2) nitrogen os does not support video calling via jio. none custom rom other then then miui support.
3)xposed is not available for oreo.
4)i have used nitrogen oreo for about 2 weeks it is stable but not as miui. some time r net would not work, jio call drop, lagging u have to restart on every time u faced problem. i suggest that wait for some time to roll out nought port for kenzo with zero bug & this will happen soon.
saifuk said:
i think i can add up little bit here.
1) u r on miui & u want to flash nitrogen so u go to recovery and backup ur current rom in case if u dont like nitrogen u can restore back to miui with all ur setting & app. now assume u r on nitrogen, after 4-5 days u dont like nitroge & u decided to come back to miui, so u go to recovery and restore yr backup that u have taken earlier. after success booting the screen with pin or password will appear. so u would enter/guess any previous password, pin u used earlier but it will not open. here the real problem come. i have also faced same issue & got upset searching endless solution on google . u will get mad on u. security bypass will also not work. after spending endless hour i come with solution. download aroma zip search on net. flash it through recovery this will help u to get in system its ike file manager. then head to data, system and delete all file u see below
locksettings.db, locksettings.db-shm, locksettings.db-wal, gatekeeper.password.key, gatekeeper.pattern.key
and then restart, yr problem would be solve.
2) nitrogen os does not support video calling via jio. none custom rom other then then miui support.
3)xposed is not available for oreo.
4)i have used nitrogen oreo for about 2 weeks it is stable but not as miui. some time r net would not work, jio call drop, lagging u have to restart on every time u faced problem. i suggest that wait for some time to roll out nought port for kenzo with zero bug & this will happen soon.
Click to expand...
Click to collapse
Thanks for the tip, will update the thread.
@JustMeErazem volte on 2nd sim works well. I myself use it. After flashing magisk just v need to hide root from all system apps to make sure volte works flawless even after reboot. Plz edit it in the description. I hav been using nos since many time so with experience i am giving my feedback. Thanks?
@saifuk what kind of nougat port u are expecting of ?
Aditya1011 said:
@JustMeErazem volte on 2nd sim works well. I myself use it. After flashing magisk just v need to hide root from all system apps to make sure volte works flawless even after reboot. Plz edit it in the description. I hav been using nos since many time so with experience i am giving my feedback. Thanks
Click to expand...
Click to collapse
I haven't rooted my phone, VoLTE still not working.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
@justmerazem Change VoLTE point again to previous. I installed NOS on mine & my other two friends' phone. They've not used magisk or superSU nor me. But VoLTE doesn't work on 2nd Sim for us.
AtomR said:
I haven't rooted my phone, VoLTE still not working.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
@justmerazem Change VoLTE point again to previous. I installed NOS on mine & my other two friends' phone. They've not used magisk or superSU nor me. But VoLTE doesn't work on 2nd Sim for us.
Click to expand...
Click to collapse
Flash latest firmware of developer rom. And volte is sure shot working.
Aditya1011 said:
Flash latest firmware of developer rom. And volte is sure shot working.
Click to expand...
Click to collapse
Mate, I'm already on 7.9.22 firmware. Lots of people are reporting it. Yours is working, must be some kind of random.
@Aditya1011 Mate, what happened? No reply? Huh. Latest firmware. No magisk, no any kind of root. No sound mod. Still Volte not working on 2nd Sim on 3 different Kenzos.
@JustMeErazem Please include in your post that VoLTE is indeed buggy.
how to install via dualboot patcher as secondary rom?
AtomR said:
@Aditya1011 Mate, what happened? No reply? Huh. Latest firmware. No magisk, no any kind of root. No sound mod. Still Volte not working on 2nd Sim on 3 different Kenzos.
@JustMeErazem Please include in your post that VoLTE is indeed buggy.
Click to expand...
Click to collapse
Idk bro y that happening to u. Flash miui EU rom n thn the nos rom. Mayb that should work.... Bcuz I had done that for the 1st time whn my volte wasn't working at any cost. Best of luck.
smjhh said:
how to install via dualboot patcher as secondary rom?
Click to expand...
Click to collapse
I don't think dual boot patcher supports oreo roms. Try asking on their thread to see if it does.
Google HDR camera 5 or 5.1 work with this ROM??
sagar13190 said:
Google HDR camera 5 or 5.1 work with this ROM??
Click to expand...
Click to collapse
Read op!
I tried google HDR camera v5 n v5.1 on lineage Oreo, MAOSP Oreo nitrogen Oreo ROM bt its not working...bt in ROM based on nogut 7.1.2 its work great
sagar13190 said:
I tried google HDR camera v5 n v5.1 on lineage Oreo, MAOSP Oreo nitrogen Oreo ROM bt its not working...bt in ROM based on nogut 7.1.2 its work great
Click to expand...
Click to collapse
It works for many users. Did you flash my zip or install an apk?
Sim card detection issue
Sometimes nitrogen os Oreo does not detect sim cards after reboot so I changed ROM and installed aosp extended. I know that Xyyx has already mentioned this as bug. Due to this bug it is not daily driver. Hope xyyx will fix this as soon as possible. If you have solution, please share it.
dhavalmehta said:
Sometimes nitrogen os Oreo does not detect sim cards after reboot so I changed ROM and installed aosp extended. I know that Xyyx has already mentioned this as bug. Due to this bug it is not daily driver. Hope xyyx will fix this as soon as possible. If you have solution, please share it.
Click to expand...
Click to collapse
Dude, it's really not a big problem, it detects it like 95% of the time. Just reboot and you're done. Or wait about 2 min and it should detect it. You could also just remove the sim and reinsert it. But since the latest few updates for me it gets detected 100% of the time. So update to 28/10/2017 build and you should be fine.
@JustMeErazem You're giving flase info. to others saying that VoLTE works on both sim. Actually, it works only on first sim. Tried, tested on 3 different Kenzo's. Clean flashed.
Conclusion: VoLTE doesn't work on 2nd sim.
What's this?
First of all, I'm not the original developer.
He post it on other Chinese forum, and I am just to ask for his permission and post it here.
All credits to Coolapk user: Tutoo.
This is an unofficial build of Pixel Experience Pie for Oneplus 5T (dumpling).
The original is for Oneplus5, you can find it here : Click here
The dev make a port version of this
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint
WiFi
Bluetooth
Camera (but same as other Pie ROM, a little laggy in third apps)
Flashlight
Camcorder
Sound / vibration
GPS
AOD
Hotspot
NFC
VPN
And device specific addition (same as OP5 thread)
Known issues:
Permissive
or other issue same as OP5
Fingerprint gesture to view notification also not working
But you can try the solution provide by @Sabissimo at #16
Although that didn't work for me, some report they success, still looking into the problem
If that work for you, don't forget to give him a thank
If you find any bugs, you can PM me or leave comments below, I'll reported it to original dev
Instructions :
First, backup your data to PC or laptop
Second, you HAVE TO wipe data,system,cache AND INTERNAL STORAGE (some reported that it didnt boot if no wipe internal storage)
Third, flash the ROM and No verity zip (In my case, I use v3, but it seems with no problem)
Now you can boot up your device, it'll boot up TWO TIMES, and this is normal
CAUTION !!!
Version1 already include Gapps,Magisk (16.7), firmware, gcam and Redflare kernel (1.13 build)
So it is unnecessary to flash other zips
But in Version2, it didn't have firmware, but with Magisk (17.1) and Redflare kernel (1.16 build)
you guys need to take notice of this
Downloads:
Because original was on Baidu Cloud, and it may block some countries IP (Example: Taiwan)
So I upload it to Google Drive
If it is needed to upload to AFH or other cloud, just PM me, I'll upload it when I'm free
Here is the GD link:Version1
Version2
Credits:
Coolapk user "Tutoo" for his awesome work
and XDA user @bhageerathreddyy for help testing
Because of the forum rule, TG group link are not allow to post publicly here.
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.4.152, RedFlare EAS kernel
ROM Firmware Required: TWRP, Unlocked bootloader
Based On: AOSP
Version 2 changelog:
VoLTE reset on reboot Fixed
Proximity Sensor Fixed for FP and Gestures (Now phone won't start dialling numbers when in your pocket )
Added more Off screen Gestures and fixed V gesture
Improved OMNI slider switch
RedFlare kernel 1.16+
Linux 4.4.154
(Well... I copied these from original 5's thread. Don't forget to thank him for fix !!)
thanks
Thanks
Sent from my ONEPLUS A5010 using Tapatalk
This was much faster than expected for this rom, been swapping between this and OOS, will have to test this tonight and Pie for the first time, ty for fast release.
HI, just flashed this. Looks and feels good but the fingerprint swipe gesture doesn't seem to work properly, It treats it like arrow keys and navigates around the UI.
rijads said:
This was much faster than expected for this rom, been swapping between this and OOS, will have to test this tonight and Pie for the first time, ty for fast release.
Click to expand...
Click to collapse
Can u tell me dose it includes the adaptive battery and gcam ? And how are the animations ? And notification slider options
ROM is awesome! Adaptive battery, gcam, slider - all working
To make fingerprint gestures work, put this file in /system/usr/keylayout , and give it 755 permissions
https://drive.google.com/file/d/1Nhjs7YWulTHy-6d-AM1R1cLN_TfK-ieY/view?usp=sharing
MyStyle0714 said:
What's this?
First of all, I'm not the original developer.
He post it on other Chinese forum, and I am just to ask for his permission and post it here.
All credits to Coolapk user: Tutoo.
Click to expand...
Click to collapse
THREAD MOVED TO HOW-TO
Per the Device Forum Rules, all threads posted in the Development section must be your own work. ROM shares may be posted in the How-To section.
@Sabissimo how long does the boot took for you ? im on google bootanimation but nothing has happened since last 5 minutes ! can you also explain your installation process !
didn't help
Sabissimo said:
ROM is awesome! Adaptive battery, gcam, slider - all working
To make fingerprint gestures work, put this file in /system/usr/keylayout , and give it 755 permissions
https://drive.google.com/file/d/1Nhjs7YWulTHy-6d-AM1R1cLN_TfK-ieY/view?usp=sharing
Click to expand...
Click to collapse
i did what you wrote,
now swiping doesn't do anything
tids2k said:
@Sabissimo how long does the boot took for you ? im on google bootanimation but nothing has happened since last 5 minutes ! can you also explain your installation process !
Click to expand...
Click to collapse
First boot took about 1 min max. You have to be decrypted, flash rom, flash noverity (I flashed v3) - and you should be good.
---------- Post added at 11:06 AM ---------- Previous post was at 11:00 AM ----------
korm85 said:
i did what you wrote,
now swiping doesn't do anything
Click to expand...
Click to collapse
Well, it's definitely working for me tho, be sure to give it permissions.
Also, don't know if it matters, but I've searched for "swipe" in settings, and got in "Swipe fingerprints for notifications" menu, which is (weirldy) not available in "Gestures", there was no toggle there, tho, just instructions video. Maybe just entering that menu enabled that, try it out.
@Sabissimo did you update your firmware to 5.1.5 ? and have you installed vendor partition data ?
tids2k said:
@Sabissimo did you update your firmware to 5.1.5 ? and have you installed vendor partition data ?
Click to expand...
Click to collapse
I was on OB15, so whatever firmware it uses - I have it And had vendor of OB15, but I don't think that vendor matters, since this is not treble rom, and doesn't use /vendor, it uses /system/vendor
Sabissimo said:
Well, it's definitely working for me tho, be sure to give it permissions.
Also, don't know if it matters, but I've searched for "swipe" in settings, and got in "Swipe fingerprints for notifications" menu, which is (weirldy) not available in "Gestures", there was no toggle there, tho, just instructions video. Maybe just entering that menu enabled that, try it out.
Click to expand...
Click to collapse
Well... the dev said that the ROM doesnt have that function, but how can you enable ? I also follow your steps and give them permission then reboot again, but nothing happen.
Step-by-step of what I did:
1. Wiped everything except internal storage
2. Flashed ROM
3. Flashed no-verity v3
4. Rebooted, it rebooted twice, then started booting up with google animation
5. Noticed that fingerprint is working as cursor, went to settings, searched for "swipe", entered that menu, there's no toggle there
6. Pasted gf_input.kl in /system/usr/keylayout, gave it 755 permissions
7. Rebooted and everything is working!
Try doing it in the same sequence (First try to to enter swipe menu before pasting gf_input.kl, then paste it), maybe that did the trick.
Sabissimo said:
Step-by-step of what I did:
1. Wiped everything except internal storage
2. Flashed ROM
3. Flashed no-verity v3
4. Rebooted, it rebooted twice, then started booting up with google animation
5. Noticed that fingerprint is working as cursor, went to settings, searched for "swipe", entered that menu, there's no toggle there
6. Pasted gf_input.kl in /system/usr/keylayout, gave it 755 permissions
7. Rebooted and everything is working!
Try doing it in the same sequence (First try to to enter swipe menu before pasting gf_input.kl, then paste it), maybe that did the trick.
Click to expand...
Click to collapse
Confirm this was the exact process I followed and works like a charm. Just need a couple of days with it to test battery life.
just have one thing to say thankyou so much and this rom is just smooth
For anyone that wants to flash this ROM, don't worry about your firmware. This ROM's .zip file contains a firmware ALREADY so it will flash the necessary firmware itself!
Sabissimo said:
Step-by-step of what I did:
1. Wiped everything except internal storage
2. Flashed ROM
3. Flashed no-verity v3
4. Rebooted, it rebooted twice, then started booting up with google animation
5. Noticed that fingerprint is working as cursor, went to settings, searched for "swipe", entered that menu, there's no toggle there
6. Pasted gf_input.kl in /system/usr/keylayout, gave it 755 permissions
7. Rebooted and everything is working!
Try doing it in the same sequence (First try to to enter swipe menu before pasting gf_input.kl, then paste it), maybe that did the trick.
Click to expand...
Click to collapse
where is this gf_input.kl?? why should i do this for the pill gestures?
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 ?