Develop Bugs

Erased my Fire HD 8.9 - Can it be saved?

I was running Candy5 ROM ver. 2.5 and saw the thread for the 4.0 ROM. I downloaded it and Gapps and put it on the Fire HD. Rebooted into Recovery and into TWRP. That's when I did one of the most stupid things that I've ever done. I wanted a clean install from scratch. Unfortunately, I erased everything! When I realized what happened I rebooted and the screen goes through the two fire HD logos stopping at the last one. Is there ANYTHING I can do to get an operating Fire HD back up and running, Please!

rebelduke said:
I was running Candy5 ROM ver. 2.5 and saw the thread for the 4.0 ROM. I downloaded it and Gapps and put it on the Fire HD. Rebooted into Recovery and into TWRP. That's when I did one of the most stupid things that I've ever done. I wanted a clean install from scratch. Unfortunately, I erased everything! When I realized what happened I rebooted and the screen goes through the two fire HD logos stopping at the last one. Is there ANYTHING I can do to get an operating Fire HD back up and running, Please!
Click to expand...
Click to collapse
Try to reboot into TWRP (press + hold volume up as soon as you see the first logo, keep holding till you see the TWRP curtain). If you are successful, copy a ROM zip into the kindle's internal storage (gapps are optional, but I recommend you flash them along with your chosen ROM), flash it, reboot, and cross your fingers.

Thank you. I'm making some progress. Your instructions got me into TWRP (ver. 2.8.6). Next step is to get the PC to allow copying of the ROM file. TWRP does recognize that there is no operating system installed. Thanks again!

rebelduke said:
Thank you. I'm making some progress. Your instructions got me into TWRP (ver. 2.8.6). Next step is to get the PC to allow copying of the ROM file. TWRP does recognize that there is no operating system installed. Thanks again!
Click to expand...
Click to collapse
If you can't directly copy it, try adb sideload path/to/ROM.zip (enable sideloading in the advanced menu in TWRP first, or you'll get an error). Make sure you have adb drivers installed and working if your PC's running Windows. Good luck!

monster1612 said:
If you can't directly copy it, try adb sideload path/to/ROM.zip (enable sideloading in the advanced menu in TWRP first, or you'll get an error). Make sure you have adb drivers installed and working if your PC's running Windows. Good luck!
Click to expand...
Click to collapse
Adb sideload worked with the Candy5 4.0 ROM. The Gapps zip failed due to the file size being too great. I can tackle that after the ROM is installed. Another stupid question - any idea where the sideloaded ROM zip file would be internally? I explored using the TWRP file manager and all I have is the directory structure - no actual files. I probably looked in 50+ folders and they were all empty. I think there must be hundreds of directories and subdirectories. I found one folder named sideload thinking I had it but no luck. Worst case I can open every folder and hopefully find the ROM zip file.

rebelduke said:
Adb sideload worked with the Candy5 4.0 ROM. The Gapps zip failed due to the file size being too great. I can tackle that after the ROM is installed. Another stupid question - any idea where the sideloaded ROM zip file would be internally? I explored using the TWRP file manager and all I have is the directory structure - no actual files. I probably looked in 50+ folders and they were all empty. I think there must be hundreds of directories and subdirectories. I found one folder named sideload thinking I had it but no luck. Worst case I can open every folder and hopefully find the ROM zip file.
Click to expand...
Click to collapse
From the TWRP FAQ for the sideloading feature:
TWRP versions 2.8.2.0 and higher will stream the zip from your PC without storing it on your device. If you wish to store the zip on your device for later, you should not use sideload and instead use adb push or some other method to copy the zip to the device.
Click to expand...
Click to collapse
Older TWRP versions used to store the zip file in /sdcard/sideload, but I think versions 2.8.2.0 and higher use it as a temporary buffer and delete the zip after flashing. If you're able to get Android up and running, then you should be able to connect it to your PC, copy the ROM and gapps zips over to the kindle without using adb, and flash the gapps.

monster1612 said:
From the TWRP FAQ for the sideloading feature:
Older TWRP versions used to store the zip file in /sdcard/sideload, but I think versions 2.8.2.0 and higher use it as a temporary buffer and delete the zip after flashing. If you're able to get Android up and running, then you should be able to connect it to your PC, copy the ROM and gapps zips over to the kindle without using adb, and flash the gapps.
Click to expand...
Click to collapse
Thanks very much for all of your advice and suggestions! I'm back up and running. The gapps package was causing an error 70 message. Once I found a smaller file it worked. It certainly was an excellent learning experience. Thank you again.

