Related
I am new to Rooting. I have never done anything to my device besides install the updates as Verizon makes them available.
Are there any good guides to doing this?
http://forum.xda-developers.com/showthread.php?t=1779810
Droid 4 Utility ICS Only
Sent from my DROID4 using xda app-developers app
dbreezy187 said:
http://forum.xda-developers.com/showthread.php?t=1779810
Droid 4 Utility ICS Only
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Hi!
I'm new and I can't post in the main discussion and I need help about rooting...
I bought my D4 in USA (to use in Europe) and it comes with ICS, Rsd Lite provide this description:
Software Version: 6.7.2-180_DR4-16_M2-37
Flex Version: XSAMASR01VRZNA025.0R
Bootloader Version: 0a74
Btw, I downloaded the Tool, RSD, Drivers.
After drivers and RSD (by my old motorola experience), I successfully connected my phone, with debug on and MTP.
I tried to root with the tool (function 9) and it seems everything fine...
I've got superuser, but it doesn't work properly...so I don't know if the root was ok or not...
How can I check the situation?
Thanks
Download Root Checker from the Play Store.
Sent from my Droid 4 - LiquidSmooth
kwyrt said:
Download Root Checker from the Play Store.
Sent from my Droid 4 - LiquidSmooth
Click to expand...
Click to collapse
Thanks! I got it...I've rooted...and it works also Voodoo OTA Rootkeeper...
about the rom I have is that the official? Once RSD showed me something like "maserati"...but I don"t know...
I just want remove the apps...can I make it manually with a file manager?
squall90x said:
Thanks! I got it...I've rooted...and it works also Voodoo OTA Rootkeeper...
about the rom I have is that the official? Once RSD showed me something like "maserati"...but I don"t know...
I just want remove the apps...can I make it manually with a file manager?
Click to expand...
Click to collapse
If all you have done is root your phone you are still on your stock Motorola ROM. Maserati is just the D4's code name. Now you have the option of installing safestrap recovery and custom ROMs but it sounds like you just want to be able to remove some bloatware apps. You do NOT want to uninstall apps on your stock ROM. If you do you will be unable update to the latest over-the-air updates without flashing the ICS fastboot files. Use an app like Titanium Backup to FREEZE apps.
Sent from my Droid 4 - LiquidSmooth
kwyrt said:
If all you have done is root your phone you are still on your stock Motorola ROM. Maserati is just the D4's code name. Now you have the option of installing safestrap recovery and custom ROMs but it sounds like you just want to be able to remove some bloatware apps. You do NOT want to uninstall apps on your stock ROM. If you do you will be unable update to the latest over-the-air updates without flashing the ICS fastboot files. Use an app like Titanium Backup to FREEZE apps.
Sent from my Droid 4 - LiquidSmooth
Click to expand...
Click to collapse
Thanks again...so I have root permission and Titanium Backup just works perfectly...at least I would like to remove all the apps of Verizon and also unuseful for me (like Amazon, MOG, Netflix...).
At the moment I don't want to install custom ROMs...what is safestrap recovery for?
What does it mean that I will be unable update to the latest over-the-air updates? Can I UNINSTALL the apps with Titanium Backup or should I just FREEZE? SOLVED
Thanks!
squall90x said:
Thanks again...so I have root permission and Titanium Backup just works perfectly...at least I would like to remove all the apps of Verizon and also unuseful for me (like Amazon, MOG, Netflix...).
At the moment I don't want to install custom ROMs...what is safestrap recovery for?
What does it mean that I will be unable update to the latest over-the-air updates? Can I UNINSTALL the apps with Titanium Backup or should I just FREEZE? SOLVED
Thanks!
Click to expand...
Click to collapse
Safestrap recovery is a custom recovery that you can boot into that allows you to install custom ROMs (AOKP, CM10.1, etc.). So if you're not interested in custom ROMs don't worry about it.
What I was referring to when I talked about not being able install the latest OTA updates is that if you change anything about the stock system, such as uninstalling a verizon app that you wouldn't normally be able to uninstall, when the next update comes along, like Jelly Bean, it will fail when trying to install. That is why, in general, you should freeze instead of uninstall.
Sent from my Droid 4 - LiquidSmooth
Hey guys. I got my grouper yesterday, I'm hoping for a warm welcome
The first thing I did when I took it out of the box was fire it up, unlocked and rooted. When I rooted, I flashed SuperSU flashable. I also flashed CWM touch. After that I flashed SmoothROM 4.4, and I was solid. I installed all of my usual apps, then went to do what I call debloating, (Looking for apps I don't use such as voicedialer.apk, and deleting them) using root browser (/system/app). I noticed it wouldn't delete, then tried another app that requires root permissions. Nothing. I got suspicious, then re-downloaded root checker. "Sorry! You're device does not have proper root access!" What happened? Is this just me, or is this a widespread problem with this ROM? I'd like to keep this ROM if possible. Is there a way to re-root my device (more or less)? Thanks, a response or any help would be very much appreciated.
Sent from my Nexus 7 using xda premium
Rom specific questions need to be posted in that rom's thread. Do not start new threads about custom rom issues.
LiquidPlatinum said:
Hey guys. I got my grouper yesterday, I'm hoping for a warm welcome
The first thing I did when I took it out of the box was fire it up, unlocked and rooted. When I rooted, I flashed SuperSU flashable. I also flashed CWM touch. After that I flashed SmoothROM 4.4, and I was solid. I installed all of my usual apps, then went to do what I call debloating, (Looking for apps I don't use such as voicedialer.apk, and deleting them) using root browser (/system/app). I noticed it wouldn't delete, then tried another app that requires root permissions. Nothing. I got suspicious, then re-downloaded root checker. "Sorry! You're device does not have proper root access!" What happened? Is this just me, or is this a widespread problem with this ROM? I'd like to keep this ROM if possible. Is there a way to re-root my device (more or less)? Thanks, a response or any help would be very much appreciated.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I am having same issue
This issue has been addressed; do a Verizon Nexus Forum search.
Uninstall supersu, reboot, then install the market version, not the flash able zip
Sent from my Nexus 7 using xda premium
That fixed my issue
Sent from my HTC Raider X710e using xda app-developers app
I just got this email today, possibly a VZW release of KitKat?
"Hi,
Thanks for joining the Motorola Feedback Network. We are inviting owners of the Droid 4 on Verizon Wireless to participate in an early preview of a new software release, and provide feedback. If you are not currently using a Droid 4, please excuse and ignore this email.
Click this link --*:link removed: to take the enrollment survey if you wish to take part. Note that you must be a member in good standing of the Motorola Owners' Forums to be included. The registration window could close without notice so please respond as quickly as possible.
This is a confidential test under the terms of the Motorola Feedback Network. Do not post any details or information about this on any public sites.
Thanks -- please understand that start times are always fluid. We ask for your patience if you register but don't hear from us right away.
Matt
Motorola Owners’ Forums
Motorola Feedback Network
To unsubscribe from the Motorola Feedback Network, visit your profile on the new Motorola Feedback Network site and click the link titled "Update Contact Information / Motorola Feedback Network Participation Preference." Click "No" under "Motorola Feedback Network" to unsubscribe.
To avoid any additional surveymonkey invitations – and MFN registration invitations -- click this link: :link removed:"
Sent from my XT894 using Tapatalk
First rule of soak tests - Don't talk about soak tests!
So is it Kitkat? :laugh:
I got one of these too. Moto has already stated the D4 is not going to get any more OS updates. This is probably just a bug fix.
Droid 4 - CM11
I don't expect much but I can't remember when a SOAK was done for bug fixes. Every SOAK I've been part of has been an OS numerical update, even if it was just a small one (x.x.1 to x.x.2 or x.1.x to x.2.x, etc).
4.2.x would be nice, 4.3.x even more so. I definitely don't expect 4.4.x.
Most likely it will be only bug fixes....though I'm still surprised a SOAK is being initiated for that.
tcrews said:
I don't expect much but I can't remember when a SOAK was done for bug fixes. Every SOAK I've been part of has been an OS numerical update, even if it was just a small one (x.x.1 to x.x.2 or x.1.x to x.2.x, etc).
4.2.x would be nice, 4.3.x even more so. I definitely don't expect 4.4.x.
Most likely it will be only bug fixes....though I'm still surprised a SOAK is being initiated for that.
Click to expand...
Click to collapse
I'd have to agree. If it is bug fixes I wonder what prompted them to want to do a SOAK test before hand.
Very minor bug fixes. Update goes from version 98.72.18 to 98.72.189. Here's Verizon's pdf on it:
http://support.verizonwireless.com/dam/support/pdf/system_update/droid-4.pdf
grhopper said:
Very minor bug fixes. Update goes from version 98.72.18 to 98.72.189. Here's Verizon's pdf on it:
http://support.verizonwireless.com/dam/support/pdf/system_update/droid-4.pdf
Click to expand...
Click to collapse
Page is unavailable
Sent from my XT894 using Tapatalk
rruleford said:
Page is unavailable
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Worked for me. Try googling 98.72.189. That is how I came across that page. Motorola also had one in the search results, but it took a couple of tries for it to load for me. Below is the highlights from Verizon's pdf. Nothing made me want to install the update yet.
KEY DEVICE ENHANCEMENTS
DROID is a trademark of Lucasfilm Ltd. and its related companies. Used under license. LTE is a trademark of ETSI. Data Usage Applies. © 2013 Verizon Wireless. 1213-G9996
Droid 4 by Motorola
• Connectivity while roaming abroad has been improved
• Data roaming in Canada on GSM networks is now supported
• Security patches have been included
who is going to be the first one trying ... ?
Updated. No noticeable change (outside the previously noted fixes in the change log), slightly faster. Was able to restore root using Voodoo.
Sent from my Nexus 7 using xda app-developers app
IndiaBhai said:
Updated. No noticeable change (outside the previously noted fixes in the change log), slightly faster. Was able to restore root using Voodoo.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
When I saw the security patches in the change log I was worried about restoring root, so I didn't install the update yet. New that I see you have been able to restore, I'll probably run the update today.
IndiaBhai said:
Updated. No noticeable change (outside the previously noted fixes in the change log), slightly faster. Was able to restore root using Voodoo.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What about safestarp still working?
I just had to uninstall and reinstall using the apk.
Sent from my Nexus 7 using xda app-developers app
IndiaBhai said:
Updated. No noticeable change (outside the previously noted fixes in the change log), slightly faster. Was able to restore root using Voodoo.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Can you run through the steps you took to install it?
I've got SafeStrap, and am rooted, and I can't seem to get the update to install.
Cheers,
Steve.
StevePritchard said:
Can you run through the steps you took to install it?
I've got SafeStrap, and am rooted, and I can't seem to get the update to install.
Cheers,
Steve.
Click to expand...
Click to collapse
Hey Steve, here's what I did:
1) Backup SU using Voodoo OTA rootkeeper
2) Disabled any functions that requires superuser (unchecked my tweaks in gravitybox, stopped seeder, etc. I didn't uninstall, just stopped)
3) Disabled and hid SU from the settings menu in SuperSU
4) Temp Unrooted using Voodoo OTA rootkeeper
5) Rebooted
6) Downloaded and installed the update
- Now here's where I ran into a bit of trouble. I had a bunch of apps disabled so I re-enabled Motorola Services, Motorola Accounts, Verizon Sync, and Motocast ID. Not sure which one did it, but that's my little side note
- Also, I had to check the update menu a few times and reboot every now and then b/c the screen would be black. When it shows "Checking for updates" after you've clicked it, then give it a few minutes.
- Installation will take place through stock recovery, not safestrap.
7) Reinstalled SU through Voodoo, re-enabled in SuperSU settings, and re-enabled all the functions I disabled.
8) Uninstalled Safestrap and Reinstalled using Safestrap 3.65 APK
Hope that helps! Let me know if you need any more info.
- Ayush
Sent from my DROID4 using xda app-developers app
IndiaBhai said:
Hey Steve, here's what I did:
1) Backup SU using Voodoo OTA rootkeeper
2) Disabled any functions that requires superuser (unchecked my tweaks in gravitybox, stopped seeder, etc. I didn't uninstall, just stopped)
3) Disabled and hid SU from the settings menu in SuperSU
4) Temp Unrooted using Voodoo OTA rootkeeper
5) Rebooted
6) Downloaded and installed the update
- Now here's where I ran into a bit of trouble. I had a bunch of apps disabled so I re-enabled Motorola Services, Motorola Accounts, Verizon Sync, and Motocast ID. Not sure which one did it, but that's my little side note
- Also, I had to check the update menu a few times and reboot every now and then b/c the screen would be black. When it shows "Checking for updates" after you've clicked it, then give it a few minutes.
- Installation will take place through stock recovery, not safestrap.
7) Reinstalled SU through Voodoo, re-enabled in SuperSU settings, and re-enabled all the functions I disabled.
8) Uninstalled Safestrap and Reinstalled using Safestrap 3.65 APK
Hope that helps! Let me know if you need any more info.
- Ayush
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Hmmm...
I'm a bit confused. When I get to step 4, I'm already unrooted (presumably because I disabled SuperSU), and get the option to "Restore Root" instead.
I unfroze everything I had frozen, and disabled the only service I can think of that requires root privileges (Keyboard manager). I ensured I had a backup of SU with Voodoo OTA Rootkeeper, and then disabled SuperSU from its settings menu (at this point Voodoo didn't give me the opportunity to temp-unroot, but root checker did say I wasn't rooted). I rebooted, and then downloaded the update and set it to install.
It got about 30% in, and I got the exclamation mark red triangle over the android on is back, and then it rebooted to tell me that the update had failed.
I've got another rooted phone with Superuser on it, and using Voodoo on that to temp unroot doesn't allow the update to install either.
Has anybody else managed to install the update on a rooted phone? If so, what steps did you take?
Cheers,
Steve.
has the baseband been udated ?
lucize said:
has the baseband been udated ?
Click to expand...
Click to collapse
Doesn't seem so. Just framework-libraries regarding telephony, the APN list, the kernel and a bunch of other stuff on the system-partition. No changes to the radio-partition. I have just downloaded the OTA and looked into it, not installed it...
So if you are running CM, this update doesn't change anything which would improve GSM/CDMA/LTE on CM.
I'd still be interested if someone manages to get the full image for this version which can be flashed with fastboot.
Regards,
Michael
Installation on rooted stock
FWIW - the way I got it installed was:
1. Using the D4 Utility, I reflashed Jelly Bean WITHOUT wiping, which removed root, but kept my apps and data
2. Went to Settings | About Phone | System Update, and downloaded, and installed the update.
3. I cleared the data on the Smart Actions app, in preparation for the re-rooting.
3. Using the D4 Utility, I rooted using RAZR Blade exploit.
4. I then jumped through some hoops to get the su binary back to my preferred SuperSU (had to fire up SuperSU, give it root access, and then remove the old superuser.apk in the system/app folder).
I hope that helps somebody else.
Cheers,
Steve.
Glad you got it working mate
Sent from my DROID4 using xda app-developers app
I have a VZW DE on 4.4.2, unlocked bootloader, rooted, no custom ROM.
Was wondering if there is any way to hide the system update prompts/notifications as I'd rather wait for a more substantial upgrade (Android L).
Using root explorer I did go to etc/security/ and renamed otacerts.zip to otacerts.zip.bak to no avail. Also, there didn't seem to be anything for me to freeze in TiBu.
Not only is this a marginal upgrade imo, I just don't want to mess with going back to stock recovery, upgrading to 4.4.4, flashing TWRP, re-root, do system tweaks (e.g. replace ugly vzw 4G Icon and bars, but first check to see if someone made one compatible to 4.4.4), research whether wifi tether from xposed module still works on 4.4.4, etc. Just plain don't have the time to do all that at the moment.
Thanks in advance!
I thought I had replied to this exact question yesterday...
use a root capable file explorer, got to /system/priv-apps and rename 3C_OTA.APK
Of course, if your phone has already downloaded the file, navigate to /cache and remove it.
Reboot after making the changes.
that has prevented getting prompted in the past.
I did what Mark said.. renamed the 3c ota apk and also 3c ota odex file and confirm it will stop download and notices. if you just rename the 3c ota apk file alone and not the odex file to, you may get the download and reboot problems.. someone will have to confirm that, I gave a Moto X to my little brother running 4.4 and only renamed the 3c ota apk file and four weeks later he gave it back to me with a cracked screen and said it kept rebooting trying to update but failed because it was rooted. that's when I opened up root file explorer and noticed I did not change the odex file, I only changed the apk file. I'm running a 4.4 rooted and change both files and I never get the updates.
on my brother's new replacement phone running 4.4.2 I have it rooted with towelPie and renamed both files and seems to not be bothering me about the update now. I did let it download the new update at first attempt I went in and deleted the two files and it interrupted the download so I can confirm it will stop the download deleting those two files even when the download has already began
Out of curiosity, why wouldn't you take the update?
Sent from my Dev Edition Moto X
Schaweet said:
Out of curiosity, why wouldn't you take the update?
Click to expand...
Click to collapse
I can say for my two Non-DE Verizon Moto X phones running 4.4.2 and TowelPieRoot that I'm not taking the update for root reasons first and foremost. Until the time when a 4.4.4 root method is developed, if ever, I'll remain on 4.4.2.
I appreciate the suggestions in this thread however because I'm looking to hide these notices myself.
doitinthedirt said:
I did what Mark said.. renamed the 3c ota apk and also 3c ota odex file and confirm it will stop download and notices. if you just rename the 3c ota apk file alone and not the odex file to, you may get the download and reboot problems.. someone will have to confirm that, I gave a Moto X to my little brother running 4.4 and only renamed the 3c ota apk file and four weeks later he gave it back to me with a cracked screen and said it kept rebooting trying to update but failed because it was rooted. that's when I opened up root file explorer and noticed I did not change the odex file, I only changed the apk file. I'm running a 4.4 rooted and change both files and I never get the updates.
on my brother's new replacement phone running 4.4.2 I have it rooted with towelPie and renamed both files and seems to not be bothering me about the update now. I did let it download the new update at first attempt I went in and deleted the two files and it interrupted the download so I can confirm it will stop the download deleting those two files even when the download has already began
Click to expand...
Click to collapse
Thanks, all! I went ahead and renamed the odex as well. Rebooted and good to go!
Schaweet said:
Out of curiosity, why wouldn't you take the update?
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Would have to do a whole mess of stuff, like:
disable xposed frameworks and gravity box, defrost certain system apps and vzw bloat from TiBu probably, re-install android sdk (since I had formatted PC since 4.4.2), flash stock recovery, take the OTA, reflash custom recovery, re-enable xposed and gravity box (only gravity box has since split from one module to an ICS and KK version and I still have the old version), then upgrade and tweak gravity box settings, get rid of ugly VZW 4GLTE icon with stock/nexus version (but first see if someone made one that works on 4.4.4), research whether the xposed wifi-tether module works on 4.4.4, and maybe one or two other things...
all that takes TIME which I don't have a whole lot of at the moment... and all that for the ability to pause video recording and a get a dialer that has a white background instead of black? and supposed tweaks under the hood like battery and performance, all unconfirmed? yeah, personally, I'd rather wait.
Fair enough. So you know if you flash system.img once you reinstall xposed all your gravity box settings are still there.
Sent from my Dev Edition Moto X
jamespark said:
Would have to do a whole mess of stuff, like:
disable xposed frameworks and gravity box, defrost certain system apps and vzw bloat from TiBu probably, re-install android sdk (since I had formatted PC since 4.4.2), flash stock recovery, take the OTA, reflash custom recovery, re-enable xposed and gravity box (only gravity box has since split from one module to an ICS and KK version and I still have the old version), then upgrade and tweak gravity box settings, get rid of ugly VZW 4GLTE icon with stock/nexus version (but first see if someone made one that works on 4.4.4), research whether the xposed wifi-tether module works on 4.4.4, and maybe one or two other things...
all that takes TIME which I don't have a whole lot of at the moment... and all that for the ability to pause video recording and a get a dialer that has a white background instead of black? and supposed tweaks under the hood like battery and performance, all unconfirmed? yeah, personally, I'd rather wait.
Click to expand...
Click to collapse
Schaweet said:
Fair enough. So you know if you flash system.img once you reinstall xposed all your gravity box settings are still there.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Why not just use the FULL FXZ? http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you flash the FXZ, (since it is a "Keep Data" FXZ), you don't need to take the OTA. You don't need to disable Xposed. You don't need to disable any modules - or subsequently set them back up. You don't need to flash stock recovery. You don't need to worry about any modifications you have made to /system.... And you DON'T NEED THE OTA!
And just like @Schaweet has advised -- once you re-flash TWRP, re-root, and re-install Xposed Framework, all of your Xposed modules and their respective settings are already set the way you had them....
It turns this in to about a 10-15 minute process from start to finish. WAYYYY Easier. I don't get it...
EDIT: I do see that you have the "Old" gravitybox installed, so this might require setting up the new version. But everything else stated is completely relevant.
I froze MotorolaOTA 1.0
samwathegreat said:
Why not just use the FULL FXZ? http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you flash the FXZ, (since it is a "Keep Data" FXZ), you don't need to take the OTA. You don't need to disable Xposed. You don't need to disable any modules - or subsequently set them back up. You don't need to flash stock recovery. You don't need to worry about any modifications you have made to /system.... And you DON'T NEED THE OTA!
And just like @Schaweet has advised -- once you re-flash TWRP, re-root, and re-install Xposed Framework, all of your Xposed modules and their respective settings are already set the way you had them....
It turns this in to about a 10-15 minute process from start to finish. WAYYYY Easier. I don't get it...
Click to expand...
Click to collapse
HUGE. I haven't been following any forums for several months and was not aware of this FXZ. Great to know, thanks!
Mayze23 said:
I froze MotorolaOTA 1.0
Click to expand...
Click to collapse
same
A thread already exists for this exact thing here. Please post question in Q&A in future and search before creating new threads.
Thread closed
I installed Xposed, and a module that thought (knock on) I think it was not compatible, to restart the device, it gives boot loop, clean the dalvik and it starts, if I reboot again, boot loop return. Any solution? :crying: my phone is a xperia z2
Starxd said:
I installed Xposed, and a module that thought (knock on) I think it was not compatible, to restart the device, it gives boot loop, clean the dalvik and it starts, if I reboot again, boot loop return. Any solution? :crying: my phone is a xperia z2
Click to expand...
Click to collapse
You have to uninstall the module to fix it. If you're on Kitkat then I think there should be a zip in Android/data/com.somexposedstuff and somewhere in there. Idk about lollipop
Sent from my Boost Mobile Moto G (xt1031) with Tapatalk. Running Android 5.0.2 stock soak test with root
Its a Lollipop
Starxd said:
Its a Lollipop
Click to expand...
Click to collapse
I don't know how to disable in on lollipop (even though i'm using it). According to this thread: http://forum.xda-developers.com/xpo...-framework-t3039371/post59082375#post59082375 you can uninstall iy withouth wiping data.
Sent from my Boost Mobile Moto G (xt1031) with Tapatalk. Running Android 5.0.2 stock soak test with root
dirty_smurf45 said:
I don't know how to disable in on lollipop (even though i'm using it). According to this thread: http://forum.xda-developers.com/xpo...-framework-t3039371/post59082375#post59082375 you can uninstall iy withouth wiping data.
Sent from my Boost Mobile Moto G (xt1031) with Tapatalk. Running Android 5.0.2 stock soak test with root
Click to expand...
Click to collapse
I did the following: with Root Explorer googled the word "Xposed" appeared some files, deleted all, restarted, same thing
Starxd said:
I did the following: with Root Explorer googled the word "Xposed" appeared some files, deleted all, restarted, same thing
Click to expand...
Click to collapse
You're on your bootlooped phone? If so, just disable and uninstall the module that caused the bootloop. I really don't know how to do this on lolliop. Maybe posting in Xposed General? I t would be the appropriate location for this thread.
Starxd said:
I did the following: with Root Explorer googled the word "Xposed" appeared some files, deleted all, restarted, same thing
Click to expand...
Click to collapse
Sent from my Boost Mobile Moto G (xt1031) with Tapatalk. Running Android 5.0.2 stock soak test with root
dirty_smurf45 said:
You're on your bootlooped phone? If so, just disable and uninstall the module that caused the bootloop. I really don't know how to do this on lolliop. Maybe posting in Xposed General? I t would be the appropriate location for this thread.
Sent from my Boost Mobile Moto G (xt1031) with Tapatalk. Running Android 5.0.2 stock soak test with root
Click to expand...
Click to collapse
I had only excluded files containing "Xposed" in the name with Root Explorer, but remained the files described in this post: http://forum.xda-developers.com/showpost.php?p=58964632&postcount=2258
Made as described, restarted, he updated one last time and went back to normal. Thanks for your help. : D
No problem. Remember to uninstall the incompatible application.
Sent from my Boost Mobile Moto G (xt1031) with Tapatalk. Running Android 5.0.2 stock soak test with root