Lockscreen wallpaper Tint Remover - Google Pixel 2 XL Themes, Apps, and Mods

Removes Lockscreen wallpaper dimming tint and Notification pulldown also. Flash in TWRP. For stock roms.
Pie uploaded 9-5-18
Magisk version
https://www.androidfilehost.com/?fid=1322778262903998215
Regular version
https://www.androidfilehost.com/?fid=1322778262903998217
-------------------------------------
DP4
https://www.androidfilehost.com/?fid=5862345805528052635
DP4 Magisk version
https://www.androidfilehost.com/?fid=5862345805528053142
8.1 July update
https://www.androidfilehost.com/?fid=5862345805528052638
8.1 July update Magisk version
https://www.androidfilehost.com/?fid=5862345805528053118
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Magisk installer causes bootloop. Module not listet in Magisk (using Magisk Manager for Recovery Mode) = can't remove / uninstall. You don't happen to have a way to revert this, do you?
EDIT: Nevermind. Going to reflash stock image.
EDIT 2: Well, I'm stuck. Flashed a factory image without wiping (removed -w from flash-all.bat) and now it won't boot at all. Stuck on splash screen.
"Your device is corrupt. It can't be trusted and may not work properly."

nitrous² said:
Magisk installer causes bootloop. Module not listet in Magisk (using Magisk Manager for Recovery Mode) = can't remove / uninstall. You don't happen to have a way to revert this, do you?
EDIT: Nevermind. Going to reflash stock image.
EDIT 2: Well, I'm stuck. Flashed a factory image without wiping (removed -w from flash-all.bat) and now it won't boot at all. Stuck on splash screen.
"Your device is corrupt. It can't be trusted and may not work properly."
Click to expand...
Click to collapse
You need to clean flash i guess
Sent from my Google Pixel 2 XL using XDA Labs

Prattham said:
You need to clean flash i guess
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Clean flash a theme? For real? Whatever. Don't care anymore. Had to factory reset and wipe the internal storage, since, well, encrypted. *Sarcasm on* My fast German internet connection will restore my apps in no time and I don't mind the lost data at all *sarcasm off*.

nitrous² said:
Clean flash a theme? For real? Whatever. Don't care anymore. Had to factory reset and wipe the internal storage, since, well, encrypted. *Sarcasm on* My fast German internet connection will restore my apps in not time and I don't mind the lost data at all *sarcasm off*.
Click to expand...
Click to collapse
No i meant you need to clean flash stock image which you did
Sent from my Google Pixel 2 XL using XDA Labs

nitrous² said:
Clean flash a theme? For real? Whatever. Don't care anymore. Had to factory reset and wipe the internal storage, since, well, encrypted. *Sarcasm on* My fast German internet connection will restore my apps in no time and I don't mind the lost data at all *sarcasm off*.
Click to expand...
Click to collapse
Always try a factory reset in TWRP first. You have to set your phone up as new but you don't lose internal data. We're you bone stock? Did you flash in TWRP?

Tulsadiver said:
Always try a factory reset in TWRP first. You have to set your phone up as new but you don't lose internal data. We're you bone stock? Did you flash in TWRP?
Click to expand...
Click to collapse
AHH! GOD F***ING DAMMIT!! Should've thought about a factory reset in TWRP. I was able to boot into it.
Yes, stock ROM, stock Kernel. Only modification was Magisk 16.7 and a user certificate installed into the system store (AdGuard).

nitrous² said:
AHH! GOD F***ING DAMMIT!! Should've thought about a factory reset in TWRP. I was able to boot into it.
Yes, stock ROM, stock Kernel. Only modification was Magisk 16.7 and a user certificate installed into the system store (AdGuard).
Click to expand...
Click to collapse
I went back to stock, rerooted, installed Magisk and flashed this on my pixel and it worked fine.

Tulsadiver said:
I went back to stock, rerooted, installed Magisk and flashed this on my pixel and it worked fine.
Click to expand...
Click to collapse
Ok, I just noticed it says "for the Google Pixel(sailfish)" on AFH and I also noticed you saying "flashed this on my pixel". Any chance this mod is meant for the Pixel 1 / XL and not the Pixel 2 / XL (Taimen)?
I've attached a log from an attempted Magisk install.

nitrous² said:
Ok, I just noticed it says "for the Google Pixel(sailfish)" on AFH and I also noticed you saying "flashed this on my pixel". Any chance this mod is meant for the Pixel 1 / XL and not the Pixel 2 / XL (Taimen)?
I've attached a log from an attempted Magisk install.
Click to expand...
Click to collapse
It says that because it is located in the root folder for my pixel phones. Inside that they all have their own folders.
Log says it installed but config file failed to inflate but it worked fine on mine.
The pixel phones are so much alike you can often flash a whole systemuigoogle.apk and framework-res.apk if you omit the meta-inf and Android manifest. Not always though.

