Database Users

[06 Sept 2012][ICS]Universal Rooting for most ICS phones, Any ROM, now with CWM6

[06 Sept 2012][ICS]Universal Rooting for most ICS phones, Any ROM, now with CWM6
See original thread here:
http://forum.xda-developers.com/showthread.php?t=1746794
For questions, feedback and support, please do not post here, but in original thread
Root your ICS phone S2 + Samsung + not Samsung phones - No more waiting for custom kernels
This topic provides universal root methods to bypass the use of custom kernels. I took the time to write it as I was tired from waiting for a Dev to publish a custom kernel for the last firmware released.
I will try here to reference most threads and ways to root your phone. Some methods will let you root as soon as you get the new ROM, no more waiting for some dev to release a kernel for you.
I will not list here custom kernels that come with root, you can find them in other threads.
As a general rule, do not forget to take extra precautions when you flash anything: ALWAYS DO A NANDROID BACKUP IN CWM
Method 1 - Recommended
Push superuser + Busybox (Now v1.20.2 from Linus Yang) in recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, on the i9100 and some other phones (N7000...), you can flash the attached signed zip files in stock recovery, no more need to CWM.
A BIG BIG THANK YOU TO Chainfire for his support that made it possible and to Entropy512 who pushed me to look for a fix
Attached is the CWM Recovery 4.x non touch version, confirmed safe for wiping. It will not superbrick your phone
>>>>>> Now it is even getting greater with attached Clockworkmod v6.0.1.2 !!!! <<<<<<
>>>>>> Also probably safe from brickbug <<<<<<​
Pros
Universal and will probably work on any ICS phone, if you have a CWM image. No longer wait for a modded kernel
On the i9100 and some other phones (N7000...), you can now even root from the stock recovery, no need to the cwm image
No PC needed, only an android device and the zip files that you download to your sd card
Fully reversible unroot without PC needed
No Yellow Triangle (Only for phones with a zip CWM image)
No custom counter increased (Only for phones with a zip CWM image)
Only copies superuser +/- busybox, nothing else is touched, neither /data nor the kernel
No brick risk while flashing cwm even if things go wrong as it will be always overwritten by stock recovery after a reboot
Click to expand...
Click to collapse
Cons
None since I switched to the CWM4 and CWM6 recoveries (no more superbrick risks under 4.0.4 ICS kernels, only CWM5.x was affected)
Click to expand...
Click to collapse
Special notes about busybox
The zip files attached in this post install busybox only in /system/xbin. I do not put any symlink in /system/bin
If you previously installed other versions of busybox, I advise to run Busybox Uninstaller v1.0 zip in the thread dedicated to it here: http://forum.xda-developers.com/showthread.php?t=1853419
It will clean any orphan symlink that could be left from a previous install. After that, install busybox from any of the attached files in this post
The uninstaller in this post, only removes busybox package from /system/xbin. I do not delete any package put in bin, as it is assumed it was put there by another program, not my script. It will not remove any symlink either. So, run the Busybox Uninstaller v1.0 for that
Click to expand...
Click to collapse
This method was first inspired from Rachmat3 thread here and Chainfire script here (do not forget to thank them). I modified it to work in stock recovery, enhanced script, include Chainfire superSU last version + BusyBox last binary. I also keep a ChainsDD superuser version.
Instructions
For phones affected by the superbrick bug (i9100, N7000) and that has a stock recovery accepting update.zip files (most phones with a temporary cwm.zip file at Clockworkmod site:
You can flash the attached files directly in stock recovery 3e, no need to cwm:
Download the root file:
- Root_SuperSU.0.96.Only-signed.zip for Chainfire SuperSU (the one that comes with CF_Root) without busybox.​- Root_SuperSU.0.96-FreeSpace.zip for Chainfire SuperSU without busybox (use only if you have issues with previous one, usually for phones having a /system partition with 0 free space).​- Root_SuperSU.0.96-Busybox.1.20.2-S2-signed.zip to install superSU + busybox v1.20.2 from Linus Yang.​- Root_Superuser_3.1.3_Busybox_1.20.2-Update1-signed.zip if you prefer the classic ChainsDD superuser + Busybox from Linus Yang.​- Root_Busybox_1.20.2_Only_XXX.zip to install only Busybox from Linus Yang.​
I advise Chainfire SuperSU for 2 reasons: it lets you unroot from within superSU application and it lets you migrate to ChainsDD superuser if you like later
.
Copy the Root_XXX.zip file you downloaded to externalsd card
Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the Root_XXX.zip file downloaded above and you are rooted
To unroot, do the above steps and replace the file Root_XXX.zip by the attached Unroot_SuperUser-Busybox-Uninstaller-Update2-signed.zip. It will delete superuser, su and busybox packages.
For a complete removal of busybox, look here at my Busybox Uninstaller which will remove ALL busybox symlinks (over 600 files depending on installers used before):
http://forum.xda-developers.com/showthread.php?t=1853419
To get temporary cwm (to make nandroid backups...) or if stock recovery gives you a signature error, follow the next more universal steps.
Click to expand...
Click to collapse
.
.
For most (if not all?) ICS phones having a CWM image at Clockworkmod site:
Download attached cwm-touch-6.0.x.x-i9100.zip for the i9100 Galaxy S2. This is the touch version but it also works with volume up/down keys and power button to select menu.
CWM6 is now thought to be probably safe for wipe, no superbrick risks under ICS 4.0.4: read more here
I also attached the cwm6 non touch version and the recovery-clockwork-4.0.1.5-galaxys2.zip. CWM4 is also confirmed to be safe for wipe by Entropy512 Recognized Developer
For other phones, download the cwm image from here http://clockworkmod.com/rommanager
.
Put the previously downloaded cwm-touch-6.0.x.x-i9100.zip file on your external sd card
Download the attached root file you want as per instructions above
I advise Chainfire SuperSU for 2 reasons: it lets you unroot from within superSU application and it lets you migrate to ChainsDD superuser if you like later
Copy the Root_XXX.zip file you downloaded to internal or external sd card
Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the cwm-touch-6.x.x.x-i9100.zip file you copied in previous step (this step gives a temporary flash that will disappear after reboot)
You get CWM recovery interface (this custom recovery is temporary, not permanent)
Inside CWM, select "install zip from sdcard". Then, select "choose zip from sdcard". Now, scroll down to the "Root_XXX.zip" file and hit power button to install it.
It will add SuperSU or Superuser last version apk to system/app, last superuser binary (su) to system/xbin and busybox last version to system/xbin, all with correct file permissions.
Reboot and you get permanent root + busybox installed on your stock kernel.
To unroot, do the above steps and replace the file Root_XXX.zip by the attached Unroot_SuperUser-Busybox-Uninstaller-Update2-signed.zip. It will delete superuser, su and busybox packages.
For a complete removal of busybox, look here at my Busybox Uninstaller which will remove ALL busybox symlinks (over 600 files depending on installers used before):
http://forum.xda-developers.com/showthread.php?t=1853419
Click to expand...
Click to collapse
Fix common issues: You end with both ChainsDD and Chainfire superuser and SuperSU
Also another symptom is having constantly superuser asking for updates from market.
Some people are getting duplicates from previous root methods using ChainsDD superuser instead of Chainfire superSU or vice versa when they come from SuperSU and switch to superuser.
Also, this can happen when you updated let's say to a future Chainfire SuperSU v1.0 and later you use one of my outdated scripts (with version 0.94 for example).
The cause is that I do not delete anything from /data/app. I can add it, it is not an issue, but till these brick things are fixed, I chose not to do it.
The solution is very easy:
Just uninstall from stock application manager all superuser applications. The /system/app application will stay as system applications cannot be removed normally in application manager
After that, just update your superuser application from market. Updates are put in /data/app and original copy will stay in /system/app.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Important notice for people that downloaded previous non touch versions 6.0.1.3 and 6.0.1.4 from post 1
20 Sep 2012: Update non touch version to 6.0.1.4 ** Recommanded Update from previous 6.0.1.4 attached here **
Now, CWM6 is built from source to fix possible issues related to previous dynamically linked binary
Big big thanks to Tallustus from Team SkyFire for the support
Click to expand...
Click to collapse
People using my previous non touch versions 6.0.1.3 and 6.0.1.4 are strongly advised to move to this updated 6.0.1.4
Previous version was not a static binary and could behave unexpectedly under some circumstances
Actual 6.0.1.2 touch and non touch are fine to use
I removed previous 6.0.1.3 and 6.0.1.4 files to avoid confusion
Original thread here:
http://forum.xda-developers.com/showthread.php?t=1746794

[3/31] Fix for KitKat Update Failing - Without ROOTING

WARNING: IF YOU ARE NOT GOING TO START FROM STEP 1 AND FOLLOW EACH STEP EXACTLY HOW I HAVE WROTE IT THEN YOU WILL FAIL. THIS METHOD WORKS IF YOU CAN FOLLOW THE DIRECTIONS.
IF YOU DID NOT RESTORE YOUR PHONE AND FOLLOW EACH STEP EXACTLY HOW I LISTED BELOW THEN DO NOT SAY THIS DOESN'T WORK FOR YOU.
Step 1. Follow @evilpotatoman 's guide below to restore your phone to MJ5 FIRST
Guide:
1) Download and install Heimdall from here for windows. You'll need this and this to avoid missing .dll file errors
2) Download the following files:
MI9_fix.img.ext4
sec_csc.zip
2400258.zip
​Put sec_csc.zip and 2400258.zip on your external SD card
3) Download and install the MJ5 partitions. Use Odin to flash these files (match the file names with the different upload slots)AP_N900AUCUBMJ5.zip​BL_N900AUCUBMJ5.zip​CP_N900AUCUBMJ5.zip​HLTE_USA_ATT_32G.pit​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4) Now is the time to use Heimdall.
Reboot into Download Mode once Odin finishes.
Install the vcredist packages downloaded from step 1.
unzip the heimdall .zip file to c:/
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message
5) Navigate on your computer to c:/Heimdall Suite/ and open heimdall-frontend.exe.
IMPORTANT -- Go to the Utilities tab and click the "Detect" button
Go to the Flash tab on Heimdall, click Browse and select the HLTE_USA_ATT_32G.pit file downloaded from step 3
Click the 'add' button, then next to 'partition name' select system from the dropdown.
click the Browse button underneath the dropdown, and select the MI9_fix.img.ext4 image you downloaded from step 2.
6) Click Start. ***I usually check the 'No Reboot' box to prepare for booting into recovery
7) Heimdall and your Note will report a bad flash at around 95% -- but don't worry -- your system.img got uploaded Reboot directly into recovery mode.
8) Once in recovery, select "Choose update from external" in the recovery, and select the sec_csc.zip you downloaded earlier (did you remember to put that file on your external SD card?). This will install the CSC files and run the preload checkin so you don't FC all over the place
9) IMPORTANT--After flashing the sec_csc, the Note will reboot.
Try to catch it in time to reboot BACK into recovery
Once in recovery, select "Choose update from external" in the recovery, and select the 2400258.zip you downloaded earlier.
END OF MJ5 RESTORE GUIDE - CONTINUE BELOW
Step 2. YOU ARE NOW ON MJ5 BE SURE TO DOWNLOAD AND INSTALL THE NB4 OTA UPDATE BEFORE CONTINUING!!!
Step 3. When you're finished the restore guide to MJ5 and updated to NB4 then delete any other files used from the restore guide so you don't mix them up and download the following 2 files:
1- Miata KitKat Fix v1
2- KitKat Ota Zip​Step 4. Extract the Miata_KK_Fix_1.0.zip to the root of your BOTH your phone storage and your sd card. (make sure they are not in any folders!!!)
Step 5. Once both files in the Miata_KK_Fix_1.0.zip are extracted and copied to both your phone and the sd card... then reboot the phone.
VERY IMPORTANT TO REBOOT NOW
Step 6. Pick one of the follow options...
(Option A) - Wipes phone - I recommend this method
1. Rename 2400258.zip to update.zip and copy to EXTERNAL STORAGE (aka sd card)
UNPLUG USB CABLE BEFORE CONTINUING
2. Reboot into RECOVERY MODE (volume up + home) and select "Apply Update from external storage" and select your update.zip
3. It should start the update process and finish successfully! Enjoy!​
If you made it this far and it fails or gives you an error then you did something wrong. Start from step 1 restoring your phone to MJ5
(Option B) - Doesn't wipe phone
1. You are going to need an ADB Side loader and it can be found here.
2. Extract to directory C:\Mini-SDK
3. Rename 2400258.zip to update. (DO NOT NAME UPDATE.ZIP, JUST "update".)
4. Place "UPDATE" into the same folder as your ADB C:\Mini-SDK
5. Hold shift and right click in the folder to "Open command window here"
6. Reboot your phone into RECOVERY MODE (volume up + home)
7. Select "Apply update from ADB"
8. Plug phone into usb on PC
9. In your command window type "adb sideload update" without quotes and enjoy!​
If you made it this far and it fails or gives you an error then you did something wrong. Start from step 1 restoring your phone to MJ5
(Option C) - Untested
1. Settings, General, About, Software Update, Check for updates...
2. Download and install update​
If you made it this far and it fails or gives you an error then you did something wrong. Start from step 1 restoring your phone to MJ5
Thanks @opsmgr3774 for the donation!
Thanks @Ciberious42 and @evilpotatoman and anyone else I forgot.

