After seeing people not being able to root their S3 and rooting mine successfully, I have decided to make this tutorial to help those out there. This tutorial covers the procedures I took to successfully root my LeEco S3 US edition with EUI 5.8.018S and Snapdragon 652 processor. My phone is permantly rooted and has permanent TWRP recovery.
Make sure your phone has developer options and has usb debugging as well as the option to unlock the bootloader enabled
First off, download the AIO Toolkit created by Rishabh Rao here
Secondly, open the toolkit. Make sure to turn off your antivirus to avoid any interruptions. Once in the toolkit, select item 6 and allow the program to download necessary files. After the files have downloaded, select item 1 to install ADB/Fastboot USB drivers. During this process, PDA Net will prompt you to connect your phone to the computer. It will download the client onto your computer and install the PDA Net application onto your phone. When the drivers are fully installed, close the toolkit.
Open command prompt and run ADB. With your phone plugged in and in recovery mode, type fastboot oem unlock-go and you should see it attempting to unlock the bootloader. If you get a successful message of unlocking your bootloader, you are ready to move on to the next step as this is a temporary unlock. Close the command prompt.
Open the toolkit again, select item 6 and then select item 3 to unlock bootloader completely. When it has finished, go back to select item 4 to check and see if the bootloader has been unlocked. If so, move on to selecting item 5 to flash the latest TWRP recovery.
When the TWRP recovery has installed, if it has not booted into recovery by itself, hold down power + volume up to enter it. You will see the recovery all in the chinese language. Simply swipe the unlock to proceed and from the menu, select the box to the right and three down (which is settings). There, select the globe icon and scroll down to select the english language. Now that you can read what is there, go back to the main menu and select wipe to completely wipe the phone back to factory defaults. When it has finished, go back and select Advanced > Tools > Root Device. Your phone will now be rooted when you reboot and will have the latest TWRP recovery installed.
- If you receive the error message saying the device is locked while you are trying to unlock the bootloader from the toolkit, you need to run ADB again to temporary unlock the bootloader.
Quick question - will this only work on 18s and is it possible to update the firmware and keep root after doing this? Or would it work after updating to I think 21s which is the latest?
Thank you!
Hi
Can you break this down further with pictures too? How do I do the command prompt ABD thing?
Root
was this the easiest way? I'm going to try it in two days. Scared to mess my phone up though..
This method does not work on the 23s ROM. Does nothing
What's the best way? Simple way I mean?
Worked for anyone?
these instructions are for the le s3 with SNAPDRAGON processor, not for the MEDIATEK x20 that is where we have the problem
Just got this phone and gonna try this out, thanks ;p
---------- Post added at 11:06 AM ---------- Previous post was at 10:13 AM ----------
Actually Ima wait...I've never rooted using TWRP Recovery so not quite familiar with it after the phone's been rooted. I've only used a couple of the one-click root apps, KingRoot and KingoRoot, for a couple phones.
Rooted it fine, now I need to figure out what I can do ;P <--- noob
How were you able to successfully root the phone?
GWARslave119 said:
Rooted it fine, now I need to figure out what I can do ;P <--- noob
Click to expand...
Click to collapse
How were you able to successfully root the phone?
i dont know what to do,, it says "waiting for device" what should i do ? i already installed the 15 sec ADB something like that.. i need your help plsssss
Rooting Le S3.
XtraTerr3sTRiAL said:
After seeing people not being able to root their S3 and rooting mine successfully, I have decided to make this tutorial to help those out there. This tutorial covers the procedures I took to successfully root my LeEco S3 US edition with EUI 5.8.018S and Snapdragon 652 processor. My phone is permantly rooted and has permanent TWRP recovery.
Make sure your phone has developer options and has usb debugging as well as the option to unlock the bootloader enabled
First off, download the AIO Toolkit created by Rishabh Rao here
Secondly, open the toolkit. Make sure to turn off your antivirus to avoid any interruptions. Once in the toolkit, select item 6 and allow the program to download necessary files. After the files have downloaded, select item 1 to install ADB/Fastboot USB drivers. During this process, PDA Net will prompt you to connect your phone to the computer. It will download the client onto your computer and install the PDA Net application onto your phone. When the drivers are fully installed, close the toolkit.
Open command prompt and run ADB. With your phone plugged in and in recovery mode, type fastboot oem unlock-go and you should see it attempting to unlock the bootloader. If you get a successful message of unlocking your bootloader, you are ready to move on to the next step as this is a temporary unlock. Close the command prompt.
Open the toolkit again, select item 6 and then select item 3 to unlock bootloader completely. When it has finished, go back to select item 4 to check and see if the bootloader has been unlocked. If so, move on to selecting item 5 to flash the latest TWRP recovery.
When the TWRP recovery has installed, if it has not booted into recovery by itself, hold down power + volume up to enter it. You will see the recovery all in the chinese language. Simply swipe the unlock to proceed and from the menu, select the box to the right and three down (which is settings). There, select the globe icon and scroll down to select the english language. Now that you can read what is there, go back to the main menu and select wipe to completely wipe the phone back to factory defaults. When it has finished, go back and select Advanced > Tools > Root Device. Your phone will now be rooted when you reboot and will have the latest TWRP recovery installed.
- If you receive the error message saying the device is locked while you are trying to unlock the bootloader from the toolkit, you need to run ADB again to temporary unlock the bootloader.
Click to expand...
Click to collapse
Hi Everyone. I recently got a new le s3 x522. Its great only that sim 2 slot doesn't connect to mobile data. I have tried rooting so that I can use build prop editor to fix this, but rooting has become a real problem. I used Kingo root, framaroot but not successful. I have downloaded AIO toolkit on pc but installng is a problem. Please guide me on how to install AOI toolkit on pc. I pretty new to this things you know. Any help will be greatly appreciated.
Related
After years fo relying on the XDA community, I thought I'd give something back. I've been for a few days now trying to get the phone properly rooted, however being a bit cautious due to completely screwing up my last phone, was being very careful.
Obviously - This guide carries all the T&Cs you'd expect... will void your warranty, could brick your phone, could fry all electronic devices within a 50 meter radius and such... USE AT YOUR OWN RISK.
Also, credit goes to the people for their hard work in making this possible. I'm only responsible for writing this post.
I'm not sure if you could have gotten away with not doing any of the steps below, but it's this sequence that I followed.. so feel free to play about.
To start off, you need the following
Ingredients
HiSuite software. I used what came with the device. If you put it in HiSuite mode, you should get a folder mounted that contains this software.
USB developer mode needs to be enabled (follow HiSuite's guide as even IT needs debugging mode enabled).
ADB - I used the latest version of Minimal ADB and Fastboot
Download TWRP from here
P7 Easy Update and Adjust from here
King Root from here (I've tried the lot and is the only one I found that actually worked).
Super SU from here. Put it on your phone storage for later.
Preparation
Install ADB, HiSuite and King Root.
Connect the phone to the pc via the USB, turning on PC Suite (HiSuite) mode and USB Debugging enabled. HiSuite should automatically load.. close it
Run King Root and start the rooting process. This should cause your phone to reboot a few times. now, following the application - towards the end of the process it says something about installing a recovery, but (at least on mine) didn't seem to install correctly. Never mind though - phone will still boot as normal, and we'll take care of the recovery next
place the Easy update and adjust excecutable in the folder where you installed ADB and run it (make sure phone is in pc Suite mode with USB debugging again and close the HiSuite app if it pops up on your PC). Note that in the ADB folder you will find a new /recovery/ folder, as well as a stock recovery image. Place the TWRP recovery image we downloaded earlier in this folder as well.
From within the Easy update, select [3] - Delete set_immutable.list / Full root.
After that Select [2] - Flash Recovery (Stock or custom)
Select the TWRP recovery. This will reboot your phone and flash the recovery image, loading back up as normal.
Go back to the Easy update app and select to reboot into recovery. If you attempted this before the last step (7), you'd just see two boot cycles, back into the normal boot up.
flash the Super SU zip and reboot
the next time you boot up, you will get a notification that king user needs something... you need to disable (or uninstall via titanium backup).
And that's it! You have root!
Hi there, just out of curiosity, do you think this method will work for b135?
Cryonisis said:
Hi there, just out of curiosity, do you think this method will work for b135?
Click to expand...
Click to collapse
Everything bar the set_immutable part worked for me.. for that i followed the below:
http://forum.xda-developers.com/ascend-p7/general/rooted-p7-l10-609-t3003605
hope that helped
Wrong thread guys soz.
TWRP recovery version?
Hi,
Will I have to download TWRP version compatible with EMUI 3.1 (which is mine case) or I can use TWRP 2.8.1.0 link that is in your post?
Thank you in advance!
Now, I know this tutorial exists all over the place, like one-click and UnjustifiedDev tutorial but none seemed to work. I am sharing the steps and method I used IN-DEPTH command for command on how to unlock, flash, and root the LG G4 from Tmobile.
NOTE THIS WILL FACTORY RESET YOUR DEVICE SO BACKUP ALL YOUR DATA
1. Activate developer settings by entering the about section and tapping build number 7 times.
2. Enter your developer settings and MAKE sure you have 'Allow OEM unlock' and 'USB Debugging' enabled.
3. Download the latest SuperSU zip and move it onto your SD card.
4. Using the android issue SDK. Open a command window and link it to your SDK folder where ADB is located (typically Platform-Tools)
5. Once the Command window is linked to the folder, connect your device via USB and allow the connection.
6. On the command window type 'adb reboot bootloader' and the device should reboot with the fastboot options on the upper left of the phone screen
7. Once again on the command window type 'fastboot oem unlock' and the command window should say OKAY and complete the action.
8. To Confirm that the device is unlocked type 'fastboot getvar unlock' and the window should respond with 'Unlock: YES'
9. Now download the latest available TWRP and drop it into the platform-tools folder where your ADB.exe is located.
10. On your Command Window type 'fastboot flash recovery "NAME OF TWRP FILE" if you get the error ' cannot load 'twrp-X.X.X.X-h811' you need to add .img to the end of the filename
11. Once the process completes you will see 'target reported max download size of 536870912 bytes
sending 'recovery' (32968 KB)...
OKAY [ 1.088s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time:'
THE FAILED UNKNOWN COMMAND NOTICE CAN BE IGNORED
12. Once the process completes the device may not let you enter recovery from the traditional method using the buttons on the back of the phone so the easiest method is to, on your command window, type
'fastboot boot twrp-2.8.7.0-h811.img' and the device should respond within just a few seconds and reboot into TWRP.
13. Once the device reboots, enter twrp and tap on install and locate the SuperSU.zip and allow it to install.
14. Once the process completes successfully, wipe cache to be safe and reboot your device.
15. Resetup your device and restore your data if necessary and install a root checker from Google Play to confirm root!
THATS IT GUYS! This took me a long time to figure this out and it's a combination of different methods to get it to work!
All credit goes to the Devs of TWRP and SuperSU!
I posted in General because I'm a new user so please move to appropriate forums! thanks!
This thread should be closed as theres already a proper one on here..http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Its more of people really dont like to search and read things
Please refer to the first line of my post. I understand that there are a large series of posts about how to do this but this is the only one that works for me even with me running android M.
Shows how to install TWRP for devices on 6.0
marcviado said:
This thread should be closed as theres already a proper one on here..http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Its more of people really dont like to search and read things
Click to expand...
Click to collapse
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
joeyicecream said:
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
Click to expand...
Click to collapse
Uhm..like i said nobody likes to read now a days lol. If you look closely the guide i linked shows you how to unlock bootloader,flash twrp,root,downgrade,and have all the files you need.
marcviado said:
Uhm..like i said nobody likes to read now a days lol. If you look closely the guide i linked shows you how to unlock bootloader,flash twrp,root,downgrade,and have all the files you need.
Click to expand...
Click to collapse
It is totally there... I looked at that guide for a really long time too. I concede.
joeyicecream said:
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
Click to expand...
Click to collapse
Yes it does. You do not need to use any codes, just enable oem unlocking in dev settings and type fastboot oem unlock and it will be unlocked.
Can't get twrp installed
Thanks for the step by step directions. I'm having trouble restarting my H811 after I've flashed TWRP. My device doesn't respond to the button method of entering recovery and 'fastboot boot twrp-2.8.7.0-h811.img' command doesn't do anything. My device is 20i and I've unlocked the bootloader. Any ideas? Seems like I've tried everything and can't get TWRP to install. Any help would be great...thanks
I have the G4 LGUS991 gotta can I tell if it's h811?
4. Using the android issue SDK. Open a command window and link it to your SDK folder where ADB is located (typically Platform-Tools)
Click to expand...
Click to collapse
What if your device could not be found despite having the latest LG drivers?
mr_blonde55 said:
Thanks for the step by step directions. I'm having trouble restarting my H811 after I've flashed TWRP. My device doesn't respond to the button method of entering recovery and 'fastboot boot twrp-2.8.7.0-h811.img' command doesn't do anything. My device is 20i and I've unlocked the bootloader. Any ideas? Seems like I've tried everything and can't get TWRP to install. Any help would be great...thanks
Click to expand...
Click to collapse
Can't remember which thread, but I ran into the same problem you have and solved it by using an additional command like fastboot erase userdata. If you google it, you'll see the commands I mean. Basically, I had to factory reset the device through fastboot first (it sits there for several minutes to do this) before installing/booting twrp. And yes, the log will show that the process was successful, not a failure as mentioned by OP. Once I did that, I booted in twrp and flashed the rom zip without any trouble.
So, you guys mean we have Marshmallow on T mobile G4, I didn't get it yet.
Please somebody give me a link to the OTA or update.zip for MM of LG G4
This one worked for me!
This is the only guide that worked for me.
I unlocked bootloader using adb, no problems...
I tried to flash TWPR with fastboot but kept getting errors. Booting into recovery got a dead android minion and red triangle with ! I ran this stupid recovery a dozen times and read a dozen threads with no obvious answers.
This guide says "ignore the error" and run fastboot boot twrp-2.8.7.1-h811.img which immediately opened TWRP and allowed SuperSU-2.71.zip to be flashed.
The part most guides are missing is the fastboot boot twrp-2.8.7.1-h811.img, so my thanks go here. Some other guides are so difficult to read and follow.
Thanks OP !
Yes, MM Android 6.0 went OTA for T-Mobile a month or so ago...
If you are already on Marshmallow, can't you do the 'fastboot oem unluck' with ADB and install SuperSU through the play store to get root? The part for TWRP would only give you the ablity to flash other roms.
Edit: Nevemind I'm wrong. You need TWRP to install SuperSU which roots the phone. SuperSU in the Play Store will only grant root acess to your apps.
Sent from my LG-H811 using XDA-Developers mobile app
NardVa said:
If you are already on Marshmallow, can't you do the 'fastboot oem unluck' with ADB and install SuperSU through the play store to get root? The part for TWRP would only give you the ablity to flash other roms.
Edit: Nevemind I'm wrong. You need TWRP to install SuperSU which roots the phone. SuperSU in the Play Store will only grant root acess to your apps.
Click to expand...
Click to collapse
Could you help me with is or point me in the right direction ? Please & thanks
Sent from my LG-H811 using XDA Labs
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
Majestyk007 said:
This is the only guide that worked for me.
I unlocked bootloader using adb, no problems...
I tried to flash TWPR with fastboot but kept getting errors. Booting into recovery got a dead android minion and red triangle with ! I ran this stupid recovery a dozen times and read a dozen threads with no obvious answers.
This guide says "ignore the error" and run fastboot boot twrp-2.8.7.1-h811.img which immediately opened TWRP and allowed SuperSU-2.71.zip to be flashed.
The part most guides are missing is the fastboot boot twrp-2.8.7.1-h811.img, so my thanks go here. Some other guides are so difficult to read and follow.
Thanks OP !
Yes, MM Android 6.0 went OTA for T-Mobile a month or so ago...
Click to expand...
Click to collapse
I keep getting this problem.
Sent from my LG-H811 using XDA Labs
I've just got a H811 and it automatically updated to Android 6 when I loaded it up. I will be giving this guide a go this evening. Many of the other links on the web are for lollipop and were released when the phone came out, so I'm thankful that this seems straight forward. http://uslugi.nie-spamuj.eu/rtv,1,0.html Hoping that it goes that way.
How to lock bootloader or hide status: bootloader state: unlocked?
Sr for my English!
So I followed this guide and I appear to be soft bricked at best and hard bricked at worst. I did read the other guide linked in the second response and I found a major difference that might be my problem. So in the guide linked in the second response it doesn't say to even try flashing TWRP from fastboot. It says to just boot from it then install it from within TWRP. I followed the steps verbatim and my phone is currently stuck at the T-Mobile splash screen. Any suggestions? I have tried to boot into recovery by holding down and the power and releasing the power for a second when the logo comes up. I get into the Factory data reset screen and select Yes twice then the green guy shows up and the phone resets but stays at the T-Mobile splash screen. I don't have ADB or fastboot with the phone in this state.
hi Guys,
So i just wanted to make sure and present my ask -
So, currently twrp flashing and obtaining root is still buggy for those who have android 6.0 preinstalled? Is this a correct assumption?
Also, my ask - I dont want root but i would like a custom recovery so that I may flash custom fonts. My work email (Good for Enterprise) is very much needed (although i hate it to the core).
Can someone please answer me / correct if I mentioned something wrong?
Thanks
rmdeathwish said:
hi Guys,
So i just wanted to make sure and present my ask -
So, currently twrp flashing and obtaining root is still buggy for those who have android 6.0 preinstalled? Is this a correct assumption?
Also, my ask - I dont want root but i would like a custom recovery so that I may flash custom fonts. My work email (Good for Enterprise) is very much needed (although i hate it to the core).
Can someone please answer me / correct if I mentioned something wrong?
Thanks
Click to expand...
Click to collapse
It's not buggy at all. All the tedium has already been bypassed if you already have Marshmallow installed.
Follow autoprime's original guide, steps 2, 4, 5, 6, and 8 under the Bootloader OEM Unlock + Root section. I would recommend a more up-to-date version of TWRP than 2.8.7.1 though. Go to TWRP's download site for the latest version.
Hey guys, I am new to this gear live dev and I want to help out. I just got my gear a few days ago and I'm still playing with it I figured that my device is at 5.0.1 and has Dev-Key in the build number. I went ahead and did some research (more than 35 hours) and came to a conclusion. I figured I can help a lot of people by posting my method here. I am currently on 5.0.2 and I am trying to figure out why I still did not get the 5.1.1 update. Looks like Samsung is slow and I will ask around if anyone got the OTA or I'll sideload the OTA scripts. Making the long story short.
Entering the bootloader (hard way)
Press and hold down the power button until your device reboots. Don't let go yet. As soon as you see the Samsung logo you have to swipe from the top left corner to bottom right corner really fast 2 times. Now let go of the power button and you should be in bootloader. If not keep trying again. I would recommend this as the last resort.
Entering bootloader (easy way):
Enable USB debugging by going to settings -> about device -> tapping build number 7 times. A new option should now show up under settings called developer options. At this point make sure that you have proper adb fastboot drivers. If not you can use the minimal ADB FASTBOOT 15 second Installer I will provide a link to the thread. Make sure that the watch is paired with your phone and keep the phone near you. Connect the watch to your machine via USB and let it recognize the device. Open a terminal or cmd window and enter adb devices. You will most likely be returned with some number and unauthorized. At this step if you get an error such like ADB is not an executable program then you have not installed ADB correctly. Switching over to your phone you will now see a debugging request from your watch. Go ahead and it always allow. Now you have granted debug permissions on you watch. Run the command again and this time, the device should return authorized. Run " adb reboot bootloader ". You will be taken to the bootloader.
Unlocking Bootloader and Flashing and relocking the bootloader:
The first step is to unlock the bootloader (don't know if this voids the warranty but I think it will). After you unlock the bootloader (fastboot oem unlock) WARNING: THIS WILL WIPE YOUR DEVICE and then boot back to the OS set it up and redo the steps under Entering bootloader. Once you have entered the bootloader you will need the stock os which is KMV78Y_stock. It is 4.4w and we will upgrade it soon. Open a cmd and run fastboot devices and you should see your device in the list. If not something is wrong , check if you have the right fastboot drivers and your watch is connected properly. Try a different usb port and don't use a usb HUB. ON WINDOWS extract the zip and navigate to the folder till you see the image files. Here shift+right click and you should see an option for open command windows here. For rest of the other people without windows cd to where the image files exist. Run the command “fastboot flash system system.img ” and “ fastboot flash boot boot.img ” . Once you have done that you will have to relock the bootloader. Relocking the bootloader is an important step to receiving further updates so I recommend relocking it. IF YOU DON'T RELOCK THE BOOTLOADER THEN YOU ARE STUCK ON 4.4W WHICH SUCKS SOOOO MUCH!!!!. Relock the bootloader by running “ fastboot oem lock “. Just keep in mind that you can re-unlock your bootloader after you have upgraded but unlocking bootloader will wipe your device again. *SIGH* I ALSO HATE READING LONG INSTRUCTIONS BUT YOU ARE ALMOST AT THE END!!!. After you relock your bootloader go ahead and swipe down on the screen until you highlight the recovery option and swipe right to select. Once you have booted into recovery you will see a warning sign. Don't Panic. Just tap on the screen and you will be brought to the recovery screen once again select reset and select yes.After the reset go ahead and reboot the device. You will be brought into the android wear stock os. Go ahead and set up your device again and go to the setting ->about device -> software updates. You will see that the update is available. There you go install the updates until you get to android 5.0.2. GREAT YOU HAVE UPGRADED YOUR WATCH. There a few ways to get to 5.1.1 but I have not tried them out. I will post the instructions as soon as I have tried it. If your watch says that there is an update the go ahead and install it. Samsung does not push the update to all users at once as it may kill their servers but roll the update out in batches. If you want to sit tight and wait till it comes through or I will be posting a how to soon.
UPDATING TO 5.1.1 AND TO 6.0
Hey, figured out how we can upgrade without waiting. It is actually really simple and easy. You will need to have a locked bootloader to do this or apply any stock update. It does not work with an unlocked bootloader. Your computer will not recognize your watch when sideloading if you have an unlocked bootloader. So let's get started. Download the ota update zip from the links below leave it in the downloads or move it wherever you want it. Open a terminal window or cmd window to the location of the zip either by shift+rightclick (only windows) or by cd’ing you way. At the location of the zip prepare your watch for sideloading. Reboot to recovery by commanding “ adb reboot recovery” or “ adb reboot bootloader” then going to recovery, or going to fastboot the hard way then to recovery. The choice is yours. Once you are in recovery select adb sideload. Now go back to your computer and hit " adb devices ". You should see your device and sideload. If not then something is wrong. Since you are already in the folder where the zip exists simply enter “adb sideload LIVE.zip” and it should send the file to devise. Don't panic if you interrupt the transfer. It will not apply the changes until the entire file has been transferred. Just redo the steps above to resend it. After the update is complete you can restart your device. Upon restart, you will see that your device has upgraded to 5.1.1. Congratulations. Now to go to 6.0 just go to software update and search for another update. I am starting to love this watch at what it can do in 6.0 so I suggest you upgrade.
Thank you, all and I hope this helped a lot of people out there.
Links:
Stock OS:
Android 5.1.1 OTA:
ADB AND FASTBOOT:
I will post inks as soon as I upload them.
-Soma
I need to root my G4 on TMO. It's on 6.0 and all I have done is enabled dev options - usb debugging- enable OEM in the menu. I've rooted devices before but it's been awhile. I obviously need to start from the beginning here, I assume by unlocking bootloader. I can't find any thread to start with as they are either outdated or for a different version of Android, or I just couldn't find one. I would really appreciate it if somebody could just link me to the thread/guide I need to be in! Thank you so much if you can!
MTN927 said:
I need to root my G4 on TMO. It's on 6.0 and all I have done is enabled dev options - usb debugging- enable OEM in the menu. I've rooted devices before but it's been awhile. I obviously need to start from the beginning here, I assume by unlocking bootloader. I can't find any thread to start with as they are either outdated or for a different version of Android, or I just couldn't find one. I would really appreciate it if somebody could just link me to the thread/guide I need to be in! Thank you so much if you can!
Click to expand...
Click to collapse
note it can only be unlock in this versions.. ill place them from oldest to newest 20i-(20p-20q-20r-20v) if you in any of the versions in parenthesis doent downgrade tp 20i... 20i is antirollback V2 all other in parenthsis is V3 you can switch bak and forth from 20p-to 20v.
well you have developers option enabled and OEM unlock
minimal adb. fastboot install it follow instructions. https://forum.xda-developers.com/showthread.php?t=2317790
download TWRP from here h811 and h815 same app for both. https://twrp.me/devices/lgg4.html
have 2 copies on in SD card other in minmal adb fastboot folder.
Bootloader OEM Unlock + Root:
Starting with the Android 6.0 20x bootloader it has to be unlocked, sorta like a Nexus, with fastboot. Previously only 'OEM Unlock' had to be toggled in Android Developer settings for TWRP or custom boot images to work.
download superSU
connect usb cable to phone.. then go to location folder of minimal adb.. ezample Crogramfiles/minimal.
then in the folder in a empty space press shift key.. and right click on mouse button . you should see open command prompt from here.. select it.
a new window should appear. enter this command
adb reboot bootloader and see screen for confirmation to acsess phone select yes.
if it doesnt boot into bootloader try command again
once booted youll see small letter on phone screen then enter command
fastboot oem unlock (this wipes ALL data!!)
it should restart phone. and optimize all apps...and bootloader should unlock
do same for twrp.... make sure command name of twrp is the same in the file example command is like this..
fastboot boot twrp-2.8.7.1-h811.img and file TWRP is say.. twrp.30.00 it wont work rename either command or files or both and name it twrp.img same in command. once it boot into twrp .. go to install then press button that says image. so the twrp.img you have in sd card appears/ select it then on next window tick recovery. swipe left to install permanently and you are done. flash new rom or superSU.
hope i make sense good luck
raptorddd said:
note it can only be unlock in this versions.. ill place them from oldest to newest 20i-(20p-20q-20r-20v) if you in any of the versions in parenthesis doent downgrade tp 20i... 20i is antirollback V2 all other in parenthsis is V3 you can switch bak and forth from 20p-to 20v.
well you have developers option enabled and OEM unlock
minimal adb. fastboot install it follow instructions. https://forum.xda-developers.com/showthread.php?t=2317790
download TWRP from here h811 and h815 same app for both. https://twrp.me/devices/lgg4.html
have 2 copies on in SD card other in minmal adb fastboot folder.
Bootloader OEM Unlock + Root:
Starting with the Android 6.0 20x bootloader it has to be unlocked, sorta like a Nexus, with fastboot. Previously only 'OEM Unlock' had to be toggled in Android Developer settings for TWRP or custom boot images to work.
download superSU
connect usb cable to phone.. then go to location folder of minimal adb.. ezample Crogramfiles/minimal.
then in the folder in a empty space press shift key.. and right click on mouse button . you should see open command prompt from here.. select it.
a new window should appear. enter this command
adb reboot bootloader and see screen for confirmation to acsess phone select yes.
if it doesnt boot into bootloader try command again
once booted youll see small letter on phone screen then enter command
fastboot oem unlock (this wipes ALL data!!)
it should restart phone. and optimize all apps...and bootloader should unlock
do same for twrp.... make sure command name of twrp is the same in the file example command is like this..
fastboot boot twrp-2.8.7.1-h811.img and file TWRP is say.. twrp.30.00 it wont work rename either command or files or both and name it twrp.img same in command. once it boot into twrp .. go to install then press button that says image. so the twrp.img you have in sd card appears/ select it then on next window tick recovery. swipe left to install permanently and you are done. flash new rom or superSU.
hope i make sense good luck
Click to expand...
Click to collapse
I'm on 20v, so I should be good.
MTN927 said:
I'm on 20v, so I should be good.
Click to expand...
Click to collapse
yes . thats latest version.. thats good.
OK, I got twrp installed but the two SU's I've flashed don't work. I have SU installed, it needs to update binaires, I try that but it fails every time. Root checkers say I'm not rooted. I think I'm using the wrong SU zip. Any help? Your guide was great btw.
EDIT: OK, now it says i am rooted but I can't get the SU binary to update. It fails every time and then asks me to reboot and try again. Any ideas?
UPDATE: Ok, the SU binary finally updated successfully! I think I'm all good! Gonna check out some custom ROMS later. Any recommendations?
Lineage
https://forum.xda-developers.com/g4/development/rom-cyanogenmod-13-0-lg-g4-t3477475
My mi A2 is currently running on the September update, the bootloader is locked, it's fresh and clean.
From the Mi A1 Gcam experience, I'm not having that much satisfying results on the default A2 stock camera. On my A1 I used that gcam toolkit for enabling Camera2Api. So the process was pretty clean and hassle free. OTA updates were nice and fine as well.
On my A2 the case is different. So far I haven't found any sort of things like that. Most of the processes include unlocking bootloader and root then magisk. And that'd be the last thing I'd ever try to do.
So is there anyway to get Google camera working on Mi A2 without losing OTA, BOOTLOADER UNLOCK AND ROOT?
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
I've found this link. But I'm not clear about the processes.
Anybody in the community with a kind heart will be generous enough to help me out? That'd be a big help. ?
Search and read read and read ... you need to have knowledge if you want to mess with this phone, and if you are afraid of flashing, then don't do it, if you are lazy, don't do it.
There is no way to enable camera2 without unlocking botloader, and then after enabling camera2, bootloader needs to stay unlocked.
Unlocking bootloader
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484
And then, there are two ways of enabling camera2, via twrp, and with magisk install and then uninstall.
Read and learn...
TWRP method
https://forum.xda-developers.com/mi-a2/how-to/tutorial-camera2api-gcam-root-t3842475
Magisk method
https://forum.xda-developers.com/mi-a2/help/how-to-install-ota-magisk-rooted-google-t3846324
Good luck.
minnuss said:
Search and read read and read ... you need to have knowledge if you want to mess with this phone, and if you are afraid of flashing, then don't do it, if you are lazy, don't do it.
There is no way to enable camera2 without unlocking botloader, and then after enabling camera2, bootloader needs to stay unlocked.
Unlocking bootloader
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484
And then, there are two ways of enabling camera2, via twrp, and with magisk install and then uninstall.
Read and learn...
TWRP method
https://forum.xda-developers.com/mi-a2/how-to/tutorial-camera2api-gcam-root-t3842475
Magisk method
https://forum.xda-developers.com/mi-a2/help/how-to-install-ota-magisk-rooted-google-t3846324
Good luck.
Click to expand...
Click to collapse
for me it's no problem To stay bootloader unlock but i don't want to root & don't want to lose ota successful installation.
Sohailsamdani said:
for me it's no problem To stay bootloader unlock but i don't want to root & don't want to lose ota successful installation.
Click to expand...
Click to collapse
Use this tool. I used today with September update, camera api enabled and the tool only use temporary root. You have to unlock the bootloader and leave unlocked.
Good luck
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585/page12
Daniesz said:
Use this tool. I used today with September update, camera api enabled and the tool only use temporary root. You have to unlock the bootloader and leave unlocked.
Good luck
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585/page12
Click to expand...
Click to collapse
I don't want to sound silly (sorry if i do) i am on the September update, unlocked bootloader and wanting to enable camera2 api, is it as simple as pressing the corresponding number that enables the unlock or do you have to do something before and after, regards
daveparki said:
I don't want to sound silly (sorry if i do) i am on the September update, unlocked bootloader and wanting to enable camera2 api, is it as simple as pressing the corresponding number that enables the unlock or do you have to do something before and after, regards
Click to expand...
Click to collapse
Sure, just choose the right option and choose the not rooted option
Daniesz said:
Sure, just choose the right option and choose the not rooted option
Click to expand...
Click to collapse
you mean 1st i select Option 1 lock/unlock bootloader then number 7 enable camera 2 api then number 10. exit then reboot my phone. Right?
Sohailsamdani said:
you mean 1st i select Option 1 lock/unlock bootloader then number 7 enable camera 2 api then number 10. exit then reboot my phone. Right?
Click to expand...
Click to collapse
Yes, if your bootloader still locked. Remember, if you unlock your bootloader, you will loose your data, so you have to wait to boot the phone and set it up. And than option 7.
Follow the instructions in the toolkit
If I unlock and relock the bootloader, do I lose my warranty? It's the single most deciding factor for me.
Daniesz said:
Use this tool. I used today with September update, camera api enabled and the tool only use temporary root. You have to unlock the bootloader and leave unlocked.
Good luck
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585/page12
Click to expand...
Click to collapse
Would you please share the processes you've gone through using this tool? ?
I follow the instruction and I installed the Gcam, put with Camera2 api app shows only Level_3, is that normal or I did something wrong.
ali7_has said:
I follow the instruction and I installed the Gcam, put with Camera2 api app shows only Level_3, is that normal or I did something wrong.
Click to expand...
Click to collapse
Lvl 3 is camera2 api enabled :good:
minnuss said:
Search and read read and read ... you need to have knowledge if you want to mess with this phone, and if you are afraid of flashing, then don't do it, if you are lazy, don't do it.
There is no way to enable camera2 without unlocking botloader, and then after enabling camera2, bootloader needs to stay unlocked.
Unlocking bootloader
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484
And then, there are two ways of enabling camera2, via twrp, and with magisk install and then uninstall.
Read and learn...
TWRP method
https://forum.xda-developers.com/mi-a2/how-to/tutorial-camera2api-gcam-root-t3842475
Magisk method
https://forum.xda-developers.com/mi-a2/help/how-to-install-ota-magisk-rooted-google-t3846324
Good luck.
Click to expand...
Click to collapse
I tried to go on with the twrp method using that toolkit. Unlocked my bootloader manually. The when I tried to use the toolkit to temporarily get access of twrp and run cmd from computer. When I enter the command adb shell, that showed my devices wasn't found. But when the phone is turned on then that shows my devices there. So I failed to figure out that. And on the other hand it want twrp as well. It was pitch black recovery something.
Secondly when I tried to go with the command 7 to enable camera2Api, it asked to temporarily root. I kept continued with Y. It came up with a note that allow USB debug with the phone will turn on again and make sure to keep phone connected. After that my phone never turned on again :") ♥. It was bricked and I wasn't even able to flash using miflash tool. So I had to go to the repair shop to get my phone fixed.
I wonder why the process is so ugly and annoying on A2 when it was the easiest thing on the A1.
Trust me? I had enough trouble. My wholes night's sleep was gone thinking that I've just got this phone 7 days ago! ?
afridishamsofficial said:
I tried to go on with the twrp method using that toolkit. Unlocked my bootloader manually. The when I tried to use the toolkit to temporarily get access of twrp and run cmd from computer. When I enter the command adb shell, that showed my devices wasn't found. But when the phone is turned on then that shows my devices there. So I failed to figure out that. And on the other hand it want twrp as well. It was pitch black recovery something.
Click to expand...
Click to collapse
With TWRP you have to enter the commands "setprop persist.camera.HAL3.enabled 1" and "setprop persist.camera.eis.enable 1" inside TWRP's terminal on your phone screen.
afridishamsofficial said:
Secondly when I tried to go with the command 7 to enable camera2Api, it asked to temporarily root. I kept continued with Y. It came up with a note that allow USB debug with the phone will turn on again and make sure to keep phone connected. After that my phone never turned on again :") . It was bricked and I wasn't even able to flash using miflash tool. So I had to go to the repair shop to get my phone fixed.
I wonder why the process is so ugly and annoying on A2 when it was the easiest thing on the A1.
Trust me? I had enough trouble. My wholes night's sleep was gone thinking that I've just got this phone 7 days ago!
Click to expand...
Click to collapse
To "unbootloop" your phone, you should enter "fastboot flashing unlock" and "fastboot unlock flashing_critical" (without quotes) in fastboot command line prompt and proceed with MIFLASH tool. Worked twice with me and I'm pretty sure can work for you.
But another advice: the process with Majisk (with the tool -> number 7) doesn't worked with me at all. I tried twice and had to MIFLASH before just bcz of Majisk. So, for a while, I recommend keep a distance from it.
kadu20es said:
With TWRP you have to enter the commands "setprop persist.camera.HAL3.enabled 1" and "setprop persist.camera.eis.enable 1" inside TWRP's terminal on your phone screen.
To "unbootloop" your phone, you should enter "fastboot flashing unlock" and "fastboot unlock flashing_critical" (without quotes) in fastboot command line prompt and proceed with MIFLASH tool. Worked twice with me and I'm pretty sure can work for you.
But another advice: the process with Majisk (with the tool -> number 7) doesn't worked with me at all. I tried twice and had to MIFLASH before just bcz of Majisk. So, for a while, I recommend keep a distance from it.
Click to expand...
Click to collapse
Please correct me if I'm going wrong.
1) unlock my bootloader.
2) put the phone in fastboot and connect to pc while USB debug enabled.
3) open the toolkit and proceed to twrp, only boot but not install method.
4) now I've to come to my phone. On the twrp I've seen an option called terminal. I've to click and enter there.
5) now I've to enter this command on my twrp terminal.
Setprop persist.camera.eis.enable 1
setprop persist.camera.HAL3.enabled 1
6) and then reboot to phone?
kadu20es said:
With TWRP you have to enter the commands "setprop persist.camera.HAL3.enabled 1" and "setprop persist.camera.eis.enable 1" inside TWRP's terminal on your phone screen.
To "unbootloop" your phone, you should enter "fastboot flashing unlock" and "fastboot unlock flashing_critical" (without quotes) in fastboot command line prompt and proceed with MIFLASH tool. Worked twice with me and I'm pretty sure can work for you.
But another advice: the process with Majisk (with the tool -> number 7) doesn't worked with me at all. I tried twice and had to MIFLASH before just bcz of Majisk. So, for a while, I recommend keep a distance from it.
Click to expand...
Click to collapse
i tried with the terminal method. and phone was not booting. It was on bootloop again. Now again stuck with the miflash thing! please help me!!!!
afridishamsofficial said:
Please correct me if I'm going wrong.
1) unlock my bootloader.
2) put the phone in fastboot and connect to pc while USB debug enabled.
3) open the toolkit and proceed to twrp, only boot but not install method.
4) now I've to come to my phone. On the twrp I've seen an option called terminal. I've to click and enter there.
5) now I've to enter this command on my twrp terminal.
Setprop persist.camera.eis.enable 1
setprop persist.camera.HAL3.enabled 1
6) and then reboot to phone?
Click to expand...
Click to collapse
Reboot and test if the camera settings that requires camera2api are working. If they are, I recommend to torn off and go to fastboot mode again and replace the modified boot (TWRP) to the stock one.
So, you setted partition b to TWRP, restore the original boot in place of it.
---------- Post added at 08:51 ---------- Previous post was at 08:11 ----------
afridishamsofficial said:
i tried with the terminal method. and phone was not booting. It was on bootloop again. Now again stuck with the miflash thing! please help me!!!!
Click to expand...
Click to collapse
There are (probably) some files missing with the tool. As you can see in the error message, the required bat to the process is missing. Download the complete tool with its .bat files and try again.