Develop Bugs

Does TWRP work on android 7.0?

If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?

You need to decrypt the phone for it to work.

Hmm anyone got the 7.0 recovery? I installed it thinking it would work but I want to keep the system encrypted. Does the stock 7.0 recovery mount system? I want to mod my build.prop dpi.

trollyphysicist said:
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
Click to expand...
Click to collapse
Try TWRP 3.0.2-1, should work properly.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Try TWRP 3.0.2-1, should work properly.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I just tried 3.0.2-1, and it worked. Before that, 3.0.2-0 also got stuck at the splash screen. However, I wasn't able to root. I tried installing SU via TWRP, but it didn't successfully root.

pkadavid said:
I just tried 3.0.2-1, and it worked. Before that, 3.0.2-0 also got stuck at the splash screen. However, I wasn't able to root. I tried installing SU via TWRP, but it didn't successfully root.
Click to expand...
Click to collapse
I had no issues obtaining root with the new twrp on an encrypted phone.

Am I the only one who encounters the flasing of recovery not sticking? After system reboot, then going back to recovery, it reverts to stock.

legendarren said:
Am I the only one who encounters the flasing of recovery not sticking? After system reboot, then going back to recovery, it reverts to stock.
Click to expand...
Click to collapse
Flash twrp, while still in bootloader volume down to reboot bootloader, hit the power button, volume down to reboot recovery, hit the power button. Twrp should stick now.
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
Flash twrp, while still in bootloader volume down to reboot bootloader, hit the power button, volume down to reboot recovery, hit the power button. Twrp should stick now.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks, man. But still TWRP still doesn't stick after system reboot.

legendarren said:
Thanks, man. But still TWRP still doesn't stick after system reboot.
Click to expand...
Click to collapse
If you decrypt it first by flashing the modified boot.img, and then flash recovery and reboot it should stick and work right? Can you kindly describe your steps?

Vanschtezla said:
If you decrypt it first by flashing the modified boot.img, and then flash recovery and reboot it should stick and work right? Can you kindly describe your steps?
Click to expand...
Click to collapse
Yes, I forgot about decrypting. It works fine now, thanks!!

legendarren said:
Yes, I forgot about decrypting. It works fine now, thanks!!
Click to expand...
Click to collapse
No problem mate ??

Vanschtezla said:
No problem mate ??
Click to expand...
Click to collapse
Which boot IMG did you use to decrypt the final release of n?

kevtrysmoddin said:
Which boot IMG did you use to decrypt the final release of n?
Click to expand...
Click to collapse
In my case I updated mine from DP5. I had my DP5 decrypted and rooted and update it using the flashfire app to flash the ota. I don't think any of the existing modified boot.img will work on the final release yet idk mate.

Vanschtezla said:
In my case I updated mine from DP5. I had my DP5 decrypted and rooted and update it using the flashfire app to flash the ota. I don't think any of the existing modified boot.img will work on the final release yet idk mate.
Click to expand...
Click to collapse
No probs

trollyphysicist said:
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
Click to expand...
Click to collapse
Just installed twrp and seeing if flashign super su stuck or not... Have to wait for modified boot images to decrypt, though
---------- Post added at 10:25 AM ---------- Previous post was at 10:14 AM ----------
trollyphysicist said:
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
Click to expand...
Click to collapse
Update-phone is decrypted after installing twrp, wiping userdate, rebooting twrp, flashing latest super su, rebooting

eggman618 said:
Hmm anyone got the 7.0 recovery? I installed it thinking it would work but I want to keep the system encrypted. Does the stock 7.0 recovery mount system? I want to mod my build.prop dpi.
Click to expand...
Click to collapse
3.0.2-1 TWRP that got released soon after I posted fixed any hanging issues.

eggman618 said:
3.0.2-1 TWRP that got released soon after I posted fixed any hanging issues.
Click to expand...
Click to collapse
-1 installs, but two issues if you're encrypted:
1) TWRP doesn't stick. After a restart, you won't be able to get back into TWRP and need to reflash it.
2) Installing SU via TWRP doesn't work. It runs into an error if you read the responses during the flash in TWRP.
We'll just have to be patient until the devs do their magic on the encrypted version.

pkadavid said:
-1 installs, but two issues if you're encrypted:
1) TWRP doesn't stick. After a restart, you won't be able to get back into TWRP and need to reflash it.
2) Installing SU via TWRP doesn't work. It runs into an error if you read the responses during the flash in TWRP.
We'll just have to be patient until the devs do their magic on the encrypted version.
Click to expand...
Click to collapse
If you root using phh's superuser and magisk, TWRP will stick. His solution also allows you to use Android Pay with root, albeit with a little hoop-jumping
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382

