1) image search in Google won't let you go to original image or go to webpage. Same search in chrome works fine
2) Clicking on links in Slickdeals causes the app to crash.
Is anyone experiencing this? Is there any issues you guys would like to confirm as well?
Sent from my Pixel XL using Tapatalk
biggiestuff said:
1) image search in Google won't let you go to original image or go to webpage. Same search in chrome works fine
2) Clicking on links in Slickdeals causes the app to crash.
Is anyone experiencing this? Is there any issues you guys would like to confirm as well?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I tried the image search and I can open the original image and go to the website without issue. I installed the Slick Deals app and clicking on links also works fine.
airmaxx23 said:
I tried the image search and I can open the original image and go to the website without issue. I installed the Slick Deals app and clicking on links also works fine.
Click to expand...
Click to collapse
Thanks. Something must have gotten jacked up for me. The first issue having a Verizon bootloader locked phone has just come to fruition. I can't just flash the system to bring things back without wiping.
Sent from my Pixel XL using Tapatalk
biggiestuff said:
Thanks. Something must have gotten jacked up for me. The first issue having a Verizon bootloader locked phone has just come to fruition. I can't just flash the system to bring things back without wiping.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I'm also on VZW but with an unlocked bootloader. You can flash the system with fastboot or flash the whole thing with the -w removed from the .bat file and it won't wipe anything.
airmaxx23 said:
I'm also on VZW but with an unlocked bootloader. You can flash the system with fastboot or flash the whole thing with the -w removed from the .bat file and it won't wipe anything.
Click to expand...
Click to collapse
Unfortunately I'm locked. I thought this time around I wouldn't need an unlocked bootloader.
Sent from my Pixel XL using Tapatalk
I left the google beta and went back to stable google and my issues with the "visit webpage" and "view original image" are gone. I'm still working on that slickdeals app link issue.
EDIT: I take that back. the factory version of Google works just fine but when I update (non-beta) it still happens.
My Google app is entirely broken. As soon as it tries to give any result, it freezes, FCs and crashes.
Sent from my Pixel XL using XDA-Developers mobile app
BCSC said:
My Google app is entirely broken. As soon as it tries to give any result, it freezes, FCs and crashes.
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Was this before or after January patches?
Okay, I give up. works perfectly in Safe mode. I've tried uninstalling nearly every app on my phone to see which one is causing it. I might as well factory reset.
I hate the YouTube app getting frozen video but audio Continues that has been on my pixel XL since the beginning
Chrome is really stuttering here and there after this update. Or maybe it behaved like that all along can't say. But Chrome isn't smooth at all!
I finally uninstalled enough apps. I think it's related to possibly one of the Daydream apps. I'm going to slowly start reinstalling them but I'm back to normal on everything now
Sent from my Pixel XL using Tapatalk
biggiestuff said:
Was this before or after January patches?
Click to expand...
Click to collapse
Im almost certain its from after the patch. I use the app multiple times a day and didnt have this issue before the 3rd.
Sent from my Pixel XL using XDA-Developers Legacy app
BCSC said:
Im almost certain its from after the patch. I use the app multiple times a day and didnt have this issue before the 3rd.
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Mine was doing that as well while I was troubleshooting. In safe mode it and fine. Try that. If it works in safe mode then start uninstalling apps like I did. Still scared to install daydream apps as I think that was the cause of my issue.
Sent from my Pixel XL using Tapatalk
After the update, I randomly get rather loud static noise (just like when a TV is seeking a channel) coming from my headphones even if nothing is playing. Once it starts, it can't be stopped until I reboot the phone.
biggiestuff said:
Thanks. Something must have gotten jacked up for me. The first issue having a Verizon bootloader locked phone has just come to fruition. I can't just flash the system to bring things back without wiping.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
While you can't use the fastboot images you can use the full OTA images.
Download current file from:
https://developers.google.com/android/ota
Boot device into recovery
Select sideload from adb
adb sideload <updatefile>
This basically the same as the full factory image but does not require an unlocked bootloader and does NOT wipe your device.
arcanexvi said:
While you can't use the fastboot images you can use the full OTA images.
Download current file from:
https://developers.google.com/android/ota
Boot device into recovery
Select sideload from adb
adb sideload <updatefile>
This basically the same as the full factory image but does not require an unlocked bootloader and does NOT wipe your device.
Click to expand...
Click to collapse
That's a good thought. If the OTA is small would it contain the system.img to restore it from scratch?
Sent from my Pixel XL using Tapatalk
biggiestuff said:
That's a good thought. If the OTA is small would it contain the system.img to restore it from scratch?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
These are not traditional 50 meg OTA files. They're in the 500 meg to 1 gig range. They're full images. Period. This is the reason they were created. To flash a complete image to a locked device.
Sent from my Pixel XL using Tapatalk
Related
I'm breaking my cherry here. Long time follower, reader, but never signed up for XDA. Now I need you!
VZW Droid Incredible 2. Stock rom. Rooted. Tried to download a short artistic video from an app I got off of Snappz (not sure if the video is going to internal storage or SD.) Anyways, thing keeps saying 'download unsuccessful.' I don't care about the download anymore. It won't stop trying to download this video. I've tried a reboot, I force stopped the process that I got the artistic video from. Out of ideas. Tried searching google and XDA. No luck. How do I stop this thing?
Edit: Deleted the app that was causing the issue. Don't know why I didn't think of that first.
Uhnaan said:
I'm breaking my cherry here. Long time follower, reader, but never signed up for XDA. Now I need you!
VZW Droid Incredible 2. Stock rom. Rooted. Tried to download a short artistic video from an app I got off of Snappz (not sure if the video is going to internal storage or SD.) Anyways, thing keeps saying 'download unsuccessful.' I don't care about the download anymore. It won't stop trying to download this video. I've tried a reboot, I force stopped the process that I got the artistic video from. Out of ideas. Tried searching google and XDA. No luck. How do I stop this thing?
Click to expand...
Click to collapse
Try going into downloads and cancelling it? Reboot not stopping it is odd, if that doesn't work kill and clear data on the downloads app.
Edit: also, welcome to xda
Sent from my Incredible 2 using Tapatalk 2
prototype7 said:
Try going into downloads and cancelling it? Reboot not stopping it is odd, if that doesn't work kill and clear data on the downloads app.
Click to expand...
Click to collapse
Hmm. This download isn't under the downloads app dealy. Killed and cleared data on downloads. Rebooted. Still trying to download this file.
Uhnaan said:
Hmm. This download isn't under the downloads app dealy. Killed and cleared data on downloads. Rebooted. Still trying to download this file.
Click to expand...
Click to collapse
Try killing the app that you were downloading file from and clearing data
Sent from whatever ROM is in the chamber
Still no worky. Anybody?
Sent via his noodly appendages
You could always do the usual wipe everything, reflash your ROM trick
Sent from whatever ROM is in the chamber
bsmitty83 said:
You could always do the usual wipe everything, reflash your ROM
Click to expand...
Click to collapse
I could reformat my hard drive and reinstall Windows every time I get some malware too but obviously that's a last resort.
Sent via his noodly appendages
Reflashing a ROM is different than formatting a hard drive , but hey if you can find a solution better than a 5 min reflash cuz I dont know what else you can do to stop the download that won't download, wish I could have been more help
Sent from whatever ROM is in the chamber
Did you try connecting to wifi to see if it will finish that way? Or if you are on wifi now did you try using the mobile network?
Sent from my ICS Dinc2
cstone1991 said:
Did you try connecting to wifi to see if it will finish that way? Or if you are on wifi now did you try using the mobile network?
Click to expand...
Click to collapse
Fails on both.
Sent via his noodly appendages
Uhnaan said:
Fails on both.
Sent via his noodly appendages
Click to expand...
Click to collapse
Could be server issues with the app or the app itself. It possibly makes a folder with the app name or something on the SD card that it saves to.
Sent from Kangdemnation
CondemnedSoul said:
Could be server issues with the app or the app itself. It possibly makes a folder with the app name or something on the SD card that it saves to.
Click to expand...
Click to collapse
The app says that it saves to SD/downloadmanager. The folder was empty. The app didn't have a folder I could easily identify either. Didn't even think to try uninstalling the app (slaps palm against forehead.) So I did that. We'll see.
Sent via his noodly appendages
I got the notification that the kitkat update was downloaded but after reading there is no flash support I have absolutely no interest in installibg this update. I got a nexus 7 over an iPad solely because I could use flash which is the only game in town on many sites I visit regularly. I got rid of the notification by unchecking notifications in the framework app but I'm worried if my tablet reboots/powers off that I will forced to update before it starts up. Please tell me this is not the case? Also is there a way to delete the download period, even if it's not installed I'd rather it not eating up limited memory that I have.
Flash should work in dolphin
godutch said:
Flash should work in dolphin
Click to expand...
Click to collapse
It won't, Google replaced the fast and compatible WebKit engine with the slow as hell and flash incompatible chromium webview...
Gesendet von meinem Nexus 7 mit Tapatalk 4
deezid said:
It won't, Google replaced the fast and compatible WebKit engine with the slow as hell and flash incompatible chromium webview...
Gesendet von meinem Nexus 7 mit Tapatalk 4
Click to expand...
Click to collapse
Dolphin use their own engine, if flash does not work on KitKat install dolphin jetpack and choose that as your rendering engine in dolphin settings
godutch said:
Flash should work in dolphin
Click to expand...
Click to collapse
Not from what I've read, read on this site an official statement from dolphin saying flash wasn't supported on 4.4. Besides I find that dolphin's flash support is not always the best, i like having a few browsers because I find certain browsers handle certain sites flash better. My biggest concern is if I power the device off will I be forced to update since my nexus 7 has already downloaded but not installed the update. Im perfectly fine with 4.3 except the touch issues when the n7 is not plugged in or in my hands....grounding issue I believe?
godutch said:
Dolphin use their own engine
Click to expand...
Click to collapse
Maybe, but WebKit is removed anyway...
https://dolphinbrowser.desk.com/cus...-in-android-4-4-how-do-i-enable-flash-player-
Gesendet von meinem Nexus 7 mit Tapatalk 4
Also if I did a factory reset would that force me to 4.4?
northernassassin said:
Also if I did a factory reset would that force me to 4.4?
Click to expand...
Click to collapse
Nope...
Sent from my Nexus 7 using xda premium
northernassassin said:
I got the notification that the kitkat update was downloaded but after reading there is no flash support I have absolutely no interest in installibg this update. I got a nexus 7 over an iPad solely because I could use flash which is the only game in town on many sites I visit regularly. I got rid of the notification by unchecking notifications in the framework app but I'm worried if my tablet reboots/powers off that I will forced to update before it starts up. Please tell me this is not the case? Also is there a way to delete the download period, even if it's not installed I'd rather it not eating up limited memory that I have.
Click to expand...
Click to collapse
The one way that I know of how to stop an OTA update first requires that you be rooted. If so you can use an app called Autostarts. Open the app go to Menu click on "Group by application." Scroll down to "Google Services Framework" and click on that. At the top you will see 4 "After Startup" entries. Click on the third "After Startup" entry from the top. In the popup window you should see "SystemUpdateService$Receiver" in the description, that's the one you want to disable. To delete the update I'm not 100% positive but I'm thinking if you delete the cache from Google Services Framework that will delete the update. Or Settings/Storage and click on "Cached data." Honestly, those are guesses because it's been a longtime since I've had to do that! SD Maid Pro will delete the update also but that app also requires root. After flashing the 4.4 factory image when it first came out I went back to 4.3 until I find a replacement for the AOSP Browser, damn it google!
Edit: Decided three weeks ago to give Dolphin another try, installed on my N5 with a hacked version of the flash player and it's working great! Used the factory image to flash 4.4.2 on the N7 and installed Dolphin Browser which now has the Jetpack built-in and it works well! Dolphin Browser with hacked flash player.
northernassassin said:
Not from what I've read, read on this site an official statement from dolphin saying flash wasn't supported on 4.4. Besides I find that dolphin's flash support is not always the best, i like having a few browsers because I find certain browsers handle certain sites flash better. My biggest concern is if I power the device off will I be forced to update since my nexus 7 has already downloaded but not installed the update. Im perfectly fine with 4.3 except the touch issues when the n7 is not plugged in or in my hands....grounding issue I believe?
Click to expand...
Click to collapse
I guess I misread the changelog
I'm still not clear as to whether I can power the device off safely without itnforcing me upgrade. I'd really hat to brick my n7 by losing flash support. Also where exactly is the update located so I could possible erase it?
northernassassin said:
I'm still not clear as to whether I can power the device off safely without itnforcing me upgrade. I'd really hat to brick my n7 by losing flash support. Also where exactly is the update located so I could possible erase it?
Click to expand...
Click to collapse
It's the zip file in /cache. It will reappear though. Rename /system/etc/security/otacerts.zip. And then don't go into the updates screen again, it will trigger the download which is several hundred megabytes once more. You need to be rooted.
I used the method posted here:
http://forum.xda-developers.com/showthread.php?t=2249350
You need to have root access, but it's worked for me so far.
airberger said:
I used the method posted here:
http://forum.xda-developers.com/showthread.php?t=2249350
You need to have root access, but it's worked for me so far.
Click to expand...
Click to collapse
Indeed, just installed this and after a reboot, the prompt has gone away and it tells me the system is up to date. Thanks. And another demonstration that people don't come here simply to get hold of custom roms!
Thanks for all the answers but nobody has yet to give a straight forward answer as to whether I will be forced to update if I reboot my n7. Sometimes I'm forced to reboot when I have a hang up and I'd hate to think when that day comes I'm going to be forced to update to kitkat. I'm also not rooted and would like to stay that way. I know to many of you it seems quite easy but everything I've read makes it seem very daunting and confusing. Kernels, bootloaders, Roms, flashing....its a lot more than I thought it would be when I went android.
northernassassin said:
Thanks for all the answers but nobody has yet to give a straight forward answer as to whether I will be forced to update if I reboot my n7. Sometimes I'm forced to reboot when I have a hang up and I'd hate to think when that day comes I'm going to be forced to update to kitkat. I'm also not rooted and would like to stay that way. I know to many of you it seems quite easy but everything I've read makes it seem very daunting and confusing. Kernels, bootloaders, Roms, flashing....its a lot more than I thought it would be when I went android.
Click to expand...
Click to collapse
I have rebooted many times while the update notification was present and never had the upgrade automatically applied.
I haven't rebooted into recovery though so I cannot say if what I said holds if you do that.
For me, I'd just add an empty line to /system/build.prop
It is an empty line so it is assured not to change any behavior and every OTA update will try and patch build.prop at which point it does a SHA1 checksum compare, finds your current build.prop has been modified, and stops the OTA before it even starts modifying a single file.
This assures you that if by accident you select the OTA to install, it won't actually do anything.
You can do similar things with other files, I just chose build.prop as an easy example.
northernassassin said:
Thanks for all the answers but nobody has yet to give a straight forward answer as to whether I will be forced to update if I reboot my n7. Sometimes I'm forced to reboot when I have a hang up and I'd hate to think when that day comes I'm going to be forced to update to kitkat. I'm also not rooted and would like to stay that way. I know to many of you it seems quite easy but everything I've read makes it seem very daunting and confusing. Kernels, bootloaders, Roms, flashing....its a lot more than I thought it would be when I went android.
Click to expand...
Click to collapse
If you take your time and read instructions carefully its very easy to root a Nexus 7. Either way, why don't you just reboot it and see if it goes to 4.4 and then do a factory reset. That should bring you back to your out of box jelly bean. Of course you'd lose your data but you can back that all up.
Sent from my Nexus 7 using Tapatalk
I deleted the update from /cache and got rid of the notification but if I go to system,about device,updates it still tells me the update is "downloaded and verified". How can I make it realize the update is no longer there?
northernassassin said:
I got the notification that the kitkat update was downloaded but after reading there is no flash support I have absolutely no interest in installibg this update. I got a nexus 7 over an iPad solely because I could use flash which is the only game in town on many sites I visit regularly. I got rid of the notification by unchecking notifications in the framework app but I'm worried if my tablet reboots/powers off that I will forced to update before it starts up. Please tell me this is not the case? Also is there a way to delete the download period, even if it's not installed I'd rather it not eating up limited memory that I have.
Click to expand...
Click to collapse
Flash now works on kitkat in dolphin: http://forum.xda-developers.com/showthread.php?t=2548001
wantabe said:
The one way that I know of how to stop an OTA update first requires that you be rooted. If so you can use an app called Autostarts. Open the app go to Menu click on "Group by application." Scroll down to "Google Services Framework" and click on that. At the top you will see 4 "After Startup" entries. Click on the third "After Startup" entry from the top. In the popup window you should see "SystemUpdateService$Receiver" in the description, that's the one you want to disable. To delete the update I'm not 100% positive but I'm thinking if you delete the cache from Google Services Framework that will delete the update. Or Settings/Storage and click on "Cached data." Honestly, those are guesses because it's been a longtime since I've had to do that! SD Maid Pro will delete the update also but that app also requires root. After flashing the 4.4 factory image when it first came out I went back to 4.3 until I find a replacement for the AOSP Browser, damn it google!
Click to expand...
Click to collapse
Hello, I did that ^^^^^^^^^^ using autostarts and checked it several times to be sure I had it correct.
All seemed good, except today an update from VZW went through on me and I didn't want it to. I looked in the cache dir and nothing was in there, yet the phone kept saying it wanted to install the update. I kept telling it not right now, but after awhile it had a mind of it's own and installed/updated anyhow. My VZW GS4 went from MJ7 to MK2 not even sure what changes it made, I'm still on JB 4.3 and I don't want KitKat 4.4
I don't understand how the update came through and where it was d/l to, I checked yet again and the "SystemUpdateService$Receiver" is disabled, exactly as shown in your pics. The broke my Root, but I still showed custom when it re-booted, so it wasn't too hard to establish Root again. Now I'm very worried that sooner or later they are going to push/force KitKat 4.4 to the S4 and I don't want it; I should have a choice to not accept it, it's my device that I paid for
Any ideas on this before KK 4.4 bites me?
Thanks
Good Evening,
So I failed at rooting my device last night so I took everything back to what I assume is factory reset. After the factory rest my play store would show the tablet 101 and all the apps optimized for tablets. Now when I go in there I do not see the buttons. I have not made any changes to my tablet. Has anyone else encountered this?
Simply flash the stock rom and everything will be fine
Taimoor166 said:
Simply flash the stock rom and everything will be fine
Click to expand...
Click to collapse
I did that, I am back to stock, unrooted and locked. Still no go.
birish21 said:
I did that, I am back to stock, unrooted and locked. Still no go.
Click to expand...
Click to collapse
Try going into settings deleting your Google account. After you reenter the account Google play *should* act normal.
oldsoldier2003 said:
Try going into settings deleting your Google account. After you reenter the account Google play *should* act normal.
Click to expand...
Click to collapse
And if that fails you might be able to use one of the apps that spoofs your device's capabilities to the play store, but I think "fixing" it is a better option.
Sent from my Nexus 7 using XDA Premium HD app
Back on Oreo, all we had to do was bring the Framework-res__auto_generated.apm from the Pixel 2 (or Pixel 2 XL) and install it in System/vendor/overlay. Since we don't have root (yet) for P, is there any other way to do it? I tried via TWRP (ADB in TWRP and making a flashable zip) but I'm honestly not extremely experienced with this. Via TWRP I can't get system/vendor/overlay to show, and putting the APK in Vendor/overlay doesn't seem to activate it. Any ideas, or just wait for root?
YTSec said:
Back on Oreo, all we had to do was bring the Framework-res__auto_generated.apm from the Pixel 2 (or Pixel 2 XL) and install it in System/vendor/overlay. Since we don't have root (yet) for P, is there any other way to do it? I tried via TWRP (ADB in TWRP and making a flashable zip) but I'm honestly not extremely experienced with this. Via TWRP I can't get system/vendor/overlay to show, and putting the APK in Vendor/overlay doesn't seem to activate it. Any ideas, or just wait for root?
Click to expand...
Click to collapse
Looks like root is working sorta with magisk, just an issue with magisk manager. You might be able to get unrestricted root access to a file explorer app and compete your task. Let me know how it goes because id like to get AOD working too :good:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/page543
Jackaroop said:
Looks like root is working sorta with magisk, just an issue with magisk manager. You might be able to get unrestricted root access to a file explorer app and compete your task. Let me know how it goes because id like to get AOD working too :good:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/page543
Click to expand...
Click to collapse
Trying that now, I'll update if it works out.
YTSec said:
Trying that now, I'll update if it works out.
Click to expand...
Click to collapse
Confirmed working!
YTSec said:
Confirmed working!
Click to expand...
Click to collapse
Steps please and thanks.
Do you have the framework APK?
---------- Post added at 11:59 PM ---------- Previous post was at 11:57 PM ----------
muppetmaster916 said:
Steps please and thanks.
Click to expand...
Click to collapse
Read that area of the thread
https://forum.xda-developers.com/pi...firehound-v4-1-pixel-xl-t3744866/post75492280
To get this working, flash Magisk 16 via TWRP, boot up and use a file manager (I used ES file manager) to move the APK here to system/vendor/overlay overwrite the original. The phone will either reboot, or systemui will crash, when you get back in, go into the file manager again and set the correct permissions.
Make sure you remove your passwords, just incase something goes wrong while installing it.
YTSec said:
To get this working, flash Magisk 16 via TWRP, boot up and use a file manager (I used ES file manager) to move the APK here to system/vendor/overlay overwrite the original. The phone will either reboot, or systemui will crash, when you get back in, go into the file manager again and set the correct permissions.
Make sure you remove your passwords, just incase something goes wrong while installing it.
Click to expand...
Click to collapse
How do we install the burn in protection? Sorry for bugging you I've been googling for hours and you're the only person who seems to know how to do this or that this is possible.
SubjectGinger said:
How do we install the burn in protection? Sorry for bugging you I've been googling for hours and you're the only person who seems to know how to do this or that this is possible.
Click to expand...
Click to collapse
I took a screen recording for 20 mins and skipped around in the recording, the charge level, notifications, and clock all move around slowly. So it seems to be enabled by default.
YTSec said:
I took a screen recording for 20 mins and skipped around in the recording, the charge level, notifications, and clock all move around slowly. So it seems to be enabled by default.
Click to expand...
Click to collapse
Awesome, thanks! I tried installing it but now all the apps are crashing and I can't get back into my file manager to set the correct permissions, it crashes too. Is there a way to get the file manager to work? I'm using Solid Explorer on 8.1
SubjectGinger said:
Awesome, thanks! I tried installing it but now all the apps are crashing and I can't get back into my file manager to set the correct permissions, it crashes too. Is there a way to get the file manager to work? I'm using Solid Explorer on 8.1
Click to expand...
Click to collapse
If you are on 8.1, you need to use the APK extracted from a 8.1 system IMG for the Pixel 2 or Pixel XL 2. As for the file manager, try Amaze, I used it when ES was crashing non-stop.
YTSec said:
If you are on 8.1, you need to use the APK extracted from a 8.1 system IMG for the Pixel 2 or Pixel XL 2. As for the file manager, try Amaze, I used it when ES was crashing non-stop.
Click to expand...
Click to collapse
Yeah I was, I used the 8.1 Feb 2018 file you provided here. I'll give that a try next, installing the March security update to try and fix the crashing
SubjectGinger said:
Yeah I was, I used the 8.1 Feb 2018 file you provided here. I'll give that a try next, installing the March security update to try and fix the crashing
Click to expand...
Click to collapse
I provided the one for Android P DP1 here, not 8.1. I put the February one in the foreground ROM thread I think though.
YTSec said:
I provided the one for Android P DP1 here, not 8.1. I put the February one in the foreground ROM thread I think though.
Click to expand...
Click to collapse
Yeah the one from the foreground thread is the one I used. This might be a dumb question but how did you open the system image from the pixel 2 factory image to get the framework file? I can't open the .img as an archive and it fails to mount on both windows and Mac saying it's a corrupted image (downloaded straight from Google's site)
SubjectGinger said:
Yeah the one from the foreground thread is the one I used. This might be a dumb question but how did you open the system image from the pixel 2 factory image to get the framework file? I can't open the .img as an archive and it fails to mount on both windows and Mac saying it's a corrupted image (downloaded straight from Google's site)
Click to expand...
Click to collapse
Honestly it's a pain, I installed Ubuntu via virtual box, and went through a extraction process. https://forum.xda-developers.com/nexus-5x/general/guide-how-to-extract-nexus-factory-image-t3562665
YTSec said:
Honestly it's a pain, I installed Ubuntu via virtual box, and went through a extraction process. https://forum.xda-developers.com/nexus-5x/general/guide-how-to-extract-nexus-factory-image-t3562665
Click to expand...
Click to collapse
I went through that link, installed the extractor for Windows and tested it with the March 8.1 for Sailfish. Worked flawlessly. Download the March 8.1 for Walleye, "imgextractor has stopped working" and only extracts about 1/4 of the system img. You weren't kidding it really is a pain
SubjectGinger said:
I went through that link, installed the extractor for Windows and tested it with the March 8.1 for Sailfish. Worked flawlessly. Download the March 8.1 for Walleye, "imgextractor has stopped working" and only extracts about 1/4 of the system img. You weren't kidding it really is a pain
Click to expand...
Click to collapse
It doesn't work on windows, needs to be Linux. Try installing it in a virtual machine, only way I was able to get it working.
Here's the 8.1 March 2018 apk from Pixel 2 XL
reddv1 said:
Here's the 8.1 March 2018 apk from Pixel 2 XL
Click to expand...
Click to collapse
I really appreciate the help, but I have a Pixel 1 (non-xl)
Any chance I could get you to post the March 2018 from the Pixel 2 non-xl?
I've been trying to get this system image extractor to work and even on Linux am running into issues.
Anyways, if not no worries but I'd be very thankful if you could find the time!
SubjectGinger said:
I really appreciate the help, but I have a Pixel 1 (non-xl)
Any chance I could get you to post the March 2018 from the Pixel 2 non-xl?
I've been trying to get this system image extractor to work and even on Linux am running into issues.
Anyways, if not no worries but I'd be very thankful if you could find the time!
Click to expand...
Click to collapse
I don't think it's much different honestly, it SHOULD still work the same. The original XL and 2 XL are significantly different and it works fine, I have also used the APK from the normal Pixel 2 on my XL with no issues.
FIRST THING FIRST
EVEN IF YOUR PERSIST IS ALREADY BROKEN AND FINGERPRINT DOES NOT WORK.
BACK UP YOUR PERSIST.IMG BEFORE YOU PERFORM THIS GUIDE, IT IS SUPER EASY TO MESS UP YOUR CALIBRATIONS IN THIS MODE.
In a root explorer of your choice go to /mnt/vendor/persist/engineermode/
You'll see a file that is called 'engineermode_config' open that file with a text editor.
Code:
[SIZE="5"][B]encrypt_app=true[/B][/SIZE]
[SIZE="5"][B]encrypt_adb=true[/B][/SIZE]
rc4_key=*************************************************************************************************************************************************************************************************************************************************
imei=*******************
last_download_time=*******************
encrypt_log=true
Switch the two lines to "false"
Code:
[SIZE="5"][B]encrypt_app=false[/B][/SIZE]
[SIZE="5"][B]encrypt_adb=false[/B][/SIZE]
rc4_key=*************************************************************************************************************************************************************************************************************************************************
imei=*******************
last_download_time=*******************
encrypt_log=true
Reboot your device and enter the stock OnePlus phone app.
Enter your factory code of choice.
Main menu is *#808#
Sorry not sure to understand the purpose?
Steve0007 said:
Sorry not sure to understand the purpose?
Click to expand...
Click to collapse
You get all the factory settings for testing the phone including recalibration sensors, display, fp reader, etc.
good job crazy it lets that part of system be modified and revert back after boot
antnyhills said:
In a root explorer of your choice go to /mnt/vendor/persist/engineermode/
You'll see a file that is called 'engineermode_config' open that file with a text editor.
Switch the two lines to "false"
Reboot your device and enter the stock OnePlus phone app.
Enter your factory code of choice.
Main menu is *#808#
Click to expand...
Click to collapse
If this works great. My wife is at sleep now.i try this tomorrow
antnyhills said:
You get all the factory settings for testing the phone including recalibration sensors, display, fp reader, etc.
Click to expand...
Click to collapse
So being new to all this I got everything on my phone but don't see the f.p. sensor for I lost mine and am trying to get it working again.
pyry666 said:
If this works great. My wife is at sleep now.i try this tomorrow
Click to expand...
Click to collapse
Edit. Sure i can acces that mode but pf crashes if try that option..
Edit. And its just ocd thing anyway. Repair center is not that far away..
Edit3: so after playing some time now wuth factory mode U thank that you would still need that OnePlus specual tool to recalibrate fp reader..Am I wrong?
For FactoryMode unlock you can simple use my Magisk Module what I created on 7.5.2020
Works for every OnePlus device
https://download.android-freaks.de/dl/?dir=Miscellaneous/Magisk Modules (Android)
jamal2367 said:
For FactoryMode unlock you can simple use my Magisk Module what I created on 7.5.2020
Works for every OnePlus device
https://jamal2367.de/downloads/?dir=Miscellaneous/Magisk Modules (Android)
Click to expand...
Click to collapse
Link is down. 404 error.
Is it still working on 10.5.12 ?
TheKnux said:
Link is down. 404 error.
Click to expand...
Click to collapse
Try this, it's still the same module created by @jamal2367. I found the module in his website.
Module doesn't work. Dialing #*808# returns to the dialer.
Sent from my IN2025 using Tapatalk
FernBch said:
Module doesn't work. Dialing #*808# returns to the dialer.
Sent from my IN2025 using Tapatalk
Click to expand...
Click to collapse
Did you debloat your phone? Check that the EngineeringMode.apk file is present in the system /app/EngineeringMode folder. This apk is essential to make factory mode work.
dianoandr said:
Did you debloat your phone? Check that the EngineeringMode.apk file is present in the system /app/EngineeringMode folder. This apk is essential to make factory mode work.
Click to expand...
Click to collapse
The app is there. Editing the config file causes it to FC on open when dialing the code, couldn't seem to get past that so I tried the module.
Sent from my IN2025 using Tapatalk
FernBch said:
The app is there. Editing the config file causes it to FC on open when dialing the code, couldn't seem to get past that so I tried the module.
Sent from my IN2025 using Tapatalk
Click to expand...
Click to collapse
I have already read about a similar problem on oneplus 7 pro, on that occasion they solved it using an old version of the EngineerMode.apk, the one available on apk mirror here. The original thread I am referring to can be found here.
dianoandr said:
I have already read about a similar problem on oneplus 7 pro, on that occasion they solved it using an old version of the EngineerMode.apk, the one available on apk mirror here. The original thread I am referring to can be found here.
Click to expand...
Click to collapse
Thanks, I'll check it out. I've had the 1+8P for about 10 days so I'm still learning some of the secrets.
Sent from my IN2025 using Tapatalk
FernBch said:
Module doesn't work. Dialing #*808# returns to the dialer.
Click to expand...
Click to collapse
Should be *#808# rather than #*800#
FernBch said:
Thanks, I'll check it out. I've had the 1+8P for about 10 days so I'm still learning some of the secrets.
Sent from my IN2025 using Tapatalk
Click to expand...
Click to collapse
It's a pleasure, when you try let them know if it works, so it can get back to someone else
Steve0007 said:
Should be *#808# rather than #*800#
Click to expand...
Click to collapse
Oops. That's a typo.... Lol
Sent from my IN2025 using Tapatalk
*#808# is supposed to take you into "Factory Mode" aka manual test mode. I still haven't gotten past the FC issue.....
*#36446337# is for "Engineering Mode". From there you can also run factory mode but it still crashes....
Sent from my IN2025 using Tapatalk
---------- Post added at 08:02 PM ---------- Previous post was at 07:14 PM ----------
I should also add you can mess your phone up here. Proceed with extreme caution!!
Sent from my IN2025 using Tapatalk