wifi not working on android p - Essential Phone Questions & Answers

I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work

TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk

Reflash it
TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...

Wolfhawke said:
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...
Click to expand...
Click to collapse
Why? Root works fine with it, this has nothing to do with that.

crixley said:
Why? Root works fine with it, this has nothing to do with that.
Click to expand...
Click to collapse
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.

jmill75 said:
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.
Click to expand...
Click to collapse
Yes it works fine and the issue has nothing to do with root. Probably half of us using it are rooted without issue

Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).

tliebeck said:
Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).
Click to expand...
Click to collapse
Just got my Essential Phone today as well and did the exact same thing, flashed straight from 7.1.1 to P. I thought I was seriously going to have to send the phone back due to a broken Wi-Fi chip or something. You are seriously a lifesaver!

rignfool said:
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.

Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
If I take your post at face value... You have a bad flash and need to try again... Or blame your cable... And go buy a new one...
Otherwise... You have a bad download... Or there is something wrong wrong with your zip or batch/script... Or you're not completely unlocked

Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.

Same here but can't roll back to Oreo
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?

1jason said:
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?
Click to expand...
Click to collapse
Yes flash the july oreo flashall. Bat

Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
I had the same problem. went back to stock on July's build (was on January's stock build previously) and reflashed P. Been smooth sailing ever since

jacksummers said:
Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.
Click to expand...
Click to collapse
The reason is because one of the OTAs did not have the partition you're looking for... And it created a mismatch somewhere...
You DO NOT need to have the same software on A and B... It just makes troubleshooting easier from our perspective... And... It forces you to reflash and probably fix the problem...
As intended... There should ALWAYS be a mismatch between A and B... At least a monthly security update... If not an Android versioning difference

Edited. We are all just trying to help others. Lets keep it that way.

so, uhmmm like yea...... there is this thread here, called the stock images thread (link for posterity https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 ) this is firmware images, directly from essential. I have added the remaining images that you dont get from essential, so that way you can reflash, and get the same version of software on both sides. there are wipe and no wipe bat files in there, twrp11 (the working twrp we have), and the fix red boot (in case you broke verity), and a stockboot.img (coincidentally the same file as called boot in the zip, but renamed for your twrp/rooting pleasure).
These images work great, many many many people have used them to go back and forth between O and P, OTA, or recover from catastrophe. As usual, beware of dragons, make SURE SURE SURE SURE you have a working adb/fastboot environment (use the version that comes with essentials drivers) (you can always do ADB VERSION or FASTBOOT --VERSION ) to check your version and where its working out of. It is 1 stop shopping. I also know the guy that makes the zips

jacksummers said:
Edited. We are all just trying to help others. Lets keep it that way.
Click to expand...
Click to collapse
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...

rignfool said:
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...
Click to expand...
Click to collapse
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.

jacksummers said:
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.
Click to expand...
Click to collapse
Wouldn't it be easier to attempt to port the 2 or 3 features we don't have as a separate systemui.apk or framework-res.apk?
And use Magisk?
Since we don't have that fancy hardware photo rendering thingymabob

Related

Nexus 9 Android N Preview

