Hello, is it going to be possible for a custom recovery and maybe a CyanogenMod ROM for the new H1611 that came out on at&t? I see that root already came out for it.
UPDATE: As of now, we currently have a custom recovery and a systemless root available for the XT The img for the TWRP can be found from this post:
enigma2446 said:
Ok so to save time I decided to make a copy of the recovery using flashify app. But to be safe I recommend using fastboot to boot it first and make sure it works . Using the following command:
Fastboot boot xtrecovery.img
The img must be in the same folder you have adb and fastboot.
https://drive.google.com/file/d/0B12_sZzJAt2qeTdoR0tzYU9GQnM/view?usp=drivesdk
Click to expand...
Click to collapse
And here are some instructions on how to install the custom recovery and root the XT: (if you're following these instructions, be sure to rename the image file from Xtrecovery to TWRP)
divineBliss said:
I flashed TWRP, made TWRP backups, flashed SuperSU, and now I got root! Thanks guys!
My notes based on what enigma2446 posted.
I'm assuming you've done some of this before like using adb, fastboot, enabling USB debugging on phone, etc - but feel free to ask questions.
1. Must have unlocked bootloader (instructions early in this thread)
2. Must install adb and fastboot, and USB drivers (I prefer to add the adb/fastboot folder to my path so I don't have to work out of the adb/fastboot folder)
3. Backup all your files from internal storage. They are going to get blown away.
4. Put the SupserSU zip from https://download.chainfire.eu/1019/SuperSU/SR2-SuperSU-v2.79-SR2-20170103215521.zip on your microSD card and remember where you put it.
5. From windows command line with phone on and USB debugging enabled:
a) adb devices (to make sure you device is recognized)
b) adb shell reboot bootloader
6. Confirm phone goes to FASTBOOT & RESCUE mode.
a) fastboot devices (to make sure you device is recognized)
b) fastboot boot TWRP.img (boot the TWRP.img shared in earlier post)
c) Phone will boot into TWRP. Always select Keep Read Only from first screen every time you go into TWRP.
Peek around a bit if you want to, then use TWRP to backup your stock recovery to external micro SD.
d) Reboot bootloader from TWRP again to flash this custom recovery image.
e) fastboot flash recovery TWRP.img (flash TWRP recovery)
7. After phone reboots, get into TWRP recovery using previously described adb command or hold power button and volume up button from power off, then release when you see Huawei logo.
8. From TWRP:
a) Once again, always select Keep Read Only from first screen every time you go into TWRP!
b) Press Settings to adjust display brightness and vibrations settings, then press home button.
c) Wipe - Format Data (Warning: You are about to blow away your files on internal storage - which you should have backed up by now. Read the red text and confirm by typing yes and blue check mark button.
d) Home - Backup - Select all six partitions, then Select Storage - Micro SDCard (very important), OK, then Swipe to Backup. When the backup is finished, Home - Advanced, File Manager, /external_sd/TWRP/BACKUPS/........ and make sure your backup files exist for each of the six partitions.
e) Home - Install then Select Storage - Micro SDCard, find your SuperSU.zip, and flash it. Swipe to confirm Flash. Be patient, as it takes a few minutes.
f) After flashing SuperSU, Wipe Dalvik and Cache, then reboot. Be patient, as it takes a few minutes. My phone rebooted several times.
9. You should have root after your phone boots up and you set it back up!
10. Be sure to make another TWRP backup of System, Data, and Boot after you get root and phone is set up again!
If I have any typos, etc, sorry. Please post to help others.
Click to expand...
Click to collapse
Thank you everyone for the hard work! (enigma2446, divineBliss, xx_iamxanderman_xx, unque9, dolph8886, mi7chy, jarrettsuydam, ensol52)
Where did you find how to root this phone
well, SRS Root tweeted that they were able to on November 13.
#SRSRoot: HUAWEI H1611 (Build: H1611C07B130) #Android 6.0.1 Now Supported for #Root at http://www.SRSRoot.com
However, I cannot get it to work on mine. Keep getting this error message.
1:16:28 AM - Starting ADB Server..
1:16:33 AM - Manufacturer: HUAWEI
1:16:33 AM - Model: H1611
1:16:33 AM - Android Version: 6.0.1
1:16:33 AM - Build ID: H1611C07B140
1:16:33 AM - Board ID: H1611
1:16:33 AM - Chipset Platform: msm8916
1:16:33 AM - Getting OffSets.. : error: only position independent executables (PIE) are supported. (False)
1:16:34 AM - Query Server for Best Method.. Found Rootkit: 8
I'm running into the same problem.. :l
Trying other methods
I just unlocked the bootloader. I'ma try and see if that will help.
Sloogle_Flugelmann said:
I just unlocked the bootloader. I'ma try and see if that will help.
Click to expand...
Click to collapse
Mind sharing how you unlocked the bootloader?
http://rootmygalaxy.net/unlock-bootloader-on-huawei-devices/
this is how i unlocked the bootloader it on my phone
Sloogle_Flugelmann said:
I just unlocked the bootloader. I'ma try and see if that will help.
Click to expand...
Click to collapse
Did you try the srs root method after unlocking bootloader?
Sent from my H1611 using Tapatalk
I keep getting stuck on < waiting for device >
I keep getting a error because of the model number when trying to get a unlock code.
SRS says root is a success but I still don't have root.
---= SRS One-Click-Root v5.1 =---
5:37:10 PM - Starting ADB Server..
5:37:15 PM - Manufacturer: HUAWEI
5:37:15 PM - Model: H1611
5:37:16 PM - Android Version: 6.0.1
5:37:16 PM - Build ID: H1611C07B130
5:37:16 PM - Board ID: H1611
5:37:16 PM - Chipset Platform: msm8916
5:37:16 PM - Getting OffSets.. : error: only position independent executables (PIE) are supported. (False)
5:37:16 PM - Query Server for Best Method.. Found Rootkit: 8
----= Start Rooting Process.. Please Wait =----
5:37:17 PM [+] Testing exploit: root8 (please wait..)
5:37:18 PM [+] Remounting /system Filesystem as R/W..
5:37:18 PM [+] Installing SU Binary...
5:37:18 PM [+] Installing SuperUser APK...
5:37:19 PM [+] Remounting /system Filesystem as R/O..
5:37:25 PM [+] Rooting Complete !
---------- Post added at 05:39 PM ---------- Previous post was at 05:31 PM ----------
dabadguycr said:
I keep getting stuck on < waiting for device >
Click to expand...
Click to collapse
Is adb turned on.
kingmt01 said:
I keep getting a error because of the model number when trying to get a unlock code.
SRS says root is a success but I still don't have root.
---= SRS One-Click-Root v5.1 =---
5:37:10 PM - Starting ADB Server..
5:37:15 PM - Manufacturer: HUAWEI
5:37:15 PM - Model: H1611
5:37:16 PM - Android Version: 6.0.1
5:37:16 PM - Build ID: H1611C07B130
5:37:16 PM - Board ID: H1611
5:37:16 PM - Chipset Platform: msm8916
5:37:16 PM - Getting OffSets.. : error: only position independent executables (PIE) are supported. (False)
5:37:16 PM - Query Server for Best Method.. Found Rootkit: 8
----= Start Rooting Process.. Please Wait =----
5:37:17 PM [+] Testing exploit: root8 (please wait..)
5:37:18 PM [+] Remounting /system Filesystem as R/W..
5:37:18 PM [+] Installing SU Binary...
5:37:18 PM [+] Installing SuperUser APK...
5:37:19 PM [+] Remounting /system Filesystem as R/O..
5:37:25 PM [+] Rooting Complete !
---------- Post added at 05:39 PM ---------- Previous post was at 05:31 PM ----------
Is adb turned on.
Click to expand...
Click to collapse
Yes, im using adb and rebooting into bootloader then I enter the commented with the unlock code and push enter than I get < waiting on any device >. I tested trying to reboot and I get no device or emulator found.
I too am interested in cyanogenmod or really any custom rom on this device, we bought 2 for black friday and IMO emui blows.
KingRoot seems like it's making progress in rooting because first it flat out said this device is not supported.. now it gets to like 34%
Just thought I'd mention I'd be interested in a custom recovery / custom rom for this device as well, I've unlocked the bootloader and unlocked the device from at&t and currently have it working with an extra Ting Sim that I had on hand. I've also tried kingroot kingoroot srsroot and framaroot without getting root.
I am an odd user of android phones and tend to use them without service and just use hangouts as my primary means for taking/receiving phone calls as I almost always have wifi everywhere I go.
Just coudn't say no to a $50 6in 720p (hd) device with 2gb ram. Antutu rated it at just below a note 3. The device only showed up sometime in October, so I'm terribly surprised theres no root/roms yet.
Bootloader unlock key
Your unlocking password is：9214691743138114
This is the code to unlock the bootloader
trepanier01 said:
Your unlocking password is：9214691743138114
This is the code to unlock the bootloader
Click to expand...
Click to collapse
How would you know someone's unlock code?
Root not happening
First, your unlock code is unique to your phone and the process to get it works. Just make sure you fill in all data fields in the request.
Second, for those of you getting the "waiting on device" issue, you need to have the correct drivers. They will all download and install if you let the Huawei plug and play software install.
So here is what I know. The bootloader unlock procedure works. The SRSRoot process appears to successfully root but is not actually installing SU or writing SU binary so root is not happening. I have also tried KingRoot and Kingoroot. All were done after bootloader was unlocked. KingRoot gets to 90% before it fails. FASTBOOT and adb were used. If anyone has any ideas I am listening
I was able to get my device unlocked.
How Just How
dabadguycr said:
Yes, im using adb and rebooting into boot loader then I enter the commented with the unlock code and push enter than I get < waiting on any device >. I tested trying to reboot and I get no device or emulator found.
Click to expand...
Click to collapse
Ok so im a little dumb and i need a better way of explaining, i have been trying to unlock the same phone for a few days now and i still seem to be stuck or just dumbfounded,
1. i have my phone is fast boot mode and i have no idea how to turn it off
2. I keep on hearing to enter this command but i have no idea where to enter it at, do i enter it directly into my phone whe its in bootloader,
3. i have no idea how to enable bootloader or if im doing it right, i can probably answer this question if the first question is answered.
Hope we get a dev to pick up development of this phone, please!
In the meantime if anyone has a list of apps to stop/freeze for better performance listing them would be appreciated. There is a lot of bloatware on this phone that is not needed. Freezing the apps would speed up the phone and provide much better battery life.
Related
*******thread is dated, i do not own the device any more*********
Thank you Senior Member: starkly_raving for a break through with a working TWRP recovery and of course Team Win Recovery Project (TWRP) for there awesome recoveries! PLEASE READ, READ AGAIN AND WHEN YOU THINK YOU'VE GOT IT, READ AGAIN! And remember kiddies no one is responsible FOR WHAT YOU DO BUT YOU! Ill be trying to update this opening post as new info comes about, 2nd post will be dated info for reference.... starkly_raving has also mentioned that when a source built TWRP is complete development on this one will stop.
ROOT
Copied from post #22 Senior Member: starkly_raving
Disclaimer!!!
This is the method I used for the Metro PCS variant running 5.1.1 LMY47V. I can't verify this process for any other model or firmware use at your own risk.
All commands are without quotes.
First you have to unlock your bootloader and root...assuming you haven't here are the steps...
Requirements:
1. SDK installed with fastboot. (Minimal adb and fastboot will work also)
2. ADB/USB drivers
1. Enable developer options.
(a) Enable USB debugging
(b) Allow OEM unlock
2. Boot your device into bootloader mode.
(a) Open a cmd prompt in SDK or minadb fastboot.
(b) Connect device via usb
(c) In the cmd prompt type "fastboot devices" this will show if your device is connected.
(d) Then type "fastboot oem unlock" this will wipe all data including internal storage so backup to your PC or cloud.
(e) Once complete type "fastboot getvar" this will give you confirmation that your bootloader is unlocked.
(f) Finally enter "fastboot reboot" this will reboot you back to Android and you you will be greeted with the "bootloader unlocked" splash screen.
Rooting...
Requirements:
Reenable & Keep USB Debugging On!
Reenable & Keep OEM Unlock On!
Enable Unknown Sources!
Install the Kingroot apk from here...
http://www.kingroot.net/wap
Replace Kingroot with supersu:
http://www.w0lfdroid.com/2015/05/How...perSU.html?m=1
At this point you can update SuperSU binary if needed and install busybox.(always helpful)
Now for you (Boost users) to supply the needed files here's what to do.
1. We need the build.prop...
(a) Use a root explorer and copy system/build.prop to your SD card
(b) Via ADB "adb pull /system/build.prop"
2. We need your fstab and partition info... "cat proc/partitions" this will spit out your partition info.
3. We need your stock recovery.img and boot.img
(a) Use a GUI based app like flashify and backup your stock recovery and kernel.
(b) ADB method..
1.If you are using ADB, connect your device to your computer via USB, launch a command prompt window on your computer and enter the following command:adb shell
2. Enter the following command:"cat proc/mtd" You will get an output similar to this. Note that your result may differ from this one and you must proceed according to the output that you get, rather than the example that you see example here.
dev: size erasesize name mtd0: 000a0000 00020000 "misc" mtd1: 00480000 00020000 "recovery" mtd2: 00300000 00020000 "boot" mtd3: 0fa00000 00020000 "system" mtd4: 02800000 00020000 "cache" mtd5: 093a0000 00020000 "userdata"
To dump the recovery image to your SD card, make note of the first word of the line which says “recovery” in the end. It is ‘mtd1’ in case of this example but may be another entry for you.
3. Now use this command, replacing ‘mtd1’ with the term that applies in your case, if different: "dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img bs=4096" Similarly, to dump the boot image to your SD card, make note of the first word of the line which says “boot” in the end, which is ‘mtd2’ in our case but may differ for you. Use this command now, replacing ‘mtd2’ with the term that is applicable in your case, if different:"dd if=/dev/mtd/mtd2 of=/sdcard/boot.img bs=4096"
That’s it – you now have recovery.img and boot.img backed up on the root of your SD card.
RECOVERY
partial copy from post #42 Senior Member: starkly_raving
Prerequisites:
1. root
2. unlocked bootloader
3. knowledge of fastboot commands.
cmds
To test and not replace your recovery
fastboot boot twrp-image-new.img
If you feel its safe for daily use....
fastboot flash recovery twrp-image-new.img
DOWNLOADS:
Beta1:
https://drive.google.com/file/d/0B46...p=docslist_api
Alpha2:
https://drive.google.com/file/d/0B46...p=docslist_api
Alpha1:
https://drive.google.com/open?id=0B4...WNfMm9sQy1RVmM
dated info for reference only. Original opening post....
Seems there isnt any info out there for this device so im trying to get something started, ill up date as time passes and new info is released/found.
lg K7 aka lgms330
*rooted with king root
*replaced king root with super su using "wolfdroid" method successfully
*device boot loops with security error #9
*obtained another "virgin" k7 for dev purposes.... researching pull rom from working device and push to bricked device
*super su, stericson busy box, tibu among other apps installed successfully
*multiple boots later is when device started boot looping
*immediately after root a "rogue" tmobile app auto granted its self root access.... tibu - frozen
*recovery inaccessible & twrp not yet available, "download mode" is available but drivers install for every thing except MTS device will not install
*adb, fastboot and drivers installed from http://forum.xda-developers.com/show...php?p=48915118
*lg drivers and lg bridge installed before above tool
*dev options: debug=on, oem unlock=on, unknown sources=on,
*current platform for development=win7x64
ill clean this up a bit later, currently just notes i need not forget. please forgive if its posted in the wrong place.
if any one has any ideas about pulling a full system image and pushing it to the brick let me know, other wise ill continue researching. Seems there isnt any info out there for this device so im trying to get something started, ill up date as time passes and new info is released/found.
Please help
reemobeens19 said:
Seems there isnt any info out there for this device so im trying to get something started, ill up date as time passes and new info is released/found.
lg K7 aka lgms330
*rooted with king root
*replaced king root with super su using "wolfdroid" method successfully
*device boot loops with security error #9
*obtained another "virgin" k7 for dev purposes.... researching pull rom from working device and push to bricked device
*super su, stericson busy box, tibu among other apps installed successfully
*multiple boots later is when device started boot looping
*immediately after root a "rogue" tmobile app auto granted its self root access.... tibu - frozen
*recovery inaccessible & twrp not yet available, "download mode" is available but drivers install for every thing except MTS device will not install
*adb, fastboot and drivers installed from http://forum.xda-developers.com/showthread.php?p=48915118
*lg drivers and lg bridge installed before above tool
*dev options: debug=on, oem unlock=on, unknown sources=on,
*current platform for development=win7x64
ill clean this up a bit later, currently just notes i need not forget. please forgive if its posted in the wrong place.
if any one has any ideas about pulling a full system image and pushing it to the brick let me know, other wise ill continue researching.
Click to expand...
Click to collapse
I rooted my lg k7 with kingroot thought i would try putting xposed on it manually with root browser yes i am a noob at this sorry so yes i replaced files in system\bin, system\lib, and the other places xposed requires now it is stuck on the metro pcs screen i tried the factory reset on the phone like 10 times its not working and my pc only is detecting my phone as LGE Android Net MTP or something like that can you please help I just got it last night :'(
BeLOWME1992 said:
I rooted my lg k7 with kingroot thought i would try putting xposed on it manually with root browser yes i am a noob at this sorry so yes i replaced files in system\bin, system\lib, and the other places xposed requires now it is stuck on the metro pcs screen i tried the factory reset on the phone like 10 times its not working and my pc only is detecting my phone as LGE Android Net MTP or something like that can you please help I just got it last night :'(
Click to expand...
Click to collapse
my advice is take it back, while its still under warranty. i wouldnt tell them you rooted it though. as of right now im having driver issues and cannot help.
do you get a security error indicating modification? can you get into recovery? if so try a wipe
Lg k7 metro pcs
Lg k7 metro pcs cant find a custom recovery yet has anyone found one if so please let me know I can't do anything cool on my phone without one
Rooting the device voids warranty i believe.. and theirs no support for this phone at all...
Frustrated.
I rooted mine with KingRoot, then installed Link2SD and moved all of my downloaded apps to the second partition of my external SD. Shortly afterward, all of my applications began crashing, even system ones like Phone, Settings, Contacts, etc. Like an idiot, I performed a factory reset on my device. After the reset, it wanted the original Gmail account that was linked prior to the reset, but LG Keyboard crashes and I can't proceed. Thought maybe I could sideload Google Keyboard but of course USB debugging was disabled after the reset. Luckily, I took it back to the MetroPCS store I purchased it from and was able to get them to order me a replacement. I still have the "bricked" device in my possession, and hopefully I won't have to exchange it to get the new one.
Now that I've explained my situation, is there anyone out there with the KDZ image for this model? I'm thinking that's my only hope to restore this poor thing. I know I've got another one coming, but it'd be nice to have a working backup phone just in case.
mine wont let me reset it need help
Guys I know this is off topic but could you share the stock wallpapers of the K7 please????
reemobeens19 said:
Seems there isnt any info out there for this device so im trying to get something started, ill up date as time passes and new info is released/found.
lg K7 aka lgms330
*rooted with king root
*replaced king root with super su using "wolfdroid" method successfully
*device boot loops with security error #9
*obtained another "virgin" k7 for dev purposes.... researching pull rom from working device and push to bricked device
*super su, stericson busy box, tibu among other apps installed successfully
*multiple boots later is when device started boot looping
*immediately after root a "rogue" tmobile app auto granted its self root access.... tibu - frozen
*recovery inaccessible & twrp not yet available, "download mode" is available but drivers install for every thing except MTS device will not install
*adb, fastboot and drivers installed from http://forum.xda-developers.com/showthread.php?p=48915118
*lg drivers and lg bridge installed before above tool
*dev options: debug=on, oem unlock=on, unknown sources=on,
*current platform for development=win7x64
ill clean this up a bit later, currently just notes i need not forget. please forgive if its posted in the wrong place.
if any one has any ideas about pulling a full system image and pushing it to the brick let me know, other wise ill continue researching.
Click to expand...
Click to collapse
Be sure to update when a custom recovery is available i just don't feel safe with my lg k7 rooted without a recovery. i mess things up quite often and custom recovery's CWM or TWRP have always got me out of sticky situations
ermond012 said:
Guys I know this is off topic but could you share the stock wallpapers of the K7 please?
Click to expand...
Click to collapse
All of them?
Atelear said:
All of them?
Click to expand...
Click to collapse
Yeah, if possible...?
I'm not sure how to upload the file where I put them
---------- Post added at 08:20 PM ---------- Previous post was at 08:13 PM ----------
ermond012 said:
Yeah, if possible...
Click to expand...
Click to collapse
There. These are all the wallpapers excluding the live wallpapers.
PM me for the link
Is the tribute 5 the same phone as the lg k7?
Migue9088 said:
Is the tribute 5 the same phone as the lg k7?
Click to expand...
Click to collapse
Yes they are the same. I think Boostmobile just named it something else
I can try to port a recovery to it if someone can point me to the right direction
I don't think there any custom recovery yet
Hey guys,
I've rooted and unlocked the bootloader on the Metro PCS variant. I have also got in contact with a developer and provided him with the fstab, stock recovery, boot.img and build.prop...what's this mean? We will have a custom recovery very soon. :thumbup:
---------- Post added at 08:20 AM ---------- Previous post was at 08:17 AM ----------
Also could someone who's rooted post the adapt folder/apk? I accidentally lost mine when I moved it to SD and when I unlocked the bootloader it wiped my storage. Thanks guys.
starkly_raving said:
Hey guys,
I've rooted and unlocked the bootloader on the Metro PCS variant. I have also got in contact with a developer and provided him with the fstab, stock recovery, boot.img and build.prop...what's this mean? We will have a custom recovery very soon. :thumbup:
---------- Post added at 08:20 AM ---------- Previous post was at 08:17 AM ----------
Also could someone who's rooted post the adapt folder/apk? I accidentally lost mine when I moved it to SD and when I unlocked the bootloader it wiped my storage. Thanks guys.
Click to expand...
Click to collapse
Can you tell the person if he could make one for the tribute 5 please
Migue9088 said:
Can you tell the person if he could make one for the tribute 5 please
Click to expand...
Click to collapse
Once we have the one for the K7 finished I'll submit the files for the Tribute 5 if some one can provide them.
I don't have anything against toolkits, I just prefer to use adb and fastboot so I have more control over of what's going on. I also think it's a good idea for folks to have a little idea about what they're doing, even if they aren't experts. Below are the steps I used to install TWRP (recovery) and SuperSU (root) for my X522 (aka S3, the US variant which uses the Snapdragon 652). I don't see any reason this wouldn't work for all other Snapdragon variants: X520 (Chinese), X526 (Indian), and X527 (International). That said, you do what you do at your own risk. If you have one of the other Snapdragon variants and this works for you, though, please respond to the thread and let me know!
This thread is intended to be noob-friendly! That means that there are no dumb questions...unless you ask a question that is directly answered in the first post or in the FAQs found in the second post. To that extent, please read and re-read and if you still can't find your answer, please feel free to post your question.
Many thanks to @Rishabh Rao and his team for getting us an official TWRP image.
WARNING: this will reset your phone entirely! Make sure you save anything you want from internal storage before proceeding any further!
WARNING: as of right now, unlocking / rooting your phone will break your ability to take official OTAs. We're not sure why. That said, you should be able to flash modified OTA zip files manually, after a certain block of the update script is removed (see second post for more information).
Unlocking and Rooting your Le 2
Download and install Minimal ADB and Fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Download latest official TWRP, place file in ADB installation folder, and rename to "twrp.img": https://twrp.me/devices/leecole2.html
Download SuperSU 2.78 (stable): https://download.chainfire.eu/1001/
Boot up phone and plug into computer
Settings > scroll to bottom to "About phone" > touch "Build" 7 times to enable developer options
Developer options > toggle "OEM unlocking" and "USB debugging" so that they're both enabled
When "Allow USB debugging?" window pops up on phone, check "Always allow..." box and hit OK
In Minimal ADB installation folder, hold Shift and right-click "Open command window here", then type:
Code:
adb reboot bootloader
Once in fastboot:
Code:
fastboot oem unlock-go
fastboot boot twrp.img
If password screen comes up, tap "Cancel" button
If it asks, tap "Keep Read Only" button (probably doesn't matter, but whatever)
Wipe > Format Data
Make backups (I suggest boot, recovery, and system since this will allow you to return everything to stock later on)
Mount > Enable MTP
Copy entire TWRP folder from internal storage to your computer
Copy SuperSU zip from your computer to root of internal storage
Reboot > Bootloader
Code:
fastboot oem unlock-go
fastboot flash recovery twrp.img
Hold Vol+ and Pwr until boots into TWRP
Swipe to Allow Modifications
Install > select SuperSU zip > swipe to flash
Wipe Cache/Dalvik
Reboot (first boot will take a little while, so be patient)
Enjoy your rooted phone!
Restoring to Stock(ish)
Follow steps 4-7 above
If your boot and recovery backups from TWRP aren't already on your phone, move them to the appropriate folder (internal storage/TWRP/BACKUPS/[yourphoneserialnumber])
In Minimal ADB installation folder, hold Shift and right-click "Open command window here", then type:
Code:
adb reboot recovery
Wipe > check Dalvik, Cache, Data
Restore > select your package, ensure boot and recovery are checked, then Swipe to Restore
Reboot > Recovery
In stock recovery: uncheck "Update system", check "Clear data", and tap "Start"
Reboot to bootloader (hold Vol- and Pwr until it comes up) and then:
Code:
fastboot oem unlock-go
fastboot boot twrp.img
Wipe > Format Data
Reboot > System
Your phone is now back to stock!
If you didn't back up your stock recovery, boot, or system, you can find the ones I pulled from my phone at the link below. They're from 19S. I don't know if that makes a difference (vs 18S) with boot and recovery or not, but obviously that's what you're getting with the system.
https://mega.nz/#F!bV0XUbhJ!k2ZfY5t9bxb8gRa3rKQbyA
FAQs
Fastboot and/or ADB doesn't see my phone!
If you've enabled OEM unlocking and USB debugging and fastboot devices returns <waiting for device> or adb devices doesn't show anything, the most likely culprit is that Windows is using updated ADB drivers and you need to roll back. You can do this via Device Manager > right-click Android Device (or Kedacom USB device) / Android Bootloader Interface > Update driver > Browse my computer for driver software > Let me pick... > Choose older version (probably something from 2014)
I haven't seen the "Allow USB debugging?" prompt. Where is it?
In some cases, you will need to run an ADB command first to make the prompt show up. If you toggled the appropriate developer options and didn't get the popup immediately, make sure your phone is plugged into your computer and type adb devices in the command prompt. You should get the popup box then.
Stock recovery is in Chinese and I can't read Chinese!
As I was testing the above procedures, this happened to me once or twice and I don't know why. Upon a full restore and boot back into recovery, it was in English again. It might have something to do with the data wipe in TWRP. Anyway, the options in stock recovery are the same in Chinese and English so do this:
Uncheck the first item and check the second
It will direct you to a screen with some red text and a blue button: tap the button
It will return you to the first page: ensure the second item is checked and tap the blue button
Uh, how do I re-lock the bootloader? Am I missing something?
As far as I can tell - and someone please correct me if I'm wrong - using this guide, your bootloader is only ever temporarily unlocked and will re-lock with a reboot. That's why you have to use fastboot oem unlock-go more than once. You can verify this by restarting the phone, rebooting into the bootloader, and using the code below to check the status:
Code:
fastboot oem device-info
If for some reason your phone shows that you still have an unlocked bootloader, you can re-lock it using:
Code:
fastboot oem lock-go
I'm stuck in a stock recovery bootloop. How do I get out of it?
This probably happened because you're just holding down the power button to reboot instead of using the "restart" button in stock recovery. If you use the "restart" button to in stock recovery, it should kick you out of the loop.
Thanks for this guide , can we expect some roms from your side.
Just curious to know if any developer is working for rom on le2
Great guide for beginners but can you tell that how can one lock the bootloader again and when we make a backup does it make the back up of TWRP recovery of stock recovery?
Great!! Informative thread for beginners!
Miketoulson said:
Just curious to know if any developer is working for rom on le2
Click to expand...
Click to collapse
Yes. @Rishabh Rao and his team (the same ones who did TWRP and the AIO toolkit) are working on CM. As a reminder, please do not ask for ETAs. They will post the ROM when it's available.
Swastik Raj Chauhan said:
Great guide for beginners but can you tell that how can one lock the bootloader again and when we make a backup does it make the back up of TWRP recovery of stock recovery?
Click to expand...
Click to collapse
1.) Regarding the bootloader: good question. I've updated the FAQ.
2.) Regarding recovery backup: that's why we only boot into TWRP the first time, rather than replacing recovery from the beginning. That way, stock boot and recovery are backed up. Later on, when we flash TWRP, stock recovery is replaced.
I'm having trouble with this guide. I have TWRP recover flashed, but it isn't working correctly. It says there is nothing in my sdcard directory and my computer won't connect to the phone in recovery. I've also tried "adb push ... /sdcard/" method. The SuperSU files gets put in the sdcard directory and I can flash it, but it says "unable to mount storage" and the file is gone after a reboot. Is this because it's encrypted and I'm just hitting cancel when it asks for a password?
abel408 said:
I'm having trouble with this guide. I have TWRP recover flashed, but it isn't working correctly. It says there is nothing in my sdcard directory and my computer won't connect to the phone in recovery. Is this because it's encrypted and I'm just hitting cancel when it asks for a password?
Click to expand...
Click to collapse
Sounds like you missed steps 12 and 14.
rczrider said:
Sounds like you missed steps 12 and 14.
Click to expand...
Click to collapse
Nope... I formatted data and enabled MTD. When I enable MTD, my computer tells my the phone is locked...
---------- Post added at 07:19 PM ---------- Previous post was at 07:14 PM ----------
My bootloader keeps locking itself...
(bootloader) Device product name: []
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
I can unlock it, but it locks itself after a reboot.
abel408 said:
Nope... I formatted data and enabled MTD. When I enable MTD, my computer tells my the phone is locked...
---------- Post added at 07:19 PM ---------- Previous post was at 07:14 PM ----------
My bootloader keeps locking itself...
(bootloader) Device product name: []
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
I can unlock it, but it locks itself after a reboot.
Click to expand...
Click to collapse
That's expected and is addressed in the FAQ
You're only ever temporarily unlocking it. You will need to unlock it every time you reboot the phone.
rczrider said:
That's expected and is addressed in the FAQ
You're only ever temporarily unlocking it. You will need to unlock it every time you reboot the phone.
Click to expand...
Click to collapse
oh wow... so there is no perm unlock with this phone yet? Does the Chinese version have perm unlock? We can flash the chinese bootloader for perm unlock if that's the case.
---------- Post added at 07:45 PM ---------- Previous post was at 07:27 PM ----------
And now I'm stuck... I cannot go back to stock because TWRP doesn't mount the storage.
---------- Post added at 08:01 PM ---------- Previous post was at 07:45 PM ----------
abel408 said:
oh wow... so there is no perm unlock with this phone yet? Does the Chinese version have perm unlock? We can flash the chinese bootloader for perm unlock if that's the case.
---------- Post added at 07:45 PM ---------- Previous post was at 07:27 PM ----------
And now I'm stuck... I cannot go back to stock because TWRP doesn't mount the storage.
Click to expand...
Click to collapse
I was able to fix this by wiping Internal Storage... You may need to add that to your guide. Thanks for the guide!
abel408 said:
oh wow... so there is no perm unlock with this phone yet? Does the Chinese version have perm unlock? We can flash the chinese bootloader for perm unlock if that's the case.
Click to expand...
Click to collapse
I can't get permanent root using the AIO Toolkit, but maybe it's just the 2 phones I've tried. I'd love to hear from other users (X522 or other variants) on whether or not their unlock actually sticks after a reboot.
abel408 said:
I was able to fix this by wiping Internal Storage... You may need to add that to your guide. Thanks for the guide!
Click to expand...
Click to collapse
If other folks run into the same issue, I'll add it. I followed my own steps on a second phone (one that had never been unlocked/rooted before and was currently set up and in use) after your post and I didn't have any need to do anything different. I'm wondering if that need arose because you didn't unlock the bootloader a second time before booting into TWRP. If that's the case, the guide works as written, so I'll add it to the FAQ.
I seem to have done something wrong. I'm having a really difficult time accessing the Data partition in TWRP. Every time I reboot into recovery I cannot access the files on the sdcard (it is simply empty). I reboot and the files are still in storage (along with the TWRP backups I made) - I just can't seem to get to them in TWRP. I cannot mount Data because it doesn't appear. There is a box to decrypt data but that then requires a password (which I obviously don't know). Don't want to go any further if I can't seem to have a dependable way to access backups. Any suggestions?
Edit: Enable MTP also doesn't work for me in TWRP so there is no way to bring any files over from my PC while in TWRP - also adb push/pull doesn't seem to be working
skyman88882002 said:
I seem to have done something wrong. I'm having a really difficult time accessing the Data partition in TWRP. Every time I reboot into recovery I cannot access the files on the sdcard (it is simply empty). I reboot and the files are still in storage (along with the TWRP backups I made) - I just can't seem to get to them in TWRP. I cannot mount Data because it doesn't appear. There is a box to decrypt data but that then requires a password (which I obviously don't know). Don't want to go any further if I can't seem to have a dependable way to access backups. Any suggestions?
Edit: Enable MTP also doesn't work for me in TWRP so there is no way to bring any files over from my PC while in TWRP - also adb push/pull doesn't seem to be working
Click to expand...
Click to collapse
If TWRP is asking for a password, that means you missed step 12.
I'm trying to upgrade from 18s to 19s and I'm getting upgrade failed every time. I've tried restoring to factory defaults and restoring my TWRP backup. Seems to be fully on stock now and it still fails. My question is, do you think it would be alright if I restored your 19s TWRP backup so that I am on 19s?
abel408 said:
I'm trying to upgrade from 18s to 19s and I'm getting upgrade failed every time. I've tried restoring to factory defaults and restoring my TWRP backup. Seems to be fully on stock now and it still fails. My question is, do you think it would be alright if I restored your 19s TWRP backup so that I am on 19s?
Click to expand...
Click to collapse
Tell you what: give me an hour or two. I'm currently on non-stock (ie. rooted) 18S and since the Xposed module EUI Moder (http://forum.xda-developers.com/xposed/modules/mod-leeco-eui-moder-t3416932) doesn't work (lockscreen flicker / system UI crash), I don't mind wiping the phone and testing the ability to go back to stock and do an OTA update to 19S. If it doesn't work for me, I'll restore 19S (from my other S3) via TWRP and see if that does it.
@abel408
My first try was to just grab the OTA file (which I did) and do a local update, but no dice. In case anyone cares, I've uploaded the OTA zip file (IFXNAOP5801910272S).
So I went ahead and used both 19S TWRP backups (one for boot/recovery and one for system only) downloadable from Mega via the link in the OP and it worked just fine. Those files were generated from a different phone and worked fine on this one, so you should be good to go.
rczrider said:
@abel408
My first try was to just grab the OTA file (which I did) and do a local update, but no dice. In case anyone cares, I've uploaded the OTA zip file (IFXNAOP5801910272S).
So I went ahead and used both 19S TWRP backups (one for boot/recovery and one for system only) downloadable from Mega via the link in the OP and it worked just fine. Those files were generated from a different phone and worked fine on this one, so you should be good to go.
Click to expand...
Click to collapse
Thanks buddy!
Thank you sir, this worked (almost) perfectly. For some reason on my laptop, I wasn't able to get the phone to connect with debugging (never got the prompt for permission, etc.). No clue why not, I've got drivers and everything, and that laptop works with many other phones. Oh well. Went to a different PC and it worked perfectly.
rczrider said:
@abel408
My first try was to just grab the OTA file (which I did) and do a local update, but no dice. In case anyone cares, I've uploaded the OTA zip file (IFXNAOP5801910272S).
So I went ahead and used both 19S TWRP backups (one for boot/recovery and one for system only) downloadable from Mega via the link in the OP and it worked just fine. Those files were generated from a different phone and worked fine on this one, so you should be good to go.
Click to expand...
Click to collapse
I think I'm doing something wrong @rczrider, but I can't get TWRP to even recognize the backup you uploaded. Do I just drag the extracted files to the TWRP folder?
This guide is supposed to help you root your lg k8 (2016) or k10 (2016) device (i guess any models with and unlockable bootloader and working TWRP).
Not for the 2017 models!
Why "friendly" root? Go see my old guide how unfriendly the method used to be:
https://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807
Guys with latest (2017 febr. 1) security patch read this before you proceed:
https://forum.xda-developers.com/showpost.php?p=71469157&postcount=183
https://forum.xda-developers.com/showpost.php?p=72414225&postcount=250
Short version:
1. unlock bootloader (read step 2.1 if there is no device corrupt message during every boot up after unlocking bootloader!!!)
2. boot into TWRP (i tested with 3.0.0 twrp and above, never tested below)
3.1 install rce_univ.zip (download from this thread: https://forum.xda-developers.com/apps/supersu/ramdisk-compression-exchanger-t3533327, but follow instructions here!)
3.2 install supersu
3.3 install rce_univ.zip again
reboot
Long version:
The links written with italic fonts are video guides (please excuse me for the quality they were made by my mobile phone)
1. unlock bootloader
- in settings/about phone/software info tap on build number about 10 times so you unlcok developer options
- in settings/developer options tick on "oem unlock" and "usb debugging" and untick "verify apps over usb"
- in settings/security tick on "unknown sources" and untick "verify apps"
video guide for above steps: Link Removed by Moderator
- make sure you installed all the drivers for your mobile from lg's site (LGMobileDriver_WHQL_Ver_4.1.1.exe and also lg bridge) - Link Removed by Moderator
- set up adb/fasboot using 15 seconds adb installer: https://forum.xda-developers.com/showthread.php?t=2588979 - Link Removed by Moderator
- go to the folder it's installed (in my case it's C:/adb - adb.exe and fastboot.exe supposed to be there) hold shift and right click "open cmd here" - Link Removed by Moderator
- in the command window type "adb devices"
it will start adb services and will print a line like "...lgk350... or ...lgk420... lgk430, etc"
if you can't find your device there check device manager or google how to work things out
normally in device manager you should find "LGE Mobile USB Serial Port" under Ports - Link Removed by Moderator
- now reboot to fastboot mode typing the command: "adb reboot bootloader"
your phone should go blank and only print fastboot mode on the bottom of the screen
- check your fastboot connection: type: "fastboot devices"
same as before (in my case it was writing some unrecognizable letters - probably wrong coding) if you see nothing then check device manager -Link Removed by Moderator
you may try to install android SDK (command line tool is enough - https://developer.android.com/studio/index.html - bottom of the page Link Removed by Moderator) if the connection is not working - however there must be a way to make it work (i had a hard time in device manager - i changed each driver a million times until it worked)
in device manager you should find "android bootloader interface" in my case its under "samsung android phone" i don't know why but it works
- In case you have a working adb and fastboot connection type (if you lost connection you have to get to fastboot again: "adb reboot bootloader"):
"fastboot oem unlock" - the phone will ask you if you really mean it, using the volume and the on/off buttons (twice) you can accept
you will lose all your data!!! and most likely lose warranty as well!!! Link Removed by Moderator
however your phone shell restart just fine (you have to manually restart it by taking out the battery or boot into twrp and reboot from there. There should be some message during boot up that your system is vulnerable from now on.
- after reboot you may want to check if your bootloader is really unlocked: get back to fastboot and type "fastboot getvar all" and find the line which sais if your bootloader is unlocked (if it's not you may repeat the process)Link Removed by Moderator
set up developer settings again:
- in settings/about phone/software info tap on build number about 10 times so you unlcok developer options
- in settings/developer options tick on "oem unlock" and "usb debugging" and untick "verify apps over usb"
- in settings/security tick on "unknown sources" and untick "verify apps"
Link Removed by Moderator
- !!!if there is no device corrupt message during every boot up then you need an additional step i'll describe at step 2.1!!! - Link Removed by Moderator
2. find a working TWRP for your device (i collect them in the first comment below - https://forum.xda-developers.com/showpost.php?p=70375626&postcount=2):
- put the recovery image (e.g "k8twrp.img") into your ADB folder (like c:\adb - where you opened command promt earlier)
- Get back to fastboot again and boot to TWRP - type in cmd: "fastboot boot k8twrp.img" (or whatever your TWRP image's filename is)
- if its not booting into TWRP normally try another TWRP (comment #2)
- on the first screen of the TWRP it's asking for password to decrypt data - just hit cancel
- if you have the device corrupt message during every boot up you can skip the next step (go straight to step 3.)
2.1. in case you have no device corrupt message during every boot up follow the next steps
- on the keep system read only? screen of the TWRP let it allow modifications (swipe!)
- reboot to System
- Link Removed by Moderator
you must see the device corrupt message during boot up -> you are ready to go for a root
- try to reboot the device if the device corrupt message is still there during boot up (Link Removed by Moderator). If it's not there you may repeat the process or check my old guide for troubleshooting.
3. the rooting part -Link Removed by Moderator[/I]
(you can read my old guide why we need to tweak the boot image before installing SuperSU - if you are interested)
- download the ramdisk compression exchanger: https://forum.xda-developers.com/apps/supersu/ramdisk-compression-exchanger-t3533327 (we need this because SuperSU can only work with gzip compressed ramdisks while we have lz4 compressed ones)
- download latest SuperSU TWRP flashable version: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
- put this (rce_univ.zip) and latest SuperSU (i used v2.79) on your sd card (you need external sd because the internal sd is encrypted in TWRP)
- reboot your device into TWRP (through adb and fastboot as before)
- cancel decrypt data
- don't swipe on system modifying screen just click on "keep read only"
- go to backup, backup your boot image (tick only boot partition /untick the rest/ and select storage as micro sd card) in case anything goes wrong during the rest of the process you can always restore it
- go to install
- select storage and chose micro sd card
- install rce_univ.zip (it will recompress your ramdisk to gzip - so SuperSU can tweak it)
- when it's finished don't wipe or don't reboot! Go back (hit back button button) and install SuperSUxxx.zip
- go back again (without restart or wipe) and install rce.zip again (this will recompress your ramdisk to lz4)
- now you can reboot to system (without any wipe) - it will bootloop a few times, be patient!
If something goes wrong check my old guide for deeper understanding and troubleshooting!
If you have any problem with installing rce_univ.zip please post comments to it's thread:
https://forum.xda-developers.com/apps/supersu/ramdisk-compression-exchanger-t3533327
Comments in this thread shell be only TWRP related or deeply device specific.
No promises... and no responsibility i take... !!!
Supported TWRPs:
in case you want to go for sure or you can't find a working TWRP port it yourself easily using my guide: https://forum.xda-developers.com/lg-k10/development/mtk-portable-twrp-porter-t3536123
or use the ones already ported:
Lg k10 k430: https://forum.xda-developers.com/lg-k10/development/teamwinrecoveryproject-3-0-0-0-lg-k10-t3404434
Lg k10 k430dsy (firmware: 10k - 2017 feb security date): Link Removed by Moderator
(Lg k10 k420n/ds: https://forum.xda-developers.com/lg-k10/development/unofficial-twrp-3-1-0-k420-ds-n-t3571943 - different root method required)
Lg K8: https://forum.xda-developers.com/lg-k10/development/recovery-twrp-3-0-2-lg-k8-k350-mtk-t3517894
others take a look around here: https://forum.xda-developers.com/lg-k10/development
or use this guide: http://www.chinaphonearena.com/foru...752-MT6753-MT6795-MT6797-TWRP-MT67xx-tutorial
Looks cleverly. May take a try
Could it be this SuperSU?
https://download.chainfire.eu/696/supersu/
a_lewicki said:
Could it be this SuperSU?
https://download.chainfire.eu/696/supersu/
Click to expand...
Click to collapse
Well... why would you use that old one? This might not even be systemless root so it would not work. Why dont you check the link i posted in the OP so you could find this one i recommend to use: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
after flashing rce.zip i got an error " unpacking boot image failed! aborting..."
what should i do to fix that? i've tried reading throught your old guide but i'm a noob and i couldn't find anything i could understand.
help anybody???
pedrodgr said:
after flashing rce.zip i got an error " unpacking boot image failed! aborting..."
what should i do to fix that? i've tried reading throught your old guide but i'm a noob and i couldn't find anything i could understand.
help anybody???
Click to expand...
Click to collapse
Next time you try, please make a recovery log (In recovery advanced menu) and send it to me or upload it here!
Which model? Which TWRP?
Also upload or send me your boot image that you backed up!
I added one more line to the script to see where its found the boot partition so please download again before you proceed for a better troubleshooting experience!
@gottlasz after everey install reboot system? (rce.zip then reboot supersu and reboot and rce.zip again and reboot?) or without rebooting?
a_lewicki said:
@gottlasz after everey install reboot system? (rce.zip then reboot supersu and reboot and rce.zip again and reboot?) or without rebooting?
Click to expand...
Click to collapse
No way! Do not reboot! Once you install rce.zip it changes the ramdisk compression so the phone can't boot up. Then the supersu tweaks the boot image (roots the phone) then you install rce.zip to change the ramdisk compression back to normal. Then you can reboot.
@gottlasz thank you so much IT WORKS
a_lewicki said:
@gottlasz thank you so much IT WORKS
---------- Post added at 01:44 PM ---------- Previous post was at 01:42 PM ----------
@gottlasz thank you so much IT WORKS
Click to expand...
Click to collapse
I know it works...
Do you mind me asking which phone you have (k8/k10), which model and which TWRP you used?
gottlasz said:
I know it works...
Do you mind me asking which phone you have (k8/k10), which model and which TWRP you used?
Click to expand...
Click to collapse
twrp 3.0.2
lg k10 k430dse
---------- Post added at 02:39 PM ---------- Previous post was at 02:24 PM ----------
[mention]gottlasz[/mention] do you know how to make snapchat working on root?
a_lewicki said:
twrp 3.0.2
lg k10 k430dse
---------- Post added at 02:39 PM ---------- Previous post was at 02:24 PM ----------
[mention]gottlasz[/mention] do you know how to make snapchat working on root?
Click to expand...
Click to collapse
okay, thanks for the info. I dont know anything about snapchat. If you just download it from playstore?
yes from playstore but i read this app won't work with root
a_lewicki said:
yes from playstore but i read this app won't work with root
Click to expand...
Click to collapse
I just downloaded and tested. Works without any issue...
gottlasz said:
I just downloaded and tested. Works without any issue...
Click to expand...
Click to collapse
Hmmm that's strange...
On my device I can't login to this app and i read this app won't work with root
a_lewicki said:
Hmmm that's strange...
On my device I can't login to this app and i read this app won't work with root
Click to expand...
Click to collapse
I don't know man... i don't think it's a root related issue. The app should promt if it had any problem with root.
However if you use any paid service through the app that can be an issue. Still.. the app has to write something about root if it has a problem with it.
gottlasz said:
Next time you try, please make a recovery log (In recovery advanced menu) and send it to me or upload it here!
Which model? Which TWRP?
Also upload or send me your boot image that you backed up!
I added one more line to the script to see where its found the boot partition so please download again before you proceed for a better troubleshooting experience!
Click to expand...
Click to collapse
Thanks for the fast reply, it's the k10 430dsf
i'll try downloading it again and give it a new try.
I was also using the twrp 3.0.0
i'm downloading the 3.0.2 now and i'll let you know if it works.
Thanks once again.
Happy new year for everyone:good:
i have the LG K8 (K350F) model.
Can i root my phone with this method???. Anyone with this model has probe this tutorial???.
thanks in advanced
raul2903 said:
i have the LG K8 (K350F) model.
Can i root my phone with this method???. Anyone with this model has probe this tutorial???.
thanks in advanced
Click to expand...
Click to collapse
If you have a working TWRP then its gonna work. Did you test any TWRPs already?
How to root your Huawei device on Nougat
Disclaimer:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this TUTO
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
Hi mates
For all those who, like me, have a lot of trouble to root their Mate 8.
I've successful to root my phone from the B560.
Last tuto (FINAL):
* Have the B560 firmware (or above - ask me for that) without no changes for Huawei Mate 8 with Nougat firmware - for the others devices, ASK ME!!!
* This Boot_Insecure_BXXX_Fix-adb_dm-verity-v2.img or v3- 5 versions for the moment: B560 - B580 - B581 - B582 - B585 - B588- B590- B592- B594- B595- B596. For another kernel, ASK ME!
* Have this TWRP 3.1.0-x - or this one (following the update)
* Have this SuperSU-v2.xx-EMUI5.0.zip on your external sdcard for supersu Chainfire - method 1
* Have the PHH superuser.zip on your external sdcard for PHH superuser - method 2
1 - Easy way to root with supersu Chainfire:
Install the TWRP via adb, or SRKtools or still TWRP if you already have it
Install the new_Insecure_BXXX_dm-verity-v2.img or v3 via adb
Reboot to the recovery
Install SuperSU-v2.xx-EMUI5.0.zip from TWRP
Reboot system
2 - Easy way to root with PHH superuser:
Install the TWRP via adb, or SRKtools or still TWRP if you already have it
Install the new_Insecure_BXXX_dm-verity-v2.img or v3 via adb
Reboot to the recovery
Install PHH superuser.zip from TWRP
Reboot system
Install PHH superuser app via PlayStore (if necessary, you had to make it with previous version)
Devices with which it works:
HUAWEI Mate 8
HUAWEI Honor Note 8
HUAWEI P9
HUAWEI Honor 8
HUAWEI MediaPad M3
HUAWEI P9 Plus
Misc:
It's certainly possible to root others Huawei models . For them, send me the stock boot.img of your current firmware in order that I make an insecure boot Fix-adb dm-verity for your device.
All apps requiring root works well with this method.
Following a problem with access to developer options, a update was made that now makes us to v3.
Credits:
ajsmsg78 - who explained me how to create the insecure boot
jac10000 - who helped me to create the insecure boot Fix-adb dm-verity
Chainfire for supersu
phhusson for PHH superuser
Donators:
Thanks to them
letschky
Frittenfresser
Tecalote
Version Information:
Status: Functionnal
Created: 2017-02-12
Last Updated: 2018-02-07
If you like that, hit the THANKS button below !
Report me if it works fine for you! I'll add you in the OP post.
Report me on which firmware you used my method.
Changes:
Code:
[B][I]Boot_Insecure_BXXX_Fix-adb_dm-verity-v2.img[/I][/B]
* fixes issue adb doesn't work
[B][I]Boot_Insecure_BXXX_Fix-adb_dm-verity.img[/I][/B]
* based on the [URL="https://forum.xda-developers.com/mate-8/orig-development/boot-decrypted-insecure-boot-img-adb-t3555257"]insecure boot[/URL]
* remove the boot checking of dm-verity for a better rooting
* authorize read/ write on the partitions
Thanks!
Install TWRP (SRKtools method)
TWRP TUTO:
Download this twrp.img
Rename it as twrpmate8mm.img
Goes to the SRKtools folder
Goes to the recovery folder
Goes to the mate8 folder
Goes to the emui41 folder
Open mate8.zip file with winrar or other extractor
Inside, you've 2 files,stockrecoverymate8mm.img and twrpmate8mm.img, delete twrpmate8mm.img file in the zip and confirm
Drag and drop your renamed file (twrpmate8mm.img) in the opened zip, confirm
Plug your phone
Authorize Debug mode in Settings\Developper options
Check if "Enable OEM unlock" is ticked
Authorize Debug mode in popup windows
Now, you launch SRKtools app
In the menu, choose 3 (Install recovery 6.0) and enter
Choose 2 (Huawei Mate 8) and enter
Choose 3 (Install Mate 8 TWRP for Marshmallow (EMUI 4.1) and enter
Type y and enter
Type f and enter
Wait the end of installation
The phone will reboot to this recovery and you will see that is good recovery
Install TWRP (ADB method)
TWRP TUTO:
Download this twrp.img
Rename it as twrp.img
Plug the phone with the debug mod activated
Check if "Enable OEM unlock" is ticked
Launch a command prompt from you ADB folder - like on the Flash_boot_img_tuto_02.jpg screenshot
Type: adb devices
Type: adb reboot bootloader
Put the twrp.img file in C: (you can put anywhere but you should know the path. So the better is to follow my instructions)
Type: fastboot flash recovery C:\twrp.img (Wait the end of installation, it's quick)
Brilliant work buddy! Keep it coming
Thank you!
Thank you for your hard work. I will try it immediately, downloading everything I need now.
Will report back when I have done it
---------- Post added at 07:08 PM ---------- Previous post was at 07:02 PM ----------
Question:
If I am already on official OTA B560, can I skip these steps?
16. Install update_data_full_hw_eu.zip - Don't reboot
17. Install update.zip - Don't reboot
Click to expand...
Click to collapse
@dexz 's method arranged by meto avoid to format data again
Only use if you are in the situation below... otherwise follow this method
Good news for those who are in my situation with my method. The @dexz 's method works fine but force again to format data... personnally I had more than tired to format data. So I made this....
You are with the semi rooted B560 or other perhaps
You have Chainfire supersu
You have decrypted your data
You have a Decrypted data boot and you wanted to keep it
Put my Decrypted data boot on the external SD
Phone is on... then unroot it fully with Chainfire supersu in its settings - it asks you to restore the boot.img, I pushed "NO" because I had a doubt if I still had it, in addition it will install again in this tuto
Reboot in TWRP (frd-twrp like @dexz 's tuto)
Install Decrypted data boot
Wipe Dalvik & cache - Strongly advised after to have flashed the boot, it doesn't eat some bread
Install superuser_noverify_nocrypt.zip
Reboot to system - It will take about 3-5mins or less, it's due to the wipe Dalvik & Cache
Go to playstore and Install phh's SuperUser app
And like me, you are fully rooted... Again thanks to @dexz for his method! The one above isn't more complicate and avoid to format again the data if you are in my situation.
franzyroy said:
Thanks!
You can try but I don't know the result. Try at least with update_data_full_hw_eu
Click to expand...
Click to collapse
Okay thanks for quick reply, will try with update_data only
---------- Post added at 07:19 PM ---------- Previous post was at 07:15 PM ----------
franzyroy said:
Thanks!
You can try but I don't know the result. Try at least with update_data_full_hw_eu
Click to expand...
Click to collapse
Another question, last one I promise.
You did not mention this in the thread, not that I saw at least.
Do I need to unlock my bootloader?
lovemajj said:
Okay thanks for quick reply, will try with update_data only
Click to expand...
Click to collapse
Perhaps it will work only with update data... I know someone has already rooted his phone like that (here).
lovemajj said:
Another question, last one I promise.
You did not mention this in the thread, not that I saw at least.
Do I need to unlock my bootloader?
Click to expand...
Click to collapse
Yes! I add it in the OP post!
franzyroy said:
Yes! I add it in the OP post!
Click to expand...
Click to collapse
Okay thank you!
lovemajj said:
Okay thank you!
Click to expand...
Click to collapse
Done
Short question is it possible that someone makes a twrp backup and i just reroll this on my phone?^^
How do I unlock the FRP lock?
EDIT: Nevermind, I figured out how to do it.
If anyone else needs an answer to this question here it is:
Before you unlock the bootloader, you MUST enable "OEM Unlocking".
If you do not do it before you unlock the bootloader, it will be greyed out and you will have to relock the bootloader and do it all over again.
---------- Post added at 09:26 PM ---------- Previous post was at 08:41 PM ----------
I have tried it now and it works!
Although I skipped one thing, which was step 3. I did not install the insecure boot because I know from the past that it screwed up my phone.
In short I did like this:
Enabled OEM Unlocking
Unlocked bootloader
Flashed TWRP (found in OP)
Factory reset
Format Data (here I rebooted to recovery)
Flashed the SuperSU zip (found in OP)
Flashed update_data_full_hw_eu.zip (also found in OP)
Then I flashed SuperSU again.
Reboot to system and done
Thank you for this post
lovemajj said:
How do I unlock the FRP lock?
EDIT: Nevermind, I figured out how to do it.
If anyone else needs an answer to this question here it is:
Before you unlock the bootloader, you MUST enable "OEM Unlocking".
If you do not do it before you unlock the bootloader, it will be greyed out and you will have to relock the bootloader and do it all over again.
---------- Post added at 09:26 PM ---------- Previous post was at 08:41 PM ----------
I have tried it now and it works!
Although I skipped one thing, which was step 3. I did not install the insecure boot because I know from the past that it screwed up my phone.
In short I did like this:
Enabled OEM Unlocking
Unlocked bootloader
Flashed TWRP (found in OP)
Factory reset
Format Data (here I rebooted to recovery)
Flashed the SuperSU zip (found in OP)
Flashed update_data_full_hw_eu.zip (also found in OP)
Then I flashed SuperSU again.
Reboot to system and done
Thank you for this post
Click to expand...
Click to collapse
So it works for you like that.
Thanks for your report, I will add you in the OP post.
Edit: Finally no, I will not add you, you don't match those who have a problem to root.
TWRP.img
franzyroy said:
Install TWRP (ADB method)
TWRP TUTO:
Download this frd-twrp.img
Rename it as twrp.img
Plug the phone with the debug mod activated
Launch a command prompt from you ADB folder - like on the Flash_boot_img_tuto_02.jpg screenshot
Type: adb devices
Type: adb reboot bootloader
Put the twrp.img file in C: (you can put anywhere but you should know the path. So the better is to follow my instructions)
Type: fastboot flash recovery C:\boot.img (Wait the end of installation, it's quick)
Click to expand...
Click to collapse
@franzyroy I do not understand the point 8. Why boot.img fastboot flash recovery? I for flashing the recovery I always used FASTBOOT command FLASH RECOVERY TWRP.img Thanks
apollo_81 said:
@franzyroy I do not understand the point 8. Why boot.img fastboot flash recovery? I for flashing the recovery I always used FASTBOOT command FLASH RECOVERY TWRP.img Thanks
Click to expand...
Click to collapse
It's a typo. Sorry!
@apollo_81
It was a typo, I corrected it.
This is:
Code:
fastboot flash recovery C:\twrp.img
@apollo_81
Can you remove your quote here #16 that others persons don't make the error.
lovemajj said:
Although I skipped one thing, which was step 3. I did not install the insecure boot because I know from the past that it screwed up my phone.
Click to expand...
Click to collapse
I did it and I haven't had any issue.
Hi guys,
I have started this thread so that you guys can root your moto M XT_1663_S356 andriod (7.0)
First of all i'm not responsible if your phone bricks burns or dies.
A big thanks to VVizard from lenovo RU forum with out him, it was not possible.
Thanks to Chainfire for the SuperSu.zip
To check Build number go to Settings -> About Phone-> Build number
Note -
1 - This only works for Moto M which is having build number XT1663_S356_170621_ROW. If you are on any other build number then please don't proceed.
2 - All the files are attached
3 - Install all the Motoral drivers and Minimal and adb folder.
4 - Following link contains all files needed to root the phone.
https://drive.google.com/file/d/0B3eDb0dWRU-uUjk4ZS1tdFpRR1U/view?usp=sharing
Rooting Moto M phone is divided into 3 Parts
1) Unlocking BootLoader
2) Flashing TWRP
3) Flashing SuperSu.zip
unlocking the bootloader
Note - This will wipe out all the data hence take a backup before unlocking boot loader
1 - First of all enable the Developer Option, To Enable the Developer Option, Go to your Settings -> About Phone-> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2 - Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3 - Download and Extract the Downloaded ADB fastboot Zip file on your PC
4 - Now connect your phone to Computer using USB Cable.
5 - When you connect your Phone to Computer, please wait until all the drivers get installed.
6 - In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
7 - Now type the command in your command window
adb devices
If you see a pop up to allow USB Debugging on your phone, Click OK
8 - Now type the command below to reboot your phone to bootloader
adb reboot bootloader
9 - Once your phone reboot into bootloader, then type the command below to make sure fastboot drivers are installed properly.
fastboot devices
10 - This command will list the connected devices. If your phone’s serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly.
11 - If your phone is listed then type in the following command in CMD.
fastboot oem unlock
12 - Check your phone you would have written"do you really want to unloock bootloader ? "(something like this). Just select yes using volume up and down button and press power button to confirm it .
13 - Congrats your bootloader is unlocked
Install TWRP
Note - You should have your bootloader unlocked before proceeding.
Copy the boot_XT1663_356.img and TWRP_Moto_M.img to Minimal adb folder
1 - First of all enable the Developer Option, To Enable the Developer Option, Go to your Settings -> About Phone-> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2 - Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3 - Download and Extract the Downloaded ADB fastboot Zip file on your PC
4 - Now connect your phone to Computer using USB Cable.
5 - When you connect your Phone to Computer, please wait until all the drivers get installed.
6 - In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
7 - Now type the command in your command window
adb devices
If you see a pop up to allow USB Debugging on your phone, Click OK
8 - Now type the command below to reboot your phone to bootloader
adb reboot bootloader
9 - Once your phone reboot into bootloader, then type the command below to make sure fastboot drivers are installed properly.
fastboot devices
10 - This command will list the connected devices. If your phone’s serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly.
11 - If your phone is listed then type in the following command in CMD.
fastboot flash boot boot_XT1663_356.img
12 - To flash the recovery, Type the command
fastboot flash recovery TWRP_Moto_M.img
13 - Congrats! you have successfully installed TWRP.
Rooting Phone.
Note -
You should have your bootloader unlocked.
You should have TWRP installed.
You should have supersu.zip copied in your phone.
1 - Switch off your phone. Now press volume down + power button till phone vibrates. Once it vibrates release the power button you should see android logo.
2 - Now with the help of volume up and down button select 'Recovery mode' and press power button.
3 - TWRP should start up.
4 - Select 'Allow Modification' and proceed.
5 - Select 'Install' and then select the 'SuperSu.zip' file and flash it.
6 -Restart the Phone.
7 - Congrats! your phone is rooted.
Note -
I have tried all this steps and have successfully rooted my phone i'm not responsible for any damage.
I have not build the boot_M_S365/ img file this is done by VVizard and really very thank full to him.
I am making a video on this!
Method Issues
Bro, I have faced a few problems since I have started
i) When I type in adb devices it shows my phone but unauthorized
so I have to allow it as you said but only after a reboot and doing the process again will it show authorized
ii) after entering adb reboot bootloader it doesnt show bootloader locked but straight up fastboot mode
iii) then when i enter fastboot oem unlock it shows asks me if I want to unlock, I press on volume up. Then it again asks me some other thing and I hold the volume up down and power together. Next I reboot into my phone. All data erased. I setup it again.
Now, does this mean my bootloader is unlocked? When I reboot it shows something on the middle right- unlocked..
So does this mean I continue and install twrp now? or what?
manandua01 said:
Thanks bro, I will give you credits ^_^
Click to expand...
Click to collapse
Cool!
manandua01 said:
Bro, I have faced a few problems since I have started
i) When I type in adb devices it shows my phone but unauthorized
so I have to allow it as you said but only after a reboot and doing the process again will it show authorized
ii) after entering adb reboot bootloader it doesnt show bootloader locked but straight up fastboot mode
iii) then when i enter fastboot oem unlock it shows asks me if I want to unlock, I press on volume up. Then it again asks me some other thing and I hold the volume up down and power together. Next I reboot into my phone. All data erased. I setup it again.
Now, does this mean my bootloader is unlocked? When I reboot it shows something on the middle right- unlocked..
So does this mean I continue and install twrp now? or what?
Click to expand...
Click to collapse
1 - It doen't matter if its authorized or not..
2 - yes! thats correct it directly takes you to fastboot mode it use to show bootloader locked for old Moto phones).I 'll make changes in the thread.
Yes! your bootloader is unlocked successfully..
if you see something like 'Your devices is unlocked and cant be trusted' on the left hand side during the moto logo.
TWRP Recovery
akash.mahadeshwar said:
1 - It doen't matter if its authorized or not..
2 - yes! thats correct it directly takes you to fastboot mode it use to show bootloader locked for old Moto phones).I 'll make changes in the thread.
Yes! your bootloader is unlocked successfully..
if you see something like 'Your devices is unlocked and cant be trusted' on the left hand side during the moto logo.
Click to expand...
Click to collapse
Thanks for your help Y_Y
Hey bro, I am not about to install the recovery.
Before this may I ask why we need to flash boot_XT1663_356.img ?
Also, isn't this command wrong? fastboot flash boot boot_XT1663_356.img
It should be fastboot flash boot boot_XT1663_356.img
Without the boot twice ryt?
Also, will the data be erased after installing TWRP recovery or not? If not, will it be erased after installing the SuperSU?
manandua01 said:
Thanks for your help Y_Y
Hey bro, I am not about to install the recovery.
Before this may I ask why we need to flash boot_XT1663_356.img ?
Also, isn't this command wrong? fastboot flash boot boot_XT1663_356.img
It should be fastboot flash boot boot_XT1663_356.img
Without the boot twice ryt?
Also, will the data be erased after installing TWRP recovery or not? If not, will it be erased after installing the SuperSU?
Click to expand...
Click to collapse
1 - It is the Image file which is specifically build for S356 (build number) hence it is necessary to flash it before flashing TWRP. If you don't flash boot image then you might face boot loop issues and hard brick your phone.
2 - The correct command is 'fastboot flash boot boot_XT1663_356.img' . the first boot is to recognize cmd that we are flashing a boot image and the second boot is the name of image file.
3 - Flashing TWRP and Super SU won't erase your data.
akash.mahadeshwar said:
1 - It is the Image file which is specifically build for S356 (build number) hence it is necessary to flash it before flashing TWRP. If you don't flash boot image then you might face boot loop issues and hard brick your phone.
2 - The correct command is 'fastboot flash boot boot_XT1663_356.img' . the first boot is to recognize cmd that we are flashing a boot image and the second boot is the name of image file.
3 - Flashing TWRP and Super SU won't erase your data.
Click to expand...
Click to collapse
I installed TWRP unlocked bootloader copied SuperSU- and was abt to root. With volume up and down I came to Factory Mode
It said Factory Mode
I pressed on power button- now it shows something in Japenese or Chinese what should I DO? I am scared as hell bro
ITS DOING SOME WEIRD STUFF NOW- GPS, SIM etc I have no clue .-.
UPDATE: Rebooting phone- Back to my home screen now. Heres what happened
(uploading video will post link here soon)
manandua01 said:
I installed TWRP unlocked bootloader copied SuperSU- and was abt to root. With volume up and down I came to Factory Mode
It said Factory Mode
I pressed on power button- now it shows something in Japenese or Chinese what should I DO? I am scared as hell bro
ITS DOING SOME WEIRD STUFF NOW- GPS, SIM etc I have no clue .-.
UPDATE: Rebooting phone- Back to my home screen now. Heres what happened
(uploading video will post link here soon)
Click to expand...
Click to collapse
As i have mentioned in my thread that you need to select recovery mode and not factory mode
Please select recovery mode and you should b able to see twrp
Note - to select recovery mode press volum up n down button till it shows 'recovery mode ' in the andrioid logo screen
akash.mahadeshwar said:
1 - It is the Image file which is specifically build for S356 (build number) hence it is necessary to flash it before flashing TWRP. If you don't flash boot image then you might face boot loop issues and hard brick your phone.
2 - The correct command is 'fastboot flash boot boot_XT1663_356.img' . the first boot is to recognize cmd that we are flashing a boot image and the second boot is the name of image file.
3 - Flashing TWRP and Super SU won't erase your data.
Click to expand...
Click to collapse
akash.mahadeshwar said:
As i have mentioned in my thread that you need to select recovery mode and not factory mode
Please select recovery mode and you should b able to see twrp
Note - to select recovery mode press volum up n down button till it shows 'recovery mode ' in the andrioid logo screen
Click to expand...
Click to collapse
Bro, I opened Recovery Mode, but now its asking for a password. It shows temp on the top. You from India, ryt? Could you give me your number? or maybe a skype id?
EDIT: Here's what was on my cmd after flashing the recovery http://prntscr.com/ft3t1l
manandua01 said:
Bro, I opened Recovery Mode, but now its asking for a password. It shows temp on the top. You from India, ryt? Could you give me your number? or maybe a skype id?
Click to expand...
Click to collapse
Go ahead ignore the password part.. it will only appear first time.. you should have a option to go ahead..
akash.mahadeshwar said:
As i have mentioned in my thread that you need to select recovery mode and not factory mode
Please select recovery mode and you should b able to see twrp
Note - to select recovery mode press volum up n down button till it shows 'recovery mode ' in the andrioid logo screen
Click to expand...
Click to collapse
Please reply asap
---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------
akash.mahadeshwar said:
Go ahead ignore the password part.. it will only appear first time.. you should have a option to go ahead..
Click to expand...
Click to collapse
Ok trying now
---------- Post added at 09:21 AM ---------- Previous post was at 08:57 AM ----------
akash.mahadeshwar said:
Go ahead ignore the password part.. it will only appear first time.. you should have a option to go ahead..
Click to expand...
Click to collapse
Yo bro, I can only view External (sd card) storage. Not internal storage! What to do now? As I have SuperSU in Internal Storage
---------- Post added at 09:29 AM ---------- Previous post was at 09:21 AM ----------
Ok, I have rooted the phone successfully. Had to copy the SuperSU file to SD Card though 6-6
manandua01 said:
Please reply asap
---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------
Ok trying now
---------- Post added at 09:21 AM ---------- Previous post was at 08:57 AM ----------
Yo bro, I can only view External (sd card) storage. Not internal storage! What to do now? As I have SuperSU in Internal Storage
---------- Post added at 09:29 AM ---------- Previous post was at 09:21 AM ----------
Ok, I have rooted the phone successfully. Had to copy the SuperSU file to SD Card though 6-6
Click to expand...
Click to collapse
Ext_sdcard folder is ur memory card folder and sdcard folder is the internal memory folder in twrp
BAM!
---------- Post added at 01:14 PM ---------- Previous post was at 01:12 PM ----------
I really thank you for this great effort
all things went good but I had a problem that I didn't find the SuperSU-v2.82-201705271822.zip although I am sure that I put it in the internal memory
please help
Hi there,
After I unlocked the bootloader, pushed the twrp recovery successfully, got stuck in the recovery mod each time I reboot the phone so can't boot the stock rom. Done wipe factory reset and format data and still nothing changed. Any ideas?
Thanks in advance OP
Edit: Just solved issue by flashing stock firmware
pdf5 said:
Hi there,
After I unlocked the bootloader, pushed the twrp recovery successfully, got stuck in the recovery mod each time I reboot the phone so can't boot the stock rom. Done wipe factory reset and format data and still nothing changed. Any ideas?
Thanks in advance OP
Edit: Just solved issue by flashing stock firmware
Click to expand...
Click to collapse
May I have the firmware file, just in case? Is it ok if firmware country code doesn't match? Do you get imei?
any idea? when image for new build will be released?
rajesh280392 said:
any idea? when image for new build will be released?
Click to expand...
Click to collapse
Well, yes ... The new boot.img for removing encryption. Especially for post-OTA updating to XT1663_S364_170803_ROW.
boot_XT1663_364.img
Does anyone know how to keep your Moto M rooted even after updating to the new security update of 7.0? Do we just flash the new .img file or what? Kinda newb here