[FIXED] I edited my build.prop and its now bootlooping - OnePlus 6T Questions & Answers

Hi everyone.
I edited my build.prop. Because oneplus didn't update the 6T with the latest security patch, I edited it in the build.prop myself. It worked, but for some reason settings then changed back to 2020-7-1. But the build.prop said 2020-10-1. I re-edited and reboot. An boom, it just reboots to twrp. I tried using adb pull /system/build.prop, edit it back to 2020-7-1. it didn't work. I even tried using :
But it still didn't work. Is there any fix, i didn't prperly back up my whatsapp, so its important that i don't wipe and factory reset my 6T.
Any help will be great. My 6T is currently in the recovery (TWRP 3.4.0-2), I was on 10.3.5 with Magisk 20.4
The issue was simple. the build.prop setting for security patches are in 0000-00-00. So its 2020-10-01

Extreme_Ninja2099 said:
Hi everyone.
I edited my build.prop. Because oneplus didn't update the 6T with the latest security patch, I edited it in the build.prop myself. It worked, but for some reason settings then changed back to 2020-7-1. But the build.prop said 2020-10-1. I re-edited and reboot. An boom, it just reboots to twrp. I tried using adb pull /system/build.prop, edit it back to 2020-7-1. it didn't work. I even tried using :
But it still didn't work. Is there any fix, i didn't prperly back up my whatsapp, so its important that i don't wipe and factory reset my 6T.
Any help will be great. My 6T is currently in the recovery (TWRP 3.4.0-2), I was on 10.3.5 with Magisk 20.4
The issue was simple. the build.prop setting for security patches are in 0000-00-00. So its 2020-10-01
Click to expand...
Click to collapse
Editing build.prop doesn't do nothing for the security patch. It's just editing the string that is shown in settings. So editing is useless. So put there 1.1.21 and bam you have January 2021 patch? Actual patch is in the rom files and libs. You can never fix it without a source code which is not available. Source code should be fixed with google security fixes and recompiled.
Reinstall the rom dirty, that should fix your problem. Good luck.
Sent from my ONEPLUS A6013 using Tapatalk

DaOldMan said:
Editing build.prop doesn't do nothing for the security patch. It's just editing the string that is shown in settings. So editing is useless. So put there 1.1.21 and bam you have January 2021 patch? Actual patch is in the rom files and libs. You can never fix it without a source code which is not available. Source code should be fixed with google security fixes and recompiled.
Reinstall the rom dirty, that should fix your problem. Good luck.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply. But it already says that the issue has been fixed. I just pulled the build.prop and edited the security string to the proper format, done it now boots.

Related

edited build.prop now camera crashes.

Hi, I'm currently on rooted by Tenfar method A2017u locked bootloader. I edited build.prop to improve the ram management and it worked, unfortunately, as a side effect, camera randomly crashes with Camera has stopped. why does that happen and how do I fix it guys? :/ any ideas? thanks.
When you flashed twrp, did you swipe to allow system modifications?
Nik2424 said:
Hi, I'm currently on rooted by Tenfar method A2017u locked bootloader. I edited build.prop to improve the ram management and it worked, unfortunately, as a side effect, camera randomly crashes with Camera has stopped. why does that happen and how do I fix it guys? :/ any ideas? thanks.
Click to expand...
Click to collapse
I've already mentioned this in my thread along with a "fix". I'm not sure what changes you made to build.prop but from what I've seen so far, corruptions only happen when editing the pre-existing build.prop. When adding something to the build.prop, all is fine.

Disable signature verification for V20 specifically

I have
LG V20 H990DS, rooted, TWRP installed, custom kernel (as per dirtysanta post), xposed installed
Since installing xposed (might be coincidental) I can not install any app (either via Play Store or adb install. The error I get in logcat is:
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION: Failed reading classes.dex in [email protected]: META-INF/MANIFEST.MF has invalid digest for classes.dex in classes.dex]
I posted this in the n00b-friedly Q&A forum and someone suggested it was an issue with signatures, so I googled and there are ways to disable signature verification. Not sure if this is a wise thing to do, but I think i need to try. The problem is the solutions all require Lucky Patcher or some Xposed app. But I can't install any app.
So, knowing I am falling for the whole XY Problem, can anyone suggest a way of disabling signature verification (or indeed solving the actual problem) without re-flashing everything again. I am thinking of some V20-compatible flashable zip or something maybe???
In my opinion I would suggest to reflash, stay with stock kernel with Xposed. You don't want to go through all of this just to install an app when clearly something you flashed isn't working right
Right, I have been experimenting with all sorts to avoid reflashing but nothing worked so I reflashed, and... still not working.
Any other ideas?
interruptingcow said:
Right, I have been experimenting with all sorts to avoid reflashing but nothing worked so I reflashed, and... still not working.
Any other ideas?
Click to expand...
Click to collapse
When you mean reflashed, do you mean dirty or clean installation?
Still_living714 said:
When you mean reflashed, do you mean dirty or clean installation?
Click to expand...
Click to collapse
dirty. Am just preparing all the files now for a clean install which is only option left available as far as I can see. I wonder if a different kernel would help?
I have an update on this.
I did a totally clean wipe and re-root, which in itself had issues but eventually worked. All was working fine right up until I installed modded google play. Since then I get the same issue as mentioned. I uninstalled it and reverted to normal googple play but I still get the error. I guess I have sort of found the issue, and next time I won't install it.
So, any ideas on
1. Why I am getting the issue?
2. How to fix it without going through the re-root.
Thank you.
interruptingcow said:
I have an update on this.
I did a totally clean wipe and re-root, which in itself had issues but eventually worked. All was working fine right up until I installed modded google play. Since then I get the same issue as mentioned. I uninstalled it and reverted to normal googple play but I still get the error. I guess I have sort of found the issue, and next time I won't install it.
So, any ideas on
1. Why I am getting the issue?
2. How to fix it without going through the re-root.
Thank you.
Click to expand...
Click to collapse
I've had the same problem installing Modded playstore. For some reason Modded playstore works on all my devices except my V20. I would suggest giving up installing it as I did. Also why would you have to reroot?
Also why would you have to reroot?[/QUOTE said:
Because that is the only way I have found to be able to install any new apps. Otherwise I get errors similar to
PackageInstaller: Commit of session 1370272024 failed: Failed reading classes.dex in [email protected]: META-INF/MANIFEST.MF has invalid digest for classes.dex in classes.dex
Click to expand...
Click to collapse
Well I found the solution and a way of installing modded google play. Although I don't really understand the reason. As I was going to wipe the phone anyway I thought I would play around. So...
I tried to install modded google play - still same issue
From Lucky Patcher I removed patches from core.jar - suddenly I could install apps again.
I successfully installed modded google play - this needs Signature Verification True
I patched Signature Verification - modded google play works and I can install apps
So the issue was with the Lucky patcher "Disable .apk Signature Verification". When patched I got the dex error from my post. With it unpatched all works fine.
Thanks for all who helped.
does this still work? I seem to always end up with playstore not functioning correctly, shows as though the applications I purchased as not purchased; and in-app purchase emulation doesn't function?.... not sure if I'm following your instructions on removing core.jar but I tried removing it and instaling core patch to disable signiture verification through edxposed but I'm not sure???
Yes it still works fine. IAP and everything works as normal.
Lucky patcher -- Patch to Android -- Remove all patches from core.jar
Lucky Patcher -- Patch to Android -- Signature Verification status always True
Lucky Patcher -- Patch to Android -- Disable .apk signature verification
Lucky Patcher -- Patch to Android -- Disable Signature Verification in the pacvkage manager
interruptingcow said:
Yes it still works fine. IAP and everything works as normal.
Lucky patcher -- Patch to Android -- Remove all patches from core.jar
Lucky Patcher -- Patch to Android -- Signature Verification status always True
Lucky Patcher -- Patch to Android -- Disable .apk signature verification
Lucky Patcher -- Patch to Android -- Disable Signature Verification in the pacvkage manager
Click to expand...
Click to collapse
thanks for the reply and instructions...... I managed to get lp working(emulation and all) using either corepatch or the module for magisk.... but there's still something funky that either stops stuff from installing off playstore and/or not as apk's without resigning them; will try this method and see how it does in comparison....... unrelated question, any clue if m3u's work at all or if there's a method to get them to open in music players?(not sure if user issue or device issue)
Sorry I don't use m3u so I do not know.

need help!

My essential phone shows up as "pixel XL" in settings for device. I believe this is from using the Google framework magisk module. I have removed the module but it remains the same. This has caused me to not be able to receive OTA updates or use the stock camera app because it believes it's a different phone. Does anyone know how to fix this without flashing back to stock? I have already tried a build.prop editor but there was nothing there regarding the word pixel to change.
bschmidy10 said:
My essential phone shows up as "pixel XL" in settings for device. I believe this is from using the Google framework magisk module. I have removed the module but it remains the same. This has caused me to not be able to receive OTA updates or use the stock camera app because it believes it's a different phone. Does anyone know how to fix this without flashing back to stock? I have already tried a build.prop editor but there was nothing there regarding the word pixel to change.
Click to expand...
Click to collapse
Flash back to stock
Yeah. I got a Google security alert saying a pixel accessed my account. Changes PW just to be sure.
Sent from my PH-1 using XDA Labs
bschmidy10 said:
My essential phone shows up as "pixel XL" in settings for device. I believe this is from using the Google framework magisk module. I have removed the module but it remains the same. This has caused me to not be able to receive OTA updates or use the stock camera app because it believes it's a different phone. Does anyone know how to fix this without flashing back to stock? I have already tried a build.prop editor but there was nothing there regarding the word pixel to change.
Click to expand...
Click to collapse
I wonder what it reports to carrier ... would it mean we can get volte if carrier has approved Pixel XL? (he thinks without looking into volte at all)
sorry not much help to you though
It's pretty strange. Same thing happened to my one plus 3 but I was running a custom rom so I didn't care at all. I'm 90% sure it's from the Google framework magisk module. I have never owned an actual pixel but for instance in my Google play music authorized devices section it lists 4 PIXEL XL phones lol. They are all from my location upon my security checkup and like I said my phone thinks that's what it is so I don't have a concern about being hacked. Only thing I'm confused about is why did removing the module not resolve the issue... Or how did they do it in the first place so I can make a module to turn it back into an essential phone lol. Only thing I found from searching was a deprecated GitHub repo for the module.
I'll probably just give in and wipe everything and go back to stock. Been wanting to avoid that because of the convoluted process of flashing and rooting with A/B partitions. I read somewhere there was a new method to maintain TWRP now though? Does anyone know anything about that? Appreciate the input (even if it wasn't much help lol)
I'm not running the framework module.
But I did install the pixel sound effects.
Sent from my PH-1 using XDA Labs

