Question Widevine - ASUS ZenFone 8

Hi guys. Can you do me a favour and check your widevine version please. Cause I haven't done anything to my phone like rooting or unlocking and got downgraded to L3 from the factory L1. System version: 30.11.51.115

L1 here, rooted with magisk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Unluck then. I've read an article saying this kept happening with the ROG5 and Zenfone 7 in the past. Hope they fix it soon. Thanks for the reply!

L1 is what you want to play 1080 content on netflix. no?

Yes

[email protected] said:
Hi guys. Can you do me a favour and check your widevine version please. Cause I haven't done anything to my phone like rooting or unlocking and got downgraded to L3 from the factory L1. System version: 30.11.51.115
Click to expand...
Click to collapse
hey,
there´s a bug on qcom side, that caused qcom based devices to randomly fall back to widevine L3 when rebooting on previous gen qcom SoCs. It happened to me too on ZF7 since I probably booted a few hundred times during development of my kernel.
It might be that qcom didn´t fix this issue and it still can happen on the sd888. It´s triggered by just a reboot, doesn´t matter if unlocked, locked, unrooted or rooted.
Could you please post your issue on zentalk? Just a thread stating which firmware you´re using, that your phone is locked was never rooted and the issue happened out of the blue to you. It´s important so Asus can investigate and acknowledge that bug. They fixed it on ROG3 and Zenfone 7 too, so they might have to do the same here.
ZenFone 8
zentalk.asus.com

Freak07 said:
Could you please post your issue on zentalk?
ZenFone 8
zentalk.asus.com
Click to expand...
Click to collapse
I would also recommend to send technical request to their support. They'll send it directly to software devs.
Usually I do it in two ways (zentalk + technical support). And for example my last request was fixed in .115 update which means that they at least read our inquiries
By the way, how to check mine status of widevine? Is it some SW or I can do that with terminal (Termux for example) ?

dron39 said:
I would also recommend to send technical request to their support. They'll send it directly to software devs.
Usually I do it in two ways (zentalk + technical support). And for example my last request was fixed in .115 update which means that they at least read our inquiries
By the way, how to check mine status of widevine? Is it some SW or I can do that with terminal (Termux for example) ?
Click to expand...
Click to collapse
DRM Info - Apps on Google Play
Shows DRM information (Widevine, PlayReady, etc) from Android DRM Framework
play.google.com
Devcheck app can also display it.
Or check logcat when opening an app that request widevine status.

Freak07 said:
hey,
there´s a bug on qcom side, that caused qcom based devices to randomly fall back to widevine L3 when rebooting on previous gen qcom SoCs. It happened to me too on ZF7 since I probably booted a few hundred times during development of my kernel.
It might be that qcom didn´t fix this issue and it still can happen on the sd888. It´s triggered by just a reboot, doesn´t matter if unlocked, locked, unrooted or rooted.
Could you please post your issue on zentalk? Just a thread stating which firmware you´re using, that your phone is locked was never rooted and the issue happened out of the blue to you. It´s important so Asus can investigate and acknowledge that bug. They fixed it on ROG3 and Zenfone 7 too, so they might have to do the same here.
ZenFone 8
zentalk.asus.com
Click to expand...
Click to collapse
Yes I saw an article stating that that happened with the ROG5 and ZF7 but nona of those described why and how it happened. I didn't want to make another account for the forums so I used the app on the phone to contact them and got a reply from a representative with some instructions. ( Basically factory reset)
dron39 said:
I would also recommend to send technical request to their support. They'll send it directly to software devs.
Usually I do it in two ways (zentalk + technical support). And for example my last request was fixed in .115 update which means that they at least read our inquiries
By the way, how to check mine status of widevine? Is it some SW or I can do that with terminal (Termux for example) ?
Click to expand...
Click to collapse
Thanks and that's what I did. I've used the built-in bug report app. Will it reach the devs? Cause I've been having another strange bug with playback and probably should report it.

[email protected] said:
Yes I saw an article stating that that happened with the ROG5 and ZF7 but nona of those described why and how it happened. I didn't want to make another account for the forums so I used the app on the phone to contact them and got a reply from a representative with some instructions. ( Basically factory reset)
Thanks and that's what I did. I've used the built-in bug report app. Will it reach the devs? Cause I've been having another strange bug with playback and probably should report it.
Click to expand...
Click to collapse
If you can spare the time open a topic on zentalk. It's the best way to really reach them.
I suppose it's still at L3 even after factory reset.
You can mention that on zentalk too.