It seems the n9 is eligible. Anyone has tried or thinking of trying? I might try
Flashing it right now. Just going to miss root, so u can drop my DPI and restore some apps.
Edit: sweet!! Though you can't fine tune the size, it now has default a way to change screen size/DPI. Now I'm only needing root to restore some apps and data.
Works pretty well for me so far, except for the fact that kernel support for libusb is gone, which stops my Headunit app from working over USB.
No root yet.
Recovery is replaced with stock recovery after a reboot.
There is more discussion in popular phone threads, like the one for Nexus 6p.
dictionary said:
Flashing it right now. Just going to miss root, so u can drop my DPI and restore some apps.
Edit: sweet!! Though you can't fine tune the size, it now has default a way to change screen size/DPI. Now I'm only needing root to restore some apps and data.
Click to expand...
Click to collapse
mikereidis said:
Works pretty well for me so far, except for the fact that kernel support for libusb is gone, which stops my Headunit app from working over USB.
No root yet.
Recovery is replaced with stock recovery after a reboot.
There is more discussion in popular phone threads, like the one for Nexus 6p.
Click to expand...
Click to collapse
Do we have to be on stock to receive the notification?
I opted in for the Android N program. Received the OTA and installed but the install FAILED. Now I can't boot and can't install an image because my bootloader is locked. Am I screwed?
EDIT: It's stuck on the "Google" screen
greiland said:
I opted in for the Android N program. Received the OTA and installed but the install FAILED. Now I can't boot and can't install an image because my bootloader is locked. Am I screwed?
EDIT: It's stuck on the "Google" screen
Click to expand...
Click to collapse
Same thing happened to me. The ota failed about 1/4 of the way through. Luckily my bootloader was unlocked. After reinstalling the system image and booting up it failed a second time when installing the ota. I think the ota has some definite issues.
Try the Nexus Root Toolkit to return to stock.
mikereidis said:
Works pretty well for me so far, except for the fact that kernel support for libusb is gone, which stops my Headunit app from working over USB.
No root yet.
Recovery is replaced with stock recovery after a reboot.
There is more discussion in popular phone threads, like the one for Nexus 6p.
Click to expand...
Click to collapse
Well I don't think the kernel if it had libusb stopped supporting it.
Because this is pretty much what changed in it https://github.com/USBhost/FIRE-ICE/commit/b88667be3ca75cdfd67269e25fb43956d78004c9
the defconfig. I ripped the defconfig from the kernel image, and I applied the needed changes to my defconfig.
edit:
if you want the N defconfig here you go https://github.com/USBhost/FIRE-ICE/commit/afdf42bd4af6aa042b9d9997de91d3e60c9ccc7e
I also went the OTA route and then got stuck in a Google logo boot loop. Boot loader is locked so I am trying a factory reset. Factory reset just finished as I'm typing this. It took about 40 minutes!!!! Once again seems to be stuck on the Google logo.
Edit--
Was able to get into fastboot and install factory image! Used the Nexus Toolkit to unlock the bootloader and so far things seem to be going smoothly.
I got the OTA and it installed fine 2 bugs I have found are if you're watching YouTube and put it in split screen with hangouts and tap the hangouts screen the video will go black until you tap on the YouTube side and the other bug is that the device decided to randomly put itself in airplane mode but over all I am liking it
Sent from my Nexus 5X using Tapatalk
OTA fails for me with message stating "Android Beta Program Verification failed..." after the download. I've registered for the BETA program as normal and got the OTA notification. Same install method worked fine on my 6P. As stated above, looks like the OTA for the 9 has some issues...
USBhost said:
Well I don't think the kernel if it had libusb stopped supporting it.
Because this is pretty much what changed in it https://github.com/USBhost/FIRE-ICE/commit/b88667be3ca75cdfd67269e25fb43956d78004c9
the defconfig. I ripped the defconfig from the kernel image, and I applied the needed changes to my defconfig.
edit:
if you want the N defconfig here you go https://github.com/USBhost/FIRE-ICE/commit/afdf42bd4af6aa042b9d9997de91d3e60c9ccc7e
Click to expand...
Click to collapse
Has somebody released N kernel source ?
I don't think there is any /dev/bus/ directory, never mind /dev/bus/usb/... but I'd feel more positive about that if I had root to verify.
mikereidis said:
Has somebody released N kernel source ?
I don't think there is any /dev/bus/ directory, never mind /dev/bus/usb/... but I'd feel more positive about that if I had root to verify.
Click to expand...
Click to collapse
well Google did release the source for it but... they goofed on it
Check it out https://github.com/USBhost/FIRE-ICE/tree/android-tegra-flounder-3.10-n-preview-1
BTW my kernel works on the N preview
Couldn't flash mine, always have "missing system.img" and "unable to allocate -xxxxx bytes"... Didn't have much time, I will try again later. Do I need to come from clean stock to flash it ?
I registered my Nexus 9 for the beta and got the OTA. But it failed with an ERROR (android on it's back with a !). It then rebooted and gets stuck at the Google logo for hours. My Nexus 9 was completely stock on 6.0.1. I downloaded the factory image, but I cannot unlock the device to flash it. All guides seem to say I need to enable Developer Options and enable USB Debugging, but since I can't boot into Android, I can't go that far. Am I screwed?
naddie said:
I registered my Nexus 9 for the beta and got the OTA. But it failed with an ERROR (android on it's back with a !). It then rebooted and gets stuck at the Google logo for hours. My Nexus 9 was completely stock on 6.0.1. I downloaded the factory image, but I cannot unlock the device to flash it. All guides seem to say I need to enable Developer Options and enable USB Debugging, but since I can't boot into Android, I can't go that far. Am I screwed?
Click to expand...
Click to collapse
sorry to tell you but yep!
you can try talking to Google to see if they can fix it.
USBhost said:
sorry to tell you but yep!
you can try talking to Google to see if they can fix it.
Click to expand...
Click to collapse
So being straight laced and not rooting actually bricked my tablet? What the hell....
I'm a bit surprised there's no way to flash a factory image when the bootloader is locked. If security is a concern why not sign the factory image? Make it something we can sideload like an OTA update.
I am in the same boat!!!
naddie said:
So being straight laced and not rooting actually bricked my tablet? What the hell....
Click to expand...
Click to collapse
I am in the same situation. I figured that the software would be buggy but not actually brick my tablet. If anyone knows of a solution, I hope they post it here!! I would advise against installing this onto a Nexus 9 if anyone reading this is considering this firmware!!!
better33 said:
Couldn't flash mine, always have "missing system.img" and "unable to allocate -xxxxx bytes"... Didn't have much time, I will try again later. Do I need to come from clean stock to flash it ?
Click to expand...
Click to collapse
No, just wipe everything except internal. You have to extract the last image.sksmsksjssksm whatever zip. Then just fastboot flash each file individually.
Will I be able to recover if the Android N preview fails on my Nexus 9 by unlocking the bootloader and enabling USB debugging beforehand then install Android N preview?
kalinskym said:
Will I be able to recover if the Android N preview fails on my Nexus 9 by unlocking the bootloader and enabling USB debugging beforehand then install Android N preview?
Click to expand...
Click to collapse
In short, yes. You're basically leaving yourself a backdoor to flash a factory image should the Android N preview OTA takes a dump on you.
As my professor said to us in the laboratory: Do as I say, not as I do.
To be fair, I was hoping to do a no-wipe upgrade so I could experience Android N with all my stuff intact. I knew it was beta, but come on!

Axon 7 brick

I've spent the whole night trying to figure this out, but to no avail. Here goes...
Hey guys, so I was innocently playing around with GravityBox when I restarted my phone so some new settings would kick in, and it sends me into a bootloop. I went into TWRP Recovery, and at first factory reset my phone, hoping it would solve the problem, but it didn't, so I ended up "Formatting Data", which still didn't work. I'm kind of new to this whole flashing/rooting/ business, and I was wondering how I could fix my phone. If turned on, it stays in the booting process with the golden "Axon" letters forever. The model is the US variant, it's bootloader is unlocked via the ZTE Request Form, and it currently has TWRP as it's custom recovery. Help will be much appreciated. Also, it's on OTA B20
Edit: Alright so I've tried to flash to boot.img as well as recovery.img in twrp, but both give me an error. Strangely enough, if I wait out the Axon logo for about 5 minutes, it actually boots up, but as if it was the first time turning it on (asks you to sign in to google, wi-fi setup, fingerpring setup, etc). Another thing I noticed was that it says I only have 4gb of storage, instead of the 64 it originally came with. Every time I reset it/turn it off, it makes me set up the phone again.
Edit #2: Fixed with the help of this thread http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895 Only problem seems to be that Wi-Fi does not work. /:
I had this problem and after restoring system backup in TWRP I losted my signal WiFi Imei ....
But I have 64 GB of storage again
Отправлено с моего HTC One M8 через Tapatalk
raber111 said:
I had this problem and after restoring system backup in TWRP I losted my signal WiFi Imei ....
But I have 64 GB of storage again
Отправлено с моего HTC One M8 через Tapatalk
Click to expand...
Click to collapse
I don't have a TWRP backup to restore to ): if that's what you mean, any other solutions?
I didn't have to but I found a backup on XDA . And I don't really know if you should use it or you should wait till full stock image will release.
Отправлено с моего HTC One M8 через Tapatalk
Did you happen to try the instructions to restore to stock already, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
reddrago said:
Did you happen to try the instructions to restore to stock already, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
Click to expand...
Click to collapse
I'm in the process of doing this as of right now, thank you. Will update.
It sounds like you're going to restore to stock, so perhaps this won't help at this point, but Xposed has a "safe mode" which can be activated during boot-up and perhaps help to resolve these sorts of issues...here's a thread about it:
http://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
This once saved me when I had a boot-loop issue with a tablet a while back. Good luck!
Same boat. last day or so of newegg 14 day return. At this point my decision is between Return or Replace. No ZTE image or flashable modem file means there is no fix for this, as far as I can tell.
FYI,. I have tried all of the possible fixes offered.
Barsky said:
Same boat. last day or so of newegg 14 day return. At this point my decision is between Return or Replace. No ZTE image or flashable modem file means there is no fix for this, as far as I can tell.
FYI,. I have tried all of the possible fixes offered.
Click to expand...
Click to collapse
Newegg is 30 day return.
Sent from my FRD-L04 using Tapatalk
flyer_andy said:
It sounds like you're going to restore to stock, so perhaps this won't help at this point, but Xposed has a "safe mode" which can be activated during boot-up and perhaps help to resolve these sorts of issues...here's a thread about it:
http://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
This once saved me when I had a boot-loop issue with a tablet a while back. Good luck!
Click to expand...
Click to collapse
Actually, I managed to get it to boot up and work normal (for the most part). The only problem is, Wi-Fi doesn't work.
bricky23 said:
Newegg is 30 day return.
Sent from my FRD-L04 using Tapatalk
Click to expand...
Click to collapse
Try doing what this thread says, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
If you have any questions feel free to pm,
Pollito788 said:
Actually, I managed to get it to boot up and work normal (for the most part). The only problem is, Wi-Fi doesn't work.
Click to expand...
Click to collapse
I'm in the exact same boat. Did you ever figure out how to get wifi back?
Pollito788 said:
Try doing what this thread says, http://forum.xda-developers.com/axon-7/how-to/how-to-restore-a2017u-to-functional-t3445895
If you have any questions feel free to pm,
Click to expand...
Click to collapse
Am I missing something. that dev-host site sends me exploit installers. good thing I do nightly acronis images.
Pollito788 said:
Actually, I managed to get it to boot up and work normal (for the most part). The only problem is, Wi-Fi doesn't work.
Click to expand...
Click to collapse
Flapjack said:
I'm in the exact same boat. Did you ever figure out how to get wifi back?
Click to expand...
Click to collapse
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
peramikic said:
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
Click to expand...
Click to collapse
Uggg... I'm really frustrated now, because I got it working with tenfar's original modified boot image and rczrider's system backup. Everything was working. Of course, I didn't have root, so like and idiot, I tried to flash SuperSU 2.76. The phone stuck at the LTE screen after that. I tried re-following all my past steps, and can get the phone to boot, but it's acting crazy. I have two empty SIM icons on the taskbar (I had none when it was working fine) and the phone is very jerky and laggy. I cannot shut it down, or connect to PC easily. It will frequently reboot on its own, and I can't even power it down (it'll say "shutting down" for a few minutes, then reboot).
I eventually got it to shutdown, and repeated the "How to reset..." steps, but it's still acting crazy. I've wiped everything except for system. I'm going to try that next.
peramikic said:
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
Click to expand...
Click to collapse
Would not mind fixing this rather than shipping my packed up axon7 to newegg. Think I have a few days before it has to ship, so I am open to working on it some more.
Thanks.
---------- Post added 08-29-2016 at 12:00 AM ---------- Previous post was 08-28-2016 at 11:51 PM ----------
Flapjack said:
Uggg... I'm really frustrated now, because I got it working with tenfar's original modified boot image and rczrider's system backup. Everything was working. Of course, I didn't have root, so like and idiot, I tried to flash SuperSU 2.76. The phone stuck at the LTE screen after that. I tried re-following all my past steps, and can get the phone to boot, but it's acting crazy. I have two empty SIM icons on the taskbar (I had none when it was working fine) and the phone is very jerky and laggy. I cannot shut it down, or connect to PC easily. It will frequently reboot on its own, and I can't even power it down (it'll say "shutting down" for a few minutes, then reboot).
I eventually got it to shutdown, and repeated the "How to reset..." steps, but it's still acting crazy. I've wiped everything except for system. I'm going to try that next.
Click to expand...
Click to collapse
Try flashing the 2.65 ver over it
peramikic said:
WiFi not working is a mismatch between boot.img and /system, they have to be from the same 'set' so if you flash B20_Boot (BL unlock) boot.img, you have to flash a matching /system as well. We have a problem with numerous file version marked just B20 floating around. From what i know, this
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
is for sure the B20_Boot /system image , but i am unsure of anyone posting matching boot.img file. The one on idlekernel might be correct, since the dump came from B20_Boot BL unlocked phone, but it might have been modded. Maybe someone can post one
Click to expand...
Click to collapse
It kinda late right now but if that is what's needed I'll be uploading my boot
Image tomorrow (b20_boot),
P. S. I know for sure CM13 is just around the corner and that alone is fix for slot of you guys boot problems .
Barsky said:
Try flashing the 2.65 ver over it
Click to expand...
Click to collapse
That's the thing.... I've restored it repeatedly. All traces of 2.67 should be gone. I've completely restored it three times now.
I'm honestly thinking I'm better off returning this phone while it's still working. I wonder if something is wrong with it.
DrakenFX said:
It kinda late right now but if that is what's needed I'll be uploading my boot
Image tomorrow (b20_boot),
P. S. I know for sure CM13 is just around the corner and that alone is fix for slot of you guys boot problems .
Click to expand...
Click to collapse
tysm bro <3
DrakenFX said:
It kinda late right now but if that is what's needed I'll be uploading my boot
Image tomorrow (b20_boot),
P. S. I know for sure CM13 is just around the corner and that alone is fix for slot of you guys boot problems .
Click to expand...
Click to collapse
Brings DrakenFX some coffee and nudges him awake. :cyclops:

Screen Not Responsive After Flash ..... +

Hey,
I've been on quite a journey since I attempted to flash the Treble rom for newbies. My phone eventually ended up as DFU'd but, I brought it back to life after a following the DFU Unbrick - Disassembly guide. After doing this, the screen was not responsive to touch at all at the Welcome screen of the EDU ROM. So, my adventure continued as I took the phone apart several times again to make certain things were connected, not damaged, etc..
After flashing TWRP I concluded the screen itself must be fine because I could use TWRP using the screen/touch. I have since tried flashing several different roms, tried many combos of unlocking the bootloader (again, because I assume it was already unlocked due to the bootloader warning screen of can not check for corruption message), tried flashing bootstack and the stock rom from DrakenFX. Used MiFlash, EDM Tool to flash various items.
Each time and currently, when it boots to the Welcome screen it does not respond to touch.
Can anyone please help me with this?
Thank you!
I remember this happened to me some years ago with a different phone, and it was a bad flash.
I resolved it by flashing the stock firmware again.
What did you flash with MiFlash? Stock firmware untouched? You must do this, try with B35 untouched. Don't flash stuff with TWRP.
Untouched? Is there anything on here like that?
https://androidfilehost.com/?fid=962187416754472312 B35 A2017U
https://androidfilehost.com/?fid=746010030569960045 B10 A2017G
https://www.androidfilehost.com/?fid=818070582850490196 B14 A2017CN
Those are "untouched" system images. Replace recovery.img with a proper TWRP version before flashing:
https://androidfilehost.com/?fid=673956719939822011
bornlivedie said:
https://androidfilehost.com/?fid=962187416754472312 B35 A2017U
https://androidfilehost.com/?fid=746010030569960045 B10 A2017G
https://www.androidfilehost.com/?fid=818070582850490196 B14 A2017CN
Those are "untouched" system images. Replace recovery.img with a proper TWRP version before flashing:
https://androidfilehost.com/?fid=673956719939822011
Click to expand...
Click to collapse
Yeah, unfortunately the very first link (since I am in the USA and have a U version) is the very stock EDL version I used with MiFlash rightg after I was successful getting the phone out of DFU. I have tried flashing it twice after and still nothing.
Thank you for helping!!!
djprez said:
Yeah, unfortunately the very first link (since I am in the USA and have a U version) is the very stock EDL version I used with MiFlash rightg after I was successful getting the phone out of DFU. I have tried flashing it twice after and still nothing.
Thank you for helping!!!
Click to expand...
Click to collapse
Sad to hear that... Maybe you can try again? Who knows, with a little bit of luck...
Or try another version, like this one:
https://www.androidfilehost.com/?fid=890129502657579386
btw, did you try every single spot in your screen while in TWRP? Maybe some pins in the connector are broken and some parts work and others doesn't?
And for the sake of it, you could try discharging your battery completely.
Last thing I can think of... is to restore the stock recovery and apply the official update via sdcard:
https://www.dropbox.com/s/xy7nd252f3rcm5y/338450B3220A2017UV1.1.0B35(SD card software).zip?dl=0
It was taken from here:
https://www.zteusa.com/axon-7#support
bornlivedie said:
Sad to hear that... Maybe you can try again? Who knows, with a little bit of luck...
Or try another version, like this one:
https://www.androidfilehost.com/?fid=890129502657579386
btw, did you try every single spot in your screen while in TWRP? Maybe some pins in the connector are broken and some parts work and others doesn't?
And for the sake of it, you could try discharging your battery completely.
Last thing I can think of... is to restore the stock recovery and apply the official update via sdcard:
https://www.dropbox.com/s/xy7nd252f3rcm5y/338450B3220A2017UV1.1.0B35(SD card software).zip?dl=0
It was taken from here:
https://www.zteusa.com/axon-7#support
Click to expand...
Click to collapse
Yeah, the entire screen works perfectly in TWRP. I disassembled it several times before when I thought I may have put it back together wrong or damaged something so, the battery was removed those several times therefore, no power.
I'll try the stock above. I'm actually trying another stock rom atm --- flashing from sdcard
djprez said:
Yeah, the entire screen works perfectly in TWRP. I disassembled it several times before when I thought I may have put it back together wrong or damaged something so, the battery was removed those several times therefore, no power.
I'll try the stock above. I'm actually trying another stock rom atm --- flashing from sdcard
Click to expand...
Click to collapse
Well, EUREKA! I found I had saved the first files you were supposed to load when the Axon was first unlocked ( file name STEP_1_3-B20_FULL_OTA). Flashed it and the screen works fine. Now, I have to remember how to update it...lol I've unlocked the bootloader in Developer mode and I should be on my way..... fingers crossed.
djprez said:
Well, EUREKA! I found I had saved the first files you were supposed to load when the Axon was first unlocked ( file name STEP_1_3-B20_FULL_OTA). Flashed it and the screen works fine. Now, I have to remember how to update it...lol I've unlocked the bootloader in Developer mode and I should be on my way..... fingers crossed.
Click to expand...
Click to collapse
Strange.
Nevertheless, congratulations. Happy for you.
Well, it's great that I now know the screen/hardware is fine but, I am unable to get any further than version B20. OTA doesn't work, the other files to flash (STEP_4-B20_to_B27 and STEP_5-B27_to_B29) won't flash and get aborted due to it expecting a certain version. I've tried DrakenFX Bootstack and then Stock System and it boots to the Welcome screen but the screen is no longer responsive again.
I have been at this all day again and it's shaping up another all night too. I am so baffled!
Restore to stock firmware your phone came shipped with.After that update trough ota or sd card package and maybe dont flash Treble again,its broken
djprez said:
Well, it's great that I now know the screen/hardware is fine but, I am unable to get any further than version B20. OTA doesn't work, the other files to flash (STEP_4-B20_to_B27 and STEP_5-B27_to_B29) won't flash and get aborted due to it expecting a certain version. I've tried DrakenFX Bootstack and then Stock System and it boots to the Welcome screen but the screen is no longer responsive again.
I have been at this all day again and it's shaping up another all night too. I am so baffled!
Click to expand...
Click to collapse
i wish i had seen this sooner, because i have this same exact problem on one of my boards. it will update perfectly to any of the MM sd card update files (see rootjunkys bl unlock video, thanks @Tomsgt) but the board/phone will not retain touch functionality on anything higher than mm b29. i had lost my imei on that board, and actually swapped to another one despite eventually regaining it simply bc i wanted to be on Oreo ROMs. if you find a fix, id love to know about it. i flashed and reflashed every update, sd card versions, edl versions, and OTA updates to no avail. Nougat or above, touchscreen didnt work... mine was a gold a2017u. good luck, man. im glad im not crazy.
Sorry to bump an old(er) thread I started. I wanted to ask if anyone has found a solution to this issue yet?
I have since tried updating using OTA to Nougat and the screen doesn't respond so, I had to flash back to Marshmallow B29. Thank you to anyone who might have an idea!

Android 10 Beta T-Mobile Variant

I have tried twice on my OnePlus 6T T-Mobile variant to upgrade to the newest Open Beta. It runs the current open beta released in September just fine. But then when I do a local upgrade to the Android 10 open beta, right after it finishes installing and I press reboot, I get a message that says Build Version and HW version do not match and it ets stuck in a bootloop. To fix it, I have to use MSMDownloadTool to fix it. I have tried doing a local upgrade using a locked and unlocked bootloader and both lead to the same problem. Has anyone succesfully updated their TMo variant because i hate having to keep restoring my device?
I usually wait for a while until official Android 10 ROM for international OnePlus 6T version (and flash it via TWRP both times so I don't get any conflicts, with same copies of the OS across both slots), then I do whatever I want (I usually upgrade the bootloader and vendor this way so newer flavor of LineageOS 16 or later ROMs work best). I didn't run into hardware mismatch warning, yet I managed to successfully flash the successive OxygenOS updates meant for the international OnePlus 6T on my T-Mobile OnePlus 6T so far without seeing any UEFI bootloader warning at all. I had to be careful, I partly bricked my Google Pixel phone the last time (rendered Slot A completely unbootable by accident, so I had to figure out how to restore it the hard way, without the computer).
Sent from my OnePlus 6T using Tapatalk
bigmikey307 said:
I have tried twice on my OnePlus 6T T-Mobile variant to upgrade to the newest Open Beta. It runs the current open beta released in September just fine. But then when I do a local upgrade to the Android 10 open beta, right after it finishes installing and I press reboot, I get a message that says Build Version and HW version do not match and it ets stuck in a bootloop. To fix it, I have to use MSMDownloadTool to fix it. I have tried doing a local upgrade using a locked and unlocked bootloader and both lead to the same problem. Has anyone succesfully updated their TMo variant because i hate having to keep restoring my device?
Click to expand...
Click to collapse
Here is the solution for the moment.
I already installed it and everything works fine.
https://forum.xda-developers.com/showpost.php?p=80600661&postcount=52
ajnexus5 said:
Here is the solution for the moment.
I already installed it and everything works fine.
https://forum.xda-developers.com/showpost.php?p=80600661&postcount=52
Click to expand...
Click to collapse
I'm not interested in rooting my phone :silly: so is there any work around for unrooted users at the moment? Ty
Not yet. The fastboot ROM is pre-rooted, so there's no additional tinkering needed. Just flash the fastboot ROM and upon reboot, it's rooted. You can always jump back to the stable build when it's released next month if you'd like.
That file was deleted. Is there any other way to flash it?
jaceypoo said:
That file was deleted. Is there any other way to flash it?
Click to expand...
Click to collapse
Yes. Payload.bin decrypt and manual fastboot flash.
1-click T-mobile Android 10 for 6T:
https://drive.google.com/open?id=1jhGVmfC42UyVGDYUQhBFInjYUmZf4lxa
bradhoschar said:
Not yet. The fastboot ROM is pre-rooted, so there's no additional tinkering needed. Just flash the fastboot ROM and upon reboot, it's rooted. You can always jump back to the stable build when it's released next month if you'd like.
Click to expand...
Click to collapse
How is the Zip? I am new to the OnePlus forums do not see the least of two of 0 years ago I do so much trust that this would not happen as with P there were never problems with the V T which Vojo is some without root version?
Installed just fine, I love the new interface. BT isn't working for my Garmin watch. I guess I will have to wait for a full release for this to be fixed up.
Just a heads up to those who haven't made an actual phone call yet, Everyone I've spoken to has told me they can't hear me at all and that the quality comes out pretty garbled. Just something to look out for! If anyone has a fix for it please let us know!
chillaxnphilx said:
Just a heads up to those who haven't made an actual phone call yet, Everyone I've spoken to has told me they can't hear me at all and that the quality comes out pretty garbled. Just something to look out for! If anyone has a fix for it please let us know!
Click to expand...
Click to collapse
No issues on the T-mo fastboot ROM
Well, actually right now I cannot get into recovery. Says Qualcomm Dump. Questions? Should I try flashing TWRP?
---------- Post added at 01:06 PM ---------- Previous post was at 01:05 PM ----------
EspElement said:
Well, actually right now I cannot get into recovery. Says Qualcomm Dump. Questions? Should I try flashing TWRP?
Click to expand...
Click to collapse
I even tried to fastboot boot recovery.img
It didn't work, just sits at fastboot screen.
bradhoschar said:
No issues on the T-mo fastboot ROM
Click to expand...
Click to collapse
You haven't used the gyro, proximity sensor, specialized fonts, or emojis yet.
The OB1 creates a new partition called "reserve". This partition is not present on the Tmobile variants and its not created during install. There are issues with the Tmobile build, and its going to stay that way until an updated MSMtool comes out, Tmobile updates to A10, or some maniac actually goes through and fixes every single symlink that's broken.
OP ran out of space on system partition, so they're solution was to create a new partition and symlink everything from there to system.
hartleyshc said:
You haven't used the gyro, proximity sensor, specialized fonts, or emojis yet.
The OB1 creates a new partition called "reserve". This partition is not present on the Tmobile variants and its not created during install. There are issues with the Tmobile build, and its going to stay that way until an updated MSMtool comes out, Tmobile updates to A10, or some maniac actually goes through and fixes every single symlink that's broken.
OP ran out of space on system partition, so they're solution was to create a new partition and symlink everything from there to system.
Click to expand...
Click to collapse
Gyro and prox works for me.
Emojis work after magisk module flash.
chillaxnphilx said:
Just a heads up to those who haven't made an actual phone call yet, Everyone I've spoken to has told me they can't hear me at all and that the quality comes out pretty garbled. Just something to look out for! If anyone has a fix for it please let us know!
Click to expand...
Click to collapse
I have heard of this from multiuple people in the forums and it is also occuring with the Hydrogen Beta for Android 10. Thats where I first saw it. I dont know if my phone is affected.
hartleyshc said:
You haven't used the gyro, proximity sensor, specialized fonts, or emojis yet.
The OB1 creates a new partition called "reserve". This partition is not present on the Tmobile variants and its not created during install. There are issues with the Tmobile build, and its going to stay that way until an updated MSMtool comes out, Tmobile updates to A10, or some maniac actually goes through and fixes every single symlink that's broken.
OP ran out of space on system partition, so they're solution was to create a new partition and symlink everything from there to system.
Click to expand...
Click to collapse
Gyro and Prox are working fine for me. Dont know about fonts and emoji's as I dont use them. Everything "else" seems fine at this point.
Scott said:
I have heard of this from multiuple people in the forums and it is also occuring with the Hydrogen Beta for Android 10. Thats where I first saw it. I dont know if my phone is affected.
Patching the boot.img with magisk canary is somehow breaking the symlinks to reserve.img (possibly others). reserve.img is where the extra fonts, oneplus specific apks (like weather, launcher icons, etc) are stored. If you wanna check, flip your font to oneplus slate, if its in italics, its hosed. If your font is looking at special characters and your getting boxes with X's in them, your hosed.
only way to fix is a clean flash, and use magisk stable manager to patch your boot.img if your rooting.
Click to expand...
Click to collapse
aer0zer0 said:
Patching the boot.img with magisk canary is somehow breaking the symlinks to reserve.img (possibly others). reserve.img is where the extra fonts, oneplus specific apks (like weather, launcher icons, etc) are stored. If you wanna check, flip your font to oneplus slate, if its in italics, its hosed. If your font is looking at special characters and your getting boxes with X's in them, your hosed.
only way to fix is a clean flash, and use magisk stable manager to patch your boot.img if your rooting.
Click to expand...
Click to collapse
Ok, yeah, I do have the italic font. I thought that was just "new".
So basically, dont root it and it will be fine?
Scott said:
Ok, yeah, I do have the italic font. I thought that was just "new".
So basically, dont root it and it will be fine?
Click to expand...
Click to collapse
root your boot.img using magisk 20.0 stable.
but your going to need to reflash? are you tmob or stable?
bradhoschar said:
1-click T-mobile Android 10 for 6T:
https://drive.google.com/open?id=1jhGVmfC42UyVGDYUQhBFInjYUmZf4lxa
Click to expand...
Click to collapse
is this the pre rooted version
Sent from my ONEPLUS A6013 using Tapatalk

Didn't realize I was upgrading to Android 11, magisk_patched.img bootloops, need help

When I downloaded the lasted OTA update for my OnePlus 8 Pro I thought it was just another hotfix and didn't realize it was a Big Deal Android 11 update. I tried using the normal OTA upgrade processed and kinda screwed myself.
After trying to install in the inactive slot the way I normally upgrade OTA, I ended up bootlooping. So I downloaded the recovery image and tried patching Magisk the long adb way. It wasn't until later that I realized I had to be on the beta channel. I didn't know you needed to disable modules when you upgrade to Android 11, so they might still be in play, but I don't know how to check. I've tried a bunch of stuff without much luck. Here's where I'm at now:
1) Bootloader is unlocked
2) I can get into Recovery Mode fine
3) I can flash the default/unpatched boot.img for my build and boot up fine, but there's no root, and wifi doesn't work and cellular data is really flakey (even though I normally have fine reception here).
4) From an unpatched boot.img I switched Magisk Manager to the beta channel and installed v21.1. Then I patched boot.img to make a new magisk_patched.img from the beta channel.
5) When I try to fastboot flash magisk_patched.img to slot A I bootloop.
6) When I try to fastboot boot magisk_patched.img I get stuck on the red dot with 2 white dots orbiting it for seemingly forever.
7) I think something is wrong in my slot B because I mostly just get stuck in fastboot. This might be an unrelated problem from a while back though.
8) When I try to run adb wait-for-device shell magisk --remove-modules, I just get an error message about magisk not being found.
What can I do to get back to a rooted working patched magisk without wiping all my data and starting from scratch?
I've honestly never seen anyone do this before so I'm curious as to how you'll recover from this
My thought are MSM but you may be able to boot. Problem is the magisk modules are still in play.
The adb command may not work for removal as you may not get that far.
Did the installation go through ok? It was just booting that failed?
Could maybe try to wipe system via recovery and go from there.
I'm not too sure buddy.
Keep us posted how u get on.
Edit: Try to boot the boot img.
What model are you on? BA ? I have the boot images in my guides in the guides section. Feel free to take what you need.
dladz said:
My thought are MSM but you may be able to boot. Problem is the magisk modules are still in play.
Click to expand...
Click to collapse
What is MSM?
dladz said:
Did the installation go through ok? It was just booting that failed?
Click to expand...
Click to collapse
You mean the result of fastboot flash magisk_patched.img? Yeah, that has finished fine every time. I'm either stuck bootlooping or booting up never finishes.
dladz said:
Could maybe try to wipe system via recovery and go from there.
Click to expand...
Click to collapse
Doesn't that delete all my data? I've only tried wiping the cache so far.
dladz said:
Edit: Try to boot the boot img.
Click to expand...
Click to collapse
Do you mean fastboot boot magisk_patched.img? That just spins forever and never finishes booting.
Flashing back to the unpatched boot.img boots up fine, but my wifi won't turn on and my cellular data is flakey (even though I usually have fine reception here).
dladz said:
What model are you on? BA ? I have the boot images in my guides in the guides section. Feel free to take what you need.
Click to expand...
Click to collapse
I have the US hardware, so I extracted the boot.img from 11.IN21AA, which was the same number that showed up after the OTA was applied.
I dunno, I tried a bunch of different stuff, ended up bricking it. Restored it with MSM to Android 11, then unlocked the bootloader, and tried to flash a fresh magisk_patched.img and it refused to boot in the same way, even though everything was completely fresh.
Are we sure the Magisk beta channel is working right now?
Ecna said:
I dunno, I tried a bunch of different stuff, ended up bricking it. Restored it with MSM to Android 11, then unlocked the bootloader, and tried to flash a fresh magisk_patched.img and it refused to boot in the same way, even though everything was completely fresh.
Are we sure the Magisk beta channel is working right now?
Click to expand...
Click to collapse
There hasn't been anyone stating issues.
Are you using lucky patcher?
dladz said:
There hasn't been anyone stating issues.
Are you using lucky patcher?
Click to expand...
Click to collapse
I don't know what lucky patcher is, so I guess not?
Turns out the wifi problem was happening on stock anyway. And EdXposed doesn't support 11 yet either. So I flashed back to 10.5.13 before bothering to set up all my apps. I'm gonna wait a bit longer for until 11 is more ripe.
Ecna said:
I don't know what lucky patcher is, so I guess not?
Turns out the wifi problem was happening on stock anyway. And EdXposed doesn't support 11 yet either. So I flashed back to 10.5.13 before bothering to set up all my apps. I'm gonna wait a bit longer for until 11 is more ripe.
Click to expand...
Click to collapse
Ah ok, that's fine if you don't know what lucky patcher is then that's a good thing
Yes, that patched boot image failed me. Can't boot. Can't find stock to flash. Bumbed.
dladz said:
Ah ok, that's fine if you don't know what lucky patcher is then that's a good thing
Click to expand...
Click to collapse
Hi dladz, can you please give me more info on lucky patcher and how it could affect things. I'm an avid lucky patcher user, and recently had issues with phone not booting, had to do a factory reset. (I wonder if lucky patcher was some how the culprit)
hbhorat said:
Hi dladz, can you please give me more info on lucky patcher and how it could affect things. I'm an avid lucky patcher user, and recently had issues with phone not booting, had to do a factory reset. (I wonder if lucky patcher was some how the culprit)
Click to expand...
Click to collapse
Don't know if you know this or not but you can't even discuss LP on XDA so I'm afraid I can't..
All I know is that it's dodgier than Donald trump's hair and should be avoided like an old woman's waffle.
If you've had problems and lucky patcher was installed that would be top of my list of culprits.
Bootloops, corruption, force closes to name but a few issues, it probably mines for coin using your phone's processor when it's not in use and god only knows what it does with your data, if that's the price of free apps? Id rather pay for them, my data is with more than any app.
Soz mate, that's all I can offer.
Just avoid it.. :good:

Categories

Resources