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)
Related
*** DISCLAIMER ***
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE! OR IF YOU LOSE ANY DATA, ITS CALLED BACK IT UP BEFORE HAND!
Word to the wise if you don't know how to use RSDLite or Fastboot to restore your phone then leave this thread now please! You need to backup everything on your internal storage before you install this in case you need to restore back. If using the Safestrap version this rom needs to be flashed to the STOCK SLOT and the 4.4.2 KitKat Kernel and Baseband need to be flashed for it to work. If your Unlocked you either need to be on 4.4.2 prior to install or flash the 4.4.2 Baseband after the install. YOU'VE BEEN WARNED!
Okay this is a stock unmodified rooted rom of the Republic Wireless and C-Spire 4.4.2 KitKat OTA with full Safestrap functionality, except for restoring back to 4.2.2. To go back to 4.2.2 you will have to restore back using RSD or Fastboot. You will need to have the phone's drivers installed to get this working, so click the link below to download them and install them before you start. https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
I don't own a XT1049 I threw this together for some users that asked for it, y'all will be my testers to confirm it's working.
Instructions to install this rom for Safestrap Users, read every step before you start...
1. You need to be rooted on 4.2.2 or 4.4 with Safestrap installed
2. You also need to have disabled write protection via MotoWpNoMo
3. Boot into Safestrap Recovery
4. Factory Reset the STOCK Slot in Safestrap DO NOT wipe the /system it can cause issues
5. Flash the Rom zip to the STOCK Slot (this can take up 10 minutes just walk away and let it finish)
6. Once the Rom has finished flashing, reboot to the Bootloader from within Safestrap
7. Plug your Moto X via usb cable into your computer the Bootloader screen should say usb connected now
8. Unzip the "RW & C-Spire Moto X Kernel and Radio Flasher.zip"
9. Open the extracted folder and find the FlashMyMotoX.bat and run it
10. For RW choose option 2 and for C-Spire option 4 within the FlashMyMotoX utility to flash the 4.4.2 KitKat Kernel
11. Once it finishes get back to the options and for RW choose option 3 and for C-Spire option 5 this will flash the 4.4.2 KitKat Baseband
12. Once it finishes successfully unplug your usb cable and reboot the phone
13. Enjoy 4.4.2 KitKat!
For Unlocked Users
1. Boot into TWRP 2.7 factory reset then install the rom.
2. If you were on 4.4.2 already then reboot and enjoy if you weren't on 4.4.2 then continue to step 3.
3. Once done installing reboot to the bootloader from within TWRP.
4. Once on the bootloader screen plug your usb cable into your Moto X the screen should say usb connected.
5. Extract and run my utility for RW choose option 3 and for C-Spire option 5 to flash the 4.4.2 Baseband.
6. Reboot and Enjoy 4.4.2!
Downloads: DO NOT repost links on other forums, link them to this thread!
Republic Wireless Versions
Safestrap Version
Unlocked Version
C-Spire Versions
Safestrap Version
Unlocked Version
Utility
RW & C-Spire Flashing Utility
Thanks to Google for Android and their Search engine, Hashcode for Safestrap, jcase for root, beaups and fuses for MotoWpNoMo, dhacker29 for TWRP 2.7, and the Chinese middle man for my bootloader unlock without them this wouldn't be possible!
great work
Stuck at "Formatting System...."
I followed your guide and at the point where I am attempting to flash the update, it is hung up. The last message the console printed was "formatting system...."
What should I do? It has been 5 minutes now... If the update is corrupt somehow, is there any way to push another version to the device from recovery?
* UPDATE * the flash finally completed. For those of you that are unsure, let it sit. It takes quite some time to flash (more than a couple minutes)!
I followed your guide, and did the install. I installed the Safestrap APK after everything was up and running. I am unable to reboot the device with R/W permissions. Write protection IS enabled after the reboot. Did I do something wrong?
slgooding said:
I followed your guide and at the point where I am attempting to flash the update, it is hung up. The last message the console printed was "formatting system...."
What should I do? It has been 5 minutes now... If the update is corrupt somehow, is there any way to push another version to the device from recovery?
* UPDATE * the flash finally completed. For those of you that are unsure, let it sit. It takes quite some time to flash (more than a couple minutes)!
Click to expand...
Click to collapse
slgooding said:
I followed your guide, and did the install. I installed the Safestrap APK after everything was up and running. I am unable to reboot the device with R/W permissions. Write protection IS enabled after the reboot. Did I do something wrong?
Click to expand...
Click to collapse
Yeah the install for Safestrap takes forever for some reason it doesn't for custom recoveries though. You need to run MotoWpNoMo to remove Write Protection, because you can't flash the 4.4.2 boot.img to the recovery partition, Moto signed them with different keys. It says that in the OP!
slgooding said:
I followed your guide, and did the install. I installed the Safestrap APK after everything was up and running. I am unable to reboot the device with R/W permissions. Write protection IS enabled after the reboot. Did I do something wrong?
Click to expand...
Click to collapse
did you run MotoWpNoMo when you were still on 4.2.2 ? thats the only way to retain write protection on 4.4.2
jbrukardt said:
did you run MotoWpNoMo when you were still on 4.2.2 ? thats the only way to retain write protection on 4.4.2
Click to expand...
Click to collapse
Well crap. I can't believe I missed that step... Is it safe for me to flash back to 4.2.2 (using safestrap recovery), remove WP and then upgrade again? I'm guessing I'm stuck...
slgooding said:
Well crap. I can't believe I missed that step... Is it safe for me to flash back to 4.2.2 (using safestrap recovery), remove WP and then upgrade again? I'm guessing I'm stuck...
Click to expand...
Click to collapse
I'm pretty sure you can run MotoWpNoMo while on 4.4.2, I might be wrong but I think someone did it in my Verizon 4.4.2 thread. I will check the comments later.
iKrYpToNiTe said:
I'm pretty sure you can run MotoWpNoMo while on 4.4.2, I might be wrong but I think someone did it in my Verizon 4.4.2 thread. I will check the comments later.
Click to expand...
Click to collapse
I just ran it MotoWpNoMo within 4.4.2. It WORKED. I verified with the following command: adb shell getprop ro.boot.write_protect
This means that for anyone that didn't remove write protection before updating (but had rooted prior to update) you can still disable WP.
slgooding said:
I just ran it MotoWpNoMo within 4.4.2. It WORKED. I verified with the following command: adb shell getprop ro.boot.write_protect
This means that for anyone that didn't remove write protection before updating (but had rooted prior to update) you can still disable WP.
Click to expand...
Click to collapse
Nah it still works because you're not on the 4.4.2 bootloader!
I was succesfully able to update to 4.4.2 with this update.zip. It is working great and I still have root! I did forget to wipe before updating, but so far I haven't noticed any problems. If I do, I just do a wipe and reflash. Thanks!
RobertsDF said:
I was succesfully able to update to 4.4.2 with this update.zip. It is working great and I still have root! I did forget to wipe before updating, but so far I haven't noticed any problems. If I do, I just do a wipe and reflash. Thanks!
Click to expand...
Click to collapse
Glad to hear, Enjoy!
Just updated my wife's moto x as well. Once again, it's working great.
Sent from my XT1049 using Tapatalk
settings are force closing when I try to access it.
I had Installed everything fine, had root, safestrap and wpnomo active prior to installing the 4.4 ROM.
Everything is working fine, except for my settings. I cannot turn off the option to install app store only apks. The settings app is force closing when I try to access it. From settings > personal > security. Then it just force closes. Any help would be appreciated.
I did do a factory reset from withen safestrap prior to installing, without wiping system. Should I wipe again now that its on 4.4? Maybe try wiping system.
It seems silly to have root If I can't use adaway, ES File explorer, titanium, Xposed and gravitybox. That sorta defeats the purpose of having root.
If you happen to be a Dev if this bug is either confirmed or absolved, I have a bug report I can share if needed.
-------------------------------------------------------
Sent via my Republic Wireless XT1049 Moto X with Tapatalk Pro.
-------------------------------------------------------
PM or e-mail me if you want to as well starting @ $5/month!
-------------------------------------------------------
Hello guys,
Just curious - Is anyone that successfully unlocked their bootloader (on Republic Wireless Moto X) with China code interested in selling their unlocked moto X?
I'm disappointed that I missed the bandwagon, so this may be my only opportunity to obtain an unlocked unit.
Thanks,
samwathegreat
EDIT: Offer withdrawn. Got BL unlocked. Thanks anyways.
EeyoreSyndrome said:
I had Installed everything fine, had root, safestrap and wpnomo active prior to installing the 4.4 ROM.
Everything is working fine, except for my settings. I cannot turn off the option to install app store only apks. The settings app is force closing when I try to access it. From settings > personal > security. Then it just force closes. Any help would be appreciated.
I did do a factory reset from withen safestrap prior to installing, without wiping system. Should I wipe again now that its on 4.4? Maybe try wiping system.
It seems silly to have root If I can't use adaway, ES File explorer, titanium, Xposed and gravitybox. That sorta defeats the purpose of having root.
Click to expand...
Click to collapse
I used Malcolmputer's exploit instructions and packages so that may be the difference but you are the first one to report this issue in either this thread or his.
Try booting into Safe Mode. That will tell you if it is an app conflict. Android Device Manager, and probably others too, can tell you what order your apps were installed in so that you can trace back to find the rogue app if Settings no longer does an f.c. in Safe Mode.
If it still crashes in Safe Mode then remember: The first rule of the Force Close club is -- don't let your cache talk to Android! The SafeStrap ROM was a bit of a learning curve for me (or I just worry too much) but if you go into it and Select WIPE there are 4 checkboxes. Start with just the cache. If you have already done that then ...
The next step is to wipe cache and Dalvik cache. Your phone will take much longer to boot up after that as it needs to rebuild the Dalvik cache. It will show you app by app until it finishes.
Malcolmputer has said that his idea was that if things went wrong that you could:
I did it. I now have an update.zip that you can flash from SafeStrap, keeping your recovery where it is at already.
This means that if you f- something up, you can just sbf back to stock 4.2.2, root, safestrap, my update.zip, and then be back at rooted 4.4.2, with WP off.
Click to expand...
Click to collapse
I sure hope it doesn't come to that.
I also haven't seen any reports of anyone trying it either, so ...
EeyoreSyndrome said:
I had Installed everything fine, had root, safestrap and wpnomo active prior to installing the 4.4 ROM.
Everything is working fine, except for my settings. I cannot turn off the option to install app store only apks. The settings app is force closing when I try to access it. From settings > personal > security. Then it just force closes. Any help would be appreciated.
I did do a factory reset from withen safestrap prior to installing, without wiping system. Should I wipe again now that its on 4.4? Maybe try wiping system.
It seems silly to have root If I can't use adaway, ES File explorer, titanium, Xposed and gravitybox. That sorta defeats the purpose of having root.
If you happen to be a Dev if this bug is either confirmed or absolved, I have a bug report I can share if needed.
-------------------------------------------------------
Sent via my Republic Wireless XT1049 Moto X with Tapatalk Pro.
-------------------------------------------------------
PM or e-mail me if you want to as well starting @ $5/month!
-------------------------------------------------------
Click to expand...
Click to collapse
Did you flash the new 4.4.2 baseband? There was issues with 4.4 if you didn't flash the baseband you would have FC's in the security settings.
iKrYpToNiTe said:
Did you flash the new 4.4.2 baseband? There was issues with 4.4 if you didn't flash the baseband you would have FC's in the security settings.
Click to expand...
Click to collapse
Maybe I was impatient in flashing the last two things
OBV if I didn't flash the kernal, it would simply not boot right?
On the kernal / baseband flasher, I get to "flashing modem" then done on my fastboot screen.
But the program seems to stick at "writing modem".
After unplugging the usb cord and then back in, it then finished erasing partition modems 1+2 and then flashed the fsg.
Okay, seems that I didn't properly flash the baseband on the first go, thanks for helping me troubleshoot! At least I can confirm that not having that updated baseband = force closing in settings app.
EeyoreSyndrome said:
Maybe I was impatient in flashing the last two things
OBV if I didn't flash the kernal, it would simply not boot right?
On the kernal / baseband flasher, I get to "flashing modem" then done on my fastboot screen.
But the program seems to stick at "writing modem".
After unplugging the usb cord and then back in, it then finished erasing partition modems 1+2 and then flashed the fsg.
Click to expand...
Click to collapse
I had this issue one time while trying to flash a kernel using my new usb 3.0 ports it ended up borking my phone pretty bad had to rsd several times to 4.2.2 to fix. I only use my usb 2.0 ports for flashing now. When do you get FC, is it as soon as you open the security settings or is it when you check unknown sources?
Hmm I used my USB 3.0 as well, didn't stop to think about it.
As for what your Bork was, what happened?
The FC happened as soon as I clicked on security, couldn't make it futhur then that.
As it is, things seem fine now, tho If you feel I should reflash em on USB 2.0, let me know.
Sent from my XT1049 using Tapatalk
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.
Hi all!
I'm new here, so please instruct me if I'm doing anything wrong.
I have a Coolpad Y82-820. It's a Chinese phone, I think.
I'm in the process of getting it rooted. ---- Was rooted before, but an update on their side (to CoolUI V24. [phone model#]. 160407) removed the root and now makes it a bit difficult to root at the moment, though I'm sure it will be done eventually. For those who have this phone, I'd suggest not to update, as this update deletes any rooting applications installed on reboot/restart.
Once rooted, I don't really mind waiting, I would like to put a Custom Rom on this phone, but not sure what options are available. I see posts about the Coolpad Note/Dazen/Shine/Rogues etc. Though nothing about this one, though spec wise it's not too far off from the others.
I'd be grateful if anyone could help with confirmations, information, on how to select a correct custom rom for this device and the steps to do. Also if there's any info on how to root this current version, even better.
Thanks!
Some details of the phone below:
Model Number
Coolpad Y82-820
CPU
Qualcomm Technologies, Inc MSM8916 Quad-core 1.2 GHz
RAM
2G
Internal memory
Total 8G
Resolution
960 * 540
Android version
4.4.4
Kernel version
3.10.28
[email protected] #1
Thu Apr 7 17:01:56 CST 2016
Build number
4.4.005.150730.Y82_820
Any help possible?
Rooting maybe? Even possibly downgrading would be an option.
Johny2k9 said:
Any help possible?
Rooting maybe? Even possibly downgrading would be an option.
Click to expand...
Click to collapse
Did you try towelroot?It's best for rooting Kitkat.https://towelroot.com/
Røbin said:
Did you try towelroot?It's best for rooting Kitkat.https://towelroot.com/
Click to expand...
Click to collapse
Gave it a shot. Failed, as well. I've tried most of the popular rooting apps. King Root, Kingo, One click, and so on as well as a few Chinese rooting apps, as well. They've all failed.
The previous version was rooted with King Root though.
Johny2k9 said:
Gave it a shot. Failed, as well. I've tried most of the popular rooting apps. King Root, Kingo, One click, and so on as well as a few Chinese rooting apps, as well. They've all failed.
The previous version was rooted with King Root though.
Click to expand...
Click to collapse
In that case you have to root your phone manually by unlocking bootloader.But as a Chinese phone don't need to unlock bootloader.But you need to have a recovery that can install flashable zip.Most of this phone have built in recovery.You can go to recovery by turning off your phone and press power+volume down button.Then see if there's any option to install zip.
Røbin said:
In that case you have to root your phone manually by unlocking bootloader.But as a Chinese phone don't need to unlock bootloader.But you need to have a recovery that can install flashable zip.Most of this phone have built in recovery.You can go to recovery by turning off your phone and press power+volume down button.Then see if there's any option to install zip.
Click to expand...
Click to collapse
There is an option there to install zip files. Though I do not know the process well of doing so. Most zips I have tried have failed. I did install GMS several days ago using the install zip method. Not certain if that was a good idea though...
If I can find a flashable zip then I wouldn't mind giving it a try. I've restored this phone countless times hoping to go back to factory firmware, but that doesn't seem to be the case. It seems to go back to the most recent updated OTA which makes it unable to root with regular apps at the moment.
Not sure what the closest phone model for this phone would be. If you have ideas I'm willing to give them a shot an report back in with any findings.
Johny2k9 said:
There is an option there to install zip files. Though I do not know the process well of doing so. Most zips I have tried have failed. I did install GMS several days ago using the install zip method. Not certain if that was a good idea though...
If I can find a flashable zip then I wouldn't mind giving it a try. I've restored this phone countless times hoping to go back to factory firmware, but that doesn't seem to be the case. It seems to go back to the most recent updated OTA which makes it unable to root with regular apps at the moment.
Not sure what the closest phone model for this phone would be. If you have ideas I'm willing to give them a shot an report back in with any findings.
Click to expand...
Click to collapse
https://download.chainfire.eu/696/supersu/ go to this link,download UPDATE-SuperSU-v2.46.zip and install it.This is the way to have root manually.
Røbin said:
https://download.chainfire.eu/696/supersu/ go to this link,download UPDATE-SuperSU-v2.46.zip and install it.This is the way to have root manually.
Click to expand...
Click to collapse
I got an error:
正在查找更新包
正在打开更新包
正在验证更新包
E : failed to verify whole-file signature
E : signature verification failed 安装失败
我会汉语一点儿，所以这个汉字我都明白了，如果你有问题我可以试一试告诉你。 My Chinese isn't too bad, so if there's something you don't understand let me know.
Letting you know the steps I did, just in case I did it wrong.
- Downloaded the UPDATE-SuperSU-v2.46.zip
- Placed it on the phone internal memory (recovery only recognizes internal)
- Powered off
- Went into recovery mode
- Then tried installing the file.
Then the mentioned error.
Should I have restored the phone to the most recent OTA, cleared cache, data, first etc?
Johny2k9 said:
I got an error:
正在查找更新包
正在打开更新包
正在验证更新包
E : failed to verify whole-file signature
E : signature verification failed 安装失败
我会汉语一点儿，所以这个汉字我都明白了，如果你有问题我可以试一试告诉你。 My Chinese isn't too bad, so if there's something you don't understand let me know.
Letting you know the steps I did, just in case I did it wrong.
- Downloaded the UPDATE-SuperSU-v2.46.zip
- Placed it on the phone internal memory (recovery only recognizes internal)
- Powered off
- Went into recovery mode
- Then tried installing the file.
Then the mentioned error.
Should I have restored the phone to the most recent OTA, cleared cache, data, first etc?
Click to expand...
Click to collapse
Ok i'll give you a last solution to root your device.
first go to this linkhttp://www.file-upload.net/download-7267586/usb_driver.rar.html and download the driver file and extract the file.Now first enable developer options in your phone to enable usb debug and connect your phone to pc.In your pc right click on Computer/My PC icon and go to manager.click device manager and you will see your connected device.Now click on your device and find install driver,go and find the extracted file to install driver.After installing driver download root genius from this linkhttps://mega.nz/#!G4US0aTA!rfkmf4GSUJ75FSpq3_OBzKw58WLlExImjzlHVti5rbM,Install it and open the app.Your device will automaticlly connect to root genius.Now the final step is to click root word,click the green box,wait for 10 minute to complete the rooting process.your phone will reboot.all done.now check your device if its rooted or not by installing root checker app via google play store.
Røbin said:
Ok i'll give you a last solution to root your device.
first go to this linkhttp://www.file-upload.net/download-7267586/usb_driver.rar.html and download the driver file and extract the file.Now first enable developer options in your phone to enable usb debug and connect your phone to pc.In your pc right click on Computer/My PC icon and go to manager.click device manager and you will see your connected device.Now click on your device and find install driver,go and find the extracted file to install driver.After installing driver download root genius from this linkhttps://mega.nz/#!G4US0aTA!rfkmf4GSUJ75FSpq3_OBzKw58WLlExImjzlHVti5rbM,Install it and open the app.Your device will automaticlly connect to root genius.Now the final step is to click root word,click the green box,wait for 10 minute to complete the rooting process.your phone will reboot.all done.now check your device if its rooted or not by installing root checker app via google play store.
Click to expand...
Click to collapse
Also failed.
I guess it's too difficult to root this new version/update. If only I could downgrade then it might be possible to root.
Johny2k9 said:
Also failed.
I guess it's too difficult to root this new version/update. If only I could downgrade then it might be possible to root.
Click to expand...
Click to collapse
There's no available firmware to downgrade. Bad luck for you.
Røbin said:
There's no available firmware to downgrade. Bad luck for you.
Click to expand...
Click to collapse
Is upgrade impossible without rooting?
Johny2k9 said:
Is upgrade impossible without rooting?
Click to expand...
Click to collapse
You can upgrade or downgrade your android version without rooting but it has to be official firmware. If you want to flash custom rom you'll need custom recovery installed and unlocked bootloader.
Røbin said:
You can upgrade or downgrade your android version without rooting but it has to be official firmware. If you want to flash custom rom you'll need custom recovery installed and unlocked bootloader.
Click to expand...
Click to collapse
I wouldn't mind upgrading. Though what would be the process to get the official firmware?
Johny2k9 said:
I wouldn't mind upgrading. Though what would be the process to get the official firmware?
Click to expand...
Click to collapse
I think you didn't get what I said.You are already using updated android version. You can't update more if your service provider don't give anymore updates.And I also searched very hard to find official firmware for your device but unluckily your phone have very less information in web.So there's no one haven't uploaded any firmware or no discussion available for your device.You can though upgrade your device using custom rom but you need to have root and custom recovery .without root you can't install custom recovery.
Røbin said:
I think you didn't get what I said.You are already using updated android version. You can't update more if your service provider don't give anymore updates.And I also searched very hard to find official firmware for your device but unluckily your phone have very less information in web.So there's no one haven't uploaded any firmware or no discussion available for your device.You can though upgrade your device using custom rom but you need to have root and custom recovery .without root you can't install custom recovery.
Click to expand...
Click to collapse
Hahh... So after combing through various Chinese sites and using my limited knowledge of Chinese, I've got a ROM (previous version before there update), got the appropriate flashing software (CoolPad Download Assistant) and have successfully flashed it after disassembling the phone to get into fastboot.
Good news:
I am Rooted... again. With KingRoot.
Bad news:
The CoolPad has there update in the background. Found where it's stored and deleted. The Phone re-downloads the update.
A restart will probably update this phone making it un-rootable again.
Edit: Deleting the update file before immediately restarting gives an error in the update on restart, so I guess that's a good thing.
For now, I will just operate for now without turning the phone off. Though I do have the necessary files if I have to flash it again.
Rooting is the first requirement you mentioned... what do I need to do next? Download what? Compatible ROM's etc?
Johny2k9 said:
Hahh... So after combing through various Chinese sites and using my limited knowledge of Chinese, I've got a ROM (previous version before there update), got the appropriate flashing software (CoolPad Download Assistant) and have successfully flashed it after disassembling the phone to get into fastboot.
Good news:
I am Rooted... again. With KingRoot.
Bad news:
The CoolPad has there update in the background. Found where it's stored and deleted. The Phone re-downloads the update.
A restart will probably update this phone making it un-rootable again.
Edit: Deleting the update file before immediately restarting gives an error in the update on restart, so I guess that's a good thing.
For now, I will just operate for now without turning the phone off. Though I do have the necessary files if I have to flash it again.
Rooting is the first requirement you mentioned... what do I need to do next? Download what? Compatible ROM's etc?
Click to expand...
Click to collapse
If you have no interest in custom rom and now you can root your device then you don't need to do anything right now.And you are saying new update automatically downloading,just in download setting select "do not auto download"or"update via wifi only"this will prevent from auto downloading update.
Røbin said:
If you have no interest in custom rom and now you can root your device then you don't need to do anything right now.And you are saying new update automatically downloading,just in download setting select "do not auto download"or"update via wifi only"this will prevent from auto downloading update.
Click to expand...
Click to collapse
I disabled the update part, thank you.
I would prefer a custom rom, what options would I have?
Johny2k9 said:
I disabled the update part, thank you.
I would prefer a custom rom, what options would I have?
Click to expand...
Click to collapse
Not sure if there's any custom rom available for your phone You can somehow install custom twrp recovery but the main problem is custom rom availability.But I would suggest you to use xposed instead installing custom ROM.You can customize and control your device using xposed installer.
Røbin said:
Not sure if there's any custom rom available for your phone You can somehow install custom twrp recovery but the main problem is custom rom availability.But I would suggest you to use xposed instead installing custom ROM.You can customize and control your device using xposed installer.
Click to expand...
Click to collapse
Installed Xposed Installer, but the Download section is empty.
I am in China currently, so a lot of things may be blocked. A VPN should fix this, I believe.
What things I should install. Xposed Installer is new to me.
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 .