Database Develop

[Q] no ADB/usb-otg with TWRP 2.6.3

I used to run TWRP 2.5.0.0 without any problems, since the OTA 4.3 update the touchscreen in TWRP 2.5.0.0 no longer works. for some reason TWRP 2.5.0.0 is the only recovery that would work with usb-otg and ADB, does anyone know how to either wipe and install a new rom only using ADB commnds in twrp, or how to get my USB-OTG and ADB working in TWRP 2.6.3? the phone currently is listed as M7WLS in the device manager while in any recovery besides TWRP 2.5.0.0

did you try adb sideload (nameofrom).zip ? using sideload in twrp.
i cant seem to get my OTG USB to work at all. it will not mount the usb no matter what i do.

only twrp 2.5.0.0 works with adb or usb otg
rchris494 said:
did you try adb sideload (nameofrom).zip ? using sideload in twrp.
i cant seem to get my OTG USB to work at all. it will not mount the usb no matter what i do.
Click to expand...
Click to collapse
sideload does not work since the phone is improperly recognized as m7wls in device manager on any recovery besides twrp 2.5.0.0

I had the same issue with twrp & otg on 4.3. I updated to twrp 2.6.3.0 & still had issues sideloading after a complete wipe in twrp. I just read that flashing philztouch from bootloader helped someone to sideload a rom. I haven't tried it yet-so fill us in if you have any luck with philztouch. I love twrp, but i'll use anything that works. We are all learning, so ur best bet is to always take the time to backup before u try anything.
Sent from my HTCONE using Tapatalk 4

tonyrance said:
I had the same issue with twrp & otg on 4.3. I updated to twrp 2.6.3.0 & still had issues sideloading after a complete wipe in twrp. I just read that flashing philztouch from bootloader helped someone to sideload a rom. I haven't tried it yet-so fill us in if you have any luck with philztouch. I love twrp, but i'll use anything that works. We are all learning, so ur best bet is to always take the time to backup before u try anything.
Sent from my HTCONE using Tapatalk 4
Click to expand...
Click to collapse
DNasingh has a 1.29 touch panel thread with a flashable zip in the general section. Flash the zip in your bootloader, then flash twrp 2.5.0.0.
Hope that helps
Sent from my HTCONE using XDA Premium 4 mobile app
---------- Post added at 09:32 PM ---------- Previous post was at 09:24 PM ----------
thanosart said:
DNasingh has a 1.29 touch panel thread with a flashable zip in the general section. Flash the zip in your bootloader, then flash twrp 2.5.0.0.
I use otg cable a lot and this worked to get back to twrp 2.5.0.0
Hope that helps
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my HTCONE using XDA Premium 4 mobile app
---------- Post added at 09:34 PM ---------- Previous post was at 09:32 PM ----------
thanosart said:
DNasingh has a 1.29 touch panel thread with a flashable zip in the general section. Flash the zip in your bootloader, then flash twrp 2.5.0.0.
Hope that helps
I use my otg cable a lot and this solved that issue.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse

thanosart said:
DNasingh has a 1.29 touch panel thread with a flashable zip in the general section. Flash the zip in your bootloader, then flash twrp 2.5.0.0.
Hope that helps
Sent from my HTCONE using XDA Premium 4 mobile app
---------- Post added at 09:32 PM ---------- Previous post was at 09:24 PM ----------
Sent from my HTCONE using XDA Premium 4 mobile app
---------- Post added at 09:34 PM ---------- Previous post was at 09:32 PM ----------
thanosart said:
DNasingh has a 1.29 touch panel thread with a flashable zip in the general section. Flash the zip in your bootloader, then flash twrp 2.5.0.0.
Hope that helps
I use my otg cable a lot and this solved that issue.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Do u mind sharing that link please? I'd like to check it out. Does the touch screen still work?
Sent from my HTCONE using Tapatalk 4
Click to expand...
Click to collapse

Touch screen in twrp 2.5.0.0 will work. Can't post a link right now but the thread is in the general section. Look for 1.29 touch panel firmware
Sent from my HTCONE using XDA Premium 4 mobile app

