yashsingh1/xdaforums huggingface dataset:
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] DanteGR:
.

I'm still on 8.12.27 vendor but I'm pretty sure that doesn't make much of a difference.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] theeta357:
Yes.. that shouldn't make a difference

And aosip is 6th Jan build right?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] thechints:
Ok, so microphone background noise cancellation is a confirmed issue it seems then. Request [MENTION=5854483]akhilnarang[/MENTION] to pls take a look into this. Thanks!
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] theeta357:
I checked again with 12.27 vendor, but still the page is disabled. (Vendor 12.27+aosip jan6th +gapps nano +dfe)

So now not sure where the issue lies.

Previously it was working fine for me on the latest build when I dirty flashed it, now not able to find links to the older build as well :crying:

Maybe Akhil can check this up, until then sticking with old school button navigation.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] thechints:
For older builds:

http://get.aosiprom.com/beryllium
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] theeta357:
Thank you, will check out the older build again :)
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] theeta357:
Figured out what the issue is,

when setting up the phone using previous google cloud backup, on the apps restore page I just unchecked the box where it said "device settings and WiFi passwords etc" and it works fine now.

My guess is all the owlsnest settings are also getting backed up in the google device backups and its causing the issue when we restore the same.

Maybe Akhil can check this up.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] DanteGR:
For anybody that is interested it seems like the rom has been "silently" updated.

Newest version on the OP is now 14/01/2019.

:)
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] akashkyh:
Yo.... Updating mine.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] theeta357:
But still no changelist ..
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] DanteGR:
Indeed...
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] akashkyh:
Finally updated :)
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] theeta357:
Dirty flashed?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] akashkyh:
yes
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] akhilnarang:
New build dated 20190114 is up!

https://t.me/AOSiP/33

Merged in January Security patches

Updated translations

Updated Derp Kernel compiled with clang 8.0.7

Added option for oreo recents

Lockscreen customizations (clock, etc)

OP Gesture Tweaks

QS tweaks

There might be some more I forgot about

About the previous build - I had to go out of town, so could not fully test it and didn't manage to get time to post about it here :P so this changelog includes some things that may have been in there
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] SiddharthS7:
Dynamic thermal added?
[Android Head-Units] pierluc:
Hello, I would like to know why my head-unit froze when it's cold and when it's hot outside. I know that it can overheat when temperature in my car is very high. But, why does it do the same with temperature below zero? The former head-unit from Toyota didn't had that issue. Could it be condensation? Does-it has anything I can do for that?

Tank-you
[Nokia 8 Guides, News, & Discussion] Toedwarrior:
Hi guys i have a question, i am looking forward to cheap dac/amp build and leaning forwards to fioo q1 mark ii. Am aware it is built for idevices but people managed to get it to work on android devices as well. But they say that andoid devices need isochronous mode activated. I couldn't managed to find any threads or articles about how to check that mode. Any help would be appreciated thanks
[Nokia 8 Guides, News, & Discussion] kutulu32:
I have a fiio e17 old version and i use it alone as usb dac-amp or together with my fiio e12 . I havent tested it with nokia 8 yet but it works with usb audio player pro that i use . Since nokia 8 has not line out mode so you should buy something like that dac with amp (fiioe17k ) i dont know about that mode you tell (isochronous) .before you buy a usb dac-amp make a research if it works with your favorite music player

Edit i tested e17 with nokia 8 all ok(usb audio player pro)
[Essential Phone Guides, News, & Discussion] ktmom:
The way I do *updates* is different (not the initial TWRP/ root).

I use the same Essential developer link as in part 1-1. I also have a copy of twrp-installer-mata-3.2.3-0 zip file on my device.

Boot to TWRP, and do a complete nandroid.

Then install the OTA file just like it's any other zip and when it's done, install the twrp-installer-mata-3.2.3-0 zip file. You can simply put them both into the flash queue before starting the flash.

This TWRP installer will install to both slots ensuring that the inactive slot has it installed. Wipe dalvik and then reboot to system which will be in the opposite slot from the one you started at.

The OTA will always flash to the inactive slot and the bootloader will switch to the slot the OTA was flashed to.

The initial boot takes a few minutes. Once I verify the ROM boots correctly, then I reboot to TWRP and flash Magisk. This ensures that Magisk get installed to the same slot that is now active.

I agree it's safer to remove screen pin, so far I have gotten away with never remembering to do that [emoji16]

If the flash fails, the bootloader should just switch you back to the original slot. I would expect that to boot fine, with one exception... The bootloader was changed between 8.1.1 and 9.0. So if you are going between major versions, the original slot will bootloop after the update.

