And then there was 5, the beta 5 - Google Pixel 3 XL Guides, News, & Discussion

Q Beta Folks,
Time to rejoice, its out!!
https://developer.android.com/preview/download.html
Let's see what's not working...root et al
Update:
So, I flashed the image I downloaded for my pixel3xl. All good so far! Few notables for me:
1. The animations are super smooth. I somehow tolerated through bad animations in beta 4. No more!! I am seeing significant performance improvements compared to Beta 4!
2. Override force dark in dev options works now and not force closing the settings app. Many apps are dark. Some notable exceptions are gmail, whatsapp, hangouts, google fi etc
3. The root works fine.
4. Most important of all: That nagging super white boot animation is gone! It now follows the dark theme setting and is completely black!! What a relief!! Thanks a ton Google for this alone!!
5. A quick settings button is added for Dark theme. Nice! You can now toggle it quickly for some of those pesky apps which behave weird with forced dark mode.
I will keep editing this post in case I find something worth sharing.

Does anyone know if the same procedures that were used to root Q4 work for Q5?
Sent from my Pixel 3 XL

Eudeferrer said:
Does anyone know if the same procedures that were used to root Q4 work for Q5?
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Works just fine. Updated and rooted in short time.

What the hell is new? ?

Do you have to flash back the stock boot.img before updating?

Sunnyschlecht said:
Do you have to flash back the stock boot.img before updating?
Click to expand...
Click to collapse
no, I was using root stock boot image and updated thru phone, grabbed new boot img rooted it rebooted phone, saw that everything was fine, then I booted into bootloader and flashed the new rooted stock boot image and booted up normally.

Anyone want to share a magisk ready boot for the lazy?

arrrgh said:
Anyone want to share a magisk ready boot for the lazy?
Click to expand...
Click to collapse
Here you go.
https://mega.nz/#!Bt1nEALa!mXmp1GNKshVFGCyZSP9EVTtTvMbaDNwpy7NeH_lCBoU

Somehow I'm having issues when flashing the patched image. I'm just using fastboot flash boot_a and boot_b with the image. It just gets to the loading screen and doesn't boot. Any recommendations?

Step x step root instructions?
Looked in the beta 4 thread, but couldn't find rooting or TWRP install instructions anywhere. Apparently it works on beta 5 as well. Could someone post them or a link to them?
Tia

Can someone confirm if the Chase Bank app is working on rooted Q5?

Anyone seeing an issue where if you are using a third party launcher and click on the recent app button you cycle between a regular preview and a huge preview of the apps?
{
"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"
}
Sent from my Pixel 3 using Tapatalk

Looks like Beta 5 has been pulled for all devices, just like the first round of Beta 4.
Sent from my Pixel 3 XL using Tapatalk

santod040 said:
Looks like Beta 5 has been pulled for all devices, just like the first round of Beta 4.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Is that only the OTA installations issues or are the beta images have been pulled as well? I still see them available for download.

devsk said:
Is that only the OTA installations issues or are the beta images have been pulled as well? I still see them available for download.
Click to expand...
Click to collapse
Just the OTA
Sent from my Pixel 3 XL using Tapatalk

I guess I got lucky. I was able to download OTA and installed it without problems.
Sent from my Pixel 3 XL

So, I flashed the image I downloaded for my pixel3xl. All good so far! Few notables for me:
1. The animations are super smooth. I somehow tolerated through bad animations in beta 4. No more!! I am seeing performance improvement compared to Beta 4!
2. Override force dark in dev options works now and not force closing the settings app. Many apps are dark. Some notable exceptions are gmail, whatsapp, hangouts, google fi etc
3. The root works fine.
4. Most important of all: That nagging super white boot animation is gone! It now follows the dark theme setting and is completely black!! What a relief!! Thanks a ton Google for this alone!!

devsk said:
So, I flashed the image I downloaded for my pixel3xl. All good so far! Few notables for me:
1. The animations are super smooth. I somehow tolerated through bad animations in beta 4. No more!! I am seeing performance improvement compared to Beta 4!
2. Override force dark in dev options works now and not force closing the settings app. Many apps are dark. Some notable exceptions are gmail, whatsapp, hangouts, google fi etc
3. The root works fine.
4. Most important of all: That nagging super white boot animation is gone! It now follows the dark theme setting and is completely black!! What a relief!! Thanks a ton Google for this alone!!
Click to expand...
Click to collapse
How did you root?Did you have to clean wipe from previous beta to 5 or installed ota then follow the magisk/root procedures all over again?

