Develop Bugs

Fastboot for ARM/ARM64

Here are the binaries for fastboot you can use on your device. The reason I'm posting them here is because they can really useful if you happen to flash something wrong while on the go. You need another device to connect to via USB to use them.
I cant really post source because I didn't keep it, since I compiled in aosp env, but I can explain how to compile them if anyone really wants. I did made these a while ago but I never tested them until I had to today, because I flashed a kernel while waiting in line behind the 4 slowest human beings in existence at Walmart. To my surprise, it worked I figured I'd have to add a USB library like I had to for adb, but apparently not.
Normally I wouldn't bother posting these, but our device is so finicky that I figure someone else might need them at some point. I didn't change any of the source code of fastboot from the 8.1 branch.
Download : https://androidfilehost.com/?fid=673791459329068348
Reshare or do whatever you want with them.
Make sure pixel 2 is the device that gets the direct USB-C connection.
Finally, don't be dumb with them, act like an adult, and if you get errors there's a good chance I'm not going to go back to fix them so post the relevant line in code that leads to whatever error you get if you want me to help or look at it.

Very cool!

You people flashing things on-the-go which can potentially render your device inoperable until you get fastboot access confuse me haha. But I guess that's JustXDAThings.

Just watch what you flash and use anykernels, not boot images. The Pixel 2 bootchain isn't as fragile as you think once you flash TWRP into the ramdisk. Protect TWRP and you'll hopefully never need to fastboot from a companion device.

MishaalRahman said:
You people flashing things on-the-go which can potentially render your device inoperable until you get fastboot access confuse me haha. But I guess that's JustXDAThings.
Click to expand...
Click to collapse
YOLO.
The way I see it, there are two kinds of developers, the kind that need testers because they have no idea what they're doing, and the kind that test themselves, because they are the only ones that know what they're doing.
I'm about to yolo flash a taimen build I just made, it will most likely fail, but that log and debug info I get from it will be valuable lol.

Good on you to carry around 2 phones though. I ain't got that luxury. Haha so I'm still screwed.

jlee08517 said:
Good on you to carry around 2 phones though. I ain't got that luxury. Haha so I'm still screwed.
Click to expand...
Click to collapse
Well anything that has an arm arm64 arch, like tablets and chromebooks would work too. So it's just convenient, ironically there's code for tcp connections in fastboot, so that's interesting...

Surge1223 said:
Well anything that has an arm arm64 arch, like tablets and chromebooks would work too. So it's just convenient, ironically there's code for tcp connections in fastboot, so that's interesting...
Click to expand...
Click to collapse
I had a device that made use of that fastboot over tcp protocol ;p
Moto G3 Prototype. Comically, it was actually a boot mode with an extended LK (as in when I used a non-proto boot image, the feature was not operable).

The ARM version doesn't seem to work. I get "illegal instruction" no matter what command I try to use.

TheSt33v said:
The ARM version doesn't seem to work. I get "illegal instruction" no matter what command I try to use.
Click to expand...
Click to collapse
@TheSt33v
I've got an older armeabi build that should work for you. Check my Odds and Ends thread, or grab it from the Magisk Modules repo.

osm0sis said:
@TheSt33v
I've got an older armeabi build that should work for you. Check my Odds and Ends thread, or grab it from the Magisk Modules repo.
Click to expand...
Click to collapse
Is it new enough that it will flash the Pixel 2 XL? It doesn't work with older versions.

TheSt33v said:
Is it new enough that it will flash the Pixel 2 XL? It doesn't work with older versions.
Click to expand...
Click to collapse
Well you can try, but probably not then. You'll just need to use a newer device as the host device to flash from.

@Surge1223 I realize this is an older thread but I'm going to ask anyways because after searching around, most I can find are x64 files. I've ordered an arm based Chromebook, am I correct in that this is what's needed to get fastboot and adb working? Thanks

@Surge1223
Just wondering if there's any chance of getting this updated?
The current version is broken, at least, on the Pixel 3. Just tried to use my old Nexus 5X to Update my Pixel with the January update. Going to be computer-less for a while starting next week and was hoping I could use the Nexus for updates.
I bypassed the version check in the flash-all.sh file and tried to run it. Bootloader and radio updated fine. But system (along with product and vendor) were a complete no go. Boot image also updates just fine.
Basically I suspect any simple flashes will work, other than that - nope.
At least it didn't brick the device in any way. I ended up with a December system, vendor, and product along with an updated modem, bootloader, and Magisk patched kernel which all booted fine. Normal update via computer worked so at least I'm good for this month.
Not expecting anything, just hoping maybe you'll update this sometime in the near future.
Thanks for your consideration.

