[Help Thread][Moto E4] Ask Any Question, Noob Friendly (2017)

KevMetal

Senior Member
Nov 11, 2016
1,570
591
0
not sure what you're talking about dude, I never said which version of 88.2 I was installing, but perhaps I made reference to something by mistake. I shall now confirm I flashed the correct version, as only one should work for this device, the sdk25, arm (not64). I'm just coming from KitKat so I'm avoiding all this systemless stuff in the first place since a) it's all new to me and b) it's unecessary since I'm comfortable with fastboot, adb, twrp, etc.

Anyways I tried flashing 88.2 through the xposed installer app, through twrp over 88.1, and after uninstalling xposed, rebooting, and installing fresh in twrp. Still got stuck on the moto/lenovo splash screen.

I'm only running gravitybox, which is claimed to work by many, and does just fine. I just can't update the framework for some reason.
well bro everyone around the e4 thread that failed to flash magisk or xposed failed cos they didn't flash the correct versions , in the correct order or they didn't remove all remnants of other heavy mods ......

remove substratum
remove old xposed AND ALL MODS
get the latest ARM version from official source
install the installer apk ( latest ) give root
reboot recovery
clear cache & dalvik
flash latest ARM framework zip IN RECOVERY
clear cache & dalvik
reboot

ALWAYS WORKS
*since you don't specify or provide ALL info one can only guess what part of the above you are not doing

* you are free to use the modded xposed from Francico but read all his thread including the post by xposed developer advising against that fix

* check my other posts helping other guys who couldn't install xposed to install xposed
( last time it was the wrong version)

* if you are happy with what you managed to achieve up to this point just ignore my post

wasn't it you who had trouble unrooting and asking for info on boot.img etc - i was helpful and gave you all the information you needed to get magisk working . i can only guess what and how much a person knows when i try to help so don't get offended . perhaps you know more than me but you are absentminded today and forgetting something simple you already know

either way bro good luck & see you around
 
  • Like
Reactions: domenci

madbat99

Senior Member
Mar 1, 2014
5,538
3,285
113
you are not flashing the correct xposed . you need to flash xposed sdk 25 ARM OFFICIAL but before flashing install the LATEST XPOSED INSTALLER APP OFFICIAL ...DO NOT INSTALL SYSTEMLESS XPOSED ...if you follow the above you will get latest official xposed . latest xposed works without any modifications ...not all xposed modules support nougat like greenify for example .
Hey bro, greenify beta works in Xposed
https://www.apkmirror.com/apk/oasis...greenify-3-8-5-android-apk-download/download/
 
  • Like
Reactions: KevMetal

mn1968

Senior Member
Nov 7, 2011
540
140
0
Not to ruffle any feathers...but, I had the unofficial Xposed installed on my stock XT1768. Also had Substratum installed. I wanted to update to the official Xposed, so I uninstalled the unofficial version and flashed 88.2....several times. Always wound up in a bootloop...or so I thought. Then for kicks, I just let it sit in the bootloop for 5-10 minutes and it eventually booted up. I now have Official Xposed and I never uninstalled Substratum. For whatever reason though, the official Xposed seems to take forever to load the first boot after flashing. Just a heads up for anyone else.
 
  • Like
Reactions: KevMetal

KevMetal

Senior Member
Nov 11, 2016
1,570
591
0
ooh nice to know ..gonna try it

---------- Post added at 03:04 PM ---------- Previous post was at 02:58 PM ----------

Not to ruffle any feathers...but, I had the unofficial Xposed installed on my stock XT1768. Also had Substratum installed. I wanted to update to the official Xposed, so I uninstalled the unofficial version and flashed 88.2....several times. Always wound up in a bootloop...or so I thought. Then for kicks, I just let it sit in the bootloop for 5-10 minutes and it eventually booted up. I now have Official Xposed and I never uninstalled Substratum. For whatever reason though, the official Xposed seems to take forever to load the first boot after flashing. Just a heads up for anyone else.
true takes long to boot ... i just advise uninstalling substratum not because of any specific conflict with xposed but rather possible conflicts between some xposed modules and some overlays ...you are more than correct in saying it might not be necessary ...certainly try ..if in case you fail try without just in case
 
A

amarc78

