[F3111/F3113/F3115][N][33.3.A.1.97] How to root and apply DRM fix guide - Sony Xperia XA Guides, News, & Discussion

Special thanks go to rrvuhpg and tplsolution for providing the necessery files and guide tips.
Click to expand...
Click to collapse
This guide only works for the Single SIM model
As there are no major changes to this version from the last version. the same files with a little modification can be used. Before proceeding with this make sure to backup your DRM keys before unlocking your bootloader. If you unlock your bootloader, before backing up you DRM keys, the DRM keys will be lost forever. The guide for backing up your DRM keys can be found here, and for unlocking the bootloader here. This guide assumes that you already downloaded and installed the latest version of Flashtool from here and that your bootloader can be unlocked. Now moving on.
Required files
Boot: https://drive.google.com/file/d/17NBChXsL15GyQaqaJYUwu0ZijBMRzwMl/view?usp=drivesdk
TWRP Recovery: https://forum.xda-developers.com/xperia-xa/development/f3111-f3113-f3115-twrp-recovery-xa-t3639206
SuperSU: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
DRM fix: https://mega.nz/#!Y0lQnTZI!WG5F2Cf_JpxqsZx59ZOVBydkQMy4Gb25kmWYl1HkzQI
Place boot and recovery to the C:\Flashtool\x10flasher_lib folder. Copy SuperSU and DRM fix to your SD card. Rename the recovery to "recovery.img".
Instructions
1.Turn off your phone and keep holding Volume+ and connect the phone to your PC. Keep holding it until the blue light turns on.
2. Open the command window in C:\Flashtool\x10flasher_lib. Then flash boot and recovery with the commands "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img".
3. Disconnect the USB cable and press Volume- and Power button until you hear a vibration. You are now in the recovery. When it prompts for a password, press Cancel and Swipe to allow modifications.
4. Then go to Wipe and press Format Data. You must do this as if you don't, a boot loop will occur. Then go back and go to Install and select your SuperSU file and swipe to install it. If you have you have a backup your TA image, you can now copy it to /data/local/tmp . Then reboot to system.
5. It will take a couple of minutes for the phone to boot up. Once it boots up, setup Android by your liking, just be sure to skip login into my Xperia as it doesn't work without the DRM fix.
6. Turn off your phone and press Volume- and Power button until you hear a vibration. Swipe to allow modifications. Then go to Install, select your DRM fix file and swipe to install it and wait for the installation to complete. Then reboot to system.
7. That's it. Your phone is now rooted and the DRM functions now work. You should have the SuperSU app on your app list now.
Contributors
@rrvuhpg
@tplsolution

anyone post if they have successfully gained root and have DRM working? please. thanks!

saudahmedbass said:
anyone post if they have successfully gained root and have DRM working? please. thanks!
Click to expand...
Click to collapse
Well, if it didn't work, I wouldn't have had posted a tutorial on it. The phone still works as usual, but I don't use it anymore, as I broke the antenna while I was trying to tinker with it, so I had to buy another one, but I haven't rooted it, as I want it to keep it at stock. Like anything else to do with rooting, it's up to you if you want to risk your warranty.

davixdevelop said:
Well, if it didn't work, I wouldn't have had posted a tutorial on it. The phone still works as usual, but I don't use it anymore, as I broke the antenna while I was trying to tinker with it, so I had to buy another one, but I haven't rooted it, as I want it to keep it at stock. Like anything else to do with rooting, it's up to you if you want to risk your warranty.
Click to expand...
Click to collapse
thanks for the reply sir.
my warranty is well overdue lol.
so i just asked if it was a succesful root with drm fix on unlocked bootloader.
i saw another post with 33.3.A.1.115 firmware drm fix and people were reporting that it didnt work so i thought i might ask if i will be able to go back to stock firmware with drm restored(i have backed up drm keys) if i mess around. still a noob around here
thanks again.

saudahmedbass said:
thanks for the reply sir.
my warranty is well overdue lol.
so i just asked if it was a succesful root with drm fix on unlocked bootloader.
i saw another post with 33.3.A.1.115 firmware drm fix and people were reporting that it didnt work so i thought i might ask if i will be able to go back to stock firmware with drm restored(i have backed up drm keys) if i mess around. still a noob around here
thanks again.
Click to expand...
Click to collapse
IDK about 33.3.A.1.115, as I never received it. The only version I got is the 33.3.A.1.97, so I can only guaranty for this version. Also lucky you that you backed up your DRM keys. When I first unlocked the bootloader, I also wanted to back them up, but it didn't work, even tho I installed an older version of the ROM, as it said so on the tutorial back then. So I got frustrated, and just unlocked the bootloader. That's why I included the DRM fix on this guide

davixdevelop said:
IDK about 33.3.A.1.115, as I never received it. The only version I got is the 33.3.A.1.97, so I can only guaranty for this version. Also lucky you that you backed up your DRM keys. When I first unlocked the bootloader, I also wanted to back them up, but it didn't work, even tho I installed an older version of the ROM, as it said so on the tutorial back then. So I got frustrated, and just unlocked the bootloader. That's why I included the DRM fix on this guide
Click to expand...
Click to collapse
the only reason i want to root and ub is to make camera less laggy. idont know why but i experience camera lag in sony camera app and snapchat in low light whereas MM works fine in low light.
can you tell me if your camera works fine or experience some lag in low light? thanks!

saudahmedbass said:
the only reason i want to root and ub is to make camera less laggy. idont know why but i experience camera lag in sony camera app and snapchat in low light whereas MM works fine in low light.
can you tell me if your camera works fine or experience some lag in low light? thanks!
Click to expand...
Click to collapse
My camera works fine.

HELP PLEASE
I did the STEPS EXACTLY but the drm fix didnt work :crying:

