If any download links for the KDZ, video, Flashing software, etc. go down, please message me on Steam (sadcamp) asking me to put them back up.
Ultimate LG L9 P769BK (US TMOBILE) Compilation Guide
YES, SORRY, THIS IS A GUIDE FOR WINDOWS SKIDS ONLY
Hey, friends and developing friends. If you don't know me, and I'm fairly sure you don't, my name is Sadcamp. I've been a lurker who has benefited from the XDA forums for a long time. I've had 3 devices, HTC One S, LG P769, and LG D415. Currently using the two LG phones I have. That doesn't matter, though. Since I benefited from modding my phones so much that they've become very effective in all aspects; I decided I would like to give back during this wonderful holiday season. This is a compilation of all the tools and guides I've used to make my LG L9 P769BK an effective phone. This guide WILL NOT INCLUDE an unlocked boot-loader. I haven't seemed to find that, but I have found pretty much everything else.
Disclaimer: As always, I'm not responsible for what YOU DO TO YOUR OWN DEVICE. Use this guide at your own risk. It might work for me, but there is always that small chance that it might not work for you. Doubt it's there, but nobody expects the Spanish Inquisition.
This guide will include:
Part 1. Flashing the phone with its STOCK ROM.
-Chapter 1: New Phone
-Chapter 2: Phone is completely wiped and ready for the Stock ROM.
-Chapter 3: [SOFT-BRICK] Phone boots up with LG Logo and "Security Error".
Part 2. Getting ALL the apps neccesary to give it amazing functionality.
Part 3. Rooting & SU & Busybox
-Chapter 1: Rooting the Phone
-Chapter 2: Installing SuperSU
-Chapter 3: Installing Busybox's components
Part 4. Custom Recovery (CWM)
5. Xposed
-Chapter 1: Installing the framework
-Chapter 2: Installing modules
-Chapter 3: Activating modules
6. Extra Useful Information
_/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\_
PART 1.
CHAPTER 1. IF YOU GOT THIS NEW PHONE FROM A STORE OR WHATEVER, IF IT'S BRAND NEW AND YOU'RE READY TO START MODDING IT, SKIP RIGHT OVER TO PART TWO.
CHAPTER 2. MY DEVICE IS WIPED AND HAS NO ROM ON IT. I WANT TO INSTALL THE STOCK ROM.
Well then, let's begin. We're gonna have lots of fun.
Step 1. Acquiring the software needed to flash the Stock Rom.
I will include a download link to a software called "LG Flash Tool 2014". The software is very minimal and has a success rate of 100%. If not, try again. If it just doesn't work for you, go dig for a guide that you think may work for you, because I did and it took me forever to get this up.
Step 2. Acquiring the Stock Rom.
Here's the DL to the Stock Rom.
Step 3. Putting your phone into S/W mode.
Have a micro-USB, your phone, and your computer handy with you.
First, hold ONLY the volume up button on the phone, then plug in the Micro USB. Continue holding the volume up button until the S/W Upgrade screen shows. Then you can let go.
After this step, There's no point in touching your phone for the rest of this chapter.
Step 4. Using the software.
Watch this video.
Step 5. After using the software.
After the software has done it's magic, it should have booted up just like it would have straight out of the box. Literally. You're now good to go to part 2.
Chapter 3. MY DEVICE IS BRICKED AND I DON'T KNOW WHAT TO DO OMG IS IT USELESS ASDFHARGA.
Trust me, do not worry. I use to think the same thing, and I left my device untouched for months because I thought it was un-recoverable. This probably occurred because this specific device has a locked boot-loader and a very complicated algorithm that prevents us from flashing custom recoveries like normal people do. So, you probably have "Security Error" when you boot your phone up. No biggie. That just means that something attempted to compromise the boot-loader and it worked, but the modified code breaks the boot so it doesn't start up.
TL;DR, Simple boot problem. You will still have ALL the data you had before attempting to flash something on this device.
Step 0.5. Acquiring Stock ROM and LG Flashing Software. (.zips)
Step 1. Put the phone into S/W Mode.
Have a micro-USB, your phone, and your computer handy with you.
First, hold ONLY the volume up button on the phone, then plug in the Micro USB. Continue holding the volume up button until the S/W Upgrade screen shows. Then you can let go.
After this step, There's no point in touching your phone for the rest of this chapter.
Step 2. Using the software.
Watch this video.
Step 3. Finished.
The phone should boot up just as normal. Here's the condition. Your root is gone, your custom recovery is gone, all your SystemUI mods are gone, pretty much everything you did with Root is gone. All the Root apps and everything is still there, you just need to get Root again and go through the long process of re-modding your entire system.
TL;DR. Your Root, Recovery, and mods are gone. All your Apps, Data, etc. are still there, but all the preloaded software is back, and ready to be deleted again. Just after you root your phone, again.
Continue to Part 2.
_/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\_
Part 2. Loading up your system with some of (my picks) the best apps. By the time you read this, most of these apps will probably be outdated, but these are just if you don't have the time and patience to get all the apps from the Play Store and want to do it here and now.
Here is a link to a .zip with all the good apps you will need to get yourselves through the next parts.
This package includes (the free versions):
The Root Browser
LGPwn.apk (to root your system)
L9RecoveryInstaller (to install a recovery without having to soft-brick your phone)
Supersu.apk (for the binaries and stoofs)
BusyBox (because you need it in order to do half, if not, most of the things you do with root.)
After you unpacked, copied all these apps onto your newly-flashed phone, and have installed them all, continue on to PARTE DE TRES.
_/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\_
Part 3. Rooting, SU, and Busybox.
This is by far one of the most important sections in this guide, because if you screw up here, who knows what might happen to your device because you accidentally forgot to install something or un-check a small box you didn't notice. Aside from that, let's get the hell to it.
Chapter 1: Rooting.
So, I assume you have installed LGPwn.apk. Well, open that app. It will open a dialog box, you don't need to read any of that because I will describe everything in detail here.
Step 1. Open LGPwn and hit RootMe.
(It opens the Backup app.)
Step 2. Click RESTORE, then select INTERNAL STORAGE.
Step 3. Click Lgpwn, and start the restore.
What it does is basically gets a system snapshot and just inserts the root into the system of the backup file. When the restore completes, it should automatically reboot the phone. You can check now, it probably has root. If it doesn't, try again.
Go to Chapter 2 of Part 3.
Chapter 2. SU/SuperSU.
You basically need this app in order to manage who has all these superuser permissions and at what elevated permissions they can use it. Plus the hell loads of other options the app has been optimized for our pleasure.
Step 1. Install SuperSU.
Self Explanatory.
Step 2. Open it and update the binary. Please, for the love of god, update it using the Normal Install. It will take only a few seconds, and bam, you have it all updated and ready to go. See additional options in Settings.
Go to Chapter 3 of Part 3.
Chapter 3. Busybox.
This badassery contains, basically, a bunch of commands that helps optimize what you can use in your system. It over-all just optimizes your system to be more compatible with the hundreds of apps that require BusyBox. It's very worth it. Plus, we're going to need this in order to get our CWM Recovery on.
Step 1. Install Busybox.
Don't even need to comment here. Too late for that though.
Step 2. Open it up, and grant it SuperUser permission using the awesome app we just installed to organize those permissions.
Step 3. Simply press Install at the bottom left and do nothing more until it has successfully installed. If it failed, close the app and restart it. Try again. If it continues to fail, make sure you granted it superuser permission and all. When it's done, well, you're ready for the world of modding ahead of you.
Go to Part 4.
_/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\_
Part 4. CWM Custom Recovery. Probably not the most up-to-date CWM Recovery, but sufficient enough for your basic wiping and .zip installing needs. I have not tested other ROM installation through it, so I will not teach that here, since it may be unstable because of the locked boot-loader. You do that at your own risk. If you soft brick it or wipe your device and cant get it to work, Go to Part 1.
Step 1. Ensure that you have Root, SuperSU, and Busybox all installed and all their utilities (as mentioned in part 3) ready to go.
Step 2. Install L9 Recovery Installer and open it up.
Step 3. On default, it should say that it is not installed. Please, please, make sure you have the busybox utilities installed or THIS WILL NOT WORK. If you do, proceed and Install/Update the recovery.
Step 4. Hit CWM ICS/JB (stable), then Yes, Install recovery.
Step 5. Grant it SuperUser Permissions. In a matter of seconds, it should be finished. It will then say "Status Installed."
Info: When you boot up your phone, the bottom buttons will blink for a small period of time. That period of time is the time you have to boot into Recovery, by holding down the Lower Volume button whilst they are blinking.
Ensure that recovery is installed.
Then, move on to Part 5, almost there guys!
_/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\_
Part 5. Xposed Framework.
The Xposed Framework is an app, just like busybox, that uses utilities and commands to optimize customization, speed, and well, you know, Android stuffs. It contains hundreds of user-made applications that use the framework to, as mentioned, customize the shell and all.
Lets dig in.
Chapter 1: Installing Framework
Step 1. Download and Install the Xposed Framework app from repo.xposed.info
Step 2. Click on the Framework button in the app. Read the warning dialog box carefully.
Step 3. Install/Update the framework. Grant it Superuser permissions, and it should install them in a matter of seconds. You will be prompted to reboot, help yourself and do so.
Go to Chapter 2.
Chapter 2: Installing Mods.
Go ahead and do whatever you want with the mods. Just know that once you give them superuser permission and activate them through Xposed, unless you ask them to prompt SU permissions every time they try to make a change, they will have complete utter control to make any change they want without you knowing. For the most part, that shouldn't happen, so happy modding. Just warning you guys incase.
Chapter 3: Activating Mods.
The app will prompt you to activate and reboot the mods you install. If you don't do this, they won't work. Just saying.
_/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\_
There you go. The entire guide on how to Flash the Stock ROM, Root, install recovery, and Xposed too. Enjoy the hell out of your optimized device.
_/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\_
Extra Info:
1. HATE THAT PESKY QSLIDE BAR IN THE NOTIFICATION SCREEN THAT JUST TAKES UP SPACE? INSTALL THIS ZIP WITH RECOVERY AND IT GETS RID OF IT.
2. Get rid of ALL the preloaded apps you don't need with this Root System Uninstaller app.
_/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\__/\_
If I am missing anything, or have made anything unclear in the slightest way, please message me so I can make corrections and add more information. No need for donations of any kind, this is all for you to love and enjoy.
Related
Hi all! I'm really hoping that some Andriod guru out there can figure out the predicament I've gotten myself into. First a litte background info:
The other day I successfully flashed the new JI5 update to my phone. It worked great, and seems to have at least patched (not fixed) the majority of this phones shortcomings. But of course most of you already know all this.
I attempted to flash the same update to my wife's phone tonight, however as soon as ODIN finished doing it's thing the phone rebooted, and I now seem to be stuck in recovery with the following error:
update media, please wait
E:Can't mount /dev/block/stl10(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:copy default media content failed.
The process I used to flash the phone is pretty standard. Fired up ODIN, used ADB to throw the phone into download mode (Both our phones seem to be HW locked), pushed the update to the phone. The one thing I DID do differently this time was select the Re-Partition option, as I've noticed some strange issues with my phone since throwing JI5 on it. I figured that repartitioning the phone back to it's prestine state might fix the issues. I made sure to use the correct 512 PIT file, which I think I remember reading was responsible for setting up the system partitions, thus I figured I wouldn't have any problems. I've read about many others that routinely repartition their phones, so I didn't think this would be an issue. Her phone was bone stock, aside from being rooted. No OC kernals, lagfixes, etc.
I've tried to throw the phone back into download mode via adb, but it just reboots the device and it immediatly goes into recovery mode. Since the phone still boots and gets into recovery mode I'm thinking it's not bricked, but I'll be damned if I know what to do next!
So how about it, any guru's out there that have seen this problem before? Any way it can be fixed?
Update: Still borked and at wits end! Since I still apparently have the ability to reinstall packages via recovery I'm hoping that there is a way to reflash the OS by utilizing a crafty update.zip file. Based off what I've read so far, I simply need to reflash to stock OS to get things rolling again, but I can't get the damn thing into download mode! So close, yet so far away. Thank you Samsung QA! I guess this is what I get for not clockwork modding her phone prior to working on it. But still, frigging ridiculous that this company is sending out broken hardware and untested products.
If anybody happens to know a way to utilize the recovery console to flash a firmware revision (without using clockworkmod recovery), or possibly how to perform a fix action via ADB, any info you can lend to me would be much appreciated.
Bumping for the sake of my sanity.
Anyone have any ideas as to how to fix this thing? I'm a hair's-breadth away from donating this thing to willitblend.
First I must scold you for not having Clockwork Recovery Flashed, it is the first thing you do when you have root. Period. Nothing else takes priority over being able to save your phone.
Secondly I must praise you for asking this in Q&A / General, NOT DEV! I FUC*ING HATE THAT! So thanks!
Steps to fix your wife's phone:
Step 1: Download attached zip, and put on phones internal SD. (adb push update.zip /sdcard/update.zip)
Step 2: Select Re-Install Packages from Stock Recovery Menu.
Step 3: Phone may reboot, if so see step 2. If phone enters clockwork go to step4.
Step 4: Flash Rom. Flash a full rom that is flashable via Clockwork. THAT OR::: try adb reboot download from clockwork.
Step 5: Reroot phone, install clockwork recovery (rom manager on market).
Optional: If all this doesn't work feel free to purchase my Vibrant, link in Sig
Edit: Also don't just do things you don't understand, like check repartition
Thank you sir! You're a saint!
zaduma said:
First I must scold you for not having Clockwork Recovery Flashed, it is the first thing you do when you have root. Period. Nothing else takes priority over being able to save your phone.
Secondly I must praise you for asking this in Q&A / General, NOT DEV! I FUC*ING HATE THAT! So thanks!
Steps to fix your wife's phone:
Step 1: Download attached zip, and put on phones internal SD. (adb push update.zip /sdcard/update.zip)
Step 2: Select Re-Install Packages from Stock Recovery Menu.
Step 3: Phone may reboot, if so see step 2. If phone enters clockwork go to step4.
Step 4: Flash Rom. Flash a full rom that is flashable via Clockwork. THAT OR::: try adb reboot download from clockwork.
Step 5: Reroot phone, install clockwork recovery (rom manager on market).
Optional: If all this doesn't work feel free to purchase my Vibrant, link in Sig
Edit: Also don't just do things you don't understand, like check repartition
Click to expand...
Click to collapse
Thanks for the fast reply! And yes, I feel retarded for not clockworking her phone. In my defense, I thought I knew what I was doing when I ticked the option, as I had read countless threads about repartioning the phone. I think the problem is that the JI5 update is an incremental update, not a full OS. By repartitioning and flashing I think the process removed some key OS files. Or not, I'm no expert when it comes to this OS.
Anyhoo, I tried pushing the file to the sdcard, however I am getting a permission denied error message. I've verified that the directory exists via the shell command, so I seem to be having some kind of a permissions problem. The root on her phone must have been undone, as when I try to enter SU I get the same permission denied error message. Is there a way around this?
Thank you for all the assistance thus far!
So while in recovery mode, I can see both drives showing up in disk manager and windows explorer on my computer, however they are grayed out. Typically at this point one would hit the "mount" button from the dropdown menu on the phone, but obviously this action is currently out of grasp due to my problem. Is there a way to manually mount the sdcard via adb?
I kind of figured that adb pushing stuff to the SDCARD didn't require root access, as I was always able to mount the two stores without root permissions from the phone...
I'm rather curious now. Has any one tried using the adb push command to copy files to the /sdcard directory on their phone without root? Everything I've read makes it sound like this should be possible, unless the phone is just that messed up.
Any and all replies appreciated!
This post is just my attempt to help less savvy users go from a fully locked/unrooted Rezound to unlocked, rooted, and running Ziggy's kernel. Really, this is just a list of links that should be followed in order (and maybe a few extra notes for clarification). Be sure to thank the respective devs for their efforts.
As of the time I'm writing this, there is no way to get the phone back to "Locked" once you've "Unlocked" it. The phone will show "Re-locked" if you relock it so know that until someone figures something out, Verizon WILL KNOW that you've unlocked your phone once you do it IF they bother to check and know how. It's your gamble, but to date, I've not heart of Verizon detecting root/unlock and refusing service to one person I can confirm. Said another way, you can "un-root" your phone (remove su and SuperUser), but that won't hide the more important fact that you've unlocked it. Consider this before continuing. Unlocking VOIDS YOUR WARRANTY. You accept responsibility for following this guide. Myself and other devs only provide information.
In general, here is what you will be doing:
Using the HTCDev.com site to submit your phones key and get an unlock.bin that you can use with fastboot to unlock your phone. NOTE: This WILL WIPE YOUR PHONE. I suggest using a temp-root method to first install Titanium or similar app, and do a app/data backup. This way when you're done, you can restore apps/data and be just about where you were when you started, only better.
Use the zergrush perm-root method to obtain permanent root and install SuperUser.
Install a customer recovery that will allow you to do a nandbackup and then install other roms/kernels (needed for the next step also).
Install Ziggys custom kernel which addresses some important issues for this phone and provides some other nice features.
NOTE: If you intend on flashing one of the newer ROMs ("newer" as of 2012-03-24) that require the 3.11.602.22 firmware, use Scott's directions HERE then come back and continue.
Now for the actual steps:
UNLOCKING - First visit THIS post for detailed instructions on how to unlock your device. This is required for permanent root and just about everything else following. This WILL VOID your warranty as the post says. This will also WIPE your device so again, I suggest first using THIS temp-root method so you can install an app like Titanium Backup to backup your apps/data.
PREPARING ADB - Once you have unlocked and your phone has rebooted, hit the home key to skip HTC Setup (no point doing it just yet really). Now hit, menu, settings, Applications, and check "Unknown Sources" (for good measure), then "Development" and check the box "USB debugging". I recommend then backing up a screen and un-checking "Start automatically", but that's my preference, not a requirement.
CONFIRMING ADB - At this point, I'm going to assume you already have ADB installed and known how to invoke the command because there are at least 9,999,999 tutorials online explaining this. Go ahead and open a cmd prompt and run "adb kill-server" and then "adb devices" and ensure that your device (if you see one, then you should be fine) shows up.
ROOTING - Now visit THIS thread and hit the less-than-obvious link titled "Download - OneClickRoot" to download the zip containing the tool. Follow the directions in that thread to permanently root your phone.
Boot fully into Android before proceeding.
RECOVERY
PREPARE RECOVERY.IMG - Visit THIS thread and download the attachment. Extract "recovery.img" from the zip and place it in a folder from which you can successfully run ADB. NOTE: If you haven't already, putting the adb.exe files folder in your PATH will let you run adb from anywhere. Same goes for fastboot. This makes life with Android tweaking/hacking MUCH easier.
FLASH RECOVERY 1/2 - Now "CD" into the folder (HERE you can find more about the CD command) with recovery.img and run the following command: "adb reboot bootloader". Once the phone has rebooted into the bootloader (a white screen with text menu, should say "*** UNLOCKED ***" at the top now). In white with a red background you should see "FASTBOOT USB". If so continue, if not, ask for help
FLASH RECOVERY 2/2 - The moment you run the following command, you should see a vertical bar on the upper-right hand corner of your phones screen. If so, it's working as expected. In your CMD window, run the following command "Now "CD" into the folder with recovery.img and run the following command: "fastboot flash recovery recovery.img"
REBOOT TO RECOVERY - If you have't touched the volume keys, "BOOTLOADER" is selected and pressing power will take you to the bootloader where you can then use the arrow keys to select "RECOVERY" and again press the power button to get into recovery. Otherwise, reboot any way you see fit and once running, use "ADB reboot recovery" to get into recovery easily.
KERNEL
DOWNLOAD FILES - First download the two files from THIS post (NOTE: The OP most may end up with more updated files, but as of the time I'm writing this, these are the way I suggest).
PUSH FILEs 1/2 - If you haven't already rebooted into recovery, review the previous steps and get your phone into recovery ("ADB reboot recovery" is my preference). Now "CD" into the folder containing the two files downloaded in the previous post. From here, I will use the file names as they were when I downloaded. Yours could be slightly different so adjust accordingly. In the recovery use the volume keys to navigate to the "Mounts" menu and then "Mount /sdcard". Use the Power button each time to select the menu option.
PUSH FILEs 2/2 - Now from your CMD window (the one in the folder containing the two kernel files), run the following commands: "adb push FlashMeInRecovery.zip /sdcard/" and then "adb push PH98IMGZIGGYUNSIGNED.zip /sdcard/PH98IMG.zip".
FLASH FILE 1/2 - Now use the back arrow (the capacitive one) to go back to the main menu and then select "Flash zip menu" and then "Choose zip from sdcard". You'll then get a list of sdcard contents. The file is likely toward the bottom. Select "FlashMeInRecovery.zip" and follow the directions to confirm flashing.
FLASH FILE 2/2 - Select the "Return" menu option, then "Developer Menu" and then "Reboot to bootloader". By default "BOOTLOADER" is already highlighted and you just need to use the power button to select it. The phone will now scan the SDCARD for "PH98IMG.zip" and when it finds it, you will be prompted to Press "<VOL UP> Yes" to flash the files.
If you get the notorious "MainVer Error", use one of the following guides to get past the error. NOTE: Neither of these are for the faint-of-heart and the first I consider easier, does carry some real danger if done incorrectly.
Option 1 - Follow the guide HERE <-- Requires the use of a HexEditor and one is recommended if you don't have a preferred one yet.
Option 2 - Follow the guide HERE <-- Requires modification of the PH98IMG.zip you're trying to flash and sometimes this can be problematic. Either way, it provides an excellent description of why the error occurs.
FINISH - Once the 2nd kernel file is flashed and you're prompted, press power to reboot. After your phone is running again, use the following command to rename the kernel file so it doesn't cause you trouble later in the bootloader (but still keep it handy): "adb mv /sdcard/ext_sd/PH98IMG.zip /sdcard/ext_sd/PH98IMGZIGGYUNSIGNED.zip"
If this guide has helped you and you want to show thanks, just hit the "Thanks" button at the bottom of this post. It's not a donation or anything like that, just a counter used here on XDA
I will try to keep this post refreshed as newer files become available, as things get easier, or things change. If you see an error/typo/concern with these directions, PLEASE PM me and don't muddy up the thread. If YOU will do this, "I" will not only try to maintain the post, but I will also try to add/maintain an FAQ post as needed.
Btw, in case you recognize me and are wondering why I've posted here, it's because my site is dead due to childish drama, I still want to help the community and this seems the most reasonable way to do so for now.
EDITS:
20111230_1804 - Added a hint and link about the "CD" command for users who aren't familiar with "DOS" like commands.
20120101_1923 - Added a direction to boot into Android after rooting.
20120101_2325 - Added warning about unlock/relock and warranty in BIG RED text.
20120208_1709 - Added instructions on how to handle the "MainVer" error.
20120324_1636 - Added note about using 3.11.602.22 based ROMs and linked to Scott's (CleanROM) directions.
Great guide, thanks! Worked just fine and wow this thing is fast as BALLS
Using SetCPU to tweak and monitor, any clue on what the best governor is for this kernel?
EDIT: Reading original post about kernel from Ziggy, "lagfree" governor is available, using that now.
Thanks!!!!!
may i flash kernels on custom rom
or has to be stock rooted?
qudwis said:
may i flash kernels on custom rom
or has to be stock rooted?
Click to expand...
Click to collapse
this kernel is based off of the one made for gingerbread, so as long as the ROM you're running is a Gingerbread ROM, you can, or should be able to use this kernel with it.
*EDIT* I believe it may matter whether the ROM is Sense or AOSP based as well. currently we only have sense roms so it doesnt much matter, but it will down the road.
one more question.
i have cwm for recovery. since cwm don't have developer menu,
do i need to change to Amon Ra recovery?
and if i do, how do i change?
The guide is clear, succinct, and accurate. Everything worked perfectly - thanks so much.
I could've got so much more work done over the last two days if I had a tutorial like this! Untold hours have been spent combing these boards to piece together this whole process. Thanks for taking the time to do this for everyone.
Seemed to work!
I only did the recovery / kernel part since I had done the rest previously. For some reason it partially wiped my phone storage and SD card. Directories are there, but nothing is in them. No idea what happened, but oh well.
At least now I can start messing with stuff.
How do you unroot from the HTCdev method? I need to return my Rezound and get a different one tomorrow. Can someone please point to the correct guide or tutorial? Thank you very much!
-brett
bal1985 said:
How do you unroot from the HTCdev method? I need to return my Rezound and get a different one tomorrow. Can someone please point to the correct guide or tutorial? Thank you very much!
-brett
Click to expand...
Click to collapse
Unrooting is just a matter of deleting "su" and uninstalling SuperUser, but it will hardly matter since your device will still be marked as "re-locked" if you use fastboot to relock it. There's no way at this point to hide that it's been tampered with and that's why I and most other devs have made such a point of clarifying that your warranty will be void one you unlock.
On the other hand, I can tell you that out of the 15,000+ users on my site and years in the Android community, I've never ONCE heard of Verizon saying "your device is rooted so we won't...."
Just uninstall SuperUser and do a factory reset/wipe and hope for the best. It's hardly worth their time to check and in the stores, more reps are too ignorant to know to check, let alone how to do it or if they do, they're likely unmotivated to do so since a warranty return won't go against them (unlike a return).
rainabba said:
This post is just my attempt to help less savvy users go from a fully locked/unrooted Rezound to unlocked, rooted, and running Ziggy's kernel. Really, this is just a list of links that should be followed in order (and maybe a few extra notes for clarification). Be sure to thank the respective devs for their efforts.
FLASH FILE 1/2 - Now use the back arrow (the capacitive one) to go back to the main menu and then select "Flash zip menu" and then "Choose zip from sdcard". You'll then get a list of sdcard contents. The file is likely toward the bottom. Select "FlashMeInRecovery.zip" and follow the directions to confirm flashing.
FLASH FILE 1/2 - Select the "Return" menu option, then "Developer Menu" and then "Reboot to bootloader". By default "BOOTLOADER" is already highlighted and you just need to use the power button to select it. The phone will now scan the SDCARD for "PH98IMG.zip" and when it finds it, you will be prompted to Press "<VOL UP> Yes" to flash the files.
Click to expand...
Click to collapse
This looks very clear and helpful. I'm not ready to use it yet, still need to study up on all this root stuff but thanks for posting.
Just wanted to point out that there may be a small and not so important typo. Both flash files are 1/2, shouldn't the second one be 2/2?
I have downloaded both files into my sd card, flashmeinrecovery.zip worked fine. The pmhimg.zip keeps saying aborted. I am running cwm, should I be running a different rom? What can I do to get the pmh zip to work?
I downloaded them via the qr codes, and they are in the download folder on my sd card. I did change the name on the second zip.
You have to put the ph zip in the root of the sd card. Not in a folder
sent from my newly unlocked Rezound
pwned3 said:
You have to put the ph zip in the root of the sd card. Not in a folder
sent from my newly unlocked Rezound
Click to expand...
Click to collapse
Ok, I did that. Now when I get into hboot, it just asks if I want to update, if I do, it updates, what I dont know, then wants me to reboot, and if I boot back into hboot, it wants me to update again. But I can power up normally. Is this correct or am I missing something?
Just reboot normally after flashing
sent from my cm7 rooted fire
And move the file. It will read it every time you go into the bootloader
sent from my cm7 rooted fire
Followed instructions and kernel would not flash. All steps completed without errors and still has same kernel. Any advice?
rainabba said:
Unrooting is just a matter of deleting "su" and uninstalling SuperUser, but it will hardly matter since your device will still be marked as "re-locked" if you use fastboot to relock it. There's no way at this point to hide that it's been tampered with and that's why I and most other devs have made such a point of clarifying that your warranty will be void one you unlock.
On the other hand, I can tell you that out of the 15,000+ users on my site and years in the Android community, I've never ONCE heard of Verizon saying "your device is rooted so we won't...."
Just uninstall SuperUser and do a factory reset/wipe and hope for the best. It's hardly worth their time to check and in the stores, more reps are too ignorant to know to check, let alone how to do it or if they do, they're likely unmotivated to do so since a warranty return won't go against them (unlike a return).
Click to expand...
Click to collapse
so I just unistall SU from the Market? Or do I have to go in with Root Explorer and delete the file? once that is done don't I have to lock the bootloader using that htcdev guide again?
remmy5r said:
Ok, I did that. Now when I get into hboot, it just asks if I want to update, if I do, it updates, what I dont know, then wants me to reboot, and if I boot back into hboot, it wants me to update again. But I can power up normally. Is this correct or am I missing something?
Click to expand...
Click to collapse
Following step 7 specifically prevents you from having to deal with that. So long as the PH file exists in your sdcard root, when you go into bootloader, you will be prompted. Once your running normally, just go follow step 7 and you'll be good to go.
Ladies and gentlemen, I would like to present to you all a formal guide to venture into one of the best smartphones in the market, the underdog to the other mass marketers, the Sony Xperia Z3v for Verizon!
*Please note I am not responsible for any bricking, destruction of your device, alien invasions, or any other problems. It is up to the user's choice to seek out what is done on your device on your own terms.*
This is the method I would recommend that's much quicker and efficient is Kingroot. I know there were some previous controversy about what could be behind Kingroot, but from what I will show here is using Kingroot as leverage to gain access quickly into my prerooted Lollipop firmware that can stand alone after removing Kingroot afterwards.
1. Have the Z3v in your possession.
2. Google "Kingroot" and download for Android and run the rooting process there.
3. Download "Superuser" from the Play Store to have the binary to run root fully. (Optional just in case the next step doesn't work)
4. Install XZDualRecovery (grab the flashinstaller for the Xperia Z3) to install TWRP from here: http://nut.xperia-files.com/path/XZ...40vagg0tpcrnm1vlnt63je5&randomizer=_ehkq575vz
(The link is subject to change, so if that happens, navigate through here: http://nut.xperia-files.com/)
5. Download my new 5.1.1 prerooted Lollipop zip from my thread here: http://forum.xda-developers.com/z3/...08-prerooted-lollipop-5-1-1-23-4-b-0-t3338967
6. Access TWRP by opening an app called NDR Utils in your App Drawer
7. Flash my zip through the install button and now you'll be on the latest prerooted stock build of Lollipop with a few mods.
Optional Step 8. Uninstall any traces of Kingroot from your phone and you're good to go. This step may already be done for you after you flash the prerooted because reportedly there were already no traces left behind. Enjoy!
Thanks to the following people:
@zxz0O0, for achieving root for our Z3v
@jal3223, for helping me as much as you can to guide me through myself
@[NUT], for the custom recovery to install onto our Xperia devices
Please hit thanks for the all in one guide to freedom!
hey man,
im getting stuck after running root.bat
i get javaruntime =null error
did you experience this and do you know what i should do.
also the java link you provided is dead
Mountainfisher said:
hey man,
im getting stuck after running root.bat
i get javaruntime =null error
did you experience this and do you know what i should do.
also the java link you provided is dead
Click to expand...
Click to collapse
At that point, that's what was stopping me too. What I did was just go ahead and redownload the root files, uninstall all Java on my desktop and resintall it. Then try again to make it work.
GigaSPX said:
At that point, that's what was stopping me too. What I did was just go ahead and redownload the root files, uninstall all Java on my desktop and resintall it. Then try again to make it work.
Click to expand...
Click to collapse
What do you think are chances are of unlocking our bootloader now? Sony's unlock site will give us an unlock key for our device. I'm not sure what is holding us up.
Oh No, I vowed to stop messing with my phones....
jal3223 said:
What do you think are chances are of unlocking our bootloader now? Sony's unlock site will give us an unlock key for our device. I'm not sure what is holding us up.
Click to expand...
Click to collapse
Personally, I'm fine without doing custom ROMs. I like how Sony's UI works as it is and I prefer it that way than going full AOSP like any other Nexus phone. I just like to buy what came with the package as is intended.
Bobby Buggs said:
Oh No, I vowed to stop messing with my phones....
Click to expand...
Click to collapse
This is well worth to do. I installed Xposed, and unlocked some awesome stuff. Such as using Superior Auto mode with 15 mp right off the start or 20.7 MP. Greater the details, amazing functions made.
Oh and also, I will now proceed to upload the flashable zip of the latest FW being prerooted. Just so there's some better things to deal with.
Ive uninstalled java, reinstalled java, factory reset twice, still the java runtime error =null
im bout cooked for today
Mountainfisher said:
Ive uninstalled java, reinstalled java, factory reset twice, still the java runtime error =null
im bout cooked for today
Click to expand...
Click to collapse
This guy said it took him 10 times so I am going to keep trying till it works!
sthrnsprtsmn said:
I was getting the same errors. I had to factory reset the phone multiple times and redo the steps. On about the 10th time, it took. I skipped the phone set up steps, and kept a root checker apk on my sd card to speed it up. Also, I unchecked the verify apps over USB. I didn't see that mentioned anywhere.
Time to send my donation. Thank you very much @zxz0O0
Click to expand...
Click to collapse
Perhaps I'm missing something. What is the secret to getting flashtool to recognize the ftf after you have moved it to the root of the firmwares folder and first open flashtool. A pop up tells me to move the file but it is already there. I love and loathe this hobby.
JediDru said:
Perhaps I'm missing something. What is the secret to getting flashtool to recognize the ftf after you have moved it to the root of the firmwares folder and first open flashtool. A pop up tells me to move the file but it is already there. I love and loathe this hobby.
Click to expand...
Click to collapse
Your C:/flashtool/firmware folder should be empty. Place the firmware you want to use in /USERNAME/.flashtool/firmware
make sure you uninstall all java and re install fresh!! that was what was holding me up
Someone should do a youtube of this process live
6. Follow the instruction exactly as stated then proceed. , I dont see the instructions.
Of course my phone is at 0 .E. 1 .44 build, so that means I have to go back to the older build, do this root and then reflash to the 1 .44 build?
Bobby Buggs said:
6. Follow the instruction exactly as stated then proceed. , I dont see the instructions.
Of course my phone is at 0 .E. 1 .44 build, so that means I have to go back to the older build, do this root and then reflash to the 1 .44 build?
Click to expand...
Click to collapse
You completely skipped steps 1 and 2 because you're on the latest build. Step 6 is following the instructions that are listed within the exploit.bat.
You won't be reflashing the latest until you've followed through to the new list of steps that occurs after 9.
Giga, sent you a Pm
---------- Post added at 09:31 AM ---------- Previous post was at 09:20 AM ----------
Call me a idiot but I dont see any instructions, I ran the exploit file and my screen shows daemon started successfully but nothing else
ROOT Z3V
This is how I did it. following GigaSPX's instructions
1. If you are NOT on stock shipped ROM, 23.0.E.0.376 / R15B, please download here
Downloaded the firmware
2. After having downloaded the FTF, please proceed to using the flashtool to flash your phone. Place your FTF in the firmware folder of the .flashtool folder to run from therein this process I found out that you don't want to just copy the files but use cut and paste. and I added the firmware i downloaded. You may uncheck Data from wipe.*
I turned the phone off, held volume down and connected the phone to the USB cable attached to the pc.
3. Download the files to root right here.
downloaded the root files but I actually downloaded these files http://forum.xda-developers.com/showpost.php?p=60529402&postcount=232
4. Grab the Java Development Kit from here. To prevent issues, you may want to uninstall Java existing on your computer to do a fresh install of this.
5. Extract the zip of the root files into a place and then run exploit.bat.
when i reached this the phone asks to let your pc connect, then you click ok... (im assuming you have developer options usb debugging enabled and allow unknown sources checked) When the exploit stops, go to your phone and go to Developer options and click on Select Debug app and choose the test2app then enable "wait for debugger"
6. Follow the instruction exactly as stated then proceed.
because I used that those root files, the process ended here since that root runs automatically after the exploit ends. phone restarted and verizon will give you the OTA update, which BTW it doesnt make you loose root
7. Once it stops at a line saying "please continue to press any key", go back to the folder named as "root" and run root.bat from there.
8. Your phone will reboot from here and you will enjoy root. If it doesn't work, try again a few times while going to command prompt and enter the following line to do a fresh cleanup before trying again:
I hope this is not too confusing. if it is I apologize. let me know and I'll take it down so I don't confuse people more
xratablancax- After you run the exploit file the root one opens by itself? I am not having this. I have to manually open both the exploit once it is finished, I then have to click the root method to get that going. Trying to clarify. I haven't gotten past the Java Null error. I know a few folks that might have me do this for them and I would like to do it for them. Lets say I don't get it. Will I still receive an OTA to get back to the latest? Or will I have to build or find an FTF to do so. Thanks.
Great write up!
Thanks for the time and effort you put on rooting our abandoned Z3v.
Really look forward to flashing the Pre-rooted firmware that you're about to made
xratablancax said:
This is how I did it. following GigaSPX's instructions
1. If you are NOT on stock shipped ROM, 23.0.E.0.376 / R15B, please download here
Downloaded the firmware
2. After having downloaded the FTF, please proceed to using the flashtool to flash your phone. Place your FTF in the firmware folder of the .flashtool folder to run from therein this process I found out that you don't want to just copy the files but use cut and paste. and I added the firmware i downloaded. You may uncheck Data from wipe.*
I turned the phone off, held volume down and connected the phone to the USB cable attached to the pc.
3. Download the files to root right here.
downloaded the root files but I actually downloaded these files http://forum.xda-developers.com/showpost.php?p=60529402&postcount=232
4. Grab the Java Development Kit from here. To prevent issues, you may want to uninstall Java existing on your computer to do a fresh install of this.
5. Extract the zip of the root files into a place and then run exploit.bat.
when i reached this the phone asks to let your pc connect, then you click ok... (im assuming you have developer options usb debugging enabled and allow unknown sources checked) When the exploit stops, go to your phone and go to Developer options and click on Select Debug app and choose the test2app then enable "wait for debugger"
6. Follow the instruction exactly as stated then proceed.
because I used that those root files, the process ended here since that root runs automatically after the exploit ends. phone restarted and verizon will give you the OTA update, which BTW it doesnt make you loose root
7. Once it stops at a line saying "please continue to press any key", go back to the folder named as "root" and run root.bat from there.
8. Your phone will reboot from here and you will enjoy root. If it doesn't work, try again a few times while going to command prompt and enter the following line to do a fresh cleanup before trying again:
I hope this is not too confusing. if it is I apologize. let me know and I'll take it down so I don't confuse people more
Click to expand...
Click to collapse
JediDru said:
xratablancax- After you run the exploit file the root one opens by itself? I am not having this. I have to manually open both the exploit once it is finished, I then have to click the root method to get that going. Trying to clarify. I haven't gotten past the Java Null error. I know a few folks that might have me do this for them and I would like to do it for them. Lets say I don't get it. Will I still receive an OTA to get back to the latest? Or will I have to build or find an FTF to do so. Thanks.
Click to expand...
Click to collapse
What line of code
JediDru said:
xratablancax- After you run the exploit file the root one opens by itself? I am not having this. I have to manually open both the exploit once it is finished, I then have to click the root method to get that going. Trying to clarify. I haven't gotten past the Java Null error. I know a few folks that might have me do this for them and I would like to do it for them. Lets say I don't get it. Will I still receive an OTA to get back to the latest? Or will I have to build or find an FTF to do so. Thanks.
Click to expand...
Click to collapse
If you look at the link I provided, that gives your a different set of root files, one that the Exploit runs and right after root runs automatically.
VERY IMPORTANT... YOU NEED TO FLASH YOUR DEVICE TO STOCK ROM, YOUR DEVICE NEEDS TO BE IN ROM, 23.0.E.0.376, BACKUP DEVICE, FLASH THEN ROOT THEN OTA UPDATE
BACKGROUND: OK this question gets asked every day, by members of varying skill levels, so this is intended to be a one stop guide on how to root, no matter what firmware version you're running. Yes this will trip Knox, no that will have no effect on your phone whatsoever, and there are ways to reset the Knox counter. If worst comes to worst and you need to bring your phone in for warranty and they give you any sort of lip for the Knox counter, tell them Kies broke your phone and they da** well better fix it (worked for me with multiple Samsung devices).
That said, this will root the SM-G900T (T-Mobile Galaxy S5) no matter what version of android you're running. Make sure you read this entire post and understand everything before trying anything.
PREPARATION: Disclaimer out of the way, now for the fun stuff. First, preparation, you need to download the following files to your PC: Odin 3.11.1 (this is Odin, it flashes stuff to Samsung android phones); twrp-3.0.2-2-klte.img.tar (this is the custom recovery we're going to use). Extract the Odin zip file to your PC's Desktop. Download the file named UPDATE-SuperSU-v2.79-20161211114519.zip somewhere to your phone's internal storage or external SD, doesn't really matter which. Now in your phone's settings, go to About device, scroll down to Build number. Repeatedly tap Build number until your phone tells you Developer options have been turned on. Go back and enter developer options, enable USB debugging and hit OK. At this point you'll want to connect your phone to your PC with USB, just to make sure it actually connects (it should). If not, you can download the USB drivers from here (scroll down to Downloads section), but most likely this won't be necessary. OK prep work done, now we get to actually get started on rooting our phone. Make sure your phone has at least 50% battery, this is always a smart safety step.
STEPS:
Power off the phone. Boot into download mode (hold vol-, home, and power all at once in that order), then hit vol+ to continue
Run Odin (double click the Odin3 v3.11.1.exe file). Click the Options tab, disable the "Auto-Reboot" option and double check that "Re-Partition" option is disabled (it should be by default), this is critical to success
Connect phone via USB. Hit AP button in Odin, select the twrp-3.0.2-2-klte.img.tar
Flash (click start). When it's done, the progress bar will be full and Odin should say "PASS!"
Hold vol+, home, and power (all at once, in that order) to boot into recovery. THIS MUST BE DONE BEFORE REBOOTING NORMALLY!. TWRP might ask if you want to let it modify your system or keep it read only. I would highly recommend you let it modify your system, you might be OK keeping it read only, but I cannot guarantee that. You will be fine letting it modify your system, that I can guarantee.
Hit the install option and navigate to the SuperSU zip file that is saved to your tablet. Select it and swipe to install.
Reboot system (normal reboot). If TWRP should ask you, do not let it install supersu the way it wants to (do not swipe to install, just reboot).
When android is booted, run the superSU app and go into settings, disable the Mount namespace separation option, and reboot immediately.
Please note the first boot might take a while. If after 10 minutes or so the phone has not rebooted, you should boot back into TWRP, install the supersu zip file again, and this time wipe cache and dalvik before rebooting. Otherwise the cache and dalvik wipe is not necessary. I will eventually post pictures to demonstrate all the steps in the 2nd post, and hopefully FAQs or whatever in the third post.
If you want to hit the thanks button that would be awesome, but the real credit goes to chainfire for his amazing work with supersu and really just all things root in general; and Dees_Troy for doing an excellent job developing and maintaining TWRP custom recovery for our device. They're the real heroes, I just wrote up this guide
Pictures to Demonstrate Steps
Sorry all the pictures are sideways. If you want, you can still view them by clicking the following link, file names begin with corresponding step numbers: https://www.dropbox.com/sh/wgguior3q2c6638/AAAzas50Zd-Du7jNXI3HsZU2a?dl=0
Proof I have the SM-G900T, latest 5.1.1 firmware, unmodified:
{
"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"
}
Step 1:
Step 2:
Step 3:
Step 4:
Step 5:
Step 6:
Step 7:
Step 8:
Proof We're Now Rooted:
FAQ's
Does this method work with the new marshmallow (6.0.1) firmware?
Yes. I have done it myself, it works
So I'm rooted now what?
Once you're rooted, you can use certain apps you would be unable to use not rooted. A few I would definitely recommend checking out: AdAway (an adblocker), Viper4Android (significantly, noticeably improve your audio quality by tweaking the settings in this app), Titanium Backup (not only backup and restore app settings, but freeze/uninstall unwanted system apps, aka bloatware), and a root-enabled file explorer such as Root Browser or ES File Explorer (with the root option enabled) is recommended. If you plan to install Viper4Android, before doing so please first flash this file in TWRP and then reboot, edit the following lines in the file /system/build.prop, and reboot again once the edits are made:
Code:
lpa.decode=true to lpa.decode=false
tunnel.decode=true to tunnel.decode=false
lpa.use-stagefright=true to lpa.use-stagefright=false
Where can I find custom ROMs for this phone?
Touchwiz (Samsung's version of Android similar to the one that comes stock with the phone) based ROMs can be found in the T-Mobile Galaxy S5 Android Development Section. AOSP (Google's original version of Android) based ROMs, such as CyanogenMod, AOKP, Mokee, Bliss, AICP, Resurrection-Remix, etc. can be found in the S5 Unified Development Section. I must warn you i can give a lot more information on the aosp based ROMs since that is my personal preference in overall Android experience, as a result my knowledge of touchwiz based development is much shakier. To each their own, and we ought to cherish android's ability to give us such a powerful freedom of choice and fight for this continued ability for our control of our personal devices against current trends of locking everything down too tight to allow for true development based innovation. Remember, when getting ROMs from this section, this phone's development name is klte (as opposed to kltevzw, kltespr, klteusc, etc.)
More info to come
Thank you very much for posting this, I just got a used S5 in the mail today and your process worked like a charm. Rooted on the first pass.
thisisapoorusernamechoice said:
Reserved, FAQ's or something
Click to expand...
Click to collapse
It works is cm stable
Sent from my LG-D851 using Tapatalk
---------- Post added at 01:09 PM ---------- Previous post was at 12:32 PM ----------
thisisapoorusernamechoice said:
BACKGROUND: OK this question gets asked every day, by members of varying skill levels, so this is intended to be a one stop guide on how to root, no matter what firmware version you're running. Yes this will trip Knox, no that will have no effect on your phone whatsoever, and there are ways to reset the Knox counter. If worst comes to worst and you need to bring your phone in for warranty and they give you any sort of lip for the Knox counter, tell them Kies broke your phone and they da** well better fix it (worked for me with multiple Samsung devices).
That said, this will root the SM-G900T (T-Mobile Galaxy S5) no matter what version of android you're running. Make sure you read this entire post and understand everything before trying anything.
PREPARATION: Disclaimer out of the way, now for the fun stuff. First, preparation, you need to download the following files to your PC: Odin 3.10.7 (this is Odin, it flashes stuff to Samsung android phones); twrp-3.0.2-1-klte.img.tar (this is the custom recovery we're going to use). Extract the Odin zip file to your PC's Desktop. Download the file named BETA-SuperSU-v2.71-20160331103524.zip somewhere to your phone's internal storage or external SD, doesn't really matter which. Now in your phone's settings, go to About device, scroll down to Build number. Repeatedly tap Build number until your phone tells you Developer options have been turned on. Go back and enter developer options, enable USB debugging and hit OK, also enable Allow mock locations a couple lines below it. At this point you'll want to connect your phone to your PC with USB, just to make sure it actually connects (it should). If not, you can download the USB drivers from here (scroll down to Downloads section), but most likely this won't be necessary. OK prep work done, now we get to actually get started on rooting our phone. Make sure your phone has at least 50% battery, this is always a smart safety step.
STEPS:
Power off the phone. Boot into download mode (hold vol-, home, and power all at once in that order), then hit vol+ to continue
Run Odin (double click the Odin3 v3.10.7.exe file). Click the Options tab, disable the "Auto-Reboot" option and double check that "Re-Partition" option is disabled (it should be by default), this is critical to success
Connect phone via USB. Hit AP button in Odin, select the twrp-3.0.2-1-klte.img.tar
Flash (click start). When it's done, the progress bar will be full and Odin should say "PASS!"
Hold vol+, home, and power (all at once, in that order) to boot into recovery. THIS MUST BE DONE BEFORE REBOOTING NORMALLY!. TWRP might ask if you want to let it modify your system or keep it read only. I would highly recommend you let it modify your system, you might be OK keeping it read only, but I cannot guarantee that. You will be fine letting it modify your system, that I can guarantee.
Hit the install option and navigate to the SuperSU zip file that is saved to your tablet. Select it and swipe to install.
Reboot system (normal reboot). If TWRP should ask you, do not let it install supersu the way it wants to (do not swipe to install, just reboot).
When android is booted, run the superSU app and go into settings, disable the Mount namespace separation option, and reboot immediately.
Please note the first boot might take a while. If after 10 minutes or so the phone has not rebooted, you should boot back into TWRP, install the supersu zip file again, and this time wipe cache and dalvik before rebooting. Otherwise the cache and dalvik wipe is not necessary. I will eventually post pictures to demonstrate all the steps in the 2nd post, and hopefully FAQs or whatever in the third post.
@lox2013
Click to expand...
Click to collapse
Cm 13 is instill thanks to u should get all the credit BC nobody else find out
Sent from my LG-D851 using Tapatalk
SuperSU Install?
Thank you for putting this together with simple to follow steps!
Hypothetically if someone were to accidentally swipe to install supersu at step 7 rather than just rebooting, what problem(s) does that cause?
thisisapoorusernamechoice said:
STEPS:
Power off the phone. Boot into download mode (hold vol-, home, and power all at once in that order), then hit vol+ to continue
Run Odin (double click the Odin3 v3.10.7.exe file). Click the Options tab, disable the "Auto-Reboot" option and double check that "Re-Partition" option is disabled (it should be by default), this is critical to success
Connect phone via USB. Hit AP button in Odin, select the twrp-3.0.2-1-klte.img.tar
Flash (click start). When it's done, the progress bar will be full and Odin should say "PASS!"
Hold vol+, home, and power (all at once, in that order) to boot into recovery. THIS MUST BE DONE BEFORE REBOOTING NORMALLY!. TWRP might ask if you want to let it modify your system or keep it read only. I would highly recommend you let it modify your system, you might be OK keeping it read only, but I cannot guarantee that. You will be fine letting it modify your system, that I can guarantee.
Hit the install option and navigate to the SuperSU zip file that is saved to your tablet. Select it and swipe to install.
Reboot system (normal reboot). If TWRP should ask you, do not let it install supersu the way it wants to (do not swipe to install, just reboot).
When android is booted, run the superSU app and go into settings, disable the Mount namespace separation option, and reboot immediately.
Click to expand...
Click to collapse
I might should have not been doing this for the first time at 3a? How much trouble did I cause myself but letting TWRP install supersu by swiping?
Thank you again.
SethVIII said:
Thank you for putting this together with simple to follow steps!
Hypothetically if someone were to accidentally swipe to install supersu at step 7 rather than just rebooting, what problem(s) does that cause?
I might should have not been doing this for the first time at 3a? How much trouble did I cause myself but letting TWRP install supersu by swiping?
Thank you again.
Click to expand...
Click to collapse
I'm pretty sure it'll cause a bootloop, I would recommend against doing the swipe to install when twrp asks you to, saying supersu isn't installed (it is when you install the zip, twrp just can't detect it). The reason for this is something in the kernel called selinux (long story, Google it if you want the full blown details) but the short version is starting with android 5.1.1 older versions of supersu (ie the one twrp wants to install for you automatically) usually cause a bootloop. The supersu zip file I link to in my post is specifically designed to avoid this issue. Thanks for reminding me, I wanted to put this question in the FAQ section. It's an important issue and something anyone who wants to know a little more about android should be aware of
thisisapoorusernamechoice said:
I'm pretty sure it'll cause a bootloop, I would recommend against doing the swipe to install when twrp asks you to, saying supersu isn't installed (it is when you install the zip, twrp just can't detect it). The reason for this is something in the kernel called selinux (long story, Google it if you want the full blown details) but the short version is starting with android 5.1.1 older versions of supersu (ie the one twrp wants to install for you automatically) usually cause a bootloop. The supersu zip file I link to in my post is specifically designed to avoid this issue. Thanks for reminding me, I wanted to put this question in the FAQ section. It's an important issue and something anyone who wants to know a little more about android should be aware of
Click to expand...
Click to collapse
Thank you for your quick and helpful response. So if my phone is booting now, with supersu installed, does that mean I am good to go?
Bootloop may be what happened. After awhile, I pulled the battery, booted back into TWRP and reinstalled the supersu zip file. I did not wipe cache or dalvik but I also did not swipe to install supersu. My phone now boots and acts fine other than showing "Set Warranty Bit : kernel", but I think that is expected, correct?
SethVIII said:
Thank you for your quick and helpful response. So if my phone is booting now, with supersu installed, does that mean I am good to go?
Bootloop may be what happened. After awhile, I pulled the battery, booted back into TWRP and reinstalled the supersu zip file. I did not wipe cache or dalvik but I also did not swipe to install supersu. My phone now boots and acts fine other than showing "Set Warranty Bit : kernel", but I think that is expected, correct?
Click to expand...
Click to collapse
The Set Warranty Bit: kernel thing is normal, that's just your phone telling you it's rooted (I mean it's technically telling you the kernel has been modified, in this case only just to allow for supersu to be installed). As long as you're booting fine, that's what's important. Thanks for the feedback, and I hope I've been helpful
thisisapoorusernamechoice said:
The Set Warranty Bit: kernel thing is normal, that's just your phone telling you it's rooted (I mean it's technically telling you the kernel has been modified, in this case only just to allow for supersu to be installed). As long as you're booting fine, that's what's important. Thanks for the feedback, and I hope I've been helpful
Click to expand...
Click to collapse
Yes, very helpful, thank you.
So any confirmed root on FOL1 yet??? With custom ROM flashed
Sent from my SM-G900T using XDA-Developers mobile app
VICIOUSVIC1 said:
So any confirmed root on FOL1 yet??? With custom ROM flashed
Sent from my SM-G900T using XDA-Developers mobile app
Click to expand...
Click to collapse
Is confirm I rooted my gf phone the s5 5.1.1 it works she running cm 13 most stable rom
Sent from my SM-N920C using Tapatalk
VICIOUSVIC1 said:
So any confirmed root on FOL1 yet??? With custom ROM flashed
Sent from my SM-G900T using XDA-Developers mobile app
Click to expand...
Click to collapse
FYI, I don't know of any Custom ROMs that are not already rooted. Rooting is only needed for Stock ROMs.
Rob
Trying with FOL, downloaded via the link provided here. After installing TWRP, i have to remove the battery to get the phone to turn off. It still acts as if it were being updated, and the power button does not work. Taking out the battery, putting it back in, and pressing vol up, home, power brings up twrp.
After hitting install, the zip file fails:
<<<<<<<<<<<
Updating partition details...
...done
Full SELinux suppot is present.
MTP Enabled
Installing zip file ' /external_sd/._BETA-SuperSU-v2.
71-20160331103524.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Zip file is corrupt!
Error installing zip file '/external_sd/._BETA-
SuperSU-v2.71-20160331103524.zip'
Updating partition details...
...done
<<<<<<<<<<<
About Device shows the baseband version: G900TUVS1FOL1
I'm probably just doing something wrong. With some help, i'd like to try again.
trips KNOX
thisisapoorusernamechoice said:
BACKGROUND: Yes this will trip Knox, no that will have no effect on your phone whatsoever, and there are ways to reset the Knox counter. If worst comes to worst and you need to bring your phone in for warranty and they give you any sort of lip for the Knox counter, tell them Kies broke your phone and they da** well better fix it (worked for me with multiple Samsung devices).
Click to expand...
Click to collapse
not good to trip KNOX from what I understand. maybe there can be included in this a way to remove KNOX? I know I posted this comment in another post that linked to this. I thought I was on the right post. sorry. OH and What is Kies and how is that pronounced?
musterion1973 said:
not good to trip KNOX from what I understand. maybe there can be included in this a way to remove KNOX? I know I posted this comment in another post that linked to this. I thought I was on the right post. sorry. OH and What is Kies and how is that pronounced?
Click to expand...
Click to collapse
Knox is Samsung's indicator if your phone has ever had a non-stock kernel installed. Currently there are very few pieces of software - Samsung only - that check this flag. One may be Samsung Pay. However, it doesn't cause any other problems with any other parts of Android. And, doesn't keep you from turning your phone back it, etc.
KIES is the software that Samsung supplies to flash updates, make backups, etc.
You can find it here: http://www.samsung.com/in/support/usefulsoftware/KIES/
Rob
SethVIII said:
Yes, very helpful, thank you.
Click to expand...
Click to collapse
When i hit the install supersu when twrp asked me i was put in a bootloop like thispoorusernamechoice said. I learned my lesson though?
I am a thank you slut.lol
rlichtefeld said:
Knox is Samsung's indicator if your phone has ever had a non-stock kernel installed. Currently there are very few pieces of software - Samsung only - that check this flag. One may be Samsung Pay. However, it doesn't cause any other problems with any other parts of Android. And, doesn't keep you from turning your phone back it, etc.
KIES is the software that Samsung supplies to flash updates, make backups, etc.
You can find it here: http://www.samsung.com/in/support/usefulsoftware/KIES/
Rob
Click to expand...
Click to collapse
Thank you Rob.
---------- Post added at 04:02 AM ---------- Previous post was at 03:15 AM ----------
thisisapoorusernamechoice said:
BACKGROUND: OK this question gets asked every day, by members of varying skill levels, so this is intended to be a one stop guide on how to root, no matter what firmware version you're running. Yes this will trip Knox, no that will have no effect on your phone whatsoever, and there are ways to reset the Knox counter. If worst comes to worst and you need to bring your phone in for warranty and they give you any sort of lip for the Knox counter, tell them Kies broke your phone and they da** well better fix it (worked for me with multiple Samsung devices).
twrp-3.0.2-1-klte.img.tar (this is the custom recovery we're going to use).
Click to expand...
Click to collapse
twrp-3.0.2-1-klte.img.tar 10.6M
twrp-3.0.2-1-klte.img 10.6M
do I need both of these or just the very top one. I downloaded both ? in the event they are bother needed. but what one will we be using here Sir or Ma'am.
Yes this will trip Knox said:
did not seem to trip KNOX. so how di I remove KNOX altogether?
Click to expand...
Click to collapse
musterion1973 said:
twrp-3.0.2-1-klte.img.tar 10.6M
twrp-3.0.2-1-klte.img 10.6M
do I need both of these or just the very top one. I downloaded both ? in the event they are bother needed. but what one will we be using here Sir or Ma'am.
Click to expand...
Click to collapse
You just need the twrp-3.0.2-1-klte.img.tar 10.6M
This tutorial gets your MetroPCS Grand Prime (model SM-G530T1) root, a deodexed and bloatware-free TouchWiz, 'fairly stock' ROM, and Xposed Framework. This method will likely work on the T-Mobile variant because much of this is actually intended for that variant... but no guarantees. If you do, indeed, attempt this with a non-MetroPCS variant, please let me know your model number and if it works or not so i can add it to the compatibility/incompatibility list.
Known compatible variants:
SM-G530T1 - MetroPCS
This tutorial comes with no guarantees or warranties. I am not responsible if you brick your device or for any damage caused by following this tutorial. You can most likely recover any problems you find along the way by simply flashing back to Stock with Odin, but I can't guarantee that you will be able to. This is true of basically everything on XDA, so no surprises here.
I estimate the entire process taking less than a half hour, assuming that everything goes as expected, and that you don't need to flash back to stock first.
There is one caveat... the TrapKernel method fully roots the device, but it trips Knox. If you don't want to trip Knox, don't use this method. As an alternative, if all you want is some minor root functionality, KingRoot will give you SOME root functionality, but not enough to install Xposed, or to do many things that a true root gives you. KingRoot can be found here: SITE / DOWNLOAD
At any time, even if you brick your device, you can probably always flash back to Stock. Here is the Stock MetroPCS SM-G530TI 5.1.1 ROM: THREAD / DOWNLOAD
Alright... without further adieu, here are the files you will need:
Odin SITE / DOWNLOAD
ShinySide's TrapKernel for SM-G530T THREAD / DOWNLOAD
DUHAsianSKILLZ's deodexed and bloatware-free ROM for SM-G530T: THREAD / DOWNLOAD
Chainfire's FlashFire SITE / DOWNLOAD
Xposed Installer THREAD / DOWNLOAD
TWRP 2.8.7.0 (for lollipop) THREAD / DOWNLOAD
Custom Xposed Framework for Samsung Lollipop THREAD / DOWNLOAD
Got all the files you need? Here are the steps:
1. On your phone, boot to Download Mode by booting your device while holding down the Down Volume and Home Button, then hitting Volume Up. Connect it to your PC. If your PC doesn't recognize the phone, you need to install drivers. There are lots of threads out there with tutorials on how to do that. This tutorial assumes you already have the drivers.
2. On your PC, open Odin, Click the "AP" button, Select the file: TrapKernel_G530T_AOF8_Root.tar.md5. Flash it. Let the phone boot normally. If it doesn't load after a few minutes, pull the battery and reboot. If it continues to get stuck on boot, it probably failed. Flash back to Stock and try again.
3. On your phone, once it fully boots up, download Chainfire's SuperSU from the Play Store. You'll need it in order to authorize the root app in the next step.
4. On your phone, download FlashFire from the Play Store at the link above, or if you have the APK, install it. Open FlashFire and authorize SU permissions. Hit the + button, then Wipe. Check System data, 3rd party apps, Dalvik cache, Cache partition, and Cache partition format, then click the Checkmark on the top-right to confirm. Now hit the + button again, then Flash Zip or OTA. Select GwizRomSMG530T-V1.1.zip, then click the Checkmark on the top-right. Now click Flash. The screen will go off during this step... DON'T WORRY. It will take about 10 minutes total to boot for the 'first time'. This ROM basically removes Knox, retains root, and frees up a lot of resources that Samsung was using for useless bloatware. Even if you stopped at this step, your phone will be MUCH better off than with a purely Stock ROM on it. I noticed a HUGE performance improvement after installing this ROM.
5. On your phone, install XposedInstaller_3.0_alpha4.apk.
6. On your phone, open FlashFire. Tap the + button, then Flash Zip or OTA. Find TWRP_2870_Samsung_SM_G530H.zip and flash it. This one takes a little while to load, so be patient. I would say, if you're at the 10 minute mark after tapping Flash, it probably failed so pull the battery and reboot. If it continues to happen, you'll likely need to flash Stock and start over completely.
7. The phone will boot back to your home screen. Once it does, restart it and go into Recovery Mode by booting the phone while holding the Volume Up and Home buttons.
8. Once in Recovery, tap Install. Find and choose the file xposed-v86.0-sdk22-arm-custom-build-by-wanam.zip and swipe the slider at the bottom to Install Xposed.
9. Once it finishes flashing and boots back up, you're good to go. Full Root. Bloatware-Free. Really fast. With Xposed.
10. One last thing, I would install an app like NoBloat or something to disable or delete the app com.tmobile.pr.adapt. It doesn't like that you rooted your device and will start acting up. The reason a T-Mobile app is there is because the bloat-free ROM you installed in step 4 above is based on a T-Mobile Stock ROM, not MetroPCS. You don't need it. It will ask for root permissions all the time, use cell data, and deplete your battery. Just disable it if you are not comfortable fully deleting it. I would also look into disabling/deleting some of the other apps like some of the Samsung stuff, but you'll have to research what is safe to remove. I know the com.tmobile.pr.adapt app is pointless and a data/battery hog.
Well then thanks for putting this together. Now everything is in one spot. Well done.
Sent from my SM-G530T using Tapatalk
after flashing "TrapKernel_G530T_AOF8_Root.tar.md5" Phone reboots fine, but wifi doesn't works anymore, I repaired it with SmartSwitch, reloading the firmware back to Stock.
bullracing said:
after flashing "TrapKernel_G530T_AOF8_Root.tar.md5" Phone reboots fine, but wifi doesn't works anymore, I repaired it with SmartSwitch, reloading the firmware back to Stock.
Click to expand...
Click to collapse
How did you end up doing that? I couldn't figure out how
you mean, how to restore to stock?
Download Smatch by Samsung, the use theere option "MORE" and go to "EMERGENCY SOFTWARE RECOVERY AND INTIALATION" there Switch will ask you phone the phone model and the SN number to get the original or Stock firmware to it
No... went to root my Samsung Galaxy Prime to remove bloatware
Help
GwizRomSMG530T-V1.1.zip will not install, there are 2 options to check on the flash screen, should I leave those blank or check them?