Tulsadiver said:
It says that because it is located in the root folder for my pixel phones. Inside that they all have their own folders.
Log says it installed but config file failed to inflate but it worked fine on mine.
The pixel phones are so much alike you can often flash a whole systemuigoogle.apk and framework-res.apk if you omit the meta-inf and Android manifest. Not always though.
Click to expand...
Click to collapse
Ok, I see. Yeah, not sure what to tell you. The install via TWRP for both the Magisk and standard install variant seemed to work fine. I first tried the regular installer and after the phone was bootlooping I tried installing the Magisk version. I don't want to risk a bootloop for the sake of a test. It took me close to 10 hours to redownload my apps and restore my WhatsApp backup. That's thanks to our glorious German internet #neuland.

nitrous² said:
Ok, I see. Yeah, not sure what to tell you. The install via TWRP for both the Magisk and standard install variant seemed to work fine. I first tried the regular installer and after the phone was bootlooping I tried installing the Magisk version. I don't want to risk a bootloop for the sake of a test. It took me close to 10 hours to redownload my apps and restore my WhatsApp backup. That's thanks to our glorious German internet #neuland.
Click to expand...
Click to collapse
Sorry to hear that. If by bootlooping you mean stuck on Google, I have gotten past that by simply rebooting my phone. Magisk is always a problem child. This is not a module but a vrthemer capable of installing to the Magisk image. I suggest to people that they uninstall Magisk, reroot, use the regular installer to get their phone like they like, then install and use Magisk manager. My Aroma installer has this mod, all the way at the bottom, and others as well and is edge sense capable. Just install the app, not the module.

Tulsadiver said:
Sorry to hear that. If by bootlooping you mean stuck on Google, I have gotten past that by simply rebooting my phone. Magisk is always a problem child. This is not a module but a vrthemer capable of installing to the Magisk image. I suggest to people that they uninstall Magisk, reroot, use the regular installer to get their phone like they like, then install and use Magisk manager. My Aroma installer has this mod, all the way at the bottom, and others as well and is edge sense capable. Just install the app, not the module.
Click to expand...
Click to collapse
Bootlooping as in; Startup > G Logo loading screen > Black screen (abrupt power off) > Startup > G Logo loading screen > Black screen (abrupt power off) > ∞
Reflashing a factory image (same ASB version) interrupted the loop by booting into some sort of recovery where it said that my device is corrupted and may not work properly and suggested I make a data wipe/factory reset.

nitrous² said:
Bootlooping as in; Startup > G Logo loading screen > Black screen (abrupt power off) > Startup > G Logo loading screen > Black screen (abrupt power off) > ∞
Reflashing a factory image (same ASB version) interrupted the loop by booting into some sort of recovery where it said that my device is corrupted and may not work properly and suggested I make a data wipe/factory reset.
Click to expand...
Click to collapse
The mod is definitely for Pixel 2XL. My pixel had rounded corners on the statusbar that goes with the curved display of pixel 2 xl. If you can upload your SystemUIGoogle.apk I'll try and make one for your phone. Maybe yours is different from the system image I extracted.

Tulsadiver said:
The mod is definitely for Pixel 2XL. My pixel had rounded corners on the statusbar that goes with the curved display of pixel 2 xl. If you can upload your SystemUIGoogle.apk I'll try and make one for your phone. Maybe yours is different from the system image I extracted.
Click to expand...
Click to collapse
Oh, man! That's so nice of you =) But I have to decline. I need a working phone by tomorrow and can't risk it.

nitrous² said:
Oh, man! That's so nice of you =) But I have to decline. I need a working phone by tomorrow and can't risk it.
Click to expand...
Click to collapse
Maybe later.

Tulsadiver said:
Maybe later.
Click to expand...
Click to collapse
No, I meant like; Here is my SystemUIGoogle.apk but I can't report back if it did work until next weekend.

nitrous² said:
No, I meant like; Here is my SystemUIGoogle.apk but I can't report back if it did work until next weekend.
Click to expand...
Click to collapse
Your framework-res apk must be different than what I show it should be. You will need to upload yours. That might be the problem.
Edit: never mind. I was thinking you were on DP5 but you are on 8.1. I used the wrong framework.

Tulsadiver said:
Your framework-res apk must be different than what I show it should be. You will need to upload yours. That might be the problem.
Edit: never mind. I was thinking you were on DP5 but you are on 8.1. I used the wrong framework.
Click to expand...
Click to collapse
So you no longer need my framework-res.apk?

nitrous² said:
No, I meant like; Here is my SystemUIGoogle.apk but I can't report back if it did work until next weekend.
Click to expand...
Click to collapse
Here is a regular version and Magisk version.

Related

