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.
Related
This guide will enable you to easily root your phone in 6 steps. I've taken out the mystery and complications.
1) Go to HTC Dev site and manually unlock your bootloader. Select "register" and create your account.
1a) After you are registered select "all other supported models" in the pull down box
1b) Click "begin unlock bootloader". it will ask "are you sure" yes of course you are. acknowledge legal terms. then continue.
1c) Ignore the battery pull instructions as we can't pull the battery. hold down the power key and the volume down key until the bottom buttons stop flashing and your phone shuts off (don't worry if you take a screenshot. It happens all the time). then release ONLY THE POWER BUTTON. Keep holding the volume down key until the bootloader screen shows up.
1d) Follow "step 3" and the rest of the instructions as listed on the HTC site to unlock your bootloader manually.
2) Install android ADB/SDK on your pc. This video shows how to do it nicely:
2a) ****NEW UPDATED 03/05/13*** Alternatively if you DON'T want to install ADB/SDK you can just download the NON-FLASHABLE platform-tools.zip file located in my dropbox folder here.
Just extract this folder to your desktop using WINZIP or whatever archive tool you use and proceed to step 3.
3) Open a command line in your "platform-tools" folder by holding shift+right click anywhere within the folder and selecting the menu option "open a command window here". Then click here to install TWRP using fastboot. Follow the "Download - Fastboot Method:" instructions.
3a) If your phone isn't detected by windows please install the proper USB drivers for your operating system. Go here for 32bit. Go here for 64 bit.
4) Flash SuperSu and Busybox on your device:
4a) Click here and download the latest version of SuperSu. save it to your sdcard.
4b) Go to my dropbox and download Busybox 1.20.2 and save it to your sdcard.
5) Reboot into recovery (via the bootloader selection)
6) Flash the SuperSu zip and the Busybox zip listed in 4a and 4b
That's it!
"So now what?" you may be asking.
You are now free to flash ROMs that support s-on.
Two are my favorites are
(1) Stock with Goodies. (my personal favorite and the one I use today). This is a great ROM for beginners and people who prefer a slimmed down ROM (minus the bloat) and lots of free memory!
(2) Viper4G. This is a ROM for more experienced users and offers TONS of customization.
You can also run apps from Google play that required ROOT access!
If you're feeling slightly adventurous you can flash a custom kernel (which will allow you to overclock your phone). Two of the kernels I use are:
(1) ElementalX by flar2. Click here to take a trip over there. This one is especially important to flash as it seems HTC was up to shenanigans with the latest HBoot (2.09).
If you're unlucky enough to have HBoot 2.09 they have RESTRICTED access to your /system partition. What does this mean to you? It means that if any app writes to your /system partition (ROOTED or not) the phone will "panic" and reboot. Shady behavior if you ask me. The solution? Flash this kernel! it will give you write access so that everything works properly.
(2) The Arc-Reactor kernel! This one is for people that are s-off (see below for an explanation of s-off) only! It's the kernel I currently use and is the fastest kernel out there! Highly recommended if you decide to go s-off!!!
If and when you're feeling more adventurous you can go "s-off" (security off) which removes any security limitations of your phone. It makes flashing ROMs and updating firmware a lot easier. You can find out about s-off by taking a trip over to the DirtyRacun thread here. I will NOT walk you through this process. They will totally help you on their IRC channel. Just read post # 1 in that thread.
There's also a new method of s-off which literally takes 2 minutes. It's called facepalm and is located here But is NOT for the feint of heart, bad typers, nor people that cannot follow instructions! Why? One typo here and your phone is a brick. A paperweight. Useless. Well...you can recover...but that's not the purpose of this thread. If you DO brick your phone PM me. I'll help you out.
I take NO credit for any of this. It's all out there to learn I just put it all together. In one spot. Any questions feel free to PM me.
If I helped you out hit the THANKS button...or buy me a beer! Either way lol!
Tested and works with 3.16.651.3 (even if you took the OTA and have hboot 2.09 and are s-on)
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
lancemoreland said:
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
Click to expand...
Click to collapse
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
rawintellect said:
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
Click to expand...
Click to collapse
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
lancemoreland said:
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
Click to expand...
Click to collapse
Indeed this is a well documented problem but really not what this thread is about. Perhaps you can check out THIS thread where they are discussing this issue at length and hopefully they will come up with a solution for it?
http://forum.xda-developers.com/showthread.php?t=1538053
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
rawintellect said:
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
Click to expand...
Click to collapse
Yes I am participating in that thread. Chainfire is looking for a work around for his specific app, other apps that write to the system partition will no longer work. The point is that with Hboot 2.09 there are limitations and we will not enjoy full root as we have before when we were s-on.
Updated with an alternative superuser program.
SuperSU would ask to update binary and then just reboot. This fixed my problem for being able to access/deny and turn off messages. However it did not uninstall superSU will this cause a conflict having them both?
Edit: Okay I am dumb, I had to uninstall superSU first. Then I reflashed superuser to be able to have root privileges for my apps. When I just reflashed superuser hoping it would get ride of and superuser and keep root it did not.
Thanks it worked!
Help with rooting please.
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
MrSteez said:
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
Click to expand...
Click to collapse
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Updated thread with instructions on manually uninstalling supersu first before installing superuser 3.2
Thank you very much!
rawintellect said:
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Click to expand...
Click to collapse
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
MrSteez said:
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
Click to expand...
Click to collapse
yes. going back to stock is as simple as this:
(1) Boot your phone into the bootloader. make sure fastboot is selected. if you have the drivers installed correctly your phone will read "fastboot usb"
(2) if you followed my instructions on rooting you have ADB/SDK installed. so issue the command to relock your phone. type: fastboot oem lock
(3) run the RUU for 3.15.651.16. Done. Your bootloader will say *relocked* but it will be 100% stock.
Uh oh
I think i messed up. I did not see busy box installed and SuperSU is not updating.
The file listed in step 6 contains busybox. It also contains supersu. You want to flash the superuser file after flashing the file in step 6. It will overlay supersu with superuser 3.2. There is no need to update superuser 3.2 once you flashed it. It is the latest release.
Sent from my EVO using xda app-developers app
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
mobilecj said:
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
Click to expand...
Click to collapse
I replied to your email. But check my first post on the subject of superuser and how to uninstall supersu. if you need to that is. I tested this myself and it did uninstall supersu for me by just flashing superuser 3.2. Some people have reported this doesn't work for them.
okay sorry just got both i am going to try it now.. Its all knew to me it seemed like the information was explaining a dual process and i only had acquired one problem.. will post back in a few!
General info:
There will be a lot of discussion, do not follow untested tuts in this thread. It could cause you to brick your phone into a Cool paperweight.
AS OF 9/1/2015
XT1528-Surnia_Verizon
Board- MSM8916
Bootloader-NOT UNLOCKABLE!- EVEN IF YOU GO THROUGH MOTO'S WEBSITE (Verizon Locked it, not moto. & verizon cant unlock it) Viewable by booting into recovery & reading the screen.
Android 5.0.2-armv7l-240 DPI
Updated to 5.1
200MHz-1.21GHz quad core-Qualcomm Snapdragon 400/410
Root- No Write/full access-Cant seem to uninstall system apps on Android 5.0?/5.1
Screenshot: Attached at bottom of KINGROOT APK(4.5) via One click root method working on my updated 5.1 lolipop xt1528.
KingRoot does not root your device, just allows for removal of pre installed software via kinguser.After uninstalling, it crashed my Google launcher app & was fixed via rebooting which caused my system to have to re-optimize all apps which took 5 minuets. Root access is denied. Autostart manager works
Unrootable, Locked bootloader, but excellent capability. I love 5.1 better. I wouldnt recommend this device for anonymous browsing (I like to use Tor as a VPN), torrenting, or sharing. But I love the battery (lasts all day without heavy gaming use), phone calls & txts, Browsing the web is good too. I love being able to take out my phone and say "Ok Google" to vocally search or open things (like cortana) and my phone talk back. As well as the easy-to Use feeling comes if you've expierienced 5.0 before, a little confusing if you've been stuck on <4.0.I feel comfortable with it & it fits in my pocket pretty well. I don't know how much radiation it throws off... I say 7/10 overall. No xposed, if your lucky to rebuild the APK & patch it you can do it.. 4g is awesome! & I'm happy I didn't go with a free phone. Although, i'll be getting one soon to play with.
Thank you, Thanks for reading, & Have a wonderful day! (ALL Useful info & credits to who said it will be added via a reserved spot below.)
LATEST Answers :SU-ME didnt work for me on 5.0, and even though KingRoot said i had root access, It wouldnt give it to anything or allow write access.... Also, I attempted to root 5.1 off the v4.1 apk. It said root strategy available-Gave me (nothing past words)root access-But caused a bunch of apps to continuously crash. (I'll try it again once i go through my dev settings, i also factory wiped it earlier). It said i could remove system apps, It couldnt though. I used the auto-start manager too (we'll see if that stuck). (pics below) Also, Anyone who provides any testing will get thanked & a name below.
_______________________________________
| RESERVED |
| Thank you, kmani.k78 |
| Whoareyou |
| DBlake1 |
Yep it is possible to root.
First download supersu.zip here-
https://download.chainfire.eu/696/SuperSU
Now install custom recovery on your device using adb and fastboot. (TWRP is preferred coz many reported cwn not working)
Once twrp is installed boot in recovery.
Then tap install and select the supersu.zip where u downloaded it.
Just flash it and tada!!
Reboot in system and your moto e with lollipop is rooted.
I rooted by same method.
#peace and hope it helped you.
The hardest part is unlocking the bootloader. Without that, it's impossible to root.
I wish I had seen this thread before I picked up this phone today. :/
As I did pick one up as something to play with and not necessarily just for custom roms, I'm not immediately returning it, but it's a strong possibility.
Manish_Sky said:
Yep it is possible to root.
First download supersu.zip here-
https://download.chainfire.eu/696/SuperSU
Now install custom recovery on your device using adb and fastboot. (TWRP is preferred coz many reported cwn not working)
Once twrp is installed boot in recovery.
Then tap install and select the supersu.zip where u downloaded it.
Just flash it and tada!!
Reboot in system and your moto e with lollipop is rooted.
I rooted by same method.
#peace and hope it helped you.
Click to expand...
Click to collapse
When I try installing twrp via fastboot I receive a preflash error. I have yet been able to boot into recovery., I just get a red triangle and "no command" . What am I doing incorrect?
I don't understand the recovery mode for this phone, I'm used to 4.0.4 lol. I'm not sure either. I thought I broke my system when I tried to adb flash twrp & found out you can't shut your phone off when its in recovery mode. (Also, you can't flash without unlocking the bootloader) DUH right?
Manish_Sky said:
Yep it is possible to root.
First download supersu.zip here-
Now install custom recovery on your device using adb and fastboot. (TWRP is preferred coz many reported cwn not working)
Once twrp is installed boot in recovery.
Then tap install and select the supersu.zip where u downloaded it.
Just flash it and tada!!
Reboot in system and your moto e with lollipop is rooted.
I rooted by same method.
#peace and hope it helped you.
Click to expand...
Click to collapse
You can't flash without an unlocked bootloader. The XT1528 isn't supported by Motorola for unlocking because its a Verizon phone. Verizon doesn't like giving out codes, and wouldn't even if you asked. I think unless someone can Dev the crap outta it, We're screwed XT1528 wise. But, I don't know much about anything lol. I'm still learning.
Manish_Sky said:
Yep it is possible to root.
First download supersu.zip here-
https://download.chainfire.eu/696/SuperSU
Now install custom recovery on your device using adb and fastboot. (TWRP is preferred coz many reported cwn not working)
Once twrp is installed boot in recovery.
Then tap install and select the supersu.zip where u downloaded it.
Just flash it and tada!!
Reboot in system and your moto e with lollipop is rooted.
I rooted by same method.
#peace and hope it helped you.
Click to expand...
Click to collapse
this is not possible on verizon version xt1528. bootloader is unlockable. will need an android 5 vulnerability to gain root which is the best the verizon version will ever get.
Most likely way to root this phone would be to use an app that has a Lollipop exploit, but they're getting harder according to this article:
http://www.androidpolice.com/2014/1...ew-modified-kernels-may-become-a-requirement/
Okay so now I have gone and picked up the AT&T XT 1527 version. I now have a XT 1528 I can test with. Question, should I go ahead and root the XT 1527? I am thinking about wiping everything off Verizon phone and installing Fedora on it, but if there are other suggesting, I now have a test sled that can be used. I am open to suggestions with the verizon phone, let me know what you all think.
XT1528 can be rooted by "Kingroot" method - a closed source app!
kmani.k78 said:
XT1528 can be rooted by "Kingroot" method - a closed source app!
Click to expand...
Click to collapse
Have you tried it yourself?
Sent from my XT1528
Ace42 said:
Have you tried it yourself?
Sent from my XT1528
Click to expand...
Click to collapse
Yes I have already rooted my xt1528.
kmani.k78 said:
Yes I have already rooted my xt1528.
Click to expand...
Click to collapse
Have you used any GSM sim in India with Verizon Moto E?
Are you getting 3G?
And if you are using with CDMA, atleast 3G working with that?
I will be receiving mine tomorrow, dunno if it works or not
kmani.k78 said:
Yes I have already rooted my xt1528.
Click to expand...
Click to collapse
Can somebody please confirm?
Thanks!
Just run on XT 1528 android 5.1..... not rooted according to root check
Harish_Kumar said:
Have you used any GSM sim in India with Verizon Moto E?
Are you getting 3G?
And if you are using with CDMA, atleast 3G working with that?
I will be receiving mine tomorrow, dunno if it works or not
Click to expand...
Click to collapse
I am using it on Reliance CDMA netowrk. When it was on 5.0.2, I could able to connect to 3G.
But After update to 5.1, I could not use 3G. Only call & sms working.
I have rooted xt1528 in android 5.1 to make modification in the system partition. Rooting works perfectly. but changes made to system partition revert backs to stock after reboot.
Could anyone help me to make permanent changes to /system/build.prop file?
kmani.k78 said:
I am using it on Reliance CDMA netowrk. When it was on 5.0.2, I could able to connect to 3G.
But After update to 5.1, I could not use 3G. Only call & sms working.
I have rooted xt1528 in android 5.1 to make modification in the system partition. Rooting works perfectly. but changes made to system partition revert backs to stock after reboot.
Could anyone help me to make permanent changes to /system/build.prop file?
Click to expand...
Click to collapse
How did you root your XT1528? Link?
Whyzor said:
How did you root your XT1528? Link?
Click to expand...
Click to collapse
I followed this video - https://www.youtube.com/watch?v=QicDqTKb_sU
kmani.k78 said:
I followed this video - https://www.youtube.com/watch?v=QicDqTKb_sU
Click to expand...
Click to collapse
kmani.k78 said:
I am using it on Reliance CDMA netowrk. When it was on 5.0.2, I could able to connect to 3G.
But After update to 5.1, I could not use 3G. Only call & sms working.
I have rooted xt1528 in android 5.1 to make modification in the system partition. Rooting works perfectly. but changes made to system partition revert backs to stock after reboot.
Could anyone help me to make permanent changes to /system/build.prop file?
Click to expand...
Click to collapse
Thanks for reporting root worked on your moto e, this is fairly new, Im waiting to see if others can repeat it, and whether it really does work. Have you tried some other apps that require root to see if they actually work with root?
For your specific /system/build.prop issue, some roms write that file from another location, /etc/build.prop or some other similar paths, so maybe need to find that file. Also you have to remount /system as read-write, assuming this worked otherwise there would be an error right away.
Usually I edit /system/build.prop files manually with terminal emulator app, then type these commands:
su (proper root needed)
mount -o rw,remount /system/build.prop
vi /system/build.prop ( may need to install busybox app)
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 !!!
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Whoa! the unlock tool is out!
Is there any chance someone can make a root guide? I really want to buy Zenfone 3 Ultra but I wouldn't do it without root method out there. Any help is appreciated.
Were waiting on a dev to compile TWRP for us then we can get root
Trying to root ZU680KL
Hi!
I have unlocked my ZU680KL with the Asus unlock tool. Bootloader shows 'unlocked'.
Then I unpacked the stock boot.img (from WW_13.6.15.21_20161215, this what I have installed) and using Vim I set:*ro.secure=0, ro.adb.secure=0, and*ro.debuggable=1 in default.prop.
Repacked the new boot.img and flashed it with 'fastboot flash boot new-boot.img'.
'adb shell getprop' indicates that the new setting was applied.
Yet in the stock recovery mode I cannot install SuperSU-v2.79.zip and no adb devices are seen in recovery mode.
What else is needed? Do I have to edit something in the stock recovery or must wait for custom TWRP?
I was following the basic instructions found here:
https://machiry.wordpress.com/2012/10/26/getting-root-access-on-android-the-actual-way/
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
hillg001 said:
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
Click to expand...
Click to collapse
Any news?
https://forum.xda-developers.com/ze...t-zenfone-3-ultra-7-0-ww14-1010-1703-t3612108
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
when the ultra 3 first came out, many suggested waiting for a boot loader unlocker, & not updating any Android versions, because an unlock program might not work on subsequent Android versions. Is that the case? ... or does the unlocker work on the newest Android version too.
Thanks
.
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
I have just downloaded the zip, made the APK and installed it on my Zenfone 3 Ultra.
When I run the app, after clicking all the "are you sure..." acknowledgements, the app does not succeed in unlocking the bootloader. The error message indicates an unknown or perhaps network error, and suggests I "try again later..."
Running WW_14.1010.1804.75_20180612
Anybody else seeing this?
Ideas??
Reading on the ASUS blogs, they indicate it isn't supported anymore (no surprise), but shouldn't it still work??
heroxbd said:
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
Click to expand...
Click to collapse
Note the links above no longer work. Yes, you can get to the page, but the unlocker isn't there any more.
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
Does anybody know which version(s) of the stock ROM this works with? I've tried a couple, and all of them just yield the "unknown error" when running the unlocker.
If you know of a stock ROM version this works with, please post a URL for where I can find it (as it's proven really hard to find specific versions...)
Thanks in advance.
agree it no longer works. getting the unknown error...wait message that everyone else is getting. there are other XDA threads that indicate the same.
Keeping bootloader locked. Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even the SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
-
jrchester said:
Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even and SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
Click to expand...
Click to collapse
How did you do that? Can I get more details?
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hi Madlzz:
Checkout my XDA post here for more details on how I did this:
unlocking bootloader zenfone ultra
Hi all ive had my zenfone 3 ultra (zu680kl) for some years, until a couple of days ago, my friend wanted to see if my phone could be charged with a dash charger, where others wouldnt my battery was already low and overnight it ran out and when i...
forum.xda-developers.com
- John
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
lucy1983 said:
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
Click to expand...
Click to collapse
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
jrchester said:
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
Click to expand...
Click to collapse
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
lucy1983 said:
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
Click to expand...
Click to collapse
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
jrchester said:
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
Click to expand...
Click to collapse
You can install Magisk 24 without any problems. For me it doesn't break safetynet and play store says "certified". Even without enabling zigisk.
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 .