Jiggs82 said:
How did you root?Did you have to clean wipe from previous beta to 5 or installed ota then follow the magisk/root procedures all over again?
Click to expand...
Click to collapse
I just flashed the beta5 image without -w flag in flash-all.sh from bootloader. Booted normally. I then extracted boot.img from the image zip, fed it to Magisk and asked it to patch it. After that I flashed the patched boot.img from bootloader using fastboot, and got the root. No need to clean wipe. You keep your apps and data.

devsk said:
I just flashed the beta5 image without -w flag in flash-all.sh from bootloader. Booted normally. I then extracted boot.img from the image zip, fed it to Magisk and asked it to patch it. After that I flashed the patched boot.img from bootloader using fastboot, and got the root. No need to clean wipe. You keep your apps and data.
Click to expand...
Click to collapse
Oh ok thx, I did installed the ota regularly from beta 4 with magisk installed/ rooted , so I will try the other stuff and see if I can still boot fine wish me luck ???

Related

[Toolkit] Wug's Nexus Root Toolkit v2.1.4 [Updated 01/16/16]: Nexus 7 (2013) Thread

Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"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"
}
Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}
I can't find 1.6.6 it still says "Version 1.6.6 coming soon, ETA = 07.28.2013"
Thanks.
ashik992 said:
I can't find 1.6.6 it still says "Version 1.6.6 coming soon, ETA = 07.28.2013"
Thanks.
Click to expand...
Click to collapse
Maybe try clearing browser cache. Here are some external mirrors:
Mediafire: [redacted]
Dev-host: [redacted]
Enjoy! ^_^
{{ WugFresh }}
Thx Wug! I was wondering if you were going to update the toolkit to work with flo, and BAM! Here it is! Love your work, hope you keep at it. :good:
I did not chose twrp
I use 1.66 to root my nexus 7 (2012) and I did not check the (also flash custom recovery) first pass was pushing temporary twrp, and second it flash the twrp.
Why? I get a real problem with twrp with the 4.3 update, so I did not want it in my device.
Is this a bug in the toolkit? or there is a reason why the twrp is push without asking to flash?
Still the best toolkit I ever use.
You may want to change the main body font. It's almost impossible to read on the xda app with the dark theme selected
prshosting.org
Thanks for your work. I first ran and used the "raw driver" install. Went to step 3 and ran the "check". "Success"! When installing Root & Recovery, it gets to the point where it says pushing root files to device, but when it's supposed to boot into TWRP, it boots into system "android man with red exclamation mark on his belly" mode. Tried it twice with the same result. Any ideas? I did notice that in Device Mgr "portable devices" isn't showing at all. However in Prompt mode, an "adb devices" shows device serial #. It's as if TWRP wasn't flashed correctly.
melfunn said:
Thanks for your work. I first ran and used the "raw driver" install. Went to step 3 and ran the "check". "Success"! When installing Root & Recovery, it gets to the point where it says pushing root files to device, but when it's supposed to boot into TWRP, it boots into system "android man with red exclamation mark on his belly" mode. Tried it twice with the same result. Any ideas? I did notice that in Device Mgr "portable devices" isn't showing at all. However in Prompt mode, an "adb devices" shows device serial #. It's as if TWRP wasn't flashed correctly.
Click to expand...
Click to collapse
Same issue I'm having.
Thanks for the app! Unlocking went fine, I'm hesitant to root if it's going to leave me with TWRP even if I leave that field unchecked, anyone else have the same problem as Lachaine? Or has anyone successfully gained root and maintained stock recovery with this?
funkbucket007 said:
Same issue I'm having.
Click to expand...
Click to collapse
Please try enabling this option:
Cheers.
{{ WugFresh }}
Thanks for all your hard work on this, and for sharing it with the community!! It's great having multiple options!!! I didn't use this, but just wanted to say thanks for building this and freely sharing it!!!! It's devs like you that make XDA such a great community to be a part of!!!
SwiftKey'ed from my White Sprint Note 2 using XDA Premium
WugFresh said:
Please try enabling this option:
Cheers.
{{ WugFresh }}
Click to expand...
Click to collapse
Check that option and start over with the root process?
I'm having the same problem. Made the changes in setting and no difference.
jsnietka said:
I'm having the same problem. Made the changes in setting and no difference.
Click to expand...
Click to collapse
Same here.
Sent from my SAMSUNG-SGH-I317 using xda premium
---------- Post added at 02:50 PM ---------- Previous post was at 01:53 PM ----------
k5mitch said:
Same here.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
jsnietka said:
I'm having the same problem. Made the changes in setting and no difference.
Click to expand...
Click to collapse
Third time is a charm.:good:
k5mitch said:
Same here.
Sent from my SAMSUNG-SGH-I317 using xda premium
---------- Post added at 02:50 PM ---------- Previous post was at 01:53 PM ----------
Third time is a charm.:good:
Click to expand...
Click to collapse
Are you saying it finally worked?
I've done it twice same lil dead android with the red triangle.
Guess I'll try again
Unlocked, rooted and installed TWRP. No problems.
Thanks!
feron said:
Are you saying it finally worked?
I've done it twice same lil dead android with the red triangle.
Guess I'll try again
Click to expand...
Click to collapse
ODD.. third time it worked... lol
feron said:
ODD.. third time it worked... lol
Click to expand...
Click to collapse
Well after I checked the option wug suggested I closed the program and re-started it. Walah it worked.
Sent from my SAMSUNG-SGH-I317 using xda premium
k5mitch said:
Well after I checked the option wug suggested I closed the program and re-started it. Walah it worked.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Yes don't forget to restart the toolkit before trying again. Worked for me when I did. Thanks wug!
Having an issue. Stock build# is JWR66N but is not listed, so i choose the closest one, JWR66V. So far it installed the adb drivers but fails on the Full Driver Test and Checking ADB Status. The device shows up perfectly now in DM, as a Nexus7, so the drivers have a clean install. Rebooted 2-3 times already. I can go to the adb command line and its installed but not sure why the app or PC doesn't see it setup right? I cant continue to the next steps if adb is not right...lol