[ROM][JB][4.1.2] Paranoid Android 2.99_Final for Photon {12.7.12}

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wanna be up to date with ParanoidAndroid project news?, click here, and visit our webpage!​
Installation Instructions
Place ROM onto phone storage
Reboot to recovery
Make a Nandroid
Install Rom: Wipe INSIDE ROM
When you select "Reboot Not", you'll get a CWM error, IGNORE IT
Install OPTIONS or Gapps
WIKI/FAQ Located: To be reworked
Click to expand...
Click to collapse
Paranoid Hints
Go to Settings, System, Font size, set it to NORMAL
Launcher Settings: margins: SMALL (If youre using Apex / Nova), show permanent searchbar: YES, Grid: 5x4, resize all widgets: YES, Wallpaper scrolling: OFF
Click to expand...
Click to collapse
Paranoid Trouble
Nothing yet. All possible visual bugs can be fixed changing PAL & PAD parameters
Click to expand...
Click to collapse
What is Borked:​
Video Camera-laggy
Transitional Stutters Possible
You tell me
Both GL issues are due to missing drivers. Since Moto won't release, there is no ETA for fix​
If you need to report a NEW bug, report it once, and the next TWO people VERIFY it. I don't need everyone reporting same bug 20 times. I you can, provide me the following information:
Version you are using
What wipe you did and what ROM you came from
Have you restored data/apps through Titanium or other app?
What app is misbehaving and steps to reproduce error
LOGCATS <--Prefer this
If you don't know how to logcat, go HERE and learn. This really nice guy took the time to write out a good how to
When you have a LOGCAT and would like to post it, please go to pastebin and post it in there, then LINK that location in this thread...I don't want to see them posted directly in here.
Click to expand...
Click to collapse
Downloads​
ROM File Located Here
Options Chooser Located Here
My CWM V1 Located HERE -Aroma Prep Here Too
Click to expand...
Click to collapse
Credits:
Cyanogenmod Project, for CM10
Jokersax11 for help with initial Photon work
scott.hart.bi for help with source work
Amarullz for Aroma Installer
Paranoid Android's Devs for making this ROM
Anyone Testing and Providing USEFUL FEEDBACK (logcats )
Click to expand...
Click to collapse
GITHUB (FOR KERNEL SOURCE)-GPL COMPLIANCE PhotonDevTeam Repo
Click to expand...
Click to collapse
SCREENSHOTS
Is this uploaded? I didnt see it on Jokers site
MikeyLee said:
Is this uploaded? I didnt see it on Jokers site
Click to expand...
Click to collapse
Under Th3Bill
wow great job, I'm happy to review the Paranoid, thanks Th3Bill, I hasten to download and test it
Thanks a lot for the new version of my favourite ICS rom! Can't donate as I don't have paypal, but rest assured I will click on your ads everyday
Ok....don't download for a little while. I have to re-upload the rom. I made a boo-boo, which will result in tablet mode not initiating properly. I just fixed it on my phone, and it is SWEET!!!
Hi Bill, the process com.android.phone stopped unexpectedly on first boot bug is still there. I tried to fix it using the previous webcorefix.zip but it just stuck on the boot animation screen.
/b/-TarD said:
Hi Bill, the process com.android.phone stopped unexpectedly on first boot bug is still there. I tried to fix it using the previous webcorefix.zip but it just stuck on the boot animation screen.
Click to expand...
Click to collapse
GSM or CDMA?
com.phone wouldn't be webcore...
If you can get me a logcat output, that'd be great. I have flashed this 3 times clean over the last few hours. I use CDMA and have had NO issues.
Th3Bill said:
GSM or CDMA?
com.phone wouldn't be webcore...
If you can get me a logcat output, that'd be great. I have flashed this 3 times clean over the last few hours. I use CDMA and have had NO issues.
Click to expand...
Click to collapse
I am using GSM. Is my way of creating a logcat output correct? I reinstall the rom, get the error msg, set usb debugging on and charge only, connect phone to computer, and use adb logcat on my command prompt?
Anyway the reason I thought the webcorefix fix the issue is because it worked for me on Paranoid Android 1.1. After flashing that, no more error messages.
Edit : Not sure where did I do wrong, I use adb logcat > logcat.txt but it kinda stuck there not moving. Am using the android-sdk from my previous Xperia Play flashing days.
Edit 2 : I got the logcat.txt after I got bored waiting and disconnect, hope its complete. Anyway, the phone doesn't detect any network after the phone process fc
/b/-TarD said:
I am using GSM. Is my way of creating a logcat output correct? I reinstall the rom, get the error msg, set usb debugging on and charge only, connect phone to computer, and use adb logcat on my command prompt?
Anyway the reason I thought the webcorefix fix the issue is because it worked for me on Paranoid Android 1.1. After flashing that, no more error messages.
Click to expand...
Click to collapse
If you have root explorer, go to build.prop to the line:
ro.telephony.default_network=7
change the 7 to 0
then reboot
go dialer put in *#*#4636#*#*
go to phone info
make sure it says GSM auto
reboot
I'll up a fix in a few mins once the re-up of this is finished.
Th3Bill said:
Ok....don't download for a little while. I have to re-upload the rom. I made a boo-boo, which will result in tablet mode not initiating properly. I just fixed it on my phone, and it is SWEET!!!
Click to expand...
Click to collapse
Right on man. Cant wait to update. Is the fixed ROM uploaded now?
Updated version is up
Th3Bill said:
If you have root explorer, go to build.prop to the line:
ro.telephony.default_network=7
change the 7 to 0
then reboot
go dialer put in *#*#4636#*#*
go to phone info
make sure it says GSM auto
reboot
I'll up a fix in a few mins once the re-up of this is finished.
Click to expand...
Click to collapse
Not sure whether I followed your instructions correctly. But it isn't working, but its okay, don't bother. I will wait for the your flashable fix and your fixed Paranoid rom together then report back
Thanks for the prompt help anyway
Awesome!
Great! cannot wait to try. No link under thebill, only MUI builds..
edit: found it, but in a weird place.... here is direct link MOD EDIT: Link Removed as per OP Request.....MD
hightech316 said:
Great! cannot wait to try. No link under thebill, only MUI builds..
edit: found it, but in a weird place.... here is direct link
Click to expand...
Click to collapse
Weird place? It's under Th3Bill "Paranoid Android for Photon" PLEASE DO NOT HOT LINK MY WORK. I have it through the site for a reason.
Please remove the link or I will ask the mod to remove it
Booting problem
Hello all,
I am not sure this is the right place for this but I can't get this to boot. I thought I had everything rooted, unlocked and latest version of clockwork recovery installed. This install doesn't make it past the dual core boot screen. I have tried this several times even with a different kernel and no luck. CM7 installs just fine. I may be missing something. Any help is appreciated.
ITSAHERO said:
Hello all,
I am not sure this is the right place for this but I can't get this to boot. I thought I had everything rooted, unlocked and latest version of clockwork recovery installed. This install doesn't make it past the dual core boot screen. I have tried this several times even with a different kernel and no luck. CM7 installs just fine. I may be missing something. Any help is appreciated.
Click to expand...
Click to collapse
When Aroma begins to install...watch it very carefully...if it goes through it really fast, it's because you have an unreported error in CWM. You need to go to Advanced menu, select Report Error, then select Show Log, then Reboot Recovery, then make sure you have at least 75% battery (if not, plug it in to the wall outlet...NOT A PC), then flash the rom
Th3Bill said:
When Aroma begins to install...watch it very carefully...if it goes through it really fast, it's because you have an unreported error in CWM. You need to go to Advanced menu, select Report Error, then select Show Log, then Reboot Recovery, then make sure you have at least 75% battery (if not, plug it in to the wall outlet...NOT A PC), then flash the rom
Click to expand...
Click to collapse
I didn't notice this was AROMA. I have been wiping before install. That could very well be my problem. Thank you.
You might also want to be on jokers recovery or TWRP. The cwm from rom manager app doesn't work for us
Sent from my MOF'd up MoPho