I had the twrp not sticking issue in the past. What has worked is to boot twrp, not flash it, then flash SU. Then boot back into the bootloader and flash twrp.
Sent from my Nexus 9 using XDA-Developers mobile app

Sprint Root questions and clarification

Hello XDA, I am trying to figure out all the steps to get mainly Twrp, Magisk, Viper and, Substratum working correctly without any hiccups. I have been reading the forums all day and trying to get all the files necessary to get all that working and the files to revert to stock if it doesn't work. I know after the Bootloader is unlocked I won't be able to relock it due to no Moto signed boot images. I just don't want to brick it and be here with other problems later.
So far I have done the following
1. Installed ADB and Fastboot + Drivers
2. Done everything to get the code to unlock bootloader
3. Downloaded the files to flash twrp from (https://forum.xda-developers.com/z2-force/development/twrp-3-1-1-0-moto-z2-force-nash-t3687421)
4. Downloaded the latest stock NCX26.122-59-8 to extract the boot img and patch it with Magisk manager from (https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859)
I think I have everything I need to get it rooted. Here's where I get kinda confused. My phone (XT1789-03 Sprint) is on NCXS26.122-59-8-11 November patch (I think the S is for sprint lol). Would It be okay to flash the Magisk patched boot img from the one I downloaded after I unlock the bootloader? Is Twrp necessary? Is there anything else I need to know about? Thanks in advance.

This forum just died? What the hell noone helps anymore???
Sent from my XT1650 using Tapatalk

TWRP is official now. Download the bootable image from https://twrp.me/motorola/motorolamotoz2force.html and the corresponding zip. Boot to twrp and flash the zip. Flash Magisk and install what you want that needs root. Hint: I'd advise the Viper4Android from Magisk modules in the magisk app.

Uzephi said:
Boot to twrp and flash the zip.
Click to expand...
Click to collapse
What do you mean by this? Fastboot flash TWRP, but then flash what zip?

breakerfall said:
What do you mean by this? Fastboot flash TWRP, but then flash what zip?
Click to expand...
Click to collapse
Do NOT flash the twrp img. "Fastboot boot imagename.img" then flash the twrp zip if you wish to have it as your recovery. You can find both on twrp.me.

This hard.. even with instructions u don't know what to flash where and what it will achieve lol. I just want unlock and root. What's the easiest way to do that on sprint z2 force?
So far I understand u need to install twrp to root with magisk, then use twrp to flash magisk Img, then boot up install magisk apk and u should be rooted. Hope I've got that all right.
But do any of the images on this site also unlock gsm on sprint or TMobile?
Sent from my Moto Z (2) using Tapatalk

Uzephi said:
Do NOT flash the twrp img. "Fastboot boot imagename.img" then flash the twrp zip if you wish to have it as your recovery. You can find both on twrp.me.
Click to expand...
Click to collapse
Not trying to be a **** here, but what exactly do you mean by imagename.img? .. the twrp.img file? and if I don't want TWRP as recovery, then are you saying that it will remain stock if I don't flash the twrp.zip file?
I recently did this on an Essential phone, and the process was: fastboot flash TWRP.img, reboot to TWRP (recovery), flash stock boot.img, then flash magisk.zip.
The last phone I rooted/rommed before that was a Nexus 6, and **** was different then.

breakerfall said:
Not trying to be a **** here, but what exactly do you mean by imagename.img? .. the twrp.img file? and if I don't want TWRP as recovery, then are you saying that it will remain stock if I don't flash the twrp.zip file?
I recently did this on an Essential phone, and the process was: fastboot flash TWRP.img, reboot to TWRP (recovery), flash stock boot.img, then flash magisk.zip.
The last phone I rooted/rommed before that was a Nexus 6, and **** was different then.
Click to expand...
Click to collapse
Yes, just boot it. If you flash, your phone will boot to recovery. Don't flash the TWRP image!!
---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------
jmagi said:
So far I understand u need to install twrp to root with magisk, then use twrp to flash magisk Img, then boot up install magisk apk and u should be rooted. Hope I've got that all right.
Click to expand...
Click to collapse
You don't flash the TWRP.img file!!! You fastboot boot it. It will temp boot to twrp

Uzephi said:
Yes, just boot it. If you flash, your phone will boot to recovery. Don't flash the TWRP image!
Click to expand...
Click to collapse
Ahhhh!
Fastboot boot TWRP.img, then just flash the magisk.zip in TWRP, right?
Thank you!
Also, @jmagi -- you shouldn't have to manually install the magisk apk. Flashing the magisk.zip in TWRP should result in a Magisk app in your "all apps" next time you boot.

Uzephi said:
Yes, just boot it. If you flash, your phone will boot to recovery. Don't flash the TWRP image!!
---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------
You don't flash the TWRP.img file!!! You fastboot boot it. It will temp boot to twrp
Click to expand...
Click to collapse
Ohhh thats how it works. So i dont have to install twrp from playstore?
Sent from my Moto Z (2) using Tapatalk

jmagi said:
Ohhh thats how it works. So i dont have to install twrp from playstore?
Click to expand...
Click to collapse
No, you don't

Uzephi said:
No, you don't
Click to expand...
Click to collapse
Ok got it thank you. So fastboot boot twrp, and from twrp flash magisk.img then run magisk after bootup.
I too havent rooted a phone since droid4 which was just doubleclick a bat file lol. All this twrp stuff is new to me. Hope i got it right. Love this phone. Might get another one soon and the qwerty keyboard mod is expected on amazon within a couple months. Only reason i upgraded.
Sent from my Moto Z (2) using Tapatalk

jmagi said:
Ok got it thank you. So fastboot boot twrp, and from twrp flash magisk.img then run magisk after bootup.
I too havent rooted a phone since droid4 which was just doubleclick a bat file lol. All this twrp stuff is new to me. Hope i got it right. Love this phone. Might get another one soon and the qwerty keyboard mod is expected on amazon within a couple months. Only reason i upgraded.
Click to expand...
Click to collapse
Some people had issues and needed to wipe user data after flashing magisk

Messed up with TWRP

Hi all, got TWRP installed OK on my Pixel 2 XL, hit reboot and then it goes straight back into TWRP, but with no Touch. So, thought I could flash a new kernel (Flash?) but... no ADB! I guess the phone hasn't probably booted so ADB can't see the phone.
Any options at this point?!

rendez2k said:
Hi all, got TWRP installed OK on my Pixel 2 XL, hit reboot and then it goes straight back into TWRP, but with no Touch. So, thought I could flash a new kernel (Flash?) but... no ADB! I guess the phone hasn't probably booted so ADB can't see the phone.
Any options at this point?!
Click to expand...
Click to collapse
If your phone boots back to bootloader on reboot, you did something wrong. Reflash system imgs and start over.

Thanks! Is that a matter of following the guides on the official google download page and getting the factory images?

rendez2k said:
Thanks! Is that a matter of following the guides on the official google download page and getting the factory images?
Click to expand...
Click to collapse
Yes. If you don't want your data wiped, open the install.bat file and take off the -w.
Did you unlock your bootloader correctly? Unlock critical? I believe the pixel 2 xl is the only phone where that has to be done.

Boot into bootloader and fastboot flash recovery.img again, once your in recovery, flash the recovery.zip from your storage again, then reboot recovery.... its happened to me, usually when I switch slots, all I have to do is reflash recovery.
Also note, If I am trying to boot at that point (rather than flash a ROM), I usually just flash the kernel and magisk and I'm good to go.

Thanks all! I flashed the patched boot.img again and it seems to be working OK

OK, this whole thing is confusing me now! I get TWRP installed then I have to re-flash my boot.img before I quit TWRP (a magisk patched version of Flash) or the phone keeps booting to TWRP. Thats fine, but when I've flashed the boot.img I loose TWRP!

rendez2k said:
OK, this whole thing is confusing me now! I get TWRP installed then I have to re-flash my boot.img before I quit TWRP (a magisk patched version of Flash) or the phone keeps booting to TWRP. Thats fine, but when I've flashed the boot.img I loose TWRP!
Click to expand...
Click to collapse
Yes you do loose twrp after flashing the boot.img. the reason being that stock recovery resides in the boot.img. So when you flash it, bye..bye twrp! Why not just fastboot twrp, then once in twrp, flash the twrp installer zip, then flash your custom kernel(if used) then flash the magisk zip for root. :good:

Ok! So this is where I'm confused. The Flash Kernel is called boot.img? So I'm flashing it in twrp with the boot option?

rendez2k said:
Ok! So this is where I'm confused. The Flash Kernel is called boot.img? So I'm flashing it in twrp with the boot option?
Click to expand...
Click to collapse
No. Flash kernel is just the kernel, the boot.img is from the factory image. Flash the zip version of Flash kernel in twrp, then flash magisk.zip :good:

Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?

rendez2k said:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
Click to expand...
Click to collapse
Download the 14mb FlashKernel-Taimen-v2.30.zip instead and put it in your phone to flash from within TWRP, followed by the magisk zip
http://nchancellor.net/downloads/kernels/taimen/8.1.0/stable/

rendez2k said:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
Click to expand...
Click to collapse
DON'T DO THAT! You'll bootloop for sure!! Do what the post below says, and what I told you earlier!
Pyr0x64 said:
Download the 14mb FlashKernel-Taimen-v2.30.zip instead and put it in your phone to flash from within TWRP, followed by the magisk zip
http://nchancellor.net/downloads/kernels/taimen/8.1.0/stable/
Click to expand...
Click to collapse

Thanks all! All sorted! Now, to Xposed or not to Xposed. That's the question. Seems to be tripping safetynet but that's another quandary

rendez2k said:
Thanks all! All sorted! Now, to Xposed or not to Xposed. That's the question. Seems to be tripping safetynet but that's another quandary
Click to expand...
Click to collapse
There is no solution for that. Xposed always fails SafetyNet.

Is Xposed worth having these days? Are people still actively developing useful mods?

rendez2k said:
Is Xposed worth having these days? Are people still actively developing useful mods?
Click to expand...
Click to collapse
I think it's worth it, for the following apps:

I've had so many problems with TWRP on this phone that I don't even flash it anymore. If I need to flash a zip file I just fastboot into TWRP and flash it that way. Kind of a pain in the ass but I don't flash many zip files anyway.

Fuse8499 said:
I've had so many problems with TWRP on this phone that I don't even flash it anymore. If I need to flash a zip file I just fastboot into TWRP and flash it that way. Kind of a pain in the ass but I don't flash many zip files anyway.
Click to expand...
Click to collapse
No problems with TWRP here. Maybe you are flashing to the wrong slot.

rendez2k said:
Is Xposed worth having these days? Are people still actively developing useful mods?
Click to expand...
Click to collapse
I keep hoping Xposed will go die in a fire. It causes more problems than it solves, to the point ROM developers will tell you not to bother reporting issues with it installed. Rovo knows his stuff, but his creation has caused more damage to custom ROM development than Cyanogenmod did in its last three years.

December update breaks magisk?

Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.

Works fine for me.

Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions

Working fine for me as well.

I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app

You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.

mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?

RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.

RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.

sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!

RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.

RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1

Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img

RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1

sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.

Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.

RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".

bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.

bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018

I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse

Bootloop back to twrp

Yesterday i sideloaded the December ota, today i decided im going to unlock the bootloader, root and install a custom kernel. I followed the instructions in the pined post in guides and well, now my pixel wont boot and its booting back to trwp.
What i did was boot twrp.img thru fastboot.
Once twrp booted i flashed the twrp zip, kernel and magisk beta zip.
How do i get out of this bootloop now?

welp, just tried to flash the factory image and got this:
error: failed to load 'image-crosshatch-pq1a.181205.006.zip': Not enough space

mac208x said:
Yesterday i sideloaded the December ota, today i decided im going to unlock the bootloader, root and install a custom kernel. I followed the instructions in the pined post in guides and well, now my pixel wont boot and its booting back to trwp.
What i did was boot twrp.img thru fastboot.
Once twrp booted i flashed the twrp zip, kernel and magisk beta zip.
How do i get out of this bootloop now?
Click to expand...
Click to collapse
fastboot flash boot --slot all boot.img
#6 in this guide.

Homeboy76 said:
fastboot flash boot --slot all boot.img
#6 in this guide.
Click to expand...
Click to collapse
Thank you! So would you know what i did wrong? Or what do i now to get root and custom kernel?

mac208x said:
Thank you! So would you know what i did wrong? Or what do i now to get root and custom kernel?
Click to expand...
Click to collapse
Pixel 3/Pixel 3 XL
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- add more zips
- Edit: Kernel of your choice
- Add more zips
- magisk-17.3.zip
- reboot system

Homeboy76 said:
Pixel 3/Pixel 3 XL
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- add more zips
- ElementalX 1.02.zip
- Add more zips
- magisk-17.3.zip
- reboot system
Click to expand...
Click to collapse
Did exactly that but instead of ElementalX kernel im trying to use Kirisakura now back to bootloop into recovery

mac208x said:
Did exactly that but instead of ElementalX kernel im trying to use Kirisakura now back to bootloop into recovery
Click to expand...
Click to collapse
After installing the TWRP.zip change slots in TWRP, reboot recovery and flash Magisk to the other slot, change slots back, then reboot.

airmaxx23 said:
Change slots in TWRP, reboot recovery and flash Magisk to the other slot, change slots back, then reboot.
Click to expand...
Click to collapse
Im so sorry but what do you mean by slot?

mac208x said:
Im so sorry but what do you mean by slot?
Click to expand...
Click to collapse
When you're in TWRP go to reboot, then switch from your current slot to the other.

airmaxx23 said:
When you're in TWRP go to reboot, then switch from your current slot to the other.
Click to expand...
Click to collapse
Alright this is becoming silly. Did exactly as you said and again, bootloop back too twrp....Should i use the twrp from dees_troy or it doesnt matter? I dont know what it can be
Edit: Nvm im using the right twrp

mac208x said:
Alright this is becoming silly. Did exactly as you said and again, bootloop back too twrp....Should i use the twrp from dees_troy or it doesnt matter? I dont know what it can be
Edit: Nvm im using the right twrp
Click to expand...
Click to collapse
Are you flashing Magisk in both slots?

airmaxx23 said:
Are you flashing Magisk in both slots?
Click to expand...
Click to collapse
No didn't do that.
Okay so fastboot boot twrp.img
Once it boots flash the twrp.zip and magisk
Change to slot b
Flash magisk
Reboot.
Right? What about kernel?

mac208x said:
No didn't do that.
Okay so fastboot boot twrp.img
Once it boots flash the twrp.zip and magisk
Change to slot b
Flash magisk
Reboot.
Right? What about kernel?
Click to expand...
Click to collapse
Try just that first and see if you can fully boot the phone.

airmaxx23 said:
Try just that first and see if you can fully boot the phone.
Click to expand...
Click to collapse
No bootloop back to trwp. Now its stuck on the white google logo screen wont go pass it

airmaxx23 said:
When you're in TWRP go to reboot, then switch from your current slot to the other.
Click to expand...
Click to collapse
Be careful with that. I did it bricked the device. It was like there was no system on that slot. I thought it was hard bricked but someone else did the same thing and eventually got it to boot.
Sent from my [device_name] using XDA-Developers Legacy app

I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.

jd1639 said:
Be careful with that. I did it bricked the device. It was like there was no system on that slot. I thought it was hard bricked but someone else did the same thing and eventually got it to boot.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've been doing it all along whenever I flash anything.
mac208x said:
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
Click to expand...
Click to collapse
You'll have to flash back to stock in fastboot.

mac208x said:
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
Click to expand...
Click to collapse
First, have you updated your sdk platform tools with the latest fastboot and adb? That's been causing a lot of people problems if they haven't updated them. If you have I would flash the stock boot image to boot slots.
fastboot flash boot_a boot.img. and
fastboot flash boot_b boot.img
If that's not enough then flash the system's image to boot slots.
Sent from my [device_name] using XDA-Developers Legacy app

airmaxx23 said:
I've been doing it all along whenever I flash anything.
You'll have to flash back to stock in fastboot.
Click to expand...
Click to collapse
jd1639 said:
First, have you updated your sdk platform tools with the latest fastboot and adb? That's been causing a lot of people problems if they haven't updated them. If you have I would flash the stock boot image to boot slots.
fastboot flash boot_a boot.img. and
fastboot flash boot_b boot.img
If that's not enough then flash the system's image to boot slots.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
How do i do this now? Flashing boot.img does nothing, phone still wont boot and hands on the boot logo. I cant enter recovery and apply from adb, nor flashing the factory image thru fastboot work, it keeps saying there isnt enough space for the .zip

mac208x said:
How do i do this now? Flashing boot.img does nothing, phone still wont boot and hands on the boot logo. I cant enter recovery and apply from adb, nor flashing the factory image thru fastboot work, it keeps saying there isnt enough space for the .zip
Click to expand...
Click to collapse
Do you have the latest sdk platform tools. If not Google that, download the zip and extract it. Replace what you do have. I create a folder c:adb and put everything in that. Then set an environment variable path in Windows so fastboot and adb are available no matter what folder I'm working in.
Sent from my [device_name] using XDA-Developers Legacy app