I did modified build.prop once, everything worked fine, but after updating my phone, build.prop reset to default. Now I tried to modify build.prop again, and I'm stuck in bootloop.
I can boot my phone by changing active slot from A to B, so it's only A slot stuck in bootloop. This is what I did:
Boot into bootloader
Unlock bootloader
Boot into twrp recovery
Pull build.prop, edit, push it back
I forgot to chmod build.prop, so after rebooting my phone, it failed, stuck in bootloop. After I chmod build.prop, it still won't boot. How do I fix it?
Try flashing system.img to slot a using fastboot, if it's only A that is a problem.
Just flash newest system image from official site using MiFlash tool without wiping the data
And there's no other way to fix this problem without flashing system image? I mean, I just modified build.prop, nothing else, isn't there faster and easier way to fix it? What if I boot twrp with B slot, pull build.prop, then boot twrp with A slot, and push build.prop?
matcho13579 said:
Just flash newest system image from official site using MiFlash tool without wiping the data
Click to expand...
Click to collapse
Will it delete apps and do I need to setup android again, i.e. login with google account again, setup fingerprint and etc?
druckis3000 said:
And there's no other way to fix this problem without flashing system image? I mean, I just modified build.prop, nothing else, isn't there faster and easier way to fix it? What if I boot twrp with B slot, pull build.prop, then boot twrp with A slot, and push build.prop?
Will it delete apps and do I need to setup android again, i.e. login with google account again, setup fingerprint and etc?
Click to expand...
Click to collapse
Flashing system, as long as that is all you do, will not remove anything like your stuff. I've done it before many times, even used miflash but made sure I did select to save user data. Everything there as before, except it completely removed root (Magisk), and relocked the bootloader.
goofball2k said:
Flashing system, as long as that is all you do, will not remove anything like your stuff. I've done it before many times, even used miflash but made sure I did select to save user data. Everything there as before, except it completely removed root (Magisk), and relocked the bootloader.
Click to expand...
Click to collapse
I need to flash it while in bootloader or recovery? And will it flash to both slots, or only active slot?
druckis3000 said:
I need to flash it while in bootloader or recovery? And will it flash to both slots, or only active slot?
Click to expand...
Click to collapse
MiFlash or flashing system, you need to put your phone in fastboot mode.
MiFlash will flash both slots.
if you manually flash, you can decide which slot you flash to.
fastboot flash system_a system.img
goofball2k said:
MiFlash or flashing system, you need to put your phone in fastboot mode.
MiFlash will flash both slots.
if you manually flash, you can decide which slot you flash to.
fastboot flash system_a system.img
Click to expand...
Click to collapse
I'm on Linux, so I can't install MiFlash tool, so if I flash via fastboot, would it save my data?
druckis3000 said:
I'm on Linux, so I can't install MiFlash tool, so if I flash via fastboot, would it save my data?
Click to expand...
Click to collapse
Nevermind, already did it and everything works fine, all data were saved. But I still got one question, why can't I edit build.prop file? Few minutes ago I tried to pull build.prop from slot B and push it to slot A, then slot B also stopped working, stuck in bootloop, even though I just pulled build.prop from slot B, and didn't modified it.
druckis3000 said:
Nevermind, already did it and everything works fine, all data were saved. But I still got one question, why can't I edit build.prop file? Few minutes ago I tried to pull build.prop from slot B and push it to slot A, then slot B also stopped working, stuck in bootloop, even though I just pulled build.prop from slot B, and didn't modified it.
Click to expand...
Click to collapse
Easier method is to use Magisk module (I guess you want to enable Camera2 API)
druckis3000 said:
Nevermind, already did it and everything works fine, all data were saved. But I still got one question, why can't I edit build.prop file? Few minutes ago I tried to pull build.prop from slot B and push it to slot A, then slot B also stopped working, stuck in bootloop, even though I just pulled build.prop from slot B, and didn't modified it.
Click to expand...
Click to collapse
You might have messed up owner or rights of the file. That's usually the main culprit. Simple file pull should not do anything wrong. Maybe you were still booting into the slot A? For the future I would suggest using Magisk systemless mods, it's much easier to apply and remove and you won't break anything (Safetynet for example).
Yes I want to enable Camera2 API. I don't wanna use Magisk, because of rooting, I do not need root. That's why I boot into TWRP recovery and edit build.prop using adb pull/push, but now I'm afraid to edit it again, due to previous issues.
druckis3000 said:
Yes I want to enable Camera2 API. I don't wanna use Magisk, because of rooting, I do not need root. That's why I boot into TWRP recovery and edit build.prop using adb pull/push, but now I'm afraid to edit it again, due to previous issues.
Click to expand...
Click to collapse
You can use Magisk and disable root (auto reply set to deny root access).
Edit: stock kernel should have dm-verity enabled, so as soon as you mount system as read write, it fails the safe boot verification. This might be the reason of your bootloops.
_mysiak_ said:
You can use Magisk and disable root (auto reply set to deny root access).
Edit: stock kernel should have dm-verity enabled, so as soon as you mount system as read write, it fails the safe boot verification. This might be the reason of your bootloops.
Click to expand...
Click to collapse
But I already modified build.prop successfully previously, how it passed safe boot verification? Using Magisk I'll not get OTA updates anymore, so I don't want to install Magisk.
edit: Ok, I did another test, I just booted into TWRP and rebooted into system, and phone stuck in bootloop, so I guess that's TWRP causing that issue?
druckis3000 said:
But I already modified build.prop successfully previously, how it passed safe boot verification? Using Magisk I'll not get OTA updates anymore, so I don't want to install Magisk.
Click to expand...
Click to collapse
Well, it's of course totally up to you, but with Magisk you need to restore only boot.img. If you modify build.prop directly, you have to reflash whole system partition to apply OTA. In both cases OTA is going to fail until you restore all partitions to stock.
If you know what you did before, just repeat the steps..[emoji846] If you can't/don't know, use verified and easy method (Magisk).
_mysiak_ said:
Well, it's of course totally up to you, but with Magisk you need to restore only boot.img. If you modify build.prop directly, you have to reflash whole system partition to apply OTA. In both cases OTA is going to fail until you restore all partitions to stock.
If you know what you did before, just repeat the steps..[emoji846] If you can't/don't know, use verified and easy method (Magisk).
Click to expand...
Click to collapse
I edited my last reply, take a look at it. I do everything correctly, but I guess it's problem with TWRP recovery. Before installing OTA update I edited build.prop successfully, now after update if I boot into TWRP, I instantly get bootloop, no need to edit build.prop.
druckis3000 said:
I edited my last reply, take a look at it. I do everything correctly, but I guess it's problem with TWRP recovery. Before installing OTA update I edited build.prop successfully, now after update if I boot into TWRP, I instantly get bootloop, no need to edit build.prop.
Click to expand...
Click to collapse
I use TWRP without any issues, so I doubt that it's caused by it. Do you flash TWRP or boot it only? Do you allow system mounting as RW in TWRP?
_mysiak_ said:
I use TWRP without any issues, so I doubt that it's caused by it. Do you flash TWRP or boot it only? Do you allow system mounting as RW in TWRP?
Click to expand...
Click to collapse
I don't flash TWRP, I only boot into it. Yesterday when I did that test, I didn't even mounted system partition, but usually yes, I mount it as RW.
I'm using older TWRP version, it's 3.1.1-1, TWRP has newer version, 3.2.1, but that one wont boot, phone boots into system when I try to boot TWRP. Maybe newer version wouldn't cause bootloop
No idea then, I am on December update and can boot into TWRP and system without any issues (though I don't mount system as RW).
_mysiak_ said:
No idea then, I am on December update and can boot into TWRP and system without any issues (though I don't mount system as RW).
Click to expand...
Click to collapse
You use TWRP image from their official website? Weird.. It never worked for me, the one I used before was downloaded from other website, not TWRP.
Hi there,
January Security Patch is not here yet so that's why I wanted to ask you guys:
Recently, I reflashed system.img and boot.img on slot B with the stock ones and locked the bootloader but I've modified the slot A before locking.
So I'm currently with a locked bootloader, using 100% stock slot B and I have a modified slot A. Will that modified inactive slot make any problems with updates (bootloops, etc.)?
Yes you will have problems, when you get a OTA you will get an error because slot A is modified, so the update won't apply.
To install OTA's you'll need to have your inactive partitions unmodified because the OTA will apply to that one (the active partition can be modified)
Modified slot A and bootloader still locks. Can anyone elaborate on this one.
So, how can I fix it WITHOUT FULL REFLASH USING MI TOOL PLEASE?
Do I just flash stock Oreo boot.img and system.img on slot A too? That will make slot A the same use the stock ROM as slot B.
Hmm?
nicolasmart said:
So, how can I fix it WITHOUT FULL REFLASH USING MI TOOL PLEASE?
Do I just flash stock Oreo boot.img and system.img on slot A too? That will make slot A the same use the stock ROM as slot B.
Click to expand...
Click to collapse
Yes flash stock on both slots. Then there won't be any trouble in getting ota.
I would recommend flash all.
alkesh95 said:
Yes flash stock on both slots. Then there won't be any trouble in getting ota.
I would recommend flash all.
Click to expand...
Click to collapse
Will flashing work without unlocking bootloader again?
I went from stock with the February security patch to rooted running the latest update from Havoc. I am getting a vendor mismatch message when I reboot my phone. I am looking for the correct steps to update my vendors update to both slots in tarp. I've read different approaches. Just a bit confused.
Sent from my [device_name] using XDA-Developers Legacy app
gregg0829 said:
I went from stock with the February security patch to rooted running the latest update from Havoc. I am getting a vendor mismatch message when I reboot my phone. I am looking for the correct steps to update my vendors update to both slots in tarp. I've read different approaches. Just a bit confused.
Click to expand...
Click to collapse
The easiest way would be to use fastboot...
...fastboot flash vendor vendor.img --slot=all
That'll flash it to both slots. If you use twrp, then after you flash it to one slot, you'd have to reboot your recovery to the other slot and flash it again :good:
Badger50 said:
The easiest way would be to use fastboot...
...fastboot flash vendor vendor.img --slot=all
That'll flash it to both slots. If you use twrp, then after you flash it to one slot, you'd have to reboot your recovery to the other slot and flash it again :good:
Click to expand...
Click to collapse
I'm not close to a computer so option 1 is not available to me. Is adb the best way or is just user preference?
Sent from my [device_name] using XDA-Developers Legacy app
gregg0829 said:
I'm not close to a computer so option 1 is not available to me. Is adb the best way or is just user preference?
Click to expand...
Click to collapse
Either way will get the job done. I flashed vendors all the time with twrp in my rom hopping days without issue. Strictly your call my friend :good:
Badger50 said:
The easiest way would be to use fastboot...
...fastboot flash vendor vendor.img --slot=all
That'll flash it to both slots. If you use twrp, then after you flash it to one slot, you'd have to reboot your recovery to the other slot and flash it again :good:
Click to expand...
Click to collapse
Huh? I've never had to flash the vendor in TWRP more than once.
Badger50 said:
The easiest way would be to use fastboot...
...fastboot flash vendor vendor.img --slot=all
That'll flash it to both slots. If you use twrp, then after you flash it to one slot, you'd have to reboot your recovery to the other slot and flash it again :good:
Click to expand...
Click to collapse
What's up man, long time no see! So you happen to have a link that contains Pixel slot commands like this? I'm bootloader unlocked on the Pixel 2 already via Nathanchance's guide but still catching up on the differences from my Nexus 5X. I'm just curious about the slot specific/all slot commands like the one above.
SlimSnoopOS said:
What's up man, long time no see! So you happen to have a link that contains Pixel slot commands like this? I'm bootloader unlocked on the Pixel 2 already via Nathanchance's guide but still catching up on the differences from my Nexus 5X. I'm just curious about the slot specific/all slot commands like the one above.
Click to expand...
Click to collapse
Hope you've been good my friend. I don't have a link for the commands, many I have just learned over time. I'm sure google search could help you out, and, you can always type...fastboot help...while in fastboot mode that will show a list of commands :good:
another way to update the vendor is to download the full factory image, then open it in a file explorer. open the zip inside the zip and find vendor.img. extract that somewhere and flash it. this is how ive done it. cuz i never have a computer handy when i want to update.
but ....... I am in twrp unable to reboot into my rom. When I click on Install I see all these folders with letters and numbers and what my original folders.
Can somone help me boot into my rom again?
ms.journie said:
but ....... I am in twrp unable to reboot into my rom. When I click on Install I see all these folders with letters and numbers and what my original folders.
Can somone help me boot into my rom again?
Click to expand...
Click to collapse
You will more than likely need to format data. This will cause you to loose everything. But that is what you are seeing, those folders, are your data. Just encrypted.
Also make sure you are on the latest version of TWRP. Sometimes the older unsupported version had encryption errors.
Omg this saddens me! So there's no way I am unable to at least retrieve my pictures?
Scott said:
You will more than likely need to format data. This will cause you to loose everything. But that is what you are seeing, those folders, are your data. Just encrypted.
Also make sure you are on the latest version of TWRP. Sometimes the older unsupported version had encryption errors.
Click to expand...
Click to collapse
Have u tested change boot partition ?
yup
J3zz said:
Have u tested change boot partition ?
Click to expand...
Click to collapse
ms.journie said:
yup
Click to expand...
Click to collapse
Simple test are:
- change boot partition
- reflash system
- Say goodbye too all
Got the same problem, Solved After reboot in twrp and enter the good decryption code
I'm right in the middle of reflashing. I am trying everything else before I do say goodbye to my pictures! :crying:
How did you figure out the decryption code?
J3zz said:
Simple test are:
- change boot partition
- reflash system
- Say goodbye too all
Got the same problem, Solved After reboot in twrp and enter the good decryption code
Click to expand...
Click to collapse
ms.journie said:
I'm right in the middle of reflashing. I am trying everything else before I do say goodbye to my pictures! :crying:
How did you figure out the decryption code?
Click to expand...
Click to collapse
First time entering in twrp after flashing update, I did not get folder to flash magisk, did a reboot and get it, just a bad encryption code I think
Did u flash rom or anything else before getting this problem ?
Yup, I sure did! 4am couldn't sleep so I thought I would finally put a fingerprint mod on; which I have done this before with no issues. For the life of me, I don't remember which mod I tried to install thru Magisk.
My phone is currently stuck on "Phone is starting"
I also think it's time to look into some sort of automatic back up service..... Got any ideas?
J3zz said:
First time entering in twrp after flashing update, I did not get folder to flash magisk, did a reboot and get it, just a bad encryption code I think
Did u flash rom or anything else before getting this problem ?
Click to expand...
Click to collapse
ms.journie said:
Yup, I sure did! 4am couldn't sleep so I thought I would finally put a fingerprint mod on; which I have done this before with no issues. For the life of me, I don't remember which mod I tried to install thru Magisk.
My phone is currently stuck on "Phone is starting"
I also think it's time to look into some sort of automatic back up service..... Got any ideas?
Click to expand...
Click to collapse
Use msmdownloadtool, have u tried using magisk uninstall in twrp with zip file ? Then boot and uninstall the "****in" fantastic module... maybe it works
I did try to uninstall Magisk in twrp using adb shell. I never had any luck with that msmdownloadtool and not only that it relocks your bootloader.
I usually go this route [ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Thanks for trying to me!
J3zz said:
Use msmdownloadtool, have u tried using magisk uninstall in twrp with zip file ?
Click to expand...
Click to collapse
ms.journie said:
I did try to uninstall Magisk in twrp using adb shell. I never had any luck with that msmdownloadtool and not only that it relocks your bootloader.
I usually go this route [ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Thanks for trying to me!
Click to expand...
Click to collapse
Good luck !!
I saw this happen when I used the official TWRP app.
It went away when I used this TWRP. Hope that helps.
I'm glad you already know not to use the MSM tool. Too many people jump straight to this.....
You just need to boot the correct recovery and your data will decrypt, and you will be able to back it up to a PC, then you can reload your ROM via TWRP or Fastboot to get the phone bootable again. So now it's a question of what ROM were you running before. Do you need a recovery with the latest security patch or something older? What TWRP are you running. Try 3.3.1-6 psychen6 linked too first. Boot that image from Fastboot. See if your password/pin will work to decrypt your data.
Screen won't respond and I can't get it to turn on. But it still charges as my wireless charger still detects it? How do I fix this?
Tried holding down power + volume up for 10-15 sec?
Happened a few times for me as well, but that always fixed it.
dmbardal said:
Tried holding down power + volume up for 10-15 sec?
Happened a few times for me as well, but that always fixed it.
Click to expand...
Click to collapse
Wow I did this earlier and it didn't work and now it worked. That makes no sense. Now it just keeps booting to Fastboot. Is there anyway to get my data safe and sound from the device?
train21 said:
Wow I did this earlier and it didn't work and now it worked. That makes no sense. Now it just keeps booting to Fastboot. Is there anyway to get my data safe and sound from the device?
Click to expand...
Click to collapse
If you're bootloader is still unlocked, fastboot boot TWRP and backup your data that way. You also might be able to still boot by trying to flash stable magisk 20.4 from within TWRP.
jeffsga88 said:
If you're bootloader is still unlocked, fastboot boot TWRP and backup your data that way. You also might be able to still boot by trying to flash stable magisk 20.4 from within TWRP.
Click to expand...
Click to collapse
Ah I just did the unbrick tool. I didn't have much on it. Now here is the thing to prevent this from happening. How are you suppose to update Magisk without bricking? I did install to inactive slot and this happened.
train21 said:
Ah I just did the unbrick tool. I didn't have much on it. Now here is the thing to prevent this from happening. How are you suppose to update Magisk without bricking? I did install to inactive slot and this happened.
Click to expand...
Click to collapse
You can just fastboot boot TWRP and install magisk, just make sure to use magisk 20.4. I've never personally had an issue installing to inactive slot after getting ota update but can always just use TWRP to install it too.