One more note, a pet peeve of mine; when referencing a post that is older, make sure that you review the forums for changes. TWRP might have a required newer release, the methods that once worked may no longer work. If you are not sure or comfortable recovering, then don't be an early adopter. [emoji6]

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Essential Phone Guides, News, & Discussion] andypiznti:
you know i just finished writing my own guide to do it after i had trouble with the sticky posts. for me, magisk couldnt find the stock boot so i had to pretty much redo it. i did most things with back-to-stock and fastboot. but now i really wanna try your method through twrp. i been using the patched_twrp_magisk_stock.img images which have twrp and magisk in the same image. using your method, in twrp, could i flash the ota, the patched_twrp_magisk_stock.img, switch slots in twrp, flash patched_twrp_magisk_stock.img again, then switch back to the original slot and reboot system? thanks!

this thread has the patched_twrp_magisk_stock.img images

https://xdaforums.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
[Essential Phone Guides, News, & Discussion] ktmom:
[MENTION=4068100]andypiznti[/MENTION]

There's no need to manually switch slots. And no reason to flash the TWRP *installer* file twice. The first time it runs, it patches both slots.

IMHO, trying to control slots is what gets people into trouble.

I do pay attention to what slot I'm on before I start though. In TWRP, if you go to the reboot menu, it will tell you. But the way I flash, I stay on the slot I started with. The OTA will always flash to the opposite slot - which should be the inactive slot. Flashing the TWRP *installer* file just once, patches both slots.

Just wipe dalvik (and cache but there is no cache partition so it will error - just ignore the error) then reboot to system like we've done after custom ROMs for years.

The next boot, the bootloader knows to switch to the slot with the newest OS.

After a successful boot, when you return to TWRP, you'll see the slot is the opposite one from when you started. But you didn't need to do any slot switching.

Don't force things. Let the slots take care of themselves.

I also think, there is less likely to be trouble with Magisk and the boot.img, if you boot fully after an update, before returning to recovery to flash Magisk. Remember that both TWRP and Magisk are making changes to the boot.img.

Final thought, unless I seriously misunderstand Magisk, if you rooted using an all-in-one boot.img you won't have a back up of the "stock" boot.img to restore, making the Magisk uninstaller useless. The backup made when installing Magisk is stored on the data partition, not the boot partition. This is why the instructions in BTS tell you to flash the stock boot.img and provide a copy of it.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Essential Phone Guides, News, & Discussion] hssxda:
The beauty of my method in the OP is you don't need to worry at all about the correct "slots" like you have to with TWRP...
[Essential Phone Guides, News, & Discussion] andypiznti:
ok that answers a lot. thanks! the guide i made for myself had me flashing the stock image with bts. i was curious about the full boot after an update, i was thinking the same thing in that it might cause problems with magisk, but i also thought twrp would cause problems too. the reason i mentioned switching slots and flashing is the all-in-one img only flashes to one slot at a time, i believe.

heres my guide for reference, its kinda long. but these were the exact steps i followed and was successful. had to flash the img twice, kept rebooting into recovery if i didnt.
[Essential Phone Guides, News, & Discussion] ktmom:
I don't know what more I could do to make the point it's not necessary to worry about slots in TWRP.

[MENTION=4068100]andypiznti[/MENTION]. The all-in-one is Fastboot flashed to either slot one at a time. All of this makes life harder than it needs to be.

My post was suggesting an alternative. Use the OTA, no Fastboot, no PC just have the TWRP installer file I linked so you don't lose TWRP.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Essential Phone Guides, News, & Discussion] hssxda:
Well, all of your posts describing your method contains the word "slot" multiple times so it is obviously a relevant concern otherwise you wouldn't have mentioned it. My post did not contain the word even once...

I see no need to use TWRP. What advantage does it have?
[Essential Phone Guides, News, & Discussion] andypiznti:
oh yes, definitely doing that next time. thanks!! i found this post thats exactly your method in a little less words. :)

https://xdaforums.com/essential-pho...1-1-nmj20d-t3701681/post78194778#post78194778
[Essential Phone Guides, News, & Discussion] rignfool:
Jeebus...

We didn't like the other 15 goddamn threads with the same topic...

XDA is cancer
[Essential Phone Guides, News, & Discussion] hidroela:
what works for me at the time to flash the patched image was

fastboot flash boot_a patched_boot.img

fastboot flash boot_b patched_boot.img

note: i am on pie

thanks for the guide.
[Essential Phone Guides, News, & Discussion] rogosteve:
Really helped lots, thank you.
[Essential Phone Guides, News, & Discussion] kma_29:
January update is out, who might like to patch boot.img with TWRP and Magisk?
[Essential Phone Guides, News, & Discussion] ktmom:
Go to the stock room thread

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Essential Phone Guides, News, & Discussion] morphius88:
OP, if you want to avoid having to sideload the whole OTA, you can have it done directly by your phone by flashing the stock boot image for the current version that you are one and then updating from the settings (or notification). Then just continue with flashing the rooted boot image for the new update. I feel like that is safer than both TWRP and sideloading the full OTA (in reference to keeping data safe).