Ok ok I'll do that this weekend. Thanks for the help!

morpheus302 said:
L1 here, rooted with magiskView attachment 5409075
Click to expand...
Click to collapse
Stupid question but the bootloader is unlocked, right?

Userspace said:
Stupid question but the bootloader is unlocked, right?
Click to expand...
Click to collapse
On ZF8 bootloader unlocking doesn't downgrade it.

Related

What's the latest on Unlocking the XZ3 Bootloader - DRM (EU model - Feb 19)

While I found some good info in the 'state of root for the XZ3' Q&A, that does not work well using the XDA Labs app, and I want to be sure I know what's going on before I do something stupid.
To my understanding from a news update on XDA here, the XZ3 camera does not break when unlocking. So, here are the steps I believe I need to take (EU version from Clove)
1) Unbox, connect to my wifi and run the updates. Update level I need is at least 52.0.A.84.
2) Checkbox for unlocking now available (under development section). Unlock the bootloader. (camera works after this)?
3) Update firmware to 52.0.A.126 via xperafirm
If I want TWRP / Root
4) Install TWRP per instructions (I read that this breaks Camera again)
5) Install TWRP camera fix
6) Install Magisk and the module to fix DRM.
As I understand it, even the DRM fix will not bring back some of the Sony stuff - Triluminous display settings, xreality, dynamic contrast enhancer, LDAC audio? and dolby ATMOS? If anyone can test those and see if they work, that'd be awesome.
Are my steps correct? Am I missing anything?
TIA!
charlatan01 said:
4) Install TWRP per instructions (I read that this breaks Camera again)
Click to expand...
Click to collapse
It is the unlocking step that breaks the camera, not TWRP/Magisk.
charlatan01 said:
As I understand it, even the DRM fix will not bring back some of the Sony stuff - Triluminous display settings, xreality, dynamic contrast enhancer, LDAC audio? and dolby ATMOS? If anyone can test those and see if they work, that'd be awesome.
Click to expand...
Click to collapse
Triluminos/X-Reality/Dynamic contrast are arguably "features" that you'd rather lose than keep. In 7 years of owning Xperia devices I have never used them. There is a generic "super-vivid" mode that replaces X-Reality after unlocking the boot loader:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LDAC doesn't appear to be affected, although I don't have a suitable device to test it with:
As for Atmos, I think I uninstalled that app immediately, and it looks like it's not available as an apk that I could find easily so I can't test it for you. I think it's unaffected by the unlock, though.
Glancing over at the camera fix thread on the XZ2 forum, it looks like 163 is safe to flash (instead of 126), but 202 is unknown. If you're unlocking anyway, you might want to test it and report back whether the camera fix still works on 202. If it doesn't, you can always use Newflasher to downgrade to 163. For the time being, I'm holding off on flashing anything as the main two things I would like are Resurrection Remix and a working port of GCam with Night Sight, both of which are unavailable for the XZ3 as of writing.
mufunyo said:
It is the unlocking step that breaks the camera, not TWRP/Magisk.
Click to expand...
Click to collapse
Right, sorry. I meant to ask... from my reading the camera 'shouldn't' break. I suppose it's okay if it does as long as I can fix it.
Thanks for posting the screens / functional differences.
mufunyo said:
I would like are Resurrection Remix and a working port of GCam with Night Sight, both of which are unavailable for the XZ3 as of writing.
Click to expand...
Click to collapse
Bingo! I would LOVE to have RR, or maybe Slim available.. and yeah, a working GCAM would be amazing.
Hoping as prices fall this device gets in the hands of some more folks in the modding community... not that I have any complaints with all the work that @MartinX3 and others are providing!
Working GCam will only be on AOSP-based ROMs like Lineage and RR, and depends on full Camera2 support.
So, it is officially supported by SONY https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
but which one are up to now the benefit we can get?
sev7en said:
So, it is officially supported by SONY https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
but which one are up to now the benefit we can get?
Click to expand...
Click to collapse
The warning is full of 'ifs' and 'may bes'. Honestly, there isn't much to dislike about Sony's ROM, so I really only want the unlocked bl to root and remove Facebook.
Root is becoming less of a requirement in my eyes, but you may find some need for it.
charlatan01 said:
The warning is full of 'ifs' and 'may bes'. Honestly, there isn't much to dislike about Sony's ROM, so I really only want the unlocked bl to root and remove Facebook.
Root is becoming less of a requirement in my eyes, but you may find some need for it.
Click to expand...
Click to collapse
I love that stock but I installed NOVA as now we lost also the themes...
I would get a better camera support as for the GCAM. The quality of the shoots of XZ3 is really poor. I did a comparison with my R1 and it is top-down everything.
Just an update to my original post - .126 is the current US custom version. Because I want to use VOLTE on Tmobile, I'll be using that for my base. I'd like to update to 202, but I'll need to wait for Sony to catch up
Camera Noise reduction isnt affected?
Unlocking under 202 does not affect
Hello! I'm researching which camera features are missing after unlocking this device. What I found out is: We have full Camera 2 support including RAW. So is everything fine now or is the image quality still not as good as on an unlocked device? I can't find any comparison photos.
What I also don't know yet is: Is good photo quality bound to the sony camera app or some driver or service?
Also I read about upgrading or downgrading the firmware to a target firmware to save keys for future use. I found no way to do this without unlocking the bootloader first.
my phone get bootloader unlocked no a can unlokin or not

