Database Info

The Lenovo A706 Owners' Thread (Root/CWM/Other Discussions)

The Lenovo A706 Owners' Thread (for Rooting, CWM, and other discussions)
Official Product Page
{
"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"
}
---------------------------------------------------------------------------------------------------------------
Device Specs:
---------------------------------------------------------------------------------------------------------------
SIM Type: Dual Mini-SIM
Band Coverage: GSM 900/1800/1900 MHz (Asia-Pacific)
GSM 850/1800/1900 MHz (Latin America)
WCDMA 900/2100 MHz (Asia-Pacific)
WCDMA 850/1900 MHz (Latin America)
WLAN: 802.11 a/b/g/n with hotspot capability
Display: 4.5" IPS (Can anyone confirm if it has Gorilla Glass?)
Resolution: 480 x 854
Navigation: 5-point capacitive touch
Processor: Quad-Core Qualcomm MSM 8225Q 1.2GHz
OS: Android™ 4.1 Jelly Bean with LenovoMagic UI
Memory: 1GB RAM
Storage: 4GB Internal Storage (eMMC) with memory card slot
Battery: 2000mAh Lithium Polymer user-replaceable
Dimensions: 136 x 69 x 10.4 mm
Weight: 130g
Sensors: A-GPS, Gravitation, Ambient light sensor, Proximity sensor
Camera: Front: 0.3MP fixed-focus, Rear: 5MP auto-focus
FM Radio: Yes
Color: White
---------------------------------------------------------------------------------------------------------------
This is a good budget device when compared to other devices from lead manufacturers like Samsung, Sony, LG or Huawei.
While searching on the internet I did find some Root & CWM installation methods.
I will be updating the relevant posts as and when needed.
You can look in the list below for what you want to do with your device.
ATTENTION!!! READ THIS BEFORE DOING ANYTHING
---------------------------------------------------------------------------------
Friend, there are two versions of this device in the market:
1. A706 (Chinese model)
2. A706_ROW (International Model)
The ROMs in this thread are only for the A706ROW model of this phone unless otherwise stated.
If you have the chinese model or another model A760 (which is a different model) then the ROMs in this thread are not for you.
Model A706 and A760 are two different models with almost same specifications. This DOES NOT mean that the ROMs of A706ROW are compatible with A760.
Please DO NOT confuse Lenovo A706 with Lenovo A760 as these are two different devices!!! Flash or experiment at your own risk!!!!
If you share a ROM link for any of the above devices, then please mention clearly the device for which the ROM can be used.
What to do with your Device ?
-------------------------------------------
DISCLAIMER:
---------------------
Rooting your device VOIDS your warranty. Remember if you are doing this, it is at your own sole responsibility
and I cannot be held responsible for any damage to your device, data loss, or any personal injury as a result of your actions.
And, If you still feel it is worth the effort, proceed with caution!
FOR NOOBS
--------------------
Read the instructions (click on SHOW to read) before attempting anything from the list below!
First you need to have the Android SDK installed on your computer. Or atleast you need to have the adb & fastboot files available on your computer.
Here's a good post that tells you how to setup ADB and fastboot.
Here's a post that has a list of adb/shell commands for noobs.
Ok, once you are done with the setup of ADB & fastboot on your computer, then you can proceed with the below instructions.
--------------------
IMPORTANT NOTE BEFORE FLASHING:
-------------------------------------------------------------
Recently, I have noticed that many people after buying the phone are flashing any firmware to their phones and most of the time without checking the phone versions and the OS versions. In the stock firmware post, I had mentioned that people having the Chinese version of the phone should NOT flash the ROW (international) firmware otherwise it would mess up their phone and network etc.
SOLUTION FOR SIM ERROR & DOWNGRADING TO CHINESE ROM
-----------------------------------------------------------------------------------------------------
Now, some of the people have already done such a mistake and for those people (who are having SIM or network problems and want to go back to chinese ROM, I am sticking this post by danyno1 to the OP:
(Click SHOW to See the quoted post)
----------------------
danyno1 said:
hi
I've just installed the "A706ROW_1_S_2_001_0020_130821 MegaFull"" rom , and now i have no network coverage, it doesnt recognize my simcards
I live in Iran.
what should i do??
is there any way to unlock it ??
please help me with this situation , i'm in a hurry
------------------------------------------
after reading the whole topic posts, and testing all the methods , the problem is solved [thanks to mixbox360's posts.] i'm going to just copy and paste his 2 separated posts.
BEST soloutions for these 2 common problems :
#1 device doesnt recognize simcards
#2 being unable to downgrade to the chinees stock rom
soloution of the #1 problem :
how I fixed: Just Installed the QNeonModern 1.7 ROM... then I installed the update of a chinese ROM from bootdroid (I mean putt the update.qsb file un the sdfuse directory o my sd card, then power and vol+ to enter the menu and selected SD UPDATE)... thats all... I have again my chinese rom with signal for calls untill we discover how to make work the athk board in the ROW roms.
Hope to be helpfull!
Click to expand...
Click to collapse
soloution for #2 problem:
Ok trying again to put my chinese device in ROW rom with sim signal, and found a solution:
1:Flash via droidboot a chinese stock firmware I used the 130325
2:Rooted device with vroot and installed CWM Recovery via ADB
3:In the procedure to install custom rom Qneon one of the steps is to flash boot.img via fastboot... well I just didn´t do this step and flashed directly Qneon_1.7.1.zip via CWM
4: Did data/factory reset, cache reset and dalvik cache reset
5:Reboot system
An Ready! Finally got my chinese device in spanish and sim signal.
Click to expand...
Click to collapse
ENJOY THE DUAL SIM ANTENNA + ROM WITH MULTIPLE LANGUAGES
CREDITS : mixbox360
Click to expand...
Click to collapse
------------------------------------------
For Installing CWM: Go to Post #2
For Rooting: Go to Post #3
For Stock ROMs: Go to post #4
For Custom ROMs: Go to post #5
Credits:
-------------
- Lenovo for making a surprisingly good budget phone
- And users for buying it!
Enjoy your phone and share your thoughts and helpful insights/useful methods with all other users here so that they can benefit from your research.

CWM Installation Instructions:
-------------------------------------------
Make sure you have all the drivers for your phone installed on your computer. Download for A706 from here. Some other Qualcomm drivers (not sure if required)
Make sure you have USB Debugging enabled, Install from Unknown Sources is enabled and device is detected in ADB run this command:
Code:
adb devices
Download the CWM Recovery for A706 from here.
Unzip the downloaded file to get a "recovery.img" recovery image file.
Press SHIFT key + Right mouse click in the folder where the file is located and select Open Command from Here.
Now, in the command prompt do the following:
a. Reboot into Bootloader mode. Use command:
Code:
adb reboot bootloader
b. Device will reboot and display Lenovo logo. (check if device is in bootloader mode by running command:
Code:
fastboot devices
. If you see a device connected then you have successfully rebooted into fastboot mode.
c. Now, run this command:
Code:
fastboot flash recovery recovery.img
(This will flash the CWM recovery image to the device).
d. Once successful, reboot the device using this command:
Code:
fastboot reboot
. Or, you can keep the power+vol up+ vol down buttons pressed to restart.​
If everything has gone well, this should get CWM installed on your device. Your device is still *not rooted*. Once you have installed CWM, please proceed to the ROOT instructions post to *root* your device.
CREDITS:
---------------
This post (in Vietnamese)
This post for Recovery (in Russian)
This post for Drivers links (in Russian)
And, to all the other great Russian/Chinese forums and sites who have such vast info on Lenovo which we need in English

DISCLAIMER: Rooting your device VOIDS your warranty. Proceed with caution!!!
1. CWM ROOT METHOD
-------------------------------------
Ok, so you have successfully installed CWM and need root.
1. Just download this Root for A706 ( CWM flashable zip file)
2. Reboot phone to CWM Recovery (use command: adb reboot recovery)
3. Flash the zip and then restart into OS.
4. Now, you should get the Super user app in the list.
2. VROOT (ONE-CLICK ROOTING) METHOD
------------------------------------------------------------------
For noobs AND people who either don't want to install CWM or are unsure of it's usage and only want root, can use this guide for VROOT one-click rooting method. The guide has been translated and posted on XDA by zhuhang. The original vroot post/method (in chinese) exists on this site.
CREDITS:
---------------
Same as in the CWM post above.
Thanks to zhuhang for posting the VROOT guide in english (translated from chinese).

DISCLAIMER: Follow these instructions at your OWN risk & responsibility. They are provided AS-IS without any liability.
IMPORTANT NOTE BEFORE FLASHING:
-------------------------------------------------------------
Recently, I have noticed that many people after buying the phone are flashing any firmware to their phones and most of the time without checking the phone versions and the OS versions. In the stock firmware post, I had mentioned that people having the Chinese version of the phone should NOT flash the ROW (international) firmware otherwise it would mess up their phone and network etc.
Solution to the problem is now in the OP. Please follow it if you have SIM error or network issue.
STOCK ROM
--------------------
I am posting a list of stock firmware(s) that I can find for the A706 here, along with instructions on how to install it.
FIRMWARE LIST
-------------------------
Build Number: A706_ROW_S018:
Details:
Firmware Type: Official Release
Languages: English, Russian, Chinese, Indonesian & Vietnamese
Build Date: 15/07/2013
OS: Android 4.1.2 with Lenovo Magic UI
Download Link: Get it from here (Lenovo-Forums.ru)
(You need to click on the green button on the page. Once you click there then you need to register and logged in, to download it.)
CREDIT: This post in Russian.​
This post by 5[Strogino] has a list of stock firmwares and links to download them.
INSTRUCTIONS
-----------------------
A memory card is required.
Boot into Android normally.
Connect your phone to your PC/Laptop with a USB cable and when asked (or in USB connection settings), please select USB Mass storage mode to mount SD card.
On the root of the memory card, create a folder called "sdfuse".
Unzip the downloaded firmware, you will get a QSB file.
Copy the QSB file to the sdfuse folder that we created earlier on the root of SD card.
Note: Please make sure that your phone has atleast 60% power before attempting or beginning upgrade. Or keep charger connected during the process.
SD card upgrade process:
Long press VOL UP + POWER_KEY to enter the droidboot,
A menu will appear. Select the fourth option, SDUPDATE.
At the bottom of the screen, you can see the progress and status of the update
When you see the message "SDCARD UPDATE SUCCESS!!!", this means you successfully completed the upgrade process
Now, reboot your device and hopefully it should be updated.
That's it! If you guys have found any more firmware download links (even for different regions, build etc.) just share them with me along with details and I will add them to the list in this post.
CREDIT: Instructions were taken from this post and formatted and edited for better understanding.

A List of Custom ROMs
------------------------------------
QNeon-Modern ROM (based on Russian Firmware but has English too): Visit the original thread (in Russian)
Please do share more ROMs with me so that I can include them in this list.

help!
hello bro! i got stuck at installing the cwm flashable file. it's saying "Verifying update package.... Installation aborted"

gr8techie said:
RESERVED (for a list of Stock ROMs/Stock ROM installation)
Click to expand...
Click to collapse
Thanks,
Very nice thread. Had the phone for a month but no support anywhere. i need the stock rom, if u have pls pm me.
thanks again

scuderialoki said:
hello bro! i got stuck at installing the cwm flashable file. it's saying "Verifying update package.... Installation aborted"
Click to expand...
Click to collapse
scuderialoki, unfortunate that you got stuck. worked for me without any issues. i upped the same file that i used on mediafire. can you re-download the file and then check if the file is ok by extracting the zip using winrar or winzip? if it is ok then try flashing it again.
guliboy123 said:
Thanks,
Very nice thread. Had the phone for a month but no support anywhere. i need the stock rom, if u have pls pm me.
thanks again
Click to expand...
Click to collapse
guliboy123, i will be putting the link and some instructions on the stock rom post soon. bear with me as i have to check the instructions from the russian/chinese sites and then put it up here. in the meantime, i suggest you take a backup of your current ROM (which is stock) using CWM and then try out the QNeon-Modern ROM. remember u need to flash that ROM using CWM.

thanks
scuderialoki, unfortunate that you got stuck. worked for me without any issues. i upped the same file that i used on mediafire. can you re-download the file and then check if the file is ok by extracting the zip using winrar or winzip? if it is ok then try flashing it again.
Click to expand...
Click to collapse
gr8techie thanks for the reply. i really appreciate it. just downloaded the flashable cwm however it's still the same bro. lemme tell you something though. i rooted the devices before using framaroot and everything is ok but i had to do a factory reset through the settings app in A706. i still see the superuser app in the system apps and i cant uninstall it. when i open the superuser app in the drawer it's giving me an error that the su binary is not installed and su cant install it.

scuderialoki said:
gr8techie thanks for the reply. i really appreciate it. just downloaded the flashable cwm however it's still the same bro. lemme tell you something though. i rooted the devices before using framaroot and everything is ok but i had to do a factory reset through the settings app in A706. i still see the superuser app in the system apps and i cant uninstall it. when i open the superuser app in the drawer it's giving me an error that the su binary is not installed and su cant install it.
Click to expand...
Click to collapse
ok, please tell me if you have CWM installed on your device? I believe it is not installed. if this is the case, then you need to flash CWM and then try installing the zip again.
if it is installed then, i believe the super su from previous rooting maybe causing the problem. check on Playstore for a method to unroot your device. or google it. then you need to root again. hope this solves your problem.

thanks
Hi bro thanks for the reply i attached a screenshot of my root validation. I used an app to identify that. And by the way my recovery is installed. I the super su app is killing it

New page for our devices :good:
I had rooted my Lenovo A706 before You made this page You are faster than me , bro :laugh::laugh:
Hope our A706 will have more ROM, Init , Kernel that make it better

Some picture of mine, they are old ones..I am cooking some new thing on A706...:laugh: hope you like

Anyone know how to switch between few apps on lenovo A706?
long press on home button will only show the google now
Changing input method when typing also an issues i met,
anyway to change the input method when typing?

Can someone upload an official updated rom (ROW) for lenovo a706? It'll be much appreciated.

FREE CALLING SERVICE PROBLEM
guys,, may be you can help me... the problem is i can hear what other people are saying in LINE / Skype /Viber but people can't hear anything i said.

Goog, I want it
Sent from my Lenovo A706 using xda premium

silv3rmoon said:
Anyone know how to switch between few apps on lenovo A706?
long press on home button will only show the google now
Changing input method when typing also an issues i met,
anyway to change the input method when typing?
Click to expand...
Click to collapse
Long press in menu button ^^
---------- Post added at 08:20 PM ---------- Previous post was at 08:18 PM ----------
rapnix said:
FREE CALLING SERVICE PROBLEM
guys,, may be you can help me... the problem is i can hear what other people are saying in LINE / Skype /Viber but people can't hear anything i said.
Click to expand...
Click to collapse
just viber bro...because maybe viber isn't usable for us now..i can use skype , line , zalo and every things else nomarly

@trithong.. bro. also in LINE and TALKRAY i encounter this problem some of us already encounter this problem what version do you have? i have A706ROW.. no problem if only chatting but if i want to use calling features that's were i encounter this kind of problem i can here them but they cannot here me

my A706 can't root.
CWM show Installation abort!
Baseband ver
A706ROW_1_A_2_0046_130604
Internal ver
A706ROW_1_S_2_001_0018_130705

[SC-01F/SCL22] Galaxy Note 3 (Japanese) (NTT Docomo) (au KDDI)

[SC-01F] Galaxy Note 3 (Japanese) (NTT Docomo)
Rooting information is in the second post.
Debloating and tweaking information is in the third post.
Available Firmwares:
Android 4.3 (SC01FOMUBMIF) - original firmware
Android 4.3 (SC01FOMUBNA8) - released on 2014/02/12 - patch notes
Android 4.3 (SC01FOMUBNB3) - released on 2014/03/04
Android 4.3 (SC01FOMUBNC3) - released on 2014/03/31
Android 4.4.2 (SC01FOMUBNF6) - released on 2014/07/08 patch notes
Android 4.4.2 (SC01FOMUBNI3) - released on 2014/10/16
Android 5.0 (SC01FOMUGOI4) - released on 2015/10/05 - patch notes
Download firmwares here.
Latest patch notes.
[SCL22] Galaxy Note 3 (Japanese) (au KDDI)
Original and rooted firmwares are available from Dev-Host.
Rooting information is in the second post.
Available Firmwares:
Android 4.3 (SCL22KDUBML1) - original firmware - patch notes
Android 4.3 (SCL22KDUBNB1) - released on 2014/03/04 - patch notes
Android 4.3 (SCL22KDUBND3) - released on 2014/05/15 - patch notes
Android 4.4.2 (SCL22KDU2FNF7) - released on 2014/07/09 - patch notes
Android 5.0 (SCL22KDU2GOH7) - released on 2014/09/01 - patch notes
Download firmwares here.

Rooting Information
This root method shows custom status, but FeliCa works.
Instructions - Device Rooting
There are guides on xda on how to do every step, so please don't ask how to do any particular step in this post.
If you can't get the Download Mode to show Samsung Official, keep reflashing the recovery image and rebooting. It may take a few tries.
If it doesn't work. Try making a tar file with the official recovery.img in. Guide here.
You must install the cwm in the last step using the dd command. You can't use Odin or it will disable NFC again.
Download these things:
The latest KitKat firnware (link in the first post)
The KitKat CWM recovery (attached)
Odin and Samsung Mobile Drivers
SuperSU CWM Installer
7zip
Extract the firmware so you have a tar.md5 file.
If you don't have KitKat yet, do this:
Reboot to download mode
Run Odin press AP and select the firmware tar.md5
Press Start and wait 5 minutes for your firmware to update
Reboot to download mode
Run Odin press AP and select your recovery tar file
Press Start and wait for the reboot.
Copy the SuperSU insstaller zip to your sdcard.
Reboot to recovery mode.
Install SuperSU by selecting the zip.
Reboot.
Install BusyBox Installer.
Install BusyBox. If it doesn't work, you don't have root.
Install Android Terminal Emulator
Extract recovery.img from the firmware tar.md5
Copy to /sdcard
Run this command (you can copy/paste it):
su
dd if=/sdcard/recovery.img of=dev/block/platform/msm_sdcc.1/by-name/recovery​
Reboot the phone, reboot into recovery, then reboot into download mode, check that it says "Current binary: Samsung Official"
Repeat these 3 reboots until it shows official. (NFC will work then)
Extract the recovery.img from your recovery tar file to /sdcard
Run this command (you can copy/paste it):
su
dd if=/sdcard/recovery.img of=dev/block/platform/msm_sdcc.1/by-name/recovery​Reboot to recovery to test that it installed.
You should now be rooted with NFC and custom recovery.
Notes:
To get to download mode: hold power+home+vol down, while the phone reboots, then at the screen with Japanese text, press vol up.
To get to recovery mode: hold power+home+vol up, while the phone rebootsp.
When using Odin, ensure re-partition is unchecked.​
Instructions - TWRP
You can find an alternate recovery in this post.​
Instructions - Install Xposed
Follow the rooting instructions above.
Install the Xposed Installer.
Open Xposed Installer, click Framework, click Install, reboot.
Recommended Modules:
Wanam Xposed​
Instructions - Enable Bluetooth Tethering
Follow the rooting instructions above.
Follow the Xposed Installation instructions above.
Install the Xposed-Bluetooth-Tethering-Enabler module.
Open Xposed Installer, clock Modules, enable Xposed-Bluetooth-Tethering-Enabler, reboot.

Lollipop Deodex Rom
I have created a deodexed Lollipop rom for the SC-01F.
It is pre-rooted, deodexed and Busybox is installed.
You don't have to wipe and you can go back to stock easily.
NFC is working.
Please download all the files in the SC-01F folder.
Guide: (This will trip knox)
Download all the files in the SC-01F folder.
Copy "SC-01F_Part2_System.zip" to your phone's SD card.
Optional: Copy "XposedInstaller_3.0_alpha4.apk" and "xposed-v75-sdk21-arm-arter97-snapdragon_requestConcurrentGC.zip" too if you want Xposed Framework.
Reboot your phone into download mode and connect the USB cable.
Extract "Odin3_v3.10.7.zip" and run the program.
Press the "AP" button and select "SC-01F_Part1.tar"
Reboot into recovery mode.
Flash the "SC-01F_Part2_System.zip" from the SD card.
Optional: Flash "xposed-v75-sdk21-arm-arter97-snapdragon_requestConcurrentGC.zip" if you want Xposed.
Optional: Skip this step if you prefer a custom recovery over NFC.
Reboot to download mode. Flash "SC-01F_Part3_OfficialRecovery.tar"
Repeat this step until download mode shows official binary.
You may have to pull the battery and cable mid flash to trigger the official check.
You won't brick your phone from a bad recovery.img flash.
Done.

I'm a SEA Note 3 SM-N9005 user. Is there any way I can use Japanese language pack from DoCoMo version? I just switched from Xperia Z and noticed the missing language.

what are the supported bandwidth of the SC-02C model?
hmm... according to this
Code:
連続待受時間注意1注意2
（静止時） 3G：約 470時間／LTE：約 410時間／GSM：約 380時間注意6注意7
連続通話時間注意2
（音声通話時） 3G：約 1000分／GSM：約 860分
seems like only Japan frequencies

SimmoF,
Are you upgrading from the Note 2 (SC-02E)?
I still have a year to go on the SC-02E contract, I wonder if NTT Docomo offer an upgrade path?

Fulvian said:
I'm a SEA Note 3 SM-N9005 user. Is there any way I can use Japanese language pack from DoCoMo version? I just switched from Xperia Z and noticed the missing language.
Click to expand...
Click to collapse
I don't think its possible, without a huge amount of effort.
Sent from my L-06C using Tapatalk 4

AllGamer said:
what are the supported bandwidth of the SC-02C model?
hmm... according to this
Code:
連続待受時間注意1注意2
（静止時） 3G：約 470時間／LTE：約 410時間／GSM：約 380時間注意6注意7
連続通話時間注意2
（音声通話時） 3G：約 1000分／GSM：約 860分
seems like only Japan frequencies
Click to expand...
Click to collapse
SC-02C is the Galaxy S2. Did you mean SC-01F?
Docomo uses its own frequencies, but their devices support a few standard frequencies when roaming, but you won't get to full speed.
Sent from my L-06C using Tapatalk 4

Grant Barker said:
SimmoF,
Are you upgrading from the Note 2 (SC-02E)?
I still have a year to go on the SC-02E contract, I wonder if NTT Docomo offer an upgrade path?
Click to expand...
Click to collapse
I'm upgrading from the Galaxy S2.
I wouldn't upgrade, the way Docomo subsidize is by giving you a discount off your bill, every month, for 2 years. This works out to about 44000yen, if you stick the 2 years out.
Also differences aren't that great between the note 2 and 3, and they'll likely filter all the new touchwiz features into the new note 2 firmware.
Sent from my L-06C using Tapatalk 4

SimmoF said:
I'm upgrading from the Galaxy S2.
I wouldn't upgrade, the way Docomo subsidize is by giving you a discount off your bill, every month, for 2 years. This works out to about 44000yen, if you stick the 2 years out.
Also differences aren't that great between the note 2 and 3, and they'll likely filter all the new touchwiz features into the new note 2 firmware.
Sent from my L-06C using Tapatalk 4
Click to expand...
Click to collapse
Yeah. Cheers. I'll be sticking with the Note 2 which I'm very happy with.

I just upgraded from my American Note 2 (Verizon) I was using with a Docomo SIM. I'm loving it so far, but I know it could be much better if I had root (to remove bloatware, change a few things, add a few things, etc). I will post links in here if I confirm root methods and recoveries that work with this device.
Sent from my SC-01F using xda app-developers app

gaxiolafm said:
I just upgraded from my American Note 2 (Verizon) I was using with a Docomo SIM. I'm loving it so far, but I know it could be much better if I had root (to remove bloatware, change a few things, add a few things, etc). I will post links in here if I confirm root methods and recoveries that work with this device.
Sent from my SC-01F using xda app-developers app
Click to expand...
Click to collapse
Great. So the De la Vega method requires the firmware dump to be available for the hacker to make it for our firmware.
So I wouldn't use that until one is available for our device. I will tell him as soon as I can.

SimmoF said:
Note: Do NOT do any updates until we know how to root this thing. Updating may block your chances of rooting.
Edit: I just saw that the Root de la Vega requires a custom version for our AP and CSC, so I will go down to the Docomo shop today and get the details, and request a custom root for us. I will post the details here when done.
Click to expand...
Click to collapse
I will be watching this page constantly waiting for an update! I just picked up my note an hour ago. Thanks for making the effort!

AllGamer said:
hmm... according to this
Code:
連続待受時間注意1注意2
（静止時） 3G：約 470時間／LTE：約 410時間／GSM：約 380時間注意6注意7
連続通話時間注意2
（音声通話時） 3G：約 1000分／GSM：約 860分
seems like only Japan frequencies
Click to expand...
Click to collapse
What you are quoting here are not frequencies, but standby and talk time ratings.
Standby 470 hours on 3G and so on.
Talk time 1000 minutes on 3G and so on.
But it seems that you are right about the fequencies either way.
look here: http://www.samsung.com/jp/consumer/mobilephone/galaxy-note/docomo/SM-N900DZKEDCM-spec

SimmoF said:
Hello everyone,
Some of you may know me for my work in the SC-02C thread.
I am starting this device thread for the users of the Japanese Galaxy Note 3.
I intend to pick up one of these on release day, October 17, so I'll post as much advice and information as I can about rooting/modding.
I will try rooting using the Root de la Vega method, as soon as I get the device.
Note: Do NOT do any updates until we know how to root this thing. Updating may block your chances of rooting.
Edit: I just saw that the Root de la Vega requires a custom version for our AP and CSC, so I will go down to the Docomo shop today and get the details, and request a custom root for us. I will post the details here when done.
You can visit the Official Docomo Page for this device.
{
"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"
}
Click to expand...
Click to collapse
Just got my Galaxy Note 3 from Docomo Shinyokohama branch last night.
This page is great and thank you to you sir for your technical knowledge and continued support for Samsung device owners here in Japan.
My previous phone was a Galaxy S2 (SC-02c) and I used your previous methods on rooting and now, my phone is still perfectly working
Though I'm still hesitant to tinker with my (20 hour-old) Galaxy Note 3...but I will continue to monitor this thread.
Thanks again in advance!

no one buying the galaxy J? :laugh::laugh:

docomo Note 3 owner now. Sweet root method please....(Onegaishimas)
tried ODIN with CF-Auto-Root-hlte-hltexx-smn9005 end status said PASS but on root check - failed.
Any pointers. Need CHAINFIRE to run.

n9005
I've purchased N9005 version off of hong kong based website. With my galaxy s3 from docomo sim card, i don't get any 3G/4G.... nothing but makeing and receiving phone calls.... i can't even send text!!!! but i can receive one... what is going on!
any help?

soul870518 said:
I've purchased N9005 version off of hong kong based website. With my galaxy s3 from docomo sim card, i don't get any 3G/4G.... nothing but makeing and receiving phone calls.... i can't even send text!!!! but i can receive one... what is going on!
any help?
Click to expand...
Click to collapse
Firstly, you need to set up the APN.
Secondly, DoCoMo has IMEI filtering on sp-mode, so you must be using a DoCoMo branded device.
You will need to switch your data plan from sp-mode to mopera to use your own device.
http://www.mopera.net/service/about/fit.html
Sent from my SC-01F using Tapatalk

I'm new to Japan and my original Note is getting long in the tooth so I'm considering buying a DoCoMo Note, hence I'm curious about bloatware. My understanding is that Japanese operators jam their phones with cute but useless apps, I also believe they only come with support for Japanese and English languages and you are not able to download support for other languages, is that true?
Is there any advantage to getting a DoCoMo device over Au?
Sent from my GT-N5110 using Tapatalk 4

Stock KitKat XXUEND6 Multi-CSC N9005 [GUIDE, ROOT, FIXES, MIRROR - ALL IN ONE PLACE]

Hi
Here is the way i used to flash the firmware, i advise to backup all your data before the flash.
All the files here are provided without any waranty.
Flash at your own risks.
Remember that go back to 4.3 is impossible after this procedure.
You may too void your knox counter when you attempt to root your device...
Click the pictures to open the root of the Mirror and find others goodies.
- Flash The Firmware :
First: Set the reactivation lock setting of your phone to OFF.
Be sure the battery of the phone is full.
- Uninstall Kies if you have it on your computer to avoid conflicts.
- Download PC Odin and Install / update the drivers from Samsung[/URL], that's all you need.
- Best and safe way is to use the original stock usb3 cable and make the job on a portable computer with his own power supply (battery connected).
1 - Download the latest repacked rom in this folder and extract it.
This is pure stock rom with only Multi-CSC OXXEND2 added.
Currently, this rom contain 19 Country Codes:
BGL, CYO, ERO, MSR, ORX, PHE, ROM, SEB, SEE, SIO, TEB, TOP, TPH, TRA, TSR, TWO, XEF, XEH, XSK
As it have a small sized hidden partition there is no need of any PIT File. More safe in my opinion.
If you need another CSC, maybe one of then is yours:
The Multi-CSC VFGENA4, 19 Country Codes:
ATL, CNX, CYV, MOB, MTL, OMN, PRO, SIM, SWC, TCL, TOP, VD2, VDC, VDF, VDH, VDI, VGR, VOD, XFV
As it have a small sized hidden partition there is no need of any PIT File.
The Multi-CSC OLBEND1, 10 Country Codes:
GLB, MM1, SIN, SMA, STH, THL, XME, XSP, XTC, XTE (Asia)
As it have a small sized hidden partition there is no need of any PIT File.
The Multi-CSC OXAEND1, 5 Country Codes:
BTU, DBT, ITV, XEF, XEO
As it have a small sized hidden partition there is no need of any PIT File.
The Multi-CSC OJVENB2, 3 Country Codes:
KSA, XFM, XSI
As it have a small sized hidden partition there is no need of any PIT File.
The CSC ITVEND1, 1 Country Code:
ITV (Italy)
As it have a small sized hidden partition there is no need of any PIT File.
The CSC ZZHENE3, 1 Country Code:
TGY (Hong Kong) - The attached modem ZHUENE2 is here.
As it have a small sized hidden partition there is no need of any PIT File.
The CSC VNZDMJ4, 1 Country Code:
VNZ (New Zealand)
The csc parts are from 4.3 rom but are confirmed working fine.
As it have a small sized hidden partition there is no need of any PIT File.
Three others CSC for specifics operators in France.
As they have a small sized hidden partition there is no need of any PIT File.
Check at the bottom of this post for French thread.
​
Just grab the one you want and put it in CSC in PC ODIN during the same flash process and it first flash the CSC inclued in the firmware, and then overwrite the CSC with the one you added.
2 - Download CF Auto Root for KitKat from Chainfire ODIN version.
Extract the tar.md5 file inside the zip to use with pc odin.
3 - Download the custom recovery PhilZ Touch ODIN version.
I advise to apply this unlock procedure before anything to avoid flash errors:
-> You need Triangle Away from Chainfire with a root acces granted.
Free version is avaible but consider to support the dev for his great job...
a/ Install the app on your phone.
b/ Run Triangle Away and Reset Flash Counter - Follow exactly what the program ask.
At the time to choose the way to reboot after the reset is done in recovery, choose reboot in download mode and then start the flash process immediatly.​
4 - In download mode flash the file that you had previously downloaded N9005-hlte_PDA-xxxxxxx_CSC-xxxxxxx_MODEMS-xxxxxxx_REPACK.tar.md5 with PC Odin in AP.
Do not forget to check/enable the Phone Bootloader Update option in pc odin. (seems working nevertheless without this option ticked)
Leave all others one by default.
Make sure re-partition is NOT ticked.
If you have an error (size error - Your phone may mismatch with this rom, another Samsung lock...) as odin fail at the end of the flash process.
- Shutdown the phone, disconnect the battery, disconnect the phone from your computer and wait a minute, return to download mode.
- Download and flash the file wich contain the CSC that you want.
5 - Auto self-reboot, let the stock recovery do his work completly (the green android man).
If you don't want to install root and a custom recovery, you can stop here.
6 - Go back download mode, flash the PhilZ Touch recovery with pc odin in AP.
7 - Again, in download flash, CF Auto Root with pc odin in AP, let the installation process terminate.
Note: If you were previously rooted, jump this step and download, If not yet done, SuperSu to update by flashing the file in custom recovery..
In this case, re-flash CF Auto Root will loose all your settings of SuperSu...​
8 - Download the fix for the ExtSdCard issue and flash it in custom recovery.
This is a Google security restriction, unnecessary to wait for a fix from Google, just from developpers of apps. Quick way is to apply this fix.
9 - Don't forget BusyBox which should be usefull too.
- About Mobile Odin :
As Mobile Odin seems to be unable to update the bootloader, don't use this one to avoid brick issues when operate with a different rom version than you have.
If you are already on the same firmware, you can use Mobile Odin to re-flash the rom or any other single part:
- Copy the file on your phone.
- Open this file in Mobile Odin.
- Enable EverRoot and Inject Superuser (SuperSu) in case of a system flashing.
- Choose to reboot in Recovery when you flash System and Cache partitions. If not, you may have problems regarding the CSC.
- Start Flashing.
- Do not skip md5 check to gain a little time. (For the life of your phone...)
- Issues :
All theses solutions were tested by me and worked for me, but without any other warranty.
The CSC region code or version are invisibles, the CSC folder is missing in system/.
The stock samsung keyboard crash often once booted.
You need another CSC (warning, you wil loose all your datas and settings, change for another CSC perform a wipe of the phone)
- Check here for the file you need, download and extract it.
-> Apply the Unlock Procedure.
- Flash the file N9005-hlte_CSC_xxxxxxx_RECOVERY-xxxxxxx_REPACK.tar.md5 with pc odin in CSC.
The Modem is not updated.
Download and extract the .tar.md5 modem file.
-> Apply the Unlock Procedure.
- Flash the file that you had previously downloaded N9005-hlte_MODEMS_xxxxxxx_REPACK.tar.md5 with pc odin in CP.
- Reboot normally.
The Bootloader is not updated.
You can check by using this app.
-> Download and extract the .tar.md5 bootloader file.
-> Apply the Unlock Procedure.
- Flash the file N9005-hlte_BL_xxxxxxx_REPACK.tar.md5 with pc odin in BL and check/enable the Phone Bootloader Update option.
- Reboot normally.
Flash player doesn't work anymore.
-> Install Firefox last up to date version and the original latest apk from adobe, nothing else to do.
-> If you prefer Dolphin, download the special version of adobe flash player, more here.
Maybe someone make an xposed module later, it should be a dream...
This fix seems working with this rom (bootloop efs corrupted related).
Not personally affected, just tested the flash.
Download here too.
After all this procedure, you should be fine, upgraded and with all yours datas and settings...
At this state, i just made a wipe of the cache and dalvik cache with phil'z recovery.
- Tune :
- Enable Init.d Support.
- To simply restore the sound at the (de)connection of the charger, you can install this app.
- If you want an imaged battery, you can use RECOVERY - SystemUI N9005 xxxxxxx MOD tkari4-Version by tkari4 based on the guide from parkhyb.
Basically revert to the old 4.3 style for battery and network icons.
{
"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"
}
Just Flash the mod with any custom recovery.
To revert back to the original situation, just flash in custom recovery the file RECOVERY - SystemUI xxxxxxx ODEX STOCK. (STOCK ODEX version)
You can use my blue battery mod. (I reworked a little the graphics for a better scale.) Just extract the .rar archive and install normally the apk Inside, you need too a working Xposed Framework installed.
You can find other Xposed compatibles battery Mods here.
Just reboot once installed.
Many Thanks to tkari4 for keeping alive his mod. :good:
- The repacks i made still works fine.
The rom repacks are made by me with this tool.
Many thanks and credits to all the persons who made this possible.
Notes:
As i do not have the time to download/extract all the roms, if someone needs another CSC repack for him or just to share, please post here with a link for the extracted CSC files only (cache.img.ext4 - hidden.img.ext4) related and with all the details (region, full code name, original rom it come from ... )
To unpack a .tar.md5 file, simply rename it as .tar and extract the content with any good archive software.
I will centralize here.
All others requests in any another form will be ignored, thanks for understanding.
To keep as simply and clear as possible, i will maintain on the Mirror and on thread only the latest updated rom, so if you put elsewhere any link from here, it may be broken in the time, the only ones which would be permanent is the one of the folder and the one of this thread. If you Mirror any file, thanks to keep credits.
Keep a local copy of the downloaded files if you think you will need then later as the content should be updated here.
I maintain the updates only for multi-csc repacks and keep others ones in the mirror, if you need one of theses mono-csc wich is not updated with the latest recovery avaible, simply ask here...
French users, clone thread is here.
Just press thanks if i helped.

Did you search the forum before posting? because if you did, you'd see that there are 500 thread about this already.

polish_pat said:
Did you search the forum before posting? because if you did, you'd see that there are 500 thread about this already.
Click to expand...
Click to collapse
Yes, every day i do.
And i saw no thread that talk about merging two différents roms to make a new one for a specific country, centralize all the majors tools with direct download links for correct versions to avoid confusions between JB & KK, that i often saw, and attached xda threads, and too provide others files needed at the same place for my device (n9005)
Maybe i had read the forum more often than you think...
Sincerly.

Perhaps you should look again
http://forum.xda-developers.com/showthread.php?t=2617932
http://forum.xda-developers.com/showthread.php?t=2631395
http://forum.xda-developers.com/showthread.php?t=2614787
http://forum.xda-developers.com/showthread.php?t=2618633
these are just thread in general section, hit in the past 24 hours, i didnt even get the ones in FAQ nor in dev section, i'm sure i could add about 10 more just by looking at the first page of each. If your thread is not getting hits from anybody, must be for a reason. Just sayin'

I made also my Rom N9005XXUENA7_OXXENA5_XXUENA2_ NoBootloader whit this TOOL from A.S._id Dev. Thanks @A.S._id
Only this files:
boot.img
cache.img.ext4 -->from NA6 (OXX)
hidden.img.ext4 -->from NA6 (OXX)
modem.bin
NON-HLOS.bin
recovery.img
system.img.ext4
Whitout Bootloader (5 files). Work well whit BL XXUENA6 and no Knox appl's.
At first boot, after enter whit my language, I have my csc TPH automatic, alright.
It's very good this [TOOL] TAR.MD5 PACKAGER and easy to make changes whit.
Anyway, thanks by Your work.
Best Regards
Valente
=======================================================================================
polish_pat said:
Did you search the forum before posting?
Click to expand...
Click to collapse
polish_pat said:
Perhaps you should look again
Click to expand...
Click to collapse
Hi Dear @polish_pat
Please, we have a MODERATION to see all Member's work. Not censure this Member. He have rights like You.
Thank You

polish_pat said:
Perhaps you should look again
....................
these are just thread in general section, hit in the past 24 hours, i didnt even get the ones in FAQ nor in dev section, i'm sure i could add about 10 more just by looking at the first page of each. If your thread is not getting hits from anybody, must be for a reason. Just sayin'
Click to expand...
Click to collapse
You made a thread, Others made a thread, i made a thread too, i just wanted to simply share my experience in another form, without any other pretention.
You seems to have a problem about that, not me.
You have time to waste, not me.
I'm not interested to play to the one that has the biggest.
Sincerly

Le [email protected] said:
You made a thread, Others made a thread, i made a thread too, i just wanted to simply share my experience in another form, without any other pretention.
You seems to have a problem about that, not me.
You have time to waste, not me.
I'm not interested to play to the one that has the biggest.
Sincerly
Click to expand...
Click to collapse
i made a thread a month ago, when it was relevant and nobody else did it.

Le [email protected] said:
Hi,
Set the reactivation lock setting of your phone to OFF.:
Click to expand...
Click to collapse
How do you do that on 4.3? (It's not on security setting).
Samsung Galaxy Note 3 T-Mobile USA.

johnvicencio said:
How do you do that on 4.3? (It's not on security setting).
Samsung Galaxy Note 3 T-Mobile USA.
Click to expand...
Click to collapse
I found it easly in security settings.
Maybe because you are on a Galaxy Note 3 T-Mobile USA, i have the HLTE international one.
In any case, check this video at about 2.30 mn

Le [email protected] said:
I found it easly in security settings.
Maybe because you are on a Galaxy Note 3 T-Mobile USA, i have the HLTE international one.
In any case, check this video at about 2.30 mn
Click to expand...
Click to collapse
I see thank you. That doesn't exist on T-Mobile USA at least not on 4.3.

1 - Download the official Poland rom...
2 - Download any NA7 rom...
To this step's We have here a MIRROR on MEGA Host.

Updated the op with a link to the repacked rom and refreshed the guide.
So it is more easy and simple, i think.

Good and informative First Post. Thanks!
Maybe you can do the same with the update that came out today

Pierre118 said:
Good and informative First Post. Thanks!
Maybe you can do the same with the update that came out today
Click to expand...
Click to collapse
Op Updated
No need to repack the whole firmware as all which is needed is Inside.
I am currently upload the rom to mirror it ...
Just made a new repack for the multi-csc.
Just flashed over the NA7 rom by following my guide and all went fine.
No full wipes.
Just made a wipe in dalvik cache and cache in recovery once done.

Great and complete Guide. Useful this ALL IN ONE PLACE. Bookmarked.
Thanks

I QUOTE from my THREAD next useful posts by @letama and @Le [email protected]
After this question to a member that not managed to flash the Bootloader NB3:
ValenteL said:
What Rom have You installed? If You have flashed the XXUENB3 why You are in NA6 BL?
Click to expand...
Click to collapse
letama said:
There is a catch in going from NA6 to NB3, it seems bootloader flashing is ignored now in NA6 BL if your rom status is custom. Solution is triangle away, reflash na6 stock, then make sure that you status is official before flashing NB3.
Click to expand...
Click to collapse
Le [email protected] said:
I was on NA7 BL previously flashed over NA6 BL without any problem.
Followed your trick and flashed my own made NB3 flashable file.
I did not any reflash, just reseted with triangle away.
And it worked, i am now on NB3 BL.
Updated my thread too..
Thanks.
Click to expand...
Click to collapse
letama said:
Thanks, good to know that reflashing pure stock is not mandatory, so the bootloader checks custom status flag only and not the whole firmware. Great, will save time for next one .
Click to expand...
Click to collapse

Updated the OP with a new version of Flash Player i found on xda wich work with Firefox too now.

Hi @Le [email protected]
Only for this time: Do not forget to check/enable the Phone Bootloader Update option in pc odin.
I don't understand why, if we flash a complete Rom whit a new bootloader. We not update the bootloader installed. Why You have this opinion now?
Thank You

Hi ValenteL
I saw (here or on other frenchs forums, no links to provide, forgot then) twice posts of somes personnes who don't have checked the option and have updated their bootloader and others one who don't had bootloader update and got soft brick issues as the rest was updated (JellyBean to Kitkat essentially)
It is usually advised here to check this option.
I not personnally took the risk to bypass this option in pc odin and always used it, so i can not confirm if it is important, effective or not.
There is this option in pc odin, i think too this is not for nothing at all.
For all this reasons, i prefer advise to enable this option when flashing a new rom, and it cost nothing to do.
Personnaly, i think it is important to do when using multi-files roms as the first Poland Leaked KitKat, but the bootloader update must be done automatically when flashing a single file rom which contain Inside all the needed parts.
Of course we can have problems when the knox is trigerred or the status of the rom is to custom, then somes parts seems to be 'jumped' when flashing. I feel this fact is increasing in the time.
When i bought my note 3, Under JellyBean, in France, i updated the rom with the latest version of JellyBean avaible on sam mobile for my country (XEF) and had no issue after the flash.
I got problem when i starded to flashed KitKat from others countries as the XEF one is not yet avaible and as i am a little an impatient flash-addict.
I wonder sometimes if i could have all this problems if were more patient and waiting for an upated version for my country.
At this time i identified three parts wich seems locked (not a secret).
CSC -> Ok, Samsung do not want i flash from another country, new policy from Samsung to lock by geographics sectors.
Modem -> Ok, region lock again.
Bootloader -> Why ? Does samsung want to block customs rom such CM, roots and others sames things? And knox related certainly too.
Samsung want to control and limit me a lot, to make more money with me.
Me, i want to be able to do ALL what i want with the device i bought, this is mine, as i can do with my Note 1.
There is a lot of chances that samsung never see again my money...
Time to bed here.
Sincerly

@ Le [email protected], Mega gives me a error when trying to download BOOTLOADER_N9005XXUENB3_REPACK.rar. Is there something wrong with the file?
---------- Post added at 09:22 PM ---------- Previous post was at 08:36 PM ----------
Pierre118 said:
@ Le [email protected], Mega gives me a error when trying to download BOOTLOADER_N9005XXUENB3_REPACK.rar. Is there something wrong with the file?
Click to expand...
Click to collapse
Never mind, Mega had a problem. Download is ok now.

Here's how I ROOTED Nougat on my S7 Edge G935T

Root Android 7.0 Nougat on Galaxy S7 & S7 Edge devices. YES! Supports all USA Qualcomm variants. T-mobile, AT&T, Verizon and *Sprint (*Note: Some people have reported problems with the Sprint device after root, while others have had success. As always, read the thread for detail and use at your own risk)
** THIS IS NOT FOR THE EXYNOS VERSION OF THE S7! **
A few answers to common questions:
YES - this breaks Samsung Pay and probably Android Pay (you will NOT be able to use Samsung Pay after root)
YES - this process is reversible by several methods, one of which would be simply doing a factory reset and re-flashing the complete Nougat Android 7.0 Firmware files in Odin, More details on this below.
NO - this process does NOT trip the KNOX counter
NO - there is no TWRP or custom recovery for this method of rooting
NO - there is no XPOSED framwork for Android 7.0 currently (as of today's date)
YES - There is a Android 7.0 custom rom! Thanks to @jrkruse https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Many thanks to the people who released the files! I am only posting the file's in a single easy to find post along with my experience and instructions which may or may not work for you! these instructions may or may not be right. these instruction may or may not be missing crucial steps. USE AND PROCEED AT YOUR OWN RISK! No one is responsible if you damage your device. CERTAINLY NOT ME!
PLEASE GIVE THANKS WHERE ITS DESERVED! Thank you :good:
MANY THANKS TO
@JUSMEJOSE https://forum.xda-developers.com/member.php?u=1113488
@princecomsy https://forum.xda-developers.com/member.php?u=5028474
@jrkruse https://forum.xda-developers.com/member.php?u=1949695
@jrkruse for his awesome job for making a custom flashable Android 7.0 Nougat ROM https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
@Chainfire for creating SuperSU and other great android utilities.
I'm sure there are many others, but I don't know who all created what, so I'm only listing those who I know - if I messed this up, I'm sorry in advance.
ENG (AP) files for S7 and S7E (from this post https://forum.xda-developers.com/showpost.php?p=71271898&postcount=28 )
https://www.androidfilehost.com/?fid=457095661767141717
(This is the ENGINEER boot kernel boot.tar file you'll be flashing in the special modified Odin software from your PC)
*edit: newer method available!* SuperSU 2.79 root.bat file (from this post https://forum.xda-developers.com/showpost.php?p=71281527&postcount=50 )
https://www.androidfilehost.com/?fid=817550096634750763
(This is the command prompt script you'll execute from a CMD prompt from a windows PC that installs the needed files for root access like SuperSU)
**EDIT: @jrkruse on 5/29/17 has created a new ROOT.BAT including SuperSU v2.82, it has been outlined in this post #480 of his custom rom thread. As always, please take a moment to hit the thanks button! Without the work of these amazing dev's we would NOT have root PERIOD! It is free for you, and mean's a lot to everyone involved in bringing these releases to you the public!!!
Here is latest root zip with SuperSU 2.82 (5/29/2017)
Nougat_S7_Root_2_82_All_Carriers_V1.zip
jrkruse said:
This root method will reset your fingerprints and lockscreen security it will also fix fingerprint issue this should help with issues of not recognizing your fingerprint after you root. I had to modify the latest SuperSu to get root to stick on SuperSU 2.82.
Here is a what I did:
The new supolicy from 2.82 Version was causing root not to stick. So I used the supolicy from 2.81 Version. I modded the SuperSu.apk to ingnore the supolicy not being 2.82 Version So you wont get asked to update the SuperSU binaries.
The SU binary is updated to 2.82 and all other files.
If you delete SuperSU apk dont reinstall it from playstore use the one in Above zip
Click to expand...
Click to collapse
**Alternative** Many thanks to active contributor of this thread @Quickvic30 for the info in post #688
https://forum.xda-developers.com/showpost.php?p=71700562&postcount=688
Who offer's another root.bat alternative which gave him better performance. Please check out that post for the file, and click the thanks button.
PLEASE REMEMBER: Results for rooting vary on each and every device. Lag, Performance, Heat - These things vary from device to device. YOUR MILEAGE WILL VARY!
** You will use either the originally posted SuperSU 2.79 root.bat, or the ALTERNATE version posted by Quickvic30 - DO NOT USE BOTH - CHOOSE ONE METHOD OR THE OTHER ** OR TRY EACH INDIVIDUALLY AND SEE WHICH GIVES YOU ACCEPTABLE RESULTS **
VoLTE VMM - IMservice hurricane icon fix thanks to jrkruse post #453
https://www.androidfilehost.com/?fid=457095661767144116
jrkruse said:
Sorry about all the VOLTE Icon problems
If your having FC issues your going to have to copy the original imsservice folder with imsservice.apk and oat folder to system/priv-app before you can flash this fix
This new zip should fix fc problems as no apk is replaced no more just the icons are replaced inside the apk
Volte Icon Fix Is now one zip for all S7 Variants. No more flashing wrong zip and getting FC. The zip only replaces Icons in imsservice apk. This zip will work on odex or deodex roms
S7_VOLTE_ICON_FIX_ALL_VARIANTS.zip
YOU MUST MOUNT SYSTEM IN FLASHFIRE WHEN FLASHING!!!
Click to expand...
Click to collapse
ALTERNATIVE SOLUTION from Post #413: Thanks to @sabresfan post #413
You will need to download and use only the PrinceComsy modified Odin which I got from https://www.androidfilehost.com/?fid=24591023225177749
Kernel Adiutor can be downloaded from Play Store
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
Original stock firmware files can be found on these sites or searching XDA
https://www.sammobile.com/firmwares/
http://updato.com/
** Edit: More information about returning to STOCK below on this first post **
**EDIT: Samsung USB driver's direct from Samsung web site http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
I'm not sure if you need the ADB files installed system wide or not? But you can also download and install the 15 minute ADB drivers. (use google or search XDA)
AGAIN: I did this to my Samsung Galaxy S7 Edge on T-mobile G935T RUNNING ANDROID 7.0 NOUGAT I believe this will work with other USA released carrier variants using Qualcomm chipset (T-mobile, AT&T, Verizon and Sprint)... BUT YOU DO THIS AT YOUR OWN RISK.
EDIT: MAKE SURE YOU ARE ON ANDROID 7.0 NOUGAT - OBVIOUSLY. (Baseband Version: G935TUVU4BQB1 in the case of a G935T S7 Edge) :fingers-crossed:
This process did NOT cause any data or application loss for me. I did this procedure from an OTA upgrade to N from MM.
Obviously, Download all needed files in advance and unzip accordingly.
Put your phone in download mode (Volume Down, Home and Power) then click home again to continue to download mode
Launch the modified ODIN on your PC
Unzip ENG BOOT file and get the boot.tar for your device (in my case it was the S7edge_qualcomm.tar was the file I needed for the S7 Edge) DO NOT UNZIP THE TAR FILE.
Put that .tar file in AP section of ODIN
Connect your phone, you should see a lighted COM port selected in ODIN meaning your good to go.
CLICK START in Odin. You Phone will flash the file quickly and restart.
Let it boot up fully and wait until you can unlock the phone (go to desktop of the phone)
Now open a CMD prompt on the computer and navigate to where you downloaded and unzipped the SuperSU 2.79 earlier
in the CMD prompt type root.bat this will push the required files to the phone and it will be rooted when its completed.
After a few minutes your phone will restart, and you will have SuperSU and root access on Android 7.0 Nougat.
This is how I rooted my SM-G935T Samsung Galaxy S7 Edge on Android 7.0 Nougat. Yes this is a bootloader locked T-mobile branded device.
Please feel free to add or correct anything here in the posts below!
EDIT: You'll want to install Kernel Auditor from the Play store, grant it supersu permission, and set both cpu govenors to ONDEMAND and set apply on boot. (core 1&2 default to performance and core 3&4 default to interactive - set both to ondemand and apply on boot)
EDIT2: You may want to experiment with the CPU governors in Kernel Adiutor (that's actually the correct spelling according to the author). It's been suggested CONSERVATIVE will give you better battery life than ONDEMAND. So you'll want to try the available options and see which results in acceptable balance of performance and battery life for you.
GOOD LUCK! AND THANK YOU!
I HOPE THIS HELPS PEOPLE GET ROOT ON THEIR USA QUALCOMM DEVICES
PLEASE TAKE A MOMENT TO THANK THE PEOPLE WHO BROUGHT THIS INFORMATION TO YOU.
Returning to STOCK Android 7.0 Nougat
You will need to have Odin installed (same modified Odin linked above should work fine)
You can download stock Android 7.0 Nougat firmware from
https://www.sammobile.com/firmwares/
http://updato.com/
For the T-mobile S7 Edge G935T ONLY
File: SM-G935T_G935TUVU4BQB1.zip
Google Drive Link: https://drive.google.com/file/d/0B9QvmNs9dpD-LTdwQUgzejk5ZGM/view
From thread (thanks to it's OP): https://forum.xda-developers.com/tmobile-s7-edge/how-to/odin-stock-nougat-firmware-s7-edge-t3558242
Thanks to @Krog18 for linking to Verizon firmware files in post https://forum.xda-developers.com/showpost.php?p=71383942&postcount=359
G930V QA2 Stock fw: https://www.androidfilehost.com/?fid=529152257862709174
G935V QA2 Stock fw: https://www.androidfilehost.com/?fid=817550096634752305
Thanks to @Quickvic30 for linking to the AT&T firmware files in post https://forum.xda-developers.com/showpost.php?p=71601821&postcount=608
G935A QA6 https://www.androidfilehost.com/?fid=745425885120713605
When you extract the .zip file for your device, you have 2 options for the CSC section. One file will erase all existing data and apps, reverting your phone to a like new state. The other will preserve your currently installed apps and data.
CSC_TMB_G935TTMB4BQB1_CL10376601_QB12449118_REV02_user_low_ship_MULTI_CERT.tar USING THIS FILE WILL ERASE ALL EXISTING DATA ON THE DEVICE
HOME_CSC_TMB_G935TTMB4BQB1_CL10376601_QB12449118_REV02_user_low_ship_MULTI_CERT.tar USING THIS FILE WILL PRESERVE (*NOT ERASE) ANY EXISTING DATA FROM THE DEVICE
Obviously you can only choose 1 of the CSC files. Using the HOME_CSC keeps your existing data, and the other CSC formats your phone.
Thanks to @billa (https://forum.xda-developers.com/member.php?u=293193) for taking taking the time to put these tips together for everyone.
Slightly edited by me
billa said:
Note (and suggestions)
----
Before and after rooting wipe the cache.
For tweak settings to stick, must reboot multiple times.
Security Updates OFF
--------------------
Settings > Lock Screen > Security > Other Security > Security Policy Updates > OFF and Wi-Fi only
Disable (things to disable after root - Use Titanium Backup or Package Disabler Pro for Samsung, both available from the Play Store - Worth the price to buy!)
-------
Samsung DM Phone Interface
Samsung DM Service
SecurityLogAgent
com.sec.android.soagent
com.wssyncmldm
tethering.automation
tethering.provisions
After Eng-Boot (root is complete)
--------------
Install Kernel Auditor, and set both CPU govenors to "OnDemand" and set apply on boot.
Set cores 1&2/3&4 to "OnDemand" and apply on boot.
EDIT: Experiment with governor settings until a balance of power and performance is reached. Kernel Adiutor is available from the Play Store
Performance tweaks
------------------
GovTuner - set to interactive and performance
Kernel Auditor
Kernel Toolkit
LSpeeds
SSD Boost
SHealth fix
-----------
Set ro.config.tima to 0 in build.prop
WiFi passwords fix
------------------
Set ro.securestorage.support to false in build.prop
VOLTE/RCS icons OFF
-------------------
Copy the imsservice.apk from the root zip to
/system/priv-app/imsservice/
and set permissions to -rw-r--r--
Data toggle
-----------
Use SQLite editor and add MobileData to a string in settings.db
Busybox fix
-----------
Install busybox to /system/xbin instead of /su/xbin
Sprint LTE fix
--------------
In Build.Prop change the following:
ro.cdma.default_numeric=310000 to 310120
ro.cdma.default_alpha=Chameleon to Sprint
ro.build.characteristics=Chameleon to Sprint
OR
Go into settings
Click Connections
Click Wi-Fi Calling
Click Cellular Network Preferred
Go back two times and click on Mobile networks
Select Network mode and select 3G/2G (auto connect)
Restart your phone and call 611 just to make sure the call goes through
Hangup and go back to Network mode and switch back to LTE mode
Click to expand...
Click to collapse
As always THANKS to all the users who continue to contribute to this thread, and to all the people involved in bringing you this information so you can ROOT your Samsung Galaxy S7 or Samsung Galaxy S7 Edge on Android 7.0 Nougat!
I will continue to update this first page with relevant links, details and information in an attempt to keep the information easier to find for everyone.
Take a moment to press the THANKS button!

So how's the lag for you compared to the eng boot on marshmallow?

As stated in the OP, what you do at this point is at your own risk. I did it, and worked smoothly. Not sure if you need CMD drivers installed before hand, probably do, but I clicked on the Root.bat, and it did it's thing. So far, so good. Thanks to the above contributors without a doubt. Snappy so far.

nitroevo said:
So how's the lag for you compared to the eng boot on marshmallow?
Click to expand...
Click to collapse
I never did the ENG root on MM, so I can't compare. The lag right now is absolutely there. I'm trying to tweak and reboot as I go. Trying to get it better.
I installed Kernel Auditor and set both of the CPU gov's to ONDEMAND - but it won't stick on reboot, one defaults back to performance and the other (core 3&4) defaults to interactive.

vazquezcmp said:
As stated in the OP, what you do at this point is at your own risk. I did it, and worked smoothly. Not sure if you need CMD drivers installed before hand, probably do, but I clicked on the Root.bat, and it did it's thing. So far, so good. Thanks to the above contributors without a doubt. Snappy so far.
Click to expand...
Click to collapse
I think the SuperSU root file has the needed ADB files, so once you navigate to that folder in CMD (command prompt on the pc for those a little lost), I assume those files are whats used to push the root.bat script to the phone? I think we are both right? but I'm not 100% that's why I mention the ADB drivers, which were already installed on this PC I used. This information was scattered in several threads, I was hoping to put all the links in 1 place so we can maybe get this working smoothly for EVERYBODY.:good:
Since you did it too, and you're getting smooth results what steps did I miss? if any.:fingers-crossed:

I did exactly as you said and worked nicely. The only thing I would add is to already be on Nougat but that might be obvious. I didn't do that earlier, and ended up in a boot loop. Thanks for putting it together. Tomorrow I'll post any lag issues.

vazquezcmp said:
I did exactly as you said and worked nicely. The only thing I would add is to already be on Nougat but that might be obvious. I didn't do that earlier, and ended up in a boot loop. Thanks for putting it together. Tomorrow I'll post any lag issues.
Click to expand...
Click to collapse
Excellent.. Glad it worked.

I just installed it, seems to be running pretty good. Definitely a lot smoother than the MM eng root. I mainly installed because I wanted to get Google assistant lol.
To enable Google assistant you have to use a root explorer app or ADB and change + add a line to the system/build.prop
Change first line to
ro.product.model=Pixel XL
Copy and paste this into system/build.prop
ro.opa.eligible_device=true
Reboot and you have Google assistant!

Quickvic30 said:
I just installed it, seems to be running pretty good. Definitely a lot smoother than the MM eng root. I mainly installed because I wanted to get Google assistant lol.
To enable Google assistant you have to use a root explorer and change + add a line to the system/build.prop
Change first line to
ro.product.model=Pixel XL
Copy and paste this into system/build.prop
ro.opa.eligible_device=true
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
LMAO... That's funny, we should be getting in legit soon... :good:
(but, I'm gonna enable it too! :silly: )

Will this work for Sprint? Thanks

Regnuf said:
Will this work for Sprint? Thanks
Click to expand...
Click to collapse
I believe so... but since I don't have a sprint device to test, I have no idea. (but I think YES)

Thank you sir! Going to be doing this to my S7 standard right now.

Araltd said:
I never did the ENG root on MM, so I can't compare. The lag right now is absolutely there. I'm trying to tweak and reboot as I go. Trying to get it better.
I installed Kernel Auditor and set both of the CPU gov's to ONDEMAND - but it won't stick on reboot, one defaults back to performance and the other (core 3&4) defaults to interactive.
Click to expand...
Click to collapse
to make it stick on reboot i think there should be a setting there that says apply on boot

Have you tried flashing the fixes from the popular root thread? Or is it not needed?

Araltd said:
VoLTE VMM icon fix (from this post https://forum.xda-developers.com/showpost.php?p=71281527&postcount=50 )
https://www.androidfilehost.com/?fid=673368273298935963
You will need to download the PrinceComsy odin which I got from https://www.androidfilehost.com/?fid=24591023225177749
Click to expand...
Click to collapse
Give this a try and see if it gets rid of that stupid icon
TMO_VOLTE_ICON_FIX.zip

jrkruse said:
Give this a try and see if it gets rid of that stupid icon
TMO_VOLTE_ICON_FIX.zip
Click to expand...
Click to collapse
Hey thanks for coming over here...
As I mentioned, I don't care about the big hurricane looking icon, but the com.sec.vmimservice icon notification (looks like a red face) pops up multiple times in my status bar whenever there is texting activity. Send or receive. That's what I want to get rid of.
Edit: here's the notification pulled down so you can see.. I have that little red icon in my status bar several times right now... I am using Android messages, and I use Tmobile digits on my other phone (note 4) just fyi... Not sure if everybody is seeing that or if it's unique to either Android messages (formerly Google messenger) or digits service by Tmobile?
{
"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"
}

nitroevo said:
to make it stick on reboot i think there should be a setting there that says apply on boot
Click to expand...
Click to collapse
Somewhere between reboots (of which there have been many tonight) the setting finally stuck. I also set kernel auditor (adiutor) to set the settings immediately on reboot with no delays.
To me, there is still significant lagging, even with on demand Governor set. I read somewhere about setting the min/max also, those values are always fluctuating in the kernel adiutor program, I'm not sure how to properly set those.... But I also tried kernel tool and had similar results. Just fyi.

cjlopez213 said:
Have you tried flashing the fixes from the popular root thread? Or is it not needed?
Click to expand...
Click to collapse
Honestly I don't think most of those fixes are still relevant even for MM 6.0.1, so I doubt any flash able version mod would be suitable for N 7.0 [emoji6]
So far, what I've done is wiping cache in recovery (volume up, home and power)
Set the governors to on demand... Beyond that we will need some experts to chime in with suggestions, tips and advice.

cjlopez213 said:
Have you tried flashing the fixes from the popular root thread? Or is it not needed?
Click to expand...
Click to collapse
They are installed when you root
---------- Post added at 02:20 AM ---------- Previous post was at 02:19 AM ----------
Araltd said:
Honestly I don't think most of those fixes are still relevant even for MM 6.0.1, so I doubt any flash able version mod would be suitable for N 7.0 [emoji6]
So far, what I've done is wiping cache in recovery (volume up, home and power)
Set the governors to on demand... Beyond that we will need some experts to chime in with suggestions, tips and advice.
Click to expand...
Click to collapse
If you set govenors to conservative you will get way better battery life.

jrkruse said:
They are installed when you root
---------- Post added at 02:20 AM ---------- Previous post was at 02:19 AM ----------
If you set govenors to conservative you will get way better battery life.
Click to expand...
Click to collapse
Please refresh, I posted a picture of the imservice notification I'm getting. Thanks!

[GUIDE/ODIN/FW/BL] SM-P610 USA/XAR WIFI ONLY: Stock Firmwares + Modded BL WarningText

THIS IS YOUR FIRST WARNING (WILL BE REITERATED PLENTY OF TIMES!) IN BIG RED BOLD LETTERS - THESE FILES ARE FROM/FOR THE USA ("XAR") REGION, SM-P610 WIFI MODEL ONLY!
(with the exception of the Odin utility, as well as possibly the modified boot splash screen, which may work on other variants, though untested and done solely at your own risk - read all the notes!!)​
I already went through the work, so I figured I would share these files for those who also own the same exact tablet. Again, it's for the USA/XAR region Samsung Galaxy Tab S6 Lite WiFi Model ONLY - "SM-P610" / "gta4xlwifi". LTE model is a different variant; do NOT flash the stock firmware files to that device! Also, sorry, I will not support or answer questions for other variants (other than what I will mention in this OP). Downloading firmwares for other variants will be a huge PITA, and I don't have / pay for any "premium" accounts which would allow me to quickly download the huge firmware files. I'm only sharing these I'm posting because I already took the time to acquire and archive them for personal usage, and might as well share them for those who own the same device / variant.
Use these files at your own risk, and only flash if you know what you're doing!! I'm not responsible for any problems user may incur from usage of these files, the usual warnings apply, etc. This device is just a backup / playaround device for me, and so it doesn't get daily usage out of me, nor will I likely be very active on this subforum (sorry! just being honest). Also, I immediately installed LOS on my device anyway, so I don't run stock ROM myself and therefore won't be sharing pre-patched Magisk boot images either. Sorry to those who are used to that from me =)
So anyway... what's in this post?
Odin3 v3.14.4 (version I've been using on this device, and working perfectly fine as of this initial posting)
Stock firmware zips for USA/"XAR" Region SM-P610, WiFi Only
Modified BL file (Odin-flashable), to remove the warning boot text
Odin3 v3.14.4:
I posted this in another thread, but figured I would also link to it here so it's easy to find in one place. This worked perfectly fine for me to root / install TWRP / flash BL files, etc.
Download Link: https://www.androidfilehost.com/?fid=10763459528675582443
Stock Firmware Files:
USA/XAR WIFI ONLY! October 2020 Update - Firmware Version P610XXU2BTJ5
Download Link: https://www.androidfilehost.com/?fid=10763459528675592742
USA/XAR WIFI ONLY! September 2020 Update - Firmware Version P610XXU2BTI3
Download Link: https://www.androidfilehost.com/?fid=10763459528675592159
Firmware files for other variants, see this post. Follow the links, use the resources, consider the context for other variants: https://forum.xda-developers.com/showpost.php?p=83083249&postcount=2
Modified [BL-slot] Odin-Flashable File To Remove Warning Splash Screen Text:
My Thoughts On This...After unlocking the bootloader and flashing non-stock images, we all know we end up with that annoying, ugly splash screen screaming that the device is modified. Most of us modifying our devices understand the security implications involved, and ironically choose to modify our devices to increase security in other ways. Yet, these warning splash screens, in the unfortunate event of possible theft, may very well end up being the reason a more tech-savvy thief is able to break into the device, or find someone who can. So, thanks to users' posts Awesomeslayerg's hint and blascogm's guide, I quickly came up with an Odin-flashable file to change the splash screen, as seen below:
(if the pic doesn't show, probably the imgur link I used is dead, but I also attached it to this post)
{
"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"
}
I know some people may be thinking "why not just remove the PRESS POWER KEY TO CONTINUE line completely and have it stay at the normal boot screen seamlessly the whole time", and the reason I decided not to do this is because it generally wouldn't make the average person suspect the device is modified, and it's still good for us to know that it's at the boot stage where we can hit the power key to skip the ~10 second timeout. It's exactly the same image, so it's still very seamless and stock-like. I even took the time to center the power key text exactly, by the pixel, from left to right and from top bottom relative to the knox and android logos.. ; )
And if it really bothers you that much, follow the guide I linked above and do it yourself. =)
I should also mention that, for our devices, the .bin.lz4 file that needs to be decrypted is actually "up_param.bin.lz4" and not "param.bin.lz4" as suggested in the guide, as it's for a different device. You will need the lz4 utility (check Awesomeslayerg's thread, or google lz4 github) to decrypt the lz4 file to a regular bin file, and then you can extract and/or replace the .jpg files using an archiver program (I recommend 7-zip for this).
The hash checksums for every single file/jpg in each up_param.bin were identical between the September and October firmwares. Therefore, at least as of this posting, the same modified Odin-flashable file will work on either firmware version, and likely future versions until they make any significant changes. I did test this myself too btw. Also, if you look at the structure and contents of the up_param.bin file for yourself, you'll see that they are simply .jpg files containing the screens, backgrounds, and text you're all familiar with when going into bootloader / download mode. Assuming they follow the same file naming structure, I suspect you can probably flash this to other variants, although it will change the text language to English (assuming they localize the bootloader / download mode text per every region; I have no idea about this as I only own US variants). To see what I'm talking about, here's a quick screenshot (better resolution pic, and just in case imgur link dies, also attached to this post):
Now that I (hopefully) tricked you into reading this entire section so that you now have some basic understanding of how it works before proceeding to flashing the warning text removal mod, here are the instructions / link for install:
- Download the .tar file provided below.
- Boot device into Download mode.
- Place .tar file into bootloader [BL] slot in Odin and flash.
Download Link: https://www.androidfilehost.com/?fid=10763459528675592179
To revert back to stock splash screen with warning text, for whatever reason:
Pull the stock up_param.bin.lz4 from the stock firmware file (from the BL****.md5 file within the firmware zip).
- Convert it to up_param.bin uzing lz4 utility.
- Add up_param.bin to an archive as .tar file, uncompressed (recommend using 7-zip).
- Flash the .tar file, which should contain only the stock decrypted up_param.bin file, in Download mode using Odin in the BL slot.
I uploaded my custom jpg's, as well as the stock untouched jpg's, for those that are curious or want to edit them further. Feel free to snag them here: https://www.androidfilehost.com/?w=files&flid=320350
* As we can see, we're only modifying the .jpg files provided by up_param.bin, so it's a relatively harmless process (unlike modifying aboot files in the old days of HTC devices, which if done improperly could literally result in an unrecoverable brick). But even so, please only flash if you know what you're doing and can recover from any potential mistakes or errors.

Not sure if there were any changes since the September / October 2020 firmwares, but here's a new one directly modified from the March 2021 (Android 11) firmware base:
NEWEST DOWNLOAD, BASED ON 2021-03 FIRMWARE:
https://www.androidfilehost.com/?fid=14943124697586346609

And another

Hi,
Thanks for these resources. I'm actually not at these steps yet. I'm having trouble gaining access to the OEM Bootloader Unlock option in developer options. Here are things I've tried already based on what I researched before my attempt.
Android 10 is the current OS installed after unboxing.
1. Disable Automatic Date and time
2. Select a date more than 7 days prior to current date of attempt.
3. Under Settings > About Phone > Software Information. Select/Tap Build Number 7-8 times to unlock Developer Option.
4. Disable Auto Update System (Apply Updates When Device Restarts) - *This was somehow already disabled the first time I entered Developer options*
5. Under Software Updates > Disable Automatic Updates -*This was also already disabled on unboxing and it says Automatically download updates over Wifi. It does not say Automatic Updates*
6. Reboot device and return to Developer Options after booting to OS.
7. The OEM Bootloader Unlock option should appear greyed out at this point. Toggle it to unlock bootloader with consideration that it will wipe the device data.
These are the steps I've found and tried with no success in gaining access to the Bootloader unlock option. I am also certain that my device is the international model SM-P610 with Exynos chipset and Mali-G72 GPU. Something else to note, I did uncheck many default options tied to improving privacy on the device before attempting the steps to gain access to the bootloader unlock option. I do not know if that would make a difference. If you recognize anything wrong with the steps I've tried already, please let me know where I'm going wrong or where I can find the correct way to unlock the bootloader. I've been posting in other threads, but nobody seems to be replying to me. Any help will be appreciated.

Hi
I've flashed your modded file on my PHN (Netherlands), no problems at all working ootb!

Hi. I used blascogm's guide for my P615 with latest firmware for SEC UI 3.1and all are OK! Thanks for all.
Add. I add link . Flash via Odin(BL).
https://androidfilehost.com/?fid=14943124697586347282

i5lee8bit said:
Not sure if there were any changes since the September / October 2020 firmwares, but here's a new one directly modified from the March 2021 (Android 11) firmware base:
NEWEST DOWNLOAD, BASED ON 2021-03 FIRMWARE:
https://www.androidfilehost.com/?fid=14943124697586346609
Click to expand...
Click to collapse
I flashed ths when I'm running lineageos 18.1 annd this is the only mod that worked for me

Thanks for posting your images and linking to the guide, worked perfectly and the images just fit to the pixel <3

Confirmed working as of March 2022. Device is running base P610XXU2DUL9. Thanks for the hard work.

can you make one for SM-P613 model plz?