Epson Moverio BT-300

Anyone have a pair of these glasses and working on root access? Anyone interested? There are a group of us that would be really interested in finding a solution.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dvegaman said:
Anyone have a pair of these glasses and working on root access? Anyone interested? There are a group of us that would be really interested in finding a solution.
Click to expand...
Click to collapse
I have a pair of the FPV Drone Edition. Have side loaded a few apps. Haven't rooted since Galaxy S3 ( back on iPhone now) am interested to get this going
Hi !
It seems the rooting of intel devices follow the scheme:
-get bootimg
-patch it
-allow oem bootloader (voiding warranty and endangering future updates)
-flash the patched bootimg and pray
Is this correct or did i oversimplify or generalize too much or am i plain wrong, anyone ?
Greetings,
Ender
P.S. Greetings dvegaman
Bump.
Well, BUMP, goddamn
Just came across 2 pairs of these (BT-300s).
If the lack of interest in rooting is due to lack of hardware, reach out to me privately here on XDA; would happily donate one to kickstart some development efforts.
-jd
jdiegmueller said:
Just came across 2 pairs of these (BT-300s).
If the lack of interest in rooting is due to lack of hardware, reach out to me privately here on XDA; would happily donate one to kickstart some development efforts.
-jd
Click to expand...
Click to collapse
Bumping this one up. Have a new pair and looking to root to wake them up some.
Sent from my Moto Z (2) using Tapatalk
This may seem easy to others but I figured out how to do a factory data reset using ADB... something that would've helped when my BT-300 went into a boot loop last weekend...
***DO AT YOUR OWN RISK! NOT RESPONSIBLE FOR BRICKING, ETC..... (but it worked fine for me).
1. Install "minimal_adb_fastboot_v1.4.2_setup.exe" (google it and grab at your own risk) on your Windows PC.
2. Go to the BT-300 and:
a. Under Security allow unknown sources
b. Under Developer Options allow USB debugging and unlock bootloader.
3. Connect same powered up BT-300 to PC via USB cable.
4. Start up that minimal ADB program. It will open in command prompt.
5. Check connection by typing "adb devices"
Should see "EMBT3C device" on PC
6. Now type, "adb reboot recovery" and wait for android with triangle/exclamation point to appear after device reboots. You will notice the physical buttons flash purple too.
7. Press and hold power button. Also press Vol Up, then release Vol Up and finally release Power button.
You should now see the recovery menu including "wipe data/factory reset", cache clear, and so on...
NOW... if I could get recovery.zip image to restore if I "kill" it to reload with ADB... THEN I'd try root. There must be a way. I just want GApps 5.1.1 on the thing for starters.
Still struggling with rooting... No dice so far. I've never rooted any Android... Once rooted can we then save the original factory ROM someplace safe, or do I need that first from another source? Newbie questions . I know just enough to be dangerous! LOL.
I got the factory image
Played around with the "SoftwareUpdate" apk and found the strings it uses to download the 1.4
Ugh just signed up but because I don't have enough posts I had to put a bunch of spaces in the links for them to
show up. Just remove the spaces and they should work? Either his or copy the SoftwareUpdate.apk and pull the strings from that.
ht tps:// download.ebz.epson.net /dsc /du /04 /SecureUpdateInfo ?PRN=BT-300&CTI=80&OSC=ARD&SCD=H756EMBT3C&SID=012345
You download a file called "SecureUpdateInfo" open it in a text editor and it will give you a link to the direct download for the zip. Its about 300megs. I have been playing with the boot options, but keep crashing it on boot and having to restore. I found 4 test pins that may be a serial port, but its 1.8 volt so I need to build something
PS - It might com back without a link but "BUSY" on it. I have been testing it a bunch so thats what happened right now. The fille will look like below
Code:
; secure update information
[BT-300;]
Version=R1.4.0
Size=371659424
Location= ht tps:// download.ebz.epson.net/ dsc/check/ 01/ GetFile. php ?PATH=xxxxxxx/OTA-R1.4.0.zip&KEY=lt1fs0DK
DownloadNumber=11474485
LALocation1=h ttp:// download.ebz.epso n.net/ dsc /hmd_license /EULA.zip
Erodros said:
Played around with the "SoftwareUpdate" apk and found the strings it uses to download the 1.4
Ugh just signed up but because I don't have enough posts I had to put a bunch of spaces in the links for them to
show up. Just remove the spaces and they should work? Either his or copy the SoftwareUpdate.apk and pull the strings from that.
ht tps:// download.ebz.epson.net /dsc /du /04 /SecureUpdateInfo ?PRN=BT-300&CTI=80&OSC=ARD&SCD=H756EMBT3C&SID=012345
You download a file called "SecureUpdateInfo" open it in a text editor and it will give you a link to the direct download for the zip. Its about 300megs. I have been playing with the boot options, but keep crashing it on boot and having to restore. I found 4 test pins that may be a serial port, but its 1.8 volt so I need to build something
PS - It might com back without a link but "BUSY" on it. I have been testing it a bunch so thats what happened right now. The fille will look like below
Code:
; secure update information
[BT-300;]
Version=R1.4.0
Size=371659424
Location= ht tps:// download.ebz.epson.net/ dsc/check/ 01/ GetFile. php ?PATH=xxxxxxx/OTA-R1.4.0.zip&KEY=lt1fs0DK
DownloadNumber=11474485
LALocation1=h ttp:// download.ebz.epso n.net/ dsc /hmd_license /EULA.zip
Click to expand...
Click to collapse
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
chuck1026 said:
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
Click to expand...
Click to collapse
Is the link in the in the secureupdate? I don't know if the strings encode the serial number in some why or if epson is reading this thread
I can pm you a link for the file if you can't get it
Erodros said:
Is the link in the in the secureupdate? I don't know if the strings encode the serial number in some why or if epson is reading this thread
I can pm you a link for the file if you can't get it
Click to expand...
Click to collapse
Yes, pm me the link. Thanks
Sent from my Moto Z (2) using Tapatalk
chuck1026 said:
Yes, pm me the link. Thanks
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Ok sending now.
I also managed to root my epson! I discovered the twrp.img here:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
If you get into bootloader mode and fastboot flash it into the recovery partition, you can adb root it and then install supersu from there. I just trashed my device though so be sure to do a full image backup first haha.
Erodros said:
Ok sending now.
I also managed to root my epson! I discovered the twrp.img here:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
If you get into bootloader mode and fastboot flash it into the recovery partition, you can adb root it and then install supersu from there. I just trashed my device though so be sure to do a full image backup first haha.
Click to expand...
Click to collapse
You trashed it? What did ya load after root to crash it?
chuck1026 said:
You trashed it? What did ya load after root to crash it?
Click to expand...
Click to collapse
Tried to load up opengapps, then every time I rebooted it would be "optimizing apps" I tried to side-load the OTA again and poof, it killed the system partition.
The ota apparently doesn't have the full image. Right now I am trying to hack together something from another cherry rom and side load it, but I need a DD of someones system Glad twrp still works or I wouldn't have shell root access to fix.
Erodros said:
Tried to load up opengapps, then every time I rebooted it would be "optimizing apps" I tried to side-load the OTA again and poof, it killed the system partition.
The ota apparently doesn't have the full image. Right now I am trying to hack together something from another cherry rom and side load it, but I need a DD of someones system Glad twrp still works or I wouldn't have shell root access to fix.
Click to expand...
Click to collapse
You tell me how to share a pure factory image of mine (I'll gladly do an FDR for the cause)... and I'll share with ya!
chuck1026 said:
You tell me how to share a pure factory image of mine (I'll gladly do an FDR for the cause)... and I'll share with ya!
Click to expand...
Click to collapse
Ok I am retarded. I didn't configure twp correctly so all the folders it had were wrong. So when I went to use the install tool it screwed up majorly.
Just glad I didn't overwrite the bootloader
PS - Ok, I figured out how to restore the original recovery loader and it recovered fine. It must be something in this hacked version of twip that isn't applying the ota correctly. Going to try to build a version of twip just for this
Erodros said:
Ok I am retarded. I didn't configure twp correctly so all the folders it had were wrong. So when I went to use the install tool it screwed up majorly.
Just glad I didn't overwrite the bootloader
Click to expand...
Click to collapse
You are not. I am the noob trying to figure out the whole root process and I don't even know how to backup the existing bootloader and ROM so I can restore it with ADB if I screw it all up in root..... I feel clueless and know just enough to be dangerous... yet for some reason, I'm not afraid, just need to learn.
chuck1026 said:
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
Click to expand...
Click to collapse
Whew! I did it. First I took the instructions from here as a start:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
In fact, if you can "almost" follow the instructions verbatim. The problem is that the data drive is encrypted and the default android password didn't work so I had to modify the boot.img to not encrypt the data partition then do a wipe. supersu installed fine then.
As for gapps, that was tricky. You have to manually install google webview apk as the built in one is garbage.
Still working on the vr settings. Camera has issues with scaling as I think good believes it to be a widescreen when its a 4.3.
Once I get it down, I will make a boot.img and recovery.img that should just work.

Root thread (US & EU) requests welcome! Oreo boot added

This is a US unlocked patched boot.img by magisk
It works on T-Mobile variant as well.
(Added EU patched boot.img)
(Added T-Mobile Oreo boot.img)
Link for Oreo T-Mobile
https://drive.google.com/file/d/17U0m0LIshFNBdNaygVqpsQ4TeLiDRUuo/view?usp=drivesdk
Link for latest T-Mobile 2.15.531.11
https://www.androidfilehost.com/?fid=890129502657596824
Install magisk manager apk from magisk thread.
Flash in fastboot
fastboot flash boot patched_boot.img in download mode.
I am not responsible for anything that happens to your device.
Credits to @Captain_Throwback for the right direction.
Credits to @topjohnwu for magisk.
And credits to anyone else that plays a part.
OS version 1.00.617.15 works for T-Mobile variant too.
Us unlocked stock boot.img link https://drive.google.com/file/d/11OFuYNePnSSCTfC4pWpxVOgKoLvByxJ0/view?usp=drivesdk
Patched boot.img link
https://drive.google.com/file/d/1XdoIln2zai1464CCTOE0LsD2SWbVZrW0/view?usp=drivesdk
ANDROID ONE FASTBOOT FLASHING IS DIFFERENT THAN US VERSIONS
because the a & b partitions.
So, now I have the patched_boot.img and the boot_signed.img for December security patch, build No. 1.09.401.2.
You have to check with "fastboot getvar all" wich partition is active so you have to boot to boot_a or boot_b. For me it was b now.
To take new update you have to flash the signed_boot first.
https://drive.google.com/open?id=1emcDV3p6Nuqgc2RVD9BnWUnU7JV-vqez
This is for os version 1.06.401.14 europe it is from
2Q3FIMG_OCEAN_LIFE_UHL_O80_SENSE90A1_HTC_Europe_1. 06.401.14_Radio_sdm630-005201-1711031628A_release_515519_signed_2_4
Patched htc_ocla1_sprout boot.img link
https://drive.google.com/open?id=1em...BnWUnU7JV-vqez
credits to @MC_Ohr
Stock boot.img
https://drive.google.com/file/d/1V69fjXKskPQ-6EpFZm2Pxe3S2yrFGIWL/view?usp=drivesdk
Awesome thanks to this I might get this device now.
EDIT: It's working, thanks.
BookCase said:
Not working for me.
Click to expand...
Click to collapse
You need to unlock your bootloader first..
I dont have tmobile version. I have normal Life (EU). How can root and unlock?
So, after installing Magisk, a lot of my apps are force closing.
Almost Evey app, and I cannot add accounts like 2nd Google or Facebook
Well just unlocked my booloader next flash me a recovery, Then it will be time to get some BadSeed up in here ,,,, Just sayin
BookCase said:
Almost Evey app, and I cannot add accounts like 2nd Google or Facebook
Click to expand...
Click to collapse
What device variant do you have?
twinnfamous said:
What device variant do you have?
Click to expand...
Click to collapse
T-Mobile HTC U11 Life
BookCase said:
T-Mobile HTC U11 Life
Click to expand...
Click to collapse
I have the same variant and no problems for me. Did u install anything else?
In case anyone has a temporary lapse of brain functioning like I did and gets confused because it seems this isn't working, it is important to remember that you'll need to install the Magisk Manager apk and Phh's Superuser (at least, those are the things I had to do after realizing I didn't pay attention to the fact that this is Magisk).
twinnfamous said:
I have the same variant and no problems for me. Did u install anything else?
Click to expand...
Click to collapse
I did install Titanium Backup and removed some bloat. Maybe I removed something I shouldn't have. I wonder if a factory reset would help or make things worse.
BookCase said:
I did install Titanium Backup and removed some bloat. Maybe I removed something I shouldn't have. I wonder if a factory reset would help or make things worse.
Click to expand...
Click to collapse
Factory reset and let google backup restore your apps
twinnfamous said:
Factory reset and let google backup restore your apps
Click to expand...
Click to collapse
Okay, so I did the factory reset and now Google Services FC's and I cannot setup the phone. I get to the "Set Up Wifi" screen and cannot progress further. I'm thinking I need a factory image to restore the phone, now. I really borked this thing.
Has anyone else had any issues with Magisk refusing to install modules after flashing this? It acts like a module is being flashed but changes nothing. I'm wondering if it has to do with not having a functional recovery at the moment. I have been able to install Xposed using the Xposed installer and Xposed is working perfectly.
BookCase said:
Okay, so I did the factory reset and now Google Services FC's and I cannot setup the phone. I get to the "Set Up Wifi" screen and cannot progress further. I'm thinking I need a factory image to restore the phone, now. I really borked this thing.
Click to expand...
Click to collapse
U should be able to get back to normal unless you modified the system. I have a system img. I can upload later if that's the case
After you install recovery, and you modify the system ( ie format the system ) are we able to flash things in recovery? I haven't yet but wondering
cbrown245 said:
After you install recovery, and you modify the system ( ie format the system ) are we able to flash things in recovery? I haven't yet but wondering
Click to expand...
Click to collapse
U can flash things in recovery now. You just can't decrypt data yet. So only you can flash from external SD card.
Yes , but is this after you format the memory ? I can't get anything to show on the SD card or the external SD card, is it required to format ?

April Update is out now

installing..,
Installed on my wife's Pixel 3 with flash-all (minus -w). Rooted with Magisk 18.1 via TWRP .img instance and installed ElementalX 1.06 with EX Kernel Manager auto. Made one custom prop setting. No issues at all.
Any idea what fixes are in this one?
davidstjohn1 said:
Any idea what fixes are in this one?
Click to expand...
Click to collapse
https://source.android.com/security/...019-04-01.html
https://source.android.com/security/...language=zh_cn
davidstjohn1 said:
Any idea what fixes are in this one?
Click to expand...
Click to collapse
https://source.android.com/security/bulletin/pixel/2019-04-01.html
Hi everyone, I need some help/advice,
I tried flashing the April factory image (minus -w), and am now on "Can't load Android System. Your data may be corrupt" error. Everytime I reboot the device it just goes to "No Command" or this error screen.
I uninstalled Magisk, and was on Sultan's kernel. Does anyone have any suggestions on how to restore my system without having to factory reset? I know some people suggested flashing stock kernel, but I can't seem to find the link to it (I thought the stock kernel was with the factory image).
Any help would be appreciated!
I am dling the factory image now, but boot.img should be in there. Are you sure it was not a bad dl?
-Boot.img is in there. Extract the zip then open the "image-blueline....zip" it is in there. If it is not then something is wrong with your dl.
sliding_billy said:
Installed on my wife's Pixel 3 with flash-all (minus -w). Rooted with Magisk 18.1 via TWRP .img instance and installed ElementalX 1.06 with EX Kernel Manager auto. Made one custom prop setting. No issues at all.
Click to expand...
Click to collapse
What prop setting are you making. Just curious, I haven't seen any prop editing threads for the pixel 3.
FilthyFord said:
What prop setting are you making. Just curious, I haven't seen any prop editing threads for the pixel 3.
Click to expand...
Click to collapse
Native tethering. This method works on my 3 XL as well as my wife's "little" 3 on T-Mobile.
https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-native-tethering-rooted-pixel-3-t3858662
atu567 said:
Hi everyone, I need some help/advice,
I tried flashing the April factory image (minus -w), and am now on "Can't load Android System. Your data may be corrupt" error. Everytime I reboot the device it just goes to "No Command" or this error screen.
I uninstalled Magisk, and was on Sultan's kernel. Does anyone have any suggestions on how to restore my system without having to factory reset? I know some people suggested flashing stock kernel, but I can't seem to find the link to it (I thought the stock kernel was with the factory image).
Any help would be appreciated!
Click to expand...
Click to collapse
I had the same issue, cant find stock kernel either.
extracted the zip, fastboot flash boot boot.img, fixed.
jk didnt work oddly enough.
got to login then wouldnt let me use my screen. no touch input.
edit again: update platform tools fixed problem. https://dl.google.com/android/repository/platform-tools_r28.0.2-windows.zip
sliding_billy said:
Installed on my wife's Pixel 3 with flash-all (minus -w). Rooted with Magisk 18.1 via TWRP .img instance and installed ElementalX 1.06 with EX Kernel Manager auto. Made one custom prop setting. No issues at all.
Click to expand...
Click to collapse
hey,bro!I would like to ask if magisk can pass the safetynet check after installing the April Updata. My pixel 3 feedback me ‘’the return value is invalid’’
wssxzzzz said:
hey,bro!I would like to ask if magisk can pass the safetynet check after installing the April Updata. My pixel 3 feedback me ‘’the return value is invalid’’
Click to expand...
Click to collapse
No problem with safetynet here.
sliding_billy said:
No problem with safetynet here.
Click to expand...
Click to collapse
Ok, thank you, I think that is my problem.
wssxzzzz said:
Ok, thank you, I think that is my problem.
Click to expand...
Click to collapse
What is the problem?
Obviously quite subjective, but the camera appears to be opening faster for me when double clicking power. There was also a Google Camera update from the Play Store this morning, so could have been that as well, but this has been a major bug bear of mine since getting the Pixel 3, so hope it stays like that!
benj! said:
Obviously quite subjective, but the camera appears to be opening faster for me when double clicking power. There was also a Google Camera update from the Play Store this morning, so could have been that as well, but this has been a major bug bear of mine since getting the Pixel 3, so hope it stays like that!
Click to expand...
Click to collapse
Def the cam app I noticed too and I'm on Jan update, it's nice tho!
I installed the April update to fix the flashing bug of the ambient display, bit it is still there. Any body else having this issue? Also, is there any fix for this?

General Root seems to be broken on December update / don't flash until it's solved

There is some talk in the P6 race to brick Telegram group, it seems that the december update is causing root to fail.
So until this is fixed/solved, DO NOT UPDATE IF YOU WANT TO RETAIN ROOT.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oh no topjohnwu you didnt
ne0ns4l4m4nder said:
Oh no topjohnwu you didnt
Click to expand...
Click to collapse
He is working for the enemy now, was only a matter of time for problems to arise since he already stopped supporting MagiskHide at the behest of Google^^
Maybe Magisk just needs an update, maybe we have a bigger problem, we'll see
Nah, he'll find root or another Magisk developer will.
Cant we flash a patched stock boot image after the problem is solved?
As OP stated, do not update to December if you want to keep root. I did before I checked forums and lost root. Rolling back to November to hopefully regain access to root.
bb709394 said:
As OP stated, do not update to December if you want to keep root. I did before I checked forums and lost root. Rolling back to November to hopefully regain access to root.
Click to expand...
Click to collapse
Please report back if its possible to roll back
I don't see any update when I check for update on my Pixel 6.
Do I need to something to get the update? I ma not rooted and hence do not worry about rooting.
bb709394 said:
As OP stated, do not update to December if you want to keep root. I did before I checked forums and lost root. Rolling back to November to hopefully regain access to root.
Click to expand...
Click to collapse
Tread carefully, someone tried dirty flashing which then required a clean flash.
cd993 said:
Tread carefully, someone tried dirty flashing which then required a clean flash.
Click to expand...
Click to collapse
Yup, dirty flashed failed and requiring a clean flash. Good learning experience and lesson for me, don't jump the gun with the newest updates.
Assumptions made when I flashed December update on 4A 5G without any problems... c'est la vie.
bb709394 said:
Yup, dirty flashed failed and requiring a clean flash. Good learning experience and lesson for me, don't jump the gun with the newest updates.
Assumptions made when I flashed December update on 4A 5G without any problems... c'est la vie.
Click to expand...
Click to collapse
Yeah I would have held off rooting, as whilst sideloading the OTA I read that root wasn't working... oh well, a fix will come soon I'm sure
i didnt read this forum before flashing, now im stuck on a screen with the google logo and a loading bar. is my phone ****ed?
does anyone get corrupted data and stuck on google logo? any help?
Lainey52900 said:
i didnt read this forum before flashing, now im stuck on a screen with the google logo and a loading bar. is my phone ****ed?
Click to expand...
Click to collapse
You'll likely have to use the Google reset to factory process to ever use the phone again. I haven't rooted my Pixel 6 yet, though, so I can't confirm. But that's how I fixed a bad Pixel 5 update.
XNine said:
You'll likely have to use the Google reset to factory process to ever use the phone again. I haven't rooted my Pixel 6 yet, though, so I can't confirm. But that's how I fixed a bad Pixel 5 update.
Click to expand...
Click to collapse
what google reset?
Vio281 said:
what google reset?
Click to expand...
Click to collapse
Google Pixel - Update and Software Repair
Need a USB cable and Chrome (I think, never used a different browser for it).
Again, I can't confirm this works but it's just an educated guess
XNine said:
Google Pixel - Update and Software Repair
Need a USB cable and Chrome (I think, never used a different browser for it).
Again, I can't confirm this works but it's just an educated guess
Click to expand...
Click to collapse
just try it, only work up to google 5
Okay, so for anyone else here who tries to root using the December patch and gets stuck on the Google logo screen, here are the steps I took to fix it:
1. Hold down the power button until the phone turns off
2. Enter fastboot via holding down the power button and volume down
3. Attach a usb cable to a computer, download the factory image zip, then extract it
4. Once extracted, double click on "flash-all.bat," this will reflash every single component of the image to your phone and once it's done, will reboot and should boot as if nothing ever happened.
Lainey52900 said:
Okay, so for anyone else here who tries to root using the December patch and gets stuck on the Google logo screen, here are the steps I took to fix it:
1. Hold down the power button until the phone turns off
2. Enter fastboot via holding down the power button and volume down
3. Attach a usb cable to a computer, download the factory image zip, then extract it
4. Once extracted, double click on "flash-all.bat," this will reflash every single component of the image to your phone and once it's done, will reboot and should boot as if nothing ever happened.
Click to expand...
Click to collapse
i got a corrupted image and still stuck on google logo.
Vio281 said:
i got a corrupted image and still stuck on google logo.
Click to expand...
Click to collapse
for anyone running into the same situation i did, I have to use the flash option on the google firmware page to get my phone working again, Thank god...

Categories

Resources