TravisAnthony07 said:
I used to run TWRP 2.5.0.0 without any problems, since the OTA 4.3 update the touchscreen in TWRP 2.5.0.0 no longer works. for some reason TWRP 2.5.0.0 is the only recovery that would work with usb-otg and ADB, does anyone know how to either wipe and install a new rom only using ADB commnds in twrp, or how to get my USB-OTG and ADB working in TWRP 2.6.3? the phone currently is listed as M7WLS in the device manager while in any recovery besides TWRP 2.5.0.0
Click to expand...
Click to collapse
Same problem to me. Solution= Install CWM recovery 6.0.3.1 Touch. work perfect!!!

TWRP 2.5.0.0 the only working recovery with usb otg/adb sideload
still no good, i have tried all versions of CWM including philZ and TWRP but TWRP 2.5.0.0 is the only recovery that will let me use usb-otg or adb sideload (would love to fix this if anyone knows how) and i am unable to set S-off because i can not push revone, for some reason my phone says adb device offline even with debugging enabled

TravisAnthony07 said:
sideload does not work since the phone is improperly recognized as m7wls in device manager on any recovery besides twrp 2.5.0.0
Click to expand...
Click to collapse
You have to update the driver when in recovery.. or else it will show up m7wls
Sent from my HTCONE using Tapatalk 2

TravisAnthony07 said:
still no good, i have tried all versions of CWM including philZ and TWRP but TWRP 2.5.0.0 is the only recovery that will let me use usb-otg or adb sideload (would love to fix this if anyone knows how) and i am unable to set S-off because i can not push revone, for some reason my phone says adb device offline even with debugging enabled
Click to expand...
Click to collapse
usb-otg work on CWM 6.0.4.3 but you not gonna see a usb-otg. Just plug-in the usb-otg and automatic mount /storage/usbdisk
im sorry!! i said CWM 6.0.3.1 in my last post. I mean CWM 6.0.4.3 I www.clockworkmod.com/rommanager. look for htc one (sprint) and flash the IMG.

new CWM works
Pacemaker2 said:
usb-otg work on CWM 6.0.4.3 but you not gonna see a usb-otg. Just plug-in the usb-otg and automatic mount /storage/usbdisk
im sorry!! i said CWM 6.0.3.1 in my last post. I mean CWM 6.0.4.3 I www.clockworkmod.com/rommanager. look for htc one (sprint) and flash the IMG.
Click to expand...
Click to collapse
the new CWM was able to mount my usb automatically and my problem is solved, ty. But i wonder, why is every other recovery but the newest CWM and TWRP 2.5 unable to use the usb?

Didn't find out about this issue until it was too late
I decided to back everything up onto my laptop and wipe the phone clean including the internal card and then install a new ROM from the USB-OTG
Problem is I didn't realize until I tried it that TWRP 2.6.3 won't mount or recognize USB to either install the ROM or push another recovery onto the phone
Help would be greatly appreciated.

jmp485 said:
I decided to back everything up onto my laptop and wipe the phone clean including the internal card and then install a new ROM from the USB-OTG
Problem is I didn't realize until I tried it that TWRP 2.6.3 won't mount or recognize USB to either install the ROM or push another recovery onto the phone
Help would be greatly appreciated.
Click to expand...
Click to collapse
I have done the same exact thing. Any help would be greatly appreciated as well.

Fixed mine
kpahl1973 said:
I have done the same exact thing. Any help would be greatly appreciated as well.
Click to expand...
Click to collapse
I was able to flash the CWM recovery through fastboot then install my ROM the way I wanted to originally. I'm uploading my files now

jmp485 said:
I was able to flash the CWM recovery through fastboot then install my ROM the way I wanted to originally. I'm uploading my files now
Click to expand...
Click to collapse
Just did the same thing. Rom is booting up now. Thanks for the suggestion!

cant update to TWRP 3.0.0 recovery

Hi, i tried updating my twrp recovery from 2.8.7 to 3.0.0, but when i rebooted my device, it gets stuck on the boot screen, never actually proceeding to recovery mode. All good, im still able to odin the old recovery. Anyone successfully updated to 3.0.0 ?
The way i flashed the new recovery was i selected the .img file in twrp and flashed into recovery partition.
Ive also tried flashing the .img in odin 3.0.7, but it didnt work aswell.

@ayeitschris, I have the same problem my friend. Has anyone figured a way yet?

Same issue.

Seems like other note 4 users are having the same issues as well:
http://forum.xda-developers.com/not...-utility-twrp-2-8-1-x-teamwin-t2956011/page56

