Related
Hey everyone,
Currently am running the Jan 5th OTA, rooted with magisk, using xposed, running the updated stock kernel and am on TWRP 3.2.1.
Should I be alright flashing the factory image with the -w removed? Could I just skip flashing the boot.img + flash the kernel seperately? Also, since TWRP recoveries are funky on Pixel atm, will this newest patch play nicely with TWRP?
Thank you in advance
I had issues booting twrp after sideloading the ota. Screen went black til battery died. Even after flashing twrp installer. Magisk wasn't installing via zip either
Download the entire factory image, unzip, open the folder and you'll see a "flash-all.bat" (supposed you're on windows, otherwise the other 2 script files are for mac and linux)
Edit it with notepad (or what you prefer) and remove the "-w" from the latest line, then save it.
Go in fastboot mode, then launch your edited flash-all script file. This will flash the new factory image but without wiping your device, like an ota, but without all the troubles ota has, then it will auto reboot.
Copy on phone magisk and/or kernel
Now disable lockscreen security, then go in fastboot again. Type in cmd "fastboot boot <twrp.img>" (or what it is called)
When terminal gives you "OKAY" unplug device and you should be in twrp. Flash the zips you've choosen and then reboot and re-enable lockscreen pin, password etc..
Magisk and kernel should now work, I did it just now without any problem.
@TENN3R you did try unlock from twrp when you were all done?
I've dirty flashed like this before many a times... but now I can't decrypt data in TWRP 3.2.1.
I disabled password, did full ota script without -w and flashed twrp and magisk like normal, booted up and set the password. Done this a few times with different variables but nothing is changing the fact that twrp won't recognize the password while the system does.
Anyone else confirm working or not for them? Thanks.
TENN3R said:
Download the entire factory image, unzip, open the folder and you'll see a "flash-all.bat" (supposed you're on windows, otherwise the other 2 script files are for mac and linux)
Edit it with notepad (or what you prefer) and remove the "-w" from the latest line, then save it.
Go in fastboot mode, then launch your edited flash-all script file. This will flash the new factory image but without wiping your device, like an ota, but without all the troubles ota has, then it will auto reboot.
Copy on phone magisk and/or kernel
Now disable lockscreen security, then go in fastboot again. Type in cmd "fastboot boot <twrp.img>" (or what it is called)
When terminal gives you "OKAY" unplug device and you should be in twrp. Flash the zips you've choosen and then reboot and re-enable lockscreen pin, password etc..
Magisk and kernel should now work, I did it just now without any problem.
Click to expand...
Click to collapse
pangolin.rollin said:
@TENN3R you did try unlock from twrp when you were all done?
I've dirty flashed like this before many a times... but now I can't decrypt data in TWRP 3.2.1.
I disabled password, did full ota script without -w and flashed twrp and magisk like normal, booted up and set the password. Done this a few times with different variables but nothing is changing the fact that twrp won't recognize the password while the system does.
Anyone else confirm working or not for them? Thanks.
Click to expand...
Click to collapse
If you removed lockscreen security you should not even get password in twrp, just main screen with wipe, flash etc..
Put your lockscreen security on "swipe" then check if lockscreen method effectively changed before going into twrp
Sent from my Google Pixel using XDA Labs
TENN3R said:
Download the entire factory image, unzip, open the folder and you'll see a "flash-all.bat" (supposed you're on windows, otherwise the other 2 script files are for mac and linux).
Click to expand...
Click to collapse
were did you find this factory image? I only see the ota-zip (pm: sailfish)
henk-jan said:
were did you find this factory image? I only see the ota-zip
Click to expand...
Click to collapse
https://developers.google.com/android/images
Section pixel sailfish, the latest 8.1.0 february
Sent from my Google Pixel using XDA Labs
TENN3R said:
https://developers.google.com/android/images
Section pixel sailfish, the latest 8.1.0 february
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
I know this site, but it's only the ota, not factory
Edit: I downloaded it again and now it's ok. Thanks
I think you misunderstood me. You used to be able to use your passcode to decrypt in TWRP (was fixed initially in 3.2.1).
After doing a FULL WIPE and fresh install without password, adding one after setup breaks TWRP decryption.
At this point unless someone corrects me with proof or a fix (I did a fresh install and it's broken) consider TWRP decryption broken again.
TENN3R said:
If you removed lockscreen security you should not even get password in twrp, just main screen with wipe, flash etc..
Put your lockscreen security on "swipe" then check if lockscreen method effectively changed before going into twrp
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
pangolin.rollin said:
I think you misunderstood me. You used to be able to use your passcode to decrypt in TWRP (was fixed initially in 3.2.1).
After doing a FULL WIPE and fresh install without password, adding one after setup breaks TWRP decryption.
At this point unless someone corrects me with proof or a fix (I did a fresh install and it's broken) consider TWRP decryption broken again.
Click to expand...
Click to collapse
OP started with: dirty flash the febr. OTA. So the answer is: no it can't without loosing TWRP. Is that right?
Seems so. The only way I can use TWRP atm is to disable any security/passwords etc.
henk-jan said:
OP started with: dirty flash the febr. OTA. So the answer is: no it can't without loosing TWRP. Is that right?
Click to expand...
Click to collapse
2x speed video of my using FlashFire to update the Pixel to the February Android 8.1 update, plus flashing ElementalX custom kernel v3.02 and Magisk v14.2: https://photos.app.goo.gl/4IVeBt8DFTQACHJi2
You have to be on Magisk 14.2 (not a higher version) to begin with, though, so if you're not, disregard this.
roirraW "edor" ehT said:
2x speed video of my using FlashFire to update the Pixel to the February Android 8.1 update, plus flashing ElementalX custom kernel v3.02 and Magisk v14.2: https://photos.app.goo.gl/4IVeBt8DFTQACHJi2
You have to be on Magisk 14.2 (not a higher version) to begin with, though, so if you're not, disregard this.
Click to expand...
Click to collapse
erm and what if we are on 14.3?
mark2410 said:
erm and what if we are on 14.3?
Click to expand...
Click to collapse
Since I haven't tried 14.3, if 14.3 doesn't work with FlashFire, then downgrade to 14.2.
TENN3R said:
Download the entire factory image, unzip, open the folder and you'll see a "flash-all.bat" (supposed you're on windows, otherwise the other 2 script files are for mac and linux)
Edit it with notepad (or what you prefer) and remove the "-w" from the latest line, then save it.
Go in fastboot mode, then launch your edited flash-all script file. This will flash the new factory image but without wiping your device, like an ota, but without all the troubles ota has, then it will auto reboot.
Copy on phone magisk and/or kernel
Now disable lockscreen security, then go in fastboot again. Type in cmd "fastboot boot <twrp.img>" (or what it is called)
When terminal gives you "OKAY" unplug device and you should be in twrp. Flash the zips you've choosen and then reboot and re-enable lockscreen pin, password etc..
Magisk and kernel should now work, I did it just now without any problem.
Click to expand...
Click to collapse
Confirmed working on march update too :good:
Hello Guys,
We have Only 1 Twrp Recovery. And u guys Might be Pissed that it has Encryption. But the Encryption Problem Is Not in the Twrp, it is due to ROM.
Guide to Remove Encryption
1. Boot to Twrp Recovery
2. Do a Factory Reset, Internal Storage Wipe
3. Reboot to Recovery Again
4. Hurray We have Removed the Encryption
F.A.Q'S
1. This Method Removes All Ur Files Which are there in Your Internal Storage.
2. I wont be responsible For the Bricks u Do For Your Device
Do Give a Thanks If U Like My Work
Reserved
ChalapathiRevanth said:
Reserved
Click to expand...
Click to collapse
pls can you tell me what this settings look like after decryption
Nothing Related to Settings
SkaboXD said:
pls can you tell me what this settings look like after decryption
Click to expand...
Click to collapse
That's a Twrp Decryption which we find in Almost All Mtk Devices Running MM, Nougat, Oreo.
Don't Worry, nothing is related to Ur settings/security
ChalapathiRevanth said:
That's a Twrp Decryption which we find in Almost All Mtk Devices Running MM, Nougat, Oreo.
Don't Worry, nothing is related to Ur settings/security
Click to expand...
Click to collapse
no,no,no i know that, i just want to know did encryption setting changed to decrypted.
What do we get with this method?
I would like to see if we can remove the system ones, and gain some performance on that.
Sent from my TA-1032 using Tapatalk
Did not Get you!
SkaboXD said:
no,no,no i know that, i just want to know did encryption setting changed to decrypted.
Click to expand...
Click to collapse
PM Me
Nothing Related To Performance!
Nikola Jovanovic said:
What do we get with this method?
I would like to see if we can remove the system ones, and gain some performance on that.
Sent from my TA-1032 using Tapatalk
Click to expand...
Click to collapse
This Is nothing related to performance, it just removes encryption in Twrp Recovery. So we can see the Internal Storage in Twrp Recovery.
If u Want to Get Performance, Remove the ****ty Apps, which are present with System App Remover!
I can confirm that this method works, i didn't know that it was that simple.
Quick question, fellas;
Mine tarp is ported from P9. Is this is the only one recovery around for our device?
What about full tarp backup and format /system and /data? Is there any chance for brick? I've rooted with Magical, but because of the encryption (I cannot see internal memory and /data) I doesn't flash any modules. Thanks for the future info!
MoHuToP said:
Quick question, fellas;
Mine tarp is ported from P9. Is this is the only one recovery around for our device?
What about full tarp backup and format /system and /data? Is there any chance for brick? I've rooted with Magical, but because of the encryption (I cannot see internal memory and /data) I doesn't flash any modules. Thanks for the future info!
Click to expand...
Click to collapse
yeah, that is only recovery that works, you can brick device if you wipe /system. You should wipe /system only when you are doing full wipe (flashing new ROM). You can wipe /data but it will remove existing non-system apps. I never did twrp backup so you can try.
Does the twrp encryption removal survive ota updates and oreo beta update?
Device Specific Comments
MoHuToP said:
Quick question, fellas;
Mine tarp is ported from P9. Is this is the only one recovery around for our device?
What about full tarp backup and format /system and /data? Is there any chance for brick? I've rooted with Magical, but because of the encryption (I cannot see internal memory and /data) I doesn't flash any modules. Thanks for the future info!
Click to expand...
Click to collapse
However Only Device Specific Comments, SkaboXD
I hope This Guy Solved Your Problem
redweaver said:
Does the twrp encryption removal survive ota updates and oreo beta update?
Click to expand...
Click to collapse
I don't think so because every .nb0 file that i flashed have encryption enabled. But after flashing new rom, you can immediately factory reset when you boot to rom to prevent losing data.
---------- Post added at 08:27 PM ---------- Previous post was at 08:25 PM ----------
@MoHuToP
ok, i tried full twrp backup, but it stops on system image backup, it stoped around 60%. Backup have 11.5 GB (really huge isn't it).
DELETED
Ok, this method worked on Nougat with SuperSU because SuperSU patched fstab and file contexts successfully. It doesn't work on Oreo because Oreo now have plat_file_contexts and non_plat_file contexts. SuperSU needs to be updated to patch these files succesufully or we need to manually patch it so we can remove encryption.
Just to update this guide: This works only on Nougat. You need to have installed twrp and unlocked bootloader. Magisk doesn't work with this method because it doesn't patch fstab and file contents file so you need to uninstall it by going to Magisk app and clicking uninstall. After that go to TWRP, flash unSu > stock boot.img. You can flash Magisk after that with removed encryption.
Steps:
1. Flash SuperSU 2.79 stable with TWRP
2. Reboot your phone to system.
3. Reboot to TWRP again.
4. Choose Wipe > Swipe to Factory reset
5. Choose Wipe > Advanced > Internal Storage
Now you wiped Data, Cache, Dalvik cache and Internal Storage.
Your phone will have removed encryption now.
If you want Magisk, just flash unSu script > stock boot.img > Magisk
If you update your phone, it will encrypt your phone again so you need to repeat steps again.
I have redmi note 5 mec7s and i instal global stable 9.5.13.0
now phone booting to mesage "encrypting don't reboot your phone" and goes to mi recovery and bootloop
if a make wipe then again booting to mesage "encrypting don't reboot your phone" and goes to mi recovery
how that i remove encrypting from adb or fastboot ?
xabaras666 said:
I have redmi note 5 mec7s and i instal global stable 9.5.13.0
now phone booting to mesage "encrypting don't reboot your phone" and goes to mi recovery and bootloop
if a make wipe then again booting to mesage "encrypting don't reboot your phone" and goes to mi recovery
how that i remove encrypting from adb or fastboot ?
Click to expand...
Click to collapse
This is only for the NOKIA 3 - if you have tried this on a different device there could be the possibility of Bricking it, let's hope not.
I suggest going to your own device forum for assistance.
I have reformatted and factory resetted many times but the issue keeps coming back after I boot into system. To clarify, my steps were to reformat inside the wipe section, boot into recovery and check to see there's no encryption, and then boot back to system to install magisk with the manager app. I have tried adding a factory reset to that process, but that won't work either. My TWRP is 3.2.1-0 and I will try to update it and see if it works. Also, sorry if I reply slow.
I went to reload 5.1.11 ..I think it might be because I forgot to remove my security features now keeps rebooting to TWPR
do I have to do a compete wipe now....or is there a simple method ?? Thanks for the help!
Did you have magisk installed? Did you install it again after flashing full ota and twrp?
ImSpiderman said:
Did you have magisk installed? Did you install it again after flashing full ota and twrp?
Click to expand...
Click to collapse
Yes I followed the guide here.. full rom, TWRP installer, reboot to recovery, Magisk 16.4 reboot system..........boots back to TWRP
double post
skyeking69 said:
Yes I followed the guide here.. full rom, TWRP installer, reboot to recovery, Magisk 16.4 reboot system..........boots back to TWRP
Click to expand...
Click to collapse
Strange, that happened to me because i didn't Remember to reflash magisk...wait for someone else to answer but if it isn't a big deal for you i'll just factory reset, it's always good to do after a new update
ImSpiderman said:
Strange, that happened to me because i didn't Remember to reflash magisk...wait for someone else to answer but if it isn't a big deal for you i'll just factory reset, it's always good to do after a new update
Click to expand...
Click to collapse
Yeah I tried that too everything except internal storage...just wondering if I have to wipe that as well ??
skyeking69 said:
Yeah I tried that too everything except internal storage...just wondering if I have to wipe that as well ??
Click to expand...
Click to collapse
No you don't have to
ImSpiderman said:
No you don't have to
Click to expand...
Click to collapse
Well I guess I'll wait for more ideas..... Or might just wipe internal and see what happens...
skyeking69 said:
Well I guess I'll wait for more ideas..... Or might just wipe internal and see what happens...
Click to expand...
Click to collapse
That didn't work? Really strange tho
See this. This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
Icon credit: Twitter
Gradusr said:
See this. This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
Icon credit: Twitter
Click to expand...
Click to collapse
Thanks but I really don't understand this....first I don't know if encryption is on ? Don't think I have turned it off...2nd 3.2.2.0 worked fine for me before..I installed 5.1.9 and 5.1.11 with no problems.....it was when I tried to reinstall 5.1.11 and forgot to remove security features this happened now?
How old is this thread about TWRP 3.2.2.0 ?
It happened to me since the first time. what i do is wipe everything except internal, flash rom, flash twrp, reboot twrp, boot system, and then after set up, reboot recovery and flash magisk.
I dont know what is the problem ive never used a security feature.(maybe thats my problem)
WOS17 said:
It happened to me since the first time. what i do is wipe everything except internal, flash rom, flash twrp, reboot twrp, boot system, and then after set up, reboot recovery and flash magisk.
I dont know what is the problem ive never used a security feature.(maybe thats my problem)
Click to expand...
Click to collapse
I'll give that a try...... you have no pin or fingerprint or face unlock setup ??
If you have face unlock and or pin than you have issues with the new twrp reed this article , I have posted than you understand it.
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
skyeking69 said:
I'll give that a try...... you have no pin or fingerprint or face unlock setup ??
Click to expand...
Click to collapse
No, any security just double tap to wake.
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
which TWRP version are you using? what Ive read is Magisk 16.7 has some problems like the pop up that say you have to contact your manufacturer
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
Thanks..I'll try that first....the TWRP I have is 3.2.2.0 from official page ( I think ?) I'll try 16.7 and see what happens..
WOS17 said:
No, any security just double tap to wake.
which TWRP version are you using? what Ive read is Magisk 16.7 has some problems like the pop up that say you have to contact your manufacturer
Click to expand...
Click to collapse
I'm using 3.2.2.0 which was working fine.....the guy below tells me to use 16.7 Magisk???? Geez not sure now ?
Gradusr said:
If you have face unlock and or pin than you have issues with the new twrp reed this article , I have posted than you understand it.
Click to expand...
Click to collapse
The thing is TWRP 3.2.2.0 does ask me to enter my pin code then goes to the options page...install, wipe, backup,restore...etc...
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
Geez ...now when I go to reboot to recovery it gives me a warning " No OS installed, are you sure you want to reboot?? " what do I do now ??
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Maj3sty said:
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
Click to expand...
Click to collapse
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Voodoojonny said:
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Click to expand...
Click to collapse
I tried it and doesnt work. It seems the module changed any files in system(via root).
wenna.speedy said:
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
Click to expand...
Click to collapse
Nice try, but looks like you are not the only person with the same issue! I'm using Jetaudio and I have great sound with my JBL (Bluetooth) & Sennheiser wired headsets. I'm pass!!!
Mi A2 Lite using Tapatalk
lbsilva said:
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Click to expand...
Click to collapse
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Voodoojonny said:
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Click to expand...
Click to collapse
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
You can try install twrp and mount internal storage. I dont know if exists new version with working mounting.
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you try using MiFlashTool?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
Hmm, as told above, then your only option is a backup with twrp. If you can't decrypt data with twrp (after you installed it - not booting) you can try to boot to slot b - that sometimes help. Just select under reboot in twrp or type "fastboot set_active b"...
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
There is no wipe required, I just got caught in the loop as well.
Two things you need:
-TRWP installed
-Uninmod installed (magisk module remover)
1. If you are stuck in the loop, boot into fastboot,
- connect your pc and run ADB & fastboot cmd, run the command fastboot boot recovery.img(or your TRWP image) and run TRWP
2. Download Uninmod zip, transfer to phone. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
- Use TWRP to install Uninmod,
- remove the Notchkiller mod
- credits to veez21
3. find this file overlays.list and delete it from /data/resource-cache/overlays.list https://github.com/Magisk-Modules-Repo/NotchBarKiller/issues/3
- credits to MatChung
Reboot and there was like a minute of delay on same boot screen, but then it should boot fine.
If you are not stuck in the loop but just installed the module:
-remove the module in magisk
-find the file and delete it.
TLDR: remove the Notchbarkiller mod and remove overlays.list file. Reboot!
Hope it works. It did for me. Poco F1
I flashed this madule last night and found that it break calls. Could not make and receive phone calls. Huawei P20 Pro with EMUI 8.1 running.
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
D1stRU3T0R said:
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
Click to expand...
Click to collapse
Written in the first post...
wenna.speedy said:
Written in the first post...
Click to expand...
Click to collapse
I know...
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
SnoopDoggyStyleDogg said:
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
Click to expand...
Click to collapse
UPDATE: This thread is a false alarm as I managed to install the module on the March update and the only crash I get is from google play services with no bootloop and everything working. Maybe the OP has another phone and except that a module that is on the Mi A2 Lite thread should work on any phone or he's done something wrong. I will attach some screenshots to confirm that the module is indeed working and OP's post is a false alarm for stock A2 Lite ROMs (No custom ROM and not other phones)
NOTE: As you can see in the YouTube screenshot there's no black back on the left side of the screen as it should be without the module installed
Hi all,
I'm presenting here my ROM for S10e (whose main thread is https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915 ).
It is generic, but it doesn't mean anything bad!
Pretty much every works, and this is my daily driver (Exynos variant).
What works:
- Camera
- Wifi
- 2G/3G/4G, including signal level
- Phone calls
- Fingerprint sensor
- Encryption
- Proximity sensor
What doesn't work
- VoLTE
- stock OneUI camera app
- MTP
You can install some modded Google Camera on it for acceptable Camera quality.
Download links:
- With included gapps
- Without included gapps
How to flash:
- Flash back latest stock ROM
- Extract the img.xz into .img
- Flash it to system partition using Heimdall: https://glassechidna.com.au/heimdall/
- Flash this to vbmeta partition https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img (also using Heimdall)
- Boot once. The device will reboot into recovery, that's okay! Just do a factory reset and boot to system again.
- If it didn't reboot into recovery on its own, that's not normal (perhas you have magisk installed?), but still reboot into recovery and do a factory reset.
- Enjoy!
Recommended after installing:
- Default Launcher is AOSP's. It sucks. You should really install another Launcher. I recommend and use Lawnchair
- Pretty much no Google app is preinstalled, only Play Store and Chrome. You'll probably want to install Google, Google Assistant apps, Gmail, ...
free post for me and myself
Support for G9700?
Could system.img possibly be flashed through recovery? And you could've made it a flashable zip, we have a pretty ok recovery when you flash multidisabler
DeHuMaNiZeD said:
Could system.img possibly be flashed through recovery?
Click to expand...
Click to collapse
Yes
And you could've made it a flashable zip, we have a pretty ok recovery when you flash multidisabler
Click to expand...
Click to collapse
TBH I recommend not to flash any disabler, they bring more issues than they fix.
Android security is already not ideal, disabling encryption sounds like a very bad idea
(And disabling dm-verity is totally useless, because when flashing a GSI it already is)
NisseGurra said:
Support for G9700?
Click to expand...
Click to collapse
Yes G9700 is supported, though bear in mind that since it's not the same device, you don't really have the same guarantees. I'll help you through your issues either way.
Ok, tested on G9700, latest stock rom installed (android 9).
TWRP with multidisabler installed, format data, reboot recovery. Install V120 gsi, reboot.
Boots nicely.
Findings: no autobrightness, slider ok tho. Wifi/BT/NFC ok. No MTP (as stated)
Dual sim ok, voice calls ok, data ok. 3.5 output ok
Edit: Best way to root?, addonsu-16.0-arm64-signed.zip?
im gonna try this right away
i have one simple question before trying does magisk work with this and can i just use a magisk pachted system
---------- Post added at 07:32 AM ---------- Previous post was at 07:16 AM ----------
To my knowledge s10e is A-only and you linked A/B. What's up with that?
Edit:// It seems it is not, I have no idea why treble testing app from app store does not detect, that it is A/B
mikk150 said:
To my knowledge s10e is A-only and you linked A/B. What's up with that?
Edit:// It seems it is not, I have no idea why treble testing app from app store does not detect, that it is A/B
Click to expand...
Click to collapse
In the true sense, it is A-only, it doesn't have seamless update.
The difference between A-only and A/B was that A/B included the init, while A-only didn't.
But since Pie, A-only also includes init, like A/B. I didn't update the naming convention (because it just gets even messier).
Hackintosh5 developed Treble Info ( https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=en_US ) to make things clearer.
Do you have PHH for Android 10 for this device?
vlubosh said:
Do you have PHH for Android 10 for this device?
Click to expand...
Click to collapse
It is still unstable, that's why I haven't shown it in this forum yet.
Do these steps apply to any devices? Or only specific models? I have an Elephone Soldier, and I notice different website have different procedures. Not sure which one is right. Thanks.
"How to flash:
- Flash back latest stock ROM
- Extract the img.xz into .img
- Flash it to system partition using Heimdall: https://glassechidna.com.au/heimdall/
- Flash this to vbmeta partition https://dl.google.com/developers/and...gsi/vbmeta.img (also using Heimdall)
- Boot once. The device will reboot into recovery, that's okay! Just do a factory reset and boot to system again.
- If it didn't reboot into recovery on its own, that's not normal (perhas you have magisk installed?), but still reboot into recovery and do a factory reset."
I just installed AOSP 9.0 v119 for my Elephone Soldier. I can confirm the system boots up, but there is no sound. (ie. ring tone, media, notification) None of these sound work.
One question guys. If i root my s10e and flash custom rom, and then if i want to back to full 100% stock rom, o just need to flash it with odin and everything will be same like before? All apps will work like samsung health and pay? Thanks
BratoMo225 said:
One question guys. If i root my s10e and flash custom rom, and then if i want to back to full 100% stock rom, o just need to flash it with odin and everything will be same like before? All apps will work like samsung health and pay? Thanks
Click to expand...
Click to collapse
No as I have heard. The knox fuse is a physical fuse which can never be reset so these apps will not work.