https://xdaforums.com/showpost.php?p=76828139&postcount=1264
[Essential Phone Guides, News, & Discussion] hssxda:
Thanks
[Essential Phone Guides, News, & Discussion] jionny:
[MENTION=4550123]bmg1001[/MENTION] are you still providing the stock boot images on your google drive. I am looking for the Feb stock boot image or can someone tell me how to get it. I tried extracting from the Feb OTA but did not see it listed in that zip
[Essential Phone Guides, News, & Discussion] bmg1001:
Yep, I have it in the same Google Drive folder where the other month's images are posted.
[Essential Phone Guides, News, & Discussion] jionny:
Sorry chalk that up to me not paying attention. I was looking for it after Jan but its actually the first one listed. Thanks!
[Essential Phone Guides, News, & Discussion] jionny:
Hi one more thing, this is my third time updating and rooting via this method. The last two times worked flawlessly however this time I did update the OTA but when I try to reroot and go to adb devices I see my phone listed then when I reboot recovery it does however when I try fastboot devices my phone does not show and nothing happens, any help will be appreciated
[Essential Phone Guides, News, & Discussion] jionny:
Found the problem, even though I had no problem with Dec and Jan the Feb was not recognizing fastboot. I redownloaded the windows driver and instantly fastboot was recognized
[Essential Phone Guides, News, & Discussion] jionny:
Anyone have a problem rooting the Mar update? installed OTAupdate fine but cannot get it to root. I get

target didnt report max-download-size

Sending 'boot' (13452 KB)...

FAILED (remote: Requested download size is more than max allowed)

finished. total time: 0.005s
[Essential Phone Guides, News, & Discussion] jionny:
I figure it out, for every other root since Dec I used minimal adb well it would not work for the Mar patched boot, went to platform tools and it worked
[Essential Phone Guides, News, & Discussion] kt-Froggy:
I always use the adb/fastboot that comes with the Essential USB drivers (it gets installed along with the drivers). This has been highly recommended in several threads and guides to avoid possible issues.
[Essential Phone Guides, News, & Discussion] chocobo842:
For some reasons I screwed up on the boot of Q beta 4 when I tried to root....I would like know if anyone able to provide the stock boot for Q beta 4 please?

I have been searching over reddit and google, and there is only patched available...
[Essential Phone Guides, News, & Discussion] dazeone:
Why not extract it from the fastboot files
[Essential Phone Guides, News, & Discussion] usafle:
So I attempted this and got this error after booting into TWRP:

I'm using the ADB provided in the link in the OP and the newest TWRP.
[Essential Phone Guides, News, & Discussion] kt-Froggy:
Never seen this, and not sure exactly what's causing it, but first I would suggest trying the adb/fastboot provided by Essentials. It gets installed along with the PH-1 drivers, meaning you don't even need to download and install the platform tools separately. You can find the binaries under "Program Files (x86)" in the Essential folder.
[Essential Phone Guides, News, & Discussion] usafle:
Tried the Essential ADB and a different USB cable.... still same error:

