Related
I caved and did the 9.0 update. Aux no longer auto detected, camera random fail, screen decides what it wants to click some times. My question is would a rom fix these issues? I haven't rooted or anything since I owned a galaxy s3 or 4 so any suggestions on how to go about this are welcome.
First what region on your?
What device model are you?
Did you flash tool or over the air update?
To me sounds like your update messed up.
Rooting would fix that. I use lineage official and I'm very happy with it. Literally zero issues.
lonewolfbtown said:
First what region on your?
What device model are you?
Did you flash tool or over the air update?
To me sounds like your update messed up.
Rooting would fix that. I use lineage official and I'm very happy with it. Literally zero issues.
Click to expand...
Click to collapse
Yeah I have a h3223. So far im having so many issues just getting it rooted. Also im in the U.S
If I custom romantic can't fix it, it would be a phone issue. But I can go ahead and help you out.
First you want to unlock the bootloader. Plenty of guides out there. But if your lazy I can find or write a guide tomorrow
Ok so i will try to go straight to the point.
I got OnePlus 7 that i bought from Aliexpress (8gb and 256gb) the thing is that im almost 90% sure this phone is defective.
You can use teh phone correctly for about 2 days then all of a sudden it will freeze completely and then you CANT do absolutely anything else, not even turn it off by holding power button ..
So i just left it there until it ran out of battery.
Then i charge while inside the fastboot and when i try to boot it is in a boot loop , doesnt even go into the boot animation
and to make things even more interesting i tried to wipe data guess what? The phone screen suddendly started blinking until again it ran out of battery. (you could see for a split of a second every time the screen blinks the progress bar of the wipe but it never moved from initial point).
So yea at this point is pretty obvious that something is wrong so i bought a Mi9T Pro meanwhile but i dont want this phone to go to waste.
Anyone out there has a clue of what could be? I wanna attempt to fix it myself if possible.
Aliexpress just gave a bit of the money back and the company Hongkong Goldway didnt give a f and they even go as far as to pretend they don't know what i'm saying ( the language barrier when it beneficial for them ).
This was gonna be a short explanation but i guess it was neccesary to be this long to explain correctly whats going on.
BTW: the only way yo make the phone work again for 2 days mayebe 3 is by using the MSM tool , any other method doesnt work.
also when it was working i filled the whole 256gb to kinda check the internal memory for corruption but it actually filled up without any problem so idk .
The problem isn't the phone, the problem is you. Clearly you stuffed the phone up yourself by trying to mod/root it and now you have ruined it further by flashing incorrect images to the device.
You shouldn't be coming to XDA when the fault is entirely on you, I've seen it all before.
@PriPhaze is your device stock(bootloader locked) or modified in any way?
aaycce said:
The problem isn't the phone, the problem is you. Clearly you stuffed the phone up yourself by trying to mod/root it and now you have ruined it further by flashing incorrect images to the device.
You shouldn't be coming to XDA when the fault is entirely on you, I've seen it all before.
Click to expand...
Click to collapse
Really? Lol it's that the best you could say? Trying to sound smart eh ? lmao
Clearly you don't know what you saying so you are not the person I'm looking for but "thanks" for such "helpful" respond.
strongst said:
@PriPhaze is your device stock(bootloader locked) or modified in any way?
Click to expand...
Click to collapse
Hi, the device is unlocked right now. I didn't install any other ROM other than OOS.
PriPhaze said:
Really? Lol it's that the best you could say? Trying to sound smart eh ? lmao
Clearly you don't know what you saying so you are not the person I'm looking for but "thanks" for such "helpful" respond.
Hi, the device is unlocked right now. I didn't install any other ROM other than OOS.
Click to expand...
Click to collapse
Thank you for the reply. Is the bootloader just unlocked or do you have installed anything like twrp, magisk or others?
Which version of OxygenOS do you have?
strongst said:
Thank you for the reply. Is the bootloader just unlocked or do you have installed anything like twrp, magisk or others?
Which version of OxygenOS do you have?
Click to expand...
Click to collapse
Thanks to you
Ahh yes twrp was installed but now it's inaccessible .
After the phone freezed I can no longer use twrp.
Also yes magisk was installed to restore my apps using swift backup.
OOS version is the last one available.
PriPhaze said:
Thanks to you
Ahh yes twrp was installed but now it's inaccessible .
After the phone freezed I can no longer use twrp.
Also yes magisk was installed to restore my apps using swift backup.
OOS version is the last one available.
Click to expand...
Click to collapse
It might be a good idea to use unbrick tool and clean flash the stock OxygenOS, recovery and remove root to see if it behaves better.
strongst said:
It might be a good idea to use unbrick tool and clean flash the stock OxygenOS, recovery and remove root to see if it behaves better.
Click to expand...
Click to collapse
I did, same behaivor ; in 2 days more less it will freeze and reboot and then system will be gone.
And so i need to use MSM tool again to get it back running. The only thing i have not tried is to use a custom ROM insetad of OOS
PriPhaze said:
I did, same behaivor ; in 2 days more less it will freeze and reboot and then system will be gone.
And so i need to use MSM tool again to get it back running. The only thing i have not tried is to use a custom ROM insetad of OOS
Click to expand...
Click to collapse
Maybe I did not understand correctly: Did you tried the stock rom without unlocking the bootloader and magisk? Or did you immediately unlock and install magisk immediately and then test?
The stock rom is stable and should work, otherwise a hardware issue can be the problem why you have those issues.
strongst said:
Maybe I did not understand correctly: Did you tried the stock rom without unlocking the bootloader and magisk? Or did you immediately unlock and install magisk immediately and then test?
The stock rom is stable and should work, otherwise a hardware issue can be the problem why you have those issues.
Click to expand...
Click to collapse
Yea tried with locked bootloader and then unlocked .
So yea maybe i wasn't clear enough but what i meant with the first post is that im 90% sure that here is a hardware issue but i dont really know what could be and there is not repair service in my country.
Thats why the only option i have left is to figure out what is wrong and change that part.
Iwas hoping someone could guide me to figure out which part i need to change.
PriPhaze said:
Yea tried with locked bootloader and then unlocked .
So yea maybe i wasn't clear enough but what i meant with the first post is that im 90% sure that here is a hardware issue but i dont really know what could be and there is not repair service in my country.
Thats why the only option i have left is to figure out what is wrong and change that part.
Iwas hoping someone could guide me to figure out which part i need to change.
Click to expand...
Click to collapse
Hmm, I can't tell you which part to exchange cause it can be the processor, flash for example which you cannot exchange. Battery might be an option, but that's not really the culprit imo...
strongst said:
Hmm, I can't tell you which part to exchange cause it can be the processor, flash for example which you cannot exchange. Battery might be an option, but that's not really the culprit imo...
Click to expand...
Click to collapse
Well in any case the cpu and internal memory are in the same board no? so that probably means i would need to change the whole board wich is 250US
PriPhaze said:
Well in any case the cpu and internal memory are in the same board no? so that probably means i would need to change the whole board wich is 250US
Click to expand...
Click to collapse
Yes, everything is on board. It's the worst case for, sadly...
Or you buy a device with broken screen and exchange the board /display. Depends how much you have to spent for this at all.
PriPhaze said:
Ok so i will try to go straight to the point.
I got OnePlus 7 that i bought from Aliexpress (8gb and 256gb) the thing is that im almost 90% sure this phone is defective.
You can use teh phone correctly for about 2 days then all of a sudden it will freeze completely and then you CANT do absolutely anything else, not even turn it off by holding power button ..
So i just left it there until it ran out of battery.
Then i charge while inside the fastboot and when i try to boot it is in a boot loop , doesnt even go into the boot animation
and to make things even more interesting i tried to wipe data guess what? The phone screen suddendly started blinking until again it ran out of battery. (you could see for a split of a second every time the screen blinks the progress bar of the wipe but it never moved from initial point).
So yea at this point is pretty obvious that something is wrong so i bought a Mi9T Pro meanwhile but i dont want this phone to go to waste.
Anyone out there has a clue of what could be? I wanna attempt to fix it myself if possible.
Aliexpress just gave a bit of the money back and the company Hongkong Goldway didnt give a f and they even go as far as to pretend they don't know what i'm saying ( the language barrier when it beneficial for them ).
This was gonna be a short explanation but i guess it was neccesary to be this long to explain correctly whats going on.
BTW: the only way yo make the phone work again for 2 days mayebe 3 is by using the MSM tool , any other method doesnt work.
also when it was working i filled the whole 256gb to kinda check the internal memory for corruption but it actually filled up without any problem so idk .
Click to expand...
Click to collapse
Ah yes, the common misconception that power shuts it off. Nope, not this phone. You have to hold power and volume up together to power off the phone when it crashes. Make sure you're using the latest platform tools (adb/fasboot) to unlock your phone. Make sure oem unlocking is enabled in developer settings after you've unlocked, having it disabled for some reason does screwy things. Mine was disabled once when I downgraded to Android 9 using the all in one tool available on xda, I thought I bricked the phone because it wouldn't boot after a reboot. Flash the latest oos twice through the system local upgrade feature, this will put the current oos on all partitions. Use the correct twrp, the unified versions found on xda 3.3.1-75 and 3.3.1-76 work well for me. The installer zip for those can be used in magisk to flash twrp after an OTA update before reboot. So, local upgrade 100% -> magisk modules "+" twrp 3.3.1-75 unified installer zip -> reboot to recovery -> flash magisk 20.3 at least (20.4 is available now). Do this twice so that everything is the same version on all the partitions. Lastly restore apps with swift backup without data, I know it's not ideal but may be necessary because some app's data may be corrupt and causing this. Good luck. Of course at any time you have it running you can reboot in safe mode (touch and hold restart until the dialogue pops up) and see how long you can use it without any third party apps to confirm that it is an app you installed.
Man I had the exact same problem as you and I got it fixed this morning after nights of fastboot commands trial and error found this thread forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Tried a few times before it worked but saved my phone all I had was fastboot mode and no recovery make sure to manually flash all fastboot commands you will then get stock recovery back wipe using all 3 options go 1st 2nd 3rd and then 1st wipe again after reboot phone might hang just force reboot and fixed
I really appreciate all the replies really but hmm im guessing there's a misunderstanding on what im saying.
I do know how to flash and recover one plus devices using MSM tool if neccesary, also to flash the fastboot rom .
The thing here is that everytime i recover the phone and all seems stable and working good , after a2 days more less it will random freeze of death and you cant even reboot holding power button NOTHING! is completely freezed.
So yea, thats pretty much it, i have tried already all that you said so far :c.
Dear All,
2 days back I was trying to unlock my LG-V20 phone using DirtySanta Method on this thread
https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296?nocache=1
For me it is not working & I want to return it to original LG ROM something goeas wrong & I was stuck on grey ribbon on screen (which I can't read anything) or I can boot it to fastboot command. I was trying to put phone on download mode to use it with LGUP but the program give me unknown device. When I check the forum they said I have to flash kernel. I was trying alot but nothing works with me. Suddenly LGUP define my device as US996 instead of H990DS. So I download the official ROM of US996 & flash it to my device it accept it & screen works normally but the device keeps restarting. It boots to welcome screen or even LG logo then restart. I can't even set it up. anyone can help on this problem??? How can I return it back to original H990DS ROM???:crying::crying::crying:
Another thing is that fastboot commands can't do anything like format & wipe it says device is locked
Hey, no worries. Your device can be saved. Dirty santa can be a bit** to get it to work. Took me like 2 days and several tries...
I'm quite sure I came across this ribbon screen. For me it looked like grey static from a tv without signal, quite scary.
So, the only not good thing you did was to flash the US996 ROM. You have a H990DS, it will not work... But it can be fixed, don't panic.
It's normal that the H990 is seen as US996 by LGUP after flashing the engineering bootloader. Every rooted H990 runs on this one, because there is no unlocked BL available other then this. So that means you came quite far with dirty santa...
I believe the reason that you phone can't start is, LGUP changed your partition layout from H990 to US996 (which will not work)
I'm going from memory here, so I'm not sure about the details. There is a thread in the forum explaining well how to recover a V20 with LGUP / (Uppercut could be important to fix unknown device / allow to cross flash). Follow this one and use the right H990DS Rom to reflash everything and repartition your device correctly. Maybe you have to play with the options like upgrade or repartition. BUT DON'T DO ANYTHING THAT IS NOT MENTIONED AS SAFE TO DO. You could even erase you BL. Then you have a nice brick...
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
You should be able to try with dirtysanta again, I promise it will work, and then you effort wasn't for nothing.
Here in the guide it even tells you that that phone will be detected as US996, the tipps here are good as well..
https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
Let me know how it went...
Best regards
Daniel
NoName! said:
Hey, no worries. Your device can be saved. Dirty santa can be a bit** to get it to work. Took me like 2 days and several tries...
I'm quite sure I came across this ribbon screen. For me it looked like grey static from a tv without signal, quite scary.
So, the only not good thing you did was to flash the US996 ROM. You have a H990DS, it will not work... But it can be fixed, don't panic.
It's normal that the H990 is seen as US996 by LGUP after flashing the engineering bootloader. Every rooted H990 runs on this one, because there is no unlocked BL available other then this. So that means you came quite far with dirty santa...
I believe the reason that you phone can't start is, LGUP changed your partition layout from H990 to US996 (which will not work)
I'm going from memory here, so I'm not sure about the details. There is a thread in the forum explaining well how to recover a V20 with LGUP / (Uppercut could be important to fix unknown device / allow to cross flash). Follow this one and use the right H990DS Rom to reflash everything and repartition your device correctly. Maybe you have to play with the options like upgrade or repartition. BUT DON'T DO ANYTHING THAT IS NOT MENTIONED AS SAFE TO DO. You could even erase you BL. Then you have a nice brick...
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
You should be able to try with dirtysanta again, I promise it will work, and then you effort wasn't for nothing.
Here in the guide it even tells you that that phone will be detected as US996, the tipps here are good as well..
https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
Let me know how it went...
Best regards
Daniel
Click to expand...
Click to collapse
Thanks a looooooooooot Daniel. Finally my LG is back to normal. I don't want DirtySanta anymore. My device was out for more than 20 days because of this.
Im very glad, that I could help you. It's a nice device and even better when working correctly.
Thanks for letting me know that it worked.
All the best to you too
Philadelphia said:
Thanks a looooooooooot Daniel. Finally my LG is back to normal. I don't want DirtySanta anymore. My device was out for more than 20 days because of this.
Click to expand...
Click to collapse
Its a bit of an op for real, but worth it when done
dornz said:
Its a bit of an op for real, but worth it when done
Click to expand...
Click to collapse
Does it pass SafetyNet with edXoposed installed?
iTzFeRReTTi said:
Does it pass SafetyNet with edXoposed installed?
Click to expand...
Click to collapse
Nope,
iTzFeRReTTi said:
Does it pass SafetyNet with edXoposed installed?
Click to expand...
Click to collapse
Worth the root
dornz said:
Nope,
Click to expand...
Click to collapse
Are you using the edXposed canary?
iTzFeRReTTi said:
Does it pass SafetyNet with edXoposed installed?
Click to expand...
Click to collapse
Glad you mentioned that about safety net, flashed me the Oreo rooted to check that, :silly:
Okay... I've been searching all over the net for this problem and I keep getting posts that skirt the issue. At least, that's what it seems. So I will begin and you can decide... and thanks for whatever info you can throw my way.
Brand new OnePlus 8T. I want to root it. Duh. So, Got the Tiny ADB and Fastboot package and all the rest, but the issue is with unlocking the bootloader. Other problems may appear later, but this is the issue now.
So, connect phone to PC (Windows 8.1) and the only way that ABD recognizes my phone is when the USB prefs are set to 'No Data Transfer". Yes, I have installed the proper drivers from the phone. So, when the 'No Data Transfer' is selected, ADB recognizes the phone and will issue the command, ABD Reboot Bootloader and the phone reboots to the bootloader. Nice! Unfortunately, it appears that once the phone has booted to the bootloader, it has changed the USB Prefs and now ADB and fastboot do not see the phone. Obviously this sucks. And here is the problem. As far as I know, I have ticked off on all the proper settings. USB Debugging, etc. No joy!
I found a post elsewhere that showed how to set the default USB mode and that didn't work either. My experience has been that ADB used to see the phone under the 'File Transfer' and PTP options before, but it doesn't now. I can't explain this.
So, pretty frustrated. This shouldn't be so bloody difficult. It's only a couple of commands and I have done this with other phones in the past so it's not like I have no previous experience. But I have already wasted way too much time here this go around. Anyone have an answer? I'll be your best friend!!
Thanks all..
R
Try nother USB C cable. Some not able to handle data.
rogerebert said:
Try nother USB C cable. Some not able to handle data.
Click to expand...
Click to collapse
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Ran Doid said:
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Click to expand...
Click to collapse
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
BillGoss said:
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
Click to expand...
Click to collapse
Hey Thanks, Bill. I"ll give this a whirl and see how it goes. I'll report back after. Cheers!
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Ran Doid said:
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Click to expand...
Click to collapse
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
BillGoss said:
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
Click to expand...
Click to collapse
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Ran Doid said:
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Click to expand...
Click to collapse
Sorry, I've no idea about that. Try flashing TWRP again.
BillGoss said:
Sorry, I've no idea about that. Try flashing TWRP again.
Click to expand...
Click to collapse
Okay, well.. I'll have to figure it out then. Thanks much, Bill. Appreciate your help. Happy Holidays!
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
BillGoss said:
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
Click to expand...
Click to collapse
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Mickade said:
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Click to expand...
Click to collapse
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
BillGoss said:
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
Click to expand...
Click to collapse
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Thx,
Mickade said:
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Click to expand...
Click to collapse
If they could fix the interminable start up time for TWRP that would be brilliant. But I believe the problem is with a file system check rather than the actual decryption which is quite fast.
Sorry, croquettes and mash aren't in my menu. But empanadas - absolutely!
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Ran Doid said:
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Click to expand...
Click to collapse
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
BillGoss said:
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
Click to expand...
Click to collapse
There-in why I asked if you might point me at something reliable. But I guess not...
Thanks anyway..
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
Actually a trick you can use is in twrp if you have the magisk APK change the ext to zip and install in twrp it patches the boot img for you in right slot so you don't have to pull img from phone
Title says it all. I never trusted Lenovo with updates. They always manage to **** something up! Anyway to get it back? Will downgrading to Android 10 fix it?
George Malas said:
Title says it all. I never trusted Lenovo with updates. They always manage to **** something up! Anyway to get it back? Will downgrading to Android 10 fix it?
Click to expand...
Click to collapse
I mean mine is fine so not sure why yours dropped honestly, fully rooted with magisk the uses zygisk and using kdragons safety net fix
Try jsut reflashing the stock firmware, thats the best I can say to a possible fix, you can't downgrade due to downgrade protections that I believe are found within the gpt file unless thats changed
ninjakira said:
Try jsut reflashing the stock firmware, thats the best I can say to a possible fix, you can't downgrade due to downgrade protections that I believe are found within the gpt file unless thats changed
Click to expand...
Click to collapse
Mine shows this in DRM info.
Can I reflash stock without factory reset?
George Malas said:
View attachment 5665339
Mine shows this in DRM info.
Can I reflash stock without factory reset?
Click to expand...
Click to collapse
George Malas said:
View attachment 5665339
Mine shows this in DRM info.
Can I reflash stock without factory reset?
Click to expand...
Click to collapse
Unfortunately no, what you could do before doing the reflash is just doing a backup, you can use the backup option the phone/Google provides in settings if you want, personally that's what I do but I don't use twrp either so I'm not sure if you have twrp and if twrp affects that. I will say though I also have the Motorola edge 2021 and when I unlocked the bootloader while it was still on Android 11 my widevine got dropped down to L3 but then I did the ota to Android 12 since I didn't use magisk at that time yet and I'm not sure what I did or anything like that but my widevine went back to L1 and it's stayed that way since and I got 2021 in may, could be a similar thing happening with you just with the 2020 model. I can also say since I still own the Moto edge 2020 and got it on day of release I never had an issue with my widevine being dropped to L3 as shown in my screenshot it's on L1 using dev check, and I did just download DRM info to double-check that on the Moto edge 2020 and it is still showing L1 so I can't say if doing a reflash of the Android 11 firmware will work but it might. I've had to reflash The 2020 edge hella including using a blank flash to get it out of hard brick and it still hasn't dropped to L3 once
ninjakira said:
when I unlocked the bootloader while it was still on Android 11 my wide Vine got dropped down to L3
Click to expand...
Click to collapse
Thing is I've never unlocked the bootloader on this phone nor rooted it. Only thing I did is have it perform multiple OTAs one after the other when I decided to upgrade to Android 11. Maybe something got corrupted during that?
Anyway, thanks for the help. I may just leave it as is since I'm worried I'll screw up reflashing it lol.
George Malas said:
Thing is I've never unlocked the bootloader on this phone nor rooted it. Only thing I did is have it perform multiple OTAs one after the other when I decided to upgrade to Android 11. Maybe something got corrupted during that?
Anyway, thanks for the help. I may just leave it as is since I'm worried I'll screw up reflashing it lol.
Click to expand...
Click to collapse
Oh if your bootloader is locked and everything and you just been doing the OTAs that's 100% just some random BS lmao that's actually a situation if you know the phone still in warranty you can probably call Motorola about that and get a replacement fr lol, and I'll be the one to say/ask it since other people will probably see this and be like yo what the hek, how is it you're a senior member but you're worried you'll screw up reflashing it lol jsut use the moto flash utility provided here (not being a butt I swear, text makes me sound bad lmao) really unless you're trying to watch Hulu and Netflix exclusively on your phone widevine honestly is not that important to deal with either I don't think Spotify is affected by it so your music quality "should" be the same still at least but again idk for sure since I haven't had widevine issues with mine, jsut the 2021 model, but that fixed itself otaing to 12 lol