Guest
Not to ruffle any feathers...but, I had the unofficial Xposed installed on my stock XT1768. Also had Substratum installed. I wanted to update to the official Xposed, so I uninstalled the unofficial version and flashed 88.2....several times. Always wound up in a bootloop...or so I thought. Then for kicks, I just let it sit in the bootloop for 5-10 minutes and it eventually booted up. I now have Official Xposed and I never uninstalled Substratum. For whatever reason though, the official Xposed seems to take forever to load the first boot after flashing. Just a heads up for anyone else.
This is what I tried to tell people. I was the first one to install it. It worked fine first try, because I was patient and let it finish booting. It took 20-25 mins for me. If it doesn't boot after 30 mins, it probably won't. But people expect things to always boot in a few mins and then claim they don't work and have a bootloop because they didn't wait long enough. Now we have numerous threads and posts with different information about the same thing. This place is toxic. Full of way too much misinformation from too many people who don't really know what they're doing or talking about. I'll probably get another infraction for this now, but other users offensive comments get ignored.
 

KevMetal

Senior Member
Nov 11, 2016
1,570
591
0
well i don't know bout toxic bro . i think xda is good that is why i spend time here ..if you think its toxic be part of the solution not the problem . complaints never solve anything ...

maybe you could do a guide and explain the boot delay ..on other hand i just flashed xposed 5 minutes ago for greenify ( only use for me ) since madbat told me greenify beta now supports nougat and it booted first time in 3 minutes ...so each device could be different

i think people pay more attention to advise from recognized developers and contributors but in the OP it clearly states this is for noobs to ask & OFFER info ...if you see bad info correct it and contribute bro or report bad behaviour

anyways

here is screenshot inviting noobs to contribute in Q&A ( If you don't ask & answer you don't learn )

here is screenshot of xposed .2 active on my device demonstrating it can be flashed and booted

lastly thanks madbat for heads up on greenify
thanks for guys reminding me it can boot with substratum
looking forward to participating more on xda and hopefully in a positive way to make it great for everyone

enjoy the weekend ..I'm off to crack a cold one
 

Attachments

Last edited:
A

amarc78

Guest
well i don't know bout toxic bro . i think xda is good that is why i spend time here ..if you think its toxic be part of the solution not the problem . ...if you see bad info correct it and contribute bro or report bad behavior
Yeah, I tried that. That's how I got my first ever infraction. I reported a post about myself yesterday that was offensive. It's still there, and my report was ignored although it was more offensive and likely to start trouble than what I was infracted for. The same type of post that I'm responding to now. Not trying to be offensive or rude at all.
 

domenci

Senior Member
Sep 14, 2011
162
30
0
well bro everyone around the e4 thread that failed to flash magisk or xposed failed cos they didn't flash the correct versions , in the correct order or they didn't remove all remnants of other heavy mods ......

remove substratum


wasn't it you who had trouble unrooting and asking for info on boot.img etc - i was helpful and gave you all the information you needed to get magisk working . i can only guess what and how much a person knows when i try to help so don't get offended . perhaps you know more than me but you are absentminded today and forgetting something simple you already know

either way bro good luck & see you around
. Thanks for your previous help, but I had to figure out the magisk situation myself, as no one could confirm which stock boot.img I needed to reflash after running the uninstaller zip to remove phh. It wasn't even you who told me there was an uninstaller zip, and the person who did was under the impression I didn't need to flash boot.img, but I did in order for magisk to work. It seems like you didn't follow that whole discussion. Anyways, I read every little thing relating to my problem before I post on here, and I've never come across "substratum" (and definitely haven't installed that on my phone, but perhaps it's part of the stock ROM that needs to be removed that no one mentioned in any of the xposed or rooting threads?) , but I assure you ONCE AGAIN that I followed all the other steps with the correct files. obviously you're not believing me, but perhaps you know of a way to grab a log of the failed boot, so we can figure out what's going on.

---------- Post added at 02:52 PM ---------- Previous post was at 02:40 PM ----------

This is what I tried to tell people. I was the first one to install it. It worked fine first try, because I was patient and let it finish booting. It took 20-25 mins for me. If it doesn't boot after 30 mins, it probably won't. But people expect things to always boot in a few mins and then claim they don't work and have a bootloop because they didn't wait long enough. Now we have numerous threads and posts with different information about the same thing. This place is toxic. Full of way too much misinformation from too many people who don't really know what they're doing or talking about. I'll probably get another infraction for this now, but other users offensive comments get ignored.
Maybe I just didn't wait long enough. With stock and 88.1 my phone boots in under 3 minutes. I waited for at least 5 for 88.2 to boot, uninstalled, put 88.1 on there, and it still booted up in 3 min. Perhaps there's some special sauce in 88.2 that takes exponentially longer to boot? Even though that makes no sense, maybe I'll give it a shot later since I know I followed all the instructions to a T, and tried variations.
 
