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.
Related
I am not very good at making good step by step instructions but Lots of others are.
Here are the steps that I used.
Unlock bootloader via normal means
Flash chainfire boot img from here
Flash Twrp
Boot into Twrp and click mount and mount /system/
ADB Push supersu Zip file to /system/
Twrp install SuperSu.zip
Reboot
Profit
Are you sure you're encrypted? What's it say under security in your settings under encryption? I assumed that kernel you flashed disabled the automatic encryption. Or did that just allow you to disable it later?
Hi
Evo_Shift said:
Are you sure you're encrypted? What's it say under security in your settings under encryption? I assumed that kernel you flashed disabled the automatic encryption. Or did that just allow you to disable it later?
Click to expand...
Click to collapse
Wish I tried that first, turned off encryption now, although could re-encrypt.
Yes this should work. TWRP doesn't support decryption, which means any files copied to the phones user storage that we might want to install by TWRP (such as SuperSU), can't be seen by TWRP, as it can't decrypt the user data, so it can't be installed from recovery.
However, the system partition isn't encrypted, so pushing a file to the system, will allow TWRP to read it and install SuperSU. Of course you can't do things like full back ups as there probably isn't enough space on the system file system, so you need the user storage area for that, so you would need that decrypted for larger files so that TWRP can gain access.
Regards
Phil
Don't forget adb sideload for installing zips without using internal storage
Use Oem Unlock?
fastboot oem unlock
Yes
How does this affect using Android Pay?
Rado_vr6 said:
How does this affect using Android Pay?
Click to expand...
Click to collapse
Same as other rooted/unlocked devices it doesn't work.
So you can root while keeping encryption enabled? I need encryption for work, but root is a MUST have. Would like to verify before I order. Thanks.
I was under the impression that flashing the chainfire boot img disables encryption?
Did you fastboot into TWRP (no flashing/installing needed) Code = fastboot boot twrp-2.8.7.0-bullhead.img and then adb push supersu?
I've done what the op had and I have root with encryption.
Sent from my Nexus 5X using XDA Free mobile app
I also want to agree. I just tried to unlock tethering without full root, but ran into issues. So to fix my issues, I just decided to follow the ops steps and root the phone. After adding the image, I was unable to push supersu due to adb not working in twrp. However, I rebooted the phone and saw the encryption password on boot. Once the os was loaded, I went into settings -> security and noticed the phone was set to encrypted. Looking through the program list, supersu installer was in the list and worked perfectly. Thanks op.
Sent from my Nexus 5X using XDA Free mobile app
How long does the device take to boot up? I've been sitting at the boot animation for a while now.
You can have root access through SuperSU with encryption enabled. I have it running just fine with encryption enabled. What you do have to have turned off is dm-verity. With dm-verity enabled, modification to the system partition are "not allowed".
And Chainfire's modified boot image has 3 main modifications:
1. A modified sepolicy with SELinux provisioning for SuperSU
2. dm-verity turned off
3. forceencrypt for data partition disabled. Basically disabled forced default encryption, but you can still encrypt.
Is there a way to root MDA build numbers at all? Whether it be encrypted or decrypted?
Camp As A Champ said:
Is there a way to root MDA build numbers at all? Whether it be encrypted or decrypted?
Click to expand...
Click to collapse
I'm not sure why you would want to. I ran the mda89f build for an hour or so before the ota to mdb08i. Phone seemed to run much smoother after the update. Possibly this was just related to timing.
Also, if you root on either of the mda builds, you won't be able to flash the ota to mdb08i. You'll be stuck. If you're waiting on the ota, just download the image and flash the system and boot, then follow OP / Chainfire's instructions.
dbrohrer said:
I'm not sure why you would want to. I ran the mda89f build for an hour or so before the ota to mdb08i. Phone seemed to run much smoother after the update. Possibly this was just related to timing.
Also, if you root on either of the mda builds, you won't be able to flash the ota to mdb08i. You'll be stuck. If you're waiting on the ota, just download the image and flash the system and boot, then follow OP / Chainfire's instructions.
Click to expand...
Click to collapse
Oh I'm special, I didn't know it was on OTA. When I go to check for system updates though, it shows that I'm up to date already. I've unlocked the bootloader and installed TWRP if that affects anything.
Should I just manually flash it to my device?
Camp As A Champ said:
Oh I'm special, I didn't know it was on OTA. When I go to check for system updates though, it shows that I'm up to date already. I've unlocked the bootloader and installed TWRP if that affects anything.
Should I just manually flash it to my device?
Click to expand...
Click to collapse
Since you already have trwp, you will have to update manually (unless you flash the stock recovery and wait for the ota, but who knows how long that will take). I would download the 80i image and just flash system.img and boot.img. That should be the equivalent of you getting the ota. Reboot and confirm that it will boot and you are on the new build. Then follow OPs instruction to root and/or decrypt.
Download, Extract everything.
Fastboot flash system system.img
fastboot flash boot boot.img
Reboot, check OP for further instruction.
This worked for me too - I tried to:
>adb push supersu.zip /system/
... Then in TWRP install -> select /system/supersu.zip
But this failed for some reason... However, this worked:
>adb sideload supersu.zip
Then reboot, and restore Thanks a lot! Didn't want to give up encryption either...
dbrohrer said:
Since you already have trwp, you will have to update manually (unless you flash the stock recovery and wait for the ota, but who knows how long that will take). I would download the 80i image and just flash system.img and boot.img. That should be the equivalent of you getting the ota. Reboot and confirm that it will boot and you are on the new build. Then follow OPs instruction to root and/or decrypt.
Download, Extract everything.
Fastboot flash system system.img
fastboot flash boot boot.img
Reboot, check OP for further instruction.
Click to expand...
Click to collapse
Will I be able to do this through TWRP or should I just use ADB to flash the image files? Sorry for all the questions, this is my first nexus phone and I'm getting used to all the new methods
Nevermind, got everything to work, thanks for the help though
Hi - I've read through almost every thread in this forum and, unless I am missing something - quite possible - I don't think that anybody has mentioned this problem.
I have a bootloader unlocked Boost Moto E4 and I can flash Squid's TWRP (I do get the "Image not signed or corrupt" message) and can boot from the bootloader after the flash into TWRP recovery. However, after I boot into the OS, the TWRP recovery gets overwritten with the stock recovery. Has anybody else bumped into this? Is there a step that I am missing somewhere to make TWRP permanent?
Thanks
D.
Hmm - okay, after a little bit more work, I've managed to make it stick. I am not entirely sure which part of the process made it successful - or if I am duplicating things - but I used Magisk to generate a new boot.img, flashed that .img through twrp, installed the magisk .zip and now twrp "sticks" as my recovery. Nice that it allows me to boot with my system as r/w.
D.
D97 said:
Hmm - okay, after a little bit more work, I've managed to make it stick. I am not entirely sure which part of the process made it successful - or if I am duplicating things - but I used Magisk to generate a new boot.img, flashed that .img through twrp, installed the magisk .zip and now twrp "sticks" as my recovery. Nice that it allows me to boot with my system as r/w.
D.
Click to expand...
Click to collapse
Your problem is the stock rom flashing the stock recovery when you reboot. If you flash twrp then reboot recovery once before booting the os, it should change a file in /system recovery-from-boot.p to recovery-from-boot.p.bak which will stop the stock recovery flash. You can also mount /system in twrp and use the file manager to change it manually.
D97 said:
Hmm - okay, after a little bit more work, I've managed to make it stick. I am not entirely sure which part of the process made it successful - or if I am duplicating things - but I used Magisk to generate a new boot.img, flashed that .img through twrp, installed the magisk .zip and now twrp "sticks" as my recovery. Nice that it allows me to boot with my system as r/w.
D.
Click to expand...
Click to collapse
after flashing recovery you have to root your device to make it
sticky. if you skip this step custom recovery will replaced on next boot *bingo*
Francesco Franz said:
after flashing recovery you have to root your device to make it
sticky. if you skip this step custom recovery will replaced on next boot *bingo*
Click to expand...
Click to collapse
Not true. You don't have to root to make twrp stick. I did just state how to do this.
Sent from my Moto E (4) using XDA Labs
amarc78 said:
Not true. You don't have to root to make twrp stick. I did just state how to do this.
Click to expand...
Click to collapse
than do this flash over default recovery and do reboot. twrp recovery removed from recovery partition on next boot.
also do this flash twrp and do allow modifications. your device ain't gonna boot. if you didn't flash no verity thing.
rooting will make it permanent. it's the same case in both marshmallow and nougat too as OP states his problem in first post.
it will permanent by doing this
fastboot erase recovery (remove default recovery from recovery partition)
than install custom recovery. it will be there no matter if your device is rooted or not.
Thanks for the replies, everybody. There is some good info in them - I have managed to "make it stick" but I'll definitely keep the advice here in mind when I need to redo things (as I am sure that I will at some point).
D.
D97 said:
Thanks for the replies, everybody. There is some good info in them - I have managed to "make it stick" but I'll definitely keep the advice here in mind when I need to redo things (as I am sure that I will at some point).
D.
Click to expand...
Click to collapse
which step actually help you?
DE SEXIEST said:
which step actually help you?
Click to expand...
Click to collapse
Whatever you do don't run "fastbootboot erase" anything unless you know for sure what by you're doing or you can screw up your partitions. I have flashed twrp many times with only running "fastboot flash recovery...", then flashing one of numerous zips to disable dmverity and forced encryption. As long as you have the option in twrp under " mount" that says "mount system read only" not checked and you may need to reboot twrp afterwards, twrp should stick. Flashing Magisk directly after the stock rom should also solve your problem and disable dmverity.
I can't seem to install Magisk 16.0 via TWRP 3.2 on the Oreo update. It installs, but enters a bootloop. Why is that?
Also TWRP said cannot mount /data. How to fix this?
"Failed to mount '/data' (No such process)"
Also cannot format data this way
EDIT: Installed Magisk 16.4, no change. Also just realized that internal storage is inaccessible.
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
GBry said:
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
Click to expand...
Click to collapse
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
kekley said:
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
Click to expand...
Click to collapse
Did you try wiping your cache?
+)KEV1N(+ said:
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
Did you try wiping your cache?
Click to expand...
Click to collapse
Technically, I'm not now, since I flashed the original boot.img
But yes, if I installed magisk either via the patched boot.img or TWRP, I get a bootloop
Actually idk if bootloop or nah since I can't access logcat via adb, but it's on the bootlogo for like 5 mins (regular start time is 30-ish sec)
+)KEV1N(+ said:
Did you try wiping your cache?
Click to expand...
Click to collapse
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
kekley said:
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
Click to expand...
Click to collapse
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
+)KEV1N(+ said:
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
Click to expand...
Click to collapse
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
GBry said:
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
Click to expand...
Click to collapse
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
How did you manage to update via twrp? I get an error when I try it.
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
Click to expand...
Click to collapse
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Yes, I searched through my history and then found out that you gave me the same link, so thank you. Updated my 2nd to last post about the condition... Do I REALLY have to factory reset? Sigh...
+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
+)KEV1N(+ said:
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
Click to expand...
Click to collapse
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
Yes, actually I just did update via TWRP, it installs flawlessly. HOWEVER, it only applies to the Oreo ROM, not the N or M ROMs. N and M needs stock recovery (the boot.img contains recovery too)
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
kekley said:
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
Click to expand...
Click to collapse
Did you install Magisk though?
GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
Click to expand...
Click to collapse
Did you try clearing it with the stock recovery?
GBry said:
Did you install Magisk though?
Click to expand...
Click to collapse
With the latest twrp, yes! :good:
I really just want to root stock. I have the Boost Mobile Perry.
guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
Yes. Install twrp, flash no verity, format data (to remove encryption) flash magisk. Some people have said if you took the last security update, you may have to patch the boot.img with magisk manager then flash the patched boot.img in fastboot or twrp to root. And will likely need the latest magisk beta (16.4).
I really don't care about encryption.
guitardoc64 said:
I really don't care about encryption.
Click to expand...
Click to collapse
You have to remove encryption.
Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.
guitardoc64 said:
Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.
Click to expand...
Click to collapse
Don't neglect to backup EVERYTHING in TWRP before doing ANYTHING (and store those images off-device!). Strongly suggest booting a TWRP image to perform this task vs. installing/flashing to the recovery partition, especially if interested in preserving/restoring OTA capability at a future time.
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.
guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
Welcome to the 5% club which is probably generous based on the number of noobs (and veterans) who neglect to image their device before messing with core components. Of course that figure may be skewed as those that do take proper precautions rarely write posts that begin with "help!" and have no path back to the prior working state.
Also, resist the temptation to flash a custom recovery (twrp) vs booting from fastboot if you want to accept accept future OTA updates or roll back to pure stock. While restoring stock recovery is possible it certainly complicates the process. Can always revisit the decision at later time.
guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
Don't have a definitive answer on the latest firmware. Suggest going through the above steps first. If no joy it's a simple matter to patch/flash boot.img .
You are wise to boot a twrp image vs flashing over stock recovery. Simplifies fallback should the need arise. Don't neglect to backup stock and store off device (or at least on a SD card).
davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
For .3, format data to remove encryption.
But the rest should work. If not, you have to download the current firmware ( the version you're on) if you can find it. Extract the boot.img from it. Then use magisk manager to patch it. And use fastboot to flash the patched boot.img
i have the moto e4 mkt which no verity version do i have to flash ?
Rafasama said:
i have the moto e4 mkt which no verity version do i have to flash ?
Click to expand...
Click to collapse
You shouldn't need a no-verity any longer. Newer versions of magisk should take care of it. Just TWRP, and magisk.
madbat99 said:
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.
Click to expand...
Click to collapse
Hello, I am running a Samsung Galaxy J5 Prime at the moment, a friend told me I must flash no verity.zip after flashing TWRP because of the verification and I tried making a backup if the entire rom but it failed so I need to confirm, do I factory reset my device then flash the no verity file or I flash the no verity file and then factory reset the device??
I know it's an old thread but a quick reply would be awesome
I'm on a rooted OP 6T, I installed TWRP and Magisk when I first got it on release day. I was using systemize to system install my GCam apk, rebooted and now I cant go any further than the dots loading screen. I tried a date wipe, still cant get any further. I want to try uninstalling magisk or the individually modules but I can't figure out how I do that. When I try to access my files through recovery they seem to be encrypted so I don't know how to get the uninstall zip flashed. Can someone please help
update
I got the magisk uninstaller sideloaded but it says magisk is not installed, is there a way I can just go back to stock and clear everything? I havent installed a custom rom just unlocked and rooted
If you're able to go to download mode then ADB sideloading should help you.
There's bunch of tutorials on how to do that on the forum.
geminium said:
If you're able to go to download mode then ADB sideloading should help you.
There's bunch of tutorials on how to do that on the forum.
Click to expand...
Click to collapse
not sure what downloading mode is, but I did get into ADB sideload mode. I tried sideloading the magisk uninstallers so I could get rid of whatever module caused the issue, but I got the reply that magisk isn't installed. So now Im not sure what to do from here besides trying to go fully back to stock, which Id rather not
Grab a stock boot.img in the fastboot stock ROM thread in general section and flash it with fastboot to replace the magisk modified one
Striatum_bdr said:
Grab a stock boot.img in the fastboot stock ROM thread in general section and flash it with fastboot to replace the magisk modified one
Click to expand...
Click to collapse
The system is modified. Maybe gonna have to sideload the whole firmware package ~1gb. I'm pretty sure this is the reason everything in magisk is systemless. Maybe contact the developer about the mod and see if they know a way to get it to work for your situation?
stryver said:
The system is modified. Maybe gonna have to sideload the whole firmware package ~1gb. I'm pretty sure this is the reason everything in magisk is systemless. Maybe contact the developer about the mod and see if they know a way to get it to work for your situation?
Click to expand...
Click to collapse
It is not the system partition that is modified (that's the point for a systemless app...) It's boot and data (magisk puts here the img it needs to mount virtually and execute all the magisk modules you installed). You got nothin to lose to flash boot.img first and if it doesn't work you restore system and data
Striatum_bdr said:
It is not the system partition that is modified (that's the point for a systemless app...) It's boot and data (magisk puts here the img it needs to mount virtually and execute all the magisk modules you installed). You got nothin to lose to flash boot.img first and if it doesn't work you restore system and data
Click to expand...
Click to collapse
OP stated that they used a systemizer app to install gcam to the system, doesn't that mean there is now a modification in the system? Which would explain why the data format is not working.
stryver said:
OP stated that they used a systemizer app to install gcam to the system, doesn't that mean there is now a modification in the system? Which would explain why the data format is not working.
Click to expand...
Click to collapse
No it's all virtual, the physical partition system is not modified.
Again, what do you have to lose by flashing boot.img...
Striatum_bdr said:
No it's all virtual, the physocal partition system is not modified
Click to expand...
Click to collapse
That's true for magisk, but installing any apps to system via 3rd party root app will cause the apps to survive factory resets, right? So if say, new system app was causing any conflicts, those conflicts will also survive.
stryver said:
That's true for magisk, but installing any apps to system via 3rd party root app will cause the apps to survive factory resets, right?
Click to expand...
Click to collapse
Again what do you have to lose by flashing boot img? Your phone doesn't boot... At worse it won't boot and you'll have to come back to factory by fastboot the would system
Striatum_bdr said:
Again, what do you have to lose by flashing boot.img...
Click to expand...
Click to collapse
Sorry I'm not trying to be argumentative, I'm merely speaking what makes sense to me
Endless speculation can be ended by experimentation...
Striatum_bdr said:
Endless speculation can be ended by experimentation...
Click to expand...
Click to collapse
Agreed, now where is OP to confirm our speculation??
And by the way App Systemizer is systemless so it doesn't touch system partition, first sentence of the module description
Striatum_bdr said:
And by the way App Systemizer is systemless so it doesn't touch system partition, first sentence of the module description
Click to expand...
Click to collapse
I was just going to check this, never used it myself. Probably should have checked before speaking. Lesson learned lol oh well
Again, sorry if I came off argumentative.
Next thing that comes to mind for OP is that there is a difference between 'wiping data' and 'formatting data'. If you just wiped, try to format data. I had a bootloop from uninstalling a magisk module and quickly recovered by formatting.
stryver said:
Agreed, now where is OP to confirm our speculation??
Click to expand...
Click to collapse
I ended up just downloading the OnePlus tool and stock fajita rom and taking it back to stock. Still not sure exactly what caused the problem, I did everything over again with no issues the second time around