Related
Rooting, Backing Up TA and unlocking bootloader on a Mac can be a pain in the backside especially if you're a nube. Since there isn't an obvious guide out there for us (the most hated computer users by developers) Mac users i decided to create one.
Before we start make sure you're running the latest Mac OS X Mavericks (which is free thanks to apple generosity ) this is to make things easier for me when it comes to helping you.
PLZZZZ PLZZZZZ Read Instruction first (making sure you have a general under standing of them) THEN FIND A POSSIBLE ESCAPE PLAN (just incase things go south) and obtain the correct files before proceeding to follow them!!!!
WARNING!!!!From this point onwards I AM NOT RESPONSIBLE for any damages to your phone, whether they are as small as a 1/1000 mm scratch or as big as a worldwide Nuclear Holocast caused by Aliens! You decided to follow these instruction so it's YOUR FAULT!
Here's the order of what we'll be covering first to last:
1) Backing Up TA
2) Unlocking Bootloader
3) Installing a custom kernel
4) Rooting
BACKING UP TA
You may have heard rumours saying that "YOU CANNOT BACKUP TA ON MAC OS X, ONE MUST HAVE WINDOWS!".
Well I'm here to tell you that's TRUE, sadly. But FEAR NOT! Because the GODS have given us a work around (which is probably longer), and here it is:
First Downgrade to .534 using latest flashtool for Mac OS X
DOWNLOAD HERE http://www.flashtool.net/download.php (make sure you dave the app in applications folder)
Downgrade instruction here: http://forum.xda-developers.com/showpost.php?p=45464122&postcount=3
You can find firmware folder by right clicking ( if thats enables, surf the interwebs on how to do it if you don't know) then "show package contents" => Contents ==> MacOS ===> firmwares. This is ware you'll place your .ftf fiiles.
Before you ask, yes I know downgrading to .534 from .290 might kills sim detection but flashing .290 again (which we'll do at the end) using flashtool will fix that.
Then download,buy or any other means that are LEGAL "wink wink" (I bought BTW cause I love these guys!), Parallels Desktop 9 or later. Or use Bootcamp if you know what that is and are willing reboot you Mac lots of times just to change something on your phone. To me personally it completely defeat the purpose of having a Mac in the first place although its a nice option.
You can get Parallels Desktop 9 or later legal and get a 14 day trial of it here at their official website here: http://www.parallels.com/downloads/desktop/
Then get yourself a copy of Windows OS (windows 8 recommend cause it comes with inbuilt anti-virus) or try this 90 day free trail of Windows 8/8.1 from Microsoft:
Here is link http://www.microsoft.com/en-gb/business/products/downloads-and-free-trials#/
Then use common sense to install Windows on mac using Parallels or if your new and confused follow instructions from this video http://www.youtube.com/watch?v=UsChUvlTePE
Once windows is installed use this seksy guide to Root: http://forum.xda-developers.com/showthread.php?t=2439328
And this other seksy guide to Back TA: http://forum.xda-developers.com/showthread.php?t=2292598&highlight=ta
NOTE: Connect your device while Parallels Desktop (PD) is running windows and a window will pop up notifying you whether you want to connect device to mac or windows. Make sure you select Windows.
Make sure you save the TA file some where safe like google drive, skydrive, drop box, box or all 4 of them
then use flashtool to flash .290 back (root might disappear depending on what you do.)
You can practically use Windows from PD with other guides on xda z1 forum to do the rest of the step. But step 3 is going to be a Nightmare especially on window because you're dealing with drivers and command prompt. If you're not in good terms with these youre going to suffer with these, trust me I know .
Unlocking Bootloader "THE EASY PART!"
Turn off Parallels Desktop open browser and head to: http://xperiafirmware.com/8-firmware/42-sony-xperia-z1-c6903
Scroll down to how to unlock bootloader and follow the instruction using Mac OS X.
then check if bootloader is unlocked by dialling *#*#7378423#*#* and go to service info / configuration
If the last line says
bootloader unlocked: Yes
Then its unlocked
If it says
bootloader unlocked allowed: Yes
then it is locked but you can unlock it
If it says
bootloader unlock allowed: No
then you cannot unlock it
Installing a Custom Kernal"THE HARD PART!"
For this you need to First set up ADB and Fastboot on MAC. I will post a link to a very very easy to follow guide on how to do that. This guide is pretty easy to follow but I do advise that you follow it carefully down the way words are spelt other wise you're going to run into problems.
Here is the guide: http://forum.xda-developers.com/showthread.php?t=1917237
Take note on of this step "press CTRL+X to exit, then Y to confirm the save then press ENTER" because people forget to press ENTER and the start complaining.
Now download and unzip DoomKernel from: http://forum.xda-developers.com/showthread.php?t=2448613
Save it some where convenient like the "android" folder you created.
Then open terminal and type the Command while your device in in fastboot mode (turn off phone and connect usb while holding volume up Button, a blue light should be shown on Z1):
"adb fastboot flash boot directory of where you placed the kernel/Z1-DooMKernel-v04.img"
here's an example of my code:
"adb fastboot flash boot /Users/RealibleCandy4/Desktop/android/Z1-DooMKernel-v04.img"
Now you have custom kernel on phone after reboot.
Rooting
Download SuperSU (do not unzip) and place on sdcard from: http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
Flash SuperSU.zip on one of the recoveries which you can access by either holding Volume down/up key after you see the DooMkernel splash screen and phone vibrates.
Well done You are now rooted!
Before you ask, yes I know downgrading to .534 from .290 might kills sim detection but flashing .290 again (which we'll do at the end) using flashtool will fix that.
Click to expand...
Click to collapse
Even on windows if you downgrade from .290 to .534 than flash .290 again, it will fix the sim detection? Also what .290 are you flashing with the mac/windows? Link to the file please?
then use flashtool to flash .290 back (root might disappear depending on what you do.)
Click to expand...
Click to collapse
Again I can't see a link to the file for .290, and root might disappear? What does a user have to do to make sure the root doesn't disappear, obviously they want to avoid this.
Sorry just clarifying questions for other people, and myself. Good work on the guide.
RealiableCandy4 said:
Then use common sense to install Windows on mac using Parallels or if your new and confused follow instructions from this video http://www.youtube.com/watch?v=UsChUvlTePE
Once windows is installed use this seksy guide to Root: http://forum.xda-developers.com/showthread.php?t=2439328
And this other seksy guide to Back TA: http://forum.xda-developers.com/showthread.php?t=2292598&highlight=ta
NOTE: Connect your device while Parallels Desktop (PD) is running windows and a window will pop up notifying you whether you want to connect device to mac or windows. Make sure you select Windows.
Click to expand...
Click to collapse
Or... you know... you could just do it from OS X. Check out my guide, much simpler.
http://forum.xda-developers.com/showthread.php?t=2449244
Seriously?! Backing up TA on Mac or Linux is just a few commands in terminal. Very simple.
Sent from my C6903 using Tapatalk
I know you can use terminal but the problem with that is its pretty easy to make spell miss takes on terminal and it can be frustrating + doing it that way is very dangerous since the TA is a sensitive area also there's no way to check if it worked properly by mock restoring TA. I choose this way cause it's much safer.
Sent from my C6903 using xda app-developers app
RealiableCandy4 said:
I know you can use terminal but the problem with that is its pretty easy to make spell miss takes on terminal and it can be frustrating + doing it that way is very dangerous since the TA is a sensitive area also there's no way to check if it worked properly by mock restoring TA. I choose this way cause it's much safer.
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Depends on how you define "safe", I much prefer doing it myself, then I know it is done properly. And what do you mean by mock restoring? You can easily verify authenticity by MD5:ing the TA partition, and subsequently the image taken of it.
Good advice didn't know that. Like you said it depends on you. I personally prefer this method because I can root and back up TA and check if it's correctly backed up with a push of a couple of buttona and I don't have to deal with the fear of accidentally miss typing commands. I'll (with your permission) put a link to your method in the tutorial sometime tomorrow. I'll have to test it first.
Sent from my C6903 using xda app-developers app
TagEHeuer said:
Even on windows if you downgrade from .290 to .534 than flash .290 again, it will fix the sim detection? Also what .290 are you flashing with the mac/windows? Link to the file please?
Again I can't see a link to the file for .290, and root might disappear? What does a user have to do to make sure the root doesn't disappear, obviously they want to avoid this.
Sorry just clarifying questions for other people, and myself. Good work on the guide.
Click to expand...
Click to collapse
Yes flash .290 will fix it make sure you use the latest Flashtool NOT 0.9.11.0.
for firmware I'm using the 14.2.A.0.290 Generic NCB (Unbranded/Nordic) found at http://forum.xda-developers.com/showthread.php?t=2572195
you can find the .290 files on xda z1 general forum
As for root it will disappear when using Flashtool but on you can get it back once you unlock bootloader, flash custom kernel and flash superSU.zip file. Im not sure if you can root 4.3 with a locked bootloader i havent found anything all ask in Q&A section. This guide is for root with unlocked bootloader.
Are you kidding me ? I like your guide... Like all oft the others which are the same.... The only difference; you are using parallels.
My suggestion for your guide: "Get Parallels on your mac, install windows and follow the known 100 tutorials".
Sorry for flamewars... But its really boring to read the same tutorials with different spellings like about 100 times.
Kind regards
Meet
Gesendet von meinem Nexus 7 mit Tapatalk 4
Edit;
@TagEHeuer
Dont Quote entire OP.............
Not everyone will read the billion guides you've read. The more the helpful. He's not doing any harm to anyone. Yes, quoting OP was a mistake, thank you for pointing it out.
meetdaleet said:
Are you kidding me ? I like your guide... Like all oft the others which are the same.... The only difference; you are using parallels.
My suggestion for your guide: "Get Parallels on your mac, install windows and follow the known 100 tutorials".
Sorry for flamewars... But its really boring to read the same tutorials with different spellings like about 100 times.
Kind regards
Meet
Gesendet von meinem Nexus 7 mit Tapatalk 4
Edit;
@TagEHeuer
Dont Quote entire OP.............
Click to expand...
Click to collapse
RealiableCandy4 said:
Good advice didn't know that. Like you said it depends on you. I personally prefer this method because I can root and back up TA and check if it's correctly backed up with a push of a couple of buttona and I don't have to deal with the fear of accidentally miss typing commands. I'll (with your permission) put a link to your method in the tutorial sometime tomorrow. I'll have to test it first.
Sent from my C6903 using xda app-developers app
Click to expand...
Click to collapse
Be my guest, I made it specifically because I wanted people to learn more about their devices and as a result hopefully help increase the average knowledge level on these boards! Let me know if you need any help following it.
meetdaleet said:
Are you kidding me ? I like your guide... Like all oft the others which are the same.... The only difference; you are using parallels.
My suggestion for your guide: "Get Parallels on your mac, install windows and follow the known 100 tutorials".
Sorry for flamewars... But its really boring to read the same tutorials with different spellings like about 100 times.
Kind regards
Meet
Gesendet von meinem Nexus 7 mit Tapatalk 4
Edit;
@TagEHeuer
Dont Quote entire OP.............
Click to expand...
Click to collapse
I understand what you mean I did mention that in the post. But i also mentioned that the problem with that method is adb and drivers (mainly drivers) I tried doing that myself and I found that dealing with drivers is a pain, but luckly for use mac users we don't have to deal with that which is a good thing. It makes the installation of custom kernels via fastboot easy and you dont have to wake up the next morning wondering why drivers don't work anymore (which i went though) and causing you to look through 100s of forums for a solution. Somestimes the long why is the best way.
I have modified zxz0O0's script for rooting to just kill the SONY RIC, not upload towelroot and stuff.
This is so you can mount /system, modify platform.xml to have full access to microSD, install xposed, etc.
It works OK (as far as I can tell, I am not an expert).
CHANGELOG:
Version 2:
Removed even more unnecessary files
Here is the file [UPDATED]:
https://drive.google.com/file/d/0B4aBOrwRL1VMeVUwcFNtNEZnRHc/view?usp=sharing
Many thanks to zxz0O0 for guidance.
Mirror if you want.
Enjoy.
Pc o recovery?
PC. Windows only.
Anyone who can confirm it working? And with no extra features.. Malware etc?
Sorry for my ignorance....but can anyone explain what RIC is and why do we want to kill it ???
forty two said:
I have modified zxz0O0's script for rooting to just kill the SONY RIC, not upload towelroot and stuff.
This is so you can mount /system, modify platform.xml to have full access to microSD, install xposed, etc.
It works OK (as far as I can tell, I am not an expert).
Here is the file:
https://drive.google.com/file/d/0B4aBOrwRL1VMLWJyWWFuTE9qZlE/view?usp=sharing
Mirror if you want.
Enjoy.
Click to expand...
Click to collapse
Can I ask what is RIC?
So is this the exploit to install supersu on 4.4.4?
cynosure4sure said:
Sorry for my ignorance....but can anyone explain what RIC is and why do we want to kill it ???
Click to expand...
Click to collapse
tleung11 said:
Can I ask what is RIC?
So is this the exploit to install supersu on 4.4.4?
Click to expand...
Click to collapse
HellRoot said:
Anyone who can confirm it working? And with no extra features.. Malware etc?
Click to expand...
Click to collapse
Here it goes.
As far as I know, Sony RIC is a kernel module that manages security, but somebody may correct me on that.
The "/system" partition i.e. folder on a Sony Xperia phone cannot be written to, if you don't disable it.
Without writing to the /system, you cannot:
Modify the .xml that enables apps to write to the microSD card, which is disabled by default in kitkat (look at https://play.google.com/store/apps/details?id=nextapp.sdfix).
Install the xposed framework
Modify files in the /system partition for any other purposes.
The usage is as follows:
Get a ftf file for your Z2
Modify it using PRFCreator by using this guide: http://forum.xda-developers.com/xperia-z2/general/4-4-4-creating-rooted-update-package-t2933155
Flash the phone using the recovery with the generated .zip file.
Make sure USB debugging is enabled on your phone, together with Allow mock locations (in Developer options), and that you have adb etc. istalled
Plug the phone, say yes to USB debugging query.
Run the script to kill RIC.
Enjoy.
forty two said:
Here it goes.
As far as I know, Sony RIC is a kernel module that manages security, but somebody may correct me on that.
The "/system" partition i.e. folder on a Sony Xperia phone cannot be written to, if you don't disable it.
Click to expand...
Click to collapse
You Sir are a gentleman and a scholar.
newb-asking-stuff-now^^
Hi there,
Im planing to do this "make ur own pre-rooted update" thing for my Z2 to get this annoying "there is an update available" message away, and maybe it also offers some nice features^^
the thing is this Z2 is my first smartphone in general (tried them in the first gen and hated those commercial-bombers xD so it took me a long while to give it a new try)
so Im not very much into rooting and so on.... I dont even know exactly how I managed to root my actual phone xD but yeah anyhow I did it with a tutorial from xda.....
what i want to ask is.... is this ric-killing really needed? as I said I dunno how exactly I did root for my 4.4.2 but I never had issues with using my SD-card or such..... never heard bout RIC before this thread here aswell.....
what is this for and does everyone need this?
....atleast how does it come that this seems to be needed with the 4.4.4 but wasnt needed on 4.4.2? or why did I never hear bout it?
(my root went something like this: using any batch-file, flashing triple-recovery twpr, cwm, and something I dont remember^^ after that rebooting several times and again flashing something from recovery.... but never there was something stated like RIC.... only TA-Backup had to be made tough Locked bootloader as this scares the **** out of me xD)
Will this work on any Sony device or just Z2?
XenoZirrka said:
Hi there,
Im planing to do this "make ur own pre-rooted update" thing for my Z2 to get this annoying "there is an update available" message away, and maybe it also offers some nice features^^
the thing is this Z2 is my first smartphone in general (tried them in the first gen and hated those commercial-bombers xD so it took me a long while to give it a new try)
so Im not very much into rooting and so on.... I dont even know exactly how I managed to root my actual phone xD but yeah anyhow I did it with a tutorial from xda.....
what i want to ask is.... is this ric-killing really needed? as I said I dunno how exactly I did root for my 4.4.2 but I never had issues with using my SD-card or such..... never heard bout RIC before this thread here aswell.....
what is this for and does everyone need this?
....atleast how does it come that this seems to be needed with the 4.4.4 but wasnt needed on 4.4.2? or why did I never hear bout it?
(my root went something like this: using any batch-file, flashing triple-recovery twpr, cwm, and something I dont remember^^ after that rebooting several times and again flashing something from recovery.... but never there was something stated like RIC.... only TA-Backup had to be made tough Locked bootloader as this scares the **** out of me xD)
Click to expand...
Click to collapse
Not really needed, no. But if you want your navigation software (Sygic, Here maps etc) or custom cameras (from the playstore) to save files to the microSD, it becomes necessary. Thank Google for instituting the silly policy with KitKat. I think they reverted it in Lollipop.
chesterr said:
Will this work on any Sony device or just Z2?
Click to expand...
Click to collapse
I am not sure. I made it for the Z2 and used it on my Z2, but the original script was supposed to work on multiple Sony devices (so it says).
So maybe you could give it a try, and report back?
forty two said:
I am not sure. I made it for the Z2 and used it on my Z2, but the original script was supposed to work on multiple Sony devices (so it says).
So maybe you could give it a try, and report back?
Click to expand...
Click to collapse
Hey bro, It works perfectly fine. I tested it on Z1C and it worked perfectly. :highfive:
just for complete understatement...
So I am actually in lack of some kind of permission as I never did this with my actual ROM? Would this allow me to move apps and just everything I desire and manage to turn on rwrwrw on the external SD?
(or is this not even part of ROM? Im not even clear bout whats included in kernel or ROM, and no idea what exactly is contained in firmware then xD anyhow I know ofcourse what those are but just can never find a explanation what differs those wich I could remember^^ Isnt it in principal all of them are part of the ReadOnlyMemory?)
Tough Im able to use foldermount and link2sd?
is this here then only usefull for "regular.no.root.required.apps" wich dont take advantage of su, or how does it come, that I read bout this kitkat.sd.killing.move but still never found the phrase RIC on my huge googling.expiditions....
(luckily knew this before purchase of a 128gb card and could go for the smaller 32gb wich is more than enough for pictures music and vids xD)
Works perfectly. I was upgraded to 4.4.4 via OTA and I was able to save the root but I wasn't able to mount system r/w. Now everything works perfectly.
XenoZirrka said:
So I am actually in lack of some kind of permission as I never did this with my actual ROM? Would this allow me to move apps and just everything I desire and manage to turn on rwrwrw on the external SD?
(or is this not even part of ROM? Im not even clear bout whats included in kernel or ROM, and no idea what exactly is contained in firmware then xD anyhow I know ofcourse what those are but just can never find a explanation what differs those wich I could remember^^ Isnt it in principal all of them are part of the ReadOnlyMemory?)
Tough Im able to use foldermount and link2sd?
is this here then only usefull for "regular.no.root.required.apps" wich dont take advantage of su, or how does it come, that I read bout this kitkat.sd.killing.move but still never found the phrase RIC on my huge googling.expiditions....
(luckily knew this before purchase of a 128gb card and could go for the smaller 32gb wich is more than enough for pictures music and vids xD)
Click to expand...
Click to collapse
But in future with Lollipop update, I think Sony will let us move apps to SD, in AOSP(CM) builds they have the option to move the apps to SD.
So I discoverd now whats this for, I found out if an app wich doesnt make use of SU wants to write on SD it fails.... I didnt get it cuz I just let make apps use of SD wich anywaye do use SU ....
Only thing Im still wondering about is why can the stock foto.app (sony) write to SD1 and other apps can not? As I know sony.foto never asked for root.permissions^^
Trouble with Google
I have used your software and my phone is full rooted. Unfortunately, OK Google won't work anymore and when I speak, it did't search. What should I do now? Sorry for my bad English.
so, can you explain step by step how to use this?
Working great on D5803 with FW .77
forty two said:
I have modified zxz0O0's script for rooting to just kill the SONY RIC, not upload towelroot and stuff.
This is so you can mount /system, modify platform.xml to have full access to microSD, install xposed, etc.
It works OK (as far as I can tell, I am not an expert).
CHANGELOG:
Version 2:
Removed even more unnecessary files
Many thanks to zxz0O0 for guidance.
Mirror if you want.
Enjoy.
Click to expand...
Click to collapse
Thank you so much. /system could not be mounted in r/w after upgrading my D5803 (Z3 compact) from .93 to .77 and nothing else seemed to work, until a found your utility. Thanks! :highfive:
hello everyone
i have this fig lx1 rooted
i want to debrand it to c432 and I have the oeminfo.bin
how to flash the oeminfo or change it?
Hello!! can you share you c432 oeminfo file please? If i can change the oem info, i'll give you how to make it. I have a tutorial and i don't find the oeminfo file...
Hi, I need oeminfo c432. Please, can you share with me?
Thanks
Is me sharing my oeminfo useful, if I'm currently running a Treble Pie GSI (unofficial)?
FIG-LX1 (L31 board) previously .148 c432 here
Lots of people need that oeminfo files to rebrand their phone, share them please :crying:
I hope this is the right file - copied it from
Code:
/dev/block/platform/hi_mci.0/by-name/
Edited until I know I don't share personal data
..
sun75 said:
Sorry, maybe I'll be wrong... (please correct me!): sharing YOUR oeminfo, you are sharing YOUR imei, mac addresses, serial numbers, etc. I'm wrong?
Click to expand...
Click to collapse
Holy cow - can someone please confirm/deny?
I just saw some other threads, where users shared theirs and I assumed it's safe...
..
sun75 said:
I saw too, but in my oeminfo backup there are many "&token=" and "&hmac=" that, I THINK, are unique for each device... MAYBE I'M WRONG!!!:angel:
---
EDIT:
Interesting things I'm seeing on my oeminfo backup viewing with an hex editor:
- All the Fw installation history, status, checksum, starting from .146 -> to .162 (latest)
- All the IMSI (service provider) you connected to...(Fw by Fw)
- My Device keys (but not, apparently serials, mac, etc, that are in the NVME partition... just done a dd of some partitions not cointained in the update.app).
- Apparently Imeis are in the modemnvm_* partitions (reading other forum posts) stored in crypto format.
So, yes, as for the first two points, I'd suggest not to share it.
Click to expand...
Click to collapse
First off, thanks again for pointing this out and alerting me!
But - I think it's safe to share - awaiting confirmation from a guy, I consider as being an Android Guru (https://forum.xda-developers.com/p1...v-lxx-toolkit-one-t3771015/page2#post77872714).
Using a HexEditor, I only found info related to the latest 2 FW updates I applied (can't remember how many I actually went through, but surely more than 2) - other than that, I can only find the generic SIM/Network Operator identifiers mentioned under IMSI (not my full IMSI), and those hmac and &token keys (which I think are related to the OS).
I also assume, there wouldn't be a Q&A section dedicated to sharing oeminfo/custom.bin files with others in the thread I linked above, if it was not safe.
Edit: Can you please give me more info about the "device keys" you mentioned, how to find them (I also didn't get the "dd of some partitions" part of your reply) - Thanks in advance
..
mega nz/#!0skClZxR!8nEuqKVhEYvBdLMo6VzjcIQwmCS6YrYG8EHr7UuKui0
i dont know if you guys still need it
So its wrong or safe?
..
sun75 said:
I don't know... but I know for sure (please read the entire first thread on this subject https://forum.xda-developers.com/huawei-p-smart/how-to/how-to-root-huawei-p-smart-fig-lx1-t3752705 ) that, no matter if you are unlocked, you will relock your BL and your unlock code will be invalid (because different oeminfo!).
So before doing anything I'll suggest:
- Go back to an earlier firmware with HuRu < June update (because it seems that from August patch DC-Unlocker is out of games!).
- Original Recovery (if something goes wrong... you will not have a Twrp not bootable!)
- Ask more info to someone who already did it!! <----
- 99% you have to pay DC-unlocker to reunlock.... with a different code, but you have a very old firmware, haven't you?
Good luck!
Click to expand...
Click to collapse
I understand, anyone to tell us the instruction? How we can do it?
I'm willing to write a guide on how to debrand, if anyone still needs clarification
Hey guys
Having a weird issue that think is caused by missing DRM data on my Nothing Phone
Basically L1 seems to pass according to DRM info but in log complains about missing /data/vendor/mediadrm/IDM1013/L1/cert.bin
Can someone check if file exists and maybe attach it here if does
File is missing for me too.
Short research tells me it should be in the firmware files or will be generated the first time you try to use something L1 related.
What di you do so far?
xtcislove said:
File is missing for me too.
Short research tells me it should be in the firmware files or will be generated the first time you try to use something L1 related.
What di you do so far?
Click to expand...
Click to collapse
well had an app that used to work just fine
after an update to latest NOS or so, seems to not work anymore
did a logcat seeing that is checking DRM data and switching fine from L3 to L1 just that fails with unknown error
somewhere above in log I see it's complaining of said missing file
did some digging in stock firmware files (extracted myself) yet can't find the file so guessing is generated at first boot or so
just want to "prevent" a factory reset first, so thought to ask how other phones behave with said file if available or not
weird thing it that I see L1 under DRM info, so guess should work
gwolfu said:
well had an app that used to work just fine
after an update to latest NOS or so, seems to not work anymore
did a logcat seeing that is checking DRM data and switching fine from L3 to L1 just that fails with unknown error
somewhere above in log I see it's complaining of said missing file
did some digging in stock firmware files (extracted myself) yet can't find the file so guessing is generated at first boot or so
just want to "prevent" a factory reset first, so thought to ask how other phones behave with said file if available or not
weird thing it that I see L1 under DRM info, so guess should work
Click to expand...
Click to collapse
DRM Info says L1 for me too and the file is missing too. Is there any app i could check if l1 is working for me?
xtcislove said:
DRM Info says L1 for me too and the file is missing too. Is there any app i could check if l1 is working for me?
Click to expand...
Click to collapse
well the app I need is working only in my country and with login credentials, so not much can do there
thx for trying anyway
gwolfu said:
Hey guys
Having a weird issue that think is caused by missing DRM data on my Nothing Phone
Basically L1 seems to pass according to DRM info but in log complains about missing /data/vendor/mediadrm/IDM1013/L1/cert.bin
Can someone check if file exists and maybe attach it here if does
Click to expand...
Click to collapse
copied from Paranoid adroid 13 alpa 2 version , with root .
Exodusnick said:
copied from Paranoid adroid 13 alpa 2 version , with root .
Click to expand...
Click to collapse
Usgtable seems there
cert.bin is missing apparently
Anyway this kind of confirmed file not there in two cases
Might be app issue, idk
oh wrong read sorry.
you wanted to have cert.bin .
the leicer is missing with me too
Don't know if it helps. Clear all app date and cache of widevine needed apps.
gwolfu said:
Hey guys
Having a weird issue that think is caused by missing DRM data on my Nothing Phone
Basically L1 seems to pass according to DRM info but in log complains about missing /data/vendor/mediadrm/IDM1013/L1/cert.bin
Can someone check if file exists and maybe attach it here if does
Click to expand...
Click to collapse
im on stock nothing...no file also...i think it lost when root or unlock bootloader
If you just want to watch a video, this is a good way to get around it.
But Widevine will be L3.
GitHub - umylive/liboemcrypto-disabler: Magisk module to disable liboemcrypto.so DRM (e.g. Netflix, My5) on rooted Android devices.
Magisk module to disable liboemcrypto.so DRM (e.g. Netflix, My5) on rooted Android devices. - GitHub - umylive/liboemcrypto-disabler: Magisk module to disable liboemcrypto.so DRM (e.g. Netflix, My5...
github.com
ot_inc said:
If you just want to watch a video, this is a good way to get around it.
But Widevine will be L3.
GitHub - umylive/liboemcrypto-disabler: Magisk module to disable liboemcrypto.so DRM (e.g. Netflix, My5) on rooted Android devices.
Magisk module to disable liboemcrypto.so DRM (e.g. Netflix, My5) on rooted Android devices. - GitHub - umylive/liboemcrypto-disabler: Magisk module to disable liboemcrypto.so DRM (e.g. Netflix, My5...
github.com
Click to expand...
Click to collapse
with this module, indeed does work
cheers
I have reported this matter to Nothing. If there are more reports they will take the issue.
Issues and New Features Form
Please fill in this form to report issues and suggest new features.
docs.google.com
Also submitted info
Maybe they'll help
Hi everyone
I have created an python script to automate patching of the super partition in A/B devices
can be found here: (https://github.com/ChromiumOS-Guy/SuperPatcherGSI)
important to mention that both Windows / Linux versions only work for 64-bit,
I have attached how a full log of the SuperPatcherGSI script looks like when it successfully makes a patched super.img
also I'm a new user in the XDA forums so please tell me if this post needs to be moved to somewhere else,
feel free to ask any question I will try to answer to the best of my abilities
Enjoy and Thanks.
@ChromiumOS-Guy , you are great and your script works smoothly.
Just installed LineageOS 20 after having MIUI 13.
Somehow, after flashing, my phone lost the MAC address and bluetooth (IMEIs are fine).
Do you think it can be due to LineageOS or for the flashing process?
Welcome to XDA!
Hello good tool i like it but im getting error on repack could you help ?
snx413 said:
Hello good tool i like it but im getting error on repack could you help ?
Click to expand...
Click to collapse
I can try to
newboihere said:
@ChromiumOS-Guy , you are great and your script works smoothly.
Just installed LineageOS 20 after having MIUI 13.
Somehow, after flashing, my phone lost the MAC address and bluetooth (IMEIs are fine).
Do you think it can be due to LineageOS or for the flashing process?
Welcome to XDA!
Click to expand...
Click to collapse
Thanks!,
never happened to me though, try changing LineageOS to 19 had only bad things happen with 20 (my own experience though may not be the same)
if it still doesn't work maybe the firmware you flashed corrupted your nvdata ?
if this is the case you can use SP flash to take a backup of current nvram /nvdata / nvcfg / protect1 / protect2
and try to restore MAC address and bluetooth with SP writer or Modem Meta (don't forget engineering rom)
sorry for reply time i took a break from phone roming (working on making custom PCBs)
edit:
also know that fastbootb(fastboot dynamic) works for flashing dynamic images with phones with fastboot support, this tool is for phones without fastboot like Samsung with download mode ,though it should work all the same just letting you know (if Samsung do have fastboot then i don't know about it)