Related
EDIT: Resolved by following Naman Bhalla's Unbrick Guide.
I'm on latest Freedom OS community build right now. I have this problem where my OP3 won't boot into recovery at all. Trying to do it just kills it and only a very long power button press is able to revive it.
I have tried flashing the recovery via fastboot but that also doesn't work. Is there a way out of it? I can't flash zips. Are there factory images I can flash via fastboot that can replace everything? I don't care about the data. Any help would be appreciated.
flash modified recovery via fastboot
Sent from my ONEPLUS A3003 using Tapatalk
I have tried Garak's TWRP and the other TWRP. It doesn't change anything. Are there factory images like Google provides which can be flashed using fastboot?
i have the same problem, flashed the previouse version of Oxygen OS. But now i can't get in to recovery.. when i flash it trough fastboot everything goes ok, but when i want to go into recovery the screen is blank and the device does nothing.
Maybe read the OP of FreedomOS rom.
NevaX1 said:
Maybe read the OP of FreedomOS rom.
Click to expand...
Click to collapse
I have read the OP of Freedom OS. I understand that obviously I overlooked something because of which I ended up where I am but I am looking for solutions here. I did not dirty flash the community build if that's what you mean.
n33raj18 said:
I have read the OP of Freedom OS. I understand that obviously I overlooked something because of which I ended up where I am but I am looking for solutions here. I did not dirty flash the community build if that's what you mean.
Click to expand...
Click to collapse
You need the modified twrp version, the only way to recognize it, it has a mouse cursor in the middle of your screen.
n33raj18 said:
I'm on latest Freedom OS community build right now. I have this problem where my OP3 won't boot into recovery at all. Trying to do it just kills it and only a very long power button press is able to revive it.
I have tried flashing the recovery via fastboot but that also doesn't work. Is there a way out of it? I can't flash zips. Are there factory images I can flash via fastboot that can replace everything? I don't care about the data. Any help would be appreciated.
Click to expand...
Click to collapse
I tried that I got the same error and wipe everything even internal then got a thread in unbrick oneplus 3 and it worked try method 2 link (http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700)
NevaX1 said:
You need the modified twrp version, the only way to recognize it, it has a mouse cursor in the middle of your screen.
Click to expand...
Click to collapse
I had the same problem with 'no recovery' and this helped!
Thanks!
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
vvverma said:
I tried that I got the same error and wipe everything even internal then got a thread in unbrick oneplus 3 and it worked try method 2 link (http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700)
Click to expand...
Click to collapse
Yea, I used exactly the same thing to get back my device working correctly again. I missed the crucial information that modified TWRP was required.
Hi all,
*I've unlocked bootloader
* Have tried fastboot boot TWRP.img, as well as tried flashing TWRP RC1 via the Skipsoft toolkit.
Every way I've tried the phone just sits at the TWRP boot screen and doesn't allow me to go any further..
Any help here would be truly appreciated!
Cheers,
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
You're braver than me. I haven't had my Pixel XL long but this is the first phone I've ever owned where I am afraid to try and install a custom recovery and ROM. With the dual partitions and what I hear about TWRP still being buggy it just seems like Google didn't want people to run anything but pure Android on the Pixels.
dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
mikefnz said:
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
Click to expand...
Click to collapse
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
mac796 said:
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
Click to expand...
Click to collapse
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
XtraArrow said:
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
Click to expand...
Click to collapse
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
mazubo said:
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
Click to expand...
Click to collapse
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
XtraArrow said:
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
Click to expand...
Click to collapse
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1 zip
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
mazubo said:
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
Click to expand...
Click to collapse
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
mac796 said:
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
Click to expand...
Click to collapse
Hmm, maybe this is where I've gone wrong.. I thought the need to create a security pin/pattern was only if coming from a previously rooted state, or from a custom ROM. I will try this as well and report back.. thanks!
XtraArrow said:
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
Click to expand...
Click to collapse
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
mazubo said:
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
Click to expand...
Click to collapse
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
XtraArrow said:
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
Click to expand...
Click to collapse
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
mazubo said:
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
Click to expand...
Click to collapse
I'm no expert but it's seems like a decent suggestion. Let us know how it goes.
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Just wait. It will take little longer
Sent from my Pixel XL using Tapatalk
freddy0872 said:
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Click to expand...
Click to collapse
Yes, I have tried fastboot to flash the TWRP img, as well as skipsofts toolkit. I guess I've been using the term "flash" for fastboot, as I haven't been able to use twrp yet.. I understand that you need to flash the TWRP img via pc and then flash the TWRP zip, then SuperSU or magisk, whatever your poison may be !
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
I have the same problem, it comes back to recovery all the time and we can tell you about it, some help please
---------- Post added at 09:59 PM ---------- Previous post was at 09:43 PM ----------
Hi, I've come back, hahaha, I installed resurrection remix 7.1, previous all the wipes and reboot in bootloader I gave start and started, great.
I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings
CypherPotato said:
I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings
Click to expand...
Click to collapse
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.
SuperUtilisateur said:
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.
Click to expand...
Click to collapse
Have you tried to boot from Fastboot?
Yes, it works once...
But if I have to restart it (or turn off and start with the power button), the phone boot always in recovery.
It is then necessary to restart fastboot then press "start".
Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
Try do a full reset through fastboot and then try installing whatever you need through fastboot and recovery. Much more reliable han ota installs/updates
Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings
grosobart said:
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings
Click to expand...
Click to collapse
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
It always says that
As long as it says at the end
Write OK
It flashed successfully
OK,
After flash,
boots automatically into recovery ...
--
I tried with various boot.img. (linéage, AOSP, OctOS, ... )
Does not work ..
I started (into fastboot), I was errors. (Process stopped)
I just restored my phone ( https://mirrors.lolinet.com/firmware/moto/cedric/official/RETAIL/ )
... boot correctly.
Never mind ...
thank you all
SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5/how-to/fyi-recovered-g5-xt-1676-to-stock-t3626088
try this first, regards
SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect
Moto G5 boots to TWRP
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Backing up Gigs of data is a huge pain. Even if I have to copy to my pc. So, just something that's less cumbersome.
Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Read the faq section (2nd post) - answer is there
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
grosobart said:
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect
Click to expand...
Click to collapse
Anyone get the stock for 16gb/2gb version?
First off I am a seasoned novice in the android flashing/ rooting scene, not know but asking for help by swallowing my pride. I've had the device for two days now and I enjoy the device but would love to try these custom ROMs out. I have installed TWRP multiple times and the TWRP A/B partition flasher, installed Magisk and had a working stock rooted with Elemental X running. No matter how many times I flash a ROM it never seems to boot past the custom ROM's boot sequence, I even tried the manual reboot fix and no dice.
I ask for help for myself and future noobs to this A/B partitioned device.
Thanks in advance
this will help you mate
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
kismetmookz said:
this will help you mate
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Thanks, I have been using this and used it as I was wring the article, I'm just trying to see how we flash the ROMs on this puppy.
i use to do these steps
wipe caches
install rom
install twrp.zip for taimen
reboot
setup phone
if you want root then reboot on recovery again then install magisk.
I do these steps and have no failure when flashing; after I wipe the Caches, I flash the ROM and then the TWRP partition flasher and reboot the system. I've waited 15 minutes to have the device boot with no luck and I don't want to risk any longer due to the Pixel 2/ XL having burn-in issues.
thowersome said:
First off I am a seasoned novice in the android flashing/ rooting scene, not know but asking for help by swallowing my pride. I've had the device for two days now and I enjoy the device but would love to try these custom ROMs out. I have installed TWRP multiple times and the TWRP A/B partition flasher, installed Magisk and had a working stock rooted with Elemental X running. No matter how many times I flash a ROM it never seems to boot past the custom ROM's boot sequence, I even tried the manual reboot fix and no dice.
I ask for help for myself and future noobs to this A/B partitioned device.
Thanks in advance
Click to expand...
Click to collapse
Probably because there's not a full OS on the slot your flashing to. If you know your fastboot, it's relatively easy going forward. The Dueces scrip it's great tool for sure to help out. If you want to do it manually, fastboot the factory image to both slots with the -w removed from the flash-all.bat file.
Once that's done, go back to fastboot, and boot into twrp. Then do a twrp factory reset with the swipe bar. Flash the rom, then the twrp.zip and let it boot up. Once in the OS, keep lock screen set to swipe, and do a minimal setup. Then go back to twrp and flash your custom kernel(optional) then flash magisk. And that should do it :good:
Will try this out right now, just restored stock, unlocked, rooted and TWRPed it. Will reply with results.
thowersome said:
Will try this out right now, just restored stock, unlocked, rooted and TWRPed it. Will reply with results.
Click to expand...
Click to collapse
If your on the stock April release, you might want to wait until the Devs have updated their roms to be compatible with the current stock release :good:
Btw...what is a twrp partition flasher????
Badger50 said:
If your on the stock April release, you might want to wait until the Devs have updated their roms to be compatible with the current stock release :good:
Btw...what is a twrp partition flasher????
Click to expand...
Click to collapse
The zip that flashes TWRP on both the A and B partition, available at the TWRP website
thowersome said:
The zip that flashes TWRP on both the A and B partition, available at the TWRP website
Click to expand...
Click to collapse
Hahahahahaha...that's pretty good bruh! I've just never heard it called that before. Carry on my friend! ??
Badger50 said:
Hahahahahaha...that's pretty good bruh! I've just never heard it called that before. Carry on my friend!
Click to expand...
Click to collapse
Hey thanks a lot, I got it to boot into AquariOS with no issues, saw that I kept downloading the latest OFW (ie April) on accident.
thowersome said:
Hey thanks a lot, I got it to boot into AquariOS with no issues, saw that I kept downloading the latest OFW (ie April) on accident.
Click to expand...
Click to collapse
Outstanding! Well done :good::good:
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.