yeah it will soft brick your recovery and you will have to odin 2.8.7.0 .

There's a fixed version posted in the twrp thread. I'm using 3.0 now and it's working very well

marseillesw said:
There's a fixed version posted in the twrp thread. I'm using 3.0 now and it's working very well
Click to expand...
Click to collapse
link?

marseillesw said:
There's a fixed version posted in the twrp thread. I'm using 3.0 now and it's working very well
Click to expand...
Click to collapse
Where is it?

Just flash it with the rashr app. U don't have to use odin when you have an existing recovery. Just flash over it via the app
---------- Post added at 02:56 AM ---------- Previous post was at 02:53 AM ----------
ayeitschris said:
Hi, i tried updating my twrp recovery from 2.8.7 to 3.0.0, but when i rebooted my device, it gets stuck on the boot screen, never actually proceeding to recovery mode. All good, im still able to odin the old recovery. Anyone successfully updated to 3.0.0 ?
The way i flashed the new recovery was i selected the .img file in twrp and flashed into recovery partition.
Ive also tried flashing the .img in odin 3.0.7, but it didnt work aswell.
Click to expand...
Click to collapse
I also have a T-Mobile note 4 and the recovery flashed perfectly. After you odin the first recovery you never have to use it again. Just use the rashr flashing app and you will never have one problem. The only time you will need odin is if you are going from twrp to cwm
---------- Post added at 02:57 AM ---------- Previous post was at 02:56 AM ----------
ayeitschris said:
Hi, i tried updating my twrp recovery from 2.8.7 to 3.0.0, but when i rebooted my device, it gets stuck on the boot screen, never actually proceeding to recovery mode. All good, im still able to odin the old recovery. Anyone successfully updated to 3.0.0 ?
The way i flashed the new recovery was i selected the .img file in twrp and flashed into recovery partition.
Ive also tried flashing the .img in odin 3.0.7, but it didnt work aswell.
Click to expand...
Click to collapse
Also do not flash a recovery update from your recovery

I have tried flashing it using odin, both stock and custom rom, as well as TWRP manager. 3.0.0 doesn't work. If I flash back to 2.8.7, all is fine. Apparently 3.0.0 doesn't work for the SM-N910T (T-Mobile) version. If anyone has had success with this model, please include links and detailed instructions as to how you successfully upgraded.

http://forum.xda-developers.com/showthread.php?p=65242953
---------- Post added at 09:55 PM ---------- Previous post was at 09:55 PM ----------
Hell-Razor said:
link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=65242953

TWRP Recovery 3.0.2-1 Official for OnePlus3

Hello OnePlus 3 Users
TWRP Recovery 3.0.2-1 Official for OnePlus3
https://twrp.me/devices/oneplusthree.html
Fastboot Install:
Code:
fastboot flash recovery twrp.img

Is only fastboot img or can it be flashed true twrp

I flashed from another twrp, after reboot i can not enter recovery any more.
Any ideas?
Update, fastboot flash fixed error

I think that after flashing you have to reboot recovery instead of rebooting system
---------- Post added at 07:57 PM ---------- Previous post was at 07:50 PM ----------
Just downloaded and flashed it true flashify

cabanas1 said:
I think that after flashing you have to reboot recovery instead of rebooting system
---------- Post added at 07:57 PM ---------- Previous post was at 07:50 PM ----------
Just downloaded and flashed it true flashify
Click to expand...
Click to collapse
flashed using flashify as well. no issues.

So after flashing this it wiped my data ? this is not the first time i flashed twrp on a phone is this has never happen ...

Does this mean no more having to remove finger print security before doing a backup?

ahmedradaideh said:
Hello OnePlus 3 Users
TWRP Recovery 3.0.2.0 Official for OnePlus3
https://twrp.me/devices/oneplusthree.html
Fastboot Install:
Code:
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
OMG!!! Thank you, and the devs! Finally ;D I'm so happy now :angel:

Is OTG with this twrp working?

_MartyMan_ said:
OMG!!! Thank you, and the devs! Finally ;D I'm so happy now :angel:
Click to expand...
Click to collapse
Why so happy?
What are the advantages over the unofficial TWRP recovery?

I flashed through Garak's Unofficial TWRP.
Install>IMG>[select official TWRP IMG]>[Select recovery partition]>Profit.

areon said:
Is OTG with this twrp working?
Click to expand...
Click to collapse
Did not work for me still, but the little arrow is gone

