Related
So after having my phone being stuck in a boot loop (just restarted one day and has been in a boot loop since) , I figured the thing to do was to flash TWRP 2.8.7.0 (I had a solution that had rooted my phone without a custom recovery). After a successful flash, I go to recovery (up volume + Power) and it says recovery on the Samsung screen.
And then, it goes back into the boot loop.
Suggests as usual flashed wrong file for model .
See multiple identical posts .
But if it was a prexisting boot loop then go back to your other posts .
Sent from my SM-N930F using XDA-Developers Legacy app
JJEgan said:
Suggests as usual flashed wrong file for model .
See multiple identical posts .
But if it was a prexisting boot loop then go back to your other posts .
Sent from my SM-N930F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Flashed twrp-2.6.3.1-hltetmo.tar successfully.
While its connected into my PC, it gets stuck at the T-mobile sign at full brightness.
When I unplug it, it goes back to a boot loop.
You want the TMobile forum not this one .
Sent from my SM-N930F using XDA-Developers Legacy app
Confirm the model # in download mode before flashing anything else.
Has there been solution for this one? I got n9005 and i can't get other than twrp 2.8.7.0 working, have tried different bootloaders but without luck. Only stock images what works are N9005XXUGNG1_N9005NEEGNG1_NEE(cant update to lollipop, stucks on bootloop) and N9005XXUGBOK6_N9005XEOGBOJ1_XEO. Also had luck with some unofficial cm13 rom.
I'am not that familiar with this samsung style of using odin instead of fastboot and adb so i'am litlle bit lost and just don't know what else anymore can i do to get working new twrp so i can install nougat.
What rom are you going to install.
Sent from my SM-N930F using XDA-Developers Legacy app
i tried official lineageos 14 hlte, it looks like installation goes fine with twrp 2.8.7.0 but phone wont boot. currently i have nordic bootloader and modem BL_N9005XXSGBQD1 and CP_N9005XXUGPQB1 and twrp 2.8.7.0 just tried to upgrade newer twrp from image file but same old bootloop again.
Could there be something wrong in filesystem? Is there some pit-file that i can try with my phone without risk of bricking it?
---------- Post added at 22:22 ---------- Previous post was at 22:06 ----------
btw, where does that charging icon come when phone is power off? my phone is just boot looping when powered off and i put charger on it.
Bootloop thats often wrong TWRP used .
Flash latest TWRP through TWRP or try Philz Recovery .
tried to install 3.1.1.0 from twrp 2.8.7.0. Install went fine without any errors but still not booting to recovery. found philz 6.13.0 after browsing, it also boots to recovery, installing lineageos went to boot loop just as it has done before.
I would start at step one.
Boot to download mode .
Note model and flash stock rom via Odin.
Sent from my SM-N930F using XDA-Developers Legacy app
i have tried both stock 4.4 and 5.0 roms, both boot and works fine but i still can't make twrp higher than 2.8.7.0 to work.
Okay. Now i have restored stock N9005XXUGBNL8, root and installed twrp app and used it to flash twrp 3.1.1.0 Flashing went fine as usually, phone boots as normally but still when i try to boot recovery phone reboots after 10-15sec. Also did try to flash multiple versions of twrp and no newer than 2.8.7.0 works.
Try one of the custom non ASOP roms see if that boots .
Sent from my SM-N930F using XDA-Developers Legacy app
Anyone found a solution?
I have the same problem,twrp above 2.8.7.0 dont work(bootloops) and new 7.1.2 roms do the same thing.
I manage to install an old 7.1.1 cyanogen 14 rom from 2016 december 10 minutes ago and it's working for now.
Next thing i tried to update the rom to a new build from january 2017 but i got bootloops...it's very strage.
Managed to install crdroid 7.1.2 from twrp 2.8.7.0, aokp unofficial also worked but still no luck with lineageos and newer twrp.
@stepi1 - Did you manage to find a solution to this problem? You are certainly not alone. I have exactly the same problem, and so do others! Nothing newer than TWRP 2.8.7 works on my N9005. Read the last few pages of this thread and you will see that I have the exact same issue. Seems there is either a bug or something different in the device tree for TWRP versions 3 and above which is not allowing the phones to boot these newer versions - https://forum.xda-developers.com/galaxy-note-3/development/recovery-twrp-3-2-1-1-t3746760
Chris
Sorry but no, i didn't find any solution used old twrp and crdroid for a while before giving up with that phone.
stepi1 said:
Sorry but no, i didn't find any solution used old twrp and crdroid for a while before giving up with that phone.
Click to expand...
Click to collapse
Thanks for confirming that.
Chris
fanilas said:
Anyone found a solution?
I have the same problem,twrp above 2.8.7.0 dont work(bootloops) and new 7.1.2 roms do the same thing.
I manage to install an old 7.1.1 cyanogen 14 rom from 2016 december 10 minutes ago and it's working for now.
Next thing i tried to update the rom to a new build from january 2017 but i got bootloops...it's very strage.
Click to expand...
Click to collapse
This is a known problem with some hlte devices, including mine. It has something to do with the way the newer TWRP versions (>v3) are built. There are devs working on it, but as of yet, the problem has not yet been resolved.
Chris
Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!
What version of TWRP did you flash first?
I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.
Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.
I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.
Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.
Well, it's not so bad.
Yesterday I bought this phone and applied the October update. Then I flashed TWRP by @mohancm (I wasn't sure about that but I did it anyway). And then I flashed Magisk. But because I couldn't get Xposed to work, I tried to remove Magisk (unsuccessfully it seems) and flash SuperSU. I played around by switching from slot B to A. I am not sure exactly what I did.
The end result is that the phone won't boot when I turn it on. (I think I might still have TWRP installed, but I am not sure.) I tried flashing stock boot.img via fastboot, but I get get an error (I think it's something to do with the partition table). I can't flash using MiFlash because it says I don't have the permission. (I've had bad experiences with MiFlash before.)
However, I am able to boot the phone manually. When I boot to bootloader I can just boot stock boot.img (flashing doesn't work like I said), and then the system boots properly and I'm rooted.
Any ideas what I can do now to fix the issue. I just need to try to avoid random reboots and I can use my phone just fine, but is there a way to fix it? Should I just wait for the November update? Any hope of getting a ROM that I can flash using TWRP?
Edit: I'm dumb. Of course you can flash an image via TWRP. I flashed the stock image via TWRP and now the phone boots properly. Problem solved.
Hello to everybody, the wifi phone of my OP5 woked very well. One day I flashed one ROM, I dont remember what and broked the wifi, now show the typical broken mac address, I saw all the post even fixing nexus wifi phone but didnt work. I lnow that I need to upgrade to Oreo, now Im in Nougat, but the problem is when I flash the oreo stock rom the phone get a bootloop, I tryied everything so I need to forget upgrade. How can resolve this problem. I updated no stock ROM oreo like aiscp but the wifi not repair. I dont know what do. I tried with QPST QXSM but nothing I can repair my phone. Any help?. I tried too modificating all the files about wifi, wifi.bin (I dont remember the names) and didnt worked
If you are using TWRP make sure to update to latest codeworks version and in the wipe section select format data. This is necessary when moving from Nougat to Oreo on the OP5 if you are using a custom recovery. That will erase everything on your phone except TWRP. Plug your phone into a computer and it will show up like a USB drive. Copy and paste the Oreo ROM zip for stock OOS onto your phone. If you want to be rooted also copy the latest Magisk zip. Flash OOS zip within TWRP. If you boot into the system after that you will be 100% stock including recovery. If you want to be rooted and keep TWRP flash Magisk zip as well before booting into system. Given your circumstance I would highly recommend going 100% stock and making sure everything is working right again. You can always install TWRP and root again later.
i remember how i flashed blu spark kernel for custom rom, when i was at stock oos and get this broken wifi. try to look at that
jhs39 said:
If you are using TWRP make sure to update to latest codeworks version and in the wipe section select format data. This is necessary when moving from Nougat to Oreo on the OP5 if you are using a custom recovery. That will erase everything on your phone except TWRP. Plug your phone into a computer and it will show up like a USB drive. Copy and paste the Oreo ROM zip for stock OOS onto your phone. If you want to be rooted also copy the latest Magisk zip. Flash OOS zip within TWRP. If you boot into the system after that you will be 100% stock including recovery. If you want to be rooted and keep TWRP flash Magisk zip as well before booting into system. Given your circumstance I would highly recommend going 100% stock and making sure everything is working right again. You can always install TWRP and root again later.
Click to expand...
Click to collapse
I did it but didnt work
Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!
starcms said:
Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!
Click to expand...
Click to collapse
It's definitely possible but I don't know how many Devs would want to take this up. I'm all for the idea, I really miss having TWRP permanently, but you kinda get used to the whole PC flashing thang.
I don't know how different the Pixel 2 is in comparison to the Essential phone, but they both share A/B partitions, so it wouldn't be too outlandish if someone were able to port something like this over to our Mata's down the road.
?
starcms said:
Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!
Click to expand...
Click to collapse
MoistPicklez said:
It's definitely possible but I don't know how many Devs would want to take this up. I'm all for the idea, I really miss having TWRP permanently, but you kinda get used to the whole PC flashing thang.
I don't know how different the Pixel 2 is in comparison to the Essential phone, but they both share A/B partitions, so it wouldn't be too outlandish if someone were able to port something like this over to our Mata's down the road.
?
Click to expand...
Click to collapse
The problem lies in the way our touch driver is implemented. For lack of a better explanation, what good would it do to need to carry a type c mouse around to use twrp if touch doesn't work. Many many people have tried and failed getting touch to work on Oreo source, let alone P. That is why twrp resides on a nougat kernel meant for LOS. Someone I know even rewrote the driver in c, no go. It's gonna be tough sledding.
Does it have to be touch though? Could it be more old school clockworkmod recovery where you use the buttons or really like default recovery. I don't know enough about it but just a thought. You definitely get use to just downloading and flashing in twrp and it would be cool to find that with the PH-1.
Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.
Gundabolu SC said:
Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.
Click to expand...
Click to collapse
Been waiting for someone to share this for 6 months.. thanks lol
aer0zer0 said:
The problem lies in the way our touch driver is implemented. For lack of a better explanation, what good would it do to need to carry a type c mouse around to use twrp if touch doesn't work. Many many people have tried and failed getting touch to work on Oreo source, let alone P. That is why twrp resides on a nougat kernel meant for LOS. Someone I know even rewrote the driver in c, no go. It's gonna be tough sledding.
Click to expand...
Click to collapse
Thanks for the explanation. Now I understand why it hasn't been done before.
But why the issue with touch in TWRP with an Oreo kernel in the first place? What's so special/different/difficult about the touch driver that the Essential uses? And why does it work fine with TWRP with a Nougat kernel? No other devices (to my knowledge) have this issue.
Edit: I wonder if since TWRP worked with the touch driver from the Nougat kernel, if it could work with the P kernel? Maybe whatever was changed in Oreo that prevented it from working has been fixed?
starcms said:
Thanks for the explanation. Now I understand why it hasn't been done before.
But why the issue with touch in TWRP with an Oreo kernel in the first place? What's so special/different/difficult about the touch driver that the Essential uses? And why does it work fine with TWRP with a Nougat kernel? No other devices (to my knowledge) have this issue.
Click to expand...
Click to collapse
Hbtp_daemon (touchscreen) doesn't work in twrp on 8.x and newer sources.
Hbtp_daemon runs in userspace iirc, which is the problem. So an entire driver needs to be hogged together in order to get twrp to work. same process that worked on N doesn't work now.
aer0zer0 said:
Hbtp_daemon (touchscreen) doesn't work in twrp on 8.x and newer sources.
Hbtp_daemon runs in userspace iirc, which is the problem. So an entire driver needs to be hogged together in order to get twrp to work. same process that worked on N doesn't work now.
Click to expand...
Click to collapse
Not possible to use the driver in userspace after TWRP decrypts the device (userspace) using the default password (after any patterns or pins are removed from the lockscreen)?
Edit: And what the heck is the driver doing in userspace anyway? Shouldn't it be in /vendor? If the driver is in userspace, then how can the touchscreen work after a factory reset?
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
It doesn't after you lets say flash magisk and gapps they create a script in /system/addon....and when updatting lineage it runs the scripts in the addon folder which is how gapps and magisk get installed to the new updated system and boot.....first magisk and gapps have to be flashed in twrp....after that u shudnt need it on dirty flashes
galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
@aer0zer0
This seems like the easiest solution to getting TWRP working on the Oreo and P boot images and being able to keep it permanently installed in ramdisk. Make TWRP use the volume up/down keys for scrolling and the power key to select. If the touchscreen is soooo difficult to get working, forget it. If someone really wants to use the touchscreen, they can use the existing TWRP version built on the Nougat boot image.
galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
What can you do in Lineage recovery if you can't flash zips? Can you make backups? What else can you do? If you have it installed, could you attach a pic (assuming you have another phone/camera)?
Has anyone looked in the stock P kernel? I was poking around and noticed some twrp residual files. This was straight from the images zip from essential. I didn't touch it.Wth are they in there for? Could they have a better twrp on the back burner for kernel development purposes for Essential? It was in the ramdisk, ill look again tomorrow when I unpack the boot.img. it would make sense to have it in ramdisk, pixel 2 has it like that. Ill post screenshots after work. But, the conversation looks good folks, you are on to something. We could always bust out some phillz recovery, or clockwork mod.
starcms said:
What can you do in Lineage recovery if you can't flash zips? Can you make backups? What else can you do? If you have it installed, could you attach a pic (assuming you have another phone/camera)?
Click to expand...
Click to collapse
I would say it is more stock-ish as far as recoverys go. It's a stock LOS recovery. You can factory reset, flash or sideload update.zips or signed zips no regular custom ROM zips or magisk. It is meant to run on LOS, it only runs on LOS actually and not made for the flashaholics out there. It's a good start though.
Sorry, out right now and no other phone/camera handy.
Gundabolu SC said:
Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.
Click to expand...
Click to collapse
Just wanted to mention this works perfectly, tried it last night was able to get into TWRP and then back into my P Beta 3 with root, no issues. Thanks for this!
One could also theoretically copy a copy of the twrp boot. Img to the ex kernel manager backup file, and while booted into the system, hit restore kernel and since its in the boot partition it will flash it then reboot into recovery. Then from there flash your normal kernel and boot back to system/android.. i backup all my kernels after rooting them so after flashing otas, i can just flash my prerooted kernel and reboot without having to flash magisk
Edit. This works, i just did it, but u must make it reboot to bootloader to then tell it to reboot recovery. I dont know if flashify is the same
MoistPicklez said:
Just wanted to mention this works perfectly, tried it last night was able to get into TWRP and then back into my P Beta 3 with root, no issues. Thanks for this!
Click to expand...
Click to collapse
Hey, I'm just curious, before I try it, anyway when using flashify and selecting flash zip - does a recovery other than stock need to be present?
dirtyreturn said:
Hey, I'm just curious, before I try it, anyway when using flashify and selecting flash zip - does a recovery other than stock need to be present?
Click to expand...
Click to collapse
Not sure what you mean by that but to be honest all I did was take the TWRP11.img, and flashed it to boot (kernel) using Rashr, Flashify didn't load up oddly, then reboot to bootloader, select Recovery and bam, there was TWRP. Then to get back I just flashed my boot.img, and Magisk and all my modules and everything were all good to go. No issues at all. ?
Edit: as long as you have TWRP.img, your boot.img, and Magisk, you can easily get to TWRP and back, just make sure you have the img's you need and boom we all got TWRP on the fly.
Wish I had tried this sooner.
MoistPicklez said:
Not sure what you mean by that but to be honest all I did was take the TWRP11.img, and flashed it to boot (kernel) using Rashr, Flashify didn't load up oddly, then reboot to bootloader, select Recovery and bam, there was TWRP. Then to get back I just flashed my boot.img, and Magisk and all my modules and everything were all good to go. No issues at all. ?
Edit: as long as you have TWRP.img, your boot.img, and Magisk, you can easily get to TWRP and back, just make sure you have the img's you need and boom we all got TWRP on the fly.
Wish I had tried this sooner.
Click to expand...
Click to collapse
Hey, Rashr doesn't support this device(phone). I get a reboot to recovery option and if I tap cancel the app just closes. Did the app identify what it needed to?
In Flashify there are 3 options ,Flash - kernel,boot, and zip. What I'm curious about is , when choosing just the zip option - would twrp first need to be flashed to the boot partition?