Q&A​
1. Is this safe?
Yes it's using the same exploit from Root De La Vega to run a script that replaces the bad file that is stopping the OTA from installing.
What the script does:
Code:
mount -o rw,remount /system
rm /system/bin/mobicore-presetup.sh
cp /sdcard/mobicore-presetup.sh /system/bin
rm /sdcard/rldv.sh
2. It doesn't work for me!!!
Try it again from the very beginning and read step by step, slowly. Make sure you didn't miss anything! Download the files again also.

mazdamiata210 said:
Reserved
Click to expand...
Click to collapse
Im sure people would be a little more willing to try this is there was a little more info here.
What are these files fixing when flashed, how do i know that these good/ok files to flash that will not brick my device? Because you said it should work. Not nit picking or even saying that it doesnt work. BUT more info on what this is would be beneficial to everyone.

the2rrell said:
Im sure people would be a little more willing to try this is there was a little more info here.
What are these files fixing when flashed, how do i know that these good/ok files to flash that will not brick my device? Because you said it should work. Not nit picking or even saying that it doesnt work. BUT more info on what this is would be beneficial to everyone.
Click to expand...
Click to collapse
Well you're not flashing anything that isn't safe considering they're all the same files from different threads (that are safe) except for the script file in the miata fix zip that I made.