[Q&A] Android Lollipop Stock Factory Image and more

Q&A for Android Lollipop Stock Factory Image and more
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
WAITING.....
Eagerly Waiting for the Multirom Flashable ZIP...
Cannot leave my Daily driver
i have error with the zip, i cannot start beacuse have the error "google play services its stopped"
What's wrong with the Play Services?
{
"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"
}
Sent from my Nexus 5 using XDA Free mobile app
touch not working
after successfully upgrading
touch input doesn't work. all other keys (sound, power) works
what's wrong?
Google services don't work..
I am stuck in setup process at screen that says google play services has stopped. I can't get into setting screen to enable usb debugging and now my pc won't open explorer to view files so I can drag anther file on to flash. I am stuck can anyone point me in the direction of what do next?
I can get into TWRP, but there's no way for me add a file to flash.
Solution: don't use a ZIP
Fastboot straight from Google like it was intended to be installed. Zero issues, all apps downloading and not a single force close. Everything that works works.
i already installed this and wow its amazing so far so good not single error...
Flashing this the correct way (fastboot w/ Google's hosted images), is there a valid way to get root? I thought SuperSU v2.14 was supposed to be it but it didn't do the trick for me.
@dekefake
I installed your nandroid backup - yet I cannot find the Mail App and I can not add an Exchange account....
styl-3r said:
@dekefake
I installed your nandroid backup - yet I cannot find the Mail App and I can not add an Exchange account....
Click to expand...
Click to collapse
I now installed the original ROM - yet my radio is not working. Not in the original ROM, nor in your nandroid backup.
But I noticed, that with your backup the icons are smaller. Where did you change this?
I installed thru fastboot and not a single error or crash until now ..love this lolipop
2 hours of screen on time still my bat is 45%
That nandroid image bricked my phone
I now have IMEI 0.
zip file cant work
When I boot up after flashing Lollipop for the first time, it says Google Play Services has stopped and I cant get passed setup
SilkyJohnson said:
Solution: don't use a ZIP
Fastboot straight from Google like it was intended to be installed. Zero issues, all apps downloading and not a single force close. Everything that works works.
Click to expand...
Click to collapse
I'm going to second this, you own a nexus for a reason.
Running smooth since Friday morning not a single crash or force close.
Sent from my Lollipop Nexus5
Email app constantly crashes, just about the only issue I got
Sent from my Nexus 5 using XDA Free mobile app
styl-3r said:
I now installed the original ROM - yet my radio is not working. Not in the original ROM, nor in your nandroid backup.
But I noticed, that with your backup the icons are smaller. Where did you change this?
Click to expand...
Click to collapse
Changed DPI to 380. DPI=480 burns my eyes
styl-3r said:
That nandroid image bricked my phone
I now have IMEI 0.
Click to expand...
Click to collapse
Restore your phone with a factory image should resolve your issue. Dont know why you face it.
chumfattyyi said:
When I boot up after flashing Lollipop for the first time, it says Google Play Services has stopped and I cant get passed setup
Click to expand...
Click to collapse
If you used the zip file, I know, it's a bug i can't fix. Seems to be related to java but dont know.
Has anyone converted a user app to system? I would assume if I move this folder and set permissions.. It would work.... Right?
Hammerhead | L Developer Preview Final
dEris said:
Has anyone converted a user app to system? I would assume if I move this folder and set permissions.. It would work.... Right?
Hammerhead | L Developer Preview Final
Click to expand...
Click to collapse
Didnt tried. Lollipop apps is now a gorgeous mess x)

