**does not yet work for 7.1.1**
Using a PC to root seems like moving backwards compaired to a 'one click' apk. but we're already at the PC to flash eng_boot, plus this new method is so much faster...so here we go
Features:
SuperSU 2.82
Init.d
Wifi fix
Flashlight fix
Issues:
For the wifi fix I just copied an edited J320a build.prop
So J320AZ users will see J320A in about device, and will have to reassign notification sounds. (Hope to fix it in the future)
Needed Files:
Odin
Root_J320A.zip
Procedure:
1. Unzip both files.
2. Run Odin click the 'AP' button.
3. Navigate to Root_J320A/bin and select sm-j320a_Engroot_601PJ2.tar and press "Start" (make sure NOT to check re-partition)
4. After it completes sucessfully, leave the phone hooked to the pc... and then wait, wait a good 2 or 3 minutes after its booted.
5. Once 2 or 3 minutes has gone by you can navigate to the Root_J320A folder.
6. There you'll see root.bat, double click that let it do its thing.
6a. If at any time during the script you see "adb out of date. killing..." hit the x to close the window and restart the script.
*This may work on J320AG models but make sure you check oem unlock from dev settings first... and let us know how it goes
Enjoy
- D
Credits:
@ashyx - eng_boot
@Sh$llNinjA - eng_root
@sjowns - flashlight fix
@Chainfire - SuperSU
@Ryuinferno - init.d script
Excellent! This works perfectly! Thank you so much for posting this.
J320A PC9 worked perfectly!
March security patch
Hi man, this method support the march security patch, or are still in january security patch
I tested on AQD2 so it'll work on AQC1 too.
I assume it'll work for all 6.0 updates we get.
I tested on AQD2 so it'll work on AQC1 too.
I assume it'll work for all 6.0 updates we get.
This works perfectly. Thank you!
I suggest you put 'root' in the tile, otherwise google cannot find it.
I googled 'j320a root', google only links to ashyx's post which doesn't... well maybe only mine phone.
I am new to this root bit.
Possibly I have done something wrong. I read your instructions carefully and quit didn't understand where the unzipped files should go. Do any of these have to be placed in the phone's directory?
Failed on my AT&T SM-J320A
I wonder if it has anything to do with the new update pushed out recently
@JeffF73
Run Odin and Click ap.
Navigate to the directory where you unzipped root_j320a.zip.
In that folder you'll see a bin folder, inside that is sm-j320a_Engroot_601PJ2.tar, which needs flashed to the phone.
Once that's complete, let it boot and wait.
Then run root.bat
DamienMc said:
@JeffF73
Run Odin and Click ap.
Navigate to the directory where you unzipped root_j320a.zip.
In that folder you'll see a bin folder, inside that is sm-j320a_Engroot_601PJ2.tar, which needs flashed to the phone.
Once that's complete, let it boot and wait.
Then run root.bat
Click to expand...
Click to collapse
Hello DamienMc Thank you for your reply and help. I figured it out. I had to put my phone in "Download Mode" by holding down Volume Down, Home Button and Power button while booting. Then I was able to use Odin without failing. This solved all my problems thank you
Is it safe to flash this after doing this?
https://mega.nz/#!D8hSzLaa!pDugFwQ0NyGBLy36j1643bI3e4f9xog7US8UTTkZ8SU
sonic0504 said:
Is it safe to flash this after doing this?
https://mega.nz/#!D8hSzLaa!pDugFwQ0NyGBLy36j1643bI3e4f9xog7US8UTTkZ8SU
Click to expand...
Click to collapse
Yes, that has selinux set to permissive as well, although there's no real difference. The build.prop differences are noticable tho...I plan on doing an update to this, just have to figure out how to tell if it's A or AZ from adb
Ragheb Alama said:
Hi man, this method support the march security patch, or are still in january security patch
Click to expand...
Click to collapse
Yes, it works for QC1. However, you may need to replace build.prop in /bin from QC1 with WiFi fix before root.
I did notice that after root, the contents of /Android/data folders in both internal storage and external sd card are hidden from PC. Before root, both are visible from PC. Any thoughts about what cause the changes?
Will this work on July security patch?
DamienMc said:
Yes, that has selinux set to permissive as well, although there's no real difference. The build.prop differences are "noticeable" tho...I plan on doing an update to this, just have to figure out how to tell if it's A or AZ from adb
Click to expand...
Click to collapse
Thanks, I just needed to install this to use adb to uninstall an update I did to System UI because it would continuously crash.
SBCarr said:
Yes, it works for QC1. However, you may need to replace build.prop in /bin from QC1 with WiFi fix before root.
I did notice that after root, the contents of /Android/data folders in both internal storage and external sd card are hidden from PC. Before root, both are visible from PC. Any thoughts about what cause the changes?
Will this work on July security patch?
Click to expand...
Click to collapse
Probably the eng_boot we use, it breaks the flashlight and wifi passwords too... it does work on j320a July update, so I assume it'll work on j320az update too
@DamienMc Dude, thanks for ur post, but i tried 2 times and fail, i got stuck at logo, i had to reflash to stock but now my build.prop is gone or corrupted, my phone says model unknow, i cant even use hidden menus like *#06, etc, i need the original file to fix it please. model SM-J320A RUNING QC1
ScSoluciones said:
@DamienMc Dude, thanks for ur post, but i tried 2 times and fail, i got stuck at logo, i had to reflash to stock but now my build.prop is gone or corrupted, my phone says model unknow, i cant even use hidden menus like *#06, etc, i need the original file to fix it please. model SM-J320A RUNING QC1
Click to expand...
Click to collapse
Reflash CSC as well, that'll wipe your device but fix your problem.
Are you sure you waited long enough after the phone booted before rooting?
If at any time during the script you see it say "adb server out of date. Killing..." something is wrong. You can x the command prompt and do root.bat again.
DamienMc said:
Using a PC to root seems like moving backwards compaired to a 'one click' apk. but we're already at the PC to flash eng_boot, plus this new method is so much faster...so here we go
Features:
SuperSU 2.82
Init.d
Wifi fix
Flashlight fix
Issues:
For the wifi fix I just copied an edited J320a build.prop
So J320AZ users will see J320A in about device, and will have to reassign notification sounds. (Hope to fix it in the future)
Needed Files:
Odin
Root_J320A.zip
Procedure:
1. Unzip both files.
2. Run Odin click the 'AP' button.
3. Navigate to Root_J320A/bin and select sm-j320a_Engroot_601PJ2.tar and press "Start" (make sure NOT to check re-partition)
4. After it completes sucessfully, leave the phone hooked to the pc... and then wait, wait a good 2 or 3 minutes after its booted.
5. Once 2 or 3 minutes has gone by you can navigate to the Root_J320A folder.
6. There you'll see root.bat, double click that let it do its thing.
6a. If at any time during the script you see "adb out of date. killing..." hit the x to close the window and restart the script.
*This may work on J320AG models but make sure you check oem unlock from dev settings first... and let us know how it goes
Enjoy
- D
Credits:
@ashyx - eng_boot
@Sh$llNinjA - eng_root
@sjowns - flashlight fix
@Chainfire - SuperSU
@Ryuinferno - init.d script
Click to expand...
Click to collapse
This was the first time i ever tried to root my phone and i followed the instructions located here:
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628
Well my wifi wouldnt save any passwords , flashlight was broken and my ATT J320A would always want to boot in to recovery mode. I thought i was screwed!!!! Then i seen one link in the thread to this thread where Kingroot was not needed.
I opened Odin and gave a shot and then ran Root.bat file, and the device rebooted wifi and flashlight were fixed and best of all my J3 was now rooted!!!!!
Still working on getting rid of that annoying pop up but all is good, thanks so much for this root and fix from the other thread.
james2ya said:
This was the first time i ever tried to root my phone and i followed the instructions located here:
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628
Well my wifi wouldnt save any passwords , flashlight was broken and my ATT J320A would always want to boot in to recovery mode. I thought i was screwed!!!! Then i seen one link in the thread to this thread where Kingroot was not needed.
I opened Odin and gave a shot and then ran Root.bat file, and the device rebooted wifi and flashlight were fixed and best of all my J3 was now rooted!!!!!
Still working on getting rid of that annoying pop up but all is good, thanks so much for this root and fix from the other thread.
Click to expand...
Click to collapse
@james2ya If you are talking about the pop that either says something in the order of "Unathorized activities where made" go to the play store, download and install SecurityLogAgent Fix, Open it up and click "Disable Securitylogagent" then restart phone when it asks. This should help get rid of that popup.
works great for me! now i just need a custom rom. is it possible to install trwp on j320a?
Related
Is there a mod that allows me disable the Installer from automatically coming up when connecting to a pc through USB?
Tyetiger said:
Is there a mod that allows me disable the Installer from automatically coming up when connecting to a pc through USB?
Click to expand...
Click to collapse
I was able to by deleting autostart.iso file from \system\etc
I use Mac and it no longer mounts the mobile Verizon app. I assume its the same for windows.
Itsmyphoneyo said:
I was able to by deleting autostart.iso file from \system\etc
I use Mac and it no longer mounts the mobile Verizon app. I assume its the same for windows.
Click to expand...
Click to collapse
Ive been trying for days! Haven't been able to find that folder or file. Unfortunately I have a PC
Tyetiger said:
Ive been trying for days! Haven't been able to find that folder or file. Unfortunately I have a PC
Click to expand...
Click to collapse
You need root to do this... I probly should have mentioned that. Sorry. Getting root is easy now, there are a could threads on how to root with very easy step by step instructions. After you gain root, purchase root explorer from PlayStore (yes, you have to spend a couple $ but its worth it) and use that app to navigate and delete the file. You will likely use the app again, unless you switch to an iPhone. So it's worth the little bit of money.
I see autorun.iso, I assume that's what you're referring?
Sent from my SCH-I545 using xda app-developers app
Itsmyphoneyo said:
You need root to do this... I probly should have mentioned that. Sorry. Getting root is easy now, there are a could threads on how to root with very easy step by step instructions. After you gain root, purchase root explorer from PlayStore (yes, you have to spend a couple $ but its worth it) and use that app to navigate and delete the file. You will likely use the app again, unless you switch to an iPhone. So it's worth the little bit of money.
Click to expand...
Click to collapse
Ok. I was able to download a root explorer and remove the autorun.iso. But I notice the phone still says "Installer is connected" and I still can't view the sdcard or drive on the phone unless I'm in Camara(PTP) mode.
Tyetiger said:
Ok. I was able to download a root explorer and remove the autorun.iso. But I notice the phone still says "Installer is connected" and I still can't view the sdcard or drive on the phone unless I'm in Camara(PTP) mode.
Click to expand...
Click to collapse
Check your usb debugging settings. you might need to either check that box or unchecked it. I can't help much more than that if you're using Windows, I'm a mac user. But that sounds like all you would need to do. Hope it helps.
Verizon installer
Okay here is a weird one (or maybe not). Started getting this when I first connected the S4 to PC via USB. Now when I connect my S3 I am getting the same popup. S3 is rooted never had this message.
I am thinking this is somehow embedded into the new Samsung USB drivers. When the phone is plugged in, some form of check reveals a VZW phone which triggers the installer????
Did anyone figure this out? I was able to stop the Verizon Installer Pop up by renaming the autorun.iso, but there is still a 30 second delay before I get access the the phones internal and external memory.
Gam3r 4 Life said:
Did anyone figure this out? I was able to stop the Verizon Installer Pop up by renaming the autorun.iso, but there is still a 30 second delay before I get access the the phones internal and external memory.
Click to expand...
Click to collapse
Bump, I'd like to know the same thing.
ecen92 said:
Bump, I'd like to know the same thing.
Click to expand...
Click to collapse
I'm getting connect/disconnect every 3 seconds.
Gam3r 4 Life said:
Did anyone figure this out? I was able to stop the Verizon Installer Pop up by renaming the autorun.iso, but there is still a 30 second delay before I get access the the phones internal and external memory.
Click to expand...
Click to collapse
Still trying to figure this one out........any ideas......anyone????
Zelmo88 said:
Still trying to figure this one out........any ideas......anyone????
Click to expand...
Click to collapse
Bump! Anyone find a cure for this yet?
I think I figured it out. I'm still on original MDK build. I don't know if that changes anything.
1. autorun.iso removed (may not be necessary, but mine is gone)
2. enable hidden menus (step 2) http://forum.xda-developers.com/showthread.php?t=2303905
3. enter dialer code *#0808#
4. select MTP+ADB
5. reboot (may not be necessary)
My phone originally had nothing selected. I don't know how to go back to that unselected mode. I can't guarantee anything. It's working for me. My phone now connects in MTP mode within a second or two of connection (unless the phone is in the middle of a reboot, then that has to complete first.)
Chris000001 said:
I think I figured it out. I'm still on original MDK build. I don't know if that changes anything.
1. autorun.iso removed (may not be necessary, but mine is gone)
2. enable hidden menus (step 2) http://forum.xda-developers.com/showthread.php?t=2303905
3. enter dialer code *#0808#
4. select MTP+ADB
5. reboot (may not be necessary)
My phone originally had nothing selected. I don't know how to go back to that unselected mode. I can't guarantee anything. It's working for me. My phone now connects in MTP mode within a second or two of connection (unless the phone is in the middle of a reboot, then that has to complete first.)
Click to expand...
Click to collapse
Tried this on Sophisticated 2.5 . It's a 4.3 rom I get this: error: device offlineerror: device offline even though Link Status is Device Connected. My autorun.iso file was in /system/etc I renamed it. Changing the dialer code *#0808# to MTP works until I reboot. Same thing with dialer code *#7284#. I edited a file in /efs/carrier/HiddenMenu "OFF" changed to "ON" all in capital letters This survives a reboot.
But MTP doesn't
desertopal said:
Tried this on Sophisticated 2.5 . It's a 4.3 rom I get this: error: device offlineerror: device offline even though Link Status is Device Connected. My autorun.iso file was in /system/etc I renamed it. Changing the dialer code *#0808# to MTP works until I reboot. Same thing with dialer code *#7284#. I edited a file in /efs/carrier/HiddenMenu "OFF" changed to "ON" all in capital letters This survives a reboot.
But MTP doesn't
Click to expand...
Click to collapse
I'm on MK2 rooted and I have the same problem with the setting not surviving a reboot. Anyone have any other ideas?
Removing the file should work, if it's giving you a delay then my guess is either your computer or the device is trying to find the file. Back on my s3 and dna rom I had only removed the file and vzw installer didn't show up
Sent from my SCH-I545 using XDA Premium 4 mobile app
CovXX said:
Removing the file should work, if it's giving you a delay then my guess is either your computer or the device is trying to find the file. Back on my s3 and dna rom I had only removed the file and vzw installer didn't show up
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Removing the file does not solve the problem, it still connects as installer for a while before connecting as media device. It's not a huge problem, just annoying! I'm curious if everyone has this problem, or if it's just a few of us??
Zelmo88 said:
Removing the file does not solve the problem, it still connects as installer for a while before connecting as media device. It's not a huge problem, just annoying! I'm curious if everyone has this problem, or if it's just a few of us??
Click to expand...
Click to collapse
I have the same issue. I've tried looking through/changing settings in build.prop, default.prop and init.usb.rc with no luck. I need to do a little more searching to better understand init.usb.rc as a lot of the settings are jibberish to me.
Chris000001 said:
I think I figured it out. I'm still on original MDK build. I don't know if that changes anything.
1. autorun.iso removed (may not be necessary, but mine is gone)
2. enable hidden menus (step 2) http://forum.xda-developers.com/showthread.php?t=2303905
3. enter dialer code *#0808#
4. select MTP+ADB
5. reboot (may not be necessary)
My phone originally had nothing selected. I don't know how to go back to that unselected mode. I can't guarantee anything. It's working for me. My phone now connects in MTP mode within a second or two of connection (unless the phone is in the middle of a reboot, then that has to complete first.)
Click to expand...
Click to collapse
Running the Casual-gnote2 I get this: file/ Open Casual Script (go to location, click on the downloaded Casual-gnote2.jar) it opens and gives me this
Description for /home/wade/Downloads/CASUAL-GNOTE2-Hidden Menus.jar
File Not Found Error: /home/wade/Downloads/CASUAL-GNOTE2-Hidden Menus.jar.txt
Delete this debug line in MenuItemOpenScriptActionPerformed()
If I just open Casual-gnote2 and click DO IT I get this: error: device offlineerror: device offline
In both cases the Link Status = Device Connected
Intro
This is a guide for people who want to make some modifications to config files, or other files, on System partition but do not want to root their phone or install custom recovery in order to keep OTAs and some apps, which don't play nicely with rooted phones, working. Examples of those config mods could be changing DPI or changing volume levels etc, which you would only do once and forget about it.
While root allows you to do those kinds of changes from within android, this methods would require a PC.
If you are familiar with temporary booting into a custom recovery, skip to step 5.
The usual i am not responsible for any of your actions / bricked phones disclaimer applies.
Prerequisites
- A working adb / fastboot environment. Please use Android SDK, if you installed your adb and fastboot using other tools, things might not work, so please just install SDK, install Google USB Driver from SDK manager, install Platform-Tools from SDK manager (should be installed by default) and then add your sdk platform-tools path to your PATH environment variable to have it available in cmd in every path.
- Unlocked bootloader
- TWRP image for you phone (.img) https://twrp.me/devices/huaweinexus6p.html
Follow the [GUIDE] Unlock/Root/Flash for Nexus 6P for that.
Instructions
Here is an example of modifying DPI. I prefer build.prop method of modifying DPI because using the adb wm density command usually caused some issues for me, but modifying via build.prop didn't.
1 - With you phone ON, connect it to the PC and make sure adb is working by running
Code:
adb devices
and making sure that device is listed
2 - Reboot into bootloader. and make sure fastboot is good to go too. Run commands one at a time:
Code:
adb reboot bootloader
fastboot devices
3 - Place your TWRP image file in some easily accessible folder, for the sake of this example i will use C:\Mods.
4 - Temporary boot into TWRP (we are not flashing it here at all).
Code:
fastboot boot c:\Mods\twrp-2.8.7.0-angler.img
Here is where things may not work. If you don't see your phone boot into TWRP then either your adb / fastboot environment not setup correctly (installed via a tool instead of SDK) or your img file is corrupt.
One thing that works for me when TWRP refuses to boot is to restart cmd and issue the command again this closes and reopens adb/fastboot daemon.
5 - Once TWRP is up on your phone it may display a warning saying "TWRP has detected an unmounted system partition". Swipe to allow modifications at the bottom. This screen may not come up at all.
6 - Go to Mount >>> Tick System >>> Make sure "Only Mount System Read Only" is unticked >>> Press Back button
7 - Back on your PC check if your device is listed
Code:
adb devices
8 - Pull the file you need to modify from system partition to your PC. Please note the direction of the slashes:
Code:
adb pull /system/build.prop c:/Mods
9 - Now you should see build.prop in your c:\Mods folder. Use Notepad++ or something like that to edit the file. Find the line with lcd_density= and change it's value to whatever you need and save the file.
10 - Push the file back to your phone:
Code:
adb push c:/Mods/build.prop /system
11 - Reboot
Code:
adb reboot
12 - Profit.
Hope this will help anyone who is looking to do some mods without installing custom recovery and rooting your phone.
Cheers.
Would this work for adding the tethering bypass line in the build prop?
Yes it will. What's the line again I was looking for it the other day and couldn't find it...
Works are per OP's original post, tested and boosted the headphone volume without a problem.
Headphone path is /system/etc/mixer_paths.xml
So as per OP's example to pull: adb pull /system/etc/mixer_paths.xml c:/Mods
push: adb push c:/Mods/mixer_paths.xml /system/etc
I'm using the OP's "Mods" folder to demonstrate the file path but this may vary on your PC.
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
skrowl said:
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
Click to expand...
Click to collapse
You can certainly push the files to system partition and they will retain there after reboot. So if you know which files have to be pushed for SuperSU then give that a go. It shouldn't break anything.
I haven't tried pushing SuperSU files to system partition before so I can't guarantee that OTAs will work after this. The only way to find out is to try it i guess...
Can you run nandroids?
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
NCguy said:
Can you run nandroids?
Click to expand...
Click to collapse
Im not sure what you mean?
rohit25 said:
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
Click to expand...
Click to collapse
If it's on the system partition then I yes you can.
locolbd said:
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
Click to expand...
Click to collapse
I've never had a problem with changing DPI using this method on a nexus phone if that helps.
denk said:
Im not sure what you mean?
Click to expand...
Click to collapse
Can you run nandroids backups from TWRP by just booting into it?
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
I got this too when I flashed MOAB via adb sideload. I'm just wondering if the same warning appears with the adb push method. Also, the file's permissions don't need to be set after adb push?
My main concern is if Android Pay still works with the red triangle warning. Anyone?
FYI Flashing back to stock is no issue for me.
NCguy said:
Can you run nandroids backups from TWRP by just booting into it?
Click to expand...
Click to collapse
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
Thanks for trying it out! Sometimes OTA notifications take a little while to come up after reboot. But based on the warning Im afraid that they might be disabled now. It looks like it runs some sort of a check on the system partition to verify its legitimacy. So modifying files would be fine on it using this method but looks like adding them won't work.
TWRP just released their recovery with decryption support so you can just follow the standard procedure or just temporary booting into TWRP and rooting from there which works as well.
denk said:
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
Click to expand...
Click to collapse
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
NCguy said:
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
Click to expand...
Click to collapse
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
denk said:
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
Click to expand...
Click to collapse
Thanks a lot for that. I didn't unlock the bootloader. Ugh. Time to start over. To me nandroids alone make it worth the effort.
I am making this tutorial as I have had multiple versions of the LG LTE Leon and have used many firmware versions. I have created a stable method that has the least issues as I have had trouble with the latest firmware (MS34510f) disabling my root privileges. I have created a MEGA account specifically for all of the files necessary to complete this operation and have your device run smoothly. So, please follow my instructions exactly as stated and you should not have any issues. THIS PROCESS WILL REMOVE ALL DATA NOT SYNCED, DO READ BELOW NOTES IT IS VERY BENEFICIAL
Important Notes:
+This process will wipe all data that is not synced, it is important to ensure that no newer LG process are still on the device. Some might argue to leave data, to that I say good luck keeping your root and tethering without the device becoming suspiciously unstable.
+ I am not GUARANTEEING this will work on every model, but I have had an extremely high success rate with all Leon versions.
+ In this tutorial the process in which I remove Kingroot and replace it with SuperSu is for system stability. I find that most root functions I use seem to not work properly. (Wifi Tether Router and many others). So, I do recommend doing so.
+After the new OS is installed a MetroPCS splash screen will appear even if you do have T-Mobile. DO NOT BE ALARMED this firmware will not limit any functionality you had before, it will even help with tethering functionality.
Tutorial:
Let's Begin.
1. Download the link posted to obtain required files for this tutorial
Link: https://mega.nz/#F!PM4CQRqb!92kgIOnD0ZBY-8HVbtTwGQ
2. Open up LGFlashTool2014.exe
Begin by copying settings posted below, then click "normal flash"
3. Next click the "START" button
4. At this time, I recommend you verify all sync settings are to your liking and that all personal info needed is backed up
a. You have the option to throw all of your personal documents/pictures onto your SD card and removing it appropriately
(Go to: Settings - Storage - [scroll down to] Unmount SD card)
b. Next, navigate to Settings -Backup & reset [leave options default; both checked off] - Factory data reset - reset phone
c. Once reset it will most likely reboot, wipe, and then back to a OS. Now, you will Power Off entirely (make sure it is not plugged in so it will not go to charging mode)
d. Here is where we will hold down the Volume Up button with the phone unplugged from your PC. Then you must plug the USB into your phone.
e. A black screen with white text should post onto your screen, here we will continue to step 6
note: If this screen does not appear please power off and retry step d.
6. Next, follow the posted settings. Make sure to click the "Clear phone Software update Registry" button Then click "OK"
7. A new screen will arrive, and should begin the firmware download process. At this time it will take a few minute to load and should reboot to a fresh OS.
8. With the new OS in place, you can either follow the setup tutorial now or skip through for a later setup.
note: you can now insert your SD card
9. In the tools folder of the folder you downloaded copy the "mrw" folder to the Main Storage folder of your phone
10. Now copy the Kingroot apk to your downloads folder located on the main storage.
11. Go to Settings - About Phone - Software Info
At this time click the build number box a few times until it says you are a developer
12. Hit back until you are at the Setting menu, click on Developer options and check off "Stay Awake" and "Enable OEM Unlock" as well as "USB Debugging"
13. You may now run Kingroot, if it does not install root the first time it should flawlessly install the next.
14. After root is obtained, please go to your home screen and click the "Google Search" widget. Press Update Google Services and let it run. After that has been updated search for terminal emulator and install.
note: If the Play Store is acting fishy and force closing while typing in the search bar do not fret it will be fixed after reboot in further instruction
as an allternative use the jackpal.androidterm-1.0.70-71-minAPI4.apk provided in the "tools" folder
15. Open terminal and in a new window type: Su
16. Allow root usage and at this time type: sh /storage/emulated/0/mrw/root.sh
17. It will run with a few failed messages do not worry it should open SuperSu momentarily
18. Once SuperSu opens up allow it to update binaries using the "NORMAL" option but DO NOT REBOOT YET
19. At this time either download TWRP Manager from the play store or alternatively use the com.jmz.soft.twrpmanager-7.5.1.3-82-minAPI11.apk provided in the tools folder
20. Install and open TWRP Manager. Once opened click on device name and scroll until you see "LG Leon LTE (c50)"
a. Click on Recovery Version to Install and select "twrp-2.8.7.0-c50.img"
b. next click "Install Recovery" and if prompted for verification of install path and for install version select "YES" & "NORMAL"
21. After the TWRP setup is complete it may prompt you to reboot, if not click the arrow in the top left of the TWRP Manager screen and scroll down to "Reboot" and select "Reboot device"
22. After Reboot click TWRP Manager and verify a SuperSu prompt comes up if it hasn't already before the boot
At this point the device should be running smoothly. From here I prefer to do the following steps.
My Personal Setup after new install:
+Personally I like to install use a Root Uninstaller (I use 3C Toolbox Pro) and Uninstall and Backup all MetroPCS BloatWare including the Metro Browser.
+I also access the Hidden Menu by using the Dialer and Dial "2776348*#*"
- I scroll down to ApnUnlock and click to "Unlock APN"
- Then I navigate to Settings -Tethering & networks - Mobile Networks (I check off roaming data) - Access point names
--I then select the top APN and edit APN Type to: default,supl,mms,dun
---I click save from the top right selection, then turn on and off airplane mode
+If you are and Xposed user download "xposed-v79-sdk22-arm.zip","xposed-uninstaller-20150831-arm.zip", and "XposedInstaller_3.0_alpha4.apk" from: http://forum.xda-developers.com/showthread.php?t=3034811
-install the Xposed Installer, then Go to TWRP Manager, use reboot to recovery and from there click install and navigate to the "xposed-v79-sdk22-arm.zip" and install and reboot, it will reboot with a installing screen before your home screen, takes 5 minutes.
+I also use this AMAZING app "Wifi Tether Router", it is the only tethering app I use that works consistently (if you have an unlimited data plan). I get 30mbps up and down, playing many multiplayer games off my PC and PS4 averaging ping as low as 30 ! Setting I use for our device are in a post I created here: http://forum.xda-developers.com/leon/help/unlimited-metropcs-t-mobile-tether-t3290180
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Special Thanks to:
MrW0lf from www.W0lfdroid.com for the Kingroot to SuperSU scrip
Numerous users on the XDA forums I pieced all of this information with
Fabio Grasso for making the amazing Wifi Tether Router
Team Win for being creating an awesome utility that has saved me from numerous bricks creating a stable method
Xposed and the creators of awesome additions such as Lolistat, Lucky Patcher, Max Lock, and SNAPPREFS
Any feedback? Did I do Okay? Questions? Let me know!
Worked for me on T-mobile H345
Worked for me on T-mobile H345 any way to install a H340 firmware on it? I GeT a Binary not authorised when trying to flash.
kodacy said:
Worked for me on T-mobile H345 any way to install a H340 firmware on it? I GeT a Binary not authorised when trying to flash.
Click to expand...
Click to collapse
Apologies for the late response, I never received a notification of your posting. I would not recommend that as I believe the H340 has a different "radio" driver or cellular chip, If I'm not mistaken the H340 isn't even LTE, the H345 is. In that case it may be possible. One thing I suggest doing before wasting your time in using any other ROM is googling H345 vs Ms345, typically the phonemore.com results will provide you with an abundance of hardware specs and let you know if they're different! Just be weary of the newest MS34510f_00.KDZ firmware I believe it has an active unroot process I've had some stability issues. I am using MS34510D_00.KDZ for months and have had no issues whatsoever! Again, I'm sorry I got back to you so late, let me know how everything goes!
brad2192 said:
Apologies for the late response, I never received a notification of your posting. I would not recommend that as I believe the H340 has a different "radio" driver or cellular chip, If I'm not mistaken the H340 isn't even LTE, the H345 is. In that case it may be possible. One thing I suggest doing before wasting your time in using any other ROM is googling H345 vs Ms345, typically the phonemore.com results will provide you with an abundance of hardware specs and let you know if they're different! Just be weary of the newest MS34510f_00.KDZ firmware I believe it has an active unroot process I've had some stability issues. I am using MS34510D_00.KDZ for months and have had no issues whatsoever! Again, I'm sorry I got back to you so late, let me know how everything goes!
Click to expand...
Click to collapse
No problem thank you for your help!
will i still have metro service?
Port(usb or serial) not found! tried on, off, update mode, changing ports and unplugging every other port. any thoughts?
kap10nuka said:
Port(usb or serial) not found! tried on, off, update mode, changing ports and unplugging every other port. any thoughts?
Click to expand...
Click to collapse
Same here (firmware update) usb not detected when using the S/W update tool
After going all the way through this guide with a T-Mobile Leon, I do indeed have a Metro PCS ROM and root, which is great! Unfortunately, it also refuses to acknowledge my T-Mobile SIM. In fairness, I did not even insert a SIM for the first time (just got the phone) until the end of the process, but it shows as carrier locked which is significantly less than useful. I'll flash back to a TMO rom and put the SIM in to double check, but it's quite a bummer. Great job on the guide otherwise, though! It definitely did what it says on the tin; I have root and apart from the SIM lock which may be my fault somehow it works great.
Hey bud those links are no longer valid know where i can get them?
**Root access required**
Download:
- G900T_PE1_Batch_Debloater
Instructions:
1. Extract the G900T_PE1_Batch_DeBloater folder onto your desktop.
2. Turn on USB Debugging from Developer Options and connect your device to your *PC.
3. Double-click debloater.bat to launch the program.
4. Grant Root Access if prompted by your device.
5. Select "Light," "Medium," or "Extreme" **debloating and press "Enter."
6. Once complete press "Enter" to return to the Main Menu and select ***Reboot Device.
7. Last, select "Exit" from the main menu to end your session. Done!
* Make certain that you have Samsung Drivers installed.
** Use Notepad++ or other text editor to view/edit the lists of removed apps in debloater.bat file.
*** It is normal for apps to begin force closing prior to rebooting your device.
muniz_ri said:
**Root access required**
Download:
- G900T_PE1_Batch_Debloater
Instructions:
1. Extract the G900T_PE1_Batch_DeBloater folder onto your desktop.
2. Turn on USB Debugging from Developer Options and connect your device to your *PC.
3. Double-click debloater.bat to launch the program.
4. Grant Root Access if prompted by your device.
5. Select "Light," "Medium," or "Extreme" **debloating and press "Enter."
6. Once complete press "Enter" to return to the Main Menu and select ***Reboot Device.
7. Last, select "Exit" from the main menu to end your session. Done!
* Make certain that you have Samsung Drivers installed.
** Use Notepad++ or other text editor to view/edit the lists of removed apps in debloater.bat file.
*** It is normal for apps to begin force closing prior to rebooting your device.
Click to expand...
Click to collapse
Thx for this tool, not just for the sake of it, but for the sake of us newbies being able to learn some basics from reading a batch file as well.
Waltsmith
I have the Samsung drivers installed and USB debugging on, however, the bat file stays on "Waiting for device". Normally I would get a notification granting my comp privileges for the debugging but no dice.
Cdub1976 said:
I have the Samsung drivers installed and USB debugging on, however, the bat file stays on "Waiting for device". Normally I would get a notification granting my comp privileges for the debugging but no dice.
Click to expand...
Click to collapse
I get the same unless i right click and run as admin but when i hit 2 (medium) then go i get the following?
UPDATE: Nevermind the reason adb commands were not running was due to the custom kernel i was using. switched kernels and the debloater worked fine.
destructionj said:
I get the same unless i right click and run as admin but when i hit 2 (medium) then go i get the following?
View attachment 3808327
UPDATE: Nevermind the reason adb commands were not running was due to the custom kernel i was using. switched kernels and the debloater worked fine.
Click to expand...
Click to collapse
Interesting. Thanks. I think I flashed the rom and Shinysides kernel. I'll have to try it without next time.
Sent from my SM-G900T using XDA-Developers mobile app
Cdub1976 said:
Interesting. Thanks. I think I flashed the rom and Shinysides kernel. I'll have to try it without next time.
Sent from my SM-G900T using XDA-Developers mobile app
Click to expand...
Click to collapse
yep thats the one. i flashed over to PhoeniX Kernel cuz i couldnt find the stock PE1. The phone booted and debloater worked fine.
http://forum.xda-developers.com/gal...kernel-phoenix-kernel-v7-marshmallow-t3340407
If you plan on using this with the latest update GPG2, edit the .bat file and remove the last line for TmoWfcPrefs, this is needed to change wifi calling preferences.
T-mobile latest marshmallow unrootable
Chuki82 said:
If you plan on using this with the latest update GPG2, edit the .bat file and remove the last line for TmoWfcPrefs, this is needed to change wifi calling preferences.
Click to expand...
Click to collapse
Hi im using the latest marshmallow of t-mobile
Any tips on how can i root my device?
ElKapitan_10 said:
Hi im using the latest marshmallow of t-mobile
Any tips on how can i root my device?
Click to expand...
Click to collapse
http://forum.xda-developers.com/tmo...l/root-how-to-root-sm-g900t-firmware-t3358190
As far as I know my phone has 6.0..1 Marshmallow and all is stock. Will the debloater program work on it?
ElKapitan_10 said:
Hi im using the latest marshmallow of t-mobile
Any tips on how can i root my device?
Click to expand...
Click to collapse
Have you tried CF-Auto-Root?
Chuki82 said:
If you plan on using this with the latest update GPG2, edit the .bat file and remove the last line for TmoWfcPrefs, this is needed to change wifi calling preferences.
Click to expand...
Click to collapse
OK, so I am dependent upon WiFI calling at work, and I did this, but maybe it's because I have an 11 month old or I don't know what but I must not have saved the BAT file correctly. anyway, I broke my WiFi calling.
- EDIT: it works if I turn it on with the quick icon - but if I go to settings, and click more networks, then click wifi calling it just crashes settings every time. any ideas?
Thanks in advance.
See post number 8 in this thread.
Sent from my SM-G900T
Hi there, i've been trying to make some changes to my build.prop (mainly enable miracast...can't believe they would disable it!) and i've had a rather challenging time.
I am now stuck on how to pull the actual build.prop...when i enter the command i get a long list of ADB definitions but no file - at least not that i could find. I tried a few times, including directing the file to be saved on an empty drive in case i could not see it.
I have unlocked my boatloader and installed TWRP. Mounted the system then gone back and entered the commands in ADB....and i don't seem to be having any success. Any help would be appreciated.
thanks
m
Why not just edit it within the built in editors in most file explorers? I use Solid Explorer and it allows me to edit at will within the app itself, no pushing or pulling. Of course I back up my current one before doing anything to it
Tower1972 said:
Why not just edit it within the built in editors in most file explorers? I use Solid Explorer and it allows me to edit at will within the app itself, no pushing or pulling. Of course I back up my current one before doing anything to it
Click to expand...
Click to collapse
i'm not rooted...and i've read that you don't get OTA updates...and it's happened to me more than once that i have an issue with the phone, and i can't get service because it's rooted...
and i guess i thought it was too much trouble to get rooted, make the changes, and then unroot...but i could be wrong at this point?!
You won't get OTA with twrp either. You need stock recovery.
so i bit the bullet and rooted my phone...i was able to get the build.prop editor to work (at first i did not have busybox which it seems helps apps to realize you have root). So now when i go to unable Casting, i can turn it on from the top right of the cast screen, and my tv appears. I can select it and it starts to sync up...then the mircosoft display adapter shows that it's also trying to sync...and then it times out it seems. I've checked it with my tablet and my wife's phone...both work.
any suggestions?
I understand Miracast no longer works in Nougat. I'm still on MM with my 6P and it works, but if you're on 7, you may have lost that feature.
What about WUGS toolkit? Do you need to re rooted for that...ifnot thats what I always use to edit the prop. So much easier as it has most edits you'll make and you just choose.
you never needed to root i edit build.prop like this all the time
1. boot to twrp recovery
2. go to mounts and select system
3. adb pull /system/build.prop
4. make edits
5. adb push build.prop /system/
idk if your edit will work but thats how to do it without root and for some of the other things said in this topic you can ota in twrp but it will fail if modify anything like you just did