Related
So tried to dirty flash one rom over the another, both 7.1.1 never been a problem before.
No my phone boots up but everythigns is just black( never happened before) Also i cant reach twrp since the phone is just saysing no command and there is a red triangle.
Well just boot into recovery use a toolkit and wipe the phone and install the rom again.... Well, my mac cant find the phone.
Basically i dont know what to do now...
mosd said:
So tried to dirty flash one rom over the another, both 7.1.1 never been a problem before.
No my phone boots up but everythigns is just black( never happened before) Also i cant reach twrp since the phone is just saysing no command and there is a red triangle.
Well just boot into recovery use a toolkit and wipe the phone and install the rom again.... Well, my mac cant find the phone.
Basically i dont know what to do now...
Click to expand...
Click to collapse
You should read the sticky thread in general. Beginners guide.
Red triangle with no command. That's stock recovery which is why you can't access TWRP, you don't have it anymore.
Also, not for nothing, don't dirty flash between different ROMs. I honestly find it extremely hard to believe (borderline of not at all) that you've been doing it 5 years and never had a single problem.
Here you go: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page519
Edit: Stop using toolkits for this exact reason. Follow the guide I posted above and do everything manually and you'll be fine.
ive had problems before but always solved them. I got the phone up and running now. Problem is that i need to flash gapps and i have no google apps on my phone. I think i will solve it. Thanks.
mosd said:
ive had problems before but always solved them. I got the phone up and running now. Problem is that i need to flash gapps and i have no google apps on my phone. I think i will solve it. Thanks.
Click to expand...
Click to collapse
You shouldn't ever switch ROMs without clean flashing. I hope you're not reporting bugs in threads while dirty flashing between different ROMs.
Anyways, ROMs can generally boot without Gapps. Any source built ROM, per Google's rules, cannot include Gapps. You can flash a source built ROM without Gapps and boot without Play Store, etc.
You don't even have a custom recovery to flash a Gapps package.
You really need to take the time to read the thread I posted so you can learn how to do things correctly so you don't need to post a thread every time something goes wrong, which likely will the way you're flashing now.
No offense intended.
I thank you for your advice. Here what i did. Since i didint had any google services i had to download google play apk from the internet. DIdnt work without google services...so installed google services but everything crashed.
1. Download flashfire but didnt work...why? Because my rom came with superuser.
2. Install flashify and then install twrp.
3. Install gapps via twrp
4. Wipe, install rom+gapps via twrp.
5. Sucess.
Thanks
Seems like fastboot would have been an easier method....
Also not bricked, simply user error.
mosd said:
I thank you for your advice. Here what i did. Since i didint had any google services i had to download google play apk from the internet. DIdnt work without google services...so installed google services but everything crashed.
1. Download flashfire but didnt work...why? Because my rom came with superuser.
2. Install flashify and then install twrp.
3. Install gapps via twrp
4. Wipe, install rom+gapps via twrp.
5. Sucess.
Thanks
Click to expand...
Click to collapse
I don't understand step 3 given what you did in step 4 but at least you got your phone back.
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.
Hey all.
I'm in need of a bit of help. I have a J5 and was getting sick of being told theres never any space to install apps, so I rooted it hoping to be able to remove the stock apps that come inbuilt like word, excel etc.... Anyway, I then decided to take it a step further and try and install a custom rom, long story short, im stuck with a green screen
I've been googling and following tutorials for hours now and I'm really at the point of giving up, so thought I would reach out incase i'm just over tired from it all and making silly mistakes.
I have TWRP 3.1.1-0 on my phone, I installed Lineage 14.1 figured out how to change the updater-script, green screen. I then installed a stock rom advanced I found here, green screen. I tried Aokp nightly nougat, green screen. After googling green screen I found a post saying its something to do with incompatibility from TWRP and that I need to install lollipop 5.1.1 firmware first before I can change to lilneage 14.1... Ive been googling for ages and I'm either coming to sites that want me to pay to download it at a reasonable speed or wait for hours. I'm a bit dubious as no other rom seems to have worked and I'm not sitting here with an empty phone.
Thanks.
LowKee84 said:
Hey all.
I'm in need of a bit of help. I have a J5 and was getting sick of being told theres never any space to install apps, so I rooted it hoping to be able to remove the stock apps that come inbuilt like word, excel etc.... Anyway, I then decided to take it a step further and try and install a custom rom, long story short, im stuck with a green screen
I've been googling and following tutorials for hours now and I'm really at the point of giving up, so thought I would reach out incase i'm just over tired from it all and making silly mistakes.
I have TWRP 3.1.1-0 on my phone, I installed Lineage 14.1 figured out how to change the updater-script, green screen. I then installed a stock rom advanced I found here, green screen. I tried Aokp nightly nougat, green screen. After googling green screen I found a post saying its something to do with incompatibility from TWRP and that I need to install lollipop 5.1.1 firmware first before I can change to lilneage 14.1... Ive been googling for ages and I'm either coming to sites that want me to pay to download it at a reasonable speed or wait for hours. I'm a bit dubious as no other rom seems to have worked and I'm not sitting here with an empty phone.
Thanks.
Click to expand...
Click to collapse
Flashing LP / MM / N ROMs based on AOSP/LOS over stock MM/ROMs based on stock MM --> green screen.
How to flash MM/N ROMs based on AOSP/LOS:
1) Install 5.1.1 stock firmware.
2) Install TWRP 5.1.1 (Nick's or Vince's).
3) Flash the MM/N ROM you want.
#Henkate said:
Flashing LP / MM / N ROMs based on AOSP/LOS over stock MM/ROMs based on stock MM --> green screen.
How to flash MM/N ROMs based on AOSP/LOS:
1) Install 5.1.1 stock firmware.
2) Install TWRP 5.1.1 (Nick's or Vince's).
3) Flash the MM/N ROM you want.
Click to expand...
Click to collapse
Don't suppose you know where I can find a copy, as I said in earlier post all the sites I find either take ages or want paying to upgrade to premium.
LowKee84 said:
Don't suppose you know where I can find a copy, as I said in earlier post all the sites I find either take ages or want paying to upgrade to premium.
Click to expand...
Click to collapse
Updato.
Awesome, went from 3 hour download to 15 minute download, finally some progress, thank you
LowKee84 said:
Awesome, went from 3 hour download to 15 minute download, finally some progress, thank you
Click to expand...
Click to collapse
Meh, tried to install but saying invalid zip file format.
LowKee84 said:
Meh, tried to install but saying invalid zip file format.
Click to expand...
Click to collapse
You extract the .zip and install it with Odin...
#Henkate said:
You extract the .zip and install it with Odin...
Click to expand...
Click to collapse
Okay, done that. So now I can install another rom from twrp or do I do it via odin?
LowKee84 said:
Okay, done that. So now I can install another rom from twrp or do I do it via odin?
Click to expand...
Click to collapse
TWRP.
You install only stock ROM with Odin (.tar format).
#Henkate said:
TWRP.
You install only stock ROM with Odin (.tar format).
Click to expand...
Click to collapse
Okay.
Anything else I need to do first? Do I need to root it again?
LowKee84 said:
Okay.
Anything else I need to do first? Do I need to root it again?
Click to expand...
Click to collapse
Most of the roms comes with root. In case it doesnt have root, you flash it after flashing the ROM.
#Henkate said:
Most of the roms comes with root. In case it doesnt have root, you flash it after flashing the ROM.
Click to expand...
Click to collapse
When I installed 5.1.1 it changed back to android recovery so I had to reinstall twrs recovery, then root again to be able to flash, but this time Lineage 14.1 finally installed
Thank you for your help.
LowKee84 said:
When I installed 5.1.1 it changed back to android recovery so I had to reinstall twrs recovery, then root again to be able to flash, but this time Lineage 14.1 finally installed
Thank you for your help.
Click to expand...
Click to collapse
So... I wanted to remove audioFx as I have no need for it, I had to root again... I tried the same root that I used originally but made it so it kept getting stuck on lineage boot screen and gave me no response on trying to boot to recovery. Any idea what went wrong?
Back to lineage again without root.
LowKee84 said:
So... I wanted to remove audioFx as I have no need for it, I had to root again... I tried the same root that I used originally but made it so it kept getting stuck on lineage boot screen and gave me no response on trying to boot to recovery. Any idea what went wrong?
Back to lineage again without root.
Click to expand...
Click to collapse
Did you flash the official SuperSU module from the lineage site?
No, I used Odin with the cf autoroot for my device.
I had problems with cf auto root, particularly the green screen on boot,try flashing the supersu from their site.
Tried it, used first one on the site, installed okay but can't see the su app anywhere, then tried the x86 version in case but wouldn't install.
Oh never mind, had to enable dev mode and enable root for apps and adb first, there is no actual app. I ran another app and it asked for root permission.
LowKee84 said:
Oh never mind, had to enable dev mode and enable root for apps and adb first, there is no actual app. I ran another app and it asked for root permission.
Click to expand...
Click to collapse
So it works?
It work
Hello all,
THIS IS AN ANNOUNCEMENT, DISCUSSION AND INFORMATION THREAD FOR OFFICIAL DIRTY UNICORNS 14.x BUILDS FOR PIXEL 2 XL (taimen).
Special thanks to all who were and are involved in the development and also to the maintenance of this ROM.
Flashing instructions:
Go to TWRP
Factory reset
Flash ROM and TWRP zip
Reboot and enjoy!!
If on a previous DU build:
Go to TWRP
Flash ROM and TWRP zip
Reboot and enjoy!!
Note:
If you're going to flash magisk make sure you flash it after you've booted the OS once.
Reminder
Weeklies and official builds are signed with private keys. This means that if you’re on the first official build or last week’s weekly, you can dirty flash this official build. If you’re on anything other than that and want to use this build you MUST perform a full wipe in recovery. If you decide to disregard this and flash this build or a weekly on top of anything, you will not be able to boot. Have fun looking at a black screen
ANY BUGS MAY BE DISCUSSED HERE OR WITH THE DEVELOPMENT TEAM ON THEIR TELEGRAM CHANNELONLY IF YOU HAVE CLEAN FLASHED
Reserved
its an excellent rom! i helped test here n there n can confirm its almost completely bug free
elliwigy said:
its an excellent rom! i helped test here n there n can confirm its almost completely bug free
Click to expand...
Click to collapse
Can you tell how is the camera quality on that?
And they have listed audi during video is janky is that for stock camera or for apps like whatsapp and snapchat too?
Sent from my Google Pixel 2 XL using XDA Labs
Been waiting very impatiently for this lol
Prattham said:
Can you tell how is the camera quality on that?
And they have listed audi during video is janky is that for stock camera or for apps like whatsapp and snapchat too?
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Just might be seldom janky...not all the time...I've tested stock DU cam, WhatsApp, Facebook, Instagram.... all working fine on all 3 different occasions:good:
Cam quality is as good as stock
No hangups...lags...or other issues
I will be using it as my daily driver
amandeepparmar said:
Just might be seldom janky...not all the time...I've tested stock DU cam, WhatsApp, Facebook, Instagram.... all working fine on all 3 different occasions:good:
Cam quality is as good as stock
No hangups...lags...or other issues
I will be using it as my daily driver
Click to expand...
Click to collapse
Can you post screenshot of the du tweaks that are currently in the rom?
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
Can you post screenshot of the du tweaks that are currently in the rom?
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
DU Tweaks...check screenshots attached
amandeepparmar said:
DU Tweaks...check screenshots attached
Click to expand...
Click to collapse
Good
What steps did you followed to install?
Cheers ?
Sent from my Google Pixel 2 XL using XDA Labs
amandeepparmar said:
DU Tweaks...check screenshots attached
Click to expand...
Click to collapse
Factory reset in twrp. flash rom and twrp. Setup phone and flash afterwards kernel and magisk if needed
Anyone know if it has support for esim on Fi?
Flashing this will remove TWRP and Magisk. Just wanted to throw that out there.
MacTheRipperr said:
Flashing this will remove TWRP and Magisk. Just wanted to throw that out there.
Click to expand...
Click to collapse
Yes it will according to what I've been reading. I just got my pixel and have been trying to catch up with all the new a and b slots and how recovery is now baked into the boot.img, so from what I understand is that if you flash anything new such as rom or kernel a flash of both twrp and your choice of root is needed also or you will have stock recovery. So much different from my Nexus 6P. Lol. I have a lot to learn that's for sure
Sent from my Pixel 2 XL using XDA-Developers Legacy app
This rom is awesome !! DU always bring the goods
I've been running since yesterday. Spaceman killed it! Amazing work, where can we donate?
MacTheRipperr said:
Flashing this will remove TWRP and Magisk. Just wanted to throw that out there.
Click to expand...
Click to collapse
Yes but you can reflash twrp and magisk with absolutely no errors ,also twrp has no touch issues with the kernal that's already baked in rom!!!! It's a great rom!
Anyone else having trouble getting this to boot?
I've followed the instructions exactly. Reboot to TWRP (3.2.1-0), factory reset via the wipe menu, install the ROM .zip followed by the TWRP installer zip.
Go to reboot, TWRP asks me if I'm sure I want to do this as there's not an OS installed. I don't know what else to do other than say 'yes' and then it boots to the Google logo with the unlocked icon at the bottom of the screen and just hangs indefinitely at that point. Tried redownloading and recopying the ROM .zip to internal storage and all steps again too.
Any ideas? I've wiped this damn phone so many times and flashed the factory images so many times trying to get a custom ROM to work I'm about to give up. And my phone seems to damn janky where sometimes it does that same freeze on boot (or freezes on the TWRP splash screen) but then a quick reboot will fix it. Doesn't make any sense.
ohlin5 said:
Anyone else having trouble getting this to boot?
I've followed the instructions exactly. Reboot to TWRP (3.2.1-0), factory reset via the wipe menu, install the ROM .zip followed by the TWRP installer zip.
Go to reboot, TWRP asks me if I'm sure I want to do this as there's not an OS installed. I don't know what else to do other than say 'yes' and then it boots to the Google logo with the unlocked icon at the bottom of the screen and just hangs indefinitely at that point.
Any ideas? I've wiped this damn phone so many times and flashed the factory images so many times trying to get a custom ROM to work I'm about to give up. And my phone seems to damn janky where sometimes it does that same freeze on boot (or freezes on the TWRP splash screen) but then a quick reboot will fix it. Doesn't make any sense.
Click to expand...
Click to collapse
I went back to latest stock using deuces script. Boot twrp. Flash twrp then the rom...boot the rom. Go back into twrp and flash magisk
I had no problems getting it to boot, I followed the op. Factory reset, flash ROM, flash magisk, flash twrp and boot into system. It booted right up no problems
Sent from my Pixel 2 XL using XDA-Developers Legacy app
Reuben_skelz92 said:
I went back to latest stock using deuces script. Boot twrp. Flash twrp then the rom...boot the rom. Go back into twrp and flash magisk
Click to expand...
Click to collapse
Did you let the phone do it's initial boot after deuce's script ran? Or just stayed in fastboot mode, fastboot booted to TWRP, and flash the ROM and TWRP installer zip?
Also, did you format userdata when given the option in deuce's script? And you flashed TWRP before the ROM? I was under the understanding that the ROM flash would erase the TWRP install.
EDIT: I didn't format userdata, didn't reboot afterwards (just booted straight into TWRP and proceeded), and flashed TWRP before ROM and now it is indeed booting. Just need to figure out now whether or not TWRP is still installed. Many thanks! Deuce's must have fixed something I must have janked I guess.
EDIT2: Yeah appears TWRP should be flashed after the ROM not (just) before like the DU post says. I'm back to stock recovery afterwards.
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: