This is just a mirror to my original thread on superSU
Make sure you have adb installed either via the sdk or adb minimal
Here is a guide for anyone running android wear 6.0.1 on rooting
(from PC)
1.Unlock the bootloader if not already unlocked
(Make sure to boot to system and set up device after unlocking bootloader otherwise broken kernel! )
Code:
adb reboot bootloader
fastboot oem unlock
2.flash THIS TWRP onto the watch MAKE SURE TO USE THIS ONE!(current official cannot mount squashfs system)
Code:
fastboot flash recovery recoveryname.img
3.Download special SuperSU here with busybox YDS included HERE and move it to watch with adb push to /sdcard while TWRP is booted and then install as normal zip
Code:
adb push nameofzip.zip /sdcard/
4.Boot watch to system (ignore TWRP message of no OS installed) Now your root apps from 5.1 should work perfect
REMEMBER squashfs is read only even with root so don't bother trying to modify system files like the build.prop
If you would like to change pixel density perform this command in either adb shell or a terminal emulator:
Code:
wm density <dpi>
Please leave thanks if it helped!
New Update!
updated to superSU 2.79
reverted to previous busybox due to incompatibility
Xmaster24 said:
Feel free to submit links to twrp for squashfs watch with model name, codename and original developer's name
Will add them to this post
I DID NOT CREATE ANY OF THESE BUILDS!
LG G Watch dory(courtesy of @rbox): http://www.mediafire.com/download/apwtscp0tn0y8qd/twrp-3.0.0-0-dory+squashfs.img
Click to expand...
Click to collapse
I read in your other thread that you have your own version of TWRP? The 3.0.0.0 version I got from twrp.me doesn't seem to flash your supersu zip properly. Or at least I don't have a busybox app installed on my watch after flashing the zip.
b1g.p0ppa said:
I read in your other thread that you have your own version of TWRP? The 3.0.0.0 version I got from twrp.me doesn't seem to flash your supersu zip properly. Or at least I don't have a busybox app installed on my watch after flashing the zip.
Click to expand...
Click to collapse
yes see step 2 download the one from post below ie. the one you quoted. The one from twrp.me is outdated and cannot mount the system as it is squashfs. the one in that post can
oh sorry! the way it was situated in your post made me think it was a signature, so I didn't even read it. Thanks!
b1g.p0ppa said:
oh sorry! the way it was situated in your post made me think it was a signature, so I didn't even read it. Thanks!
Click to expand...
Click to collapse
Yes thanks for pointing that out, I have made it more obvious now.
Non-relatedid you notice xda updated this evening? notifications are broken now have to check things manually
I followed the instructions to a T and when I went to reboot in TWRP I have no OS installed what the **** happend?
EDIT: I saved myself when because I used the rootjunky tool to restore 5.1.1 then flahsed twrp on that and then flashed the update 6.0.1 zip from another thread on here. Hopefully I can figure this out. I'm good with android phone... first time messing with android wear.
EDIT: Second time is the charm I guess. Thanks for nobody screaming at me and calling me a nub!
codyedmonson said:
I followed the instructions to a T and when I went to reboot in TWRP I have no OS installed what the **** happend?
EDIT: I saved myself when because I used the rootjunky tool to restore 5.1.1 then flahsed twrp on that and then flashed the update 6.0.1 zip from another thread on here. Hopefully I can figure this out. I'm good with android phone... first time messing with android wear.
EDIT: Second time is the charm I guess. Thanks for nobody screaming at me and calling me a nub!
Click to expand...
Click to collapse
Um probably should have told people but TWRP would say that but you should just ignore it cause your system is there
Xmaster24 said:
Um probably should have told people but TWRP would say that but you should just ignore it cause your system is there
Click to expand...
Click to collapse
Yeahhh I figured that out after a while. My knowledge with rooting android wear is very limited at the moment. I've read as much as I could in one night lol. After figuring everything out with twrp/rooting I know have root and everything is going smoothly. Thanks for the tut!
okay, i used ur tutorial... fastboot flashed the twrp and pushed the supersu via adb to the sd... installed the zip via twrp... on leaving twrp it says "no os installed"... when i try to reboot the system it always just boots straight into twrp
/edit
okay! please add to your tutorial that you have to reboot and pair your watch first, after unlocking the bootloader! thx
cYraXx said:
okay, i used ur tutorial... fastboot flashed the twrp and pushed the supersu via adb to the sd... installed the zip via twrp... on leaving twrp it says "no os installed"... when i try to reboot the system it always just boots straight into twrp
/edit
okay! please add to your tutorial that you have to reboot and pair your watch first, after unlocking the bootloader! thx
Click to expand...
Click to collapse
Thanks was not aware that was a requirement strange that that happens
his thread gets a tad confussing ..is there a clear guide on doing 6.0.1 ? please..
Eggman72 said:
his thread gets a tad confussing ..is there a clear guide on doing 6.0.1 ? please..
Click to expand...
Click to collapse
What's confusing you? It's almost the same as rooting a phone flash twrp install supersu zip
Posters saying this is missing etc...im unsure whether posted tools etc are all there...rooted plenty of phones etc..just never a smartwatch..dont want to end up with a nice paperweight (I know its always a risk) seems some people have had a couple of issues Os missing etc..
Eggman72 said:
Posters saying this is missing etc...im unsure whether posted tools etc are all there...rooted plenty of phones etc..just never a smartwatch..dont want to end up with a nice paperweight (I know its always a risk) seems some people have had a couple of issues Os missing etc..
Click to expand...
Click to collapse
OS missing is just fault of twrp not me besides it's meaningless error it simply cannot write to system so it assumes it those not exist. Everything you need is there apart from adb but just get adb minimal from XDA. With my method there is no risk of a paperweight it only touches recovery and kernel which both can be easily replaced. The only thing that can really kill a phone is a messed up bootloader update/mod. I have taken everything posters said into account and updated accordingly. Originally I just wrote what worked for me but now I updated it for universal use
Thanks for the reply & clarificartion.. you say 1.Unlock the bootloader if not already unlocked
(Make sure to set up device after unlocking bootloader otherwise no boot!) does that mean after unlock it will reboot into OS and you perform language setup & pairing ? or after its done the unlock it go's straight into os for setup ?
Eggman72 said:
Thanks for the reply & clarificartion.. you say 1.Unlock the bootloader if not already unlocked
(Make sure to set up device after unlocking bootloader otherwise no boot!) does that mean after unlock it will reboot into OS and you perform language setup & pairing ? or after its done the unlock it go's straight into os for setup ?
Click to expand...
Click to collapse
After unlocking go straight to OS and setup because rooting with an empty data partition breaks the kernel
Do you reboot or does just go straight in ?
Eggman72 said:
Do you reboot or does just go straight in ?
Click to expand...
Click to collapse
I'm not sure I think it does yes just try it if it thosen't its simple as clicking start on the watch bootloader screen
bootloader unlocked fine..twrp installed fine..pushed files install and i get this error..any clues guys ?busy box installs but no super user... help !!!
Related
Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Update: I've finally figured out how to get the TWRP recovery booted. Now working on trying to get my phone to boot up an OS of some sort. Very slowly but surely.
bullmurf said:
Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Click to expand...
Click to collapse
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Addicted2xda said:
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Click to expand...
Click to collapse
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
bullmurf said:
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
Click to expand...
Click to collapse
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Addicted2xda said:
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Click to expand...
Click to collapse
"use sideload to copy / install a custom ROM..." OK I don't know anything about this but it will point me in the right direction. I have the phone unlocked. The HBOOT version is 1.40.0000. I'll see if I can do what you suggested, thanks.
Update: Atempting an adb sideload using TWRP which seems to be the only option for me.
ADB Sideload
What is ADB sideload?
--------------------------------------------------------------------------------
ADB sideload is a new feature that was added to AOSP recovery in Jelly Bean. As of version 2.3, TWRP now supports ADB sideload mode. ADB sideload is a different ADB mode that you can use to push and install a zip using one command from your computer. Most likely ADB sideload won't be very useful for your average recovery user, but ADB sideload can be a huge time-saver for a ROM developer.
How do I use ADB sideload?
--------------------------------------------------------------------------------
1.Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher
2.Have newer ADB binaries installed on your computer. If it's been a while since you installed ADB on your computer, you may need to get the latest ADB binaries in platform-tools from the Android SDK. You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line.
3.Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
4.From the command line, type adb sideload /path/to/rom.zip
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Note that sideload mode is a separate ADB mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.
Click to expand...
Click to collapse
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
bullmurf said:
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
Click to expand...
Click to collapse
Update: after trying the same thing 100 times it decided to send "sideload". command line was adb sideload name.zip. Installing Viper ROM for HOX+ atm. I'll see if it fixes all of my problems. Thanks for all of the help to this point. I'll type up a guide of what went wrong with my root and how we managed to get it fixed.
Update: Phone is booting to HTC white screen and then shutting off. Now trying to figure that one one out.
Update" Phone is booting to HTC white screen now and staying there. In TWRP under reboot is says "no os installed, do you still wish to reboot". Still digging in the forums to figure this one out and how to fix it. I installed the Viper ROM fine but when it asked to reboot now it just rebooted to HTC white screen. Missing something here? The phone is S-ON, does that make a difference in using the TWRP?
Is there an RUU exe file I can run from my computer? I relocked the phone but the links you gave me are for installing the ap through google play. Not sure how you do that with a phone that wont boot past htc screen.
Update: I've found an RUU application from these boards that is supposed to work for HOX+ so i'm downloading it. It really is taking forever to find the information I need along the way from this board but it's here....somewhere...I think...Will keep plugging away but feel free to throw me a bone ever once in a while! =)
Update: The version that worked for others isn't the same version I have. Going to dig again for 1.19.502.1 version.
Update: Found the version in the last place I thought it would be...HTC website...Downloading it and just hoping its and application I can run on my computer.
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
I would suggest you to use hasoon's all in one toolkit
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
bullmurf said:
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
Click to expand...
Click to collapse
There is a great lockscreen called CLocker
Addicted2xda said:
There is a great lockscreen called CLocker
Click to expand...
Click to collapse
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
bullmurf said:
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
Click to expand...
Click to collapse
You will find it in the playstore itself
You need to set lockscreen to None
Addicted2xda said:
You will find it in the playstore itself
You need to set lockscreen to None
Click to expand...
Click to collapse
Thanks again man. I got it and the ring is gone \0/ Phone looks freakin amazing now with that lock screen and Elegancia rom. Glad you stopped by to help :good: Still learning my way around the forums and my rooted phone. It's great to not be stressed about bricking it ^^
suppils soars
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
mrmagoogt said:
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
Click to expand...
Click to collapse
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Addicted2xda said:
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Click to expand...
Click to collapse
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
mrmagoogt said:
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
Click to expand...
Click to collapse
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Addicted2xda said:
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Click to expand...
Click to collapse
Thanks, I used a script to charge my battery, relock bootloader and installed ruu file to get back to stock, rooted again using Hasoon2000's all in one kit...
Hello! I've upgraded to 5.1 and have lost my root. I have tried using kingo and towelroot but neither have worked. I have tried downgrading to 4.3 re-rooting and then upgrading to 5.1 only to lose root again. Any help as to fix this would be awesome and highly appreciated!
Use TWRP
Milkteabubbles said:
Hello! I've upgraded to 5.1 and have lost my root. I have tried using kingo and towelroot but neither have worked. I have tried downgrading to 4.3 re-rooting and then upgrading to 5.1 only to lose root again. Any help as to fix this would be awesome and highly appreciated!
Click to expand...
Click to collapse
You can flash twrp to root, then install superusersu. There's a zip file that's been posted in the forums recently by ArkAngel 06 that has everything you should need and a step by step guide to do it. Hope this helps
This question has been asked and answered. Do you guys read the other threads at all?
To get root and TWRP.
Credit to Foltz61.
1. Boot to bootloader.
2. Fastboot boot TWRP-L.img
3. Install supersu-2.49.zip (even though I didn't lose root)
4. Reboot back to system.
5. Reboot back to bootloader.
6. fastboot flash recovery TWRP-L.img.
7. fastboot reboot.
8. Boot to recovery and had TWRP
Thanks
Thank you both for your help! I saw this posted in the other threads but there's been a lot of activity since the release of 5.1 and it was all getting confusing
to get su 2.49 .zip do a Google search u will find it after twrp just flash su 2.49.zip and ur all set .
I tried n its working fine
Would be best at this time to not flash twrp. Instead fastboot boot twrp.img then install the beta.SuperSU v2.49.
Sent from my MT2L03 using XDA Free mobile app
Re-rooting your LOLLIPOP HAM2
Milkteabubbles said:
Hello! I've upgraded to 5.1 and have lost my root. I have tried using kingo and towelroot but neither have worked. I have tried downgrading to 4.3 re-rooting and then upgrading to 5.1 only to lose root again. Any help as to fix this would be awesome and highly appreciated!
Click to expand...
Click to collapse
If your Bootloader is still unlocked, skip to step 5
UNLOCKING YOUR BOOTLOADER
1) Request your 16 digit Bootloader Unlock Code from [email protected] (you'll need to give them your phone's IMEI and SERIAL numbers)
2) Download the HW-QmOneKeyTool to your PC from here: http://www.mediafire.com/download/um5sqbwp094r2x4/HW-QmOneKeyTool.rar
3) Connect your phone to your PC, open the HW-QmOneKeyTool and enter your 16 digit unlock code into the text box in the first tab of that tool, then click 'ROOT' {This button should actually read 'UNLOCK'}
4) Now that your phone's Bootloader is unlocked, flash TWRP as follows:
INSTALLING TWRP
4a) Download TWRP Recovery from the following site: http://forum.xda-developers.com/asc.../2014-09-22-teamwin-recovery-project-t2885144
4b) Rename TWRP_MT2-L03_RECOVERY.img to TWRP.img
4c) Move TWRP.img to hard drive C, folder: adb
4d) Connect you phone to your PC, open Command Prompt and type: cd C:\adb
4e) After the adb prompt, type: adb devices
4f) With your device serial showing in the Command Prompt, type: fastboot flash recovery c:\adb\TWRP.img
4g) The Command Prompt should now say "waiting for device"
4h) Unplug your phone and reboot into bootloader (power + volume down)
4i) Once in the bootloader make sure it says unlocked then plug your phone in.
4j) The command prompt should say done after 2 seconds and your phone will stay the same.
4k) Unplug your phone and reboot.
INSTALLING SUPERUSER
5) Download BETA-SuperSU-v2.49 to your root: http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
6) Boot into TWRP and Flash BETA-SuperSU-v2.49
7) download the TWRP App from Google Play, and let it install BusyBox, then run the SD fix if needed
7) Now you can grant Superuser status to Apps that need root
Is there a backup of the mt02 emui 3.1 boot loader before I go to the twrp?
omnithesis said:
5) Download BETA-SuperSU-v2.49 to your root: http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
6) Boot into TWRP and Flash BETA-SuperSU-v2.49
7) download the TWRP App from Google Play, and let it install BusyBox, then run the SD fix if needed
7) Now you can grant Superuser status to Apps that need root
Click to expand...
Click to collapse
Step 7 is required if you don't have an SD card issue?
For anyone that knows, if you root your device, will this cause issues getting OTA updates from Huawei? I registered my IMEI after converting to OEM and loading Lollipop so I would like to ensure I get these updates and can install without issue.
No one?
No
Moody66 said:
No
Click to expand...
Click to collapse
What sort of response is this on a community forum where people try to help each other? Or I thought people helped each other?
I don't get a couple of you members here on the Huawei forums.
Trying to figure out if root causes an issue with OTA updates I believe is a valid question. Thanks for nothing though Moody. You're awesome. :good:
What phone because only a few phones are rooted on lollipop and they have to have unlocked bootloaders.
Sent from my SM-N910V using XDA Free mobile app
TheIgster said:
What sort of response is this on a community forum where people try to help each other? Or I thought people helped each other?
I don't get a couple of you members here on the Huawei forums.
Trying to figure out if root causes an issue with OTA updates I believe is a valid question. Thanks for nothing though Moody. You're awesome. :good:
Click to expand...
Click to collapse
The question was did root affect OTA. The answer is NO. What more do you want.
Moody66 said:
The question was did root affect OTA. The answer is NO. What more do you want.
Click to expand...
Click to collapse
Well, your simple one worded response was misinterpreted. How about that...
And yes, it does effect OTA. I just received B20 and it clearly said to make sure your phone was NOT rooted before upgrading, so obviously it causes an issue with the OTA updates.
Root does not affect OTA. Only if you change system files. Stock recovery and stock system files will not. At worst you will loose root and have to reroot.
---------- Post added at 02:19 PM ---------- Previous post was at 02:14 PM ----------
does root affect OTA....type that into Google. Thousands of posts will tell you the same thing.
Was simply reporting what the update to B20 said. It stated ensure your device is NOT rooted before updating. Perhaps it is just them being careful and ensuring that bugs that may appear on a rooted device would be tougher to diagnose.
Personally I don't see a big need for root with no ROM's available for the HAM.
Because you can't make some changes without root. LCD etc.
Moody66 said:
Because you can't make some changes without root. LCD etc.
Click to expand...
Click to collapse
Yeah, that's true, but to date, I have been pretty happy with the HAM stock. The LP update made this phone a whole new phone. The UI is very nice for an older phone with older specs. Coming from and LG G3 (yes, some would think the HAM is a downgrade), I love the HAM over the G3. The colors are amazing, the screen size is awesome and the new UI for LP is way better than stock LG.
Have a look at a G4. Shame they are expensive
Worth it. But expensive.
Trying to root Nougat (Android 7)? Then read the comments at the bottom please...
I will first state I do NOT own a Moto G4, I own the G3 and the X Pure which are both 3rd Gen devices, but I was requested to write this tutorial by a few users here due to lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3/4, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread. Remember, I do not own this device although the methods used are the same as similar devices.
Prerequisites:
0) Be running Marshmallow (Android 6.x) stock ROM, at this time Nougat (Android 7.x) is not working via any method.
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: As of 7/18/2016, Amazon ad-subsidised Moto G 4th Gen devices cannot be bootloader unlocked, therefore they cannot be rooted. Sorry, Lollipop and newer Android security changes pretty much put an end to that.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP's Moto G 2016 page
3) You need a copy of the latest stable SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. SR1-SuperSU-v2.78-SR1-20160915123031.zip is the lastest version verified to work with this method.
Note: Do NOT use any 2.77 version, it was a beta intended specifically for the SG Note 7 and will not work, it does not harm but fails to root.
4) Reboot and start TWRP recovery, and PERFORM A COMPLETE BACKUP IN TWRP (Nandroid)!!!
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Notes on Nougat/Android 7... At this time this method of rooting does not work properly on the official Nougat ROM for this device, it causes WiFi issues and interface problems (settings crashes, etc) and with no complete factory image there is no work fix other than to restore your Nandroid backup to pre-root status. If you wish to play with this method and try it, your on your own, I will try to assist but as I stated earlier I do not own this device. To my knowledge as of this posting, there is no working root on stock Android 7 on this device.
I can confirm this worked on my formerly-amazon XT1625 16GB G4. You will get an error about not being able to mount /data, but it proceeds and works anyway.
This is exactly what was missing! I rooted as normal with the latest SuperSU expecting it to just work like on other phones/tablets, but yeah. Before specifying systemless, it hung on boot. After following your instructions it booted right up. Thanks!
Also if you setup adaptable storage with your SDcard, so it works like internal storage, TWRP can't find any files on the SDcard. You will need to revert to non-adaptable storage for TWRP to find the supersu ZIP file.
And make sure you're using the latest SuperSU-- I accidentally tried a very old version which did not work!
Scared Noobie
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Appreciate this. I miss the old days where it was all simple. Everything was flashable. Never had to flash back to something or re flash.
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
Very rare...all you need is read, read, read and follow the instructions. Good luck
Very nice and just what I needed. Worked perfectly on my Amazon Moto G4 with ads. I got no errors or messages but booted fine-got caught in a boot loop once as the SuperSU file explains after it installs. Boots in less then a minute first time.
Marty
acejavelin said:
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Tomsgt said:
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Click to expand...
Click to collapse
cheers mate
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
zipjay said:
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
Click to expand...
Click to collapse
Your welcome... Just give click thanks on the first post, but if you feel absolutely compelled to buy me dinner, there is the Donate button.
Sent from my MotoG3 using Tapatalk
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
mikeruss said:
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
Click to expand...
Click to collapse
Can't you just use MTP mode of TWRP to copy the latest SuperSU to internal storage then flash after creating the config file?
Sent from my MotoG3 using Tapatalk
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
mikeruss said:
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
Click to expand...
Click to collapse
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
acejavelin said:
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
Click to expand...
Click to collapse
32 bit
Sent from my Moto G (4) using Tapatalk
thanks, xposed works fine
Well, I was planning on joining all of you with your Moto G4's soon, or possibly the G4 Plus... but since the Amazon version can't be unlocked anymore I got cold feet, and today Best Buy was running a special on the Moto X Pure 32GB edition for $249 (My Best Buy Elite members only), I pulled the trigger on that one instead. No change in helping though, I didn't have the device to begin with so I will continue to assist with this thread as I can.
I'm trying to root a friend's Metro LG Aristo MS210 7.0, what method works for rooting this phone?
Msjoannalynn said:
I'm trying to root a friend's Metro LG Aristo MS210 7.0, what method works for rooting this phone?
Click to expand...
Click to collapse
https://androidforums.com/threads/recovery-twrp-v3-for-lg-aristo-metropc-t-mobile.1117942/
Messi got you covered.
Personally I would recommend against rooting right now. There isn't much to be done with the Aristo at this point in time except to make backups of your system. Most you'll end up doing is learning a few things about why mixing system based and systemless mods can lead to pretty unpredictable results.
ninjasinabag said:
There isn't much to be done with the Aristo at this point in time except to make backups of your system.
Click to expand...
Click to collapse
This is exactly what I've wanted to do - preferably by having direct rw access to the flash, like I did on my old phone. Unfortunately the only viable custom recovery procedure right now (messi2050's) involves wiping the userdata partition (unless you somehow happen to have an unlocked bootloader). To make matters worse the userdata partition is encrypted AFAIK. Surely the keys are stored on the phone somewhere but there wouldn't be a way to get them without some exploit, and I don't know if this phone is popular enough for someone to bother researching and publishing an exploit.
There was some progress here (github.com/Lekensteyn/lglaf) on reversing and exploiting LG's LAF protocol in their recovery OS, but it hasn't been updated for more than a year now. If anyone wants to play around with that code, be sure to read this issue (github.com/Lekensteyn/lglaf/issues/7) which has ongoing attempts at reversing LAF's current auth methods. I don't have the time right now to dive into this unfortunately.
messi2050 said:
https://androidforums.com/threads/recovery-twrp-v3-for-lg-aristo-metropc-t-mobile.1117942/
Click to expand...
Click to collapse
reboot into fastboot [ adb reboot bootloader ]
- fastboot oem unlock [ this is going to wipe your data ]
how do i do this any one got any video tutorial for all of this ?
@Messi help
1118niranjan said:
reboot into fastboot [ adb reboot bootloader ]
- fastboot oem unlock [ this is going to wipe your data ]
how do i do this any one got any video tutorial for all of this ?
@Messi help
Click to expand...
Click to collapse
You need to do some search yourself
messi2050 said:
You need to do some search yourself
Click to expand...
Click to collapse
i saw your post in android form they've said u are the best guy to help any link if u can ?
1118niranjan said:
i saw your post in android form they've said u are the best guy to help any link if u can ?
Click to expand...
Click to collapse
Power your phone off.
Hold VOL DOWN WHILE PLUGGING DEVICE INTO COMPUTER WITH USB - this will bring it to the fastboot screen. If you have all drivers installed then you can simply open a cmd window and type "fastboot oem unlock" - which should unlock the bootloader - if all drivers are installed. Then continue with the tutorial as usual.
Is root worth it
So, I have an LG ms210 (Lg Aristo) that I've own for a little over 3 months now, but i have been experiencing this issue since about 1 week into ownership. The phone seams to have a RAM leak or something similar as about every hour it slows down substantially, usually to the point of freezing, or crashing all together and restarting on its own, even if not being touched since I power it on. Ive been thinking about rooting it to debloat, but im not sure if it will help, or if i should just invest in a new handset. I have since factory reset it, deleting more high-resource apps, and leaving it bare-bones system apps and nothing else, but the problem still persists. The carrier i MetroPCS if thats a factor, but i dont see why it would be. Any thoughts?
Rooted mine! Thanks to the modified twrp. I couldn't get into it for alost a week, then had a system update that rebooted me right to it, still had the super su zip in sd card so i flashed it and the no verity zip THANKS OP!!??
captnbluebeard said:
Rooted mine! Thanks to the modified twrp. I couldn't get into it for alost a week, then had a system update that rebooted me right to it, still had the super su zip in sd card so i flashed it and the no verity zip THANKS OP!!
Click to expand...
Click to collapse
If you still have trouble reaching recovery after this, either download an advanced shutdown prompt from the market. (There's one literally called advanced reboot) or you can download a terminal emulator app and use the reboot recovery command with root.
su
reboot recovery
ninjasinabag said:
If you still have trouble reaching recovery after this, either download an advanced shutdown prompt from the market. (There's one literally called advanced reboot) or you can download a terminal emulator app and use the reboot recovery command with root.
su
reboot recovery
Click to expand...
Click to collapse
I did that already, im trying to get xposed up and running but my model #lvl3 doesnt match what is in the terminal in twrp. I still get a weird error ph4u
Most likely shows as the lg stylo 2 plus as I guess your using the lineage backup. So just use the model of the lg stylo 2 in terminal? Guessing as I don't use xposed. What do you use xposed for?
To get it running on the aristo is to either edit build prop values to match the ms210 model, or remove the device requirements from xposed's update binary.
failed remote cannot flash this partition in unlocked state.
Anyone?
can some walk me thru this idk what im doing wrong but i go into adb i reboot bootloader and when i try to fastboot oem unlock it says device not found what am i doing wrong?
question
does this root works for lg ms210 security patch level jan 1 2018?
I believe the root is just twrp so it should work fine. Just update first then follow the steps for flashing twrp and the most recent magisk and probably dm verity thing. If something fails it can be eaily reflashed with the original firmware with correct software and the firmware image/kdz.
Edit: try to reinstall the lg drivers? Also a try a tool called minimal adb and fastboot here
Help. It just staus on "" waiting for device " with oem unlock step
Before rooting your phone , it is necessary to backup data for your phone .
READ THE WHOLE THREAD BEFORE CONTINUING or FLASHING THE ZIP ! AS THIS ONLY WORKS DESCENT FOR G VERSION , I ONLY RECOMMEND TO DO SO ! USING IT ON A U-VERSION (B19/B25) MIGHT BRICK YOUR PHONE. ALSO TESTED & WORKING ON Project New World (Oreo) on G VERSION
I am not responsible for damaging/bricking your phone or other related stuff…DO MAKE A FULL BACKUP !
ONLY FOR A2017G & also on A2017G B32 Oreo PNW
DON'T USE ON B13 (MF5.0) BECAUSE IT DOES NOT WORK !!! Tested it myself.
Only to use whether flashed Universal B15 (or B32 on PNW) or Stock Bootloaders before.
Don't use on encrypted phones and remove security pattern before flash
Always backup your data. In case you have to format data you'll have a spare one to restore
EDIT : made a flashable zip : Remove Bootloader Unlock Warning on Axon 7G : https://androidfilehost.com/?fid=745849072291698596
As @Choose an username... asked to bring this to your attention again hereby a fairly easy and safe method to get rid of that annoying "unlocked bootloader" warning.
I did mentioned this before in the earlier days but perhaps its usefull to post it again. And if you're planning to stay a while on your rom this might help to have a clean boot.
I performed this steps often on my G and imo are safe to do.
So, take a look HERE
Prepare with necessary files (if you already haven't from before )
( Be on twrp 3.1.1.0 (3.2.1.0) )
Just perform steps 6 to 14 again (NOTE ! : If you get a permissions denied issue, try doing these steps while your device is in TWRP )
After that just type "fastboot reboot" and you should have a clean boot.
-------------------------------------------------
B) Unlock the bootloader
Q: Why do I need to unlock the bootloader?
A: With an unlocked bootloader, you can install custom ROMs.
1) Go to https://mega.nz/#F!rcFCQZ7C!vn457hU1zDwc0uVpvm5otw and download the aboot.img file from there (1024Kb). Put it in the same folder you used in the previous process
2) Download this file: https://www.androidfilehost.com/?fid=529152257862665656
3) Unzip the file and copy/cut the file called "fastboot_unlock.img"
4) Paste that file in the folder where "adb.exe", "axon7tool.exe", "recovery.img", "recovery.bin" and "aboot.img" are located
5) If there's none open, open a new command window in that folder again (Shift + right-click and "open command window here")
6) Type "adb push aboot.img /sdcard/" and hit enter
7) Type "adb push fastboot_unlock.img /sdcard/" and hit enter
8) Type "adb shell dd if=/dev/block/bootdevice/by-name/fbop of=/sdcard/fbop_lock.img" and hit enter
9) Type "adb shell dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot_lock.img" and hit enter
10) Type "adb pull /sdcard/fbop_lock.img" and hit enter
11) Type "adb pull /sdcard/aboot_lock.img" and hit enter
12) Type "adb shell dd if=/sdcard/fastboot_unlock.img of=/dev/block/bootdevice/by-name/fbop" and hit enter
13) Type "adb shell dd if=/sdcard/aboot.img of=/dev/block/bootdevice/by-name/aboot" and hit enter
14) Type "Adb reboot bootloader" and hit enter to go to the bootloader
-------------------------------------------------
Thanks @Controllerboy
Can we not create flashable ZIPs for this to save Time? Something with AROMA to choose the Specific Device Files would be cool or nah? Let Me know if there is interest on this. I could help with the Scripts...
BR
Miustone said:
Can we not create flashable ZIPs for this to save Time? Something with AROMA to choose the Specific Device Files would be cool or nah? Let Me know if there is interest on this. I could help with the Scripts...
BR
Click to expand...
Click to collapse
Thnx for your reply.
But AFAIK this procedure might not work on the U version but not sure ( afaik no go on A2017). So therefore i just used the "known" familiar bootloader files.
But if it would work, so someone should test their specific files on U version, an AROMA zip would be interesting to make.
I can i you want but feel free to join in if A2017U and A2017 or good to go :good:
But then again we have to get some feedback on this.
raystef66 said:
Thnx for your reply.
But AFAIK this procedure might not work on the U version but not sure ( afaik no go on A2017). So therefore i just used the "known" familiar bootloader files.
But if it would work, so someone should test their specific files on U version, an AROMA zip would be interesting to make.
I can i you want but feel free to join in if A2017U and A2017 or good to go :good:
But then again we have to get some feedback on this.
Click to expand...
Click to collapse
First of all a happy new Year! :angel:
Think i will take a look on it in the next Days, would be cool if someone could test which Variants are supporting this. I see a flashable ZIP could be very useful for People who are switching the OS a lot of times (like i do). I own the G Version BTW.
BR
At the boot hold the Vol-Button and Power. And now you cant see the Bootloader-Message. Otherwise flash this zip: http://www120.zippyshare.com/v/xYBio6uW/file.html
I dont know if its work on the A2017U oder A2017 Devices. But it works definitely on the A2017G.
Miustone said:
First of all a happy new Year! :angel:
Think i will take a look on it in the next Days, would be cool if someone could test which Variants are supporting this. I see a flashable ZIP could be very useful for People who are switching the OS a lot of times (like i do). I own the G Version BTW.
BR
Click to expand...
Click to collapse
Happy new Year too and best wishes to all here on XDA !
Yeah such a zip for all variants should be handy. A A2017U user should test this method.
Anyway on G it works.
BaamAlex said:
At the boot hold the Vol-Button and Power. And now you cant see the Bootloader-Message. Otherwise flash this zip: http://www120.zippyshare.com/v/xYBio6uW/file.html
I dont know if its work on the A2017U oder A2017 Devices. But it works definitely on the A2017G.
Click to expand...
Click to collapse
This zip works on G version (not sure about other versions) but only when coming from Universal BL imo. When using the B13 bootstack f.e. like on Mifavor 5.0 this ZIP would not work imo. So be carefull flashing it. As said, when on Universal BL this should work.
Thanks !
BaamAlex said:
At the boot hold the Vol-Button and Power. And now you cant see the Bootloader-Message. Otherwise flash this zip: http://www120.zippyshare.com/v/xYBio6uW/file.html
I dont know if its work on the A2017U oder A2017 Devices. But it works definitely on the A2017G.
Click to expand...
Click to collapse
And if i have stock B08/B09 bootloader, not the universal BL?
I cant say that. It works under a2017g. But...you can test it. And say me if its work for the a2017u or a2017. But i cant guarantee for anything. Sry.
Okay then in another way: which bootloader was installed before you flashed your linked zip?
I messed up my phone completely one time with this "removal" from the first thread a few month ago.
So a wanna get sure this works with stock bootloader and not only the universal bootloader.
I also have the A2017G.
Spillunke said:
Okay then in another way: which bootloader was installed before you flashed your linked zip?
I messed up my phone completely one time with this "removal" from the first thread a few month ago.
So a wanna get sure this works with stock bootloader and not only the universal bootloader.
I also have the A2017G.
Click to expand...
Click to collapse
If you're not sure about the zip he provided, just don't use it
Do the above steps in 1st post and you'll be good to go. It takes only a minute or so, just copy paste in adb
Tip : just boot your phone in twrp before you do the steps. So you'll be sure about permissions
Spillunke said:
Okay then in another way: which bootloader was installed before you flashed your linked zip?
I messed up my phone completely one time with this "removal" from the first thread a few month ago.
So a wanna get sure this works with stock bootloader and not only the universal bootloader.
I also have the A2017G.
Click to expand...
Click to collapse
Better use @raystef66 method to remove the message.
Owning a A2017G isn't the only prerequisite to flash this file; like already said it depends on bootloader version, device encryption and probably much more ...
As you said, flashing this sort of stuff is too hasardous. Just take a look at the thread concerning this remover; lot of users "bricked" their devices with this stuff.
Pff
Spillunke said:
Hi all,
we need a person to test the tool, which removes the unlocked bootloader screen.
It do what it should do, but main problem is the question, if the adb.exe, which is included, is working in this case.
Axon 7 2017G on nougat with unlocked BL info-screen and a windows pc without ADB are the only requirements.
Download the file and give a feedback pls.
Click to expand...
Click to collapse
Why can't this be made via a flashable zip? It would be much easier to use and you wouldn't have to rely on Windows behaving.
The only thing needed would be to test if ro.product.model=ZTE A2017G, I don't know if you can read from build.prop with a flashable zip but if possible that would be the best approach. That would be to test if your phone is actually a G, minimize problems. Also, if you have the Universal Bootloader all this would do is restore fastboot; it wouldn't brick a G with univ bl (Someone made a flashable zip with an old aboot a while back actually. It was meant for getting fastboot back. I think it doesn't work though).
Choose an username... said:
Why can't this be made via a flashable zip? It would be much easier to use and you wouldn't have to rely on Windows behaving.
The only thing needed would be to test if ro.product.model=ZTE A2017G, I don't know if you can read from build.prop with a flashable zip but if possible that would be the best approach. That would be to test if your phone is actually a G, minimize problems. Also, if you have the Universal Bootloader all this would do is restore fastboot; it wouldn't brick a G with univ bl (Someone made a flashable zip with an old aboot a while back actually. It was meant for getting fastboot back. I think it doesn't work though).
Click to expand...
Click to collapse
It's indeed better to make an aroma zip for all devices. I'm actually looking into that right now. Hopefully with success. Come back to you when working on G in the first place.
A2017G & A2017U Remove Bootloader Unlock Warning
As the aboot and fastboot_unlock (from controllerboy thread) are the same in G & U (correct me if i'm wrong) this can be used on both models.
I've tested on my G and works flawless. Perhaps a U-user can test it out.
Remove Bootloader Unlock Warning on Axon 7G & U : https://androidfilehost.com/?fid=745849072291698596
it work but after reboot it dose not accept pattern password !
am2006 said:
it work but after reboot it dose not accept pattern password !
Click to expand...
Click to collapse
On my G it does. Pin, pattern.... No problem there.
Hmm, maybe coz am on LOS rom
am2006 said:
Hmm, maybe coz am on LOS rom
Click to expand...
Click to collapse
Don't think so because you used the universal B15 I suppose? Did those tests coming from that universal.
Can you not pattern afterwards?
Having a A2017U?
raystef66 said:
Don't think so because you used the universal B15 I suppose? Did those tests coming from that universal.
Can you not pattern afterwards?
Having a A2017U?
Click to expand...
Click to collapse
i use universal, my is A2017G, i do factory reset its work fine now