jcmm11 said:
@Surge1223
Just wondering if there's any chance of getting this updated?
The current version is broken, at least, on the Pixel 3. Just tried to use my old Nexus 5X to Update my Pixel with the January update. Going to be computer-less for a while starting next week and was hoping I could use the Nexus for updates.
I bypassed the version check in the flash-all.sh file and tried to run it. Bootloader and radio updated fine. But system (along with product and vendor) were a complete no go. Boot image also updates just fine.
Basically I suspect any simple flashes will work, other than that - nope.
At least it didn't brick the device in any way. I ended up with a December system, vendor, and product along with an updated modem, bootloader, and Magisk patched kernel which all booted fine. Normal update via computer worked so at least I'm good for this month.
Not expecting anything, just hoping maybe you'll update this sometime in the near future.
Thanks for your consideration.
Click to expand...
Click to collapse
Yeah new devices use fastbootd to update vendor system product vbmeta and dtbo, I'll try to update it soon, I'll try to hook it up before next week for ya though.

Surge1223 said:
Yeah new devices use fastbootd to update vendor system product vbmeta and dtbo, I'll try to update it soon, I'll try to hook it up before next week for ya though.
Click to expand...
Click to collapse
I normally wouldn't ask, and if you can't (for whatever reason) that's fine. But you did say you'd try to get this updated. New security patches are due out Monday and it would be real nice if I could apply them ?
If not, I'll live. Thanks, no matter what.

Surge1223 said:
Here are the binaries for fastboot you can use on your device. The reason I'm posting them here is because they can really useful if you happen to flash something wrong while on the go. You need another device to connect to via USB to use them.
I cant really post source because I didn't keep it, since I compiled in aosp env, but I can explain how to compile them if anyone really wants. I did made these a while ago but I never tested them until I had to today, because I flashed a kernel while waiting in line behind the 4 slowest human beings in existence at Walmart. To my surprise, it worked I figured I'd have to add a USB library like I had to for adb, but apparently not.
Normally I wouldn't bother posting these, but our device is so finicky that I figure someone else might need them at some point. I didn't change any of the source code of fastboot from the 8.1 branch.
Download : https://androidfilehost.com/?fid=673791459329068348
Reshare or do whatever you want with them.
Make sure pixel 2 is the device that gets the direct USB-C connection.
Finally, don't be dumb with them, act like an adult, and if you get errors there's a good chance I'm not going to go back to fix them so post the relevant line in code that leads to whatever error you get if you want me to help or look at it.
Click to expand...
Click to collapse
Sorry for bumping an old thread but would you be willing to explain how to compile or upload the fastboot and adb binaries of the latest platform tools? I have a PineBookPro that's running arm64 architecture and was looking for them in the repos but the ones I could find were for api23 and would very much like api30 so I could revive my old p2xl. Thank you for your contribution.

Fe Mike said:
Sorry for bumping all old thread but would you be willing to explain how to compile or upload the fastboot and adb binaries of the latest platform tools? I have a PineBookPro that's running arm64 architecture and was looking for them in the repos but the ones I could find were for api23 and would very much like api30 so I could revive my old p2xl. Thank you for your contribution.
Click to expand...
Click to collapse
Not sure if this helps...I'm on the newest version of Platform tools, I have a pixel 2 xl and have no issues.

cubzfan68 said:
Not sure if this helps...I'm on the newest version of Platform tools, I have a pixel 2 xl and have no issues.
Click to expand...
Click to collapse
It may, are you using fastboot from op on the phone from another arm device or a PC?

Fe Mike said:
It may, are you using fastboot from op on the phone from another arm device or a PC?
Click to expand...
Click to collapse
I use it from a pc

[DEV] Bootloader unlock development

You can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (cheaper but FunkyHuawei is more certain)
As most of you already know, Huawei stopped giving away bootloader unlock codes. So it is up to us, to hack our way to root and custom ROMs.
Following, are a few things we could try,
Also, I own a Nova 3i currently. There are always the possibility that something working for me won't work for you, because of different chipsets, but I guess that this forum is also for the development of Nova 3i.
NOTE THAT SOME OF THE FOLLOWING ARE PAID SERVICES. I'M NOT RELATED WITH ANY OF THEM.
+DC-Unlocker:
I tried the latest version, got an unknown error 375. (This error also goes for the latest versions of P20 Pro, Mate 10, etc.). And the developers said that they won't support any new Huawei phones, and that they'll leave new Huawei phones for HCU-Client, because the two services are related.
+HCU-Client:
You can't try this without buying credits. If you feel generous, go on and try this. They released a couple of new versions in this week.
+Bootloader exploiting:
I really don't know anything about this, feel free to contribute.
+Secret Fastboot backdoors:
There can be a LOT of these, considering that there are a family of commands under <fastboot oem backdoor>. And I discovered quite a lot of secret commands, almost every one of them sounding like that they could seriously brick the device. For example, consider what <fastboot oem djtagtosd> sounds like. (Search Google for JTAG) If you would like to test some of the less-dangerous looking ones, please PM me, even an old Huawei device is okay as long as it has a Kirin chipsets.

Please check this link from P20 Pro Forum - we may have a chance to be supported if many of us do the request. I have done mine. - https://forum.xda-developers.com/hu...ol-tool-one-driversunlocktwrpfactory-t3779080

waltermsalomon said:
Please check this link from P20 Pro Forum - we may have a chance to be supported if many of us do the request. I have done mine. - https://forum.xda-developers.com/hu...ol-tool-one-driversunlocktwrpfactory-t3779080
Click to expand...
Click to collapse
Sorry, did not see this. So, this tool installs TWRP without unlock codes? Still we need to get TWRP compiled.

