Related
Hey guys, I'm a little devastated. Hoping I didn't ruin my phone.
So, earlier today I unlocked my Moto G4 Plus's bootloader and installed TWRP recovery. I installed ElementalX and a superuser.zip file as well. After reboot, there was no superuser in my app drawer and when I checked my root status with Phh's Root Checker, it said that my phone was not rooted properly. I then found the guide here on how to root, and noticed that it had Phh's SuperUser. I changed the config.txt file like mentioned in the guide, booted into TWRP recovery and installed it and clicked on reboot. I got the usual bootloader unlocked message, but after that my screen went blackish-grey and has been that way since, which is about 15-20 minutes now. I (panicking and being a noob) tried switching it off using the power button which didn't work. I then checked to see if it showed up as connected device in android sdk/fastboot, which it didn't.
WHAT DO I DO? I can't just buy another phone since I can't afford it as I recently bought this one, so it's a really big deal for me. :crying:
PLEASE HELP ME.
Thank you.
UPDATE.
Hey guys,
First of all, thank you for the replies. I'm sorry I couldn't reply to them.
Secondly, a few things have happened since the OP. Keep in mind I had absolutely NO internet during the following events, so I couldn't do any research.
The night my phone went black screen, I went to sleep thinking i'll let it die out of battery and work the rest out in the morning. So the next morning I put the phone on charge and went into the bootloader. I tried doing a normal reboot which didn't work (I got the same screen) so I went into into bootloader again, connected the phone to my computer (it got recognized this time) and re-flashed TWRP. I went into recovery mode on the phone and tried re-flashing ElementalX and superuser. This time I got an error when trying to flash the superuser.zip, and the error was:
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/superuser.zip'
I had another supersu.zip in my phone storage, tired installing it and got the same error.
When I tried doing a normal reboot into my system, it goes on a boot loop on the "your device is unlocked" screen and has been that way ever since.
What do I do now?
Should I try to re-flash TWRP and superuser with the right files, or should I restore stock recovery? I don't have any backup. (noob mistake)
I'd highly appreciate it anyone linked me the proper twrp and superuser or stock recovery files and if possible guided me on what to do.
PLEASE HELP ME.
thank you.
UPDATE #2
So I did what abhi212b told me to do and flashed the stock rom. Everything is fine now.
I'll try rooting it again a bit later. Thanks for the help.
UPDATE #3
I tried rooting my phone again, and it went flawlessly this time! Rooted successfully.
What an emotional rollercoaster lol.
Push the power button for at least 2-3 minutes. Worked for me and others in the past.
SSJGod said:
Hey guys, I'm a little devastated. Hoping I didn't ruin my phone.
So, earlier today I unlocked my Moto G4 Plus's bootloader and installed TWRP recovery. I installed ElementalX and a superuser.zip file as well. After reboot, there was no superuser in my app drawer and when I checked my root status with Phh's Root Checker, it said that my phone was not rooted properly. I then found the guide here on how to root, and noticed that it had Phh's SuperUser. I changed the config.txt file like mentioned in the guide, booted into TWRP recovery and installed it and clicked on reboot. I got the usual bootloader unlocked message, but after that my screen went blackish-grey and has been that way since, which is about 15-20 minutes now. I (panicking and being a noob) tried switching it off using the power button which didn't work. I then checked to see if it showed up as connected device in android sdk/fastboot, which it didn't.
WHAT DO I DO? I can't just buy another phone since I can't afford it as I recently bought this one, so it's a really big deal for me. :crying:
PLEASE HELP ME.
Thank you.
Click to expand...
Click to collapse
Like the poster above stated, hold the power button until the screen shuts off. YOUR PHONE WILL AUTO REBOOT!!! The instant the screen turns off, begin holding the volume down button. When you see the fastboot screen pop up, begin flashing your N images again, or use a custom ROM (which are generally much faster, easier to mess with, and easier to recover from).
Ex didn't flash properly.. That is what I can estimate! If u root on stock kernel, it breaks the device.
As said above go to bootloader (works on any screen... Power and volume down) and then to twrp maybe (flash twrp from fastboot). And then restore any previous nandroid u have.. If not u will have to flash stock via fastboot and then flash ex kernel. When u flash, restart and go to about phone and see if the kernel shows elemental x.. If yes, go to twrp and root it via suoersu, phhh's superuser or magisk su.. Whichever u like.. That should be fine!
UPDATE.
Hey guys,
First of all, thank you for the replies. I'm sorry I couldn't reply to them.
Secondly, a few things have happened since the OP. Keep in mind I had absolutely NO internet during the following events, so I couldn't do any research.
The night my phone went black screen, I went to sleep thinking i'll let it die out of battery and work the rest out in the morning. So the next morning I put the phone on charge and went into the bootloader. I tried doing a normal reboot which didn't work (I got the same screen) so I went into into bootloader again, connected the phone to my computer (it got recognized this time) and re-flashed TWRP. I went into recovery mode on the phone and tried re-flashing ElementalX and superuser. This time I got an error when trying to flash the superuser.zip, and the error was:
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/superuser.zip'
I had another supersu.zip in my phone storage, tired installing it and got the same error.
When I tried doing a normal reboot into my system, it goes on a boot loop on the "your device is unlocked" screen and has been that way ever since.
What do I do now?
Should I try to re-flash TWRP and superuser with the right files, or should I restore stock recovery? I don't have any backup. (noob mistake)
I'd highly appreciate it anyone linked me the proper twrp and superuser or stock recovery files and if possible guided me on what to do.
PLEASE HELP ME.
thank you.
SSJGod said:
Hey guys,
First of all, thank you for the replies. I'm sorry I couldn't reply to them.
Secondly, a few things have happened since the OP. Keep in mind I had absolutely NO internet during the following events, so I couldn't do any research.
The night my phone went black screen, I went to sleep thinking i'll let it die out of battery and work the rest out in the morning. So the next morning I put the phone on charge and went into the bootloader. I tried doing a normal reboot which didn't work (I got the same screen) so I went into into bootloader again, connected the phone to my computer (it got recognized this time) and re-flashed TWRP. I went into recovery mode on the phone and tried re-flashing ElementalX and superuser. This time I got an error when trying to flash the superuser.zip, and the error was:
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/superuser.zip'
I had another supersu.zip in my phone storage, tired installing it and got the same error.
When I tried doing a normal reboot into my system, it goes on a boot loop on the "your device is unlocked" screen and has been that way ever since.
What do I do now?
Should I try to re-flash TWRP and superuser with the right files, or should I restore stock recovery? I don't have any backup. (noob mistake)
I'd highly appreciate it anyone linked me the proper twrp and superuser or stock recovery files and if possible guided me on what to do.
PLEASE HELP ME.
thank you.
Click to expand...
Click to collapse
That won't help!
Best is that u should flash stock rom, since the phone is bootlooping...
U can find it here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Flash it on bootloader screen via fastboot.
Do not relock the bootloader. Skip that step and also do NOT flash bootloader.img and partition. That can mess up the device.
once this is done, boot the device once... Finish the setup and then flash twrp.. Then flash ex kernel then flash any root Zip. (supersu, magisk or phhh's superuser)
Twrp can be found from here. https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
abhi212b said:
That won't help!
Best is that u should flash stock rom, since the phone is bootlooping...
U can find it here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Flash it on bootloader screen via fastboot.
Do not relock the bootloader. Skip that step and also do NOT flash bootloader.img and partition. That can mess up the device.
once this is done, boot the device once... Finish the setup and then flash twrp.. Then flash ex kernel then flash any root Zip. (supersu, magisk or phhh's superuser)
Twrp can be found from here. https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Click to expand...
Click to collapse
Thank you, will try this now.
Only the last SuperSU Beta defaults to systemless install. Any other ones require writing of a .SuperSU file to force systemless before rooting.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
SSJGod said:
Thank you, will try this now.
Click to expand...
Click to collapse
If you have not done this already, you can give it a try by flashing the stock boot.img via twrp and see if that boots the device.
I am not sure that it will work since, i have not tried it.
Exact same thing with the XT1625. I have also found that the systemless method of rooting with SuperSU kills my wifi and cellular network's connection abilities, which might just be a standard G4 thing but the only way I know of to fix it is reflashing the OS (data wipe not necessary).
Just thought this might be helpful to anyone who ran into similar issues to the ones I had.
also i'm still having issues with the stupid thing actually rooting but i'm gonna try again some other day.
just_magikkal said:
Exact same thing with the XT1625. I have also found that the systemless method of rooting with SuperSU kills my wifi and cellular network's connection abilities, which might just be a standard G4 thing but the only way I know of to fix it is reflashing the OS (data wipe not necessary).
Just thought this might be helpful to anyone who ran into similar issues to the ones I had.
also i'm still having issues with the stupid thing actually rooting but i'm gonna try again some other day.
Click to expand...
Click to collapse
I think that is the kernel issue.. you should try EX.. and then use SuperSU or maybe use Magisk SU..
abhi212b said:
That won't help!
Best is that u should flash stock rom, since the phone is bootlooping...
U can find it here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Flash it on bootloader screen via fastboot.
Do not relock the bootloader. Skip that step and also do NOT flash bootloader.img and partition. That can mess up the device.
once this is done, boot the device once... Finish the setup and then flash twrp.. Then flash ex kernel then flash any root Zip. (supersu, magisk or phhh's superuser)
Twrp can be found from here. https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Click to expand...
Click to collapse
Had the same problem as OP and this fixed it, thanks a lot man!
Good to hear now the phone is alive!
Hi. I was enjoying Lineage OS's latest ROM (14.1) and wasn't able to enjoy the "nightly" updates because when I went to do the update, I found out I needed a compatible recovery to do so. I had TWRP sitting on my computer and would FASTBOOT Boot twrp.img to flash roms. When I saw you needed to install twrp to make the Nightly update feature work, I flashed it with fastboot. I also went ahead and decided to start from scratch with a fresh install and used the latest Nightly LIneage OS file . After it installed, it booted up great. But when I went to add many apps back to my phone, so many of them were not showing up in the play store. And when some did, it would say "Incompatible Device" So I went to my settings and decided to try out the Nightly update hoping maybe that was the problem. When it booted to TWRP, nothing happened. So I hit REBOOT. and no matter what I choose, it just boots back into TWRP. Even when I hold the power button down and let it boot back up. Without touching any volume buttons, it just boots into TWRP. I can't get back to my OS. I'm going to try to install Lineage OS again and just hope I can get to my phone to make sure I'm getting messages from friends, doctors, etc...
Any help on how to fix this would be appreciated. I used this site " http://www.androidinfotech.com/2016...2-laser-ze551kl-marshmallow-install-twrp.html "
to root my phone so I could use Titanium Backup. I'm hoping something in there didn't mess me up.
Thank you in advance.
-Fuzzy
Well dang. I tried installing LINEAGE OS rom again and hoped for some strange reason it would boot into it. TWRP just keeps loading. I try the Reboot command in TWRP then choose SYSTEM and it still just goes to TWRP.
Well sometimes it just helps to air your frustration. As is true with many things in life. Say it out loud. Etc...
I was sure I had THE latest version of TWRP installed when this was happening. I rechecked to make sure. I didn't. I was 1 version away. Fastboot flashed that and it's booting normally . For now. Now, to see if I can get those apps to show up in the play store.
Things like Snapchat, Facebook messenger, etc... would just not show up.
Nope. That's still a problem . I wonder why this is happening?
Try clearing dalvik cache and sync you data for your mail account. I think those app wil show up. As for snapchat, you can't install it via playstore you can't pass safetynet.
FuzzyFone said:
Hi. I was enjoying Lineage OS's latest ROM (14.1) and wasn't able to enjoy the "nightly" updates because when I went to do the update, I found out I needed a compatible recovery to do so. I had TWRP sitting on my computer and would FASTBOOT Boot twrp.img to flash roms. When I saw you needed to install twrp to make the Nightly update feature work, I flashed it with fastboot. I also went ahead and decided to start from scratch with a fresh install and used the latest Nightly LIneage OS file . After it installed, it booted up great. But when I went to add many apps back to my phone, so many of them were not showing up in the play store. And when some did, it would say "Incompatible Device" So I went to my settings and decided to try out the Nightly update hoping maybe that was the problem. When it booted to TWRP, nothing happened. So I hit REBOOT. and no matter what I choose, it just boots back into TWRP. Even when I hold the power button down and let it boot back up. Without touching any volume buttons, it just boots into TWRP. I can't get back to my OS. I'm going to try to install Lineage OS again and just hope I can get to my phone to make sure I'm getting messages from friends, doctors, etc...
Any help on how to fix this would be appreciated. I used this site " http://www.androidinfotech.com/2016...2-laser-ze551kl-marshmallow-install-twrp.html "
to root my phone so I could use Titanium Backup. I'm hoping something in there didn't mess me up.
Thank you in advance.
-Fuzzy
Click to expand...
Click to collapse
What version of TWRP have you used? If it's 3.0.2.4 and below, update it.
darkeyes22 said:
What version of TWRP have you used? If it's 3.0.2.4 and below, update it.
Click to expand...
Click to collapse
(As shown in Post #3)
Already updated it. I got that part of the problem fixed. Thanks tho! :good:
FuzzyFone said:
(As shown in Post #3)
Already updated it. I got that part of the problem fixed. Thanks tho! :good:
Click to expand...
Click to collapse
What do you mean by saying "part of the problem"? Maybe I can help you with the rest of it.
darkeyes22 said:
What do you mean by saying "part of the problem"? Maybe I can help you with the rest of it.
Click to expand...
Click to collapse
Hello. I'm running the latest version of LineageOS 14.1 (just installed the nightly update) and several of the apps close the second I launch them. Clock was the first one I noticed . Loading pictures to share in other apps from Quckpic. and other apps I can't remember right now.
So I wanted to backup everything and try a different Rom thinking I might not have those problems. I installed SU and TWRP and then Titanium Backup Pro. After installing SU I had root. This morning I went to run a current backup and it said I no longer had root.
Dang. I have to go to the Pain Clinic. Time always catches up with me so fast when trying to problem solve.
Thank yo for reaching out! I really appreciate it. Especially with a phone that's not so popular out there in the wild that it's limited on folks available for help. it's 9:16am where I'm at. I'll probably be back in a few hours from now.
Thanks again, DarkEyes.
-Fuzzy
FuzzyFone said:
Hello. I'm running the latest version of LineageOS 14.1 (just installed the nightly update) and several of the apps close the second I launch them. Clock was the first one I noticed . Loading pictures to share in other apps from Quckpic. and other apps I can't remember right now.
So I wanted to backup everything and try a different Rom thinking I might not have those problems. I installed SU and TWRP and then Titanium Backup Pro. After installing SU I had root. This morning I went to run a current backup and it said I no longer had root.
Dang. I have to go to the Pain Clinic. Time always catches up with me so fast when trying to problem solve.
Thank yo for reaching out! I really appreciate it. Especially with a phone that's not so popular out there in the wild that it's limited on folks available for help. it's 9:16am where I'm at. I'll probably be back in a few hours from now.
Thanks again, DarkEyes.
-Fuzzy
Click to expand...
Click to collapse
Re-check your root with Root Checker. If you still have it, flash su removal through TWRP and flash systemless SuperSU. If you don't have it, just install systemless SuperSU. After you do that, boot back to the system (your boot might loop once - it's normal, do not interrupt boot), give TB pro root access, and see if it helped.
darkeyes22 said:
Re-check your root with Root Checker. If you still have it, flash su removal through TWRP and flash systemless SuperSU. If you don't have it, just install systemless SuperSU. After you do that, boot back to the system (your boot might loop once - it's normal, do not interrupt boot), give TB pro root access, and see if it helped.
Click to expand...
Click to collapse
Hello. Sorry it took me long to reply. After appointment, I was in too much pain to get online.
I installed thru Fastboot "addonsu-remove-14.1-arm64-signed.zip" rebooted, then installed addonsu-14.1-arm64-signed.zip thru Fastboot too and rebooted. Still no root. I checked it with RootChecker and there was no root.
Running latest nightly of LineageOS.
FuzzyFone said:
Hello. Sorry it took me long to reply. After appointment, I was in too much pain to get online.
I installed thru Fastboot "addonsu-remove-14.1-arm64-signed.zip" rebooted, then installed addonsu-14.1-arm64-signed.zip thru Fastboot too and rebooted. Still no root. I checked it with RootChecker and there was no root.
Running latest nightly of LineageOS.
Click to expand...
Click to collapse
Through Fastboot? Try through TWRP, flash removal, then flash Systemless SuperSU (not the one you have now).
Here is the link to systemless SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Hi
1st Step is Install official TWRP 3.1.1 which is availble for our device ze551kl aka Zool or ZooLD.
Boot in to TWRP
wipe cache+Dalvik cache+system+ASDF+internal storage.
now install Lineage rom latest version.
then gapps.
wipe dalvik cache.
hit Reboot system option
.it wlll not go in bootloop if u followed these steps which are guided by Devs here.
if u still facing bootloops u must have done extra ordinary thing with ur Device.
RonakRonak said:
Hi
1st Step is Install official TWRP 3.1.1 which is availble for our device ze551kl aka Zool or ZooLD.
Boot in to TWRP
wipe cache+Dalvik cache+system+ASDF+internal storage.
now install Lineage rom latest version.
then gapps.
wipe dalvik cache.
hit Reboot system option
.it wlll not go in bootloop if u followed these steps which are guided by Devs here.
if u still facing bootloops u must have done extra ordinary thing with ur Device.
Click to expand...
Click to collapse
It is Z00T that is ZE551KL, not Z00L. Do not even think about flashing something that was developed for Z00L on Z00T. It will not work.
Sent from my ASUS_Z00UD using XDA Labs
darkeyes22 said:
It is Z00T that is ZE551KL, not Z00L. Do not even think about flashing something that was developed for Z00L on Z00T. It will not work.
Sent from my ASUS_Z00UD using XDA Labs
Click to expand...
Click to collapse
Yes.i already mentioned model name.
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:
Hi, I downloaded the last update in OTA but after reboot I'm stuck on the boot animation.
I'm on the stock rom, never updated since I bought the phone in august.
I'm root and of course my bootloader is unlocked. I have TWRP that I managed to reinstall with ADB Sideload after this f***ing update get me back on stock recovery.
Now I keep trying install Roms (Official and customs) via ADB Sideload. Each time it look like the install is successful but then TWRP tell me "no os install, are you sure you want to reboot". Then I'm always stuck on the boot animation (at least it's the animation of the rom I tried to install).
Before I tried to update via OTA the 1st time I made a backup with TWRP but now all my files have been replaced by files with random letters ans numbers, so I can't even restore my backup and I'm affraid I lost everything I had on my phone.
What should I do now ?
Thanks for your help
Simply reflash the rom or do factory reset using pc { adb }
Swarup550 said:
Simply reflash the rom or do factory reset using pc { adb }
Click to expand...
Click to collapse
as i said, after flashing a rom it tell me "no os installed".
by factory reset you mean format hd ? i'd like not to loose everything.
Then you have to format it and then you have to install the stock rom.
Swarup550 said:
Then you have to format it and then you have to install the stock rom.
Click to expand...
Click to collapse
oh no :crying:
well, if i have no choice
Ya you hav to sacrifice your data
i think oneplus could warn you before download update !!!
i just had a message that told me that i was root and i won't be root anymore after updated. nothing about that i'll have to format my phone
It's done. It seems to work fine
Thanks a lot for your help
Kawa Banana said:
It's done. It seems to work fine
Thanks a lot for your help
Click to expand...
Click to collapse
Welcome.But next time if u want to root use adb to flash twrp then flash super su or i prefer magisk module:
I'm just trying to understand what I did here. This is the first phone that's given me this much trouble.
Was running 7.1.1 stock. Finally got annoyed by that auto volume thing from sony that I had time to flash AOSP. I followed
https://forum.xda-developers.com/x-compact/development/nougat-7-1-1-android-source-project-t3555510
I used xperifirm/flashtool to update to newest UK firmware ( US has no fingerprint ) . I did NOT backup my drm keys. I have them from before when I rooted. Besides I didn't need them really. I use opencamera.
Followed that guide exactly. Everything worked. Then I flashed twrp 3.1.1 from adb. I think this is where I went wrong. I wanted to flash supersu and viper4android. As soon as I tried this I got twrp errors about mounting /data. Missing crypto footers. I also noticed that supersu binary always said it needed updating, and viper4android would not install drivers.
Did some googling. Saw I just had to format /data from twrp. TWRP was unable to format data with the same errors. More google, saw I had to recreate the /data from terminal from this link https://forum.xda-developers.com/xperia-sp/help/format-data-using-twrp-3-0-2-t3371137 .
Did that. Same errors in twrp. Ok had enough. Restored my twrp backup from 7.1.1 where everything worked. That went through and just hosed everything, due to not being able to read /data. After this finished I was stuck in a boot loop.
Got into fastboot and reran the original AOSP guide above. Now I'm there. Everything left exactly as it was. No twrp etc.
My question is what the heck did I break and how? And as a secondary question can I root this, if so how? The recovery that is flashed with that guide cannot mount /sdcard so I don't see a way to flash supersu for example.
Just trying to understand before I really break something.
j1tters said:
I'm just trying to understand what I did here. This is the first phone that's given me this much trouble.
Was running 7.1.1 stock. Finally got annoyed by that auto volume thing from sony that I had time to flash AOSP. I followed
https://forum.xda-developers.com/x-compact/development/nougat-7-1-1-android-source-project-t3555510
I used xperifirm/flashtool to update to newest UK firmware ( US has no fingerprint ) . I did NOT backup my drm keys. I have them from before when I rooted. Besides I didn't need them really. I use opencamera.
Followed that guide exactly. Everything worked. Then I flashed twrp 3.1.1 from adb. I think this is where I went wrong. I wanted to flash supersu and viper4android. As soon as I tried this I got twrp errors about mounting /data. Missing crypto footers. I also noticed that supersu binary always said it needed updating, and viper4android would not install drivers.
Did some googling. Saw I just had to format /data from twrp. TWRP was unable to format data with the same errors. More google, saw I had to recreate the /data from terminal from this link https://forum.xda-developers.com/xperia-sp/help/format-data-using-twrp-3-0-2-t3371137 .
Did that. Same errors in twrp. Ok had enough. Restored my twrp backup from 7.1.1 where everything worked. That went through and just hosed everything, due to not being able to read /data. After this finished I was stuck in a boot loop.
Got into fastboot and reran the original AOSP guide above. Now I'm there. Everything left exactly as it was. No twrp etc.
My question is what the heck did I break and how? And as a secondary question can I root this, if so how? The recovery that is flashed with that guide cannot mount /sdcard so I don't see a way to flash supersu for example.
Just trying to understand before I really break something.
Click to expand...
Click to collapse
I don't know if I know what went wrong, but I wonder, 1) why not Magisk, and 2) why not TWRP 3.2.1? Might be better off...
levone1 said:
I don't know if I know what went wrong, but I wonder, 1) why not Magisk, and 2) why not TWRP 3.2.1? Might be better off...
Click to expand...
Click to collapse
I've never really used magisk. Flashable zip? I'd need a working twrp since the recovery included with that rom can't mount /sdcard.
I think I just happened to grab 3.1.1, I must have missed the 3.2.1 version. At this point I'm not flashing anything until I know it works. I don't remember seeing it in nougat, but I see that under 8.1 the phone status shows as encrypted.
I'm a little leery of flashing anything currently since I currently have no root so I cant use titanium to backup. I also don't want to end up with a non working recovery again. I posted to that aosp thread seeing if anyone rooted it.
At this point I'd almost like to get a working twrp just to go back tro 7.1 where everything worked.
j1tters said:
I've never really used magisk. Flashable zip? I'd need a working twrp since the recovery included with that rom can't mount /sdcard.
I think I just happened to grab 3.1.1, I must have missed the 3.2.1 version. At this point I'm not flashing anything until I know it works. I don't remember seeing it in nougat, but I see that under 8.1 the phone status shows as encrypted.
I'm a little leery of flashing anything currently since I currently have no root so I cant use titanium to backup. I also don't want to end up with a non working recovery again. I posted to that aosp thread seeing if anyone rooted it.
At this point I'd almost like to get a working twrp just to go back tro 7.1 where everything worked.
Click to expand...
Click to collapse
Find twrp in rom forum here, and search xda for Magisk. Flash twrp, wipe everything, then flash rom, then flash Magisk. See if all better... Also, you can flash V4A modules, (and many others), through Magisk.
Twrp - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
Magisk - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
levone1 said:
Find twrp in rom forum here, and search xda for Magisk. Flash twrp, wipe everything, then flash rom, then flash Magisk. See if all better... Also, you can flash V4A modules, (and many others), through Magisk.
Twrp - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
Magisk - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Ok. So I'm reflashing the rom via fastboot just like that guide states. Just ignoring the recovery flash?
j1tters said:
Ok. So I'm reflashing the rom via fastboot just like that guide states. Just ignoring the recovery flash?
Click to expand...
Click to collapse
I have never flashed recovery with aosp, because it doesn't do anything. I haven't tried aosp O yet, though. Typically, yes, skip the recovery flash and flash twrp instead.
levone1 said:
I have never flashed recovery with aosp, because it doesn't do anything. I haven't tried aosp O yet, though. Typically, yes, skip the recovery flash and flash twrp instead.
Click to expand...
Click to collapse
I'll give it a whirl. One question though, since I've never run into this. What do you mean because it doesn't do anything? Granted this is the only aosp I've played with so far, so my knowledge is a bit limited.
j1tters said:
I'll give it a whirl. One question though, since I've never run into this. What do you mean because it doesn't do anything? Granted this is the only aosp I've played with so far, so my knowledge is a bit limited.
Click to expand...
Click to collapse
Stock recovery is usually limited to stock functions. If you want to customize, you need custom recovery.
levone1 said:
Stock recovery is usually limited to stock functions. If you want to customize, you need custom recovery.
Click to expand...
Click to collapse
Ohhh. right. I thought you meant recovery didn't do anything with aosp. Read that wrong, brain fart.
So nope. Twrp cannot read /data. Same error as before. Magisk seems to have installed.
My guess is this is all coming from the forced encryption, though I haven't done enough research.. I'm going to see if I can get viper running..
j1tters said:
Ok. So I'm reflashing the rom via fastboot just like that guide states. Just ignoring the recovery flash?
Click to expand...
Click to collapse
Just wanted to say thanks. Magisk and viper are installed and working. TWRP still errors out with not being able to read /data but I got viper and root, and thats all I wanted.
Thanks!
j1tters said:
So nope. Twrp cannot read /data. Same error as before. Magisk seems to have installed.
My guess is this is all coming from the forced encryption, though I haven't done enough research.. I'm going to see if I can get viper running..
Click to expand...
Click to collapse
Yeah, I guess still no custom kernels for O yet, so... Did you already try decrypt data with twrp?
Nope. I got what I wanted at this point. I'm leaving well enough alone. I don't see having to really do anything with TWRP in the near future. I'll miss being able to do a full backup, and I'm a little annoyed I cant restore my 7.1 backup but I can live with that. I see I can decrypt but I'm a little gun shy and don't want to break anything again.
At the end of the day AOSP + viper is really all I needed.
Thanks again for all the help.