July Security Happened Automatiically - Deleted Magisk

Well restarted my phone on the weekend and when it started up a notification showed it was being updated. I had automatic updates turned off. I checked and see I am now on July update.
Magisk manager is still installed but it says Magisk has been uninstalled. The strange this is that the Google Camera is still working.
Has anyone else had something similar happen?
Yes magisk and twrp has been removed
Yes it has happened to me too.
Twrp got removed from boot and also magisk was uninstalled.
Gcam app is also not working
Can anyone help me remove the gcam app from boot.
Thanks in advance
ludditefornow said:
Well restarted my phone on the weekend and when it started up a notification showed it was being updated. I had automatic updates turned off. I checked and see I am now on July update.
Magisk manager is still installed but it says Magisk has been uninstalled. The strange this is that the Google Camera is still working.
Has anyone else had something similar happen?
Click to expand...
Click to collapse
No, had updates turned off since early Oreo and its never updated 'automatically'.
Happened to me also. As it didn't behave like a normal update, I am wary of reinstalling magisk/twrp. Has anyone done it, can they post a link to the guide they used?
Thanks all
Sent from my Mi A1 using Tapatalk
I didnt have twrp installed, but i dontbthink i will bother with Magisk reinstall because gcam is still working.. only problem is that my Viper i stall has gone.. so if i get sick of the low volume through headphones, i will install magisk again
Have installed magisk - or at least have root acess, but magisk manager says it's not installed. Maybe I am doing something wrong. or is it a version release issue. Also is Cosmic Dan's twrp the best way to go with July release
Thanks
M

Cannot open SIM & Network settings / com.android.phone crashes after uptdate to OO10