cabanas1 said:
I think that after flashing you have to reboot recovery instead of rebooting system
---------- Post added at 07:57 PM ---------- Previous post was at 07:50 PM ----------
Just downloaded and flashed it true flashify
Click to expand...
Click to collapse
hm...me, too, flashed from another TWRP and then rebooted, worked without problems...

Fir3blade said:
Why so happy?
What are the advantages over the unofficial TWRP recovery?
Click to expand...
Click to collapse
I can't tell Maybe that the official TWRP team has a OnePlus 3, or that is official.

kramer987 said:
flashed using flashify as well. no issues.
Click to expand...
Click to collapse
Did that too, but is there a way too see what version of TRWP you have?

Bradl79 said:
Did not work for me still, but the little arrow is gone
Click to expand...
Click to collapse
This is sad, hopefully they add it soon.

I flashed it,it removed encryption so I tried to re-encrypted the phone left it over night,and it didn't encrypted any ideas?

slonn said:
Does this mean no more having to remove finger print security before doing a backup?
Click to expand...
Click to collapse
Good question, anybody tried?

Hogyoku said:
So after flashing this it wiped my data ? this is not the first time i flashed twrp on a phone is this has never happen ...
Click to expand...
Click to collapse
Happened to me, too. Flashed via fastboot, forced a reboot, booted to recovery, and (I think after entering my encryption password) it wiped the /data partition. Glad I had a TWRP backup from earlier in the day. :/

slonn said:
Does this mean no more having to remove finger print security before doing a backup?
Click to expand...
Click to collapse
Probably not, the official TWRP for the 5X and 6P still need security removed before backup. But it doesn't hurt to try!

[ROOT] SuperSU

This thread was originally for Pixel-specific rooting instructions, but by now the SuperSU ZIP and TWRP are fully supported:
- Fastboot boot TWRP
- Install latest SuperSU ZIP (v2.79-SR3 at the time of writing)
Note that at this time I recommend against fastboot flashing TWRP. With the Pixel's new partition layout, the recovery files are inside the boot partition, and so is SuperSU. If you flash both, SuperSU's internal boot image backup will not be of the original boot image, but of TWRP. This means that neither the 'full unroot' option in SuperSU, nor incremental OTA update through FlashFire, will work as expected.
OR
- Use CF-Auto-Root for Pixel (not released at the time of writing, but should be released soon)

Thank you once again for root, do you finally get to enjoy your new Pixel?

Woooooooooooooo! I am so fricken excited for this.

can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!

Here is everything you need.
spunks3 said:
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Click to expand...
Click to collapse
http://www.xda-developers.com/root-is-now-available-for-the-google-pixel-and-pixel-xl/
Here is everything you need.

Once again you're the man Chainfire, thanks for all your hard work
- An unnamed tester needed to do the whole thing twice for the root to stick. While I assume this was Jeff's own fault, we can never be sure. -lol
---------- Post added at 09:17 PM ---------- Previous post was at 09:14 PM ----------
spunks3 said:
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Click to expand...
Click to collapse
According to the post..
The images for the Pixels need to be 'fastboot boot'ed, not flashed. After a few minutes (have patience) and a couple of (automatic) reboots, Android should boot fully rooted. Read the README in the ZIP.

clockcycle said:
Once again you're the man Chainfire, thanks for all your hard work
---------- Post added at 09:17 PM ---------- Previous post was at 09:14 PM ----------
According to the post..
The images for the Pixels need to be 'fastboot boot'ed, not flashed. After a few minutes (have patience) and a couple of (automatic) reboots, Android should boot fully rooted. Read the README in the ZIP.
Click to expand...
Click to collapse
needed to set everything up and enable usb debugging - thennnn boot into bootloader and flash boot-to-root.img.
all is well!

Running just fine, thank you Chainfire!
Sent from my Pixel using Tapatalk

Worked like a charm! Thanks @Chainfire. I had just posted my pixel up for sale. Guess I'll keep it a while longer.

root issues
Pixel 32gig bought from google store unlocked bootloader and did as tutorial said, i have superSU icon but not asking for root privilage, apps saying no root?

You are the best Chainfire I've met today.
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
mrnovanova said:
Worked like a charm! Thanks @Chainfire. I had just posted my pixel up for sale. Guess I'll keep it a while longer.
Click to expand...
Click to collapse
And I was eyeing a 5X... maybe not now!

