All future discussion will happen in the Pixel 2 XL thread as the kernel is fully unified!
...
Reserved
I'm so subscribed
I'll be flashing this the second I get home. Used the kernel on my 6P and it was rock solid. Looking forward to getting it on my device!
I see you mention that the kernel is based on 4.4.97 but I am running the latest build (025) and kernel version says 4.4.56, but I guess it is still ok to install?
Also, have anyone tried to patch the boot image with Magik?
xda890 said:
I see you mention that the kernel is based on 4.4.97 but I am running the latest build (025) and kernel version says 4.4.56, but I guess it is still ok to install?
Also, have anyone tried to patch the boot image with Magik?
Click to expand...
Click to collapse
Were you flashing the boot image with fastboot? It should be 4.4.97.
Sent from my Pixel 2 XL using XDA Labs
nathanchance said:
Were you flashing the boot image with fastboot? It should be 4.4.97.
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I actually downloaded the full ROM from Google and used the boot image from the zip file and tried to patch the boot image using Magisk but that did not work. So I am checking other methods..
But strange that the version does not match...
---------- Post added at 11:08 PM ---------- Previous post was at 10:20 PM ----------
Found a newer version of Magisk Manager and patched your boot image and now I have root and running your kernel...
xda890 said:
I actually downloaded the full ROM from Google and used the boot image from the zip file and tried to patch the boot image using Magisk but that did not work. So I am checking other methods..
But strange that the version does not match...
---------- Post added at 11:08 PM ---------- Previous post was at 10:20 PM ----------
Found a newer version of Magisk Manager and patched your boot image and now I have root and running your kernel...
Click to expand...
Click to collapse
So you have to have the boot.img on your phone for magisk to patch it, then do you need to transfer that boot.img to your computer where you can use fastboot to flash it while in the bootloader?
530farm said:
So you have to have the boot.img on your phone for magisk to patch it, then do you need to transfer that boot.img to your computer where you can use fastboot to flash it while in the bootloader?
Click to expand...
Click to collapse
Yes, that's correct..
Patched with Magisk 14.4 from Pixel 2 XL thread and fastboot flashed on November 8.0 stock
All good, SafetyNet passed. I'll be testing for stability and report back.
Thanks Nathan!
The OP says:
Security and stability are paramount. Vulnerabilities are patched as soon as they are disclosed.
Click to expand...
Click to collapse
Does this mean, for example, that something like the Krack vulnerability would have been patched much sooner than with Google's montly security patch? Or is this kernel dependent on waiting for Google's monthly releases first?
cb474 said:
The OP says:
Does this mean, for example, that something like the Krack vulnerability would have been patched much sooner than with Google's montly security patch?
Click to expand...
Click to collapse
Yes
cb474 said:
Or is this kernel dependent on waiting for Google's monthly releases first?
Click to expand...
Click to collapse
No
cb474 said:
The OP says:
Does this mean, for example, that something like the Krack vulnerability would have been patched much sooner than with Google's montly security patch? Or is this kernel dependent on waiting for Google's monthly releases first?
Click to expand...
Click to collapse
As @Natakranta said, the fact I have kernel source means I am free to update literally whenever I want. So as soon as I see a fix for a vulnerability available, I will queue it up and release it with the next kernel.
Sent from my Pixel 2 XL using XDA Labs
@nathanchance Good to see you here
It's been stable for me and it's the end of the day for me usually my phone is dying or dead before I get to my car. And I am at 18% unlocking the doors now. ?
Wakelock control? I have installed exkm and was wondering if every known wakelocks in the app can be blocked without consequences? Or is there some that should not be blocked?
Sent from my Nexus 7 using Tapatalk
xda890 said:
Wakelock control? I have installed exkm and was wondering if every known wakelocks in the app can be blocked without consequences? Or is there some that should not be blocked?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I don't block any wakelocks by default on purpose; they shouldn't really be disabled because 1. they don't make that much of a difference and 2. they are usually needed for the device to function properly. But any of the ones that EXKM shows by default should be okay to disable.
Yes, I know they are needed but just thought I would try to disable those with most wakelocks and see if I noticed any difference..
Hi,
Thanks for coming in to support this device!
Was just wondering if it would be possible to add sound control, something like faux sound or boeffla sound or wodoo ( or the other ones around which increase the analog gain )
Thanks again!
Ash
Related
Hey everyone. currently uploading the latest Odin package fresh off Samsung's kitchen
N920AUCU2APB2
That is the build number. It is the same as Verizon's note 5 MM update.
I do not have the ATT note 5 to test this on so when the file is uploaded I will need someone to confirm for me. Thanks!
EDIT:
HERE IS THE LINK DOWNLOAD
PLEASE MAKE A BACKUP OF YOUR DATA. THIS WILL PROBABLY DELETE YOUR STUFF. YOU'VE BEEN WARNED
I'm game...
How do I use it?
Zefr said:
How do I use it?
Click to expand...
Click to collapse
Flash with odin 3.10.7
Zefr said:
How do I use it?
Click to expand...
Click to collapse
If you have to ask this, don't use it.
Flashing now...
---------- Post added at 05:22 PM ---------- Previous post was at 05:12 PM ----------
So... This is 5.1.1
Sunderwear said:
Flash with odin 3.10.7
Click to expand...
Click to collapse
Thank you, flashing as of now.
I downloaded it and noticed that the files have same size of 5.1.1 stock files
Russ77 said:
So... This is 5.1.1
Click to expand...
Click to collapse
Russ77 said:
[/COLOR]So... This is 5.1.1
Click to expand...
Click to collapse
Yeah I got the same results.
it's got the Mm build #, device status is official, and Knox counter is 0, but it's 5.1.1
Russ77 said:
it's got the Mm build #, device status is official, and Knox counter is 0, but it's 5.1.1
Click to expand...
Click to collapse
That's confusing,how can it have a mm build # and be 5.1.1 ?
have a look.
the MM beta is N920AUCU2BPB2, this is N920AUCU2APB2. coincidentally, N920AUCU2APB2 is the version all these various root methods are based on.
so, is this maybe an unreleased update from ATT? I can't really see any differences, and the phone works fine. I'm almost tempted to try one of those root files, but frankly I'm a little tired of wiping my phone when it gets buggy like chimera did to it.
That's the purpose and the fun of testing
Russ77 said:
the MM beta is N920AUCU2BPB2, this is N920AUCU2APB2. coincidentally, N920AUCU2APB2 is the version all these various root methods are based on.
so, is this maybe an unreleased update from ATT? I can't really see any differences, and the phone works fine. I'm almost tempted to try one of those root files, but frankly I'm a little tired of wiping my phone when it gets buggy like chimera did to it.
Click to expand...
Click to collapse
I hope someone could shed some light on this
Sent from my SAMSUNG-SM-N920A using Tapatalk
wp4jot said:
That's the purpose and the phone of testing
Click to expand...
Click to collapse
by all means feel free to test it :'p
something tells me I wouldn't get super su to install anyway.
It's not "phone" but "fun".
Russ77 said:
by all means feel free to test it :'p
something tells me I wouldn't get super su to install anyway.
Click to expand...
Click to collapse
---------- Post added at 11:52 PM ---------- Previous post was at 11:48 PM ----------
I've tested those root files posted here in 5.1.1. None of them work. I flashed back the stock boot image and my N920A is still working fine. But I don't want to flash this MM Odin files because I don't want to loose everything that I have downladed. I know I can backup first, and I already did, but I prefer to wait for the official MM upgrade from AT&T.
Russ77 said:
by all means feel free to test it :'p
something tells me I wouldn't get super su to install anyway.
Click to expand...
Click to collapse
Damn well I guess it's just a "Performance" update with the same build number as other 6.0 roms. Sorry but thanks for trying
I'm calling it now we will get the update on the 13th of march.
In 4 days!!!
maheshwar said:
I'm calling it now we will get the update on the 13th of march.
Click to expand...
Click to collapse
Not Marshmallow. It's the update released today, March the 9th, for N920A.
Sunderwear said:
Hey everyone. currently uploading the latest Odin package fresh off Samsung's kitchen
N920AUCU2APB2
That is the build number. It is the same as Verizon's note 5 MM update.
I do not have the ATT note 5 to test this on so when the file is uploaded I will need someone to confirm for me. Thanks!
EDIT:
HERE IS THE LINK DOWNLOAD
PLEASE MAKE A BACKUP OF YOUR DATA. THIS WILL PROBABLY DELETE YOUR STUFF. YOU'VE BEEN WARNED
Click to expand...
Click to collapse
Hopefully some new features in this update! Will update after installed.
ColoMtn said:
Hopefully some new features in this update! Will update after installed.
Click to expand...
Click to collapse
I ma getting it, too. Thanks for the notice! It didn't show until I manually checked for an update. 431 MB!!! Must be huge!
Release notes:
About this update:
This Software update include Wi-Fi Calling,
Advanced Messaging Services and other enhancements
ColoMtn said:
Release notes:
About this update:
This Software update include Wi-Fi Calling,
Advanced Messaging Services and other enhancements
Click to expand...
Click to collapse
What is a build of new update?
Sent from my SAMSUNG-SM-N930A using XDA Premium HD app
norbarb said:
what is a build of new update?
Click to expand...
Click to collapse
mmb29k.n920aucu3cpha
I noticed that the WiFi calling needs to be switched on. It is defaulted to off. Has anyone had the chance to try it out?
downloading now.. i think i seen where it will automatically push and download future updates in back ground.. have you seen any performance improvements so far? (nvm about auto updated thought was going to be 7.0)
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Info about the update: https://www.att.com/devicehowto/tut...step_KB426900?make=Samsung&model=SamsungN920A
Android Version: 6.0.1
Android Security Patch Level (SPL): September 1, 2016
Baseband Version: N920AUCU3CPHA
Kernel Version: 3.10.61-8961126 [email protected] #1 Fri Aug 26 14:43:25 KST 2016
Build Number: MMB29K. N920AUCU3CPHA
File Size: 431MB from version ending in PH4, 464MB from version ending in PG1
The Gallery app has been updated to the new version as well
Looks like this update includes a new version of Gallery. It is now version 3.0.16 -- I assume the same version as what is on Note7. Hope other system apps get the same update treatment.
I would really like to see the blue light filter added in like on the Note 7
---------- Post added at 03:27 AM ---------- Previous post was at 02:42 AM ----------
How do you get the advanced messaging to work?
I turned it on but am not seeing the read receipts. However I can send large attachments.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Carsus55 said:
I turned it on but am not seeing the read receipts. However I can send large attachments.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
I wonder if both parties need to have the same messaging app to register read receipts. Seems likely.
It actually started working this morning, but yes, both parties need to be using an enhanced messaging app.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Someone can update a Odin or sideload file?
do u have a link N920AUCU3CPHA yet ?
Kundinga said:
Someone can update a Odin or sideload file?
Click to expand...
Click to collapse
thien191189 said:
do u have a link N920AUCU3CPHA yet ?
Click to expand...
Click to collapse
Here is sideload from file BPH4 to CPHA . Remember if you sideload all of you data will be erase from your phone. Make sure you have backup.
tks so much bro <3
norbarb said:
Here is sideload from file BPH4 to CPHA . Remember if you sideload all of you data will be erase from your phone. Make sure you get backup.
Click to expand...
Click to collapse
No way for not wipe?
Kundinga said:
No way for not wipe?
Click to expand...
Click to collapse
No i don't play with this maybe someone else can create NONE wipe file. This one is from AT&T server.
This ROM is highly experimental . Bugs may occur at any time.
Thanks LineageOS team for the source.
First boot takes time, just wait patiently
What works:
Audio
WIFI
USB
Camera
Gravity
...
Issues:
HW still broken
but thanks for the solution provided by @USBhost , maybe it isn't a perfect solution for our broken hw, but stock video player and camera works now.:good:
Root Method :
Magisk 16.4
Device Tree : (Force encryption disabled)
https://github.com/LineageOS/android_device_htc_flounder
Lineage Builds: (06/17/2018)
https://www.androidfilehost.com/?w=files&flid=234619
Gapps:
https://androidfilehost.com/?w=files&flid=237585
Great! Hope this ROM can be more and more stable.
LeoYL said:
Great! Hope this ROM can be more and more stable.
Click to expand...
Click to collapse
今天重新编译了一个userdebug版本，目前用起来感觉还不错
I will flash it when a stock version gapps 8.0 is available.
Edit:
Oh I have found it: https://androidfilehost.com/?fid=673368273298983999
Now I can experience a stock-like Nexus ROM.
Dirty flashed over Noobuilds and the only issues are that Bluetooth crashes and it encrypted my device, but can live with that, especially given that I dirty flashed a completely different version of android
Rooted with Magisk 14.
Sent from my Nexus 9 using Tapatalk
Good enough for daily driver.
lmulli said:
Dirty flashed over Noobuilds and the only issues are that Bluetooth crashes and it encrypted my device, but can live with that, especially given that I dirty flashed a completely different version of android
Rooted with Magisk 14.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
My fault.I forgot to modify fstab file:crying:
But I used SuperSU for root and it seems to prevent device being encrypted.So I didn't find that
chrisclaytonnz said:
Good enough for daily driver.
Click to expand...
Click to collapse
Well it works, but I've gone back to my original rom only I'm not sold as to whether or not this is a genuine Android 8 rom as I noticed it making mention of Android 7.1.1 when installing. Also surprised that it would install over the top of a 7.1.2 AOSP based rom with no issues as such.
I could be wrong of course!!
lmulli said:
Well it works, but I've gone back to my original rom only I'm not sold as to whether or not this is a genuine Android 8 rom as I noticed it making mention of Android 7.1.1 when installing. Also surprised that it would install over the top of a 7.1.2 AOSP based rom with no issues as such.
I could be wrong of course!!
Click to expand...
Click to collapse
It's just a build fingerprint in lineage.mk and doesn't make any sense for Google only released Android 7.1.1 for Nexus 9.
And LOS15 is in the early stage so there won't be much difference between AOSP and LOS I think
lmulli said:
Well it works, but I've gone back to my original rom only I'm not sold as to whether or not this is a genuine Android 8 rom as I noticed it making mention of Android 7.1.1 when installing. Also surprised that it would install over the top of a 7.1.2 AOSP based rom with no issues as such.
I could be wrong of course!!
Click to expand...
Click to collapse
The first builds of unofficial Lineage still had CyanogenMod text in some places
read/write nfts otg supported?
䙉Êû said:
My fault.I forgot to modify fstab file:crying:
But I used SuperSU for root and it seems to prevent device being encrypted.So I didn't find that
Click to expand...
Click to collapse
Thanks for your work. Can you make a new version that doesn't encrypt the tablet please, when you have free time?
Sent from my Nexus 9 using Tapatalk
albsat said:
Thanks for your work. Can you make a new version that doesn't encrypt the tablet please, when you have free time?
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
Of course when I finish migrating data to my new computer
albsat said:
Thanks for your work. Can you make a new version that doesn't encrypt the tablet please, when you have free time?
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
Can you post the file /fstab.flounder ?
If the problem is the option "forceencrypt" that needs to be replaced with "encryptable" in fstab files it's very easy to do. For instance with a zip that I made some time ago that disable forceencryption and dm_verity.
jolinnard said:
Can you post the file /fstab.flounder ?
If the problem is the option "forceencrypt" that needs to be replaced with "encryptable" in fstab files it's very easy to do. For instance with a zip that I made some time ago that disable forceencryption and dm_verity.
Click to expand...
Click to collapse
That's it.I just replace forceencrypt with encryptable in fstab
And I'll start a compile if everything goes well after I finish my exam tomorrow.
Thanks for your post again
䙉Êû said:
That's it.I just replace forceencrypt with encryptable in fstab
And I'll start a compile if everything goes well after I finish my exam tomorrow.
Thanks for your post again
Click to expand...
Click to collapse
Good luck with your exam. Come back after it. :d
Sent from my Nexus 9 using Tapatalk
---------- Post added at 02:55 PM ---------- Previous post was at 02:51 PM ----------
jolinnard said:
Can you post the file /fstab.flounder ?
If the problem is the option "forceencrypt" that needs to be replaced with "encryptable" in fstab files it's very easy to do. For instance with a zip that I made some time ago that disable forceencryption and dm_verity.
Click to expand...
Click to collapse
You are saying that installing the file posted by you, will not let encrypt the tablet. Right? This file will not alter other files (like boot.img) which is my concern? Thanks
Sent from my Nexus 9 using Tapatalk
albsat said:
Good luck with your exam. Come back after it. :d
Sent from my Nexus 9 using Tapatalk
---------- Post added at 02:55 PM ---------- Previous post was at 02:51 PM ----------
You are saying that installing the file posted by you, will not let encrypt the tablet. Right? This file will not alter other files (like boot.img) which is my concern? Thanks
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
Typically, it will. dm-verity/verified boot is a kernel feature, hence completely related to boot.img. :good:
The file will probably patch your current boot and disable forced-encryption.
依旧不能硬解
albsat said:
Good luck with your exam. Come back after it. :d
Sent from my Nexus 9 using Tapatalk
---------- Post added at 02:55 PM ---------- Previous post was at 02:51 PM ----------
You are saying that installing the file posted by you, will not let encrypt the tablet. Right? This file will not alter other files (like boot.img) which is my concern? Thanks
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
The zip will extract boot.img, replace fstab and will repack again. Check the script boot/editramdisk.sh, as you can see it replace the word forceencrypt to encryptable. All the scripts were took of FIRE-ICE or ElementalX I believe, I only removed all the parts related to zImage...
I can't flash now Lineage to test this zip, so if you can't wait, make a backup and try. All should be fine, but I don't know if anything changed in boot.img parameters (like pagesize, ramdisk_offset, tags_offset, etc...)
So far this ROM is awesome! The only bugs I've found yet are face unlock and NFC not working. Anyone who doesn't care about those issues can use this ROM as a daily driver. I'd never dreamed of such a stable unofficial 8.0 ROM until I found this one, since speaking of third-party ROMs Tegra sucks (e.g. Two gens of Nexus 7, the 2012 version with Tegra received 6.0 port while the 2013 version with Snapdragon received 7.0 port) and Google abandoned updating Nexus 9. Great thanks to the OP!
This is the new refined home for DarkRoom Development. If you submit bug reports without a log, you may be prosecuted...or executed.
Disclaimer:
If your device fails to comply with your standards of what you consider functioning, I am not liable. This is provided free of charge and does not come with a warranty. Although, if you provide a log, I can provide some sort of assurance that I will look into your issue.
Links:
Social:
Twitter - http://twitter.com/DespairDev
G+ Community - https://plus.google.com/u/0/communities/117685307734094084120
Telegram - https://t.me/darkroomdev
Discord - https://discord.gg/BGTFutW
Downloads:
https://go.hunternott.com/darkroom
Source:
Github – https://github.com/matthewdalex/
Github – https://github.com/UBERROMS/
Credits:
faux123
franco
Google
flar2
imoseyon
Cl3Kener
neobuddy89
Star Wars
The files with P2 in the name are for Pixel 2, non XL
Tested and it boots.
fastboot flash boot xxxx.img
Where can I find information about what this kernel does? I don't see it anything linked to in the OP.
cb474 said:
Where can I find information about what this kernel does? I don't see it anything linked to in the OP.
Click to expand...
Click to collapse
You could read the changelog here https://github.com/matthewdalex/wahoo/commits/master
Would this kernel stop safetynet from detecting an unlocked bootloader? Thanks.
SuperSmashedBro said:
Would this kernel stop safetynet from detecting an unlocked bootloader? Thanks.
Click to expand...
Click to collapse
yep
DespairFactor said:
yep
Click to expand...
Click to collapse
Just flashed it, everything working flawlessly! Thanks
R3 is up and compiled with clang
anyone online for testing???
DespairFactor said:
R3 is up and compiled with clang
Click to expand...
Click to collapse
tried "fastboot flash boot ###.img'
With Snoke-R5-P2 but get exceeds max-download-size
maxrhys said:
tried "fastboot flash boot ###.img'
With Snoke-R5-P2 but get exceeds max-download-size
Click to expand...
Click to collapse
You try USB 2.0 and your unlocked as well correct?
Sent from my Nexus 6 using Tapatalk
bryantjopplin said:
You try USB 2.0 and your unlocked as well correct?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I was using USB 3.0... tried with 2.0 and works now that thanks...
maxrhys said:
I was using USB 3.0... tried with 2.0 and works now that thanks...
Click to expand...
Click to collapse
It's the damnedest things
Sent from my Nexus 6 using Tapatalk
I'm getting the same error using the USB C to USB C cable that came with the P2. I'm going to try with something else.
Edit: Strange...I used another cable with USB 3.0 and it worked. >_<
R6 up now for all of you Enjoy!
Maybe dumb, but can someone please post instructions on flashing this image? I've been out of the customization game since S4 and could use a refresher (just need to know what to name the file before flashing). TIA
Edit: bootloader is unlocked. I got that far on my own.
csxt8142 said:
Maybe dumb, but can someone please post instructions on flashing this image? I've been out of the customization game since S4 and could use a refresher (just need to know what to name the file before flashing). TIA
Edit: bootloader is unlocked. I got that far on my own.
Click to expand...
Click to collapse
Not trying to be mean, but it will help in the long run:
Try googling it first
csxt8142 said:
Maybe dumb, but can someone please post instructions on flashing this image? I've been out of the customization game since S4 and could use a refresher (just need to know what to name the file before flashing). TIA
Edit: bootloader is unlocked. I got that far on my own.
Click to expand...
Click to collapse
You don't need to rename it anything
You can either use "fastboot flash boot filename.img" or substitute boot_a or boot_b for boot to specify the slot. When not specifying it will flash the current slot.
Sent from my Pixel 2 using Tapatalk
---------- Post added at 07:02 PM ---------- Previous post was at 06:42 PM ----------
[/COLOR]
joetheshmo said:
You don't need to rename it anything
You can either use "fastboot flash boot filename.img" or substitute boot_a or boot_b for boot to specify the slot. When not specifying it will flash the current slot.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Worked first try, thanks!!
This is a beta rom so as the name implies you may encounter various problems/bugs.
Fastboot (unlocked bootloader)(erases all your internal storage):
http://bigota.d.miui.com/8.3.1/scor....1_20180301.0000.00_8.0_global_7127f41234.tgz
Recovery (TWRP and unlocked bootloader)(full wipe highly recommended):
http://bigota.d.miui.com/8.3.1/miui_MINote2Global_8.3.1_74f30a299a_8.0.zip
The update has been suspended at the moment but download links are still working... Anyway you flash the packages at your own risk, I don't assume any responsibilities for any bricked or exploded devices! This is only for sharing purposes!
Thank I very much for sharing
Thank you!
Thank you! But download from this server is a pain... could you upload it to another site?
Enviado desde mi MI Note 2 mediante Tapatalk
Hmmm, the mentioned version is basing on nougat 7.0... would be interesting to see if it is really basing on oreo
Gesendet von meinem Mi Note 2 mit Tapatalk
strumbol said:
Thank you! But download from this server is a pain... could you upload it to another site?
Enviado desde mi MI Note 2 mediante Tapatalk
Click to expand...
Click to collapse
Sorry i can't, my connection is too slow
haarmatte said:
Hmmm, the mentioned version is basing on nougat 7.0... would be interesting to see if it is really basing on oreo
Gesendet von meinem Mi Note 2 mit Tapatalk
Click to expand...
Click to collapse
Those two versions posted here are based on Oreo.
Are you sure?
realjumy said:
Are you sure?
Click to expand...
Click to collapse
If you updated through OTA or you downloaded from the miui forum you will have the nougat one. There are two versions of the 8.3.2 build: one is nougat and the other (the one I posted) is oreo
alexmanu1 said:
Those two versions posted here are based on Oreo.
Click to expand...
Click to collapse
Spezia12 said:
If you updated through OTA or you downloaded from the miui forum you will have the nougat one. There are two versions of the 8.3.2 build: one is nougat and the other (the one I posted) is oreo
Click to expand...
Click to collapse
Any link to something we can use with locked bootloader?
realjumy said:
Any link to something we can use with locked bootloader?
Click to expand...
Click to collapse
Nothing at the moment
I was reading some comments of the OTA bricking phones... Are you having any problem so far?
---------- Post added at 08:07 PM ---------- Previous post was at 08:01 PM ----------
I wonder if we can use this: http://bigota.d.miui.com/8.3.1/miui_MINote2Global_8.3.1_74f30a299a_8.0.zip
I think it's the right file... But maybe right beta privileges are needed?
realjumy said:
I was reading some comments of the OTA bricking phones... Are you having any problem so far?
---------- Post added at 08:07 PM ---------- Previous post was at 08:01 PM ----------
I wonder if we can use this: http://bigota.d.miui.com/8.3.1/miui_MINote2Global_8.3.1_74f30a299a_8.0.zip
Click to expand...
Click to collapse
Well if you like risking a hard brick you can download that file, rename it update.zip and put it in the folder downloaded_rom. Then go to the miui updater app and it should see it as an update and the installation will start. The problem is that if you are on locked bootloader without TWRP and the flash goes wrong you can throw away your phone...
realjumy said:
I think it's the right file... But maybe right beta privileges are needed?
Click to expand...
Click to collapse
Very likely
Spezia12 said:
Well if you like risking a hard brick you can download that file, rename it update.zip and put it in the folder downloaded_rom. Then go to the miui updater app and it should see it as an update and the installation will start. The problem is that if you are on locked bootloader without TWRP and the flash goes wrong you can throw away your phone...
Click to expand...
Click to collapse
No risk, no fun... I used the option in the updater and it doesn't allow me to install it. Probably because I need special privileges... In any case, these are excellent news for custom ROMs
Edit: previous to the installation of the .ZIP it asks me to be connected to the internet... It can't be connected without being connected to the internet. So definitely they check if the user is allowed to install it.
Anyways. Anyone using the ROM can give some feedback, please?
Installed by twrp and running perfect ... for now no failure
routed with magisk 16.0
So installed last TWRP, wiped all data and storage for decryption, all went ok, inastalled oreo beta rom and magisc 16, during booting phone first get encrypted again and then rom boots up. Restarting back to TWRP is asking for password again to decrypt phone. So because of that I get back to nougat and TWRP 3.1.1.0 because that is only one that is not asking password. So please help and inlight me what I was doing wrong.
Spezia12 said:
Well if you like risking a hard brick you can download that file, rename it update.zip and put it in the folder downloaded_rom. Then go to the miui updater app and it should see it as an update and the installation will start. The problem is that if you are on locked bootloader without TWRP and the flash goes wrong you can throw away your phone...
Click to expand...
Click to collapse
A hard brick for a snapdragon device does not exist.
realjumy said:
No risk, no fun... I used the option in the updater and it doesn't allow me to install it. Probably because I need special privileges... In any case, these are excellent news for custom ROMs
Edit: previous to the installation of the .ZIP it asks me to be connected to the internet... It can't be connected without being connected to the internet. So definitely they check if the user is allowed to install it.
Click to expand...
Click to collapse
You have to be in the Beta Team to install those packages with the updater app. The method the Super Moderator recommended me is fastboot because it's an android version update. The ROM worked fine in the first day , no important bug that can prevent it to be a daily driver.