Can't root through SuperSU or Magisk on open beta 25 (android O)?

I've tried to root using Magisk to SuperSU but I'm into the same issue, The device get stuck on the boot screen until I re-flash the stock boot image, is there any solution for that's?

Not yet. Did this really require a thread of its own ?

skymera said:
Not yet. Did this really require a thread of its own ?
Click to expand...
Click to collapse
I just want to know how much will take so that it will be available.

rsm23 said:
I just want to know how much will take so that it will be available.
Click to expand...
Click to collapse
Nobody here can see in the future...

https://forum.xda-developers.com/showpost.php?p=74161852&postcount=3634
here try this Good Luck !

On my phone SuperSU 2.82 SR5 works fine. On other phones not, or SR3 woks....
Magisk 1.4 or 1.42 beta not working. I did not get boot loops, but not working.

rsm23 said:
I've tried to root using Magisk to SuperSU but I'm into the same issue, The device get stuck on the boot screen until I re-flash the stock boot image, is there any solution for that's?
Click to expand...
Click to collapse
Follow this guide brother

Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))

baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
How did you achieve this?

baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
This is a good news. Cannot wait for more details!

baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
Does this seems ok to you : https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901 ?

ashokmor007 said:
Follow this guide brother
Click to expand...
Click to collapse
Thanks, but I don't like SuperSU
---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------
mr.charlie said:
Does this seems ok to you : https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901 ?
Click to expand...
Click to collapse
Thanks, but too much of a hassle for me right now.
I think I'll just wait for an official Magisk update to be released, at this point

baskaflyfer said:
Magisk 14.0 & Oreo(beta25) still testing, later i'll share it)))
Click to expand...
Click to collapse
! We are looking forward to your description: how to take the steps? !

papzi57 said:
! We are looking forward to your description: how to take the steps? !
Click to expand...
Click to collapse
Be carefully, you can lose you data!!! For me all work fine)))
1.Flash Oreo via trwp
2.Downgarde bootloader for DM-Verity
3. Flash Magisk via twrp
4. Turn off the phone manualy
5.Turn on & boot in twrp
6.Do the backup of boot
7.And edit boot.win in hex editor on pc
Code:
androidboot.selinux=permissive
screen in attachment
8.And flash boot back, reboot.
P.S When you set selinux permissive via fastboot you'll have freeze (braking) in system - i don't know how it say

