Due to an error of magisk, I lost some of my partitions of my Pro 5. So now it's hard-bricked.
But luckily, the bootloader remains unlocked, so that means I still have chance to fix it.
I found a way to backup the default partitions from this url:
https://forum.xda-developers.com/meizu-pro-5/development/meizu-pro-5-backup-tool-st0rm77-t3460138
My Pro 5 is 64GB version.
Could anyone please backup the default partitions and share with me to save my phone? Thanks!
Same problem here. Please help us.
aegoyu said:
Due to an error of magisk, I lost some of my partitions of my Pro 5. So now it's hard-bricked.
But luckily, the bootloader remains unlocked, so that means I still have chance to fix it.
I found a way to backup the default partitions from this url:
https://forum.xda-developers.com/meizu-pro-5/development/meizu-pro-5-backup-tool-st0rm77-t3460138
My Pro 5 is 64GB version.
Could anyone please backup the default partitions and share with me to save my phone? Thanks!
Click to expand...
Click to collapse
Hello,
have a look at that : https://forum.xda-developers.com/me...-12-0-unofficial-t3478872/page56#post73263021
(the latest comments)
untick AUTH
Hi All,
My first post on XDA even though I've been around for long now. Faust, thanks for your excellent work.
Regarding the Token Sign Failed error message. It seems you just need to untick "Auth" in the top right corner in the multiupgrade tool.
It worked for me and I could complete the process as described in the PDF file.
After the process, the phone rebooted... I could see the Battery icon and Meizu logo!!! Then I landed on the "Upgrade Firmware" screen from meizu. Weird, I thought I just did it.
I took the update.zip file from the demo and flashed it. It passed the checking Firmware and installation process. The phone reboots... and bootloops on the meizu logo.
Fastboot is still on but BL is now locked. I am stucked. If anyone has another tip to share
GL
Hello, somebody could help me in a backup of the persist or efs folder for moto g5 xt1671?, this problem ocurred me when i flashed the original firmware and i forgot make a backup of that partition, please.
thank you very much for your attention.
Your device is a G5 (cedric), not a G5 Plus, right? If so, you're in the G5 Plus forums.
However, you do NOT want to flash any other device's persist, you will permanently cause damage to your phone. Instead, back up your persist and efs now, and then look at this thread:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
The links in that thread are specific to potter, but the same principles apply.
I restored someone's else persist when i didn't know how bad it was... Im at imei 0 and only calls. is there any way to get 3g bacck?
Sorry man, but the best case is that you have an old backup of efs when it was working if you don't have your own persist.
Sorry for a noob question.
I rooted my previous device, Xperia Z3 compact, without unlocking bootloader, so I am completely new to this stuff.
I am looking into buying a used X Compact and worried that the device no longer has its TA intact.
I've searched the forum but didn't quite find an answer to my question.
So, for X compact and many other xperia models, there is DRM fix that restore DRM keys on a bootloader-unlocked device, even if you didn't backup your TA and your TA is completely wiped by unlocking, correct?
Then, how can you tell the difference between a device that has its original TA (either still intact or TA properly restored from backup) and a device without TA but DRM keys restored?
And, if you can't tell the difference, what is the point of having TA backup and restoring it later?
Sorry it seems pretty basic stuff but I can't find any direct answer to it.
Hope someone can help. Thanks in advance!
tapa_t said:
So, for X compact and many other xperia models, there is DRM fix that restore DRM keys on a bootloader-unlocked device, even if you didn't backup your TA and your TA is completely wiped by unlocking, correct?
Click to expand...
Click to collapse
Not exactly - the drm fix is a mod that attempts to replicate the features and functions that are lost when wiping ta. I've never used it, so can't say myself, but it seems like people who have are happy with it. The main issue with wiping ta is the loss of Sony camera features and quality. I believe there are also other things attached to the ta, but most people probably wouldn't ever miss them.
If you wipe the ta without backing it up, then it is gone, and your only option is drm fix. Most people would probably rather have the ta intact...
levone1 said:
Not exactly - the drm fix is a mod that attempts to replicate the features and functions that are lost when wiping ta. I've never used it, so can't say myself, but it seems like people who have are happy with it. The main issue with wiping ta is the loss of Sony camera features and quality. I believe there are also other things attached to the ta, but most people probably wouldn't ever miss them.
If you wipe the ta without backing it up, then it is gone, and your only option is drm fix. Most people would probably rather have the ta intact...
Click to expand...
Click to collapse
Thanks -- but that doesn't really answer my question. Question is *HOW* do you tell apart a phone with drm fix and no TA from a phone with an intact TA. If you can't tell the difference, people can't be sure they've got the TA intact whether they prefer it or not.
tapa_t said:
Thanks -- but that doesn't really answer my question. Question is *HOW* do you tell apart a phone with drm fix and no TA from a phone with an intact TA. If you can't tell the difference, people can't be sure they've got the TA intact whether they prefer it or not.
Click to expand...
Click to collapse
Service menu > service tests > security
See in screen shot :
- Widevine... "OK"
- ckb... "OK"
- Fido keys provisioned
with drm fix
zokkii said:
with drm fix
Click to expand...
Click to collapse
Interesting - and thats with drm keys missing (TA wiped)?
yes,without drm keys
That's only half of the story. The DRM Fix library has two working modes, and what defines which mode it'll pick depends if you have your unique device key (that get wiped when you unlock the bootloader) flashed in an alternate TA Unit. You can extract your device key and then flash it on an alternate unit as long as you have a TA backup taken before unlocking the bootloader (the RootKernel utility from @tobias.waldvogel ships with the required tools to extract and flash your device key).
On the "normal" mode (DRM Fix + device key flashed on alternate TA unit) you have exactly the same functionality you would get on a bootloader locked device with its TA intact, everything works. But, in case you don't have your device key flashed into an alternate TA unit (e.g. unlocked the bootloader without backing up the TA first, lost backup, etc), then DRM Fix will work in emulation mode. On emulation mode, most features that check for DRM will still work (e.g. camera algorithms, X-Reality Engine, etc) but some specific DRM features that requires the device key (e.g. Widevine L1 decryption, HDCP on Screen Mirroring, etc.) won't work. As it was increasingly more difficult to find exploits for newer devices and firmwares, that's the mode most DRM Fix users utilize, I guess.
Now, how to tell a DRM Fix restored device apart a device with intact TA is a little tricky, but you basically have 3 situations:
• Bootloader locked device, security test in Service Menu shows both Widevine and CKB as [OK] [Active] => stock device with TA partition intact
• Security test in Service Menu shows [unknown] or [generic error] on Widevine or CKB (or both) => TA partition wiped, DRM Fix not applied
• Bootloader unlocked device, security test in Service Menu shows both Widevine and CKB as [OK] [Active] => TA partition wiped, DRM Fix applied
When a device has the DRM Fix applied, it's not possible to tell if it's working in normal or emulation mode until you try something that requires the device keys (e.g. Widevine L1 or HDCP on Screen Mirroring). If it works, DRM Fix is in normal mode, otherwise it's in emulation mode. Also, you can't trust the "Bootloader Status" info on the Security Test of the Service menu to tell whether the bootloader was unlocked or not, as it'll always report "locked" if you have the DRM Fix applied. A safe way to tell the bootloader status is (re)booting the device and observing if the "Your device has been unlocked and can't be trusted" message appears before the Sony logo. If that message appears, the bootloader was unlocked.
You'll also find many people debating whether FIDO Keys being provisioned or not actually indicates the status of the DRM Fix, but from my experience, they aren't related. Fact is that I had FIDO Keys not provisioned on my Xperia X right after I turned it on for the first time (brand new device, had just taken it from the box), but upon registering a fingerprint, FIDO Keys became Provisioned again. Same thing occurred after I backed up my TA with the dirtycow exploit then unlocked the bootloader, FIDO Keys became not provisioned but after enrolling a fingerprint they became Provisioned again, even through I hadn't installed DRM Fix yet at that point.
And to finish, keep in mind all I said on this post is only valid for Xperia devices that launched before Xperia XZ Premium. With XZ Premium launch, Sony reworked many parts of the DRM protection and the original DRM Fix from previous devices didn't work at all. Another user eventually developed a new DRM Fix solution for those newer devices, but it works completely different and I have absolutely zero experience with it.
Does this work on the Android 9.0 custom roms? DRM Camera fix for 9.0?
sheeplings said:
Does this work on the Android 9.0 custom roms? DRM Camera fix for 9.0?
Click to expand...
Click to collapse
No
mbc07 said:
That's only half of the story. ...
Click to expand...
Click to collapse
Thanks A LOT for this information!
I have searched for a long time for something similar but everyone seems to just know this and expecting everyone else too, so it's never thoroughly described, until now!
mbc07 said:
On the "normal" mode (DRM Fix + device key flashed on alternate TA unit)
Click to expand...
Click to collapse
Do you have any information that would help a noob accomplish this? Link to a good, noob adopted, step-by-step guide? So far I'm out of luck finding anything that will give me confidence enough to try it.
Thanks again!
Holton181 said:
Do you have any information that would help a noob accomplish this? Link to a good, noob adopted, step-by-step guide? So far I'm out of luck finding anything that will give me confidence enough to try it.
Click to expand...
Click to collapse
Sorry, nope. The process is "half" streamlined if your phone happens to be supported by the original Root Kernel tool or the modded version posted on the last pages of that thread, but you would still need knowledge on how to get a TA backup on your particular device and on unlocking the bootloader / flashing a modded kernel. If your phone isn't supported then the process also involves manually modding the kernel to include the DRM Fix library too, and none of that is noob-friendly, at all...
If you can't/don't want to deal with it, your best bet is searching at your device's subforum, perhaps somebody already did the work for your particular phone model and published a ready to flash, DRM Fixed kernel there...
mbc07 said:
Sorry, nope.
Click to expand...
Click to collapse
Okay, thanks anyways. My understanding of this is much better already after your description.
Backing up TA, unlocking bootloader and rooting is the easy part, pretty good understanding how its done. It's how to make good use of the DRM:s that's all new to me.
My device is the full size X (not Compact as in this sub-forum), my wife's old working phone. I'll try to search the forum for it.
Hi XDA's
It is humble request kindly if some one have twrp nv backup of lnd-l29 which is converted from lnd-al30b.
Phone was completely soft brick i recover it from dead condition according to the pcb which is LND-AL30B TO LND-L29 successfully
but i am facing No service issue in that phone. I almost try every thing like update, re flash, stock, root, repair imei data, nothing works for me.
Sim service is also not working on stock rom LND-AL30B
XDA is my last hope because i tried to search on net every thing according to my knowledge but could not find any thing which could solve my problem
that's why i am requested here if some body have nv partition backup please share with me.
OR let me know any thing that could solve my problem
Present situation of phone
* Phone is on LDN-L29 8.0.0.155 (C432)
* TWRP INSTALLED
* ROOTED WITH MAGISK
THAKS IN ADVANCE
PHONE WAS WORKING FINE BEFORE SOFT BRICKED..