[ROM][Flo][7/5/15] - Stock Rooted 5.1.1 - LMY48G - Root and BusyBox only!

AS the name implies this is a stock rooted Android 5.1.1 - LMY48G Lollipop ROM!
Features
100% Stock
Rooted / Powered by SuperSU by @Chainfire!
Busybox
FSTRIM on install
Zip Aligned
No other edits
Notes:
Should update bootloader. It is attached as a flshable ZIP.
First boot is a loooooooooooong time! About 5 to 7 minutes!
You must be on Latest TWRP to enjoy this ROM. No other recoveries supported however they may work.
Install:
Copy ROM to storage
Reboot to TWRP recovery
Factory Reset (no other wipes needed)
Flash ROM
Reboot and Profit!
Troubleshooting
If you get no status bar reboot to recovery and clear all cache. If that doesn't work try flashing the factory image then flash TWRP again and then this ROM.
Getting Symlinks failed during install? Make sure /system is unchecked in TWRP mounts
Problems with internal storage? Look at THIS POST for fix by @freakzapster
{
"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"
}
If you appreciate my time and effort please consider a small (or large) donation
A little bit goes a long ways!
Please hit Thanks!
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed​
Sharing Policy
You are free to use this ROM or any part of this ROM any way you like as long as you give proper credit!
Consider this your permission! Please do not PM me asking if its OK to build off this ROM. Permission granted!
Hit Thanks!
Looks like the Nexus Trolls are at it again! In case you dont know the trolls are jealous hateful people with no skills that go around rating everyone's thread 1 star. I really kind of feel sorry for these sad little creatures One day they may seek the therapy they need (and move out of there parents basement).
But untill then...
Can I get everyone to thank the Opening Post and rate it 5 stars?
Oh snap! Donation coming your way when I get paid
scrosler said:
AS the name implies this is a stock rooted Android 5.1.1 - LMY47V Lollipop ROM!
Features
100% Stock
Rooted / Powered by SuperSU by @Chainfire!
Busybox
Init.d Support
FSTRIM on install
Zip Aligned
No other edits
Notes:
Should update bootloader. It is attached as a flshable ZIP.
First boot is a loooooooooooong time! About 5 to 7 minutes!
You must be on Latest TWRP to enjoy this ROM. No other recoveries supported however they may work.
Install:
Copy ROM to storage
Reboot to TWRP recovery
Factory Reset (no other wipes needed)
Flash ROM
Reboot and Profit!
Troubleshooting
If you get no status bar reboot to recovery and clear all cache. If that doesn't work try flashing the factory image then flash TWRP again and then this ROM.
Getting Symlinks failed during install? Make sure /system is unchecked in TWRP mounts
Problems with internal storage? Look at THIS POST for fix by @freakzapster
If you appreciate my time and effort please consider a small (or large) donation
Did you know that there have been over 20,000 Stock Rooted ROMS downloaded just since Android 5.0.0? Thats not counting every version before 5.0.0!
Please consider donating that way I can focus on making new ROMS and always bringing you the latest versions of Android FIRST!
A little bit goes a long ways!
Please hit Thanks!
Download HERE!
​
Click to expand...
Click to collapse
Been waiting to give this a test drive...
Cheers...
i flashed the factory image thru flashfire.. and viola.. my root still there
Sent from my H940 using XDA Premium 4 mobile app
Dirty flash over Scott's 5.1 with cache / Davlik clear appears to work fine.
My magnetic screen off sensor is not working after the update. Flashed this zip but I'm quite sure it's not the problem of the zip. Anyone else?
paulbonner said:
Dirty flash over Scott's 5.1 with cache / Davlik clear appears to work fine.
Click to expand...
Click to collapse
Worked for me too. Thanks Scott! :good:
The Download site seems to be down at present.
yonster said:
The Download site seems to be down at present.
Click to expand...
Click to collapse
Not for me. Just downloaded and flashed fine
-> Sent from my mind to your screen
mindmajick said:
Not for me. Just downloaded and flashed fine
-> Sent from my mind to your screen
Click to expand...
Click to collapse
Thanks. Downloading now through a VPN. The site didn't seem to like my IP.
Trolls lost! lol
Rated thread and Thanks left. I was happy to return the N7 back to you but i'm missing it already....lol
I did pick up the LG GPad 7.0 from Sprint for free but its not even close to the N7. Enjoy the rom everyone and thanks again for your work Scott
ImjuzCY said:
My magnetic screen off sensor is not working after the update. Flashed this zip but I'm quite sure it's not the problem of the zip. Anyone else?
Click to expand...
Click to collapse
Nope, everything's ok here. So it seems not be ROM related.
paulbonner said:
Dirty flash over Scott's 5.1 with cache / Davlik clear appears to work fine.
Click to expand...
Click to collapse
it works for me too!!!
All good here. Nice job.
Thanks guys, we are beating the trolls :good:
Thanks Scott you always have your Roms up quick need to get this flashed I just flashed 5.1 not a week ago finally got the notice for update lol
Any tried whether CWM is ok to flash this rom?