PS C:\Program Files (x86)\Essential\ADB> adb sideload OTAUpdate.zip
opening 'OTAUpdate.zip'...
connecting...
falling back to older sideload method...
error: closed
[Essential Phone Guides, News, & Discussion] kt-Froggy:
Bummer... I don't use TWRP, and always do an OTA sideload via stock recovery with no issues. I don't know if this may be related to TWRP... Did you follow the same steps successfully for previous updates?
[Essential Phone Guides, News, & Discussion] usafle:
Following the persons instructions above, I was able to flash the OTA. The OPs instructions didn't work for whatever reason.
[Essential Phone Guides, News, & Discussion] tribulationwolf:
anyone know where i can find a stock boot img of android q beta 5? the only link i could find on xda in for beta 3.
[Essential Phone Guides, News, & Discussion] DAE1964:
https://www.essential.com/developer/android-q-beta
[Essential Phone Guides, News, & Discussion] kboya:
Updated to 10 using these instructions without any issues. You do need to have Magisk's canary channel for root, but you can dl and install after the first system boot.
[Essential Phone Guides, News, & Discussion] jionny:
This worked for me also although I made the mistake of then using substratum and swift black which is not updated for Android Q yet(didn't think about that until after I applied) it corrupted the os and I had to do a factory reset, when I factory reset it was still rooted, just needed to update Magisk
[Essential Phone Guides, News, & Discussion] lqvd:
Maybe include the option of uninstalling magisk and installing to inactive partition. Working well since magisk 17.x (not sure which version anymore), but this method can be done on phone directly without connecting to pc or using adb. Only works if you do receive OTA updates on the phone. A guide can be found here.
[Essential Phone Guides, News, & Discussion] sd_shadow:
May have been posted already.

If you get an error while flashing magisk_patched.img like

FAILED (remote: No such partition.)

Change to inactive slot ,

Flash magisk_patched.img

Change back to the original slot

reboot

To check active slot

fastboot getvar current-slot

To change to slot a

fastboot --set-active=a

To change to slot b

fastboot --set-active=b
[Essential Phone Guides, News, & Discussion] Darkside1984:
I need the January stock boot image. Any alternative way to get it to root with the latest update?
[Essential Phone Guides, News, & Discussion] kt-Froggy:
Here are my steps.

1. Download the full fastboot image from Essential's website.

2. Extract boot.img from it.

3. Apply the update either via OTA directly on the phone, or by sideloading the OTA image from Essential.

4. Install Magisk Manager, if not installed already.

5. Copy the extracted boot.img to the phone, then patch with Magisk.

6. Copy the patched boot.img to PC.

7. Reboot into bootloader.

8. Fastboot flash the patched boot.img.

9. Reboot the phone.

I also gave you the link to the rooted (patched) boot.img from the latest update in the other thread.
[Essential Phone Guides, News, & Discussion] Darkside1984:
Thanks so much!
[Essential Phone Guides, News, & Discussion] jionny:
Hi does anyone have the Jan 2020 stock boot image I did not see it in bmg's folder
[Essential Phone Guides, News, & Discussion] good4y0u:
What do you do in the case where you had TWRP installed (and everything was working) then ran this and did not re-flash TWRP.

The issue is it leaves you without a recovery.
[Essential Phone Guides, News, & Discussion] i8890321:
[Solved]

in case someone still seeking for the answer for stuck at fastboot flash boot.

i just use another PC to try that command and it works charm.

i think my 1st try on my decktop computer is failed because the window messed up the essential driver.

i m using the latest(Q10 jan 007.img)

i patched it with magisk manager , i got the patched file.

when i fastboot flash into boot, i got the following error, please help , now i m living without root......

error screen on cmd.exe (Powershell?)

many thanks

========================================================================

PS C:\platform-tools> fastboot flash boot magisk_patched.img

target didn't report max-download-size

sending 'boot' (24097 KB)...

PS C:\platform-tools> fastboot flash boot magisk_patched.img

target didn't report max-download-size

sending 'boot' (24097 KB)...

FAILED (command write failed (No error))

finished. total time: 0.016s

PS C:\platform-tools>
[Essential Phone Guides, News, & Discussion] mpena:
The February OTA isn't working. I flushed twice in TWRP then TWRP installer and the device reboot in bootloader several times then start with previous version of the security patch
[Essential Phone Guides, News, & Discussion] freshlysqueezed:
Installing TWRP onto the Feb OTA doesn't work anymore. If you want root, you will need to flash a magisk patched boot image through fastboot.
[Essential Phone Guides, News, & Discussion] rocketrazr1999:
Lrooted using an all-in-one boot.img you won't have a back up of the "stock" boot.img to restore, making the Magisk uninstaller useless. The backup made when installing Magisk is stored on the data partition, not the boot partition. This is why the instructions in BTS tell you to flash the stock boot.img and provide a copy of it.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini[/QUOTE]

OP is not referring to the TWRP.zip installer that flashes TWRP to both slots in a single flash, he is talking about flashing a patched boot image with TWRP, Magisk, and a custom kernel already patched to it. And NO, you can not flash the same patch to your inactive slot because the inactive slot will still have the previous OTA update on it, and just wanted and during uo a new updated boot image will most likely have updated code which will not be compatible with the previous update. You CAN, however, flash both slots with the new update and then flash the inactive slot with the new patched boot.img in TWRP (just change the file option from .zip to .IMG first). Or you can flash the inactive slot with your previous updates' patched boot .IMG, provided you saved it, but if not redownload it.
[Essential Phone Guides, News, & Discussion] godzulu:
magisk

:(
[Essential Phone Guides, News, & Discussion] rocketrazr1999:
Same here...flashed it many times and flashed TWRP, Magisk, and ElementalX and booted to system but got the redirect to opposite slot with January on it. What's going on???
[Essential Phone Guides, News, & Discussion] godzulu:
I got magisk to work on the Feb update. Of course, I patched the boot.img w/magisk mgr and put it in computer fastboot folder. Dont know if this made a difference or not, but I renamed it to boot.img. booted phone into bootloader/fastboot devices/ fastboot getvar current-slot /fastboot flash boot_"slot" boot.img

I flashed to the same slot i was in - and it worked finally :)
[Essential Phone Guides, News, & Discussion] UltraMagnus0001:
So,if I'm understanding right, you have to flash Feb 2020 on your computer? I'm spoiled with using TWRP to update.