Just bought Mi 9 Lite and I have some questions

Everytime I have had an android smartphone, I unlocked and rooted straight away. I know what benefits unlocking the bootloader and rooting the ROM bring to the whole experience of using the smartphone but I have never actually looked or thought about the negative effects of unlocking and rooting.
I just received my Mi 9 Lite last night and I am just about the unlock its bootloader and get Magisk flashed. But before I do that, I am interested in people's opinion about what they think of rooting their phone.
- Can I root the stock ROM without unlocking the bootloader? I have heard this is possible but no idea how! If yes, does it have any limitations or is it the same as rooting after unlocking the bootloader?
- Does anyone have any other valid reason for not unlocking their device except warranty and maybe system updates? They always warn you about security, system updates and finger print sensors not working etc... is this true?
About the system updates, usually Xiaomi publishes the flashable ROM on their website which I can download and flash it manually so I don't have to worry about missing out on ROM updates.
Warranty wise, I am not too concerned either.
Security wise, I don't think this is an issue too as I always know what I would be flashing and installing on my phone.
Thank you.
I used some rooted device before . Don't no what you need, but, with this phone WITH NO ROOT, it's possible to uninstall or freeze some app, using blokada, you can stop/ block many thing.... and keep a clean and fresh device, with no mod, like out of the box ; )
I'm also getting this phone, can anyone from Europe confirm if Mi 9 Lite supports Carrier Aggregation? (LTE+)
k3lcior said:
I'm also getting this phone, can anyone from Europe confirm if Mi 9 Lite supports Carrier Aggregation? (LTE+)
Click to expand...
Click to collapse
Had the 4g+ logo out and about yesterday if that's what you mean?
technotika said:
Had the 4g+ logo out and about yesterday if that's what you mean?
Click to expand...
Click to collapse
Yes, but are you from Europe?
k3lcior said:
Yes, but are you from Europe?
Click to expand...
Click to collapse
For the time being - 'UK'
got the 4G+ in France too
4G+ in Sweden as well
Skickat från min Mi A2 via Tapatalk
Welp. I tried unlocking yesterday and I got the message saying I need to wait 168 hours. Damn.
One reason to maybe not root/unlock is it can stop NFC payments being made?
Just got my phone and i'm super impressed so far (especially by screen), the performance is surprisingly good aswell. Now waiting 168h for bootloader unlock..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And...what are the questions now?
@Jeanz Sensation, also expecting mine next year and ll be pleased if you or someone can tell me what's the actual available internal memory in 128gb version?.........thanks in advance.
Jeanz Sensation said:
I just received my Mi 9 Lite last night and I am just about the unlock its bootloader and get Magisk flashed. But before I do that, I am interested in people's opinion about what they think of rooting their phone.
Click to expand...
Click to collapse
Please tell us, why you could unlock the bootloader without 168 hours of waiting?
Jeanz Sensation said:
Everytime I have had an android smartphone, I unlocked and rooted straight away. I know what benefits unlocking the bootloader and rooting the ROM bring to the whole experience of using the smartphone but I have never actually looked or thought about the negative effects of unlocking and rooting.
I just received my Mi 9 Lite last night and I am just about the unlock its bootloader and get Magisk flashed. But before I do that, I am interested in people's opinion about what they think of rooting their phone.
- Can I root the stock ROM without unlocking the bootloader? I have heard this is possible but no idea how! If yes, does it have any limitations or is it the same as rooting after unlocking the bootloader?
- Does anyone have any other valid reason for not unlocking their device except warranty and maybe system updates? They always warn you about security, system updates and finger print sensors not working etc... is this true?
About the system updates, usually Xiaomi publishes the flashable ROM on their website which I can download and flash it manually so I don't have to worry about missing out on ROM updates.
Warranty wise, I am not too concerned either.
Security wise, I don't think this is an issue too as I always know what I would be flashing and installing on my phone.
Thank you.
Click to expand...
Click to collapse
Don't try to flash or modify anything on an Xiaomi with locked bootloader, you have many different ways to hardbrick device xD ?