[OOS][Oreo] Enable Google Daydream VR Support

For Oxygen OS - 5.1.3 Oreo on Oneplus 5T.
Flash in TWRP after making a backup.
Please read all info below.
{
"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"
}
!!! CAUTION !!!
Use at your own risk. Backup before flashing.
I am not responsible for bricked devices,
thermonuclear war or your monkey dancing samba!
IMPORTANT INFO:
Flashing
The installer changes one file. It overwrites \system\etc\permissions\handheld_core_hardware.xml
with an updated version to enable the Google Daydream support.
Removing
There is also the remover ZIP. It restores the stock OOS 5.1.3 permission file.
After flashing - get ready
You wiped your cache and dalvik and boot the device.
Go to your application list and show system apps.
Delete cache and data of the Play Store app so Daydream is
downloadable via Play Store. Open Play Store,
do not forget to set your previous Play Store configuration and install:
• Daydream
• Daydream Keyboard
• Google VR Services
Some reported that setting to skip all intros in Daydream developers options
fixed problems that occured.
Start, set the other config which is needed and try. For me it works fine.
The only thing that is a bit sad is that the 5T with full HD gives a not very sharp display view - it is grainy.
๏[-ิ_•ิ]๏
Does it work on 5.0.3?
Also, does it trigger the 'safetynet'?
lockywolf said:
Does it work on 5.0.3?
Click to expand...
Click to collapse
Actually the file did not change for 5.0.3, but I changed the ZIP filename to clearify.
lockywolf said:
Also, does it trigger the 'safetynet'?
Click to expand...
Click to collapse
I don't think so.
By the way; it is a tiny mod that does no heavy system tweaking.
I made it just for convenience so users do not need to use a root explorer and text editor for the changes.
Thank you.
Just FYI, it's not working in Oreo Resurrection Remix.
I can open Daydream without issue.
But as soon as I put my OP5T into the headset, the OP5T hard reboots.
I attached a logcat in case anyone is interested.
CZ Eddie said:
Thank you.
Just FYI, it's not working in Oreo Resurrection Remix.
I can open Daydream without issue.
But as soon as I put my OP5T into the headset, the OP5T hard reboots.
I attached a logcat in case anyone is interested.
Click to expand...
Click to collapse
This is happening to me as well on AICP. Wanting this to work lol. Please keep me updated if you find anything out!
CZ Eddie said:
Just FYI, it's not working in Oreo Resurrection Remix.
Click to expand...
Click to collapse
bschmidy10 said:
Please keep me updated if you find anything out!
Click to expand...
Click to collapse
See, I am not a real dev... just some guy with basic knowledge. I updated the ZIP and made two new for the ROMs you use.
Try them, but read the OP/CAUTION section please.
The attached ZIPs contain the modified file from your ROMs which are different in one line compared to OOS.
Plus I added a mod for the build.prop to maybe make it work.
If all fails I guess this try was just an interesting waste of time,
and someone more advanced would have to figure out a possible solution.
•••
Thank you!
I'm sorry but my Resurrection Remix Oreo still forced rebooted when I put the phone into the headset. I attached another logcat if you're interested.
CZ Eddie said:
Thank you!
I'm sorry but my Resurrection Remix Oreo still forced rebooted when I put the phone into the headset. I attached another logcat if you're interested.
Click to expand...
Click to collapse
As I wrote I can not help any further.
I installed Google VR keyboard, Daydream, VR services etc. and tested some apps under OOS 5.0.3, but all without VR hardware - I do not own the headset/controller. I enabled developer options on Daydream and skipped all intros, read that elsewhere.
I've got the same problem, RR 8.0.1. Logcat implies that the ACore process lacks permissions to access the VR hardware, and crashes upon attempting it, taking the entire systemui and all of its children with it.
I'm in the process of experimenting and seeing if it's possible to grant those permissions somehow..
Anybody got it working? I saw the set today at a store and thought about buying it...
This has always worked for me: https://www.xda-developers.com/force-daydream-vr-compatibility/
never needed to change the device name, just added the 2 lines and rebooted. Daydream apps download and update via playstore as well.
OTA Updates
Does unlocking bootloader, flashing twrp and installing this, cause problems with OTA Updates or something?
aschi2403 said:
Does unlocking bootloader, flashing twrp and installing this, cause problems with OTA Updates or something?
Click to expand...
Click to collapse
Did you face problems with OTA? I will update this if I find the time.
Gesendet von meinem ONEPLUS A5010 mit Tapatalk
t-ryder said:
Did you face problems with OTA? I will update this if I find the time.
Gesendet von meinem ONEPLUS A5010 mit Tapatalk
Click to expand...
Click to collapse
No I din't face any, I just wanted to know if there are known problems before I install this.
But now I have a new Question. I thought to not mess around with OTA as I read on some XDA-Thread that TWRP might keep official OTA from working, I would just unlock the bootloader and then boot into TWRP with "fastboot boot recovery.img", flash this zip and reboot into stock OOS with this guide https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592 on.
But then on the twrp Website I read that "swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel" so my question is, can I flash this zip without messing around with OOS, I don't really want to install a custom kernel, because for now I just want the stable stock rom.
aschi2403 said:
No I din't face any, I just wanted to know if there are known problems before I install this.
But now I have a new Question. I thought to not mess around with OTA as I read on some XDA-Thread that TWRP might keep official OTA from working, I would just unlock the bootloader and then boot into TWRP with "fastboot boot recovery.img", flash this zip and reboot into stock OOS with this guide https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592 on.
But then on the twrp Website I read that "swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel" so my question is, can I flash this zip without messing around with OOS, I don't really want to install a custom kernel, because for now I just want the stable stock rom.
Click to expand...
Click to collapse
I tried it and I didn't face any of my concerns, but I'm on OxygenOs 5.1.2 and after flashing this, wiping cache, then reboot. Daydream App after a long black screen shows me, that my device isn't compatible with Daydream. Did I do something wrong or is it because of the OxygenOS Version?
EDIT: see post #19
I just bought a Daydream Set (v1) for like 20$ second hand online. Will report regarding further testing when the set has arrived.
Updated for Oxygen OS 5.1.3
Got my headset and all works fine. The image is a bit grainy because 5T has only full HD.
No need for an installer with build.prop changes. I tested the system changes and updated the installer and remover.
If you have tried the old installer/enabler you may restore your build.prop using a root file explorer. It is located in /system (.bak file).
Have fun.
M.Sami said:
never needed to change the device name, just added the 2 lines and rebooted.
Click to expand...
Click to collapse
Yes, you are right.