baskaflyfer said:
edit boot.win in hex editor
Click to expand...
Click to collapse
This worked for me too, but maybe some other users need more information on the boot partition
Oreo compatible TWRP: Download (Credits: @akhilnarang)
OOS Open Beta 25: Download (Official OnePlus Website)
Magisk 14.3 (Beta): Download (stolen from this thread)
Magisk Manager 5.4.0: Download (GitHub)
You are responsible, if it kills your device, but this was my way:
1. Full Backup in TWRP
2. Reboot into Fastboot Mode
3. Flash Oreo compatible TWRP
4. Use Volume Keys to select and boot into recovery
5. Install OOS Open Beta 25
Then i did a reboot and Steps 1&2 again but i don't think this is required.
6. Install Magisk 14.3 Beta
7. Create an image of the boot partition
Code:
adb shell
dd if=/dev/block/sde18 of=/sdcard/boot.img
exit
8. Copy the boot.img file to your computer
9. Open this file in a hex exitor, add the following text after "buildvariant=user" (image in baskaflyfer's answer) and save the file:
Code:
androidboot.selinux=permissive
10. Reboot into fastboot mode
11. Flash modified boot image
12. Reboot to OOS
13. Install the Magisk Manager APK

Is it safe?
Do you dirty flash open beta 25?
Why need I modifyed the boot. img? Why don't modifyeed it the Magisk for me?
Sent from my Pixel 2XL using XDA-Developers Legacy app

papzi57 said:
Is it safe?
Do you dirty flash open beta 25?
Why need I modifyed the boot. img? Why don't modifyeed it the Magisk for me?
Click to expand...
Click to collapse
I am not able to tell you how safe this method is.
Yes, i did a dirty flash of OOS Open Beta 25, but some apps lost their data (Jodel, photoTAN, ...) but not Google Authenticator :fingers-crossed:
I think the modification of the boot.img is device-specific. I can not tell you details about this because i don't know that either.
There might be another way to set selinux=permissive as recently described in this thread, but your bootloader need to allow the following command:
Code:
fastboot oem selinux permissive
If you are able to perform this command in fastboot mode, maybe you don't need to modify the boot.img manually. Just reboot to fastboot mode after the installation of Magisk in TWRP and type that command.

davidlueder said:
This worked for me too, but maybe some other users need more information on the boot partition
Oreo compatible TWRP: Download (Credits: @akhilnarang)
OOS Open Beta 25: Download (Official OnePlus Website)
Magisk 14.3 (Beta): Download (stolen from this thread)
Magisk Manager 5.4.0: Download (GitHub)
You are responsible, if it kills your device, but this was my way:
1. Full Backup in TWRP
2. Reboot into Fastboot Mode
3. Flash Oreo compatible TWRP
4. Use Volume Keys to select and boot into recovery
5. Install OOS Open Beta 25
Then i did a reboot and Steps 1&2 again but i don't think this is required.
6. Install Magisk 14.3 Beta
7. Create an image of the boot partition
Code:
adb shell
dd if=/dev/block/sde18 of=/sdcard/boot.img
exit
8. Copy the boot.img file to your computer
9. Open this file in a hex exitor, add the following text after "buildvariant=user" (image in baskaflyfer's answer) and save the file:
Code:
androidboot.selinux=permissive
10. Reboot into fastboot mode
11. Flash modified boot image
12. Reboot to OOS
13. Install the Magisk Manager APK
Click to expand...
Click to collapse
Is Magisk stable? Did you try any modules and which ones? Are they working fine?

ishanp said:
Is Magisk stable? Did you try any modules and which ones? Are they working fine?
Click to expand...
Click to collapse
I did not try any modules but multiple apps that require root: AirDroid, AFWall+, Amaze (Root enabled). They're working fine.
Additionally, this magically fixed my ctsProfile. Magisk's SafetyNet-Test is successful on my device now.
Edit: I was able to install ViPER4Android FX for Magisk v14+ (v2.5.0.5) by ShadySquirrel without any errors, but driver status tells me that it is not enabled. Maybe because they officially just support ROMs up to Android Lollipop.

davidlueder said:
Edit: I was able to install ViPER4Android FX for Magisk v14+ (v2.5.0.5) by ShadySquirrel without any errors, but driver status tells me that it is not enabled. Maybe because they officially just support ROMs up to Android Lollipop.
Click to expand...
Click to collapse
Try in terminal after boot:
Code:
su
setenforce 0
Restart ViperFX app. Please report, I am on SuperSU but will jump the moment my fav modules start working
Also I'm using Viper4Arise (bundled with Magnum Opus) right now. If that didn't work you can use that.

[Guide]Magisk Modules Disabler for Modules gone wrong

Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/showthread.php?t=2239421
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work. Dot files are hidden files so if your root explorer can't see hidden files, run the "Remove disable_magisk" bat file in ADB.
1. Same as above but use the overlay.dcoreonly1.zip
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
****************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixel3xl.img
You will boot with root but modules disabled. After you remove the offending module you will need to go to /cache folder and delete the .disable_magisk file before your modules will work.
fastboot boot image-newpixel3xlRemove.img
This one should remove magisk and all modules, then reboot and magisk should reinstall itself (ask to install necessary binaries). This is what osm0sis uses to recover from failed flashes. See this post:
https://forum.xda-developers.com/pi...odules-disabler-booting-magisk-t3976625/page2
Images are in this common folder. Pick the appropriate image for your phone.
6-4-20
https://www.androidfilehost.com/?w=files&flid=313291

Looking forward to this, Tulsa. Will be a real lifesaver and game changer.

sliding_billy said:
Looking forward to this, Tulsa. Will be a real lifesaver and game changer.
Click to expand...
Click to collapse
It's official. It works.

Tulsadiver said:
It's official. It works.
Click to expand...
Click to collapse
You are going to make a lot of people (who "forget" to disable the modules before update) very thankful.

sliding_billy said:
You are going to make a lot of people (who "forget" to disable the modules before update) very thankful.
Click to expand...
Click to collapse
I'm one of those, lol! Also, with the nutty stuff I try, I will be able to get by without a factory reset all the time

Tulsadiver said:
I'm one of those, lol! Also, with the nutty stuff I try, I will be able to get by without a factory reset all the time
Click to expand...
Click to collapse
This link worked, but the one on the Pixel 3 page results in a Mega decryption key error.

sliding_billy said:
This link worked, but the one on the Pixel 3 page results in a Mega decryption key error.
Click to expand...
Click to collapse
I pasted it again. Hopefully it works now.

Tulsadiver said:
I pasted it again. Hopefully it works now.
Click to expand...
Click to collapse
It works!

Thank you!!!!

Latest magisk canary added an adb command to remove modules if bootlopps happens ?

DvLAx3l said:
Latest magisk canary added an adb command to remove modules if bootlopps happens
Click to expand...
Click to collapse
That's what I heard. Do you know the steps on how it works? You flash a module and you bootloop. What do you do next?

Tulsadiver said:
That's what I heard. Do you know the steps on how it works? You flash a module and you bootloop. What do you do next?
Click to expand...
Click to collapse
Didn't try yet, I was searching on topjohnwu GitHub but I don't find nothing, it's in the changelog but I don't know ?

DvLAx3l said:
Didn't try yet, I was searching on topjohnwu GitHub but I don't find nothing, it's in the changelog but I don't know
Click to expand...
Click to collapse
Well, if it's an ADB fix, a person is going to have to, at the very least, flash boot.img (though probably system images depending on what you flashed), reboot without root. Enable the ADB mode, flash ADB commands, and reboot. Remove bad modules. Then, go back and root again.
Seems simpler to just flash the modded image-new.img, reboot with root, remove modules (with ADB if you like) and reboot.
Edit: what would be cool is an option to patch a boot.img in core-only mode, right from Magisk manager, where the other option is to patch the boot.img. All that would be needed on John's part is an edited init file in that option. That's the only difference.

Thanks for this! I could've really used this image a few times in the past...

Face_Plant said:
Thanks for this! I could've really used this image a few times in the past...
Click to expand...
Click to collapse
You and me both, buddy!

Got in to a bootloop situation with Bromite systemless webview module. I restored stock boot image and patched it with the latest canary build (the one with 'recovery mode' checked under advanced settings) and bootlooped again. I flashed this file, got in with magisk working, disabled the offending module, patched the boot image without recovery mode, then flashed the patched boot image and everything is up and running! Thanks for the help!

Ok thanks for this but after rebooting from home screen even if I disable/remove bad mods from magisk I still get rr's/boot loops. Would I need to uninstall magisk completely then and start fresh or what?

Jiggs82 said:
Ok thanks for this but after rebooting from home screen even if I disable/remove bad mods from magisk I still get rr's/boot loops. Would I need to uninstall magisk completely then and start fresh or what?
Click to expand...
Click to collapse
Can you open magisk manager? If so, uninstall magisk from there.
If not, once booted in core-only mode, unzip the contents of this zip in a folder you can use ADB from and run the bat file. It'll push the .disable_magisk file to the cache folder and totally disable any module activity.

Tulsadiver said:
Can you open magisk manager? If so, uninstall magisk from there.
If not, once booted in core-only mode, unzip the contents of this zip in a folder you can use ADB from and run the bat file. It'll push the .disable_magisk file to the cache folder and totally disable any module activity.
Click to expand...
Click to collapse
Yes I was able to open magisk but even if I uninstalled it I still had this weird bootlloop so before I saw this message I ended up just flashing factory 10 image clean this time just to be sure everything would flash/install successfully and luckily they did lol but thanks anyways and I will hold onto to these files for future references:good:

would the modded boot img that disables modules work for the pixel 3 as well?

10.0.6 OTA filenames HD65BA

I noticed a system update was announced, grabbed the data from ADB and sharing them here.
Not sure how usefull this is, but perhaps someone can figure out the URL that hosts them and share the downloads.
I have not been able to find the url, but you can copy the file from .Ota directory on the sdcard
OnePlus7TOxygen_14.E.08_OTA_006-008_patch_1911061922_db44361aba217b4.zip
OnePlus7TOxygen_14.E.08_OTA_008_all_1911061922_1846b.zip
Task thread startDownload currentType:http patchFile:id:0 fid:0 name: OnePlus7TOxygen_14.E.08_OTA_006-008_patch_1911061922_db44361aba217b4.zip md5:8746fcd2a75dd7abe4bdf91c4c47f411 size:186116097 downloadedSize:0 downloadFinished:0speed0extract#OnePlus 7T Oxygen OS 10.0.6.HD65BA
Task thread startDownload currentType:http patchFile:id:0 fid:0 name: OnePlus7TOxygen_14.E.08_OTA_008_all_1911061922_1846b.zip md5:d9846a7a941786fed60ad54a0a2b096c size:2710484155 downloadedSize:0 downloadFinished:0speed0extract#OnePlus 7T Oxygen OS 10.0.6.HD65BA

https://otafsg1.h2os.com/patch/amaz...ygen_14.E.08_OTA_008_all_1911061922_1846b.zip

supaflyx3 said:
https://otafsg1.h2os.com/patch/amaz...ygen_14.E.08_OTA_008_all_1911061922_1846b.zip
Click to expand...
Click to collapse
Thx
Now we need someone to extract boot image from this ota ,so we can magisk patch it
No patched boot image for 10.0.6 global around yet

Why you need patched_boot.img?
I have downloaded ota file, put it into root directory, install it through setting>System update>local update, open magisk and made "Install to inactive slot (after ota), reboot, once phone started I open magisk and made "Direct install (Recommend)". Everything is fine.
If it's mater, my phone is unlocked and rooted.

You find it her
spoonymoon said:
Thx
Now we need someone to extract boot image from this ota ,so we can magisk patch it
No patched boot image for 10.0.6 global around yet
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7t/how-to/pre-rooted-boot-image-op7t-european-t4006559

MICRO-G LineageOS 17.1 - Xiaomi A2 Lite - Development Only

Hello,
Its me reujea0/packmaan7144/hukad,
I have been asked by many to build a microG version of lineageOS. I do not plan to run this build, as I prefer gapps, so all the testing/features/fixes will depend on you and your logs. This build should behave exactly the same as my other (standart) los build. This thread is for developement only, meaning that it will be used until I feel that the rom is stable enough and make a propper thread for it. Of course i am not accountable if this blows up your device.
Here is the link to the first version: https://github.com/a-huk/otaserver/...ge-17.1-20200917-UNOFFICIAL-daisy_micro-g.zip
Second version with actual microG: https://github.com/a-huk/otaserver/...ge-17.1-20201012-UNOFFICIAL-daisy_migro-g.zip
Always latest version: https://github.com/a-huk/otaserver/releases/download/09/lineage-17.1-20201124-UNOFFICIAL-daisy_micro-g.zip
Here are the sources:
Device: https://github.com/a-huk/device_xiaomi_daisy
Kernel: https://github.com/a-huk/kernel_xiaomi_daisy
Vendor: https://github.com/a-huk/vendor_daisy

Not quite microG LineageOS, just signature spoofing enabled.

celrau said:
Not quite microG LineageOS, just signature spoofing enabled.
Click to expand...
Click to collapse
OK my bad, I did not fully understand how to bake in micro-g. I'll make sure it is present in the next build/OTA

reujea0 said:
OK my bad, I did not fully understand how to bake in micro-g. I'll make sure it is present in the next build/OTA
Click to expand...
Click to collapse
I think the easiest would be to integrate the minimal or minimalAP configuration from these guys. It works really good for me

New version and OTA is out, hopefully this is fully working with proper microG and what you have been asking for

reujea0 said:
New version and OTA is out, hopefully this is fully working with proper microG and what you have been asking for
Click to expand...
Click to collapse
Hey, I just flashed it and Phonesky was not properly initialized for sig spoofing, I achieved that by this command:
Code:
pm grant --user 0 com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE
And thanks for adding microG.

Ok, so normally the november ota is out, let me know if it all works and if you have the right security patch

reujea0 said:
Ok, so normally the november ota is out, let me know if it all works and if you have the right security patch
Click to expand...
Click to collapse
All is good with the new ota.

Out of interest, what are the exact differences between this rom and the other version? Like what parts of microG are installed, in addition to the signature spoofing?

julianfairfax said:
Out of interest, what are the exact differences between this rom and the other version? Like what parts of microG are installed, in addition to the signature spoofing?
Click to expand...
Click to collapse
If my memory serves me right :
GmsCore GsfProxy FakeStore MozillaNlpBackend NominatimNlpBackend com.google.android.maps.jar FDroid FDroidPrivilegedExtension

reujea0 said:
If my memory serves me right :
GmsCore GsfProxy FakeStore MozillaNlpBackend NominatimNlpBackend com.google.android.maps.jar FDroid FDroidPrivilegedExtension
Click to expand...
Click to collapse
Does this mean Google Maps is installed by default or is it some kind of system component required to use it, that would be otherwise uninstallable as a user app? It seems to be this: https://github.com/microg/android_frameworks_mapsv1?

The ROM is working great and I feel better without Google (well, their closed source apps, still need to connect to their servers ofc). Thanks for developing this!

I've tried installing the latest version of this rom on my Xiaomi Mi A2 Lite. Besides following the standard LineageOS instructions, I've also installed TWRP (just in case). After running "adb sideload" I got this error:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch)
Updater process ended with ERROR: 1.
Any clue about what should I do?

mirluin said:
I've tried installing the latest version of this rom on my Xiaomi Mi A2 Lite. Besides following the standard LineageOS instructions, I've also installed TWRP (just in case). After running "adb sideload" I got this error:
Error applying update: 26 (ErrorCode::kDownloadMetadataSignatureMismatch)
Updater process ended with ERROR: 1.
Any clue about what should I do?
Click to expand...
Click to collapse
Which TWRP are you using? It is also better to flash directly than to sideload. Try this TWRP https://github.com/LinkBoi00/twrp_d...rc6_2/twrp-3.4.0_9-rc6_2-unofficial-daisy.img

reujea0 said:
Which TWRP are you using? It is also better to flash directly than to sideload. Try this TWRP https://github.com/LinkBoi00/twrp_d...rc6_2/twrp-3.4.0_9-rc6_2-unofficial-daisy.img
Click to expand...
Click to collapse
I tried with twrp-3.5.0_9-dees_troy-daisy.img
I'll try again with your suggested version.
What do you mean by flash directly? Adb pushing the image to the sdcard and install from TWRP?
Sorry for the question but I'm pretty new to flashing and stuff. Thanks.

mirluin said:
I tried with twrp-3.5.0_9-dees_troy-daisy.img
I'll try again with your suggested version.
What do you mean by flash directly? Adb pushing the image to the sdcard and install from TWRP?
Sorry for the question but I'm pretty new to flashing and stuff. Thanks.
Click to expand...
Click to collapse
Deestroy twrp is broken, so use the one linked. You can either adb push it or it should simply show up in This Pc as storage on your computer so just drag it in there. Ans then flash directly from inside twrp and your phon'es or sdcard storage.

reujea0 said:
Deestroy twrp is broken, so use the one linked. You can either adb push it or it should simply show up in This Pc as storage on your computer so just drag it in there. Ans then flash directly from inside twrp and your phon'es or sdcard storage.
Click to expand...
Click to collapse
Tried again with twrp-3.5.0_9-1-daisy-unofficial.img and it failed with a different error:
Zip signature verification failed! Error installing zip file '...
Retrying removing the zip signature verification from TWRP installation lead to flashing... and apparently it worked.
Should I be concerned about the missing signature verification?

mirluin said:
Tried again with twrp-3.5.0_9-1-daisy-unofficial.img and it failed with a different error:
Zip signature verification failed! Error installing zip file '...
Retrying removing the zip signature verification from TWRP installation lead to flashing... and apparently it worked.
Should I be concerned about the missing signature verification?
Click to expand...
Click to collapse
Not at all

reujea0 said:
Not at all
Click to expand...
Click to collapse
Thank you for the support!

These are probably unrelated issues but I'm just wondering if there's anything I can do to fix them: I have dark mode set to turn on/off automatically but most of the time it doesn't actually work, and when I used the regular version of this rom I was able to swipe on the keyboard to type, but it seems that doesn't work on this version?