What version of stock rom do you use?

Hello everyone, I got few questions.
As the title says, which version of stock rom do you use? Does it have any issues, are you rooted or not, green camera even with TA keys provisioned? Asking because, while I was following tutorial I couldn't pull out TA-unlocked.img, it said that file doesn't exist. I pulled entire /data/local/tmp folder and it showed 3 renoroot files and one "g+fffffffffffffff+fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff" file which is 12kb in size. I have green camera in Oreo, so Oreo is no go for me. Looking for decent stock Pie version, because latest one has touchscreen issues, it becomes unusable for 5-6 seconds and then works and stops working. Also, someone mind directing me to which TWRP should I use for PIE to install Magisk and other things, would be really nice. Any help is wellcome.
The last pie stock "2.2.8 should not have touchscreen issues, or any other firmware. If you have issues, and you still have warranty, try to send it it. Sony, in my opinion, is notorious for their touchscreen issues. I experienced touchscreen issues on z3 compact and z5 compact EOL. I suspect the same will happen with xz1 compact, unfortunately. However I am on my 3rd original screen repair/replacement , so hopefully it will last a bit longer this time.
mcmanuf said:
The last pie stock "2.2.8 should not have touchscreen issues, or any other firmware. If you have issues, and you still have warranty, try to send it it. Sony, in my opinion, is notorious for their touchscreen issues. I experienced touchscreen issues on z3 compact and z5 compact EOL. I suspect the same will happen with xz1 compact, unfortunately. However I am on my 3rd original screen repair/replacement , so hopefully it will last a bit longer this time.
Click to expand...
Click to collapse
Phone is not under warranty, so that is out of question, also don't want to lose waterproofing. This touchscreen issue happens only on Pie, currently I can find only latest pie and latest LineageOS, who aswell have that issue, while no issue occurs on stock Oreo, besides green camera.
Frano35 said:
Asking because, while I was following tutorial I couldn't pull out TA-unlocked.img
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
adb pull /data/local/tmp/TA-locked.img
Have you done a full wipe when installing the latest ROM? I've updated 3 times to Pie and come back to Oreo within hours due to certain issues so you may live to regret not following the guide properly.
SXUsr said:
adb pull /data/local/tmp/TA-locked.img
Have you done a full wipe when installing the latest ROM? I've updated 3 times to Pie and come back to Oreo within hours due to certain issues so you may live to regret not following the guide properly.
Click to expand...
Click to collapse
I did as the guide said, and I have done it all on Oreo. I have pulled TA-Locked.img and later it said to pull TA-Unlocked.img and push TA-Locked.img. I tried pulling out entire tmp folder but it had only renoroot files and weirdly named one. Then I pushed back locked img and did rest as guide says. I have attest key provisioned but not SOMC Fido and SOMC Attest. Any idea if I can still fix it?
Frano35 said:
Any idea if I can still fix it?
Click to expand...
Click to collapse
If you still have your TA-Locked.img then yes, the unlocked one is for "(for future comparisons)".
Start from scratch with the guide and redo the restoration of the locked TA img. If it doesn't work you're doing something wrong.
SXUsr said:
If you still have your TA-Locked.img then yes, the unlocked one is for "(for future comparisons)".
Start from scratch with the guide and redo the restoration of the locked TA img. If it doesn't work you're doing something wrong.
Click to expand...
Click to collapse
Do I need to flash back to Oreo or I can do it from LOS16?
Frano35 said:
Do I need to flash back to Oreo or I can do it from LOS16?
Click to expand...
Click to collapse
You tell me.

