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..
Hello,
I am currently with Freedom Mobile, but my phone was purchased through Rogers, has the open Network Bands to use the Freedom network, and a new P6 Freedom Mobile SIM Card. My phone is also running as HTC_001.
Before modifying my phone and having to re-do everything I may have done in the past:
Can anyone on either Freedom Mobiles network with their stock RUU confirm they have the Wifi Calling option and it works?
To be able to use services of a carrier, like WiFi calling etc, you MUST be using a firmware that came from that carrier. If freedom issue a specific firmware for the m9 you must use it. If they don't and their phones come "network unlocked/debranded", ie using the 401 firmware, then you should be able to access the WiFi etc on any device. Another example is if you want to use tmobile features then you need a tmobile firmware.
So the question you need to find the answer to is "does freedom carrier have a branded firmware for the m9".
You are correct. Based on my research earlier, I came across that same conclusion.
I think the best/only way to test this however, is a) if someone has a latest version of their branded firmware and can check this or b) I get a TWRP restore and install this on my phone (I assume this is possible and not IMEI restricted) or c) I find another way to get to a stock firmware.
I changed my CID back to the Freedom Mobile one and downloaded the stock TWRP backup from the old Canadian Stock ROM thread, but it is either too large or possibly too old and incompatible with my phone.
I had to use ADB commands through computer to restore, and it looked like it would accept. However, the computer was stuck at "unlock phone screen to continue" and TWRP said "MTP enabled."
Those backups are most likely too old. You can try to find a suitable RUU on easy-firmware or you need to contact llabtoofer's RUU service since at the moment there is no freely available RUU for your phone. The links can be found in the FAQ of the ReadMe thread.
Sent from my Motorola XT1572 using XDA Labs
Just a quick update. I ended up aborting this "project" of mine.
Despite using Mac OS, encountering corrupt zip files and other files issues where I would get an 22 RU_HEADER_ERROR, I ended up finding my biggest issue.
My MID was set to OPJA10000, instead of 0PJA10000. This issue caused multiple hours of frustrations. I have now flashed my phone back to stock 4.28.401.3. I will most likely have to reinstall TWRP and restore my previous backup.
On another note, is anyone else unable to find the HTC Mail app in Google Play store? Mine crashes every time I try to reply to emails or create a new one. Google Play Store on the computer shows my M9 is not compatible.
Get rid of Google Chrome. I don't know what's exactly the reason but current chrome versions break the HTC Mail app.
Sent from my HTC One M9 using XDA Labs
Same for me. Not compatible.
Just an update to this.
They released a new version of HTC Mail v10.70.1031252.
Based on quick trials, this has resolved the recent issues regarding HTC Mail and Google Chrome being at the latest version, regarding crashing when creating a new email or replying, but I have not tested it extensively.
I know this should be a new thread with a proper title instead of piggybacking on an old one, so if a mod can create one (or prefers I do), that would be great.
Hi,
I have an XT1789-06, RETEU. I had it unlocked and rooted, but went back to stock without rom. However, bootloader is still unlocked. Got it somehow working to pas SafetyNet and run google pay while on Android 8, but now I OTA-updated to Android 9 (although first 10 attempts with OTA weirdly failed, number 11 finally worked ).
But now, with Pie, Google Pay is not working anymore and I receive two (instead of one at Android 8) error/warning messages while starting.
First one is still the "Your device has loaded a different Operating system" and the typical error screen.
But when booting up and showing the Motorola logo, theres a small hint saying "Verity mode is set to disabled"....
Please help!
No one here to help?
ElwynnEldoriath said:
No one here to help?
Click to expand...
Click to collapse
The Z2 Force doesn't quite have the support that it had in the early days. @Uzephi doesn't have the device anymore so he cannot do any building or testing anymore. The days of strong active development support has passed for this device. It sucks because I love the Z2 Force and it's my daily driver.
My understanding is that the text you see that says verity mode it set to disabled is there because the bootloader is unlocked. I'm not 100% sure about it though but I remember reading some other users posting about it.
If your device is fully stock on the Pie OTA, you can always relock the bootloader to see if that will allow you to use Google Pay and your banking apps.
My suggestion is to leave the bootloader unlocked because I'd you ever have any issues it will give you a couple more options to recover your device.
Sent from my Z2 Force using XDA Labs
My wife had been on whatever stock ROM came on her Pixel 2 since i bought it with no issues. She ran into a problem after maxing out her storage that the phone wouldn't boot and stayed stuck at the "G" boot screen. I got that fixed by sideloading an OTA of what seems to be some pre-release version of Android. it says "R" version. Many vital apps aren't working correctly - messaging, gmail, can't search from google bar, camera stopped working properly. So i am thinking i should start fresh and install something else now that at least the OS is back booting properly and hopefully everything will work ok.
I just want to make sure if anyone can help tell me what i'm dealing with, i believe this was a locked bootloader? not sure i can or need to unlock it.... > Install twrp... > Flash stock rom...? she doesn't need a fancy rom just something simple and stable.
Here's some of her vital info, any tips greatly apprecaited as i'm out of the loop on this stuff and an old pedestrian user at best.
Android Version
R
Baseband version
g8998-00020-1912200251
kernel version
4.4.210-gf13e65034114-ab6213703
Build Number
Rpp2.20227.009
Since your phone boots now. Simply wiping out everything should do the trick i guess.
Yeah. You can a factory reset. Your are currently on Android 11(R) preview ROM, it's still in the early phases and not suitable as a daily driver.
If all fails you can always flash a factory image, just remember to backup your data first.
Is this device a carrier device and if so, which carrier? You can only flash factory images with an unlocked bootloader so you need to figure that out first.
To figure out if you can unlock the bootloader you will first have to figure out if you have a Google or Verizon variant. Google variants can be unlocked. Verizon variants, for the most part, can't (although there is a thread where I believe someone may have done it on a Verizon variant). To figure out if you have a Google or Verizon, go here... https://www.imeipro.info/check_lg.html
Under "Buyer Name", if it says Google you're good to go. If it says Verizon or VZW, then you can't unlock the bootloader (unless the method in the thread I mentioned above actually works).
If you find you have a Google variant then via fastboot unlock the bootloader and fastboot flash the latest Q factory image.
https://9to5google.com/2020/04/23/h...d-11-dp1-to-android-10-on-google-pixel-video/
u need check ur phone can or not unlock bootloader.
if can... first thing u need to do is enable " oem unlock" in "development options"
when u unlock u can flash whatever firmware you want.
.
the problem u in android 11 . this very much bug.
Once you unlock, it'll wipe the phone.
You say you're running 11 DP1... At this point, I'd suggest signing up for the beta program and let the system update to I'd imagine the latest preview. Doing this should not wipe the phone.
From there you should have a working device and can back up what you want.
You should be given the option to unenroll on the beta website. Doing that, will downgrade the phone to the latest 10 release. it WILL also wipe the phone.
Go here. I see there's a link that could help you out.
google.com/android/beta
Hey all,
I just got my 9 Pro. Unfortunately I had to get it thru T-Mobile. That last couple OnePlus devices I have always converted them to the Global firmware.
This go around I am wondering if it is worth it. Are there any benefits aside from de-bloating?
Looking for some opinions to help me make my decision before I reset and go thru the process of setting up my phone again.
And yes, the SIM is unlocked already, and I have my unlock token to unlock my bootloader.
Fatmonk8 said:
Hey all,
I just got my 9 Pro. Unfortunately I had to get it thru T-Mobile. That last couple OnePlus devices I have always converted them to the Global firmware.
This go around I am wondering if it is worth it. Are there any benefits aside from de-bloating?
Looking for some opinions to help me make my decision before I reset and go thru the process of setting up my phone again.
And yes, the SIM is unlocked already, and I have my unlock token to unlock my bootloader.
Click to expand...
Click to collapse
TMobile 9 Pro user here. Had the 9 as well. Both converted. Quick question without seeming cocky, you mentioned you converted your old OP devices in the past, why did you convert them?
TheKnux said:
TMobile 9 Pro user here. Had the 9 as well. Both converted. Quick question without seeming cocky, you mentioned you converted your old OP devices in the past, why did you convert them?
Click to expand...
Click to collapse
To de-bloat.
But if that's the only positive this go around then it's probably not worth me doing since I have been de-bloating more with ADB lately. But if others have any input on other benefits then I may do it again.
Well my opinion, updates. I'm still on OOS11 but that's by choice. For one,even though I can't change the stock oos bootanimation, it's still better than T-Mobile stock. Second, a lot of support with custom roms, kernels, and mods don't give support to people who are on TMobile firmware for some reason (don't ask, don't know lol).
Third, it's a lot easier to cross-flash firmwares and downgrade, especially with an unlocked bootloader. I was able to go from OOS12 beta to stable, then to custom w/kernel, then to COS 12.1, then back to OOS11 with one single MSM. To me, it just seems all around easier. There's more reasons, I'm just in lunch so I figured give you my two cents.
Right now my setup is OOS 11.2.10.10_DA with latest alpha Magisk using the latest Shamiko with Zygisk with Hide off, fully passing SafetyNet. Arter R12 with latest TWRP.
TheKnux said:
Well my opinion, updates. I'm still on OOS11 but that's by choice. For one,even though I can't change the stock oos bootanimation, it's still better than T-Mobile stock. Second, a lot of support with custom roms, kernels, and mods don't give support to people who are on TMobile firmware for some reason (don't ask, don't know lol).
Third, it's a lot easier to cross-flash firmwares and downgrade, especially with an unlocked bootloader. I was able to go from OOS12 beta to stable, then to custom w/kernel, then to COS 12.1, then back to OOS11 with one single MSM. To me, it just seems all around easier. There's more reasons, I'm just in lunch so I figured give you my two cents.
Right now my setup is OOS 11.2.10.10_DA with latest alpha Magisk using the latest Shamiko with Zygisk with Hide off, fully passing SafetyNet. Arter R12 with latest TWRP.
Click to expand...
Click to collapse
I appreciate you input, and that did help me make a decision.
What was your method to convert your T-Mobile 9 Pro? Because every method I tried ended up bricking my phone. It would always be when I had to flash the modem when it would brick. Followed the guide on here and other sites multiple time and always the same.
Guess it's not like old OnePlus where we can just flash different firmware willy nilly.
Fatmonk8 said:
I appreciate you input, and that did help me make a decision.
What was your method to convert your T-Mobile 9 Pro? Because every method I tried ended up bricking my phone. It would always be when I had to flash the modem when it would brick. Followed the guide on here and other sites multiple time and always the same.
Guess it's not like old OnePlus where we can just flash different firmware willy nilly.
Click to expand...
Click to collapse
So I spent a week figuring this out. I realized a few days ago that I mistakenly flashed the Indian firmware for the OnePlus 9 PRO. I have the regular 9. I tried to flash every other msm I could find and download. Nothing seems to work except the Indian OnePlus 9 PRO msm... Problem is, the camera, flash and fingerprint scanner didn't work. I was able to toggle the unlock oem button by running an adb command line then I did oem unlock in fastboot. After that, I followed the instructions for installing StagOs 12.1, which involves installing lineage recovery then flashed the rom. Everything works flawlessly! Love this rom.