PanagiotisXL said:
HELP PLEASE
I did the STEPS EXACTLY but the drm fix didnt work :crying:
Click to expand...
Click to collapse
When you tried to flash the zip, what error did it say?

davixdevelop said:
When you tried to flash the zip, what error did it say?
Click to expand...
Click to collapse
there was no error in the flashing
but when i went to check the drm keys with this--> *#*#7378423#*#*
the screen i saw was :
Factory Reset Reason: Unknown by
WIPE_COMMAND_DATA from TA_MASTER_RESET
2018-07-22 18:09:38 GMT
WIDEVINE_TEST [Unknown Error]
CKB_TEST [Unknown Error]
PRODID_AID : [Unknown Error]
OTP_LOCK_CONFIG : [Unknown Error]
OTP_LOCK_STATUS : [Unknown Error]
AUTH_ENABLE : [Unknown Error]
DEVICE_ID : [Unknown Error]
And then saw another post about F3111 but for 33.3.A.1.115 not for 33.3.A.1.97 here: https://forum.xda-developers.com/xperia-xa/how-to/f3311-root-patched-drm-fix-ta-backup-t3717103
and His keys are working like shown in the pictures did i do something wrong or this is supposed to happen?

PanagiotisXL said:
there was no error in the flashing
but when i went to check the drm keys with this--> *#*#7378423#*#*
the screen i saw was :
Factory Reset Reason: Unknown by
WIPE_COMMAND_DATA from TA_MASTER_RESET
2018-07-22 18:09:38 GMT
WIDEVINE_TEST [Unknown Error]
CKB_TEST [Unknown Error]
PRODID_AID : [Unknown Error]
OTP_LOCK_CONFIG : [Unknown Error]
OTP_LOCK_STATUS : [Unknown Error]
AUTH_ENABLE : [Unknown Error]
DEVICE_ID : [Unknown Error]
And then saw another post about F3111 but for 33.3.A.1.115 not for 33.3.A.1.97 here: https://forum.xda-developers.com/xperia-xa/how-to/f3311-root-patched-drm-fix-ta-backup-t3717103
and His keys are working like shown in the pictures did i do something wrong or this is supposed to happen?
Click to expand...
Click to collapse
try reflashing the drm fix zip, if still not fixed try the steps again by formatting data, and reflashing the files like OP said. it should work

saudahmedbass said:
try reflashing the drm fix zip, if still not fixed try the steps again by formatting data, and reflashing the files like OP said. it should work
Click to expand...
Click to collapse
I did that and didnt work

how to know if DRM is active.??? and what is DRM use on phone.???

Related

Root E5823 on marshmallow