mazdamiata210 said:
Well you're not flashing anything that isn't safe considering they're all the same files from different threads (that are safe) except for the script file in the miata fix zip that I made.
Click to expand...
Click to collapse
Yes i understand have used the Evilpotato mans process. I was reffering to the miata Fix. Just want to know what we are flashing. I am not a dev i dont know how to look at a file and see if it will work/harm a phone.

the2rrell said:
Yes i understand have used the Evilpotato mans process. I was reffering to the miata Fix. Just want to know what we are flashing. I am not a dev i dont know how to look at a file and see if it will work/harm a phone.
Click to expand...
Click to collapse
It can't harm anything do not worry. If you followed this guide exactly it will work. Worst case scenario is that you will have to start over again. All it does is copy the missing file back onto the phone so it no longer fails at 27% it's a simple 3 line script you can open it in notepad and see what it's doing if you like.

I hope that posting this is not bad form, as I don't mean to sound skeptical of the OP....
Has anyone tried this method and had success?

TeldenW said:
I hope that posting this is not bad form, as I don't mean to sound skeptical of the OP....
Has anyone tried this method and had success?
Click to expand...
Click to collapse
Yes! Me! Lol it's completely safe

This fix is failing. Error appears that the device is not using NB4 update.

mazdamiata210 said:
It can't harm anything do not worry. If you followed this guide exactly it will work. Worst case scenario is that you will have to start over again. All it does is copy the missing file back onto the phone so it no longer fails at 27% it's a simple 3 line script you can open it in notepad and see what it's doing if you like.
Click to expand...
Click to collapse
thats all that i think most people will need to know just add that to the OP. the more info the better. if it will help people with the update then hey people need to be here testing/using this method.

TheChefSLC said:
This fix is failing. Error appears that the device is not using NB4 update.
Click to expand...
Click to collapse
Whoops I forgot to mention to take the ota update for nb4 before continuing! Sorry I'm running on 0 sleep... Try it again and after the mj5 restore update to nb4... then continue from step 2

mazdamiata210 said:
Whoops I forgot to mention to take the ota update for nb4 before continuing! Sorry I'm running on 0 sleep... Try it again and after the mj5 restore update to nb4... then continue from step 2
Click to expand...
Click to collapse
Indeed
after MJ5 restore, I was able to run the RDLV script in order to replace the system file needed, Then I ran the OTA update from recovery for NB4, Upon reboot, I was then able to install the KK update NC2

TheChefSLC said:
Indeed
after MJ5 restore, I was able to run the RDLV script in order to replace the system file needed, Then I ran the OTA update from recovery for NB4, Upon reboot, I was then able to install the KK update NC2
Click to expand...
Click to collapse
How do you run the script?

opsmgr3774 said:
How do you run the script?
Click to expand...
Click to collapse
It is part of the OP, the RDLV.sh file that you copy to the root of the internal storage. This is a script file that will replace the other .sh file on your system partition.

opsmgr3774 said:
How do you run the script?
Click to expand...
Click to collapse
When you finish the mj5 restore and update to nb4... As long as the miata fix files are on your internal memory and you reboot the script will run

mazdamiata210 said:
When you finish the mj5 restore and update to nb4... As long as the miata fix files are on your internal memory and you reboot the script will run
Click to expand...
Click to collapse
Thank you. I had done everything but the nb4 update and it failed so I of course panicked, then noticed TheChefSLC said they "ran" the script and wondered if I had missed a step. It's all squared away and fully updated now. It worked. Hooray.

This deserves a news page recommendation
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

I am getting a temporary error when trying to download the miata_kitkat fix. new link please
EDIT...It is working now. THanks

I can confirm this works. I just did it and I am now on 4.4.2 NC2. Thanks!!

This worked for me...
But I did have to use "(Option B) - Doesn't wipe phone", Option A did not work.
Now to wait for root...

[D855] [GUIDE] One Click ROOT+TWRP Recovery for Lollipop Stock Firmware [20H/20P/20G]

