Related
Hello ! Here is the Ultimate n00b FAQ !
I am mainly writing this FAQ to educate the n00bs about their Android Phone. Many n00bs don't read much and just go about dirtying threads which does not much good to the developments. This FAQ will get you accustomed to the widely and common terms of the Android World ! So here we go...
Glossary:
1)flashing - Installing (In plain language)
2)ROM - The package of the entire system for your phone.
3)bloatware - Unnecessary apps added by Companies to Stock ROMs.
4)Deodex - Your system apps come with additional .odex files. Deodexing means packing these odex files into the app. This is mainly done because deodexing makes it easy to modify the apk also theming becomes easier.
5)EXT4 - A type of Linux system partition like FAT32 or NTFS in windows.
6)Brick ! - The condition of your phone when it becomes a Paperweight ! There are two types of brick conditions- Hard bricked means the phone cannot be recovered and needs to be taken to the service centre. Soft brick means your phone will reboot or will be stuck at the botoscreen. This can mostly be recovered by reflashing your Firmware again.
7)Bootloop- Your phone will continuously boot to the Logo.
Ok so here goes the first question--
1)What is 'Rooting' ? How should I do it? Will it help me not help me ?
A: 'Rooting' means getting Superuser access to your phone. This means that Rooting will provide access to the System files and the core components of the OS. You can Root your phone by using Tools like SuperOneClick Root or Z4Root. This happens in just one click and is very easy ! Rooting can provide you with a lot of benefits like ability to flash a Custom ROM, a Custom Kernel, Theme, system level modifications. You can also install apps which require Root access such as Root Explorer, Font Changer,Chainfire 3D, Faster Fix and lots more. Rooting will generally not cause any problem if you do it correctly !
P.S: Rooting voids your warranty ! However you can unroot and reclaim your warranty so no need to worry !
2)What is a Firmware Package or How to Upgrade my Phone ?
A: A firmware package is usually called Stock ROM or the ROM released officially by the Company. This can usually be flashed to your device by using the software provided by the Company or another third party software.
For.eg. Samsung users can use Kies (Official) but we all use ODIN(Third-Party) all sammy users out there you all know how reliable KIES is XD XD
3) What is a Custom ROM ? How is it beneficial/not-beneficial[Root needed]?
A: A Custom ROM is a modified version of the Operating System System. A Custom ROM comes with lots of features implemented by the dev. Custom ROMS come pre-rooted, Deodexed,Zipalligned.etc. They also come pre-installed with useful apps. Custom ROMs are usually high on Benchmark Scores since devs usually add many tweaks and performance improvements. However read a lot and flash Custom ROMs specefic to your device and Firmware or you will end up with a bricked phone.
4) What is a Kernel ?
A: Kernels are something more deep into the System. The Kernel is a Bridge between the Hardware and Software of your phone. Without a Kernel the device will not boot. For eg. When you receive a message the system sends a message to the kernel and the kernel lights up the notification LED. The kernel is also responsible for the turning on of your screen and also controls the CPU clock Rate i.e the frequency or speed of your CPU. When the phone is idle and not in use the Kernel puts the Phone in Deep Sleep mode. Messing with Kernel components can result in undesirable problems is you don't know what you are doing.
5)What is a Custom Kernel ? [Root needed]
A: A Custom Kernel is a Kernel developed by a developer which may include many improvements and features. It may also support Overclocking your phone i.e running your phone at a higher clock frequency. It may also have more CPU Governers and IO Schedulers. Custom Kernels may also come with a Custom Recovery and EXT4 support.
However do some reading before flashing a Custom kernel.
6) What is OverClocking and how does it affect my device ? [Root needed]
A: Overclocking means running your phone at a higher frequency than Stock. However you need to flash a Kernel which supports overclocking for this. Apps like SetCPU and No Frills CPU (Both require Root access) can be used to alter CPU speeds.
ADVANTAGES: Overclocking can help you run games which lag on your device smoothly. Also it can give you some good speed and zippyness when required.
DISADVANTAGES:Higher CPU speeds may need more power and can cause battery drain. It can also cause your phone to get heated and can fry up internal components.
P.S:Each device has a different Chip. Each Chip has different levels of tolerance to overclocking and every device may not handle overclocking the same way. Results will vary with each chip. So if a Galaxy S plus supports overclocking from 1.4Ghz to 1.9Ghz, a device like Galaxy SL will support Overclocking(stable) upto 1.2Ghz - 1 3Ghz.
7) What is Recovery,Download Mode ?
A: Download mode is a mode through which a New Firmware Package is installed to the device. This can be done by first powering off your device. Then pressing the Volume Down + Home + Power buttons at the same time. As long as your phone enters recovery mode, you can recover it ! Recovery Mode Can be accessed by Volume Up + Home + Power button Combo. You can perform vital tasks like Factory Reset, you can wipe Cache Partition(required after flashing most ROMS). Custom Recoveries [Root needed] like CWM come with even more features like you can wipe Dalvik Cache (is also needed to be wiped after flashing ROMs). Custom ROMs have to be installed through Custom Recovery like CWM. However CWM is not an app alone. You need to flash a Kernel with CWM Recovery support.
NOTE: To enter Recovery or Download mode. Make sure you have enabled USB Debugging at Settings->Applications->Application Development->USB Debugging
8) What is a bootloader ? What is a locked bootloader ? How important is it?
A: A bootloader is rather the part of your system that boots up the device. It is however contained in a separate Partition. If your bootloader gets corrupt or if you flash the bootloader of anither phone you will be hardbricked and your phone wont even boot. Bootloader loads up the Kernel which then loads up the ROM. Some devices come with bootloader locked by companies. This rules out flashing Custom ROMs ! Yes the best thing is to never mess around with the bootloader because only the service centre will be able to help you then.
And n00bs always read, understand and then go about posting or messing up threads. Its not with an intention of being rude but a little reading can help. Once even I was a n00b ....
Yes ! Thats the FAQ for you ! Do not PM me with stupid questions (That is a kind request). If you have any doubts post here I will try to help you .
Hit Thanks if it helped you !
Still Lots more to come in the FAQ !.. ..
I would probably call it "Newbie's Guide" as opposed to "n00b's guide," as there is a real, if pedantic distinction made by the online community regarding "newbs" vs "n00bs"--the former being people who are simply new to the scene and ignorant of much of the inner workings, the latter being people who are considered willfully ignorant and/or annoying.
I'd also proofread it and make it look a little more professional. Simply slapping 'Ultimate' on the title a definitive FAQ does not make. Happy to assist on that front, if you like.
Unroot -OK. But Reclaim Warranty ?
Adi_Pat said:
Rooting voids your warranty ! However you can unroot and reclaim your warranty so no need to worry !
Click to expand...
Click to collapse
I know we can unroot it , but we can't factory LOCK the bootloader! :silly:
The bootloader will always show RELOCKED.
Then "HOW" can we reclaim our warranty may I know?
Thanks for the guide, BTW, Can I overclock my LG Optimus ME to 1GHz?
Paresh Kalinani said:
I know we can unroot it , but we can't factory LOCK the bootloader! :silly:
The bootloader will always show RELOCKED.
Then "HOW" can we reclaim our warranty may I know?
Click to expand...
Click to collapse
That depends on the particular device. Doesn't apply to my Galaxy Nexus. Fastboot oem lock and no one is ever the wiser =)
Will I be able to reclaim warranty?
jesusice said:
That depends on the particular device. Doesn't apply to my Galaxy Nexus. Fastboot oem lock and no one is ever the wiser =)
Click to expand...
Click to collapse
So what do you think about HTC One V?
Paresh Kalinani said:
So what do you think about HTC One V?
Click to expand...
Click to collapse
Don't know much but I know if you use HTC's unlock then they definitely will know. Not sure if anyone's found an exploit or workaround for it yet. That's why I went with a Nexus this time, not to have to worry about such things.
i decided to put EVERYTHING for this phone under one roof.. the drivers, root, roms, tweaks, tutorials, links etc etc, all consolidated in one spot.. this way, anyone that bought or buys this phone dont have to scour the interwebs to find what theyre looking for. normally, its fair to assume if youre here, you have some degree of knowledge about everything to follow. however, im going to over simplify some or eventually most stuff for, example, family or friends that ask me to "jailbreak" their phone then have no idea what to do once i do. or, for anyone else that meets the same criteria ("budding android modders") lol. :good:
at the moment though, i dont have time to get everything up all at once, so i decided to create a placeholder and upload a rom in the meantime.. theres more to come as time permits..
ROM
deodexed
(now you can switch from "dalvik" to "art" in "developer options" without all the FCs.. the pros and cons with odex vs odexless roms goes back and fourth. having an odexed rom can make your phone a little faster, and free up more room for apps and stuff which is why most if not all phones come odexed (eventually, you can click here to see how to free up room by getting the most of your sdcard, so the free space you lose being unodexed wont really matter), but it has a few setbacks when it comes to modding your phone depending on what youll be doint to/with it now that its rooted (wil discuss more in detail later). If youre coming from another phone with a custom rom, and became spoiled by having developer options already in settings for you. or, you just wanna try art and/or have access to more features (this will later be moved when i explain how to root and setting up drivers, since debugging becomes relevant), getting the menu back is pretty simple. just open settings and go down to "about phone", then click on "software information". on the following screen click "build number" 7 times and if you did it right a popup will display welcoming you to the world of development lol. so simplified its "Settings>About phone>software info", click "Build number" 7x.. "Developer options" is now in settings again. in developer options ("settings>developer options") youll see "select runtime", where you can do just that).
added root and enabled adb root (you need to download your superuser app of choice though).
added busybox with symlinks.
fixed a few invalid permissions. (come to think, im gonna add them back jic its relevant to other carriers besides boost mobile)
and removed some useless symlinks. (come to think, im gonna add them back jic its relevant to other carriers besides boost mobile)
fixed kitkat sdcard write restriction.
this is a "rough draft", there is a few more little tweaks i wanna add (ie: once the device is activated on boost mobile, it downloads all the boost related apps, and those apps reinstall even after a fresh wipe/format/rom installation. its inconvenient if you switch carriers) but i just wanted to get a link up, this is a great phone for the price (only $40, when the HTC Vision still sells for $100 at a fraction of the performance), but it seems like there is close to zero development being done probably because of that (ie; i couldnt find 1 single rom for this device, its not exactly a well known, high demand, highly advertised device. but imho that doesnt mean the 27 or so rooted owners shouldnt have some easy options). unfortunately, even though i stumbled across the kernel source code for w5c (ironically on a LG l70 board) my laptop would probably take days to compile from source, so in the meantime ill tweak the stock image, and maybe eventually see if i can hack some cyanogenmod goodness together.. ill make this thread more professional as time progresses, as well as add an odexed version (definately the stocks version, but i might even redo odexing the right way as well, i donno yet because i dont see the benefit, its just my OCD acting up because i know LG did it half assed), and MAYBE a completly stock rom w/ no mods (which seems redundant since most people keep a "stock" recovery backed up.. but if you were like me and didnt know how easily the bootloader could be unlocked, so you just rooted and started playing with stuff, it might come in handy to have a stock rom lying around.)
Downloads
http://[email protected]/download/%75c%749%6D%6459%77%659%78sl%78/lgls620.zip
http://[email protected]/public/%42%54%44s%42%56/lgls620.zip
http://[email protected]/#!KZFkxb5K!zXW_1p_WMcR_EenrGPoLEgo_-OURR2i7tHSa6GCk5j8
MD5: cc88f51b3e483c4a8c3b974d6f87ceec
File Name: lgls620.zip
(google url shortener didnt like my link and claimed it was a TOS violation, then mediafire deleted the file claiming the same, all within only a few hours of uploading.. so i apologize for the obscured non clickable download links. i never had this problem before so i dont know what they dont like or how theyre deciding its a violation, and if i make the urls clickable xda automatically un-obscures them, so untill i figure out what they dont like or how they go about making that decision, im gonna assume its a bot. i tried an anonymous referer but then mediafire falsely claims the file was removed for violating TOS, without the referer it works fine though (completely unrelated, keep that in mind.. if you ever try downloading something on mediafire that says its been removed, and you were sent there by a referer, try reloading the mediafire link independently before giving up on the dl, i imagine they assume if your being refered anonymously its pirate related so they block you)
PLACEHOLDER
Placeholder
Placeholder
Placeholder0
Placeholder0
Placeholder1
Placeholder1
Placeholder2
Placeholder2
Placeholder3
Placeholder3
How did you unlock the boot loader?
I zeroed the laf partition and did fastboot oem unlock with fastboot oem device-info reporting:
Code:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.004s]
but when I try flashing a modified (using Android Kitchen) boot image it comes up saying:
Code:
ERROR : boot certification verify
[750] ------------------------------------------
[760]
[760] Secure booting Error!
[760] Cause : boot certification verify
[760]
[760] ------------------------------------------
I'd like to be able to change the init scripts, and possibly the kernel (where did you find the source?), but I'm stuck getting it to boot with the new image.
Laf
Zero laf, fastboot oem unlock, flash recovery, profit
soulife said:
Zero laf, fastboot oem unlock, flash recovery, profit
Click to expand...
Click to collapse
this thread will be updated soon (for those who give af)
Recover your dead LG REALM (LS620)
First of all thanks to @soulife for the deodexed rom.
2nd to @fatherguido for the boot.img
3rd to @bcrichster for the stock recovery.img
4th to @elisam98 for the bumped twrp img
This is for you all that want to recovery your dead LS620.
This applies to all phones that have no recovery/fastboot mode enabled/download only/or just a faulty rebooting system.
1. you have to enter download mode and zero out LAF partition: to do this you have to download the LG root zip and follow some steps in this tutorial (until step 10) then run the following command:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
2. Power off the phone and enter download again, only this time it will be fastboot mode.
2a. here you will fastboot oem unlock command
2b. flash twrp from here
(the commands to flash this twrp img in fastboot are: fastboot flash recovery w5c_twrp_bumped.img)
3. Enter twrp and flash my backup which has the boot.img from fatherguido and the stock deodexed rom from soulife.
Or you can flash the stock deodexed rom in this forum by soulfie
and then reboot to fastboot again and flash manually the boot.img by fatherguido.
links to all files:
boot.img (zipped)
twrp.img (zipped and bumped)
LG ROOT (zipped)
Stock recovery (zipped)
My TWRP backup (7zipped)
GOOD LUCK!!!
Sweet! Nice job, bro.
Gratefully sent from my Rooted JollyRoger_B13
Alex_XV6700 said:
First of all thanks to @soulife for the deodexed rom.
2nd to @fatherguido for the boot.img
3rd to @bcrichster for the stock recovery.img
4th to @elisam98 for the bumped twrp img
This is for you all that want to recovery your dead LS620.
This applies to all phones that have no recovery/fastboot mode enabled/download only/or just a faulty rebooting system.
1. you have to enter download mode and zero out LAF partition: to do this you have to download the LG root zip and follow some steps in this tutorial (until step 10) then run the following command:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
2. Power off the phone and enter download again, only this time it will be fastboot mode.
2a. here you will fastboot oem unlock command
2b. flash twrp from here
(the commands to flash this twrp img in fastboot are: fastboot flash recovery w5c_twrp_bumped.img)
3. Enter twrp and flash my backup which has the boot.img from fatherguido and the stock deodexed rom from soulife.
Or you can flash the stock deodexed rom in this forum by soulfie
and then reboot to fastboot again and flash manually the boot.img by fatherguido.
links to all files:
boot.img (zipped)
twrp.img (zipped and bumped)
LG ROOT (zipped)
Stock recovery (zipped)
My TWRP backup (7zipped)
GOOD LUCK!!!
Click to expand...
Click to collapse
hey ive been doing this for a long time now, but im still a noob to some things.....
what is a boot.img?
i always read people saying to flash it this way or that, and i see it on file hosting sites along with the stock and custom roms and recovery.img, but ive never gotten it and done anything with it because i dont know what the hell it is,what it is for, and what the point of having it is
just wondering lol
mistaweeks said:
hey ive been doing this for a long time now, but im still a noob to some things.....
what is a boot.img?
i always read people saying to flash it this way or that, and i see it on file hosting sites along with the stock and custom roms and recovery.img, but ive never gotten it and done anything with it because i dont know what the hell it is,what it is for, and what the point of having it is
just wondering lol
Click to expand...
Click to collapse
If you dont need to repair or resurrect your phone or change to a custom rom then you dont need to modify the boot.img
:good::good::good::good:
I'm stuck my lg realm ls620 only enters download mode, no recovery, and won't boot. So following your instructions in step one gets me stuck on step 2 of the thread you referred to in step 1. How can I transfer the rootedsystem file into the root of my phone if it will ONLY go into download mode? Please help.
Wazza
bcrichster said:
Sweet! Nice job, bro.
Gratefully sent from my Rooted JollyRoger_B13
Click to expand...
Click to collapse
Hey wassup remember me from the other website??
You helped me root my ZTE Z730 and made a custom
ROM for it. I got this phone now, but I'm probably not
Gonna use this ROM. I'll wait for an odexed one.
Thanks anyways!!
i recently seen a web site that says 5.0 update for lg realm is this a legit rom or a fake
Hello XDA. I'm curious if anyone has any info or advice on getting working camera libraries for cm12 for the lg realm. As those from Android forums are aware, we have some cm12.1 Roms for the ls620, but they are incomplete in a few aspects.
One is cameras. Neither front or back cameras work, which I believe to be an issue with the libraries used. I don't know enough about compiling the ROM with proper Android lollipop camera libraries for this phone.
Aside from that, the Roms work pretty well. There seems to be less development for this phone which is a beast otherwise(not considering the small memory...)
Hoping someone can lend some input.
Thanks!
Hey I've bricked my lg ls620 I can get into factory reset and download mode can you instruct me on how to get it fixed or at least get twrp on it and I got it from there it's a girls phone I'm fixing for here and she has her dought that it can be done normal thing would be flash tool and kdz but the only way to get the kdz is to buy it and it may still not work I get a secure boot error
Sent from my XT1526 using XDA-Developers mobile app
hard bricked
i need to unbrick ( Qualcomm DLoader mode ) no recovery no boot. :crying:
p.d. Sorry for reviving old threats but I need it i have no phone or money to have another one :/
It seems no matter how much this topic gets discussed, people still use old methods and they either fail, or they break something like WiFi, Mobile Data, infinite bootloop, or getting stuck on the boot logo... THIS DOESN'T HAVE TO HAPPEN and it IS repairable, usually without reflashing the entire image. The problem comes from using an old method, outdated SuperSU, or incorrect method. This guide will help you correct most issues, or help you to flash root correctly the FIRST time.
I have written rooting guides for multiple Moto device, and I have owned many Moto devices as well, so I have some idea what I am saying and I have tested these methods extensively, they work.
------------------------
This guide covers ALL Moto X 2015 models that can be bootloader unlocked and have TWRP available, it doesn't matter if it is the XT1575 or XT1572, the method is identical (untested on Chinese XT1570, but it should work). In fact, this method will work on all 2015 and 2016 series Moto phones running Marshmallow, including the Moto E, X, G3, G4, and Z with the appropriate TWRP image.
Please read completely and make sure you understand each step and how to do it, if you don't get something search the thread or ask an open question, no offense, but do not PM me with a question because you think it is too stupid to ask in public (we all started as noobs), or because you want me to hold your hand and do it for you, I will politely tell you no and ask you to post in the thread.
If you are coming here because you followed an old guide where you used a special boot.img file and now you have no service (WiFi and/or mobile data) and you don't have a TWRP backup to restore first, well, the RIGHT way to fix it is to reflash the current stock firmware image and start over... why? Because the various "help" people give to have you flash the radio files that match the kernel (ie. boot image) that was patched for the old style root method, has now put you in a mismatched firmware environment and could potentially brick on the next OTA. If you are in this situation and don't know for to properly fix it... go to the FAQ section in post #3 below (WIP-incomplete).
If came are coming here to root the first time, or you just thought you could flash SuperSU and reboot and now stuck in either a bootloop or stuck on the boot logo... Your in luck, read on, because we can fix that in a jiffy!
tl;dr version for advanced users: Skip to "How to do it" section to root, or "Do the prep" section to fix a bad root.
I am writing this tutorial because there are still lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto X P/S, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover the details of rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread.
Prerequisites:
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: Performing this prerequisite will give you all the tools (fastboot) and drivers needed to continue, and wipe your device, meaning erase all your information and programs. Make sure to backup any important data first. This step will also permanently void your warranty once an unlock code has been issued by Moto, it doesn't matter if you even use it, your warranty is done.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See the official TWRP pages for clark here. I will NOT teach you how to use TWRP in this thread, if you are going to root you need to understand that your self, but if you get in a real bind I may knudge you in the right direction. I will tell you that there are two modes, flashed or booted, the later is much better if you plan to take an OTA later as long as you don't do something stupid like flash Xposed.
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device, you can always fine the latest stable version here: https://download.chainfire.eu/supersu/ As of this posting update UPDATE-SuperSU-v2.82-20170528234214.zip (version 2.82) is the current stable version and it has been tested and verified to work.
NOTE: Unless otherwise stated, do not use a beta version for rooting Moto devices. SuperSU versions with even numbers are stable versions, while odd numbered versions are beta editions.
4) Reboot and start TWRP recovery, the method you use to do this doesn't matter (boot or flash).
5) Backup your device with TWRP to your SD card, even if you just unlocked and the phone is as blank as a printed page from a 1988 HP DeskJet printer with it's original cartridges still installed, backup... You will always have a good point to return to if the worst happens.
Do the prep:
Note that the hidden Do the prep section is ONLY for repairing a bad flash, SuperSU has been updated and as of version 2.79 the hidden section should no longer be needed for general purpose root on a working device, you just flash SuperSU. If you flashed an older version and are bootlooped, perform this section and continue.
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, when you have your backups and are ready to root, first go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press ENTER (there is no confirmation returned). You can verify this worked correctly by entering 'cat /data/.supersu' in the terminal and see if it returns "SYSTEMLESS=true", if not, you did it wrong, try the echo command again. Now press exit/back and press the HOME key.
After you have successfully entered the command in the TWRP Terminal you may continue
How to do it:
Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
Again, this is somewhat dated information and only applies to fixing a bootlooping device when improperly rooted.
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
If you need assistance, we need detailed information about what what's going on and what you have tried to do... Please provide details including:
1) Device model number and Android version
2) TWRP version
3) SuperSU version
4) Output of 'cat /data/.supersu' from TWRP terminal
And a copy of recovery.log if possible, and any other pertinent information you can think of. Without specific information there is nothing that I can do to assist you and request for help may be ignored.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
NOTE: I no longer own this device, but will help where I can and will keep this thread open to assist users where ever possible, but I no longer have a device to test/verify things with.
Alternate Method #1
Some users have noted that the above method doesn't seem to work, we don't know why as it seems inconsistent but we can't pin it down specifically to user error, certain model number or build, or anything else, as it works 98% of the time...
But if the above method fails, the alternative is to download and copy to SD card or internal storage SuperSU 2.62-3 ßeta version available here and flash it through TWRP like normal.
Reserved - FAQ (oops, guess I already did that)
I'm so glad I found this thread! I've been procrastenating fixing my phone because of all the crappy methods. This one very easy to follow!
But still can't manage to get my WiFi working
I don't get it. But somehow my nandroid backup failed too, because it's only some 2.X MB big and I don't seem to recover anything....
So I guess I'll have to keep trying..
FYI:
1) Moto X Style 6.0
2) TWRP 3.0.2-0
3) Tried both 2.78 and 2.62. Currently running 2.62
4) SYSTEMLESS=true
Jorinde123 said:
I'm so glad I found this thread! I've been procrastenating fixing my phone because of all the crappy methods. This one very easy to follow!
But still can't manage to get my WiFi working
I don't get it. But somehow my nandroid backup failed too, because it's only some 2.X MB big and I don't seem to recover anything....
So I guess I'll have to keep trying..
FYI:
1) Moto X Style 6.0
2) TWRP 3.0.2-0
3) Tried both 2.78 and 2.62. Currently running 2.62
4) SYSTEMLESS=true
Click to expand...
Click to collapse
Find the latest rom image for the version you have installed, and flash the radios with fastboot.
acejavelin said:
Find the latest rom image for the version you have installed, and flash the radios with fastboot.
Click to expand...
Click to collapse
Thanks for your quick reply. Tried that, didn't work.. The ROM i'm currently running is MPH24.49-18 btw... I'm now trying it the hard way, just reverting everything step by step. But the first step (flashing gpt.bin) is already giving me the preflash error. This is going to be a lot harder than I thought and it's been too long since I've been flashing these things.
Used to flash my Moto Milestone and my Sony X10, can you imagine.
Jorinde123 said:
Thanks for your quick reply. Tried that, didn't work.. The ROM i'm currently running is MPH24.49-18 btw... I'm now trying it the hard way, just reverting everything step by step. But the first step (flashing gpt.bin) is already giving me the preflash error. This is going to be a lot harder than I thought and it's been too long since I've been flashing these things.
Used to flash my Moto Milestone and my Sony X10, can you imagine.
Click to expand...
Click to collapse
Because you are not on 49-18, if you were on the latest OTA for 6.0 you were on 49-18-4. Pre-flash validation failure confirms your using the wrong version. Look in my sig for the return to stock thread, there are links to current roms and discussion of the 'preflash validation error'.
Wasn't systemless method only intended for not altering the system partition in such way not to break compatibility with Android Pay and such apps that don't allow root?
Maybe I got it wrong when I first saw the appearance on the scene of systemless root. From what you are saying the auto detect it's supposed to detect with which method the device is compatible (not only detects if system was already modified? let's say like by TWRP).
I wasn't able to flash SuperSu newest stable versions either, all ended up stuck at boot, except for the 2.62 version (updatable later through playstore and binaries thorugh app via normal update). Honestly I haven't tried systemless as for me I through it was a waste (as said I through it wasn't meant for other purpose).
ATM I'm using CM's own root, but I will report as soon as I will try SU again. I never had problems with modem/wifi with SU, only that it didn't boot on newer stable builds.
Got the Moto X Pure a few days ago. It came with 6.0. This procedure works. Thank you!
ban.codrut said:
Wasn't systemless method only intended for not altering the system partition in such way not to break compatibility with Android Pay and such apps that don't allow root?
Maybe I got it wrong when I first saw the appearance on the scene of systemless root. From what you are saying the auto detect it's supposed to detect with which method the device is compatible (not only detects if system was already modified? let's say like by TWRP).
I wasn't able to flash SuperSu newest stable versions either, all ended up stuck at boot, except for the 2.62 version (updatable later through playstore and binaries thorugh app via normal update). Honestly I haven't tried systemless as for me I through it was a waste (as said I through it wasn't meant for other purpose).
ATM I'm using CM's own root, but I will report as soon as I will try SU again. I never had problems with modem/wifi with SU, only that it didn't boot on newer stable builds.
Click to expand...
Click to collapse
No, although that was one thing we thought we would gain (which we didn't), Systemless root is to get around Marshmallow security. Root is detected by SafetyNet API, and it detects pretty much any system modification, systemless or not
Currently Using TWRP 3.0.2.0 . Just unlocked bootloader and haven't done anything else . Recovery flash went well during the initial process of unlocking . Now Im trying to make a backup of the stock Rom , everytime I try to make one I keep getting failed at the end of the process ? Is this a known bug ? I have been doing google searches for the past hour and still unable to find anything to indicate anyone else is having this problem . Unless I didn't use the correct terms while searching . Any help would be appreciated
SouthernEvo said:
Currently Using TWRP 3.0.2.0 . Just unlocked bootloader and haven't done anything else . Recovery flash went well during the initial process of unlocking . Now Im trying to make a backup of the stock Rom , everytime I try to make one I keep getting failed at the end of the process ? Is this a known bug ? I have been doing google searches for the past hour and still unable to find anything to indicate anyone else is having this problem . Unless I didn't use the correct terms while searching . Any help would be appreciated
Click to expand...
Click to collapse
It is not a known issue... Where are you storing the backup, internal storage or SD card?
acejavelin said:
It is not a known issue... Where are you storing the backup, internal storage or SD card?
Click to expand...
Click to collapse
Was backing up to the SD Card . Been messing with it and now its working for some weird reason . I appreciate your quick response though
I used windroid to unlock the bootloader and install twrp( don't reboot system but rather boot into recovery to make twrp stick) , from there I just flashed supersu and I was good to go. Many methods out there but this worked for me.
Thank you so much for this guide. I have to say, as a new Motorola user coming from Samsung phones exclusively, this whole process made me feel like a real noob again.
I made the switch from iOS to Android back when the Galaxy S2 came out because I grew tired of the jailbreak cat and mouse games on the iPhones and iPads. Learning to root and flash ROMs on all my subsequent Samsung devices was fairly simple and very enjoyable. This Moto X Pure though was a real tasker for me. I honestly never knew about the extra steps you had to take to unlock, twrp and root this phone. I really wish manufactures would help us make this much easier.
Anyway, thank you again for your help. I'll be seeing y'all around the forums as a new MXPE user!
acejavelin said:
No, although that was one thing we thought we would gain (which we didn't), Systemless root is to get around Marshmallow security. Root is detected by SafetyNet API, and it detects pretty much any system modification, systemless or not
Click to expand...
Click to collapse
Thank you for clarifying a misconception I had on systemless root
(I intentioned to reply to you earlier, but the mad busy week made me forget about my intent )
I'm going to try right now the latest stable with systemless method (rather than flashing the older version) on a full wiped clean stock to see if it works. (Even tho I see lots of feedbacks here inspiring me to believe it would)
In what order?
acejavelin said:
It seems no matter how much this topic gets discussed, people still use old methods and they either fail, or they break something like WiFi, Mobile Data, infinite bootloop, or getting stuck on the boot logo... THIS DOESN'T HAVE TO HAPPEN and it IS repairable, usually without reflashing the entire image. The problem comes from using an old method, outdated SuperSU, or incorrect method. This guide will help you correct most issues, or help you to flash root correctly the FIRST time.
I have written rooting guides for multiple Moto device, and I have owned many Moto devices as well, so I have some idea what I am saying and I have tested these methods extensively, they work.
------------------------
This guide covers ALL Moto X 2015 models that can be bootloader unlocked and have TWRP available, it doesn't matter if it is the XT1575 or XT1572, the method is identical (untested on Chinese XT1570, but it should work). In fact, this method will work on all 2015 and 2016 series Moto phones running Marshmallow, including the Moto E, X, G3, G4, and Z with the appropriate TWRP image.
Please read completely and make sure you understand each step and how to do it, if you don't get something search the thread or ask an open question, no offense, but do not PM me with a question because you think it is too stupid to ask in public (we all started as noobs), or because you want me to hold your hand and do it for you, I will politely tell you no and ask you to post in the thread.
If you are coming here because you followed an old guide where you used a special boot.img file and now you have no service (WiFi and/or mobile data) and you don't have a TWRP backup to restore first, well, the RIGHT way to fix it is to reflash the current stock firmware image and start over... why? Because the various "help" people give to have you flash the radio files that match the kernel (ie. boot image) that was patched for the old style root method, has now put you in a mismatched firmware environment and could potentially brick on the next OTA. If you are in this situation and don't know for to properly fix it... go to the FAQ section in post #3 below (WIP-incomplete).
If came are coming here to root the first time, or you just thought you could flash SuperSU and reboot and now stuck in either a bootloop or stuck on the boot logo... Your in luck, read on, because we can fix that in a jiffy!
tl;dr version for advanced users: Skip to "How to do it" section
I am writing this tutorial because there are still lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto X P/S, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover the details of rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread.
Prerequisites:
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: Performing this prerequisite will give you all the tools (fastboot) and drivers needed to continue, and wipe your device, meaning erase all your information and programs. Make sure to backup any important data first. This step will also permanently void your warranty once an unlock code has been issued by Moto, it doesn't matter if you even use it, your warranty is done.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See the official TWRP pages for clark here. I will NOT teach you how to use TWRP in this thread, if you are going to root you need to understand that your self, but if you get in a real bind I may knudge you in the right direction. I will tell you that there are two modes, flashed or booted, the later is much better if you plan to take an OTA later as long as you don't do something stupid like flash Xposed.
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device, you can always fine the latest stable version here: https://download.chainfire.eu/supersu/ As of this posting SR4-SuperSU-v2.78-SR4-20161115184928.zip is the current stable version and it has been tested and verified to work.
NOTE: Unless otherwise stated, do not use a beta version for rooting Moto devices. SuperSU versions with even numbers are stable versions, while odd numbered versions are beta editions.
4) Reboot and start TWRP recovery, the method you use to do this doesn't matter (boot or flash).
5) Backup your device with TWRP to your SD card, even if you just unlocked and the phone is as blank as a printed page from a 1988 HP DeskJet printer with it's original cartridges still installed, backup... You will always have a good point to return to if the worst happens.
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. You can verify this worked correctly by entering 'cat /data/.supersu' and see if it returns "SYSTEMLESS=true", if not, you did it wrong, try the echo command again.
Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
If you need assistance, we need detailed information about what what's going on and what you have tried to do... Please provide details including:
1) Device model number and Android version
2) TWRP version
3) SuperSU version
4) Output of 'cat /data/.supersu' from TWRP terminal
And a copy of recovery.log if possible, and any other pertinent information you can think of. Without specific information there is nothing that I can do to assist you and request for help may be ignored.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Click to expand...
Click to collapse
I really appreciate the help, but I have one question. Do I flash SuperSu and then type the command into the terminal, or do I type the terminal command first?
Thanks again for your help,
Matt
Iglooian said:
I really appreciate the help, but I have one question. Do I flash SuperSu and then type the command into the terminal, or do I type the terminal command first?
Thanks again for your help,
Matt
Click to expand...
Click to collapse
First, a little etiquette lesson, please don't quote long posts (especially the first post) for no reason, at the very least edit it down to only show the relevant parts so people don't have to scroll through a long meaningless quote.
And to answer your question, you enter the terminal command first, then install SuperSU, that is how it is ordered in the first post instructions. If you read the entire first post, it explains what the command does, and logic therefore lets you know it must be done first.
acejavelin said:
First, a little etiquette lesson, please don't quote long posts (especially the first post) for no reason, at the very least edit it down to only show the relevant parts so people don't have to scroll through a long meaningless quote.
And to answer your question, you enter the terminal command first, then install SuperSU, that is how it is ordered in the first post instructions. If you read the entire first post, it explains what the command does, and logic therefore lets you know it must be done first.
Click to expand...
Click to collapse
Actually, it was unclear what order I was supposed to do it in; we call that a clarifying question, but thanks anyway.
Iglooian said:
Actually, it was unclear what order I was supposed to do it in; we call that a clarifying question, but thanks anyway.
Click to expand...
Click to collapse
Fair enough... I will edit the "How to do it" section to make it more clear.
iPioneer Stock v1 for LG Aristo (LGMS210)(10i)
Disclaimer:
/***
* Your warranty is void now (and I'm sure it was void before this process).
* I am not responsible for hard or soft bricked devices, boot loops, dead or corrupt sd cards, strange behavior or you getting a heart attack 'cuz your youtube app is not working properly.
* YOU and only YOU are choosing to make these modifications, do not blame on me.... I will just ignore you.
***/
This rom is a stock rom and is almost 100% stock but it comes without dm-verity to avoid boot problems in case you want to preserve your custom recovery.
This rom is meant to be used in case of emergency, give a fresh start to your device, restore your device in case of corruption or just to play around.
I have tested this rom on my own device and everything is working properly.
Please check the specifications at the end of this op.
Requisites:
New assert-fixed twrp version forked from messi's twrp
Note: All the credit for twrp goes to @messi2050, this is just an assert revision of the current twrp made from messi. It will be deleted as soon as we get an updated version with the right assert tags.
Installation steps
Download the new assert-twrp version and flash it as you would normally do it.
Standard Wipe (factory reset) and Format Data are optional (unless you have a non-stock based rom installed already). If you want a full fresh start you should format data, reboot into recovery again and do an standard wipe x3.
Install the rom.
Download files:
New assert-fixed twrp version: https://www.androidfilehost.com/?fid=889764386195921266
Rom: https://www.androidfilehost.com/?fid=817550096634786356
Device: LG Aristo
Model: LGMS210
Code Name: lv3
Carrier: MetroPCS
Android version: 7.0
Software version: MS21010i
Patch level: April 1, 2017
#####
Update
------------
Please read requisites and download the new file using the new link.
With this new assert-fixed version of the current twrp made from messi we can now avoid issues flashing the original iPioneer Rom.
NOTE: This will only work on MetroPCS, not sure about tmobile, I will try to make it for both carriers...
Reserved 1...
Reserved 2...
Screens if you can?
bwinbig_87 said:
Screens if you can?
Click to expand...
Click to collapse
I think you mean screenshot right??
I usually don't take screenshots on my stock roms, basicly because there is nothing new/fancy to show. It is stock and it'll look the same as when you buyed your phone, with the same default wallpaper and apps...
I take screenshots in my slim versions (wich I will start soon).
For some reason doing the Vol - and Power does the same wipe problem as in Messi's V1 of twrp for me. Am i doing something wrong?
Lgms210 custom roms
My name is red208 and I just want to know if there is a custom ROM for MetroPCS LG ms210 preferably like Resurrection Remix I also want to know if this stock
ROM right here is at all any different form the way metro does it? Im really trying to bypass the 8 gig hotspot restrictions that metro has so it can be a truly unlimited hotspot and i know the easiest way to do that is too just Flash a custom rom plz help me??!!?
bwinbig_87 said:
For some reason doing the Vol - and Power does the same wipe problem as in Messi's V1 of twrp for me. Am i doing something wrong?
Click to expand...
Click to collapse
You mean that you power off your device and the use the Volume Key and Power hit yes twice, right???
If that is the case you could try flashing DM-Verity or SuperSu again to avoid that little bootloop. Or you can just stick (like me) to do and ADB REBOOT RECOVERY.
Please notice that I never mentioned that the bug-fixed twrp was intended for this bootloop/reset issue, it just correct some asserts problems that block our devices from installing this rom and any other room with the right and original asserts.
red208 said:
My name is red208 and I just want to know if there is a custom ROM for MetroPCS LG ms210 preferably like Resurrection Remix I also want to know if this stock
ROM right here is at all any different form the way metro does it? Im really trying to bypass the 8 gig hotspot restrictions that metro has so it can be a truly unlimited hotspot and i know the easiest way to do that is too just Flash a custom rom plz help me??!!?
Click to expand...
Click to collapse
Question 1: There is not at the moment, I will start with Leaneage OS after doing my slim version. I don't know how many time it will take as this is my second device and I am just playing around with it (my V20 give me more pleasure).
Question 2: Stock means Stock... Nothing new nor fancy, same setup, apps, etc.... I mention on the OP what this rom porpuse is.
Hotspot issue: not all the time depends on a custom rom, this is my first device with metropcs service, I don't know if they sync your hotspot usage with their servers. If they do you are not going to be able to bypass that. Any ways my slim version it would get rid of plenty of bloatware and it may work if they depend on the main app on the device.
red208 said:
My name is red208 and I just want to know if there is a custom ROM for MetroPCS LG ms210 preferably like Resurrection Remix I also want to know if this stock
ROM right here is at all any different form the way metro does it? Im really trying to bypass the 8 gig hotspot restrictions that metro has so it can be a truly unlimited hotspot and i know the easiest way to do that is too just Flash a custom rom plz help me??!!?
Click to expand...
Click to collapse
The hotspot will be monitored regardless of if you're using a stock room or custom. The only difference being that on a custom rom, you won't receive a notification stating you went over 8 gigs. Once you hit the 8 gig limit, your hotspot speed will be slowed down.
Also, when you go over your 8 gigs of high-speed hotspot it won't reset at the beginning of your pay period, but exactly a month (to the day) after you went over.
So say your pay period is the 5th and you go over your limit on the 4th. You'd have to wait until the 4th of the following month before you get high speed back.
---------- Post added at 07:36 PM ---------- Previous post was at 07:33 PM ----------
xtremelora said:
Question 1: There is not at the moment, I will start with Leaneage OS after doing my slim version. I don't know how many time it will take as this is my second device and I am just playing around with it (my V20 give me more pleasure).
Question 2: Stock means Stock... Nothing new nor fancy, same setup, apps, etc.... I mention on the OP what this rom porpuse is.
Hotspot issue: not all the time depends on a custom rom, this is my first device with metropcs service, I don't know if they sync your hotspot usage with their servers. If they do you are not going to be able to bypass that. Any ways my slim version it would get rid of plenty of bloatware and it may work if they depend on the main app on the device.
Click to expand...
Click to collapse
I was just about to ask if your slim rom would be a debloat, but now I know. So good look there.
Also, if and when you get down on lineage. I'll be more than happy to test, I had been working on it myself before I blew up my hard drive. So I'd rather help then be a sponge.
Im also willing to test.
Ufffff...
Ok guys... After several days testing / building the slim version I am getting really frustated and dissapointed...
Everytime something goes wrong there is no way to boot into recovery mode using hard keys, that only makes twrp wipe and reboot but not entering on the complete twrp options. So everytime that I flash the test .zip of the slim version and I get an error before actually booting completely into the normal system I have to go to Mocosoft (windows) and use LGUP to flash the .kdz and start from scratch all over.
I hate to have to reboot my laptop and use Mocosoft, I really hate not been able to reboot in recovery mode as in other LG devices with the hardkeys.
I guess is another limitation of the actuall twrp version that we have, maybe we will have to wait for an updated twrp version to avoid all this trauma.
Right now I feel like I'm done with this device, I have used LGUP around 15 times in 3-5 days just because I can no go into twrp.
If this is happening with a stock based slim version I don't want to think about building/testing lineageos.
If you know an option to go to twrp version after a corrupted/incomplete system tell me about please. I have used the followings procedure but not success:
1.- Hardkeys (just makes twrp wipe the system).
2.- Fastboot boot twrp.img (command fails).
3.- Flashing original twrp (from messi) and then the flashing back the bug-fixed twrp (forked from messi) and trying to reproduce the first boot taking out the battery and using hardkeys (no luck, still wipes the system and reboot by it self).
Sorry guys, I think I will stop for a few days... Maybe I need to go out and have a little fun and come back...
Lgms210
any luck?
n33b said:
any luck?
Click to expand...
Click to collapse
Actually yes...
@messi2050 already builded an updated twrp version avoiding problems with the Hardkeys...
So now I can continue with the test and after that with Lineage if no body build it first... :laugh:
xtremelora said:
Actually yes...
@messi2050 already builded an updated twrp version avoiding problems with the Hardkeys...
So now I can continue with the test and after that with Lineage if no body build it first... :laugh:
Click to expand...
Click to collapse
I hope you can success with lineage 14.1, i wasn't able to make it boot on the stylo 2 plus since ms210 and ms550 are almost the same if you managed to boot it then I'm sure it will work on the stylo too, good luck.
I know it's really late, but I was just gonna say build a version of your rom with the flags for Messi's twrp and just use that to flash.
Either way, I'm glad you managed to sort the shiz out and I'm wishing you the best of luck with development.
ninjasinabag said:
I know it's really late, but I was just gonna say build a version of your rom with the flags for Messi's twrp and just use that to flash.
Either way, I'm glad you managed to sort the shiz out and I'm wishing you the best of luck with development.
Click to expand...
Click to collapse
???
I don't get it?
You mean the asserts right?
I haven't test the new twrp version of messi (no free time), so you are telling me that the new version still have the wrong flags?
I usually don't remove the CORRECT flags from my roms (a Tmo user could flash the metropcs and cause a brick/softbrick for example) to avoid user's mistakes/misread...
xtremelora said:
???
I don't get it?
You mean the asserts right?
I haven't test the new twrp version of messi (no free time), so you are telling me that the new version still have the wrong flags?
I usually don't remove the CORRECT flags from my roms (a Tmo user could flash the metropcs and cause a brick/softbrick for example) to avoid user's mistakes/misread...
Click to expand...
Click to collapse
The new version has the correct flags. I never said it didn't.
I'm saying that a twrp can be created with unified flags allowing a room to be shared between devices without having to build between the lv3 and the aristo. Sorta like what had been done with the LG Leon a couple years ago.
Instead of using the h or Ms flags relating to model number, you can use the consistent board config as the basis.
Either way, the only way someone could brick or soft brick from this method is if it were like the S4 situation where you have to flash the carrier specific kernel version for the device. Like using the At&t rom on the Verizon s4 will cause a soft brick until you flash the Verizon s4 kernel.
This is only just an idea in response to you having to go back and forth (before you got the updated twrp) on recovery versions during your tests
OP updated to link and point to the new and updated twrp version from messi.
You guys no longer need the bug-fixed twrp version as before.
Sent from my LGMS210 using Tapatalk
xtremelora said:
OP updated to link and point to the new and updated twrp version from messi.
You guys no longer need the bug-fixed twrp version as before.
Sent from my LGMS210 using Tapatalk
Click to expand...
Click to collapse
Can you do me a solid, sorry if I'm turning into an annoyance. Add "lg aristo" into either the thread tags or into the thread name itself. It'll add the thread into the Aristo board for easier access and make this easier to find. I recommended your rom to another user who had no idea what I was even talking about. (So I shared the link if you don't mind me doing so)
First of all, don't get your hopes high, i rooted as traditional method like many others. I'm flashaholic and i started new thread for those who upgraded intentionally or accidentally and now think download would brick their sets. it won't. things are pretty obvious here but i repeat I'm sharing this to people who've upgraded for any reasons and have no clue how to downgrade or achieve root.
So i bought a cell (sm g920V) with preinstalled PI2 (MM6.0.1) . found out pingpong root is avail only for 5.02 . i was afraid to downgrade so i searched more. found out nogat 7.0 DQD1 has root. and can be rooted via cf autoroot. i upgraded and i tried. but it didn't worked. on nougat i did everything. tried every root app (both pc and apk ver) but failed. i decided to go back.
here i found This thread by @toutanje which said even i upgraded to nougat, i can safely downgrade to PK2 (6.0.1) , PH1 (6.0.1) and BOG7 (5.1.1) . i flashed BOG7 (5.1.1) directly because during search i've foundout that there is temporary root available for BOK7, and they both are 5.1.1. i did this because BOG7 is earlier version than BOK7, for this i won't have to downgrade but to upgrade that i did. i flashed BOK7 and headed Here, a thread by @klip1 . there wasn't any clear instructions not links no attachments. but thanks to @MrMike2182 who shared main file Here. BEWARE that you'll lose root each time you reboot, but you can gain it back easily by running root apk simply from your mobile. this is better then not having one.
so if you desperately want root. wherever you're on nougat DQD1 or MM. Downgrade to BOK7.
simply follow instructions there and all you have to do is to flash BOG7 from thread mentioned above (for safety as i did did step and i'm not sure if you may directly downgrage to BOK7), then flash BOK7, odin Sboot file (attached). you'll see some yellow codes above when restart. i was stuck there with bootloop on VZ logo. all you need to do is to factory reset. (by pressing and hold vol + & vol down + power button until you see black screen with options. press vol down and highlight second option factory data and reset. now press home button. )
phone will start normally, goto devloper options, enable usb debug, allow unknown sources and than root it with kingroot apk. done.
Those who prefer SuperSu can get lead from Here thanks to @EvilRubberDuck. but i am not sure about point 3. there is nothing attached at first post. tough little search may lead you to success.
Thanks to whoever took even little interst to make this beast rooted. please try to get permanent root for this device too. if anyone know how to get it, or any more info regarding rooting this device. please share. let me aware. i'll really appreciate that.
NOTE : i take no responsibility of what you do to your mobile. you're doing it with your own consent. if you're unsure what you're doing, don't do it. I, developers/members mentioned and xda are not responsible for ANYTHING or what you do to your phone.
Sharjeel.Khan said:
First of all, don't get your hopes high, i rooted as traditional method like many others. I'm flashaholic and i started new thread for those who upgraded intentionally or accidentally and now think download would brick their sets. it won't. things are pretty obvious here but i repeat I'm sharing this to people who've upgraded for any reasons and have no clue how to downgrade or achieve root.
So i bought a cell (sm g920V) with preinstalled PI2 (MM6.0.1) . found out pingpong root is avail only for 5.02 . i was afraid to downgrade so i searched more. found out nogat 7.0 DQD1 has root. and can be rooted via cf autoroot. i upgraded and i tried. but it didn't worked. on nougat i did everything. tried every root app (both pc and apk ver) but failed. i decided to go back.
here i found This thread by @toutanje which said even i upgraded to nougat, i can safely downgrade to PK2 (6.0.1) , PH1 (6.0.1) and BOG7 (5.1.1) . i flashed BOG7 (5.1.1) directly because during search i've foundout that there is temporary root available for BOK7, and they both are 5.1.1. i did this because BOG7 is earlier version than BOK7, for this i won't have to downgrade but to upgrade that i did. i flashed BOK7 and headed Here, a thread by @klip1 . there wasn't any clear instructions not links no attachments. but thanks to @MrMike2182 who shared main file Here. BEWARE that you'll lose root each time you reboot, but you can gain it back easily by running root apk simply from your mobile. this is better then not having one.
so if you desperately want root. wherever you're on nougat DQD1 or MM. Downgrade to BOK7.
simply follow instructions there and all you have to do is to flash BOG7 from thread mentioned above (for safety as i did did step and i'm not sure if you may directly downgrage to BOK7), then flash BOK7, odin Sboot file (attached). you'll see some yellow codes above when restart. i was stuck there with bootloop on VZ logo. all you need to do is to factory reset. (by pressing and hold vol + & vol down + power button until you see black screen with options. press vol down and highlight second option factory data and reset. now press home button. )
phone will start normally, goto devloper options, enable usb debug, allow unknown sources and than root it with kingroot apk. done.
Those who prefer SuperSu can get lead from Here thanks to @EvilRubberDuck. but i am not sure about point 3. there is nothing attached at first post. tough little search may lead you to success.
Thanks to whoever took even little interst to make this beast rooted. please try to get permanent root for this device too. if anyone know how to get it, or any more info regarding rooting this device. please share. let me aware. i'll really appreciate that.
NOTE : i take no responsibility of what you do to your mobile. you're doing it with your own consent. if you're unsure what you're doing, don't do it. I, developers/members mentioned and xda are not responsible for ANYTHING or what you do to your phone.
Click to expand...
Click to collapse
If you use the SuperSU instead of KingRoot then you can use my installroot script and then the rootatboot if you need to reboot for some reason however if you are not near a PC at the time and you really need to reboot then use terminal emulator from the play store and open it and type su then enter and on the next line type pkill zygote and voila reboots without PC.
MrMike2182 said:
If you use the SuperSU instead of KingRoot then you can use my installroot script and then the rootatboot if you need to reboot for some reason however if you are not near a PC at the time and you really need to reboot then use terminal emulator from the play store and open it and type su then enter and on the next line type pkill zygote and voila reboots without PC.
Click to expand...
Click to collapse
yes i've read this post of yours, i should've added this. Glad you came here and i really appreciate your efforts for s6 users. you've done great job for us.
it'll be great if you attach your script and write or quote your method here too. so users don't have to go through earlier threads and finding things. like me who bought this phone pretty late.
right now i'm using quickreboot apk to get hot reboot which keeps the root. but sometimes when you really need to restart. i see your solution as best.
Sharjeel.Khan said:
yes i've read this post of yours, i should've added this. Glad you came here and i really appreciate your efforts for s6 users. you've done great job for us.
it'll be great if you attach your script and write or quote your method here too. so users don't have to go through earlier threads and finding things. like me who bought this phone pretty late.
right now i'm using quickreboot apk to get hot reboot which keeps the root. but sometimes when you really need to restart. i see your solution as best.
Click to expand...
Click to collapse
OK so my phone is on 5.1.1, it was originally on 7.0 so you can downgrade back to the 5.1.1 firmware.. I've included in the file the eng kernel and eng sboot but there's different versions so this one in my file called boot.tar is from the eng kernel to the S6 G925V so if you're using G920V you need to get the eng kernel for that one.. Now first you put the phone into download mode and flash the eng kernel using odin and after the phone boots then using Windows command prompt navigate using the cd command to where the file is you downloaded called S6rootbyMrMike2182 once you're in there type installroot and the script should run and flash everything needed including busybox and then the phone will reboot (it will also boot just this one time without using the rootatboot because the same codes in this file too) now when you click on the SuperSU app it's going to say it needs to update su ignore it and go right to the play store and install/update the SuperSU from there and then the phone should be rooted and ready to go.. If you ever need to reboot for some reason connect the phone to your PC and open a command prompt in the same folder again and run rootatboot and it will set the phone as permissive again so it boots.. You can unplug it after you see the Verizon logo.. If for some reason you aren't near a computer and you really need to reboot then use terminal emulator from the play store and open it and type su and grant root access and then on the next line type pkill zygote and voila reboots without a computer
If you have KingRoot on your phone and you want to get rid of it to use SuperSU thanks to @Chainfire then use this script that I'm listing below.. Also keep terminal emulator open while you are doing this because you might(not all devices just some) get a continuous annoying popup that prevents you from doing anything (thanks to KingRoots junk) so you'll have to use terminal emulator to kill/end that process in order to continue and after you kill/end that process then go delete it immediately! Links to root with SuperSU and KingRoot removal are below!
S6EdgeRootByMrMike2182
KingRoot removal script
G920V ENG Sboot
By the way I nor XDA-DEVELOPERS is responsible for anything you choose to do to your phone! If something goes wrong, just reflash your original firmware but don't go blaming me nor XDA because I don't have to put this up so please do your research before messing with your phone and as always, make a backup of everything you wish to keep! And no this will not delete or wipe your phone unless you choose to! Links are above. You can change it or whatever just give props where it's due!!
SERIOUSLY MAKE A BACKUP OF ALL YOUR PICTURES ETC ETC BEFORE DOWNGRADING AND I'M NOT KIDDING!!!
MrMike2182 said:
OK so my phone is on 5.1.1, it was originally on 7.0 so you can downgrade back to the 5.1.1 firmware.....
Click to expand...
Click to collapse
great. you completed the thread :highfive:
Didn't know about script removing kr.. wil give it a try for sure. :good:
ok i'm getting confuse here. can you please provide exact files that needed to flash on g920V please ? i mean eng kernel and sboot ? and the file with odin says "G920A_Kernel_Root_5.1.1_S****.tar", A ? isn't A refers to at & t ?
i'm afraid if i may flash wrong file. can you please help me here with exact files needed for us (G920v) ?
and when i'm running installroot via cmd, it execute it goes like it created by you until daemon started successfully for like for five to 8 sec and then disappear. phone doesn't reboot. nothing happens. ,
can anyone confirm if i can directly downgrade to BOK7 ? im currently on DQD1 also can anyone guide me how to actually flash my phone like step wise im new here.. I upgraded to 7.0 but I desperately want root now I've odin installed i just need some1 to teach me how to do it like where to select sboot file and other files
Thanks
Sharjeel.Khan said:
so if you desperately want root. wherever you're on nougat DQD1 or MM. Downgrade to BOK7.
simply follow instructions there and all you have to do is to flash BOG7 from thread mentioned above (for safety as i did did step and i'm not sure if you may directly downgrade to BOK7), then flash BOK7.
Click to expand...
Click to collapse
Muhammad Aliyan said:
can anyone confirm if i can directly downgrade to BOK7 ? im currently on DQD1 also can anyone guide me how to actually flash my phone like step wise im new here.. I upgraded to 7.0 but I desperately want root now I've odin installed i just need some1 to teach me how to do it like where to select sboot file and other files
Thanks
Click to expand...
Click to collapse
welcome here. first things first, i don't mean to discourage you but if you don't know about where to "put sboot and other files", you really shouldn't be doing this. additionally downgrading is a risky process where things get messy due to single mistake .
To answer your question directly, NO. i've read a post somewhere here that we can only downgrade to mentioned (in 1st post) firmware. OP there tried to downgrade to other fw but failed.
and that is exactly why i did long and safe procedure and downgraded to BOG7 and then BOK7. . both are 5.1.
2nd question : you need to put sboot file in "AP" section of odin. (be careful with using it)
i assume you have G920V, which have locked bootloader, my suggestion would be... its not worth it. trust me. even if you downgrade, and rooted too, you'll loose root if you restart your device. and you cannot install recovery and so on. there is no permanent root for this device.
Exchange your device for international version or so, either wait for it and enjoy being on nougat. devs are working on it may be. some claim to root nougat too. better don't downgrade and much better if you stop right there when you don't have basic knowledge about this. you'll end up having paper weight instead of device.
Sharjeel.Khan said:
welcome here. first things first, i don't mean to discourage you but if you don't know about where to "put sboot and other files", you really shouldn't be doing this. additionally downgrading is a risky process where things get messy due to single mistake .
To answer your question directly, NO. i've read a post somewhere here that we can only downgrade to mentioned (in 1st post) firmware. OP there tried to downgrade to other fw but failed.
and that is exactly why i did long and safe procedure and downgraded to BOG7 and then BOK7. . both are 5.1.
2nd question : you need to put sboot file in "AP" section of odin. (be careful with using it)
i assume you have G920V, which have locked bootloader, my suggestion would be... its not worth it. trust me. even if you downgrade, and rooted too, you'll loose root if you restart your device. and you cannot install recovery and so on. there is no permanent root for this device.
Exchange your device for international version or so, either wait for it and enjoy being on nougat. devs are working on it may be. some claim to root nougat too. better don't downgrade and much better if you stop right there when you don't have basic knowledge about this. you'll end up having paper weight instead of device.
Click to expand...
Click to collapse
But on 5.1.1 my battery life was so good now it just keeps draining even on power saving just drain and drain I previously also upgraded using Odin from 5.1.1 to 7.0 (biggest mistake) and i'm regretting it although its much better it terms of improvements and performance i just cant live with this battery life also i need root for WifiKill and to hack in-app purchases .. and i don't reboot my device often..
so if im downgrading to both of these BOK7 or BOG7 i need to use the sboot file u provided right ?
Muhammad Aliyan said:
But on 5.1.1 my battery life was so good now it just keeps draining even on power saving just drain and drain I previously also upgraded using Odin from 5.1.1 to 7.0 (biggest mistake) and i'm regretting it although its much better it terms of improvements and performance i just cant live with this battery life also i need root for WifiKill and to hack in-app purchases .. and i don't reboot my device often..
so if im downgrading to both of these BOK7 or BOG7 i need to use the sboot file u provided right ?
Click to expand...
Click to collapse
alright. nothing to worry about. just downgrade like i mentioned on OP (for safe side as no one here to confirm)
okay so like i said you just need to put the provided file (all credits to original dev/coder) in AP section and flash after you install BOK7. .
i can only tell you about BOK7 as i've done and using this. not G7.
so after to downgrade to bok7, let it boot properly. factory reset your phone, go to download mode and flash attached file using odin. (uncheck all options but f reset time and auto reboot)
phone will restart, and you'll see some green numbers and something when booting. let it boot. go to dev options enable usb debugging. uncheck "verify apps usgin adb" and... root either from kingroot (comes with 100 of ads even on lock screen) or look at this post by MrMike2182 who gave us superSU :victory:
and most important part here : make a backup of everything. and i take no responsibility of what you do to your mobile. you're doing it with your own will. if you're unsure what you're doing, don't do it. I, developers/members mentioned here and xda are not responsible for ANYTHING in any way.
good luck :good:
Sharjeel.Khan said:
alright. nothing to worry about. just downgrade like i mentioned on OP (for safe side as no one here to confirm)
okay so like i said you just need to put the provided file (all credits to original dev/coder) in AP section and flash after you install BOK7. .
i can only tell you about BOK7 as i've done and using this. not G7.
so after to downgrade to bok7, let it boot properly. factory reset your phone, go to download mode and flash attached file using odin. (uncheck all options but f reset time and auto reboot)
phone will restart, and you'll see some green numbers and something when booting. let it boot. go to dev options enable usb debugging. uncheck "verify apps usgin adb" and... root either from kingroot (comes with 100 of ads even on lock screen) or look at this post by MrMike2182 who gave us superSU :victory:
and most important part here : make a backup of everything. and i take no responsibility of what you do to your mobile. you're doing it with your own will. if you're unsure what you're doing, don't do it. I, developers/members mentioned here and xda are not responsible for ANYTHING in any way.
good luck :good:
Click to expand...
Click to collapse
Quick question if i can root my device with this method it possible to install xposed framework via Flashfire?, just a question.
If not possible install xposed not a problem, better root than nothing, and i am not reboot so much, to say nothing.
And like say Muhammad Aliyan, the battery in 7.0 is much more less than 5.1.1
(Sorry for my bad english.)
LuisElListo said:
Quick question if i can root my device with this method it possible to install xposed framework via Flashfire?, just a question.
If not possible install xposed not a problem, better root than nothing, and i am not reboot so much, to say nothing.
And like say Muhammad Aliyan, the battery in 7.0 is much more less than 5.1.1
(Sorry for my bad english.)
Click to expand...
Click to collapse
i have tried it earlier and failed but now when i saw youre asking this, i gave it another try and i'm stuck on bootloop. lol.
better don't do it.
i've read it that xposed is not compatible to our devices (64bit) yet ( just read it not confirming it) + in xposed official thread, it has been warned that bootloops occur in samsung stock roms. soi'd say do not try this.
Sharjeel.Khan said:
i have tried it earlier and failed but now when i saw youre asking this, i gave it another try and i'm stuck on bootloop. lol.
better don't do it.
i've read it that xposed is not compatible to our devices (64bit) yet ( just read it not confirming it) + in xposed official thread, it has been warned that bootloops occur in samsung stock roms. soi'd say do not try this.
Click to expand...
Click to collapse
So close, well better wait to safe method in stock room, or unlock bootloader. Thanks anyway.
Sharjeel.Khan said:
alright. nothing to worry about. just downgrade like i mentioned on OP (for safe side as no one here to confirm)
okay so like i said you just need to put the provided file (all credits to original dev/coder) in AP section and flash after you install BOK7. .
i can only tell you about BOK7 as i've done and using this. not G7.
so after to downgrade to bok7, let it boot properly. factory reset your phone, go to download mode and flash attached file using odin. (uncheck all options but f reset time and auto reboot)
phone will restart, and you'll see some green numbers and something when booting. let it boot. go to dev options enable usb debugging. uncheck "verify apps usgin adb" and... root either from kingroot (comes with 100 of ads even on lock screen) or look at this post by MrMike2182 who gave us superSU :victory:
and most important part here : make a backup of everything. and i take no responsibility of what you do to your mobile. you're doing it with your own will. if you're unsure what you're doing, don't do it. I, developers/members mentioned here and xda are not responsible for ANYTHING in any way.
good luck :good:
Click to expand...
Click to collapse
everything was good I downgraded to BOG 7 first with odin all good then OK7 and again all good successfully booted up everything is fine fingerprint sensor etc right after i flash the sboot file my fingerprint sensor stopped working it says an error occurred can you please help me .. phone is rooted though but cmon fingerprint sensor i can't live without it..
Edit: tried factory reset and restarting, none worked.
edit2: reflashed OK7 again and its fingerprint is working but can't root. flashed sboot to root but fingerprint stopped working.
edit3: again flashed OK7 then sboot again green text in the corner again root succeed but again fingerprint not working guess something wrong with the sboot..
Muhammad Aliyan said:
everything was good I downgraded to BOG 7 first with odin all good then OK7 and again all good successfully booted up everything is fine fingerprint sensor etc right after i flash the sboot file my fingerprint sensor stopped working it says an error occurred can you please help me .. phone is rooted though but cmon fingerprint sensor i can't live without it..
Edit: tried factory reset and restarting, none worked.
edit2: reflashed OK7 again and its fingerprint is working but can't root. flashed sboot to root but fingerprint stopped working.
edit3: again flashed OK7 then sboot again green text in the corner again root succeed but again fingerprint not working guess something wrong with the sboot..
Click to expand...
Click to collapse
thats strange because i had FP working while rooted from same sboot file that i attached.
try downloading from another source like in second post where mrmike2182 shared it. and try removing Samsung account (if its there, don't forget to turn off reactivation lock before that.)
see if it helps.
Sharjeel.Khan said:
thats strange because i had FP working while rooted from same sboot file that i attached.
try downloading from another source like in second post where mrmike2182 shared it. and try removing Samsung account (if its there, don't forget to turn off reactivation lock before that.)
see if it helps.
Click to expand...
Click to collapse
Same issue with this flash OK7 FP work ok, but install Sboot and FP not working.
edit1: cant root the device i open cmd with adm permission, installroot, daemon is stop, is starting, after close cmd and the phone not reboot.
LuisElListo said:
Same issue with this flash OK7 FP work ok, but install Sboot and FP not working.
edit1: cant root the device i open cmd with adm permission, installroot, daemon is stop, is starting, after close cmd and the phone not reboot.
Click to expand...
Click to collapse
hmm. i believe FP didn't came friendly with this sboot. any experienced dev might help us out here
make sure you have proper drivers installed and have working adb. read instructions, search fourm. by the way, for same kind of issues, i had to go with kingroot.
Sharjeel.Khan said:
hmm. i believe FP didn't came friendly with this sboot. any experienced dev might help us out here
make sure you have proper drivers installed and have working adb. read instructions, search fourm. by the way, for same kind of issues, i had to go with kingroot.
Click to expand...
Click to collapse
Well better than nothing, uninstall all bloatware for my phone (finally), FP sensor yes it to cool but, meee y si better pin or patron.
Just have to try install Xposed and all done.
Do you try to install official xposed? Or the unofficial for Samsung Stock https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
LuisElListo said:
Well better than nothing, uninstall all bloatware for my phone (finally), FP sensor yes it to cool but, meee y si better pin or patron.
Just have to try install Xposed and all done.
Do you try to install official xposed? Or the unofficial for Samsung Stock https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Click to expand...
Click to collapse
i'd love to try right now but i can't because i'm currently working on something else.
but for your assistance, Here is what you're looking for. its a success.
Sharjeel.Khan said:
i'd love to try right now but i can't because i'm currently working on something else.
but for your assistance, Here is what you're looking for. its a success.
Click to expand...
Click to collapse
I try a shoot.
Its working, its ****ing working, I sacrifices FP, and Supersu but I dont mind i have xposed and a root.
imgur(dot)com/a/zLvrD
Edit1: bad news activated module xposed requeried reboot, soo the root is lost and requiered to root again with kingroot the problem is my percent is not advance 01%. Also every time I rooted the phone is slowing arriving a point where it restarted alone and is only 01%.
If i a factoy reset i lost xposed and root or better reflash the Rom OK7?