Cannot open SIM & Network settings / com.android.phone crashes after uptdate to OO10
Device:
Rooted OP 6t, OxygenOS 10.3, stock recovery, Magisk 20.2, Magisk Manager 7.5.0
What did I do:
I updated from the last OxygenOS 9 Version to OxygenOS 10.3 by uninstalling magisk, restoring images and doing the manual update through the downloaded full image. Reinstall magisk. It all went well. First boot took a while but went through.
SIM was not recognised at all.
I've reset all network settings and cleared cache and data of com.android.phone.PhoneApp.
Found out here that its due to a call record magisk module which I uninstalled. Mobile data is working just fine since then.
I tried to uninstall magisk and reinstall it before rebooting in order to keep the possibility to keep root as I do not have twrp installed. (suggested here). I guess this is unrelated.
Issue:
I cannot access the SIM & Network Settings. When I try, the app com.android.phone crashes instantly.
Logs throw these warnings:
Code:
Unable to launch app com.android.phone/99901001 for broadcast Intent { act=android.telephony.action.CARRIER_CONFIG_CHANGED flg=0x15000010 (has extras) }: process is bad
Is there a way to check the carrier config or renew it?
Code:
Unable to launch app com.android.phone/99901001 for broadcast Intent { act=android.intent.action.SIM_STATE_CHANGED flg=0x5000010 (has extras) }: process is bad
Hows the SIM state changing?
and this Error:
Code:
Sending non-protected broadcast com.android.internal.telephony.ACTION_IMS_CAPABILITY_STATUS_CHANGE from system 1102:system/1000 pkg android
java.lang.Throwable
at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:15963)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:16666)
at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:15980)
at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:16808)
at android.app.ContextImpl.sendStickyBroadcastAsUser(ContextImpl.java:1422)
at com.android.server.TelephonyRegistry.broadcastImsCapabilityStatusChangeForPhoneId(TelephonyRegistry.java:2644)
at com.android.server.TelephonyRegistry.notifyImsCapabilityStatusChangeForPhoneId(TelephonyRegistry.java:2636)
at com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact(ITelephonyRegistry.java:964)
at android.os.Binder.execTransactInternal(Binder.java:1032)
at android.os.Binder.execTransact(Binder.java:1005)
I am not sure what to do. But I do want to avoid a full factory reset.
Thanks for your hints.
Alternatively is it possible to access the settings of this submenu through a different app or way?
hey_malik said:
Alternatively is it possible to access the settings of this submenu through a different app or way?
Click to expand...
Click to collapse
Sounds like a bad flash, or you didn't factory reset. If you update from 9 to 10 without wiping data, **** can happen
True, I did not because I don't want to set up the whole phone afterwards.
Could it be a solution to flash the ROM again through the integrated update system? Or would I then need to install twrp? I haven't done this in ages
Have you got any magisk module active?
estapagu said:
Have you got any magisk module active?
Click to expand...
Click to collapse
I uninstalled magisk for the update. Reinstalled it, forgot the call recording module. Removed that.
I still have systemless hosts, viper and YouTube vanced active.
hey_malik said:
I uninstalled magisk for the update. Reinstalled it, forgot the call recording module. Removed that.
I still have systemless hosts, viper and YouTube vanced active.
Click to expand...
Click to collapse
I had some SIM problems at the beginning related to a magisk module but I can't remember which. And another problem with WiFi after OTA update using magisk OTA udapte method, so finaly I deleted Magisk completely and updated from TWRP
Just to get this straight:
I may in a first step boot a twrp image (just boot) dirty flash the latest stock image, flash magisk (or not and lose root for the moment which is no issue because I have an unlocked boot loader) and see if the issue is still present. If yes a clean wipe and install is in order?!
@hey_malik
dude when i upgraded from 9.0.17 to 10.3.0 occurred same issue...
Backup all your stuff and MSM your device.
Look for '[OP6T][LATEST 10.3.0] Collection of unbrick tools' thread,
posts #83 - #86 and see how i solved.
Good luck :fingers-crossed:
Cheers
Dadditz said:
@hey_malik
dude when i upgraded from 9.0.17 to 10.3.0 occurred same issue...
Backup all your stuff and MSM your device.
Look for '[OP6T][LATEST 10.3.0] Collection of unbrick tools' thread,
posts #83 - #86 and see how i solved.
Good luck :fingers-crossed:
Cheers
Click to expand...
Click to collapse
I don't really get what you mean. What's msm? Magisk? And what am I supposed to do? Remove magisk completely? I've read the posts 83-86 but it's a bit cryptic for me.
hey_malik said:
I don't really get what you mean. What's msm? Magisk? And what am I supposed to do? Remove magisk completely? I've read the posts 83-86 but it's a bit cryptic for me.
Click to expand...
Click to collapse
Sorry, sometimes I take certain things for granted.
By MSM I meant (incorrectly) the unbrick / downgrade package
posted on the first page of the thread I indicated to you.
If you have not solved that problem and want to try,
I recommend using the Android 10-based package.
Back up all your stuff, be sure you have installed the OP6T drivers on your PC.
All information is already described in the aforementioned thread
or in the link posted on the first page that reports to that of iaTa.
All the credits go to these fantastic guys.
Cheers
Dadditz said:
Sorry, sometimes I take certain things for granted.
By MSM I meant (incorrectly) the unbrick / downgrade package
posted on the first page of the thread I indicated to you.
If you have not solved that problem and want to try,
I recommend using the Android 10-based package.
Back up all your stuff, be sure you have installed the OP6T drivers on your PC.
All information is already described in the aforementioned thread
or in the link posted on the first page that reports to that of iaTa.
All the credits go to these fantastic guys.
Cheers
Click to expand...
Click to collapse
I suggest you boot to Twrp, then flash the Twrp. Get inside twrp and flash these > OOS, Twrp, Magisk Then reboot again to twrp repeat > OOS, Twrp, Magisk. And for the last time reboot again to twrp and flash the Magisk.
You will be good to go. :good:
Is there any risk involved concerning the encryption?
hey_malik said:
Is there any risk involved concerning the encryption?
Click to expand...
Click to collapse
As you already mentioned, you are in Android 10, and if you are using the correct Twrp. There won't be any.
Still it's always better to take a back up just in case if something goes wrong.
Stuck with the same issue. Did you manage to get it fixed somehow?
Actually the latest available oo update to 10.3.1 fixed it.
hey_malik said:
Actually the latest available oo update to 10.3.1 fixed it.
Click to expand...
Click to collapse
Lucky you. I got this issue when switching to 10.3.1 from 9. I tried flashing 10.3.1 once again. Didn't work.
You need to uninstall Magisk then factory reset, it will get rid of all Magisk modules ghost residues. Then flash Magisk again with fastboot twrp method. I had this and going back to factory state was the only fix. No need to flash again and again the rom it doesn't touch Magisk data in /data partition.
hey_malik said:
Actually the latest available oo update to 10.3.1 fixed it.
Click to expand...
Click to collapse
Just an update, this worked for me too. Thanks for posting that tip else I would have went ahead and reset the phone. You saved me a hell lot of trouble.
Additionally, I figured out a solution which might work for people still having this issue. I haven't tested this myself since I found this after my issue was solved.
The reason why the issue happened to us is because the system app "Phone Services" was missing, or not installed properly while dirty flashing. There is an alternative hidden activity for sim settings called "com.android.settings.network.telephony.MobileNetworkActivity", which is not a part of Phone Services app, but a part of the Settings app itself. This could be invoked using any activity launcher apps available in the Play Store.
Also, this activity gives more advanced sim settings too. So, probably worth a look if interested.
Same problem here, but fixed!!
Sim not working anymore after update to Magisk 21.2. nothing would change it.
After installing previous version (21.1) the problem persisted. After almost giving up, I found this thread. Simply uninstalled the OOS Native Call Enabbler module and everything workes like a charm again!!!
So it was an easy fix (once you know) and I am very thankful, because I would never have thougt of it! Unfortunately I cannot record Calls anymore, nor find the module now that I am successfully running on 21.2 again with working SIM. Though the choice between being able to use my SIM or record calls was easy
Hope someone finds use of this info.
As mentioned before Encryption is not a problem if the right TWRP version is used.
Put in you password (or pin) and all is nicely decrypted and reachable in TWRP Recovery.
Good luck to all!
PS: still hoping for a new (compatible) call recorder module though

Categories

Resources