I unenrolled from the Android beta program yesterday but they still haven't sent an OTA to rollback to N. Can I use wugz to manually do it?
Sent from my Pixel XL using XDA-Developers Legacy app
ucpro said:
I unenrolled from the Android beta program yesterday but they still haven't sent an OTA to rollback to N. Can I use wugz to manually do it?
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Have you tried just flashing the latest N factory image or are you trying to retain data and such?
I'd wipe data just to be safe
Sent from my Pixel XL using XDA-Developers Legacy app
Jammol said:
Have you tried just flashing the latest N factory image or are you trying to retain data and such?
Click to expand...
Click to collapse
On Verizon you cannot flash the latest public image. The bootloader is too old coming from Android O
fresnored said:
On Verizon you cannot flash the latest public image. The bootloader is too old coming from Android O
Click to expand...
Click to collapse
What?
I have an unlocked pixel. I just wanna make sure nothing will mess up if I try to flash an image through wugz
Sent from my Pixel XL using XDA-Developers Legacy app
ucpro said:
I have an unlocked pixel. I just wanna make sure nothing will mess up if I try to flash an image through wugz
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
I guess wugz is a toolkit right? I'm not sure why you'd need to use anything other than the bootloader menu to flash a factory image. Extract the image you want, in bl menu (on the computer) just type flash-all if you're on Windows, walk away when it starts and come back in 10 minutes. Done.
bobby janow said:
I guess wugz is a toolkit right? I'm not sure why you'd need to use anything other than the bootloader menu to flash a factory image. Extract the image you want, in bl menu (on the computer) just type flash-all if you're on Windows, walk away when it starts and come back in 10 minutes. Done.
Click to expand...
Click to collapse
That's what I was thinking. And the fact that a full wipe is desired makes it even easier.
Yes wugz is a root toolkit but it also let's you restore your phone with whatever version of Android you want, and also downloads the image for you. I haven't tried doing it through the bootloader
Sent from my Pixel XL using XDA-Developers Legacy app
ucpro said:
Yes wugz is a root toolkit but it also let's you restore your phone with whatever version of Android you want, and also downloads the image for you. I haven't tried doing it through the bootloader
Click to expand...
Click to collapse
Are you familiar with flashing Google factory images? If not, @CZ Eddie has a nice tutorial in the guides sub-forum.
I do that through ADB right?
Sent from my Pixel XL using XDA-Developers Legacy app
ucpro said:
I do that through ADB right?
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
No, you do it while in the bootloader menu from the computer. You just need to make sure your device is recognized in bootloader mode on the computer with the command fastboot devices. It should show up. Then flash to your hearts content. Just download and extract the correct image to the correct folder on the computer.
Ok I'll give it a shot
Sent from my Pixel XL using XDA-Developers Legacy app
i'm not having any luck with adb. It doesn't show my device in fastboot OR recovery. When the phone is booted up, adb works fine. Can I just put the image zip on the phone and install through revovery?
ucpro said:
i'm not having any luck with adb. It doesn't show my device in fastboot OR recovery. When the phone is booted up, adb works fine. Can I just put the image zip on the phone and install through revovery?
Click to expand...
Click to collapse
No I think you should properly learn how to use fastboot and adb before continuing any further.
What fastboot version are you currently using.
What output do you get when you type fastboot devices with your device in the bl menu. Let's figure out you're fastboot issues first and then worry about flashing the image(which will be the easy part).
toknitup420 said:
No I think you should properly learn how to use fastboot and adb before continuing any further.
What fastboot version are you currently using.
What output do you get when you type fastboot devices with your device in the bl menu. Let's figure out you're fastboot issues first and then worry about flashing the image(which will be the easy part).
Click to expand...
Click to collapse
Wise words. Not replying to the OP so hopefully he reads down a bit. It looks like his drivers are not working, i.e. the fastboot ones since he can adb. If he's on Windows then device manager should show an exclamation mark or unknown device. There is a fastboot installation, let me take a look see if I can find it. Ok here ya go. https://www.androidusbdrivers.com/google-pixel-usb-drivers/ I actually didn't need to do that exact procedure but I've been fastbooting for some time.
To the OP. You need to get 'fastboot devices' command to show your device when connected via usb to your computer and in bootloader mode. Once it sees the device the rest is child's play.
---------- Post added at 12:12 PM ---------- Previous post was at 12:11 PM ----------
ucpro said:
i'm not having any luck with adb. It doesn't show my device in fastboot OR recovery. When the phone is booted up, adb works fine. Can I just put the image zip on the phone and install through recovery?
Click to expand...
Click to collapse
See above.
bobby janow said:
Wise words. Not replying to the OP so hopefully he reads down a bit. It looks like his drivers are not working, i.e. the fastboot ones since he can adb. If he's on Windows then device manager should show an exclamation mark or unknown device. There is a fastboot installation, let me take a look see if I can find it. Ok here ya go. https://www.androidusbdrivers.com/google-pixel-usb-drivers/ I actually didn't need to do that exact procedure but I've been fastbooting for some time.
To the OP. You need to get 'fastboot devices' command to show your device when connected via usb to your computer and in bootloader mode. Once it sees the device the rest is child's play.
---------- Post added at 12:12 PM ---------- Previous post was at 12:11 PM ----------
See above.
Click to expand...
Click to collapse
I can get the phone to show on the computer in adb when the phone is booted up, but it won't show while in fastboot. I use the same command 'adb devices' when the phone is booted up and also in fastboot. I looked through my device manager and there's no exclamation points anywhere on both computers that I've tried
ucpro said:
I can get the phone to show on the computer in adb when the phone is booted up, but it won't show while in fastboot. I use the same command 'adb devices' when the phone is booted up and also in fastboot. I looked through my device manager and there's no exclamation points anywhere on both computers that I've tried
Click to expand...
Click to collapse
You need to type "fastboot devices" when in the bootloader.
Ok I'll give it a shot later tonight
Related
I am getting mixed messages with how to root. I figured I have to flash TWRP before rooting, but how do I do that with having MDA89E version? The tutorial for flashing new OTA says I have to have TWRP first??? Can someone put me in the right direction??? Thanks a lot.
Sent from my Nexus 5X using XDA Free mobile app
dave2775 said:
I am getting mixed messages with how to root. I figured I have to flash TWRP before rooting, but how do I do that with having MDA89E version? The tutorial for flashing new OTA says I have to have TWRP first??? Can someone put me in the right direction??? Thanks a lot.
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Get this one: MDB08I - 6.0.0: https://dl.google.com/dl/android/aosp/bullhead-mdb08i-factory-64536fcf.tgz , unpack it fully down to the folder that has the image files in it and that can be anywhere (let's say \temp for now).
Notice that there is a batch file that can do a full flash of the OS that you'll have unpacked from the .tgz file. You'll use that once in Fastboot to flash it. Don't worry about having TWRP or a special bootloader before you do any of this. Just get into fastboot (like "adb reboot bootloader" or hold down up&down&power buttons for awhile until in fastboot). Once in flashboot:
Flash MDB08I, boot things up, set things up, make sure it seems "normal" and check the "about phone" settings, and then you should be set to do what you want with the modified image & TWRP, etc.
I don't know what I'm doing wrong but when I try to flash I get an error "fastboot is not recognized...blah."
Sent from my Nexus 5X using XDA Free mobile app
I confirmed fastboot and adb are working correctly so not sure what I'm doing wrong. Just opening the batch file opens command window correct? I don't have to do anything else?
Sent from my Nexus 5X using XDA Free mobile app
You need to put the extracted files from the download "flash-all.sh, flash-all.bat, flash-base.sh bootloader-bullhead-bhz10i.img, image-bullhead-mdb08i.zip, radio-bullhead-m8994f-2.6.28.0.065.img" in the same folder as platfrom-tools. From there you run the flash-all.bat in the command prompt. just did it today.
dave2775 said:
I confirmed fastboot and adb are working correctly so not sure what I'm doing wrong. Just opening the batch file opens command window correct? I don't have to do anything else?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
If you are getting confused you can always use the Unified Android Toolkit to download/flash the MDB08I image automatically. It will guide you through decrypting and rooting it too.
If you want to learn and do it all manually then good luck
Mark.
dave2775 said:
I confirmed fastboot and adb are working correctly so not sure what I'm doing wrong. Just opening the batch file opens command window correct? I don't have to do anything else?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
You say that you "confirmed fastboot and adb are working correctly", but that doesn't sound right since your prior post said that "fastboot not recognized". Everyone else that's posted is on the right track and you need to be certain that fastboot (and adb for that matter) are in the correct path or they won't run or be recognized. It's not automatic. You need to either modify %PATH% var in windows, but that's semi-complex, or take the easy road, and move a copy of fastboot & adb to the same folder your image files (.img) are in. Also be certain to move the 'flash-all.bat' file(s) to the same place.
Change your directory to be where all those files are. Be certain the device is in fastboot mode and then make sure it's all working by doing this (or these) commands:
Code:
c:\{place-where-it's-all-at}: fastboot devices
That command should list some number which is the device number which verifies that fastboot is recognized and that the device is recognized.
you can do the same thing with adb (adb devices, look at the number).
---------------------- If that works.... -----------------
Stay in that folder and do the flash-all.bat (OK, I don't recall the exact name of their everything flash file, but I think it's that). It takes some time, but I've used these instructions to help a couple people through this.
Of course, mskip's way is also fine. Whatever works is good. -- Good luck. You're no where near being bricked and in good shape to get this done.
I thought I wasn't able to do that without flashing the image first. Anyway ibwas able to figure it out. I did try to flash TWRP and root with your tootkit but got a nessage " recovery not recognized" or something to that effect. Any idea?
Sent from my Nexus 5X using XDA Free mobile app
dave2775 said:
I thought I wasn't able to do that without flashing the image first. Anyway ibwas able to figure it out. I did try to flash TWRP and root with your tootkit but got a nessage " recovery not recognized" or something to that effect. Any idea?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
The way I've talked about flashing the image, you don't need TWRP, or anything before you do it, other than what I said. If someone has now put up a zip version of the image, then yeah, you'd need custom recovery, but you don't need to use a zip image. It's less confusing just to use the native stuff and fastboot.
Is fastboot working or not. Are you sure you are getting the phone into fastboot? Can you get output from a "fastboot devices" command? Also, please give us the exact error messages. Write them down when you see them. It'll help whichever of us is trying to help.
I helped someone with this type of problem over here http://forum.xda-developers.com/showpost.php?p=63439400&postcount=17 , so maybe reading that will help.
I was able to flash the image over with fastboot so I'm now on the OTA. My question now is with flashing twrp. When it prompts within twrp to allow modifications or keep as read only? That's where I'm stuck now. Thanks for your help.
Sent from my Nexus 5X using XDA Free mobile app
dave2775 said:
I was able to flash the image over with fastboot so I'm now on the OTA. My question now is with flashing twrp. When it prompts within twrp to allow modifications or keep as read only? That's where I'm stuck now. Thanks for your help.
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Good. There's no point in installing TWRP at all unless you allow modifications. Allow them and tell that screen to go away forever. Good luck.
Yeh I figured that but never came across if before with other phones. Would you know if its an excessively long boot time after first flashing it?
Sent from my Nexus 5X using XDA Free mobile app
dave2775 said:
Yeh I figured that but never came across if before with other phones. Would you know if its an excessively long boot time after first flashing it?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Once you get to this point (installing TWRP), it's best to find & follow the best guide (by that I mean that people had the least problems with) verbatim. Then ask questions in that thread:
I took a quick look and this one looks fine: http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
Another way to to use mskips ways, but ask questions afterward in his thread.
I don't have a 5x (or anything like it) and I only really want to comment on things I've done a number of times before. My only comment about boot "quickly" vs. "booting normally", is that the first time you've done something "traumatic" like unencrypting, or wiping something, then of course it takes longer to do a regular boot. Booting into recovery should always be nearly instant.
So, I tried to install CM13 on my zenfone 2 using a tethered custom recovery and now when I apply the update and restart, I am redirected to the bootloader menu. (cm13 and gapps install but when i restart i go back to reboot i go to bootloader)
If possible help me make it stay on cm13 or marshmallow
i have zenfone 2 1080p
I'm not 100 percent sure, but I believe you need installed TWRP. Tethered wont do. I could be wrong tho.
Sent from my ASUS_Z00A using Tapatalk
When i try to install it via adb (flashing twrp.img) it either does not see my device or it says it is unauthorized
Is your bootloader unlocked?
I have the same problem, I followed a guide I found here on xda to unlock the bootloader of the ze550ml mm beta, problem is that, after using that guide and supposedly unlocking the bootloader, using the twrp i found in that guide i tried to flash the latest cm13 build for my device but it always goes to fastboot, also the only recovery that works is the twrp I found in that guide. Please help me fix this.
Dan_Jacques said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
By unlocked do you mean if I can get into the bootloader or into the stock recovery. I cannot get into the stock recovery but I can get in the bootloader
hudasameer450 said:
By unlocked do you mean if I can get into the bootloader or into the stock recovery. I cannot get into the stock recovery but I can get in the bootloader
Click to expand...
Click to collapse
When I get home I will post a video of what happens
nvm i just realized i dont have a phone
hudasameer450 said:
nvm i just realized i dont have a phone
Click to expand...
Click to collapse
What the heck?
Sent from my ASUS_Z00A using Tapatalk
hudasameer450 said:
When i try to install it via adb (flashing twrp.img) it either does not see my device or it says it is unauthorized
Click to expand...
Click to collapse
Do you have the advantage drivers and fastboot installed on your pc? Did you go into developer mode in your phone and turn on USB debugging? Lastly, did you authorize the pc to debug your phone? (the authorization screen that pops up the first time you send an add command to your phone)... It sounds like one of these issues are your problem
Sent from my ASUS_Z00AD using XDA-Developers mobile app
jflow36 said:
Do you have the advantage drivers and fastboot installed on your pc? Did you go into developer mode in your phone and turn on USB debugging? Lastly, did you authorize the pc to debug your phone? (the authorization screen that pops up the first time you send an add command to your phone)... It sounds like one of these issues are your problem
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Click to expand...
Click to collapse
what are advantage drivers and yes to everything else
My Zenphone will not boot. It say's it's updating firmware and then goes to the Android on it's back..
I can get to the boot loader and recovery but no commands via adb will work. Say's I have "no permissions". I'm using ubuntu if that matters.
I downloaded UL-Z00A-WW-4.21.40.184-user.zip and try to sideload via adb but again, no permissions.
I'm hoping I can unbrick and any help is greatly appreciated.
IFWI Version 0094.0177
christanya99 said:
My Zenphone will not boot. It say's it's updating firmware and then goes to the Android on it's back..
I can get to the boot loader and recovery but no commands via adb will work. Say's I have "no permissions". I'm using ubuntu if that matters.
I downloaded UL-Z00A-WW-4.21.40.184-user.zip and try to sideload via adb but again, no permissions.
I'm hoping I can unbrick and any help is greatly appreciated.
IFWI Version 0094.0177
Click to expand...
Click to collapse
in bootloader where it shows IFWI version , you can fastboot flash only ,reboot to recovery , then adb sideload .
timbernot said:
in bootloader where it shows IFWI version , you can fastboot flash only ,reboot to recovery , then adb sideload .
Click to expand...
Click to collapse
The device shows up when I send "fastboot devices".
I tried fastboot flash and the name of the zip but terminal just sits at "waiting for device".
Any fastboot commands just result in the same.
Sent from my Pixel using XDA-Developers Legacy app
I don't know fastboot cmds for ubuntu but if you're not bothered about wiping data , maybe try >
fastboot erase data
Then
fastboot reboot
Maybe , even wipe data from recovery if update was corrupted
timbernot said:
I don't know fastboot cmds for ubuntu but if you're not bothered about wiping data , maybe try >
fastboot erase data
Then
fastboot reboot
Maybe , even wipe data from recovery if update was corrupted
Click to expand...
Click to collapse
Commands are the same I believe. It's just ADB through the Linux Terminal.
I did wipe data through recovery but that did nothing.
Fastboot erase data results in "waiting for device"
Sent from my Pixel using XDA-Developers Legacy app
Cab you not get your hands on a Windows pc ?
You could flash raw with AFT in bootloader
timbernot said:
Cab you not get your hands on a Windows pc ?
You could flash raw with AFT in bootloader
Click to expand...
Click to collapse
Just booted into Windows 10 and am trying what you suggest. My model Z00AD isn't listed in aft thought. Aft did find the device though.
Sent from my Pixel using XDA-Developers Legacy app
christanya99 said:
Just booted into Windows 10 and am trying what you suggest. My model Z00AD isn't listed in aft thought. Aft did find the device though.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
check my signature for aft download in unbrick thread, its listed in the dropdown box to the left in that AFT
run as admin .
---------- Post added at 05:19 AM ---------- Previous post was at 04:55 AM ----------
this AFT
http://www.mediafire.com/file/sm76jyyz8t1axmz/AsusFlashToolInstaller_1.0.0.17.rar
timbernot said:
check my signature for aft download in unbrick thread, its listed in the dropdown box to the left in that AFT
run as admin .
---------- Post added at 05:19 AM ---------- Previous post was at 04:55 AM ----------
this AFT
http://www.mediafire.com/file/sm76jyyz8t1axmz/AsusFlashToolInstaller_1.0.0.17.rar
Click to expand...
Click to collapse
Got it but xFSTK won't open at all. Followed the steps..
Thanks for all your help!!
Sent from my Pixel using XDA-Developers Legacy app
christanya99 said:
Got it but xFSTK won't open at all. Followed the steps..
Thanks for all your help!!
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
WHOOOA THERE !!!
Don't go anywhere near xFSTK
You just run AFT as admin , do not use xFSTK downloader ...and flash raw file only in AFT ,
timbernot said:
WHOOOA THERE !!!
Don't go anywhere near xFSTK
Click to expand...
Click to collapse
Haha, OK. It wouldn't run anyway.
When I open the version of aft that you sent, it finds my device and shows me the serial number but my model isn't listed.
Gotta crash now but will watch the video in full tomorrow.
Thanks again!!
Sent from my Pixel using XDA-Developers Legacy app
@christanya99
You click dropdown box to the left in aft then scroll to bottom lol
timbernot said:
@christanya99
You click dropdown box to the left in aft then scroll to bottom lol
Click to expand...
Click to collapse
Lol, I did. I'm just saying that Z00AD isn't listed specifically. Not sure if that matters though.
Sent from my Pixel using XDA-Developers Legacy app
@christanya99
Z00AD is ze551ml
timbernot said:
Z00AD is ze551ml
Click to expand...
Click to collapse
OK, that's what I thought.
Sent from my Pixel using XDA-Developers Legacy app
timbernot said:
@christanya99
Z00AD is ze551ml
Click to expand...
Click to collapse
Lol, it's flashing now. I wasn't highlighting the serial before clicking start. SMRT
Thank you so much!!
Sent from my Pixel using XDA-Developers Legacy app
Just got it from tmo. Was hoping I could remove the carrier from the status bar. Anyone able to tell me how.
Also. To piggy back. Google pay doesn't work on rooted phones right now does it
VivisClone said:
Just got it from tmo. Was hoping I could remove the carrier from the status bar. Anyone able to tell me how.
Also. To piggy back. Google pay doesn't work on rooted phones right now does it
Click to expand...
Click to collapse
Magisk hide, then you're good to go.
Uzephi said:
Magisk hide, then you're good to go.
Click to expand...
Click to collapse
Mind pointing me in the right direction? Haven't touched root since the Samsung S5. And I don't think ODIN works on Motorola.
VivisClone said:
Just got it from tmo. Was hoping I could remove the carrier from the status bar. Anyone able to tell me how.
Also. To piggy back. Google pay doesn't work on rooted phones right now does it
Click to expand...
Click to collapse
Try this:
Settings - Network & Internet - Mobile Network
Uncheck "Show Mobile Network"
Sent from my Moto Z2 Force using XDA Labs
---------- Post added at 06:45 PM ---------- Previous post was at 06:43 PM ----------
VivisClone said:
Just got it from tmo. Was hoping I could remove the carrier from the status bar. Anyone able to tell me how.
Also. To piggy back. Google pay doesn't work on rooted phones right now does it
Click to expand...
Click to collapse
Here is the guide for unlocking the bootloader and installing TWRP + root...
https://forum.xda-developers.com/z2-force/how-to/oreo-nougat-how-to-root-z2-t3756669
Sent from my Moto Z2 Force using XDA Labs
fast69mopar said:
Try this:
Settings - Network & Internet - Mobile Network
Uncheck "Show Mobile Network"
Sent from my Moto Z2 Force using XDA Labs
---------- Post added at 06:45 PM ---------- Previous post was at 06:43 PM ----------
Here is the guide for unlocking the bootloader and installing TWRP + root...
https://forum.xda-developers.com/z2-force/how-to/oreo-nougat-how-to-root-z2-t3756669
Click to expand...
Click to collapse
Awesome! Thanks! That was the spot. Having issues with flashing the img. But I'll look at it later. Kept saying waiting on device
VivisClone said:
Awesome! Thanks! That was the spot. Having issues with flashing the img. But I'll look at it later. Kept saying waiting on device
Click to expand...
Click to collapse
Make sure you have downloaded and installed the correct drivers for your new Z2 Force. Once the drivers are installed and your device is connected, open the device manager and make sure you don't have any yellow question marks next to your device. If you do, right click on the line and select update driver and let Windows do its thing to locate the drivers.
You also need to make sure you have adb and fastboot installed on your PC. You can you the simple adb/fastboot installer or download the Android SDK Platform Tools which contains arb and fastboot.
If you decide to download an app/fastboot installer, make sure you select the option to install it system wide.
Now, make sure you have connected your Z2 and open a command prompt window and type:
adb devices
It will start the daemon. Type adb devices again and you should see your device serial number.
Once you see your serial number type:
adb reboot bootloader
Now begin the TWRP installation process
Okay, be careful with your choice of commands when trying to install TWRP. With our device, when you first attempt to install TWRP, you want to "BOOT" the TWRP.img
You DO NOT want to flash the TWRP.img
You only want to BOOT the TWRP.img and then once booted to TWRP recovery, you will flash the TWRP installer zip that can be obtained from
www.TWRP.me webiste.
Flashing the TWRP Installer zip will complete the TWRP installation.
Sent from my Moto Z2 Force using XDA Labs
fast69mopar said:
Make sure you have downloaded and installed the correct drivers for your new Z2 Force. Once the drivers are installed and your device is connected, open the device manager and make sure you don't have any yellow question marks next to your device. If you do, right click on the line and select update driver and let Windows do its thing to locate the drivers.
You also need to make sure you have adb and fastboot installed on your PC. You can you the simple adb/fastboot installer or download the Android SDK Platform Tools which contains arb and fastboot.
If you decide to download an app/fastboot installer, make sure you select the option to install it system wide.
Now, make sure you have connected your Z2 and open a command prompt window and type:
adb devices
It will start the daemon. Type adb devices again and you should see your device serial number.
Once you see your serial number type:
adb reboot bootloader
Now begin the TWRP installation process
Okay, be careful with your choice of commands when trying to install TWRP. With our device, when you first attempt to install TWRP, you want to "BOOT" the TWRP.img
You DO NOT want to flash the TWRP.img
You only want to BOOT the TWRP.img and then once booted to TWRP recovery, you will flash the TWRP installer zip that can be obtained from
www.TWRP.me webiste.
Flashing the TWRP Installer zip will complete the TWRP installation.
Sent from my Moto Z2 Force using XDA Labs
Click to expand...
Click to collapse
We are all set! Thanks! Now to figure out what version of xposed I need lol
VivisClone said:
We are all set! Thanks! Now to figure out what version of xposed I need lol
Click to expand...
Click to collapse
Glad you got it worked out. If you are using Magisk for root you can scroll all the way to the bottom of "Downloads" to find the Xposed Framework modules. If you are running Android 8.0 it is SDK 26. Android 8.1 is SDK 27.
Sent from my Moto Z2 Force using XDA Labs
fast69mopar said:
Glad you got it worked out. If you are using Magisk for root you can scroll all the way to the bottom of "Downloads" to find the Xposed Framework modules. If you are running Android 8.0 it is SDK 26. Android 8.1 is SDK 27.
Sent from my Moto Z2 Force using XDA Labs
Click to expand...
Click to collapse
Thanks figured that out too. Have Android pay working still. But poke go is not working. Small loss. Love that I rooted just so I could cleanup my status bar and add a theme.
VivisClone said:
Thanks figured that out too. Have Android pay working still. But poke go is not working. Small loss. Love that I rooted just so I could cleanup my status bar and add a theme.
Click to expand...
Click to collapse
Nice work. This is an awesome device. There is still so much more to be figured out though. I have dedicated myself to figure out why we can't delete anything from the OEM Partition. I posted a question a couple of weeks ago but nobody responded with an answer or any ideas so I'm gonna do what I can to figure it out.
On Pokemon Go, have you tried to hide Magisk from Pokemon Go in the Magisk Manager under Magisk Hide? May give it a shot.
Sent from my Moto Z2 Force using XDA Labs
fast69mopar said:
Nice work. This is an awesome device. There is still so much more to be figured out though. I have dedicated myself to figure out why we can't delete anything from the OEM Partition. I posted a question a couple of weeks ago but nobody responded with an answer or any ideas so I'm gonna do what I can to figure it out.
On Pokemon Go, have you tried to hide Magisk from Pokemon Go in the Magisk Manager under Magisk Hide? May give it a shot.
Sent from my Moto Z2 Force using XDA Labs
Click to expand...
Click to collapse
Yeah. Tried it. Still said it wasn't compatible. It was weird.
As for the oem thing, how you going about looking on to it?
I always wanted to make a room or whatever. But never knew where to start
Hi everyone.
I'm desperate for help here. I've not even had this phone 12 hours and it's unusable. I feel sick to stomach.
I tried to root my phone via TWRP.img boot and Majisk.
Followed the process, booted into TWRP.img.
Flashed TWRP and Majisk(I assume on the same partition, my idiot mistake there) and it went into bootloop.
No problem, reflash back to factory image and now touch screen doesn't work on the OS.
To test, I reboot back into TWRP.img and touch works there.
I'm begging you wonderful people here.
Please help.
Edit: Additional information, it always boots into recovery mode before booting OS
ryanhavana said:
Hi everyone.
I'm desperate for help here. I've not even had this phone 12 hours and it's unusable. I feel sick to stomach.
I tried to root my phone via TWRP.img boot and Majisk.
Followed the process, booted into TWRP.img.
Flashed TWRP and Majisk(I assume on the same partition, my idiot mistake there) and it went into bootloop.
No problem, reflash back to factory image and now touch screen doesn't work on the OS.
To test, I reboot back into TWRP.img and touch works there.
I'm begging you wonderful people here.
Please help.
Click to expand...
Click to collapse
Try flashing the stock firmware keeping the -w and then boot the twrp.img, switch slots, reboot to bootloader and flash stock again.
Misterxtc said:
Try flashing the stock firmware keeping the -w and then boot the twrp.img, switch slots, reboot to bootloader and flash stock again.
Click to expand...
Click to collapse
Hi,
Thank you.
I'll try this immediately
Misterxtc said:
Try flashing the stock firmware keeping the -w and then boot the twrp.img, switch slots, reboot to bootloader and flash stock again.
Click to expand...
Click to collapse
This didn't work.
:crying:
Boot into twrp then run the magisk uninstaller. Then flash the factory image.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Boot into twrp then run the magisk uninstaller. Then flash the factory image.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Stupid question,
I can't seem to get access to the phone's storage on my PC since I can't get into the OS.
I assume there's another way to access the storage?
Thank you!
ryanhavana said:
Stupid question,
I can't seem to get access to the phone's storage on my PC since I can't get into the OS.
I assume there's another way to access the storage?
Thank you!
Click to expand...
Click to collapse
Do you have the stock recovery on your device now? If so boot into it and use adb to push the file to your device.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Do you have the stock recovery on your device now? If so boot into it and use adb to push the file to your device.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thank you,
I'm not sure I'm doing it correctly.
C:\Users\Ryry\Desktop\Pixel 3 XL B\platform-tools>adb push "C:\Users\Ryry\Desktop\Pixel 3 XL B\Magisk-v18.0.zip" /storage/
adb: error: failed to get feature set: no devices/emulators found
ryanhavana said:
Thank you,
I'm not sure I'm doing it correctly.
C:\Users\Ryry\Desktop\Pixel 3 XL B\platform-tools>adb push "C:\Users\Ryry\Desktop\Pixel 3 XL B\Magisk-v18.0.zip" /storage/
adb: error: failed to get feature set: no devices/emulators found
Click to expand...
Click to collapse
Push it to /storage/emulated/0/Download
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Push it to /storage/emulated/0/Download
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I feel like a right fool here. I'm really sorry.
C:\Users\Ryry\Desktop\Pixel 3 XL B\platform-tools>adb push "C:\Users\Ryry\Desktop\Pixel 3 XL B\Magisk-v18.0.zip" /storage/emulated/0/Download
adb: error: failed to get feature set: no devices/emulators found
ryanhavana said:
I feel like a right fool here. I'm really sorry.
C:\Users\Ryry\Desktop\Pixel 3 XL B\platform-tools>adb push "C:\Users\Ryry\Desktop\Pixel 3 XL B\Magisk-v18.0.zip" /storage/emulated/0/Download
adb: error: failed to get feature set: no devices/emulators found
Click to expand...
Click to collapse
What do you get when you type adb devices. Does that return the serial number. Also, do you have the latest sdk platform tools?
Sent from my [device_name] using XDA-Developers Legacy app
ryanhavana said:
Hi everyone.
I'm desperate for help here. I've not even had this phone 12 hours and it's unusable. I feel sick to stomach.
I tried to root my phone via TWRP.img boot and Majisk.
Followed the process, booted into TWRP.img.
Flashed TWRP and Majisk(I assume on the same partition, my idiot mistake there) and it went into bootloop.
No problem, reflash back to factory image and now touch screen doesn't work on the OS.
To test, I reboot back into TWRP.img and touch works there.
I'm begging you wonderful people here.
Please help.
Edit: Additional information, it always boots into recovery mode before booting OS
Click to expand...
Click to collapse
What process did you follow?
Did you purchase it from Google or Verizon?
Do you have the latest SDK Platform-tools r28.0.1?
jd1639 said:
What do you get when you type adb devices. Does that return the serial number. Also, do you have the latest sdk platform tools?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have the latest SDK platform tools.
C:\Users\Ryry\Desktop\Pixel 3 XL B\platform-tools>adb devices
List of devices attached
It's just blank
Homeboy76 said:
What process did you follow?
Did you purchase it from Google or Verizon?
Do you have the latest SDK Platform-tools r28.0.1?
Click to expand...
Click to collapse
Yes, the latest.
I followed this - https://www.youtube.com/watch?v=BgV1xxkcBk8
I purchased via contract from EE(UK). I very much doubt they will replace the handset.
I'm starting to panic
ryanhavana said:
I have the latest SDK platform tools.
C:\Users\Ryry\Desktop\Pixel 3 XL B\platform-tools>adb devices
List of devices attached
It's just blank
Click to expand...
Click to collapse
That may not be good. When you boot into the stock do you select the adb sideload, I don't remember exactly what it says. You need to do that too run the adb commands.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
What do you get when you type adb devices. Does that return the serial number. Also, do you have the latest sdk platform tools?
Click to expand...
Click to collapse
@jd1639@ryanhavana
Sorry, I'm dropping out, you are more than qualified to assist him
One question what did he get when he typed fastboot devices?
jd1639 said:
That may not be good. When you boot into the stock do you select the adb sideload, I don't remember exactly what it says. You need to do that too run the adb commands.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have no idea. I don't think I have touched anything that mentions adb sideload
Duplicate
Ok, you're booting into the bootloader and then going to recovery? Then you get the dead andriod? Then you press and hold power then press and release vol up to get into the recovery? Then you should see a selection for "Apply update from adb". You need to get there to run adb commands.
Sent from my [device_name] using XDA-Developers Legacy app
Homeboy76 said:
@jd1639@ryanhavana
Sorry, I'm dropping out, you are more than qualified to assist him
One question what did he get when he typed fastboot devices?
Click to expand...
Click to collapse
Fastboot devices returns my serial number