For those who didn't know already: yes, there's a way to root Z5 compact with MM. Bootloader needs to be unlocked.
(1) Install Marshmallow. I did it with flashtool. (I used E5823_32.1.A.1.163_1299-0270_R7C)
--> Clean install, if not, you'll get Google Play Store and Google Play Service to be forced to close.
(2) Install another kernel over here. It's AndroPlus kernel, and I choose the latest version (v20).
--> extract boot.img
-->> (in fastboot mode: power down + press vol up + insert USB) fastboot flash boot boot.img
Edit 20/03/2016: Don't use this version of TWRP. It won't work.
(3) Install TWRP over here, like found in this threat. It's TWRP 3.0.0
--> rename recovery.img
-->> fastboot flash recovery recovery.img
(4) Flash SuperSU like you can find here. I flashed v2.65
You can reboot, your Z5 compact will be on Android 6.0 with Root Access.
By the way, read this before you try to install Xposed.
It's possible to install Xposed. I used v80-sdk23-arm64.zip (framework to flash) and XposedInstaller_3.0_alpha4.apk as installer.
thanks for the summary. It might be worth mentioning that there's a way to keep the DRM functionalities with unlocked bootloader, even when the keys are erased. http://forum.xda-developers.com/xperia-z5/development/sony-credentials-restore-unlocking-t3296383
Didn't try it for myself, but according to the replys, it looks very promising.
Won't hurt you to mention its for Unlocked Bootloader (UB)...
Thanks for the guide, I'll try this once I get home.
E: Clean install means I should wipe my userdata?
bubimir13 said:
Won't hurt you to mention its for Unlocked Bootloader (UB)...
Click to expand...
Click to collapse
You're 100% right. I didn't think about that, because my bootloader was already unlocked.
Kallu609 said:
Thanks for the guide, I'll try this once I get home.
E: Clean install means I should wipe my userdata?
Click to expand...
Click to collapse
Clean install = you need to wipe userdata (not SD card)
Dirty install = you flash new ROM without changing existing userdata.
So indeed, you need to start on a blank canvas and reinstall your apps.
--> If you're using a password manager, like LastPass or something else, it's way easier to start off from a clean system. If you're not using a password manager yet, maybe it's time to reconsider using one.
for me a big point to mention here: sdcard is not workin gat the moment..
so you do have to place all things you need to flash on internal storage.
youvedone said:
for me a big point to mention here: sdcard is not workin gat the moment..
so you do have to place all things you need to flash on internal storage.
Click to expand...
Click to collapse
Weird...
For me, having root access didn't change anything to SD card performance. Which means (for me):
- no problem to install/flash SuperSU using my external SD card.
- no difference after root was installed. I still can flash anything from SD Card.
does it have to be E5823_32.1.A.1.163_1299-0270_R7C?
I'm currently on 32.1.A.1.163_1298_7782_R9C.
should i flash the R7C one?
youvedone said:
for me a big point to mention here: sdcard is not workin gat the moment..
so you do have to place all things you need to flash on internal storage.
Click to expand...
Click to collapse
Helleren said:
does it have to be E5823_32.1.A.1.163_1299-0270_R7C?
I'm currently on 32.1.A.1.163_1298_7782_R9C.
should i flash the R7C one?
Click to expand...
Click to collapse
I only wanted to share the way *I* did it. (because different people mentioned there's no root for Z5C)
I guess it will work with any E5823_32.1.A.* and. it. could also work with other/newer kernels/TWRP/superSU... but I didn't test anything else than this device and this setup. + I know for me it didn't work with TWRP 2.8.7.
toxic_garden said:
thanks for the summary. It might be worth mentioning that there's a way to keep the DRM functionalities with unlocked bootloader, even when the keys are erased. http://forum.xda-developers.com/xperia-z5/development/sony-credentials-restore-unlocking-t3296383
Didn't try it for myself, but according to the replys, it looks very promising.
Click to expand...
Click to collapse
The solution to restore drm functions is already included in the Andropluskernel
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
youvedone said:
for me a big point to mention here: sdcard is not workin gat the moment..
so you do have to place all things you need to flash on internal storage.
Click to expand...
Click to collapse
For me sdcard is working normally under Marshmallow, but can't be mounted in TWRP
--jenana-- said:
I only wanted to share the way *I* did it. (because different people mentioned there's no root for Z5C)
I guess it will work with any E5823_32.1.A.* and. it. could also work with other/newer kernels/TWRP/superSU... but I didn't test anything else than this device and this setup. + I know for me it didn't work with TWRP 2.8.7.
Click to expand...
Click to collapse
Allright,I'll give it a go with the Nordic combined firmware.
Has anybody tried to encrypt after rooting?
Anybody knows if this could work on a E5803 model?
Sent from my E5803 using Tapatalk
I don't really understand the Kernel stuff. But would this just be a workaround to get root for now?
Is it stable?
Would you recommend waiting for a future release?
Thanks!
vibo2013 said:
The solution to restore drm functions is already included in the Andropluskernel
Hang on.... so do i have to follow the guide to update the drm functions or you saying the kernel already has this built in? as in all i need to do is flash the kernel and rom
And can i backup my TA like on the z1c.
Thanks
kam
Click to expand...
Click to collapse
do_salah said:
vibo2013 said:
The solution to restore drm functions is already included in the Andropluskernel
Hang on.... so do i have to follow the guide to update the drm functions or you saying the kernel already has this built in? as in all i need to do is flash the kernel and rom
And can i backup my TA like on the z1c.
Thanks
kam
Click to expand...
Click to collapse
"...Added DRM functions restore patch (thanks tobias.waldvogel)
--This is just a fallback and you have to delete contents of /data/credmgr to enable restore patch...."
Thats what the Changelog on the Androplus Kernel Website says
Click to expand...
Click to collapse
For me scared is working to! I also did not wipe my user data. I just flashed the german vodafone firmware over my existing LP 5.0.2 using flashtool, which kept all my apps. The rest was done as described in the first post. The only app which caused trouble was spotify, I just reinstalled it and everything was fine ...
kevinwu128 said:
I don't really understand the Kernel stuff. But would this just be a workaround to get root for now?
Is it stable?
Would you recommend waiting for a future release?
Thanks!
Click to expand...
Click to collapse
No, nothing about this is stable.
-- Dirty flash of MM could mean that certain apps or parts of the system become unstable.
-- TWRP 3.0 is only released a few days ago. Could contain bugs, who knows...
-- AndroPlus kernel is work in progress. Literally "status: testing". And for more info about that kernel, you can always read/ask in that threat (I don't know the ins and outs of kernels at all)
-- Xposed + it's modules: all work in progress. Some could be stable, some could be buggy.
For now, this is a way to get root. Maybe other developers come with different methods to root, maybe not. But getting root access means: f*ck*ng around with your system on the deepest possible level and breaking some "stability" sony intended to give us. If you would like to take advantage of what root access can give you: give it a try. If you're afraid to break anything: stay away from it or be prepared that you'll have to start over from scratch.
Yes forgot that to clear. Sdcard is working in running system, but not in twrp. Thats no big deal, only nice to know...
And I've tried it german customied did work.. Schud not make any difference as long as it the same version number...
Drm restoration I couldnt check until now.
Nice that I now can restore my app data with titanium backup
---------- Post added at 12:25 AM ---------- Previous post was at 12:20 AM ----------
--jenana-- said:
Weird...
For me, having root access didn't change anything to SD card performance. Which means (for me):
- no problem to install/flash SuperSU using my external SD card.
- no difference after root was installed. I still can flash anything from SD Card.
Click to expand...
Click to collapse
I'll think I have to try again. Perhaps the first boot something was going wrong.. But I couldn't access sdcard and flash supersu from the card with twrp. SoI booted, copied supersu to internal "sdcard" and from there it worked.. I also tried to mount sdcard.. No reaction (but also only at first boot)
--jenana-- said:
No, nothing about this is stable.
-- Dirty flash of MM could mean that certain apps or parts of the system become unstable.
-- TWRP 3.0 is only released a few days ago. Could contain bugs, who knows...
-- AndroPlus kernel is work in progress. Literally "status: testing". And for more info about that kernel, you can always read/ask in that threat (I don't know the ins and outs of kernels at all)
-- Xposed + it's modules: all work in progress. Some could be stable, some could be buggy.
For now, this is a way to get root. Maybe other developers come with different methods to root, maybe not. But getting root access means: f*ck*ng around with your system on the deepest possible level and breaking some "stability" sony intended to give us. If you would like to take advantage of what root access can give you: give it a try. If you're afraid to break anything: stay away from it or be prepared that you'll have to start over from scratch.
Click to expand...
Click to collapse
Thanks for the reply, i can't stand lollipop anymore so i'll give it a try ! I'll update once done!

Blu R1 HD Remove Amazon Ads and OTA Updates for good CUSTOM STOCK SYSTEM

Hi Guys its Rootjunky here and i put together some files for you. Note that this system images is based on custom build version BLU_R0010UU_V6.4_GENERIC and if you use it on other builds you make have problems.
View attachment 3825611
<Mod Edit: Link removed for promoting affiliate sales link.>
How to remove amazon ads and ota updates
Steps
1. Download SP-Flash-Tool-Remove-Amazon-Ads-plus-ota-updates.zip
2. Extract the SP-Flash-Tool-Remove-Amazon-Ads-plus-ota-updates.zip to your desktop. Note 7zip is great to extract files.
3. lauch Flash_tool.exe
4. select scatter-loading and browser to load MT6735_Android_scatter_R1_HD_NO_ADS.txt
5. click download button to start.
6. now plug your phone into the computer. to boot the device to preloader and start the flash. You can do it two ways: 1. power off the phone and flash will start or 2. From a powered off stat power on the device while plugged into the computer. either way will start the sp flash tool.
7. once the flash is complete you can unplug the device and reboot it. Congrats you have removed the ads and ota updates from the Amazon Blu R1 HD. Bounce you have also enabled bootloader unlocking if you want it.
NOTE: ads may still be on the lock screen after this process if so please factory reset the device to remove those ads that are saved in userdata. or if you follow Bootloader unlock Method 2 steps 1-8 your userdata will get wiped in the process
Nice. I already have no ads though.
A couple of questions just to be sure, do I have to be on OTA 6.4 to follow the procedure?, and what do I have to do after that if I want to unlock the bootloader?, use the bootloader unlock script? do I need root and TWRP?, thanks for your awesome work
Edit: Nvm I checked your updated post, he added all the answers HERE, still don't know if I have to be on 6.4 tho
viktorfk said:
A couple of questions just to be sure, do I have to be on OTA 6.4 to follow the procedure?, and what do I have to do after that if I want to unlock the bootloader?, use the bootloader unlock script? do I need root and TWRP?, thanks for your awesome work
Edit: Nvm I checked your updated post, he added all the answers HERE, still don't know if I have to be on 6.4 tho
Click to expand...
Click to collapse
i would recommend being on v6.4 yes but i think the system will still work on v6.1 but i havent checked. and yes the other post just got updated
Tomsgt said:
i would recommend being on v6.4 yes but i think the system will still work on v6.1 but i havent checked. and yes the other post just got updated
Click to expand...
Click to collapse
Don't want to bother you but can I use those system images to recover my phone with spft in case something goes wrong later? since it's custom stock system.
viktorfk said:
Don't want to bother you but can I use those system images to recover my phone with spft in case something goes wrong later? since it's custom stock system.
Click to expand...
Click to collapse
you can use this firmware to recovery the phone at any time it will return it to full stock v6.4 with working ota updates and all the ads
Tomsgt said:
you can use this firmware to recovery the phone at any time it will return it to full stock v6.4 with working ota updates and all the ads
Click to expand...
Click to collapse
You're awesoomeee man, thanks :highfive:
How do I factory reset the device to remove those ads on the lockscreen. I have looked everywhere in the settings menu with no luck. I saw the video rootjunky made and followed step by step, but can't find the factory reset button. I am new to Android.
xchaser said:
How do I factory reset the device to remove those ads on the lockscreen. I have looked everywhere in the settings menu with no luck. I saw the video rootjunky made and followed step by step, but can't find the factory reset button. I am new to Android.
Click to expand...
Click to collapse
Just added a video to the OP
Tomsgt said:
you can use this firmware to recovery the phone at any time it will return it to full stock v6.4 with working ota updates and all the ads
Click to expand...
Click to collapse
Does this restore stock recovery, boot and system images? Or just System? Do you have a version of SPTools with all three of these?
What exactly is needed to remove the ads? (excluding flashing an entire modified system partition.) What has been modified in this partition?
EDIT - nevermind, i figured it out
I followed your root method and bootloader unlocking video prior to this, what steps would I do to remove the ads.
cmart0125 said:
I followed your root method and bootloader unlocking video prior to this, what steps would I do to remove the ads.
Click to expand...
Click to collapse
Just flash the files in sp flash tool a d thats it
My apologies if this has been covered elsewhere but I followed the guide to root and unlock the bootloader. Out of curiosity I downloaded titanium backup and froze Amazon Offers. I haven't had any ads on the lock screen since then. Rebooted a few times and it seems to have worked. Is there any benefit to going through this process rather than what I have done?
Tomsgt said:
Just flash the files in sp flash tool a d thats it
Click to expand...
Click to collapse
Flash removal of ads script using sp flash tool then boot into twrp recovery and clear data and cache...correct?
Natef53 said:
My apologies if this has been covered elsewhere but I followed the guide to root and unlock the bootloader. Out of curiosity I downloaded titanium backup and froze Amazon Offers. I haven't had any ads on the lock screen since then. Rebooted a few times and it seems to have worked. Is there any benefit to going through this process rather than what I have done?
Click to expand...
Click to collapse
Nope really except for the fact that I also removed ota updates.
cmart0125 said:
Flash removal of ads script using sp flash tool then boot into twrp recovery and clear data and cache...correct?
Click to expand...
Click to collapse
Yes that will work.
Tomsgt said:
Just added a video to the OP
Click to expand...
Click to collapse
Thanks A lot that worked like a charm.
For people not willing to download 1.3GB of data to remove a few files I updated the original ad removal post with TWRP install files http://forum.xda-developers.com/showpost.php?p=67892852&postcount=567
It's only 3kb
This updated method remove the need of wiping the data and will remove all ads, even the one currently displayed on the lock screen.
Root or exposed are not required (only TWRP obviously) so it won't affect the device security.
I created 2 scripts, one to clean everything, the other one leave the Underground app store in the system, your choice.
If you use it a lot, it's nice as it will update the apps automatically without the need of allowing unknown sources.
OTA are disabled by renaming the updater. Safer than the previous method (pm disable and pm hide), and safer than deleting if we need it later.
would flashing the stock system image from non ad version also work.?
I have BLU_R0011UU-V12-GENERIC 27-06-2016
I have the 16gb no ad. the file is 2.6 gb so dont want to upload it if it will not be of any use

Help I wanto to Re-Lock the bootloader

Hi I need your help, Iwant yo re-lock the bootloader on my OnePlus 6T
I understand that I have to go back everything on factory but I dont know how do it.
I did the ''root'' because I wanted to change the font and improve the sound but tlost quality on Netflix, and I that is important to me because I use it a lot. I want to back to L1
The problem was when I tried to eliminate the ''root'' (magisk) The system did not star and i was afraid because Iam not an expert so i flashed the ''full OTA'' and it works again, Now I want to remove twrp but I dont know how so I need help because i dont want brick my phone
I got the recovery 9.0.7 stock.img if I flash it will work?
sorry for my english..
Thanks
ross92 said:
Hi I need your help, Iwant yo re-lock the bootloader on my OnePlus 6T
I understand that I have to go back everything on factory but I dont know how do it.
I did the ''root'' because I wanted to change the font and improve the sound but tlost quality on Netflix, and I that is important to me because I use it a lot. I want to back to L1
The problem was when I tried to eliminate the ''root'' (magisk) The system did not star and i was afraid because Iam not an expert so i flashed the ''full OTA'' and it works again, Now I want to remove twrp but I dont know how so I need help because i dont want brick my phone
I got the recovery 9.0.7 stock.img if I flash it will work?
sorry for my english..
Thanks
Click to expand...
Click to collapse
Check this thread, and follow local update method, then you need only of a command to lock the bootloader:
https://forum.xda-developers.com/oneplus-6t/how-to/how-to-update-return-to-stock-oneplus-6-t3870795
I just locked the bootloader for my OnePlus 6t. Follow the steps given below.
1. Backup all the important data. I am not responsible for any data loss!!!
2. Remove security lock screen (pin/pattern) or any thing
3. Download the stock rom from https://oxygenos.oneplus.net/OnePlus6TOxygen_34_OTA_020_all_1904032212_38e22c8b9abd42e3.zip
and transfer it to your phone.
4. Boot into twrp recovery.
5. flash the downloaded zip
6. Once done, reboot the system.
7. Now, boot back into the fastboot. (you can enable advance restart from developer mode for easy boot into fastboot)
8. Run fastboot oem lock
9. You will be presented with two options on phone screen. Select the one that says lock the bootloader.
10. It will wipe everything.
11. Once you in the system, enable developer mode and make sure that oem unlock is turned off. If not, turn it off and restart your phone.
And, you are done.
Let me know if it helps or if you have any question/concern.
MDM Tool in my opinion the easiest and quickest way to go back to 1000% stock. It will re-flash every partition on the phone so it's like brand new again. Using the MSM Tool guarantees that everything is back to stock and should restore the Widevine version back to L1 or whatever it was originally.
A question please
Once you lock again your phone, does it loose the root????
I mean, I have a Xperia 10 with the bootloader unlocked , it is root as well. Now root permissions for special aps work fine, but Google Pay is unusable, it does not work anymore. I hid root with xposed framework and rootCloak, but Google Pay still does not work now because the bootloader is unlocked...
As you should know, it is possible to lock the phone again... and many of those phones that relock their bootloaders keep the root permissions...
However , in my case, with Xperia devices (bq and xiaomi happen de same) is you lock the bootloader again, the phone resets, everything dissapear and root is eliminated. What is a really disaster.
As you have heard, the majority of phones, if you lock them again the root continues working, at least the apps that you gave them root permissions they continue working as they used to. But in my case this is different....ç
So please,
Is there any possibility to Lock my bootloader again without loosing the Root in my Xperia?????
Thousand of thanks!!!!
Bardok84 said:
A question please
Once you lock again your phone, does it loose the root????
I mean, I have a Xperia 10 with the bootloader unlocked , it is root as well. Now root permissions for special aps work fine, but Google Pay is unusable, it does not work anymore. I hid root with xposed framework and rootCloak, but Google Pay still does not work now because the bootloader is unlocked...
As you should know, it is possible to lock the phone again... and many of those phones that relock their bootloaders keep the root permissions...
However , in my case, with Xperia devices (bq and xiaomi happen de same) is you lock the bootloader again, the phone resets, everything dissapear and root is eliminated. What is a really disaster.
As you have heard, the majority of phones, if you lock them again the root continues working, at least the apps that you gave them root permissions they continue working as they used to. But in my case this is different....ç
So please,
Is there any possibility to Lock my bootloader again without loosing the Root in my Xperia?????
Thousand of thanks!!!!
Click to expand...
Click to collapse
Go ask in Xperia threads
Striatum_bdr said:
Go ask in Xperia threads
Click to expand...
Click to collapse
Yes I did:
https://forum.xda-developers.com/xperia-10/development/help-how-to-lock-bootloader-loosing-t3965829/post80203451#post80203451
Also I asked for help here:
https://forum.xda-developers.com/android/help/how-to-lock-google-pay-xperia-rooted-t3965637
https://forum.xda-developers.com/galaxy-nexus/themes-apps/app-bootunlocker-nexus-devices-version-t1731993/page66
https://forum.xda-developers.com/galaxy-nexus/themes-apps/app-bootunlocker-nexus-devices-version-t1731993/page66
This is the only Thread where I could find some information about locking a bootloader again. Yes , this is dedicated to xiaomi 6t, but locking bootloaders is something common.
The only thing I want is to lock my Bootloader again without loosing Root permisions. Xperia devices seem to RESET everything when you lock the booloader automatically...., but perhaps there is another way.... a possibility to lock the bootloader without the phone is reset (loosing root permissions) ....
I asked for some help here. I regret any inconvenience that could may be caused on this thread with my message.
Regards
Nobody have your phone here how could we help you? Each phone has its specific behavior
If you relock a OnePlus phone you reset everything, like when you unlock it and it's logical. A locked bootloader is meant to ensure safety of data, safety that can't be provided with root access. Locked BL and root are antinomic.
Striatum_bdr said:
Nobody have your phone here how could we help you? Each phone has its specific behavior
If you relock a OnePlus phone you reset everything, like when you unlock it and it's logical. A locked bootloader is meant to ensure safety of data, safety that can't be provided with root access. Locked BL and root are antinomic.
Click to expand...
Click to collapse
Thank you for your message and understanding. So in Oneplus devices happen the same. So once you unlock the bootloader you loose Google Pay forever because it does not work wit BL unlocked...
Some users suggested me to lock again the bootloader,
Imagine:
- I become Root. Then I modify some apps
- I give to some apps root permissions.
- I lock the bootloader again.
- I won't be able to modify my phone anymore, but all those apps that were given root permissions, Will they be kept in the phone although it has BL locked again.
would it be like this?
or all changes you did while being root would dissapear with everything?????
If So... there is no exit what I see..., We have to choose between being Root users.... or being stock with Google Pay. It is a Pity.
I was not sure if all Phones reset and erase everything when you lock the bootloader .... but as I can see here, this is the reality. Root users loose Google PAY definitely.
Is there any option to solve this??
thanks again for your attention.
regards
Bardok84 said:
Thank you for your message and understanding. So in Oneplus devices happen the same. So once you unlock the bootloader you loose Google Pay forever because it does not work wit BL unlocked...
Some users suggested me to lock again the bootloader, but if I do that, as you have said, the Root and everything will be erased because the phone resets everything. So... there is no exit what I see..., We have to choose between being Root users.... or being stock with Google Pay. It is a Pity.
I was not sure if all Phones reset and erase everything when you lock the bootloader .... but as I can see here, this is the reality. Root users loose Google PAY definitely.
Is there any option to solve this??
thanks again for your attention.
regards
Click to expand...
Click to collapse
I'm unlocked and rooted c and Google pay works perfectly with Magisk
Striatum_bdr said:
I'm unlocked and rooted c and Google pay works perfectly with Magisk
Click to expand...
Click to collapse
Does google pay work??? What did you do in magisk exactly to achieve that???
I rooted my xperia using Magisk..., is there any tutorial or info that you suggest to me to follow ? or what should I do in magisk options???
I have 10 days with my phone stopped, trying and trying to make Google Pay works....Maybe this is happening to me because my Xperia uses Android 9.0.... or Magisk should make google pay work even being in android 9.0?
First Google pay recognized Root, and the app stopped working. I hid it using xposed and RootCloak
Then, Google pay recognized Bootloader. But now... I dont know what to do to hid bootloader unlocked for Google..., Google pay recognises it is unlocked... a disaster and a nightmare for me, I dont know what to do...
Thousand of thanks, I really thankfull for your help.
Regards

G6 Play: Pie Soak Test

Please mirror.
ui_print("Target: motorola/aljeter/aljeter:9/PPP29.41/b1fe5:user/release-keys");
Download
As far as I know, you must be on the Sept. patch. So, you must downgrade firmware first. It also appears to be for the Aljeter only, so I don't know if it'll work on the Jeter.
I am not responsible for any bricked devices.
1. Downgrade to OPP27.91-143 first.
2. Extract gpt_main0.bin from the ota zip and flash it in fastboot.
fastboot flash partition gpt_main0.bin
3. Reboot to recovery, and apply the OTA update from your sdcard.
4. Let the system restart. It'll take about 10min.
Could anyone verify?
Figures it's for Aljeter. Makes me wonder if Jeter will get it at all.
yes it is for aljeter and is working fine
Spaceminer said:
Please mirror.
ui_print("Target: motorola/aljeter/aljeter:9/PPP29.41/b1fe5:user/release-keys");
Download
As far as I know, you must be on the Sept. patch. So, you must downgrade firmware first. It also appears to be for the Aljeter only, so I don't know if it'll work on the Jeter.
These installation steps need confirmation. I am not responsible for any bricked devices.
1. Downgrade to OPP27.91-143 first.
2. Extract gpt_main0.bin from the ota zip and flash it in fastboot.
fastboot flash partition gpt_main0.bin
3. Reboot to recovery, and apply the OTA update from your sdcard.
4. Let the system restart. It'll take about 10min.
Click to expand...
Click to collapse
Tested and working on G6 Play do Brasil!
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Eddster3000 said:
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Click to expand...
Click to collapse
That's a Pie/Magisk problem. Easy fix...
1. Format /data in TWRP using the "yes" option. Then reboot directly back into recovery.
2. Mount /vendor then flash the universal dm-verity disabler by zackptg5.
3. Reboot directly into recovery once more and flash Magisk.
4. Reboot normally, and install the Magisk manager app manually. Done.
(Magisk should disable encryption and verity, but I've never had it work %100 of the time for both. Hence the disabler.)
Spaceminer said:
That's a Pie/Magisk problem. Easy fix...
1. Format /data in TWRP using the "yes" option. Then reboot directly back into recovery.
2. Mount /vendor then flash the universal dm-verity disabler by zackptg5.
3. Reboot directly into recovery once more and flash Magisk.
4. Reboot normally, and install the Magisk manager app manually. Done.
(Magisk should disable encryption and verity, but I've never had it work %100 of the time for both. Hence the disabler.)
Click to expand...
Click to collapse
Thanks @Spaceminer !!!! I'll give it a go. I thought at first that I might need to make some sort of patched boot image and faff about quite a bit but your instructions are clear and straightforward.
I must say I'm impressed with the G6 Play. I had a Nexus 6P and a Pixel both of which died on me from physical and customisation fatigue. I could afford a flagship so got this to see be through and I haven't had one complaint yet.
The handful of Pie features and esthetics have been implemented well by Motorola and battery life is still epic on this device.
Edit: rooted and fully set up how I usually have my daily driver handset. Pie is so tasty!
Eddster3000 said:
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Click to expand...
Click to collapse
Ta for taking the plunge and testing mate! Was beginning to think we'd never get this thing, glad to know it works on the same model number as I've got
Now to figure out the exact detailed step-by-step to getting this going, considering I'm actually on the November update...
picopi said:
Ta for taking the plunge and testing mate! Was beginning to think we'd never get this thing, glad to know it works on the same model number as I've got
Now to figure out the exact detailed step-by-step to getting this going, considering I'm actually on the November update...
Click to expand...
Click to collapse
Op is a step by step. Literally. Downgrade to Sept = Flash the build specified. Except the bootloader etc.
Flash the gpt.bin from the new build, apply update.
madbat99 said:
Op is a step by step. Literally. Downgrade to Sept = Flash the build specified. Except the bootloader etc.
Flash the gpt.bin from the new build, apply update.
Click to expand...
Click to collapse
Well yeah, I know that much. I meant the extra stuff like unlocking bootloader and downgrading the firmware etc lol. Ta for the extra info, mind.
Extra questions though because despite being having novice experience of doing phone flashing stuff, I've never touched a soak test for official firmware before...but I'm guessing I'll have to move back to Oreo temporarily to get the official Pie update...? Or will it just shift up from this soak test version?
Anyone get this working with the xt1922-7?
Donavonn said:
Anyone get this working with the xt1922-7?
Click to expand...
Click to collapse
No dice! The bootloader won't accept the gpt.bin. I think the recovery partition is the only thing that gets expanded though, so... I think if someone makes a back up of Pie in TWRP, then I can make it work on our phone. My idea is this.
1. Restore a Pie system backup using twrp, including the boot.img.
2. Use fastboot to flash the modem, oem.img, and vendor.img. Basically flash every part that isn't a patch file.
3. Hope that crap works.
I think that, or something similar would make it happen. I'll be the lab rat if someone wants to upload a system backup.
Spaceminer said:
No dice! The bootloader won't accept the gpt.bin. I think the recovery partition is the only thing that gets expanded though, so... I think if someone makes a back up of Pie in TWRP, then I can make it work on our phone. My idea is this.
1. Restore a Pie system backup using twrp, including the boot.img.
2. Use fastboot to flash the modem, oem.img, and vendor.img. Basically flash every part that isn't a patch file.
3. Hope that crap works.
I think that, or something similar would make it happen. I'll be the lab rat if someone wants to upload a system backup.
Click to expand...
Click to collapse
Haha yes! Someone get this guy a backup! Also, if it does work, the UI and everything can be changed to English, right?
Okay quick question, considering it was said "Flash the build specified except bootloader etc."; what is meant by "etc" here? Which parts of the older firmware should I avoid flashing. I know I gotta get in on that sparsechunk action but what about the other stuff like fsg, modem, boot etc? Sorry for asking what's probably a very obvious question but I don't wanna accidentally bugger my phone up trying to get this working
Donavonn said:
Haha yes! Someone get this guy a backup! Also, if it does work, the UI and everything can be changed to English, right?
Click to expand...
Click to collapse
Yes, it should be possible on the first setup. I think if it works, LTE probably won't without an APN edit. That's what happens when I flash xt1922-5 RETUS firmware anyways.
picopi said:
Okay quick question, considering it was said "Flash the build specified except bootloader etc."; what is meant by "etc" here? Which parts of the older firmware should I avoid flashing. I know I gotta get in on that sparsechunk action but what about the other stuff like fsg, modem, boot etc? Sorry for asking what's probably a very obvious question but I don't wanna accidentally bugger my phone up trying to get this working
Click to expand...
Click to collapse
Flash every part of the old firmware that you are able to. The bootloader and gpt.bin usually fail to flash if they are older than your current version. You should still try anyways. If they fail, just continue flashing the next items in line.
Spaceminer said:
Flash every part of the old firmware that you are able to. The bootloader and gpt.bin usually fail to flash if they are older than your current version. You should still try anyways. If they fail, just continue flashing the next items in line.
Click to expand...
Click to collapse
Righto. Just to clarify, I'm gonna need to unlock my bootloader to make this downgrade happen, right?
picopi said:
Righto. Just to clarify, I'm gonna need to unlock my bootloader to make this downgrade happen, right?
Click to expand...
Click to collapse
Official firmware should flash without any issue on a locked bootloader. That's my understanding. I don't know if this is %100 accurate. Every Motorola I've ever had, I unlocked the bootloader immediately. So, I've never had to test this.
Spaceminer said:
Official firmware should flash without any issue on a locked bootloader. That's my understanding. I don't know if this is %100 accurate. Every Motorola I've ever had, I unlocked the bootloader immediately. So, I've never had to test this.
Click to expand...
Click to collapse
Righto. In that case I'll report back with my findings, but yeah I'd imagine it should work fine as well. We'll see, fingers crossed.

Beginner Tutorial - Unlock Bootloader + TWRP + Root

Hi everyone, I just want to share this tutorial for someone like me (NEWBIE, NOOB, BEGINNER, ZERO KNOWLEDGE).
ALL CREDITS TO THE RIGHTFUL OWNER.
PRE-REQUISITES
- Laptop
- Applications, .img files (https://mega.nz/file/igphSCTD#OybJo9t1zwvJ0bdbAcN2BCqxWXAfHdhk3JFB4_5xkVc)
- Your Nubia Phone
ENSURE THAT:
- You installed the application and driver (Minimal ADB and Fastboot & the driver from your Nubia phone).
- You updated your OS in the latest version.
- You UNLOCK the developer option (setting>>about phone>>tap 7x the build number) and you switch ON the OEM unlocking & USB Debugging.
- You approved the RSA request in your RM5G
NUBIA RED MAGIC 5G UNLOCK BOOTLOADER
1. Connect your Nubia in laptop, in your laptop, open Minimal ADB and Fastboot and type the following:
a. adb reboot bootloader
b. fastboot oem nubia_unlock NUBIA_NX659J
c. fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
d. fastboot flash vbmeta vbmeta_BL_skip.img
e. fastboot flash modem NON-HLOS.bin
f. fastboot flash parameter parameter.img
2. Go to your RM5G, select reboot to recovery
3. It will reboot in TWRP twice, in the 2nd reboot it will stay in TWRP, change the language to English and select the keep read only.
4. Go to WIPE option, then select FORMAT DATA, type yes
5. Press home button, then go to REBOOT, select REBOOT to RECOVERY
NUBIA RED MAGIC 5G ROOTING PROCEDURE
6. Go to ADVANCED, below there are list, select INSTALL ROOT.
7. Reboot your RM5G.
At first, my RM5G restart twice, I was afraid that it was bootloop, the 3rd boots, it booted up and its rooted already.
Also, when I first registered my Finger Print, it’s malfunctioning, so I just deleted the OLD FP , register NEW FP and it works like a charm.
Now, I managed to flash the wonderful kernel of @mslezak.
Credits:
@mslezak - for his tutorial,
files we used in this thread https://forum.xda-developers.com/nu...how-to-unlock-bootloader-redmagic-5g-t4081743
And kernel in this thread: https://forum.xda-developers.com/nu...od-kernel-red-magic-5g-simply-source-t4112811
Ibr ALnaQbi - for his video tutorial
And to all who made it successful.
Great job bro !
Note for those that don't know how to enable developer options - go to settings, about phone, click build number 7x. It should take you right to the Developer Options menu. Nice clear concise guide by the way! Glad someone wrote a simpler one than the one I wrote initially, only so many hours in the day.
mslezak said:
Note for those that don't know how to enable developer options - go to settings, about phone, click build number 7x. It should take you right to the Developer Options menu. Nice clear concise guide by the way! Glad someone wrote a simpler one than the one I wrote initially, only so many hours in the day.
Click to expand...
Click to collapse
Thanks for mentioning the dev. option. All credit to all of you guys who made this possible.
I've been trying for days to download the MEGA zip, but no matter what I do it always stays on 0% and gives me an error. I tried on different browsers, on different computers, and using the desktop app, I even tried with the mobile app with no luck. Could someone please share a mirror or another link, please?
Nevermind, I was finally able to download the file, my solution was to use chrome instead of firefox and close every window except the mega one... I left it like that for a couple of hours and it finally downloaded it.
Possibly a stupid question, but are there any downsides to this other than the risk of bricking?
samussamus1 said:
Possibly a stupid question, but are there any downsides to this other than the risk of bricking?
Click to expand...
Click to collapse
If you follow the tutorial, there will be no problem even soft brick.
luis7654 said:
Nevermind, I was finally able to download the file, my solution was to use chrome instead of firefox and close every window except the mega one... I left it like that for a couple of hours and it finally downloaded it.
Click to expand...
Click to collapse
Its a normal troubleshooting, if its not working to other browser, try another one, great to hear that you managed, happy rooting.
CaLix25 said:
If you follow the tutorial, there will be no problem even soft brick.
Click to expand...
Click to collapse
Thanks but this isn't what I meant, I was thinking more so of apps not working due to root detection. Banking apps or others?
-
Sam
samussamus1 said:
Thanks but this isn't what I meant, I was thinking more so of apps not working due to root detection. Banking apps or others?
-
Sam
Click to expand...
Click to collapse
You can hide the Magisk (setting/select the apps/then hide magisk) so it will not detect that you are rooted.
CaLix25 said:
You can hide the Magisk (setting/select the apps/then hide magisk) so it will not detect that you are rooted.
Click to expand...
Click to collapse
Brilliant, thank you!
-
Sam
Hi,
2 questions. First of all, does this method work for all of the 5G phones? As in the European version etc. And second of all, will the phone brick if you update it via OTA, or do we need to do this method every time?
Noahesbjerg said:
Hi,
2 questions. First of all, does this method work for all of the 5G phones? As in the European version etc. And second of all, will the phone brick if you update it via OTA, or do we need to do this method every time?
Click to expand...
Click to collapse
Hi,
1. Yes its applicable for all version.
2. Yes it will brick your phone when updating via OTA
you can take a screen for hide magisk for app (Root) because I can't find it.
and still no solution to recover the fingerprint reader? thank you
cyberpunkfw1983 said:
you can take a screen for hide magisk for app (Root) because I can't find it.
and still no solution to recover the fingerprint reader? thank you
Click to expand...
Click to collapse
Hi, see attached. You have to rename the Magisk after selecting in pic. # 1.
You can find the FP calibration procedure here in XDA.
Ty ?
Hi Guys, first of all thanks for awesome tutorial. Got it rooted and enjoying the perks. However, some issues do exist. 1. The phone has detected a new update v4.09. Will the root be deactivated if I update the system? Second question, my banking app is detecting the root and does not want to start. I did set magisk manager to hide it from the app and restarted the phone even, but no luck the app still sees the root. Any solution for it? Thanks all
hello I would like to know how to put it back original? bootloader, Root ... thank you
Zigi86 said:
Hi Guys, first of all thanks for awesome tutorial. Got it rooted and enjoying the perks. However, some issues do exist. 1. The phone has detected a new update v4.09. Will the root be deactivated if I update the system? Second question, my banking app is detecting the root and does not want to start. I did set magisk manager to hide it from the app and restarted the phone even, but no luck the app still sees the root. Any solution for it? Thanks all
Click to expand...
Click to collapse
1. If you updated your RM5G before rooting, its bug, ignore it.
2. Mine is working as i showed in the photo above (ANB)

Categories

Resources