A

amarc78

Guest
. Thanks for your previous help, but I had to figure out the magisk situation myself, as no one could confirm which stock boot.img I needed to reflash after running the uninstaller zip to remove phh. It wasn't even you who told me there was an uninstaller zip, and the person who did was under the impression I didn't need to flash boot.img, but I did in order for magisk to work. It seems like you didn't follow that whole discussion. Anyways, I read every little thing relating to my problem before I post on here, and I've never come across "substratum" (and definitely haven't installed that on my phone, but perhaps it's part of the stock ROM that needs to be removed that no one mentioned in any of the xposed or rooting threads?) , but I assure you ONCE AGAIN that I followed all the other steps with the correct files. obviously you're not believing me, but perhaps you know of a way to grab a log of the failed boot, so we can figure out what's going on.

---------- Post added at 02:52 PM ---------- Previous post was at 02:40 PM ----------

Maybe I just didn't wait long enough. With stock and 88.1 my phone boots in under 3 minutes. I waited for at least 5 for 88.2 to boot, uninstalled, put 88.1 on there, and it still booted up in 3 min. Perhaps there's some special sauce in 88.2 that takes exponentially longer to boot? Even though that makes no sense, maybe I'll give it a shot later since I know I followed all the instructions to a T, and tried variations.
I first installed the official 88.1 SDK 25 arm and it took about 15 mins to boot. I think I had a substratum theme running at the time also. I updated to 88.2 and it took about 15-20 mins to boot. I also had Magisk 14.3 beta installed. I'm sure the boot time will be longer the more apps you have installed because of how Xposed works. These stock ROMs are also very different and everyone will likely have different results. I think the OEM overlays interfere with things a lot. I had a lot of things disabled with the OEM partition so that might give different results also.
 

domenci

Senior Member
Sep 14, 2011
162
30
0
I first installed the official 88.1 SDK 25 arm and it took about 15 mins to boot. I think I had a substratum theme running at the time also. I updated to 88.2 and it took about 15-20 mins to boot. I also had Magisk 14.3 beta installed. I'm sure the boot time will be longer the more apps you have installed because of how Xposed works. These stock ROMs are also very different and everyone will likely have different results. I think the OEM overlays interfere with things a lot. I had a lot of things disabled with the OEM partition so that might give different results also.
The first time I put 88.1 on my e4 the bootup time was indistinguishable from stock. I just don't get how there can be such a large disparity (3 min vs 15-20) between versions of Xposed. On my older devices I never ran into this.
 
A

amarc78

Guest
The first time I put 88.1 on my e4 the bootup time was indistinguishable from stock. I just don't get how there can be such a large disparity (3 min vs 15-20) between versions of Xposed. On my older devices I never ran into this.
I don't know, but the best way to find out what is going on and possibly get it fixed is to get a log while the device is booting, and properly report the problem and provide a log in the Xposed thread.
 

domenci

Senior Member
Sep 14, 2011
162
30
0
I don't know, but the best way to find out what is going on and possibly get it fixed is to get a log while the device is booting, and properly report the problem and provide a log in the Xposed thread.
Yeah I mentioned that a couple posts ago, I'm not sure how to go about getting that log. I found how to get it once the phone is booted up but can't find a way to view it live or grab it once a boot has failed and I pull the battery
 

KevMetal

Senior Member
Nov 11, 2016
1,570
591
0
Yeah I mentioned that a couple posts ago, I'm not sure how to go about getting that log. I found how to get it once the phone is booted up but can't find a way to view it live or grab it once a boot has failed and I pull the battery
why pull the battery out ? hold power +volume down until you boot to bootloader ..then using the volume keys navigate to recovery and press power to select recovery as boot option

go to advanced tab in custom recovery ..click on logs ...tick include kernel logs ..swipe to copy logs to sd ...download app from Play to read them ...this will copy dmes logs and there might be something about boot in there

humour me and try two things
wipe cache after installing
flash no-dm verity zip
try to boot and allow at leasy 15minutes

are you using magisk 14.3 o 14 ? if 14 update to 14.3 . are you on Qualcomm or mediatek ?
 
  • Like
Reactions: domenci

domenci