Unable to unlock bootloader {RESOLVED}

This is my first time posting on this forum, please do correct me if I'm doing something wrong or haven't provided some information I should have.
DEVICE: Redmi 4x (santoni) [Indian Version] running on MIUI 11.0.2 | Stable.
I've been trying to unlock to bootloader for this device for about a month but it always seem to run into some error while running the official miunlock tool (latest). Along with the offiicial tool i've been trying to use XioamiToolV2(latest) as well but sadly it throws the same errors
I've tried most of the suggestions dropped here on XDA as well as Reddit, but none of them seem to work for me.
error from mi unlock tool & xiaomitoolv2:
https://imgur.com/a/h64uuLw
Please guide me through the process if there's something i could do.
I use windows 10 btw & required drivers are up to date.
PS: English is not my first language, please ignore grammatical errors
mi-saan said:
This is my first time posting on this forum, please do correct me if I'm doing something wrong or haven't provided some information I should have.
DEVICE: Redmi 4x (santoni) [Indian Version] running on MIUI 11.0.2 | Stable.
Click to expand...
Click to collapse
Check here that everything is correct:
https://c.mi.com/thread-1857937-1-1.html
try with an older version.
Check that your phone appears here
https://us.i.mi.com/
Login with flash code
put the program at the root of your disk.
NOSS8 said:
Check here that everything is correct:
https://c.mi.com/thread-1857937-1-1.html
try with an older version.
Check that your phone appears here
https://us.i.mi.com/
Login with flash code
put the program at the root of your disk.
Click to expand...
Click to collapse
I can see my device on Xiaomi Cloud and have already used the "Find Device" option as well to double check.
can you suggest some old version? i have already tried my luck using some of the old unlock tools available but unfortunately it doesn't work
i'm not familiar with flash code. can you tell me what it is ?
TIA
https://imgur.com/a/VCazgo3
mi-saan said:
I can see my device on Xiaomi Cloud and have already used the "Find Device" option as well to double check.
can you suggest some old version? i have already tried my luck using some of the old unlock tools available but unfortunately it doesn't work
i'm not familiar with flash code. can you tell me what it is ?
TIA
Click to expand...
Click to collapse
Use mail for login or
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All version
https://xiaomifirmware.net/xiaomi-mi-unlock-tool-all-versions/
NOSS8 said:
Use mail for login or
View attachment 5636617
View attachment 5636619​
Click to expand...
Click to collapse
logging in isn't a concern, but the upcoming process after that is. refer the screenshots posted below.
Further addition:
the process seems to fail at 99%
https://imgur.com/a/h64uuLw
EDIT:
seems logging in is also a problem atm
https://imgur.com/a/Kz5hGLT
mi-saan said:
logging in isn't a concern, but the upcoming process after that is. refer the screenshots posted below.
Further addition:
the process seems to fail at 99%
https://imgur.com/a/h64uuLw
Click to expand...
Click to collapse
Paired Mi account under Developer Options / Mi Unlock status
OEM unlocking is enabled
USB Debugging enabled
All this is ok?
try change usb2 port and/or cable
Old version post above
If still failing:
Logout mi account, reboot and login.
or reset your phone
Done already
already changed the cable and usb port
seems now i have to try the old tools one by one
the problems i am facing rn is already raised by someone in this forum and i've tried the solution offered there as well but nothing seems to work
Similar query : https://forum.xda-developers.com/t/help-unable-to-unlock-bootloader.4422491/
"seems now i have to try the old tools one by one "
start with the V3 versions
NOSS8 said:
"seems now i have to try the old tools one by one "
start with the V3 versions
Click to expand...
Click to collapse
tried every tool out there sadly it doesn't work
mi-saan said:
tried every tool out there sadly it doesn't work
Click to expand...
Click to collapse
Try to:
Log out on the phone.
Go to https://us.i.mi.com/
and delete all phones.
Reboot the phone.
Login on the phone.
Try.
In Miflash unlock and the phone ,use mail adress for login.
i went beyond that.
i made a new account w/different region as well. still not working
https://imgur.com/a/neRWTWM
kinda fed up with this issue now. maybe it's not worth it to pursue this any further since i'm doing this for about 2 months with no development whatsoever
mi-saan said:
i went beyond that.
i made a new account w/different region as well. still not working
https://imgur.com/a/neRWTWM
kinda fed up with this issue now. maybe it's not worth it to pursue this any further since i'm doing this for about 2 months with no development whatsoever
Click to expand...
Click to collapse
Is this good?
can you please elaborate?
as far as i understand do you want me update the drivers? i don't see the need to do that since i have recently unlocked a different device without any issues.
mi-saan said:
can you please elaborate?
as far as i understand do you want me update the drivers? i don't see the need to do that since i have recently unlocked a different device without any issues.
Click to expand...
Click to collapse
Just click on the gear in the top right and check.
https://romprovider.com/solved-couldnt-unlock-cant-get-info-connect/
NOSS8 said:
Just click on the gear in the top right and check.
https://romprovider.com/solved-couldnt-unlock-cant-get-info-connect/
Click to expand...
Click to collapse
https://imgur.com/a/zw9c4Sf
old version miunlock tool :
https://imgur.com/a/Tf2gW10
still stuck after 99%, getting the error: can't get info, couldn't unlock
mi-saan said:
https://imgur.com/a/zw9c4Sf
old version miunlock tool :
https://imgur.com/a/Tf2gW10
still stuck after 99%, getting the error: can't get info, couldn't unlock
Click to expand...
Click to collapse
Hi,
Have You found solution to your redmi 4x problem?
I have the same problem, I tried all the advice I found on the internet and still nothing,
I can't unlock it.
Regards
IJ
no luck as of now. i am not going to pursue this issue any further as there's no solution available out there. peace out
It seems to be a recurring problem on this device.
I saw this and the guy says he waited 5 days for it to work.
" If unlocking does not work in first try, don't keep trying again and again (don’t try at one time)..just give a break and try unlocking again for the next week."
mi-saan said:
no luck as of now. i am not going to pursue this issue any further as there's no solution available out there. peace out
Click to expand...
Click to collapse
Have you tried to create and try with another Xiaomi account?