So far when I flash EX kernel root stops working and when I reboot the phone to root it again kernel reverts back to stock. Lol! Guess I can't have both.

mrnovanova said:
So far when I flash EX kernel root stops working and when I reboot the phone to root it again kernel reverts back to stock. Lol! Guess I can't have both.
Click to expand...
Click to collapse
You're doing something wrong, it all works fine.
fastboot flash ElementalX and then fastboot boot Chainfire's boot-to-root.img

flar2 said:
You're doing something wrong, it all works fine.
fastboot flash ElementalX and then fastboot boot Chainfire's boot-to-root.img
Click to expand...
Click to collapse
Yup. It seems I was just booting the kernel image without flashing it. All good now followed directions on your last post where you say fastboot flash boot and not fastboot boot. I think that made all the difference.
Sent from my Pixel using XDA-Developers mobile app

More donations to come, after I return from Cruise

Will Xposed framework work? Or do we need to wait for twrp?

maflin18 said:
Will Xposed framework work? Or do we need to wait for twrp?
Click to expand...
Click to collapse
I'm wondering the same thing, but I'm pretty certain we need twrp. From what I understand there's a working version out there for the pixels, so it shouldn't be long before it's released.
Sent from my Pixel using XDA Labs

do i have to use fastboot boot boot-to-root.img or do i have to put it in slot a?

varun.gid said:
do i have to use fastboot boot boot-to-root.img or do i have to put it in slot a?
Click to expand...
Click to collapse
Slot a for kernel and fastboot boot boot-to-root for root worked for me.
Sent from my Pixel using XDA-Developers mobile app

maflin18 said:
Will Xposed framework work? Or do we need to wait for twrp?
Click to expand...
Click to collapse
Why ask the same question in more than one thread ?
Have you even read anything in the xposed thread ?
Your answer is in the xposed thread, not here
Sent from my Pixel using XDA-Developers mobile app

October update is out - QP1A.190711.148

October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds

chanh2018 said:
October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
Won't root for me.

you mean magisk not working with this build?

mcdull said:
you mean magisk not working with this build?
Click to expand...
Click to collapse
No, it's not working for ME.
Sent from my PH-1 using XDA Labs

avd said:
Won't root for me.
Click to expand...
Click to collapse
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.

kt-Froggy said:
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.
Click to expand...
Click to collapse
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:

JimmyCash030 said:
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:
Click to expand...
Click to collapse
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.

kt-Froggy said:
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.
Click to expand...
Click to collapse
yeah worked for me as well with the latest canary MM !!

Magisk 19.4 works just fine on latest 148 build if need be I can upload magisk rooted boot. Img

https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img

allenjthomsen said:
https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img
Click to expand...
Click to collapse
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
avd said:
getting back to the topic at hand, i flashed this, then twrp on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now i got to plug this in and swap slots to reinstall twrp.
Is possible that magisk and twrp are back to not playing nice to each other again?
(i'll test this out if i get a chance to swap slots)
Click to expand...
Click to collapse
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.

Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.

allenjthomsen said:
Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.
Click to expand...
Click to collapse
pretty much everything for this phone resides in t.me/ESSENTIALPH1DEV

avd said:
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.
Click to expand...
Click to collapse
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again

rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
Flashing the patched image provided just sits there looking at the boot animation.
I'll play with it tonight.
It's a Sprint phone. Could that be the issue?
Sent from my PH-1 using XDA Labs

I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?

I'm no expert but did this ans it worked:
1. In TWRP recovery (created nandroid and wiped cache)
2. Flashed full update zip from official download link, then TWRP, then wipe cache
3. Reboot system and let it settle
4. Reboot into TRWP and flashed Canary Channel zip file
5. Wipe cache
6. Reboot system
Hope this helps.

jionny said:
I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?
Click to expand...
Click to collapse
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
? I always have trouble remembering, not anymore it seems

gavinfernandes2012 said:
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
I always have trouble remembering, not anymore it seems
Click to expand...
Click to collapse
Are you able to give more precise instructions on fastboot instructions?

jionny said:
Are you able to give more precise instructions on fastboot instructions?
Click to expand...
Click to collapse
Nevermind, got the instructions from essentials site. flashed via fastboot which erased everything had to do a complete setup again