well as we all know, backing up DRM keys is possible with MM but our device doesnt have a MM FW.
is it possible to simply port a MM FW from older sony devices and make it compatible with the XZP? then we can simpley backup DRM and get on with unlocking
is that possible or is it impossible?
It is impossible resulting in a bricked device. The problem is qualcomm Sd835 drivers/libs
Only with a dumb luck so that the libs for qualcomm 820 devices recognizes 835 as generic processor and allow it to boot. But is near 0 percent possible
But who knows if the bootloaders allows that firmware to boot.
The real problem here is android as not being able to boot on same soc's firmwares like Windows does, then when loaded to search for drivers. If you move one hard drive with win7 for example installed on Intel, you have many chances to boot that win on amd processor. That is not true for Android. I am waiting the day when win10 arm will boot Any android device.
But as I have said in a previous post, that will still ruin our warranty. To unlock bootloader you need permision from sony. And then sony will know the phone imei.
Why even bother when is a sollution for drm fix?
Aaa, you should have asked if having drm keys will open Doors for gcam hdr!+ and other software. No, that will not happen. The real problem for sony devices is their encrypted stuff.
Related
Hello,
received the Phone with the t-mobile branding (german version).
What i did is to use the official device unlock from Sony so be able to flash another Firmware.
Then i downloaded the generic DE from the FlashTool, and flashed it.
This failed because the rom was already on Android 7.
I did not manage to aquire the -9090 Rom in Android 6.0.1
So i flashed the central europe version.
First problem: this version does not (yet?) update to Android 7 - and actualy is NOT the version i wanted to have in the end.
Second problem: The camera app did not work anymore (already in use)
So i've read through this forum, and got the information, i need to re-unlock the device.
Did that, camera works.
However now i always get "this device is not trusted"
What i actualy want to have:
- A stock ROM in german, whcih gets OTA updates.
- Working Stock-Apps
- No warning when starting the Phone.
I do not care wether the warning is disabled, or simply not shown because of another bootloader. There should simply be no annoying warning.
I also have the exact same phone twice (mine, and the one for my girlfriend) in case this help somehow. In theory the best situation would be to hard-sync every single byte on the disk (i assume?)
I did not read anything about "do not flash currently, as this will make you loose your drm keys forever and the stock camera will no more work at all". But after watching this forum for some days now, it seems that exactly that has happened? So using a locked bootloader will not work anymore due to lost and unrecoverable drm keys? I cannot copy them from the other phone? So i need to replace the bootloader with another one to get rid of the message? And i also need to reflash the firmware as soon as FlashTool supports Android 7?
In the end a total piece of crap, because of a goddamn branding -.-
What would you guys recommend to do now? Just want to make it work without an error or unsecure warning displayed at every boot.
You did not need to unlock to flash another firmware.
Now you have unlocked you can't use the camera without keeping it unlocked and if it is unlocked you will get the warning message.
Just flash a 6.0 ftf from a region with the update then you will get the ota update
Ps, there are plenty of warnings on the Sony site about drm keys that you must have visited to get your unlock code...
And you cannot copy drm keys from another device
I've been all over trying to find a root that'll help delete these preinstalled apps with viruses on this darn Android phone. They all say root failed Not Supported. I don't need to root for major installs, I need it to delete these apps, that's all. The phone's an unbranded model: A9 (2018), CPU: MTK6592 Octa core, Android 8.1, Kernal version 3.10.72, RAM 4G & ROM 64G. Also if I can't personally root this phone do you think I can take it to a pro and have them to do it. Someone, please help.
Well, you'll have to get the correct files (scatter file, TWRP installer, etc.), but try this procedure:
https://forum.xda-developers.com/ge...ng-unlocking-bootloader-t3812910/post79358295
Don't use the files for the Blu Life One X3, each phone has its own files, and using the wrong ones will brick your phone.
But I've found that (for the Blu Life One X3, with a Mediatek MT6753 chipset) just as the phone shuts down, it drops all security, allowing one to push TWRP to the phone as bootloader. That's your 'in' to getting the thing rooted, even if your bootloader can't be unlocked.
Lusty Rugnuts said:
But I've found that (for the Blu Life One X3, with a Mediatek MT6753 chipset) just as the phone shuts down, it drops all security, allowing one to push TWRP to the phone as bootloader. That's your 'in' to getting the thing rooted, even if your bootloader can't be unlocked.
Click to expand...
Click to collapse
Wow. That is probably the dumbest root method i've ever seen. xD
ParzivalWolfram said:
Wow. That is probably the dumbest root method i've ever seen. xD
Click to expand...
Click to collapse
How, exactly, is it dumb? It works. My phone is rooted, and the bootloader cannot be unlocked.
Lusty Rugnuts said:
How, exactly, is it dumb? It works. My phone is rooted, and the bootloader cannot be unlocked.
Click to expand...
Click to collapse
Dumb as in "wow, i can't believe the manufactuers left in this glaring hole", not dumb as in "wow this is dumb you suck nerd." My bad.
Ah, I see.
It's a good thing that MTK's chipset has this vulnerability... and I don't think MTK can quash it without a major revamp of their chipset architecture, which they likely wouldn't undertake just to stop a few folks rooting their devices.
What surprises me is that the entire Android industry hasn't embraced rooting. There are ways nowadays to ensure the phone isn't stolen (fingerprints, PINs, etc), so why they continue to fight it is beyond me... there's more innovation on the rooting and FOSS side than on the 'lock it down' side. Innovation and openness is what drives users to use the phones in the first place. If we wanted a 'walled garden' user experience, we'd go with Apple... with the understanding that Apple knows everything about us, and with the hope that Apple doesn't go Google-evil.
I'll go with a known-evil company that I can lock out rather than a company that may someday go evil (or may be evil, but no one knows they are), but which cannot be locked out even the slightest bit.
I recently came to know that Qualcomm found some vulnerabilities in many chipsets that allow remote access to phone data and encryption keys including 835 n all. It also has 625 in the list . Qualcomm is rolling update to fix that . Lenovo will never provide the update and we are on custom ROMs , anyway to patch that update to our devices ?
https://app.beebom.com/qualcomm-patches-critical-flaw-dozens-snapdragon-socs
tanzeel.ahmed1306 said:
I recently came to know that Qualcomm found some vulnerabilities in many chipsets that allow remote access to phone data and encryption keys including 835 n all. It also has 625 in the list . Qualcomm is rolling update to fix that . Lenovo will never provide the update and we are on custom ROMs , anyway to patch that update to our devices ?
https://app.beebom.com/qualcomm-patches-critical-flaw-dozens-snapdragon-socs
Click to expand...
Click to collapse
probably not.
Hey,
I don't know if I'm publishing in the most correct subforum, since I'm new here on the forum, but I need some help from you.
About a year ago I bought the Samsung S10e and although my experience was good, I miss the stock android I had on my Nexus 5x (previous smartphone). On that phone, I flashed the Pixel Experience ROM to install android 10 verious times (since google only supported it until android 9) so I can say that I have some experience in the matter. The problem came with Knox, and all the impositions that samsung added to make life difficult for nerds who want to control their smartphones.
I am thinking of installing LineageOS 18.1 (unofficial) published here (I don't have much need for VoLTE and VoWiFi, I think).
My question is this: Despite following all the instructions that the ROM publisher wrote, there is still a possibility of something going wrong, a soft brick can occur or even worse a hard brick right? In soft brick, do I still have the possibility to recover it? What about hard brick? My phone's still under warranty until December this year. If I flash a custom ROM, will completely I lose it 100%?
I just want to know what I'm getting into. I don't want to keep a 500€ brick at home.
Thanks.
Look into Warranty Card that came with phone to find out what is covered in your warranty / when you loose it.
Personally think tampering a phone always voids warranty. And Samsung detects this!
jwoegerbauer said:
Look into Warranty Card that came with phone to find out what is covered in your warranty.
Personally think tampering a phone always voids warranty. And Samsung detects this!
Click to expand...
Click to collapse
You're right! I've looked into it and voids warranty unfortunately.. but thats to be expected, I just thought that you could revert back like you can do on some devices when you root, but seems like when knox is tripped, a fuse blows or something, making it impossible to revert back without them noticing the device was tampered.
I've flashed successfully an Android 11 based rom (lineage os 18.1) but then I wanted to try out pixel experience, which was on 10 and now I'm getting a Rev check fail Device 9 binary 8 message. Could anyone help me?
AFAIK an error like this indicates that the phone cannot use the ROM provided ( via Samsung's ODIN loader ) because the ROM is either not legitimate or is a version prior to the one currently installed.
jwoegerbauer said:
AFAIK an error like this indicates that the phone cannot use the ROM provided ( via Samsung's ODIN loader ) because the ROM is either not legitimate or is a version prior to the one currently installed.
Click to expand...
Click to collapse
Exactly what I understood from the error message. Do I have any options right now?
I can flash the recovery, but it doesn't let me access it.
Downloaded Samsung's Stock Android 11 One UI 3 firmware and flashed with odin while in download mode. Device is now booting correctly.
I don't know if it's permitted or not but I'm in search of the system firmware so if anyone could help I'd be grateful. I know it's unreleased but let's just say I've got the prototype lying around. Thanks in advance.
Doesn't exist. Ideally, you would dump the firmware yourself from the phone.
Now that the phone is released, stock images should be available soon here:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
kobiandy said:
I don't know if it's permitted or not but I'm in search of the system firmware so if anyone could help I'd be grateful. I know it's unreleased but let's just say I've got the prototype lying around. Thanks in advance.
Click to expand...
Click to collapse
Since Google bricked your phone remotely with the hardware ID (since you got one of the dev models before release), it will be quite difficult to get it running again, a simple firmware flash will probably not do the trick.
And even if you'd manage to get a firmware running, you will not be able to go online, since Googles system has flagged your hardware ID and just brick it again. The only hope you have really is to wait for a custom kernel/OS and use that, IF you can actually manage to flash any sort of data on that phone. Was the bootloader still locked when Google bricked your device?
Morgrain said:
Since Google bricked your phone remotely with the hardware ID (since you got one of the dev models before release), it will be quite difficult to get it running again, a simple firmware flash will probably not do the trick.
And even if you'd manage to get a firmware running, you will not be able to go online, since Googles system has flagged your hardware ID and just brick it again. The only hope you have really is to wait for a custom kernel/OS and use that, IF you can actually manage to flash any sort of data on that phone. Was the bootloader still locked when Google bricked your device?
Click to expand...
Click to collapse
No it was never locked to begin with. Does this mean even original stock firmware( when released) won't work?
kobiandy said:
Does this mean even original stock firmware( when released) won't work?
Click to expand...
Click to collapse
That is highly likely, but don't let me stop you from trying. Maybe you will have success. Also keep your eyes out for the Android Flash tool or the Pixel Repair tool, once Google updates them for the P7 Pro. Big companies usually not have all the tools interconnected, so chances are that the Repair tool won't check for blacklisted hardware IDs, it's just important that under no circumstances you may connect to the Internet with that thing, IF you manage to get it running and as long as it runs stock.