Question Android 13 DP1 locked bootloader !!!

I installed A13 DP1 my OP10Pro(NE2215) software but it is not working with a locked bootloader.cannot get pass the password setup screen or connect any wifi also it keeps saying try another PW option.i cant fastboot any stock rom it says locked bootloaders cannot do this.I cant enable oem unlocking dot in developer settings because i cant pass setup screen.phone is stuck this stitution.any method for EDL tool or for unlock oem unlock ?
Well if you can't get past the screen you'll have to contact support and see if they can remotely flash your device with the stock software. If they can't/won't do this, you will have to send the device in for service. Without an unlocked bootloader, there's nothing you can do.
If they do it, try to snag the MSM files before they can delete them
EtherealRemnant said:
Well if you can't get past the screen you'll have to contact support and see if they can remotely flash your device with the stock software. If they can't/won't do this, you will have to send the device in for service. Without an unlocked bootloader, there's nothing you can do.
If they do it, try to snag the MSM files before they can delete them
Click to expand...
Click to collapse
Hahaha .thx for replying.i wrote and waiting.
Issue video
VID_20220615_015451_01.mp4
drive.google.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you hit the X in the top left, does it give you the option to skip setting a password?
EDIT: Nevermind, watched the video again and I see it just takes you back and makes you do it again.
I assume you tried factory reset from stock recovery too to make sure nothing got corrupted?
This is why I always unlock my bootloader before I tinker with anything.
Hopefully they agree to remotely flash it for you.
I did
EtherealRemnant said:
If you hit the X in the top left, does it give you the option to skip setting a password?
EDIT: Nevermind, watched the video again and I see it just takes you back and makes you do it again.
I assume you tried factory reset from stock recovery too to make sure nothing got corrupted?
This is why I always unlock my bootloader before I tinker with anything.
Hopefully they agree to remotely flash it for you.
Click to expand...
Click to collapse
You could sure I did factory reset in fastbootd screen but same result like a video .
metrixx02 said:
I did
You could sure I did factory reset in fastbootd screen but same result like a video .
Click to expand...
Click to collapse
That's unfortunate. I hope you can get them to fix it for you.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
I solve it and wrote solution.just fallow this .
Could be a chance to get the log in for MSM??
Just saying.
dladz said:
Could be a chance to get the log in for MSM??
Just saying.
Click to expand...
Click to collapse
He said on the OnePlus forum that they didn't even answer. It seems like it's probably true that they aren't going to do remote flashing anymore for devices outside of China.
EtherealRemnant said:
He said on the OnePlus forum that they didn't even answer. It seems like it's probably true that they aren't going to do remote flashing anymore for devices outside of China.
Click to expand...
Click to collapse
Ok so that's the last straw.
This is my final OnePlus device.
I really hope the tensor chip v2 does a job cos that the only avenue I'd consider at this point unless the nothing phone actually is decent.. Which I can't see.
OnePlus is screwed..
Why the hell did I sell my 8 pro.
What is the point of having a development forum for a device that isn't being developed for?
I'm done with the turd, it's a bullet taken nothing more.. I took one on the note 4 and the Evo 3D
Thought I was past all that.
Jesus.
If we were to get ROMs they'd have been out by now, it's not happening mate, period.
OnePlus is the new HTC. All that promise and no desire to stay faithful.
It is what it is, I won't buy another 1+ again.
Pixel only now
dladz said:
Ok so that's the last straw.
This is my final OnePlus device.
I really hope the tensor chip v2 does a job cos that the only avenue I'd consider at this point unless the nothing phone actually is decent.. Which I can't see.
OnePlus is screwed..
Why the hell did I sell my 8 pro.
Click to expand...
Click to collapse
Yeah it's incredibly disappointing that they're going so south with regards to being dev friendly, the same way Samsung did.
I tried extracting the OnePlus 10 Pro ColorOS MSM to see if it can be tweaked to flash units from other regions like regular MSM Tools can and the publicly-available decryption tools don't even work on it. I figured yeah, ColorOS sucks, but being able to unbrick and then use fastboot enhanced to get back to the right firmware would be a much better option but no, the MSM Tool they provide with it requires a technician to log in and the encryption method on the files is different from OnePlus OPS files OR Oppo OFP files.
EtherealRemnant said:
Yeah it's incredibly disappointing that they're going so south with regards to being dev friendly, the same way Samsung did.
I tried extracting the OnePlus 10 Pro ColorOS MSM to see if it can be tweaked to flash units from other regions like regular MSM Tools can and the publicly-available decryption tools don't even work on it. I figured yeah, ColorOS sucks, but being able to unbrick and then use fastboot enhanced to get back to the right firmware would be a much better option but no, the MSM Tool they provide with it requires a technician to log in and the encryption method on the files is different from OnePlus OPS files OR Oppo OFP files.
Click to expand...
Click to collapse
Ping it to me please if you have it.. I'll see if I can get it cracked.
Afaik people have had repairs with the MSM outside of China, or so I've heard anyway.
I may know someone who can remove the validation
dladz said:
Ping it to me please if you have it.. I'll see if I can get it cracked.
Afaik people have had repairs with the MSM outside of China, or so I've heard anyway.
I may know someone who can remove the validation
Click to expand...
Click to collapse
one plus support team offered me remote flash .but i solved already i hope u can contact them and solve ur problem
so i have to unlock bootloader to install A13 ?
I have some inquiries if it’s not too much trouble, guide me about this. These inquiries are displayed underneath here:
https://forum.xda-developers.com/t/...ntly-being-sold-prime-day-discussion.4465075/
Sitting tight for most appropriate response straightaway. I’m excessively confounded here.
For me it worked without unlocking bootloader. There was everything normal expect having no network signal.
Try to factory reset in bootloader

Categories

Resources