New update now live (MR1 -Oreo 8.1)

{
"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"
}
Not included in the changelog is the addition of a feature from Paranoid Android, locking recent tasks! And multitouch has also been fixed
Update is a rollout so you may not have it yet.
Factory images now live, check out @linuxct post here
If you come across any bugs please be detailed about it and leave bug reports.
Anyway of installing via TWRP so I don't loose root... Haven't really flashed a/b phones.
Wow, just when I finished wiping all my data and installing a Resurrection Remix. Ironic.
Is there any way to extract the camera apk to install it in my current ROM?
guys please i need help. has anyone successfully installed razers stock img files?
After the update, my sim card is no longer being detected. I tried restarting, shutting down, and turning back on. It was working perfectly fine before I restarted after updating.
Edit: It may be the sim card actually died. I tried it on another phone and it doesn't work there either. So it seems like coincidence that it died after the update.
Hmmmmm update fails for me. Not rooted bootloader locked. Error couldn't update installation issue helpfull error.
Fastboot images now live: https://developer.razer.com/razer-phone-dev-tools/factory-images/
Direct link: https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-5038.zip
Taking a hell of a long time to install.... I'm using Snap Camera these days, which is great, I wonder what the new portrait mode is like..... But I can't see me changing back to stock now..
What is the best way to update when I'm rooted and have TWRP installed?
SeriousFlash said:
What is the best way to update when I'm rooted and have TWRP installed?
Click to expand...
Click to collapse
Use the factory images posted here
My update also fails when I'm not rooted and have my bootloader locked
My may update is now installing itself. I do wish it had prompted me rather than having to run a manual update as I was just going through some setting and clicked the update in error.
Updated and noticed loads of fixes, however, Bluetooth is now a complete no go with my car stereo. Sometimes I manage to actually connect it and can play music by pressing play on the phone but no song titles are shown on the car and music playback controls don't work at all... Has anyone had a similar issue or an idea as to what's wrong?
linuxct said:
Use the factory images posted here
Click to expand...
Click to collapse
How would I go about doing that then?
Make sure you go to Settings, system and Razer Preferences and Disable the Share Data again... it gets turned on with the update.
Got the OTA this Morning on my Three branded device and installed without issue.
Nice to see a timely release of the monthly security fixes - is this a benefit of Project Treble support ?
ccjack said:
Anyway of installing via TWRP so I don't loose root... Haven't really flashed a/b phones.
Click to expand...
Click to collapse
Just use the factory images but before flashing, edit the flash_all.bat go to the line that reads %fastboot_cmd% erase userdata" and put a pound "#" sign before the line so that adb ignores that line. Also do the same at the end of the script where you see "%fastboot_cmd% reboot". Doing the following will stop the script from formatting your data partition and keep your phone in download mode after the flashing process. Now you can do the "fastboot boot twrp-whatever-filename.img" and boot to twrp like you were to root like before and once in twrp, flash twrp zip and magisk zip same as before. Everything should work fine now.
Again. Make sure you edit the bat file so the factory images dont factory reset your data partition.
The update took 45 minds to install, it was very slow...
Confirm that Multi touch is fixed now
Razer has introduced the portrait mode, but I still prefer Gmod or
Nokia 's stock camera app..
Yet these updates are welcome...
Is there still no way to update and keep twrp?
navin2max said:
The update took 45 minds to install, it was very slow...
Confirm that Multi touch is fixed now
Razer has introduced the portrait mode, but I still prefer Gmod or
Nokia 's stock camera app..
Yet these updates are welcome...
Click to expand...
Click to collapse
Where I can fine a Nokia cam app?

Categories

Resources