One Click ROOT+TWRP Recovery for Lollipop Stock Firmware ​-----------------------------------------------------------------------
I recommend you to use AutoRec For Lollipop 20H from @[B]bender_007[/B]
@ingoljosh includes all version of autorec (D855, D852, D850, LS990 ...) in his post : Flash TWRP With AutoRec
​
First use OneClic Script ( by @avicohh ) to root your G3
Then install and use AutoRec to install the recovery custom
-----------------------------------------------------------------------​Only for D855​Only Lollipop (not KitKat)
(16GB/2GB and 32GB/3GB variants)​Use only this tuto in case of failure with the previous quoted method​Credit
- @6ril1 for all his advice and convinced me to publish this method here
- @somboons and his post for the LG G2 : [TOOLS] One Click ROOT+TWRP Recovery for Lollipop Stock Firmware
Somboons have modified One Root Script ROOT KitKat / Lollipop firmware that for One Click ROOT+TWRP D802 firmware 30a/30d and I have updated his work for the LG G3 D855
- @avicohh for his One click script
- @thecubed for Bumps!
- @Unjustified Dev for send_command and his New Root Method for LG Devices
- @Chainfire for SuperSU
- G3 tuto on Frandroid
---------------------------------------------​Download Link for Lollipop 20H:
Mega LGG3-D855-OneClickRootRecoveryV1.1.zip
Box LGG3-D855-OneClickRootRecoveryV1.1.zip
Dropbox LGG3-D855-OneClickRootRecoveryV1.1.zip
md5 : 33c50a727eecc9402ae1551e818b9615
---------------------------------------------
NEW​
Download Link for Lollipop 20P:
Mega LGG3-D855-OneClickRootRecovery-V20P.zip
Dropbox LGG3-D855-OneClickRootRecovery-V20P.zip
md5 : a5f1776215dc6e9792e57efae400dcae
Download Link for Lollipop 20G:
Mega LGG3-D855-OneClickRootRecovery-V20G.zip
Dropbox LGG3-D855-OneClickRootRecovery-V20G.zip
md5 : 624a30b28037a6ed7023ea1f245c2aa8
@6ril1 thank to him for the bump of the 20P and 20G boot :good:
20P and 20G --> If you are not root having applied this tool, copy UPDATE-SuperSU-v2.46.zip on your SDCARD , restart on recovery mode and flash UPDATE-SuperSU-v2.46.zip
For those who used the LGG3-D855-OneClickRootRecoveryV1.1.zip version (for 20H) on the firmware:
- 20P download this file : Kernel fixed by @6ril1 (v20p) --> http://forum.xda-developers.com/showpost.php?p=60770468&postcount=1019
- 20G download this file : Kernel fixed by @6ril1 (v20G) --> http://forum.xda-developers.com/showpost.php?p=60940277&postcount=220
And use Flashify or your custom recovery to install this boot
For more informations see here : http://forum.xda-developers.com/showpost.php?p=60913483&postcount=23
Thank's @black_horse_88
---------------------------------------------​
changelog:
http://forum.xda-developers.com/showpost.php?p=59926518&postcount=91
older version:
Mega LGG3-D855-OneClickRootRecovery.zip
Box LGG3-D855-OneClickRootRecovery.zip
Dropbox LGG3-D855-OneClickRootRecovery.zip
md5 : 9f0dfaa556e33457163cb7d57ebc6b1d
(recovery includes in LGG3-D855-OneClickRootRecovery.zip file: TWRP 2.8.6.1 w. Splash Screens/Modem/F2FS)
Backup Data on SDCARD Before doing everything​
How to install
1 - Install LG drivers if they are not installed yet.
2 - Make sure you are enable USB Debuging Mode . (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3 - Connect your phone to pc on PTP mode
4 - Extract LGG3-D855-OneClickRootRecovery.zip and double click on the OneClick_ROOT_RECOVERY.bat file, to run the script.
5 - Follow the instructions.
If the phone not recognize, try to switch between MTP and PTP options.
Watch the screen of your smarphone you could see this popup asking you to access to the G3
Of course, accept
Your G3 reboot several times.
If you see this message , reboot the G3 manually into Download mode
6 - Enjoy ROOT+TWRP on Lollipop Firmware
7 - Verify if you are root, you have custom recovery and working Download Mode
Problems and solutions
​1 - @somboons describes the manual procedure on his original publication for the LgG2. If you have errors during the script you can try the manual procedure.
somboons said:
Normally If doesn't work for people please checking port that connecting between device and computer or checking LG driver and Re-run script again or use Manual method
What does the automate script do ?
(For people can't use automate script we have to use manually ROOT+TWRP)
Make sure you are enable USB Debuging Mode . See this Method > Enable Debugging Mode
1. Pushing all stuff files
Run file
Command Prompt.bat
Click to expand...
Click to collapse
It will be show command DOS windows
C:\Users\M\Desktop\LGG3-D80230a-OneClickRootRecoveryV1.1>
Click to expand...
Click to collapse
Using command as below to push files to device
adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp/ && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp/
adb.exe push aboot.img /data/local/tmp/aboot.img
adb.exe push laf.img /data/local/tmp/laf.img
adb.exe push boot.img /data/local/tmp/boot.img
adb.exe push recovery.img /data/local/tmp/recovery.img
Click to expand...
Click to collapse
2. Reboot to Download mode
3. When enter to Download mode successfully.We need to send command to connect device with computer
Send_Command.exe \\.\COM_PATH
Click to expand...
Click to collapse
COM_PATH . we can find with ports.bat command
Ex.
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>ports.bat
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>reg query HKLM\hardware\devicemap\SERIALCOMM
HKEY_LOCAL_MACHINE\hardware\devicemap\SERIALCOMM
\Device\LGANDNETMDM0 REG_SZ COM3
\Device\LGANDNETDIAG1 REG_SZ COM4
A command that send to device when connecting to computer with Download Mode is
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>Send_Command.exe \\.\COM4
Click to expand...
Click to collapse
4. When we see this prompt
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>Send_Command.exe \\.\COM4
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#
Click to expand...
Click to collapse
Try to use this command to ROOT+TWRP
# sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
Click to expand...
Click to collapse
5. When we see this message
ui_print - Disabling OTA survival
ui_print - Removing old files
ui_print - Placing files
ui_print - Post-installation script
ui_print - Unmounting /system and /data
ui_print - Done !
Please press Ctrl+C, and then type N and ENTER to reboot.
#
Click to expand...
Click to collapse
Try to use LEAVE command to restart device.
#LEAVE
Click to expand...
Click to collapse
6. Enjoy ROOT+TWRP
Click to expand...
Click to collapse
2- If you always have errors or blockings try this other manual method
1 - Apply this tuto : [GUIDE] New Root Method for LG Devices
2 - Then this one : http://forum.xda-developers.com/showpost.php?p=59931455&postcount=104
3 - If your G3 don't boot on system but you can go on Recovery and Download Mode
Your boot is not correctly flash and we have to make it by line of commands
Tuto here : http://forum.xda-developers.com/showpost.php?p=59962266&postcount=127

Good find, good job m8

Thanks for this solution and for the work done.

Hi, I'm currently rooted on stock lollipop but do not have recovery. Can I run this to give me custom recovery? Cheers

Smowza said:
Hi, I'm currently rooted on stock lollipop but do not have recovery. Can I run this to give me custom recovery? Cheers
Click to expand...
Click to collapse
+1
Sent from my LG-D855 using Tapatalk

Smowza said:
Hi, I'm currently rooted on stock lollipop but do not have recovery. Can I run this to give me custom recovery? Cheers
Click to expand...
Click to collapse
Yes you can
it's the twrp 2.8.6.1 version

Nice work.
Thx for the credit.

Huge Improvement!
HI @jac10000,
This is great! Way better than what I have posted.
I assume that this can be repackaged to cater to other LG G3 variants, by simply replacing aboot.img, laf.img, boot.img (users need to have this "bump'd" prior), and recovery.img (need to be "bump'd" prior as well) from those of their respective LG G3 variants, correct?
EDIT: I have promoted your approach in my how-to thread: http://forum.xda-developers.com/showpost.php?p=59897649&postcount=455

topet2k12001 said:
HI @jac10000,
This is great! Way better than what I have posted.
I assume that this can be repackaged to cater to other LG G3 variants, by simply replacing aboot.img, laf.img, boot.img (users need to have this "bump'd" prior), and recovery.img (need to be "bump'd" prior as well) from those of their respective LG G3 variants, correct?
EDIT: I have promoted your approach in my how-to thread: http://forum.xda-developers.com/showpost.php?p=59897649&postcount=455
Click to expand...
Click to collapse
Yes I think it's possible. I don't know the others models of G3 and their specific characteristics for installing custom recovery

jac10000 said:
Yes I think it's possible. I don't know the others models of G3 and their specific characteristics for installing custom recovery
Click to expand...
Click to collapse
HI @jac10000,
Great to hear.
Based on my experience in the Imageprep thread, installation of custom recovery is the same. I'll go ahead and try it out with my D858HK. Will let you know!

Does it make any difference if I have the LG G3 D855 16GB/2GB variant?
Can anyone report back?

@afilbit It work for 16go/2go and 32go/3go variants

Any other host for the file? Mega is blocked in India :/

@alsiladka Ok I do that , just a moment
https://app.box.com/s/qyquibqpnsh6tiq0kf8a7on2kyelvmf7

jac10000 said:
@alsiladka Ok I do that , just a moment
Click to expand...
Click to collapse
What would I need to provide to make this work on a f460k G3 Cat6? I have not found a bump'd boot.img to start with and don't fully understand how to make one myself.

Works great for my LG G3 D855 16GB. Big thanks! [emoji2]

Has anybody tried it on D855TR Turkish version?

BoredKender said:
What would I need to provide to make this work on a f460k G3 Cat6? I have not found a bump'd boot.img to start with and don't fully understand how to make one myself.
Click to expand...
Click to collapse
I do not know the specific obligations for the f460k. But for the D855 I extracted from kitkat Kdz the aboot.img and laf.img and copy them in the tools folder. I think you must use specific recovery Twrp for the f460k. For the bump boot, I have ever install recovery and bump boot by this method and I use here le boot.img includes in it.

Bump stock lp kernel can be made with linux :
http://forum.xda-developers.com/showthread.php?p=59806620
You need unpackbootimg and mkbootimg bin (you can compile them from source).
For the recovery, open bump in linux or the windows tool made for open bump should do the job

Success
Successfully completed process. TWRP installed and Download mode works. LG Stock OS (V20h-EUR-XX) was rooted before using "No Downgrade" method.
Details of my phone -
LGD855
32GB (European Model),
Software Version: V20h-EUR-XX
Thank you OP! You have just opened a new world for me.

SM-T380/T385 Root?

Is anyone working on rooting this device? I just bought one and it seems to be a really nice tablet, except I'd prefer something other than touchwiz. Although I'd be perfectly happy with just rooting at least.
If there's no one rooting it, could someone help me find the resources to learn how to possibly root this device myself? I'm a beginner with modding android but I pick up things quickly so I'd like to at least give it a shot.

Yesterday I has rooted it via Magisk Manager APK v.5.5.3 & Magisk 15.2.
Procedure:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!

Mefody said:
Yesterday I has rooted it via Magisk Manager APK v.5.5.3 & Magisk 15.2.
Procedure:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
Click to expand...
Click to collapse
Thank you so much! It worked perfectly!
You should post a thread detailing your instructions. Hell, I'll do it if you're too busy

shahmir_k said:
Thank you so much! It worked perfectly!
You should post a thread detailing your instructions. Hell, I'll do it if you're too busy
Click to expand...
Click to collapse
OK! Make this thread, cause I'm working now on TWRP for this tablet.
Please after thread creating place here link to it... :good:

Thank you for the solution
Mefody said:
Yesterday I has rooted it via Magisk Manager APK v.5.5.3 & Magisk 15.2.
Procedure:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
Click to expand...
Click to collapse
Thank you so much. I am a newbie to the whole rooting android thing. I came across this post when trying to root my SM-T385 tab and thought it was too complicated. I tried many other simpler methods and nothing worked. Finally, I took my time figure out your solution and lo-behold it actually works.:good:
I am now a proud owner of a rooted android tablet.

Thank you for the detailed write-up. Just got a new SM-T380 (already on 7.1.1) and would like to have root.
I followed the instructions and got to the Odin Flash part and the tablet came up with "Only official released binaries are allowed to be flashed". Had to hard reset to get it to boot again (w/o root).
Anyone know of a workaround or why didn't work on this one?

crewdog said:
Thank you for the detailed write-up. Just got a new SM-T380 (already on 7.1.1) and would like to have root.
I followed the instructions and got to the Odin Flash part and the tablet came up with "Only official released binaries are allowed to be flashed". Had to hard reset to get it to boot again (w/o root).
Anyone know of a workaround or why didn't work on this one?
Click to expand...
Click to collapse
You should activate "Developer mode" & in developers menu unlock OEM bootloader.

Mefody said:
You should activate "Developer mode" & in developers menu unlock OEM bootloader.
Click to expand...
Click to collapse
Thanks. I don't see "OEM unlock" in the developer now, so think I'm in the penalty box for a week. Bummer.

Mefody said:
You should activate "Developer mode" & in developers menu unlock OEM bootloader.
Click to expand...
Click to collapse
What's the firmware build number?

Im having the same issue, help please?
ashyx said:
What's the firmware build number?
Click to expand...
Click to collapse
My SM-T380 build number is: NMF26X.T380DXU1AQI7
Can't find a way to boot T380 to fastboot mode to run "fastboot oem unlock" unless it can somehow be done with ADB.
Thanks!!!

ashyx said:
What's the firmware build number?
Click to expand...
Click to collapse
I'm on T385XXU1AQJ3-20171116091340 now:
PDA/AP Version - T385XXU1AQJ3
CSC Version - T385OXE1AQJ1
MODEM/CP Version - T385XXU1AQHE
Build Date - 2017-10-30
OS - Nougat 7.1.1
Link to original firmware.
Link to patched "boot.img".
I see, You are guru in TWRP assembling . . .
So here is some sources & technical infos:
Link to kernel OpenSource.
Tablet technical name: gta2slte
Partition sizes from command "dd i= ... o= ..."
BOARD_BOOTIMAGE_PARTITION_SIZE := 33554432
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 33554432
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 3674210304
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053993984
BOARD_CACHEIMAGE_PARTITION_SIZE := 314572800
BOARD_PERSISTIMAGE_PARTITION_SIZE := 33554432

joeyw007 said:
Can't find a way to boot T380 to fastboot mode to run "fastboot oem unlock" unless it can somehow be done with ADB.
Thanks!!!
Click to expand...
Click to collapse
There is no "Fastboot Mode" in this model, like in many other from Sansung, HTC ets. Samsung also insert absolutely bad for ROM-creators KNOX system.
So here is S-shot for OEM is unlocked (and tablet is rooted)... But there no chances for "fastboot"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Under Linux I use Heimdall. Here is screen, where device are detected & ready to be flashed.
One thing about Heimdall... Version from repos didn't work with our device. So we have to compile it from Benjamin-Dobell github where this bug are fixed yet.
Building source is trivial:
Code:
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
make

OEM Unlock Enabled On New Update
I contacted Samsung and spoke with them about the OEM unlock feature missing from developer options and explained I needed to root my table for development purposes for work. They gave me the usual reply of we don't support rooting. I replied I'm not asking you to. I'm asking you to unlock the boot loader on a device I bought, belongs to me and should be allowed to modify as I see fit. I am aware of security and warranty issues please do something about this. Remember Apples DE boggle. A few days later an OTA update puts the feature in my developer options. Coincidence or did they listen? Who knows. I will be trying the root procedure as soon as the new rom downloads and I can get the boot.img from the AP Block. I'll let you guys know how it comes out.

Root Achieved!!! For Cellular South Build T380XAR1AQK3
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
OK with the new update the boot loader can be unlocked from dev options and the above method for rooting is %100 successful. Just make sure to tell Magisk Manager under settings to output patched boot.img to odin mode "img.tar" then just flash the patched_boot.img.tar via the AP slot with Odin.

joeyw007 said:
Who knows. I will be trying the root procedure as soon as the new rom downloads and I can get the boot.img from the AP Block. I'll let you guys know how it comes out.
Click to expand...
Click to collapse
I know at last 3 person with the same situation... Sometimes, when we try to change region of firmware or try to root it out by progs like Kingo, Kingroot & CF-Autoroot it seems to Samsung, that You are dangerous hacker - and it set the 1-week "penalty" mode. So OEM-unblocking became disabled during this penalty period.

Like I said Who Knows, I am Curious...
I am curious if anyone missing the OEM Unlock feature in dev options running build T380DXU1AQI7 before this morning received an OTA update to build number T380XAR1AQK3 with the ability to unlock your bootloader from dev options. I haven't changed regions successfully flashed anything to this tablet and have had it for a month. OEM unlock appeared after OTA update this morning. Now I'm rooted and all is well. Before restarting your tablet if you root this build I would suggest turning OEM Unlocking on again after rooting, as it wipes your tablet, otherwise you will get an error message about not being able to boot unauthorized binaries and have to repeat the process.

Mefody said:
I'm on T385XXU1AQJ3-20171116091340 now:
PDA/AP Version - T385XXU1AQJ3
CSC Version - T385OXE1AQJ1
MODEM/CP Version - T385XXU1AQHE
Build Date - 2017-10-30
OS - Nougat 7.1.1
Link to original firmware.
Link to patched "boot.img".
I see, You are guru in TWRP assembling . . .
So here is some sources & technical infos:
Link to kernel OpenSource.
Tablet technical name: gta2slte
Partition sizes from command "dd i= ... o= ..."
BOARD_BOOTIMAGE_PARTITION_SIZE := 33554432
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 33554432
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 3674210304
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053993984
BOARD_CACHEIMAGE_PARTITION_SIZE := 314572800
BOARD_PERSISTIMAGE_PARTITION_SIZE := 33554432
Click to expand...
Click to collapse
If you could try this build of TWRP out. It's built using the T380 kernel, but should work for the T385 also.
https://androidfilehost.com/?fid=889964283620778312
.

ashyx said:
If you could try this build of TWRP out. It's built using the T380 kernel, but should work for the T385 also.
Click to expand...
Click to collapse
Thanks a lot!!! It works commonly fine!
Two moments:
1. CPU Temperature too high, as for me May be path to termal probe not correct.
2. /data partition are unmount. I think it's due to uncorrect "footer".
I started on github TWRP repo, but I have no enough experience - my build on minimal twrp-7. 1. manifest builds OK, but after flashing I have boot-loop.
Maybe You will kindly find some time to look at this repo: https://github.com/mefody1971/android_device_samsung_gta2slte
Some info regardly temperature & /data partition
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053977600 # 8053993984 - 16384 (footer)
TARGET_USE_CUSTOM_LUN_FILE_PATH := "sys/class/android_usb/android0/f_mass_storage/lun/file"
TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
TW_CUSTOM_CPU_TEMP_PATH := /sys/devices/virtual/thermal/thermal_zone1/temp
In attachment I put recovery.log

Mefody said:
Thanks a lot!!! It works commonly fine!
Two moments:
1. CPU Temperature too high, as for me May be path to termal probe not correct.
2. /data partition are unmount. I think it's due to uncorrect "footer".
I started on github TWRP repo, but I have no enough experience - my build on minimal twrp-7. 1. manifest builds OK, but after flashing I have boot-loop.
Maybe You will kindly find some time to look at this repo: https://github.com/mefody1971/android_device_samsung_gta2slte
Some info regardly temperature & /data partition
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053977600 # 8053993984 - 16384 (footer)
TARGET_USE_CUSTOM_LUN_FILE_PATH := "sys/class/android_usb/android0/f_mass_storage/lun/file"
TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
TW_CUSTOM_CPU_TEMP_PATH := /sys/devices/virtual/thermal/thermal_zone1/temp
In attachment I put recovery.log
Click to expand...
Click to collapse
The errors you are seeing are due to an encrypted data partition. TWRP doesn't support Samsungs encryption method yet.
To mount DATA you need to FORMAT the DATA partition and flash my encryption patch to disable encryption which you can find in my sig.
When I post a proper thread all instructions will be there. For now you can consult any one of my TWRP threads for more info.

ashyx said:
The errors you are seeing are due to an encrypted data partition. TWRP doesn't support Samsungs encryption method yet.
To mount DATA you need to FORMAT the DATA partition and flash my encryption patch to disable encryption which you can find in my sig.
When I post a proper thread all instructions will be there. For now you can consult any one of my TWRP threads for more info.
Click to expand...
Click to collapse
OK! Thanks a lot!!! Will find all available info and try to play with formatting /data partition & setting on Your patch.
Awaiting Your special thread for this device. Anyway - You did a great job :good:

[F3111][Guide][N][33.3.A.1.115] Root with Working patched DRM fix (without ta backup)

Hi all!
Happy to share a workaround for root and successful DRM fix.
If you lose your drm key, that's okay, this fix will restore all function which depends on it (picture quality, super vivid mode, etc.....). There's nothing satisfying than using your phone at its full potential with your own custom. Spot the difference!!!!
1. Unlock bootloader
2. Flash boot.img (Patched to be compatible with the drmfix)
>>> fastboot flash boot boot.img
3. Flash recovery.img
>>> fastboot flash recovery recovery.img
4. Boot to recovery by holding vol - and power; then swipe to allow modification and Format data (mandatory)
5. Flash drmfix.zip
6. Flash Magisk 14.0
7. Boot to android, you're done!!!
Type *#*#7378423#*#* then >>Service info>>Configuration or >>Service tests>>Security to check if all your keys are active.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download link:
# For boot.img here!!!
# For recovery.img here!!!
# For drmfix This does the trick

@pa7taloha Recovery Download link not working for me. Is normal TWRP also okay?
Edit: Nevermind, just saw its for F3311 not for F3111.

F3311? You mean Xperia XA or Xperia E5?

okhayko said:
F3311? You mean Xperia XA or Xperia E5?
Click to expand...
Click to collapse
I mean Xperia xa F3111. OP corrected, Thank you

Hi OP, still not working, all my is are "unknown"

okhayko said:
Hi OP, still not working, all my is are "unknown"
Click to expand...
Click to collapse
That's Strange, can you provide further info, like did you got any error when flashing the drmfix?

pa7taloha said:
That's Strange, can you provide further info, like did you got any error when flashing the drmfix?
Click to expand...
Click to collapse
Unfortunately, it's flashed well, no error.
Before i flash the drmfix, just 2 first lines are [Unknow Error] and the other lines are all [Active], Number or something like that
After i flash the drmfix, all of them are [Unknow Error]

okhayko said:
Unfortunately, it's flashed well, no error.
Before i flash the drmfix, just 2 first lines are [Unknow Error] and the other lines are all [Active], Number or something like that
After i flash the drmfix, all of them are [Unknow Error]
Click to expand...
Click to collapse
That means the drmfix you've flashed has deleted your credential which is located at /data/credmgr/ . For sure the linked drmfix here will not delete anything in your system.
Note: This drmfix will not be compatible with another boot.img different from the O.P. You have to do some mod in your boot.img to make this working. If you want to, let me know.

pa7taloha said:
That means the drmfix you've flashed has deleted your credential which is located at /data/credmgr/ . For sure the linked drmfix here will not delete anything in your system.
Note: This drmfix will not be compatible with another boot.img different from the O.P. You have to do some mod in your boot.img to make this working. If you want to, let me know.
Click to expand...
Click to collapse
Hi, can i ask a question?
My model is F3116, can i do step by step with this guide to make it work?
Sorry but i did not flash your boot.img file, i flashed boot.img file from the other thread, i though it the same. i will try your method but can you answer me that this will work with my model TY!

okhayko said:
Hi, can i ask a question?
My model is F3116, can i do step by step with this guide to make it work?
Sorry but i did not flash your boot.img file, i flashed boot.img file from the other thread, i though it the same. i will try your method but can you answer me that this will work with my model TY!
Click to expand...
Click to collapse
Post here your boot.img then, I will try to mod it. But make sure you still have your credmgr.db file which is located at /data/credmgr, this Fix won't work without it.

pa7taloha said:
Post here your boot.img then, I will try to mod it. But make sure you still have your credmgr.db file which is located at /data/credmgr, this Fix won't work without it.
Click to expand...
Click to collapse
Thanks buddy. Here is my boot.img that i was flash
boot.img file

For F3116 [33.3.A.1.97]
okhayko said:
Thanks buddy. Here is my boot.img that i was flash
boot.img file
Click to expand...
Click to collapse
Now
1. flash this bootF3116.img file, using the command "fastboot flash boot bootF3116.img" (without quotes)
2. Go to twrp recovery and "format data" (I suppose you already have flashed twrp)
3. Flash drmfix.zip
4. Flash Magisk if you need root.
5. Reboot
Download link
bootF3116.img
The compatible drmfix.zip
If you still have any problem let me know

Hi,
i had a F3112, is the DRM fix compatible ?
thanks

bobladure said:
Hi,
i had a F3112, is the DRM fix compatible ?
thanks
Click to expand...
Click to collapse
Hi, F3112 and F3116 has the same boot.img file so you can try to flash the boot.img, and drmfix.zip above your post and post your feedback here

Hi @pa7taloha,
Can you share your kernel drm fix changes (github or some other cloud server)? I'm trying to implement some custom changes in the kernel and I could add this as well. Thanks.

cojocar.andrei said:
Hi @pa7taloha,
Can you share your kernel drm fix changes (github or some other cloud server)? I'm trying to implement some custom changes in the kernel and I could add this as well. Thanks.
Click to expand...
Click to collapse
Sorry for late reply.
I will try to be clear as much as I can(bad english speaker).
We have tested this workaround to: xperia xa f3111(Mediatek, Nougat) and xperia x perfomance(qualcom, Nougat and 0reo) and it work fine in Nougat and Oreo too. I hope this will work too to the other xperia devices, so we can relate it.
I did not compile kernel from source, I have just extracted it with flashtool kernel.elf and unpacked/repacked it with AIK Linux/Carliv-image-kitchen. I am a Linux user.
For mediatek processor,
In the kernel, unpack it and edit.
1. disable dm-verity
2. edit init.rc
add this red line in on early-init, .
Code:
on early-init
[COLOR="Red"]restorecon /vendor/lib64/libdrmfix.so
restorecon /vendor/lib/libdrmfix.so[/COLOR]
# Set init and its forked children's oom_adj.
write /proc/1/oom_score_adj -1000
# Disable sysrq from keyboard
write /proc/sys/kernel/sysrq 0
3. edit init.aee.rc
add this red line in on init
Code:
on init
export LD_PRELOAD libdirect-coredump.so
write /proc/self/coredump_filter 39
setprop ro.aee.enperf off
[COLOR="Red"]export LD_PRELOAD libdrmfix.so[/COLOR]
4. edit default.prop
change the value of "ro.secure=0" to "ro.secure=1"
7. Open "fstab.mt6755" and copy in new text file the path to your system, it should be in the first line, we will use this later in the drmfix.zip
6. repack your kernel
II. We will do some mod to the drmfix.zip
open with the "open archive manager" the drmfix.zip and edit the updater-script in drmfix/META-INF/com/google/android/
This red line in the updater-script should be the same path to your system found in "fstab.mt6755" file in the boot.img (you've copied in step 5 in kernel)
Code:
ui_print(" ==================================");
mount("ext4", "EMMC", "[COLOR="red"]/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system[/COLOR]", "/system");
ui_print("updating..");
package_extract_dir("system", "/system");
unmount("/system");
ui_print("Done!!!");
save it and update the drmfix.zip
For Qualcom processor
In the kernel, unpack it and edit.
1. disable dm-verity
2. edit init.rc
add this red line in on early-init
Code:
on early-init
[COLOR="red"]restorecon /vendor/lib64/libdrmfix.so
restorecon /vendor/lib/libdrmfix.so[/COLOR]
# Set init and its forked children's oom_adj.
write /proc/1/oom_score_adj -1000
# Disable sysrq from keyboard
write /proc/sys/kernel/sysrq 0
3. edit init.environ.rc
add this red line to the last line.
Code:
export SYSTEMSERVERCLASSPATH /system/framework/services.jar:/system/framework/ethernet-service.jar:/system/framework/wifi-service.jar
[COLOR="red"]export LD_PRELOAD libdrmfix.so[/COLOR]
4. edit default.prop
change the value of "ro.secure=0" to "ro.secure=1"
5. Open "fstab.qcom" and copy in new text file the path to your system, we will use this later in the drmfix.zip
6. repack your kernel, flash it
II. We will do some mod to the drmfix.zip
open with the "open archive manager" the drmfix.zip and edit the updater-script in drmfix/META-INF/com/google/android/
This red line in the updater-script should be the same path to your system found in "fstab.qcom" file in the boot.img (you've copied in step 5 in kernel)
Code:
ui_print(" ==================================");
mount("ext4", "EMMC", "[COLOR="red"]/dev/block/bootdevice/by-name/system[/COLOR]", "/system");
ui_print("updating..");
package_extract_dir("system", "/system");
unmount("/system");
ui_print("Done!!!");
save it and update the drmfix.zip, and flash it.
Avalaible for clarification.

https://imgur.com/OHuNKyk
Guys I can't seem to get it to work, tried reflashing your boot.img and recovery.img, tried formatting data and factory reset after every flash and wipe cache/dalvik cache after drm.zip install, nothing seems to get rid of those "Unknown error", btw I'm using F3111 single SIM on 33.3.A.1.97.
Almost forgot, when i plug my phone in fastboot and flash the files i don't get that flash status on the phone itself, only on cmd screen that it's done.

matan290 said:
https://imgur.com/OHuNKyk
Guys I can't seem to get it to work, tried reflashing your boot.img and recovery.img, tried formatting data and factory reset after every flash and wipe cache/dalvik cache after drm.zip install, nothing seems to get rid of those "Unknown error", btw I'm using F3111 single SIM on 33.3.A.1.97.
Almost forgot, when i plug my phone in fastboot and flash the files i don't get that flash status on the phone itself, only on cmd screen that it's done.
Click to expand...
Click to collapse
Sorry to hear that, It is always recommended to do a full nandroid backup before flashing anything. To get rid of those Unknown error you have to reflash your firmware. What causes these error is that the drm.zip you've flashed has deleted the credmgr.db file in /data/credmgr/, this contains all your phone credential. May be you've flashed any drmfix(old drmfix in other thread) before flashing this, because this fix will not delete anything in your system. And no need to wipe cache/dalvik after flashing it.

Yeah that's the problem,cause i flashed the other DRM fix few weeks ago. Can you please post a link or something for a firmware I can flash or should I try the PC Companion.

matan290 said:
Yeah that's the problem,cause i flashed the other DRM fix few weeks ago. Can you please post a link or something for a firmware I can flash or should I try the PC Companion.
Click to expand...
Click to collapse
You can use flashtool and download a frimware the latest version by xperifirm which is integrated in the flashtool. Or if you want to use Pc Companion you have to relock your bootloader and unlock after it's done.