Senior Member
Sep 14, 2011
162
30
0
why pull the battery out ? hold power +volume down until you boot to bootloader ..then using the volume keys navigate to recovery and press power to select recovery as boot option

go to advanced tab in custom recovery ..click on logs ...tick include kernel logs ..swipe to copy logs to sd ...download app from Play to read them ...this will copy dmes logs and there might be something about boot in there

humour me and try two things
wipe cache after installing
flash no-dm verity zip
try to boot and allow at leasy 15minutes

are you using magisk 14.3 o 14 ? if 14 update to 14.3 . are on Qualcomm or mediated ?
I tried the keypress while in bootloop but it didn't work, that is why I pulled out the battery. Maybe I didn't do it long enough, I'll try next time I have the same issue.

I did the other things already, but I'm going to give it more time here in a bit.

I'm on the latest magisk. xt1768 (QC). I'm pretty sure if I tried to flash any arm version on a mediatek device it wouldn't work at all and I'd have much different problems that what I'm describing lol
 
Last edited:

KevMetal

Senior Member
Nov 11, 2016
1,570
591
0
just flash no dm-verity after xposed and wait

-im sure you did but just remember to enable usb debugging in developer settings
-im using ARM on mediatek variant...only one that works

mt6737m is using arm cortex A53 architecture
 

Attachments

Last edited:
  • Like
Reactions: domenci

madbat99

Senior Member
Mar 1, 2014
5,538
3,285
113
The first time I put 88.1 on my e4 the bootup time was indistinguishable from stock. I just don't get how there can be such a large disparity (3 min vs 15-20) between versions of Xposed. On my older devices I never ran into this.
Can't compare this Xposed to ones on older phones. Very different.
A lot more is being optimized in 88.2 as opposed to 88.1 (means longer first boot), especially if you have alot of apps installed. Stock has a bunch of apps too, they all have to rebuild caches and optimize. I think the one you have working cuts out many of these " optimizations" which is why it boots faster.
In Android 7.1, apps optimize alot different than they used too. They build caches and optimize depending on usage, and potential usage. Meaning it changes based on usage, Very complex (that's one reason it took rovo so long to release Xposed for it.
Older versions of Android (and Xposed) didn't act that way.
Okay, I've blabbed on enough.


Rovo89's post here explains some of it.
 
Last edited:
  • Like
Reactions: domenci

domenci

Senior Member
Sep 14, 2011
162
30
0
Can't compare this Xposed to ones on older phones. Very different.
A lot more is being optimized in 88.2 as opposed to 88.1 (means longer first boot), especially if you have alot of apps installed. Stock has a bunch of apps too, they all have to rebuild caches and optimize. I think the one you have working cuts out many of these " optimizations" which is why it boots faster.
In Android 7.1, apps optimize alot different than they used too. They build caches and optimize depending on usage, and potential usage. Meaning it changes based on usage, Very complex (that's one reason it took rovo so long to release Xposed for it.
Older versions of Android (and Xposed) didn't act that way.
Okay, I've blabbed on enough.


Rovo89's post here explains some of it.
yeah I think I'm going to give it another go later on this evening and I'll give it 30 min to boot before I call it. Hopefully I just didn't wait long enough!

---------------
Edit

well I'll be ***! Waited just over 10 minutes and it booted up. Guess I just didn't wait long enough before. cheers all
 
Last edited:
  • Like
Reactions: BandzTFM

_izant_

New member
Dec 7, 2015
2
0
0
How can I restore stock firmware on a Verizon e4? A few weeks ago my phone started bootlooping, with no warning signs. Just pulled it out my pocket and it wouldn't fully boot up. I can't seem to get RSD Lite to recognize the phone, used 3 different cords and 4 different USB ports on my laptop. Please help!
 

BandzTFM

Member
Mar 30, 2017
18
3
0
How can I restore stock firmware on a Verizon e4? A few weeks ago my phone started bootlooping, with no warning signs. Just pulled it out my pocket and it wouldn't fully boot up. I can't seem to get RSD Lite to recognize the phone, used 3 different cords and 4 different USB ports on my laptop. Please help!
RSD doesn't work on USB3 so if you have a regular USB port, use that or try on another computer. I just use ADB & Fastboot cmds to restore mine. It's easy and quick once you have the stock ROM in .xml.zip form

---------- Post added at 03:23 PM ---------- Previous post was at 03:22 PM ----------

Hello what the good small DPI for the Moto e
I think 320 is the best smallest