Related
Today I rebooted my device into bootloader mode to check some stuff and noticed that Secure Boot display "no RPMB" next to "Enabled". What does it mean?
Banan PL said:
Today I rebooted my device into bootloader mode to check some stuff and noticed that Secure Boot display "no RPMB" next to "Enabled". What does it mean?
Click to expand...
Click to collapse
Did you recently receive a refurbished device? "No RPMB" in effect means your bootloader will automatically re-lock itself on reboot. I believe it has something to do with a replaced main board.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Did you recently receive a refurbished device? "No RPMB" in effect means your bootloader will automatically re-lock itself on reboot. I believe it has something to do with a replaced main board.
Click to expand...
Click to collapse
Yep, I received it yesterday, they replaced motherboard. So it's mean no more mods? That's the reason why I bought this device. Can it affect DRM protected multimedia, because I can't watch videos in Play Movies app?
Sent from my Nexus 5X using XDA Labs
Banan PL said:
Yep, I received it yesterday, they replaced motherboard. So it's mean no more mods? That's the reason why I bought this device. Can it affect DRM protected multimedia, because I can't watch videos in Play Movies app?
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
There's a temporary workaround if you're a stock rooted user:
Here's a reddit link regarding a workaround:
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
However, this isn't helpful if you're a regular custom rom user as you'll notice in the details.
As for DRM, I think so. I have been looking for confirmation about DRM being impacted by this "No RPMB" status. I've only seen one other person outright mention this. It's hard to find users who get this issue and even harder to get them to respond on my inquiry on whether they can use DRM apps. What issue are you seeing with Play Movies? Can you open the app? Or are you given an error message of any kind? I'm interested from the troubleshooting perspective so that I can help ID when others have the same issue. Also, can you confirm this affects other multimedia apps with DRM protection? I was thinking that Hulu, Netflix, HBO would be apps that utilize DRM if you have subscriptions.
Sent from my Nexus 5X using Tapatalk
I don't care much about custom OS, at least for now. I can open Play Movies browse feed and library, but it ain't play any video (Couldn't fetch license (error -1)). Unfortunately I don't have subscriptions in these services, but I used local TV streaming app that uses DRM and it showed error 203 (whatever that means). I tried also watch movies from Google's app on YouTube, no luck.
Sent from my Nexus 5X using XDA Labs
Hi there, same case, no rpmb after replacing motherboard, Netflix won't start (error 500 device failure). Tried with stock but now PureNexus rom.
Sent from my Nexus 5X using Tapatalk
send phone on warranty "No possibility to use value based on drm license" after LG should fix your mb
tuningsea said:
send phone on warranty "No possibility to use value based on drm license" after LG should fix your mb
Click to expand...
Click to collapse
Thanks for the advise, however I want to find a way to create this Rpmb at home, for users who warranty has gone, still looking..
Sent from my Nexus 5X using Tapatalk
Netflix norpmb
can anybody of you with the norpmb issue test the netflix app again ? after the oreo update its working again for me. confused
kmike243 said:
can anybody of you with the norpmb issue test the netflix app again ? after the oreo update its working again for me. confused
Click to expand...
Click to collapse
I confirm it's working. Has anybody found a different solution for no rpmb from the one posted on reddit?
Inviato dal mio Nexus 5X utilizzando Tapatalk
kmike243 said:
can anybody of you with the norpmb issue test the netflix app again ? after the oreo update its working again for me. confused
Click to expand...
Click to collapse
Netflix app will crash few times, try to hide with Magisk Btw. Re open few times, like 10 and login. Then you will be redirected to the homepage.
Envoyé de mon Nexus 5X en utilisant Tapatalk
hi guys, i have the same no rpmb model
how do i fresh install oreo as the bootloader keeps relocking? is there a way? also i'd like to root!
androidfreak11 said:
hi guys, i have the same no rpmb model
how do i fresh install oreo as the bootloader keeps relocking? is there a way? also i'd like to root!
Click to expand...
Click to collapse
I'm also looking for a solution all the time
but I haven't found one yet
openyourmind said:
I'm also looking for a solution all the time
but I haven't found one yet
Click to expand...
Click to collapse
Unlock bootloader, flash newer version of it and newer radio. Reboot bootloader, unlock it again*, flash rest of the stuff.
*In my case OEM unlock toggle doesn't disable itself after bootloader lock itself. It also stays enabled even after factory reset.
To get root simply flash TWRP instead stock recovery and install SU package of your choice. You can also run customs on locked bootloader and use Jolla's multirom if you want, just keep TWRP installed**.
**Honestly I prefer 4core TWRP modded, it might be life saving one day.
If you use Oreo and want to downgrade it to Nougat or Marshmallow just flash system and vendor in TWRP.
NOTE ABOUT RADIO:
Oreo's radio MIGHT not work on every Marshmallow based ROM (example: XOSP, multibooted Stock - they doesn't detected SIM card also baseband is unknown in my case) it work on CM13, not sure about call quality. It work on every Nougat based without issues.
Sent from my Nexus 5X using XDA Labs
Banan PL said:
Unlock bootloader, flash newer version of it and newer radio. Reboot bootloader, unlock it again*, flash rest of the stuff.
*In my case OEM unlock toggle doesn't disable itself after bootloader lock itself. It also stays enabled even after factory reset.
To get root simply flash TWRP instead stock recovery and install SU package of your choice. You can also run customs on locked bootloader and use Jolla's multirom if you want, just keep TWRP installed**.
**Honestly I prefer 4core TWRP modded, it might be life saving one day.
If you use Oreo and want to downgrade it to Nougat or Marshmallow just flash system and vendor in TWRP.
NOTE ABOUT RADIO:
Oreo's radio MIGHT not work on every Marshmallow based ROM (example: XOSP, multibooted Stock - they doesn't detected SIM card also baseband is unknown in my case) it work on CM13, not sure about call quality. It work on every Nougat based without issues.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
i was able to flash stock rom via fastbook (had to unlock bootloader 3 times, everytime it rebooted, but it worked tho)
only problem, when i install twrp and press reboot phone, it will only boot to twrp! and i have to type in a decription password or something, because i unlocked the bootloader and android should have deleted everything, but didn't cause i would have to reboot for that, but it will only boot in twrp .. so yeah, that's where i got stuck .. any idea?
otherwise i'll resell this thing and maybe get an htc 10 or a nexus 5x with stock mobo
Hi all,
I currently have stock 8.1 installed on my refurbished Nexus 5X with NO RPMB, and would like to install a custom ROM (Pixel2ROM from argraur).
If possible, I prefer NOT to get root. Maybe it helps passing safetynet.
As I understood, I should do following steps:
- Unlock bootloader
- Flash stock ROM. -> Is this step necessary since I already have stock 8.1 installed?
- Flash TWRP
- Reboot directly into TWRP
- Wipe data and cache
- Flash custom ROM
- Flash Magisk or superSU -> Without this step, would TWRP get replaced with stock recovery? Is Magisk or superSU better?
Can you please check if the steps are right, and answer the 3 questions.
Thanks!
EDIT: I tried without flashing the stock ROM nor root. Everything went fine and TWRP remains installed.
Hello I created a thread trying to help with this cases.. If someone with better knowledge see a better option, please say it there to update it..
NO RPMB (how to install TWRP, a new ROM and using Magisk)
Hi Pedro,
what will happen in case of rom update? e.g. Nightly?
ciorci said:
Hi Pedro,
what will happen in case of rom update? e.g. Nightly?
Click to expand...
Click to collapse
Without the magisk part its like you are using a normal rom with a normal boot image, just need to dirty flash the new rom..
With the magisk part it would need to make a new patched boot image..
So at least you will need to extract the new boot image of the new rom file, use it on magisk and patch it, after that I dont know... to my method work the first time it was needed a clean installation, but didn't tried it yet because the new update of my rom developer needed to be a clean installation due to many changes on the rom, so i didn't have opportunity to try update normally but when I do I will update my thread with what to do on that case and if it works..
So it looks like the major feature added is the Google Play assistant, which I don't even use on my phone.
But also, I believe the latest version of YouTube will be the stock app, which I just don't like.
I am rooted, which I realize will go away after the upgrade. But also, I don't have anything installed that requires root really. I wanted to take advantage of some xposed features, but apparently there is no version of the framework that supports nvidia shield tv 5.2?
So is it worth upgrading right now? Has anyone tried it? Anything notable worth upgrading for?
I'm in the same situation (rooted) as you. I tried to update, but I end up in TWRP and I don't know what to do from there. If I boot system it just start up as normal and ask me again to update.
Any ideas? Anyone?
What to do, what to do?
Kickasscowboy said:
I'm in the same situation (rooted) as you. I tried to update, but I end up in TWRP and I don't know what to do from there. If I boot system it just start up as normal and ask me again to update.
Any ideas? Anyone?
What to do, what to do?
Click to expand...
Click to collapse
Most likely have to wait for the developers image .
jionny said:
Most likely have to wait for the developers image .
Click to expand...
Click to collapse
And flash through FlashFire
orificium said:
So it looks like the major feature added is the Google Play assistant, which I don't even use on my phone.
But also, I believe the latest version of YouTube will be the stock app, which I just don't like.
Click to expand...
Click to collapse
I have a stock shield (not rooted), but had backed off the YouTube app to be the old one (the one that works with secondary accounts).
I let it upgrade and it did not force a YouTube update. After it finished, I'm still running YT 1.3.11. So you should be okay there.
Of course other than Google Assistant, I haven't found much new. What I really want is for Google Assistant to work with Google Play Music, but it doesn't do that (yet?).
I'm in the same boat as you guys. Currently rooted and debating the upgrade. I would think that we could update via flash fire if someone knows where the ota is stored once it downloads.
Sent from my Pixel XL using Tapatalk
I hear you guys. I will wait for OTA update to be downloadable or I might even consider returning to stock. I really don't have any use for root now.
FYI, Doesn't work with flashfire.
https://m.imgur.com/a/4ZKy6
n1gh7mar3 said:
FYI, Doesn't work with flashfire.
https://m.imgur.com/a/4ZKy6
Click to expand...
Click to collapse
That's not a developer image right? wouldn't think it would work unless it is the developer image or your bootloader is locked
I got mine to update even though its rooted.
After it finished downloading, it rebooted into twrp and installed the update automatically with no issues.
I did however get some issues after it finished updating.
The recovery/twrp is gone and cant boot into that anymore.
Root is of course gone.
And now im also just getting a black wallpaper in the launcher instead of the default nvidia one.
WisdomWolf said:
I'm in the same boat as you guys. Currently rooted and debating the upgrade. I would think that we could update via flash fire if someone knows where the ota is stored once it downloads.
Click to expand...
Click to collapse
data/data/com.nvidia.ota/app_download
jionny said:
That's not a developer image right? wouldn't think it would work unless it is the developer image or your bootloader is locked
Click to expand...
Click to collapse
I would assume the OTA is a developer image. Since it couldn't get flash fire to work, I reflashed the stock recovery image and applied the OTA, but it kept freezing and after about 10 minutes it would just boot into the original os.
n1gh7mar3 said:
I would assume the OTA is a developer image. Since it couldn't get flash fire to work, I reflashed the stock recovery image and applied the OTA, but it kept freezing and after about 10 minutes it would just boot into the original os.
Click to expand...
Click to collapse
Sorry I meant the developer rooted image that Nvidia usually releases shortly after a upgrade that you can flash over a unlocked bootloader and root and keep root
jionny said:
Sorry I meant the developer rooted image that Nvidia usually releases shortly after a upgrade that you can flash over a unlocked bootloader and root and keep root
Click to expand...
Click to collapse
I totally understand what you mean, I was already on 5.2.0 developer image, so I assume if presented with an OTA it's of the same type.
n1gh7mar3 said:
I totally understand what you mean, I was already on 5.2.0 developer image, so I assume if presented with an OTA it's of the same type.
Click to expand...
Click to collapse
No you have to get that from Nvidias site however last time I checked it was not up yet
n1gh7mar3 said:
I would assume the OTA is a developer image. Since it couldn't get flash fire to work, I reflashed the stock recovery image and applied the OTA, but it kept freezing and after about 10 minutes it would just boot into the original os.
Click to expand...
Click to collapse
you have to flash all the files inside, not only recovery. (nv-recovery-image-shield-atv-5.2.0.zip)
now it worked
Screen flickers
My shield got the latest upgrade (non root) and now my screen flickers from time to time. Any known solution to this issue ?
Tifulb said:
My shield got the latest upgrade (non root) and now my screen flickers from time to time. Any known solution to this issue ?
Click to expand...
Click to collapse
I've seen a few fixes for screen issues, either making sure in advanced display resolution settings things are correct, or disabling/renabling the CEC in settings.
You may want to check out the nvidia geforce forums thread, I'd probably start out middle to last several pages (assuming you read this soon, in a few days you'll just have to take a guess as there will be way more pages) https://forums.geforce.com/default/.../shield-experience-upgrade-6-0-for-shield-tv/
I think there's a post about chroma clipping which may be what yours is doing, but it could be some of the HDR stuff or something with the HDMI or CEC issues for all I know.
Hi,
i have a 2015 Shield (root) with 5.2 image.
I would back to stock image and unroot my shield.
I have download the "nv-recovery-image-shield-atv-5.2.0".
my approach.
*** Prerequisites:
1. Ensure that the bootloader is unlocked (see above step)
*** Flashing instructions:
1. Execute these commands on the host PC:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
Is this the right way?
Thanks!
OTA zip shield 2015 6.0
if someone need:
Original ota zip for Shield TV 2015 (non pro) 5.2 -> 6.0
https://mega.nz/#!BChlSbaR!em9CV5PoRzalWnMWf7iqAj4oVeDQqLhrz_Q1GGXy0Ug
Hello all!
I've gotten too lazy to maintain updating my rooted Pixel XL whenever there's a security patch.
I've re-locked the boot-loader and done a full stock flash from google's stock images, but now i get this warning when it boots up:
"Your device has loaded a different operating system. "
It then boots up fine, barring the fact OTA's still fail, the one thing I was trying to get working.
Any advice?
Thanks in advance.
You skipped flashing the bootloader and radio without those ota will fail.
Am i mistaken in thinking the "flashall.bat" from google does that as well?
Thanks
Edit.
Think i found it, your comment made me watch for the radio and boot-loader when i tried the flash-all batch script again, I believe i Locked the boot-loader before flashing it to stock again.
Unlocked, flashed, re-locked and it appears to be working now.
Thanks!
Help me
Vacross said:
Am i mistaken in thinking the "flashall.bat" from google does that as well?
Thanks
Edit.
Think i found it, your comment made me watch for the radio and boot-loader when i tried the flash-all batch script again, I believe i Locked the boot-loader before flashing it to stock again.
Unlocked, flashed, re-locked and it appears to be working now.
Thanks!
Click to expand...
Click to collapse
Can you help me... I have same problem...
DR3W5K1 said:
You skipped flashing the bootloader and radio without those ota will fail.
Click to expand...
Click to collapse
Can you pls explain on how to do that
Follow the guide for flashing stock images via fastboot and you shouldn't have this problem.
Stop after step 4
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
I also had the same issue on Nexus 6p.. after I realised that I forgot to flash boot.img from stock firmware.. anyway it is resolved...
UI Design Services with Compelling and Engaging User-Experience
Get user-centered UI Design for your mobile app or website.
UI Design services
[New Firmware] 47.2.A.4.45 [G8441] (8 January 2018)
change log? security patch and kernel version have not change
Nope, nothing change. Only one general bug even on locked bootloader, google pay stop working, ctsprofile - false
Fixed by Sony, now gpay work.
russel5 said:
Nope, nothing change. Only one general bug even on locked bootloader, google pay stop working, ctsprofile - false
Fixed by Sony, now gpay work.
Click to expand...
Click to collapse
Is there a new update to fix this? can you share the version number? I get random reboots on 47.2.A.45 UBL, magisk and cts profile false.
Seems like it's still on December patch. Customised MY variant
Sent from my G8441 using Tapatalk
Finally out for customized DE. Is it okey to install? They took their time but I'm still worried
Evzzza said:
Finally out for customized DE. Is it okey to install? They took their time but I'm still worried
Click to expand...
Click to collapse
Just have done in - Disabled PIN, installed Customized DE, enabled PIN - everything seems to be normal, except Oreo is really nice
So I'm still on a DE Oreo rom with unlocked bootloader and magisk, but got the Ota prompt today to x.45..... Can I let it download and install rather than using flashtool?? I've never had it offer an update the official way before heh also now that there's twrp for Pie, is getting magisk back hard after updating to Pie?
OTA won't work with unlocked bootloader. Rooting with magisk is just as easy as always, just use the latest TWRP for xz1c pie.
If you want to keep your data, delete userdata*.sin from the downloaded firmware (and probably should also delete all .ta and persist*.sin if you still have your drm etc. keys) and flash with newflasher (flashtool might also work, I don't know).
Not sure if it will work without a factory reset, probably will, but maybe back up first...
Are you guys also having a slow response from Screen auto brightness? mine gets very dimm and takes, 3,4 seconds to go to a acceptable brightness...
anyone?
rsk_kelkar said:
Is there a new update to fix this? can you share the version number? I get random reboots on 47.2.A.45 UBL, magisk and cts profile false.
Click to expand...
Click to collapse
Was due to a rogue magisk module. All ok now
profyler said:
Are you guys also having a slow response from Screen auto brightness? mine gets very dimm and takes, 3,4 seconds to go to a acceptable brightness...
anyone?
Click to expand...
Click to collapse
Built-in auto brightness has always been ****, I use lux auto brightness, setup your lux values and link manually what light level readings you want the display to be at. You can have that set to auto brightness but I'd suggest setting it to on display wake, no constant polling.
I did update via OTA and no problems so far, but i have one bug, when i want delete a app it's not possible to do it via settings and apps (when i push the button "deinstall" than just nothing happens), i have to use a third-part app.
The auto brightness is a bit stupid, but i read that it have to learn for a while and than it will work better. So i will wait a bit and see if it works better in some days.
This update, whatever it is, always fails to install.
Now here's the catch: When I uninstall Magisk, I no longer am being offered the update! Anyone knows WTF is going on with that? :-O
WalrusInAnus said:
This update, whatever it is, always fails to install.
Now here's the catch: When I uninstall Magisk, I no longer am being offered the update! Anyone knows WTF is going on with that? :-O
Click to expand...
Click to collapse
OTA update does not work with an unlocked bootloader. Flash manually.
vofferz said:
OTA update does not work with an unlocked bootloader. Flash manually.
Click to expand...
Click to collapse
That is not true. All the smaller updates before downloaded and installed without any problems.
WalrusInAnus said:
That is not true. All the smaller updates before downloaded and installed without any problems.
Click to expand...
Click to collapse
Well, that's news for me. Everyone else has stated that OTA update fails with unlocked bootloader.
vofferz said:
OTA won't work with unlocked bootloader. Rooting with magisk is just as easy as always, just use the latest TWRP for xz1c pie.
If you want to keep your data, delete userdata*.sin from the downloaded firmware (and probably should also delete all .ta and persist*.sin if you still have your drm etc. keys) and flash with newflasher (flashtool might also work, I don't know).
Not sure if it will work without a factory reset, probably will, but maybe back up first...
Click to expand...
Click to collapse
And for those of us who do not have DRM-keys, which of those should I keep in?
bofis said:
And for those of us who do not have DRM-keys, which of those should I keep in?
Click to expand...
Click to collapse
Just delete those mentioned files before flashing. You should be fine too.
If you flash the persist sin file, you'll lose android attest key, but I don't think you anyway gain anything by flashing it, so just delete. Probably same with the .ta files - no gain, maybe something to lose. If you flash userdata you lose all your settings (&apps?) - it's like a factory reset.
Some people recommend a reset after a big update, but if you don't want to lose settings and apps, you should at least try if everything works fine.
call recording apps under this firmware update
Dean F said:
[New Firmware] 47.2.A.4.45 [G8441] (8 January 2018)
Click to expand...
Click to collapse
Hi Guys
There were some posts that call recording would not work anymore with Android Pie. Can someone confirm this statement /issue with Android Pie and specifically for this firmware upgrade?
Can someone send me.a direct link to all Firmwares for the pixel 6 pro that I can flash stock Firmwares that is. I need the official Firmwares for all countries
Is this what you are looking for
https://developers.google.com/android/ota
Or the full firmwares https://developers.google.com/android/images, and the December ones that they removed from there Alternate links to December full factory images for .017, .016.A1 & A4, and OTAs for .017 & .016.A1 available.
I'm december FW without bug. If i want to clean flash the next FW what i must to do.
Can i wipe system in recovery or i must use adb/fastboot command ?
Vincent_40 said:
I'm december FW without bug. If i want to clean flash the next FW what i must to do.
Can i wipe system in recovery or i must use adb/fastboot command ?
Click to expand...
Click to collapse
You'll be able to use Official Google Android Flash Tool or the full factory image zip which as always would be available at Pixel 6 Pro Factory Images. Either will fully wipe your device. I don't have firsthand experience with Official Google Android Flash Tool so I don't know if it wipes by default but I know it can or has an option to if it's not default. The full factory images at Pixel 6 Pro Factory Images, without modification, always fully wipes the phone. Make sure and update SDK Platform Tools every month (sometimes earlier version Platform Tools doesn't work correctly and update the Google USB Driver if you're using Windows.
Ok thx i'll try to clean flash with next update with flash tool.
Hope Twrp will be released soon.
Vincent_40 said:
Hope Twrp will be released soon.
Click to expand...
Click to collapse
I wouldn't hold my breath or take any bets on that. So far without TWRP hasn't held anything back.
roirraW edor ehT said:
I wouldn't hold my breath or take any bets on that. So far without TWRP hasn't held anything back.
Click to expand...
Click to collapse
Yeah, about a month or two ago bigbiff said he was working on TWRP for Android 12 in general, but it would be a while. Honestly, haven't used it since the Nexus days. Really haven't missed it at all and probably wouldn't use it even when/if it does come out.
I'm on january security patch and I'd unlock the bL without disable the DM-Verity verification.
Can i root with last Magisk canary directly or do i need to disable DM-Verity ?
Last point, my play protect is uncertified, but it's not important
Vincent_40 said:
I'm on january security patch and I'd unlock the bL without disable the DM-Verity verification.
Can i root with last Magisk canary directly or do i need to disable DM-Verity ?
Last point, my play protect is uncertified, but it's not important
Click to expand...
Click to collapse
Yes, you can root with Canary Magisk 23016 without disabling verity & verification.
Ok i'll try
Thx for your reply