Huawei nova 3i rom
Dears I need stock firmware and flash tool officially for Huawei Nova 3i ine-lx1

cant EU do anything about this bootloader unlocking situation? I mean, isn't it our right to do whatever we want with our bought device? Im actually not from any EU country btw.

jioleight said:
cant EU do anything about this bootloader unlocking situation? I mean, isn't it our right to do whatever we want with our bought device? Im actually not from any EU country btw.
Click to expand...
Click to collapse
Maybe there is some legislation about that, actually the issue of locked bootloaders runs more than 6/7 years (I think) and they had plenty of time if they wanted to do that... but we can hope, considering things like GDPR.
At least one of things they MUST do is releasing the kernel sources, because by using Android they agree to some license (I don't remember the name) that mandates releasing kernel source..
BTW you can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (they are cheaper, but they look more shady, and I can't help noticing that there website looks just like one of those poorly done scam sites :laugh

Supersonic27543 said:
Maybe there is some legislation about that, actually the issue of locked bootloaders runs more than 6/7 years (I think) and they had plenty of time if they wanted to do that... but we can hope, considering things like GDPR.
At least one of things they MUST do is releasing the kernel sources, because by using Android they agree to some license (I don't remember the name) that mandates releasing kernel source..
BTW you can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (they are cheaper, but they look more shady, and I can't help noticing that there website looks just like one of those poorly done scam sites :laugh
Click to expand...
Click to collapse
mandated but no one is enforcing it so huawei will just delay the relase of the kernel source until the insterest has died out.
nope, not gonna take that risk :laugh:. $55 seems cheaper until it's converted to my country's currency. haha.

Supersonic27543 said:
Maybe there is some legislation about that, actually the issue of locked bootloaders runs more than 6/7 years (I think) and they had plenty of time if they wanted to do that... but we can hope, considering things like GDPR.
At least one of things they MUST do is releasing the kernel sources, because by using Android they agree to some license (I don't remember the name) that mandates releasing kernel source..
BTW you can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (they are cheaper, but they look more shady, and I can't help noticing that there website looks just like one of those poorly done scam sites :laugh
Click to expand...
Click to collapse
Another one source to unlock bootloader - $22
This method has already been tested on 4pda. Working TWRP can be taken from here
And HCU doesn't have NOVA 3 support yet to read the unlock code now

OEM Unlock option
Is it enought to enable "OEM Unlock" in "Developer Options" from the phone settings to unlock the bootloader and I can simply install TWRP afterthat? (the option "OEM Unlock" is not greyed out, and can be easily enabled, at least in the devices that are sold in my country).
Or do I still have to unlock it using unlock key from Huawei Website (or other sources)?

Jan oatcoal said:
Do I still have to unlock it using unlock key from Huawei Website (or other sources)?
Click to expand...
Click to collapse
Yep. It is like this when you issue the command in fastboot to unlock:
Without code and without enabling the toggle: Gives and error telling to turn on the toggle.
With code and without enabling the toggle: Same as above
Without code and toggle enabled: Error wrong password
With both: Success
I think we are lucky on that side, I think that the toggle is also disabled on Mate 20 series. So we can unlock the bootloader. with external sources for now, so it may be a good idea to block OTA updates.

Ine-lx2 8.2.0.131(c636)
*update*
so i checked using fastboot oem get-bootinfo. lo and behold it's really unlocked.

jioleight said:
does Phone Unlocked mean the bootloader or just the GSM part that is unlocked?
Click to expand...
Click to collapse
I did this then installed titanium backup and it said it wasn't rooted.

meekspace said:
I did this then installed titanium backup and it said it wasn't rooted.
Click to expand...
Click to collapse
you have to root first by installing magisk or supersu. and it needs twrp to root. in case of nova 3i there isnt any existing twrp. only on nova 3 since it has the same soc as p20pro.
was about to test it on my nova 3i. good thing i checked the specs of nova 3 first before proceeding.

Unfortunately, cant flash patched ramdisk since fastboot fail. Remote command not allowed. So close yet so far away.

jioleight said:
Unfortunately, cant flash patched ramdisk since fastboot fail. Remote command not allowed. So close yet so far away.
Click to expand...
Click to collapse
Let's try flashing the stock boot.img. If that works, I will patch the boot image to manually disable dm-verity and add Magisk.

Supersonic27543 said:
Let's try flashing the stock boot.img. If that works, I will patch the boot image to manually disable dm-verity and add Magisk.
Click to expand...
Click to collapse
"fastboot flash ramdisk patched_boot.img". That's what entered in cmd. Also after magisk patched the ramdisk the patched ramdisk is only 5mb. The original was around 25mb.
What should be patched anyway? I patched ramdisk.img via magisk ang since the partitioning is different with phones released with oreo. What is your method?
*update*
well, this sux. based on what i have read on other huawei device flashing via fastboot is not always the best way. the phone may display that the bootloader is unlock but it wont still allow any modifications. why cant this be straight forward like samsung/oneplus. this is frustrating.

jioleight said:
"fastboot flash ramdisk patched_boot.img". That's what entered in cmd. Also after magisk patched the ramdisk the patched ramdisk is only 5mb. The original was around 25mb.
What should be patched anyway? I patched ramdisk.img via magisk ang since the partitioning is different with phones released with oreo. What is your method?
*update*
well, this sux. based on what i have read on other huawei device flashing via fastboot is not always the best way. the phone may display that the bootloader is unlock but it wont still allow any modifications. why cant this be straight forward like samsung/oneplus. this is frustrating.
Click to expand...
Click to collapse
What if we try obtaining a code by one of the third party methods and try that? Maybe they just forgot or didn't care to set the variables you saw there as this is a new chipset. I think it is not really unlocked, if it was the phone will display the "Your device has been unlocked and cannot be trusted" message on boot.

Looks like what I said before is true. fastboot oem lock-state info returns USER Locked.

Has anyone tried this?
https://www.techdroidtips.com/unloc...i/#How_to_Unlock_Bootloader_on_Huawei_Nova_3i

stevefwt said:
Has anyone tried this?
https://www.techdroidtips.com/unloc...i/#How_to_Unlock_Bootloader_on_Huawei_Nova_3i
Click to expand...
Click to collapse
They are just copy pastes and no longer works as of Huawei stopping providing codes.
Google should try to remove them from coming at top of Google searches, IDK.

Widevine Level 3/ DRM stock and locked bootloader

Hey guys,
when I got the P3XL I unlocked the bootloadeer immediately. Widevine level was still on L1 even though I've installed a custom rom. Then I had to try something, flashed another rom and also flashed the latest factory image and it was changed to L3.
Now even after flashing the factory image and completely locked the bootloader, it still says L3...So in amazon prime and netflix only HDR/UHD works... but not HD for shows and movies which are not netflix/amazon originals.
Did someone had the same issue? If yes is there a fix to it or maybe Google is aware of it already? Some people reported that after a while their Widevine level changed to L3 with custom rom/custom kernel, but it should be back to L1 with completely locked bootloader and full stock rom. It does that way for all other phones (htc U12+, essential PH-1 and many many others)
Is there something in the Pixel which is similar to Samsung's Knox? ... I'm just so disappointed and angry...

I also catched a log, where it says cannot open file /vendor/firmware_mnt/imagine/widevine.mdt. this file is missing in that folder and the Essential PH-1 even with unlocked bootloader, rooted/custom rom has it still there and the phone is also in L1... so google did something, what deleted that file....

DeeZZ_NuuZZ said:
Hey guys,
when I got the P3XL I unlocked the bootloadeer immediately. Widevine level was still on L1 even though I've installed a custom rom. Then I had to try something, flashed another rom and also flashed the latest factory image and it was changed to L3.
Now even after flashing the factory image and completely locked the bootloader, it still says L3...So in amazon prime and netflix only HDR/UHD works... but not HD for shows and movies which are not netflix/amazon originals.
Did someone had the same issue? If yes is there a fix to it or maybe Google is aware of it already? Some people reported that after a while their Widevine level changed to L3 with custom rom/custom kernel, but it should be back to L1 with completely locked bootloader and full stock rom. It does that way for all other phones (htc U12+, essential PH-1 and many many others)
Is there something in the Pixel which is similar to Samsung's Knox? ... I'm just so disappointed and angry...
Click to expand...
Click to collapse
No there is no security measure which trips Pixel 3 as far i am aware of nor is mine tripped.
flashed a lot of custom roms flashed march & april factory images with -w and without -w and i am on custom rom now, bootloader still unlocked, rooted, custom kernel and it's still widevine security is L1.
While doing a search I see that you already posted the issue with Google support lets see if they can say else that unlocking bootloader is the reason.

SacredDeviL666 said:
No there is no security measure which trips Pixel 3 as far i am aware of nor is mine tripped.
flashed a lot of custom roms flashed march & april factory images with -w and without -w and i am on custom rom now, bootloader still unlocked, rooted, custom kernel and it's still widevine security is L1.
While doing a search I see that you already posted the issue with Google support lets see if they can say else that unlocking bootloader is the reason.
Click to expand...
Click to collapse
Yes that is the strange thing, L1 worked fine when I was on aquarios first.
Then tried DU and had to reflash factory image and L1 wasn't working anymore.
I was told by google supported to also issue that to widevine, sent them some logs too. Let's see who can help.
There must be something wrong, because @Freak07 also tried the widevine.mdt file from another pixel 3, but it didn't worked either. The same error 13 was there.
I gonna try the full ota image tomorrow or so. Gonna see if that might help with a locked bootloader. I hope it can be sorted, because it's stupid if a phone like the pixel has such issues
Can you also please check in logcat what it shows for you when you search for widevine and drm?
Also is that file I mentioned above also available in that specific folder? And other widevine files in that folder?
Sent from my Google Pixel 3 XL using XDA Labs

DeeZZ_NuuZZ said:
Yes that is the strange thing, L1 worked fine when I was on aquarios first.
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
Then tried DU and had to reflash factory image and L1 wasn't working anymore. ( have you flashed any vendor.img other than the one's you have extracted from google's full factory.img file )
had to reflash factory image and L1 wasn't working anymore. ( i've flashed factory image with a full wipe and without wipe multiple times including last week while trying to do a clean install with april image along with -w )
Can you also please check in logcat what it shows for you when you search for widevine and drm? (didn't get this question sorry )
Also is that file I mentioned above also available in that specific folder? ( i have vendor/firmware_mnt/image folder but there is no widevine.mdt )
And other widevine files in that folder? (no widevine files in that folder)

SacredDeviL666 said:
had to reflash factory image and L1 wasn't working anymore. ( have flashed mutltiple times factory image including last week while trying to do a clean install with april image along with -w )
Can you also please check in logcat what it shows for you when you search for widevine and drm? (didn't get this question sorry )
Also is that file I mentioned above also available in that specific folder? ( i have vendor/firmware_mnt/image folder but there is no widevine.mdt )
And other widevine files in that folder? (no widevine files in that folder)
Click to expand...
Click to collapse
For the logcat I mean when you use an app like matlog, you can directly use the search function to search for specific words, in that case widevine and drm. Can you attach the screenshot/logs of both ?
Also very strange that there is no such file in the imagine folder and yet L1 works fine for you....
Did you try different ROMs, or only bootleggers? Was it always on L1?
Actually I haven't flashed vendor.img manually, I let the flash script do the job. Do you think this might be the issue?
Also I don't remember if I flashed the April vendor from DU homepage ....
Sent from my Google Pixel 3 XL using XDA Labs

DeeZZ_NuuZZ said:
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
For the logcat I mean when you use an app like matlog, you can directly use the search function to search for specific words, in that case widevine and drm. Can you attach the screenshot/logs of both ? (does the attached screenshot of matlog highlighting the result what i got when searched for widevine.dmt helps? and the error the log states is same as what you said in your initial post )
Also very strange that there is no such file in the imagine folder and yet L1 works fine for you.... ( )
Did you try different ROMs, or only bootleggers? Was it always on L1? ( it was always on L1/AOSIP/Bootleggers/Scorpion these are the roms which i keep shuffling in between/Kernel ElementalX/Kirisakura )
Actually I haven't flashed vendor.img manually, I let the flash script do the job. Do you think this might be the issue? ( no harm in giving a try as flashing vendor image won't mess up your rom setup or installations )

SacredDeviL666 said:
For the logcat I mean when you use an app like matlog, you can directly use the search function to search for specific words, in that case widevine and drm. Can you attach the screenshot/logs of both ? (does the attached screenshot of matlog highlighting the result what i got when searched for widevine.dmt helps? and the error the log states is same as what you said in your initial post )
Also very strange that there is no such file in the imagine folder and yet L1 works fine for you.... ( )
Did you try different ROMs, or only bootleggers? Was it always on L1? ( it was always on L1/AOSIP/Bootleggers/Scorpion these are the roms which i keep shuffling in between/Kernel ElementalX/Kirisakura )
Actually I haven't flashed vendor.img manually, I let the flash script do the job. Do you think this might be the issue? ( no harm in giving a try as flashing vendor image won't mess up your rom setup or installations )
Click to expand...
Click to collapse
Thanks.
Yeah gonna definitely flash full ota img first tomorrow or the day after tomorrow. And maybe unlocking again at the weekend and flash vendor.img on both slots manually
Sent from my Google Pixel 3 XL using XDA Labs

DeeZZ_NuuZZ said:
Thanks.
Yeah gonna definitely flash full ota img first tomorrow or the day after tomorrow. And maybe unlocking again at the weekend and flash vendor.img on both slots manually
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
Let me know if you get that sorted because I too have L3 and I've flashed stock April image with full wipe and relocked the bootloader. Unclear what the issue is...

Dark_Eyes_ said:
Let me know if you get that sorted because I too have L3 and I've flashed stock April image with full wipe and relocked the bootloader. Unclear what the issue is...
Click to expand...
Click to collapse
According to freak07 it might be related to the trustzone, that it doesn't allow to use Level 1...
Gonna try different things this week and also wait for widevine support for an answer ...
Sent from my Google Pixel 3 XL using XDA Labs

My phone is unlocked since day one, I am on Q Beta 2 and before i used to flash 3 different Custom ROMS and back to factory image abt 4 times. i always have L1 on the security level.

driss.sadok said:
My phone is unlocked since day one, I am on Q Beta 2 and before i used to flash 3 different Custom ROMS and back to factory image abt 4 times. i always have L1 on the security level.
Click to expand...
Click to collapse
Yeah there must be some sort of trigger or so, which seems to break Widevine. I probably gonna flash later today the full ota image and then see if it might be working again
Sent from my Google Pixel 3 XL using XDA Labs

DeeZZ_NuuZZ said:
Yeah there must be some sort of trigger or so, which seems to break Widevine. I probably gonna flash later today the full ota image and then see if it might be working again
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
Keep us updated on this. I'm curious too since mine is showing L3 as well and I'm rooted on stock with the latest Kirisakura kernel.

Flyer66 said:
Keep us updated on this. I'm curious too since mine is showing L3 as well and I'm rooted on stock with the latest Kirisakura kernel.
Click to expand...
Click to collapse
okay, so I've flashed the latest full ota image... and guess what?
IT DIDN'T FIXED IT... man I'm so annoyed and tired by this...
really...on every other device which came with L1 out-of-the-box too, will always revert back to L1 when back to full stock/relocked/locked bootloader...only the pixel now has some issue like that ... and somehow I can't find any otherpost about it... is there really no one else who cares about that? paying so much money for a phone and then things like that don't work properly... it's somehow sad...

DeeZZ_NuuZZ said:
okay, so I've flashed the latest full ota image... and guess what?
IT DIDN'T FIXED IT... man I'm so annoyed and tired by this...
really...on every other device which came with L1 out-of-the-box too, will always revert back to L1 when back to full stock/relocked/locked bootloader...only the pixel now has some issue like that ... and somehow I can't find any otherpost about it... is there really no one else who cares about that? paying so much money for a phone and then things like that don't work properly... it's somehow sad...
Click to expand...
Click to collapse
Bro try this post, i didn't read all and it's old, but it may help somehow.
https://forum.xda-developers.com/android/apps-games/app-netflix-hd-widevine-drm-l1-devices-t3307241

driss.sadok said:
Bro try this post, i didn't read all and it's old, but it may help somehow.
https://forum.xda-developers.com/android/apps-games/app-netflix-hd-widevine-drm-l1-devices-t3307241
Click to expand...
Click to collapse
This only works if the device has L1 but is not whitelisted by Netflix (like the HTC u12+, it's L1 but server side not whitelisted, same as Amazon)
I'm still waiting for an answer from the Widevine team... Hopefully they will come back to me soon
Sent from my Google Pixel 3 XL using XDA Labs

DeeZZ_NuuZZ said:
This only works if the device has L1 but is not whitelisted by Netflix (like the HTC u12+, it's L1 but server side not whitelisted, same as Amazon)
I'm still waiting for an answer from the Widevine team... Hopefully they will come back to me soon
Sent from my Google Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
Did you contact google support or checked google forums? I think it has something only with google devices

driss.sadok said:
Did you contact google support or checked google forums? I think it has something only with google devices
Click to expand...
Click to collapse
Yes posted on google forum/community and also contacted the support. They advised me to contact widevine. Even though it should be an issue by them, not widevine directly...
Sent from my Google Pixel 3 XL using XDA Labs

Very strange. I have Pixel 3 and my level is L1. This even though it is rooted, bootloader unlocked, and running DU rom.

wangdaning said:
Very strange. I have Pixel 3 and my level is L1. This even though it is rooted, bootloader unlocked, and running DU rom.
Click to expand...
Click to collapse
Yeah there must be some sort of trigger or so, where it can end up with L3 all the time.
Sent from my Google Pixel 3 XL using XDA Labs

Question I'm very overwhelmed please help

The last time I rooted a phone was 3 years ago, in general whenever I try to root a phone I feel like the entire process has changed and im completely out of the loop.
All i want to do is make it so i can install f.lux and youtube vanced, how do I do this?
I know that I need to install magisk but apparently I also need to enable the bootloader whatever that means?
Sideload, flashing, caprip, boot-image, fastboot, TWRP: these words mean nothing to me, they serve to confuse and demean me.
Is there any resource for figuring out how to go from a new out-of-the-box moto g30 to one which lets me install youtube vanced? Usually I'd look up a tutorial but the only one I found was in spanish and I don't speak spanish.
Thanks for any help you can give.

First things first.
Android has Night Light built in and Youtube Vanced doesn't need root.
But, if you're still serious about rooting and installing magisk to make use of all of the really useful modules, you'll need:
An Unlocked Bootloader: Motorola's Own Guide
Keep in mind that unlocking the bootloader will wipe your phone and void its warranty, so be absolutely sure you want to do it and back up your files.
Then you'll need to manually patch a boot.img from your stock ROM (can be found here.) and flash it using ADB (Android Debug Bridge) using your PC.
I rooted mine within 3 days of owning it and have been enjoying it with no problems whatsoever ever since.
I used this guide as reference. If you have any questions you can always just message me here or on Telegram (@Kuntitled).

samjoebobtomted said:
The last time I rooted a phone was 3 years ago, in general whenever I try to root a phone I feel like the entire process has changed and im completely out of the loop.
All i want to do is make it so i can install f.lux and youtube vanced, how do I do this?
I know that I need to install magisk but apparently I also need to enable the bootloader whatever that means?
Click to expand...
Click to collapse
Bootloader is small program which runs before Android operating system running. Bootloader is first program to run so It is specific for board and processor. -RootJunky
Click to expand...
Click to collapse
Unlocking the bootloader
You can flash a custom system only if the bootloader allows it. Note, though, that the bootloader is locked by default. You can unlock the bootloader, but doing so deletes user data for privacy reasons. After unlocking, all data on the device is erased, that is, both private app data and shared data accessible over USB (including photos and movies). Before attempting to unlock the bootloader, back up any important files on the device. - https://source.android.com/setup/build/running
Click to expand...
Click to collapse
samjoebobtomted said:
Sideload,
Click to expand...
Click to collapse
Generally sideload means installing an app without the playstore.
samjoebobtomted said:
flashing,
Click to expand...
Click to collapse
Flashing usually refers to installing through fastboot mode or recovery
samjoebobtomted said:
caprip,
Click to expand...
Click to collapse
codename or development name for Moto G30
samjoebobtomted said:
boot-image
Click to expand...
Click to collapse
The boot.img is the fie that creates the boot partition
/boot​This is the boot partition of your Android device, as the name suggests. It includes the android kernel and the ramdisk. The device will not boot without this partition. Wiping this partition from recovery should only be done if absolutely required and once done, the device must NOT be rebooted before installing a new one, which can be done by installing a ROM that includes a /boot partition.
-RootJunky
Click to expand...
Click to collapse
samjoebobtomted said:
fastboot,
Click to expand...
Click to collapse
Fastboot refers to several things
Fastboot is the fastboot protocol to communicate with an Android device.
Fastboot.exe is the part of SDK Platform-Tools used to communicate with an Android device when it's in fastboot mode.
samjoebobtomted said:
TWRP:
Click to expand...
Click to collapse
Twrp is a Custom recovery,
The stock recovery has very limited functions,
a custom recovery has more options
/recovery​This is specially designed for backup. The recovery partition can be considered as an alternative boot partition, that lets the device boot into a recovery console for performing advanced recovery and maintenance operations on it. -RootJunky
Click to expand...
Click to collapse
samjoebobtomted said:
these words mean nothing to me, they serve to confuse and demean me.
Is there any resource for figuring out how to go from a new out-of-the-box moto g30 to one which lets me install youtube vanced? Usually I'd look up a tutorial but the only one I found was in spanish and I don't speak spanish.
Thanks for any help you can give.
Click to expand...
Click to collapse
I have general Moto rooting instructions here
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com

Kuntitled said:
First things first.
Android has Night Light built in and Youtube Vanced doesn't need root.
Click to expand...
Click to collapse
Wait really I didn't even realize I didn't need a root for that lol.
Kuntitled said:
But, if you're still serious about rooting and installing magisk to make use of all of the really useful modules, you'll need:
An Unlocked Bootloader: Motorola's Own Guide
Keep in mind that unlocking the bootloader will wipe your phone and void its warranty, so be absolutely sure you want to do it and back up your files.
Then you'll need to manually patch a boot.img from your stock ROM (can be found here.) and flash it using ADB (Android Debug Bridge) using your PC.
I rooted mine within 3 days of owning it and have been enjoying it with no problems whatsoever ever since.
I used this guide as reference. If you have any questions you can always just message me here or on Telegram (@Kuntitled).
Click to expand...
Click to collapse
Hi thanks this really helped me get the grip of things haha.
I managed to unlock the bootloader but I'm a bit confused on what stock ROM you were referring to, the link you sent had a bunch of possibilities, I assume I need a reteu one since that's the name of my phone's software channel but there's a wide variety of them and the guide you sent seems to have their own ROM as well.
Either way thanks for all the help!

samjoebobtomted said:
Wait really I didn't even realize I didn't need a root for that lol.
Hi thanks this really helped me get the grip of things haha.
I managed to unlock the bootloader but I'm a bit confused on what stock ROM you were referring to, the link you sent had a bunch of possibilities, I assume I need a reteu one since that's the name of my phone's software channel but there's a wide variety of them and the guide you sent seems to have their own ROM as well.
Either way thanks for all the help!
Click to expand...
Click to collapse
You should check the Build Number under "About Phone" in settings, and match it what you find on that link i sent.

Question From USA to Italy, which factory image to load?

Hello everyone
I have a question for you who are more experienced. I'm missing from the Android ecosystem from the glorious Pixel 3 from Samsung, about 11 years ago. I loved the Pixel3 user interface, so polisched and modern for the times. Now I have finally decided to do the swith from my iPhone xs to Pixel 6 pro.
I bought the phone in USA, directly from google, but I live in Italy.
Do you advise me to flash the P6P with a different factory image?
I understand that the code name for P6P is raven, but it's not clear to me which factory image I should upload. Can you give me the right suggestion?
Thanks in advance for the support.
Regards,
Giuseppe

granosalis said:
Hello everyone
I have a question for you who are more experienced. I'm missing from the Android ecosystem from the glorious Pixel 3 from Samsung, about 11 years ago. I loved the Pixel3 user interface, so polisched and modern for the times. Now I have finally decided to do the swith from my iPhone xs to Pixel 6 pro.
I bought the phone in USA, directly from google, but I live in Italy.
Do you advise me to flash the P6P with a different factory image?
I understand that the code name for P6P is raven, but it's not clear to me which factory image I should upload. Can you give me the right suggestion?
Thanks in advance for the support.
Regards,
Giuseppe
Click to expand...
Click to collapse
Hi, I mention in this post which image is for where. https://forum.xda-developers.com/t/...a4-and-otas-for-017-016-a1-available.4384059/
I believe you want the Global one, SQ1D.211205.016.A1.

roirraW edor ehT said:
Hi, I mention in this post which image is for where. https://forum.xda-developers.com/t/...a4-and-otas-for-017-016-a1-available.4384059/
I believe you want the Global one, SQ1D.211205.016.A1.
Click to expand...
Click to collapse
Thanks,
I do not have the phone right now in my hands, and most probably this will not happen for the next 10 days. Maybe is's worth waiting for the Jan update?

granosalis said:
Thanks,
I do not have the phone right now in my hands, and most probably this will not happen for the next 10 days. Maybe is's worth waiting for the Jan update?
Click to expand...
Click to collapse
You're welcome! It's at least 50/50 chance that it would be better to wait. I have no problem on the .017 December firmware, but plenty of folks do, and I haven't had much of a problem at all with any of the firmwares so far.

What I do not understand is why there are those who force the installation of a release that has been intentionally removed from distribution. If google did there will be a reason, I think. But perhaps the benefits are greater than the disadvantages.

granosalis said:
What I do not understand is why there are those who force the installation of a release that has been intentionally removed from distribution. If google did there will be a reason, I think. But perhaps the benefits are greater than the disadvantages.
Click to expand...
Click to collapse
Because it fixes some things for some people.

So January update is finally here and, if I well understood is a Global (unified) version.
I have downloaded raven sq1d.220105.007 Factory.
And sorry for the stupid question, which is the best way to install it on a brand new, out of the box P6P?
I have to start the phone first and do the first configuration or I can immediately flash the factory image and start from a fresh new install? How?

granosalis said:
So January update is finally here and, if I well understood is a Global (unified) version.
I have downloaded raven sq1d.220105.007 Factory.
And sorry for the stupid question, which is the best way to install it on a brand new, out of the box P6P?
I have to start the phone first and do the first configuration or I can immediately flash the factory image and start from a fresh new install? How?
Click to expand...
Click to collapse
You'll have to allow the phone to boot up first since you'll need access to the OS to perform some commands on your PC. You can just allow the phone to boot and skip a lot of the setup process, only because flashing the most recent factory image will put you back to stock, AKA wipe your phone back to where it was when it left the factory, and then once the new image has been installed you can do a proper phone setup from scratch.
If you're not familiar with using terminal commands and don't want to run the risk of messing up your phone, I suggest you use the Android Flash Tool since it'll do everything for you and is fairly simple. Just connect your device over USB and visit the Android Flash Tool using the link below. Android Flash Tool works with any Web browser that supports WebUSB, such as Chrome or Edge. The Android Flash Tool guides you step-by-step through the process of flashing your device - there's no need to have tools installed, but you will need to unlock your device and enable USB Debugging from Developer Options.
I've provided a link on how to enable USB Debugging and Developer Options, here - https://source.android.com/setup/contribute/flash
To flash the latest January Stock image on your device, simply visit this link - https://flash.android.com/build/8030436?target=raven-user&signed
Click through those links and see if it all makes sense; and if not, report back. Either I (or someone else) will be happy to help.

RetroTech07 said:
Click through those links and see if it all makes sense; and if not, report back. Either I (or someone else) will be happy to help.
Click to expand...
Click to collapse
I would like to thank you. You were really very helpful.
I have a doubt: what's the difference between loading a Factory image with ADB and using the Android Flash tool?

They do the same thing, however the android flash tool is much easier to use.

granosalis said:
What I do not understand is why there are those who force the installation of a release that has been intentionally removed from distribution. If google did there will be a reason, I think. But perhaps the benefits are greater than the disadvantages.
Click to expand...
Click to collapse
I forced it on day one and I guess I was one of the lucky ones that didn't have any issues.

granosalis said:
I would like to thank you. You were really very helpful.
I have a doubt: what's the difference between loading a Factory image with ADB and using the Android Flash tool?
Click to expand...
Click to collapse
You're welcome! I'm assuming all went well and you're on the latest release?
The flash tool is automated and much simpler. it's a better way to make sure you're fully stock if you were planning on selling the device or trading it in.
Think of ADB as a more advanced way of interacting with your phone when you plan on modifying it from stock. The flash tool only allows you to flash official Google images, unless a developer has implemented the same tool with a custom ROM they've developed that you plan on using.
I'm sure there's other things I'm missing that folks will chime in with.

RetroTech07 said:
You're welcome! I'm assuming all went well and you're on the latest release?
The flash tool is automated and much simpler. it's a better way to make sure you're fully stock if you were planning on selling the device or trading it in.
Think of ADB as a more advanced way of interacting with your phone when you plan on modifying it from stock. The flash tool only allows you to flash official Google images, unless a developer has implemented the same tool with a custom ROM they've developed that you plan on using.
I'm sure there's other things I'm missing that folks will chime in with.
Click to expand...
Click to collapse
No my phone should arrive in about 10 days if everything goes as planned.
It is not easy to take a P6P 256gb white from italy , this model, in fact, is not sold in europe for what I know.
While waiting I try to keep myself informed. It's been a long time since my Galaxy Nexus.