Related
Hi someone with an account on 4dpa with 30 posts could please download this rom and share it here? I don't know Russian so it's impossible for me to write 30 posts.
I have a Zenfone Go (Z00VD) and the stock ROM it's terrible (crash in the camera, 1 Gigabyte of app space already full....)
In case you can't, could you provide an alternative ROM with as less bugs as possible?
Thank you
Original Thread 4pda
Translated Google
Guess we're on the same boat buddy. Have you tried the other ROMs on their forum like the nougat ones? They seem nice.
I personally prefer to use the RR 5.5.9 lollipop rom provided by 4pda since for some reason the nougat and marshmallow roms on their site just give me bootloops. It may be different for you though.
JustAnormalGuy said:
Guess we're on the same boat buddy. Have you tried the other ROMs on their forum like the nougat ones? They seem nice.
I personally prefer to use the RR 5.5.9 lollipop rom provided by 4pda since for some reason the nougat and marshmallow roms on their site just give me bootloops. It may be different for you though.
Click to expand...
Click to collapse
Hi, not yet, it's not my phone so I'm searching a stable ROM. I saw the nougat thread here but it's not very clear what works and what not, there seems to be a nougat rom on 4dpa which should work well except the videocamera with the stock app, but the Oreo one seems almost bug free although more complex to install. Unfortunately I can't access it.
Hello,
From what I can tell, both Oreo and Nougat ROMs were unstable and/or sluggish for me, so I'd recommend to stick to Marshmallow based ROMs(for now). My personal preference is ResRemix 5.7.4, but if you decide to try any of them, keep in mind that ROMs with kernel 3.18.19(as far as I've seen most of ROMs in that thread) all have these two issues that I was able to find so far:
Notification LED doesn't work
Bluetooth audio doesn't work either
Other than that, the ROM is super-stable and somehow better than 5.1.1 ROMs from official dev thread there.
And for JustAnormalGuy, bootloops in later ROMs seem to happen because of unwiped internal storage(basicly needs entire /data partition wiped somewhy). Try marking the 'Internal SD' option when wiping partitions for ROM installing.
Good luck!
aurismat said:
Hello,
From what I can tell, both Oreo and Nougat ROMs were unstable and/or sluggish for me, so I'd recommend to stick to Marshmallow based ROMs(for now). My personal preference is ResRemix 5.7.4, but if you decide to try any of them, keep in mind that ROMs with kernel 3.18.19(as far as I've seen most of ROMs in that thread) all have these two issues that I was able to find so far:
Notification LED doesn't work
Bluetooth audio doesn't work either
Other than that, the ROM is super-stable and somehow better than 5.1.1 ROMs from official dev thread there.
And for JustAnormalGuy, bootloops in later ROMs seem to happen because of unwiped internal storage(basicly needs entire /data partition wiped somewhy). Try marking the 'Internal SD' option when wiping partitions for ROM installing.
Good luck!
Click to expand...
Click to collapse
Those 2 bugs are not a deal breaker for me, would you mind linking to the ResRemix 5.7.4 rom that you used?
Sure, buut since I can't post links(thanks XDA for 10 post restriction, love ya!), I'll have to send one another way.
PM me your Discord handle(if you have one) or something else. I should be able to send you the link there.
aurismat, and what version of twrp do you use ?
I use TWRP 3.0 by Jemmini. It's been a *long* time since I installed it though, so if you have something different, I'm afraid I won't be of much help unless I'll be able to pull my recovery .img file.
Actually, i use the same version. Problem is most probably my method of root. The common method of rooting for our device didn't include any flashing with sp flash tool. But for my situation, my bootloader is locked even after downgrading. So i did the other method (also found on the forum) in which includes flashing.
Hmm, it *may* be the root method, may be also the locked bootloader.
If I recall right(and this might be THE common way), I used the fastboot method from XDA, and I knew it'd work cause I rooted more phones that way. I remember downgrading the stock ROM down to version 39(i think that one still had the bootloader check in dev options) and then trying to unlock the bootloader and obviously go through flashing the recovery image.
Dunno what might be the issue with your way of flashing, though. AFAIK might be anything from leftover files to bootloader giving the finger.
@aurismat i think the problem might be that i used the "format all + download" option on sp flash tool. Does that affect the phone in any way that deprives my phone from using 6.0 - 7.0 roms? (Besides the "null" imei effect)
@JustAnormalGuy I don't think it should be a problem, because the ROM .zips install their own stuff to the partitions AFAIK, so even if Flashtool wipes everything, it should still be fine. Try doing one of them ROMs(previously said ResRemix worked for me), but remember to wipe the Internal Storage partition if you can.
Oh and remember to take a backup of your current ROM, should it bootloop again at least you won't have to do the hassle of reinstalling everything back(learned that the hard eay haha).
EDIT: was it just Nougat ROMs that you were trying or was it both Nougat and Marshmallow? Not sure what might be the cause, but the ROMs developed under the same kernel from ska-vova in 4PDA worked for me. Just a thought.
well actually i already tried various roms from Marshmallow to Nougat all of which gave me bootloops. I've already followed the steps of installation as written. However, i tried once installing a Marshmallow rom from the facebook group named "ASUS Zenfone Go Indonesia" and it surpisingly worked for me (numerous bugs present however), as well as most of the marshmallow (and only marshamallow roms) on their group.
The thing is I also might think one of the reasons why i get the bootloops in the roms from the 4pda forum is the kernel used in them. (just speculation) Should it be correct to assume that ?
As I recall:
Working rom shows "kernel version > [email protected]"
Not working rom - "kernel version > [email protected]"
Hmm, I'm using [email protected] kernel version 3.18.19.
All the ROMs there seem to be by mosly nik-kst's kernel. ska-vova seems to just build ROMs with the kernel.
Besides, take note from the working ROM - it's also from 4PDA.
Only thing I can speculate is that your device is somewhat different(maybe different hardware, not sure) and hence why it gives you BLs.
Dunno, this case is a tough cookie to be honest - only thing I can recommend at this point is to flash literally EVERYTHING back to stock and try using fastboot method to get recovery and root back.
Hey @Darkorn,
Over the span of a few days, I've tried installing 4PDA's Oreo ROM.
It took me a good couple of headaches to make out what translated Russian meant in the instructions, but I've managed to repartition the entire device to the guide.
Seems to work properly so far, hell even Bluetooth and Notification LED issues from older ROMs seem to be fixed!
Though one thing that annoys me *personally* is that it's impossible to install SuperSU, so you're stuck with Magisk. It's not the end of the world, though, as long as you don't care about SafetyNet's BS.
Oh and @JustAnormalGuy, try repartitioning your device according to the Oreo instructions in 4PDA, that might be the solution for ya.
If I ever get up to 10 posts I'll ask those guys permission to let me post the tutorial here with all the links(hopefully).
Until then, good luck to both of ya!
aurismat said:
Hey @Darkorn,
Over the span of a few days, I've tried installing 4PDA's Oreo ROM.
It took me a good couple of headaches to make out what translated Russian meant in the instructions, but I've managed to repartition the entire device to the guide.
Seems to work properly so far, hell even Bluetooth and Notification LED issues from older ROMs seem to be fixed!
Though one thing that annoys me *personally* is that it's impossible to install SuperSU, so you're stuck with Magisk. It's not the end of the world, though, as long as you don't care about SafetyNet's BS.
Oh and @JustAnormalGuy, try repartitioning your device according to the Oreo instructions in 4PDA, that might be the solution for ya.
If I ever get up to 10 posts I'll ask those guys permission to let me post the tutorial here with all the links(hopefully).
Until then, good luck to both of ya!
Click to expand...
Click to collapse
Nice! Resurrection Remix is working too well to bother, but who knows in a few months!
That would be great man, thanks !!
Hi there. I have the UK varient which is not the same as the us version. I'm looking for info regarding root and custom roms. All info I can find points toward the us (James) varient.
Any info or links greatly appreciated
ok so update, found this thread but not sure if the information is correct, thoughts or experiences please
https://forum.xda-developers.com/moto-e5/how-to/moto-e5-xt1920-15-pettyl-unlock-t3859586
mac_d4di said:
ok so update, found this thread but not sure if the information is correct, thoughts or experiences please
https://forum.xda-developers.com/moto-e5/how-to/moto-e5-xt1920-15-pettyl-unlock-t3859586
Click to expand...
Click to collapse
That's my thread and yes the information is correct.
If you are not sure yourself that the information I have posted is correct, then I suggest you stop thinking about rooting your E5 or flashing custom ROMs.
You have to remember no one has tested the rooting/flashing procedures on PETTYL.
Everything that's listed here on XDA is designed for James/Nora/Hanna devices so no one has tested anything on our devices as it's newer and not many have it.
All the GSIs (custom ROMs) are only listed as working on the James/Nora/Hanna devices, there is currently no support offered for PETTYL, although technically they should work.
The devs of those other devices and the resources for them claim everything should work on our E5 as its treble compatible, but unfortunately that's not quite correct.
If you are really not sure about anything, or don't know if information is correct, you will have problems.
Im not being mean.....I really don't want anyone else to have the problems I have had and really wouldn't advise anyone to go through the process as it's fraught with issues, bad explanations and lacking important information.
Some files are incorrect for our device and some listed procedures for the other devices do not work on our E5.
BTW-my device is an E5 play XT1920-15 PETTYL SIM unlocked purchased from Argos.
Here's a list of the issue I found, it might be different for someone else as two people are saying they successfully rooted their PETTYL, and I couldn't.......
1. I had no issues unlocking the bootloader.
2. There are two versions of TWRP posted on XDA for PETTYL, but neither worked for me.
I used the James version.
3. I could not root my device.
Magisk installed but I could not get v17.3 or v17.2 to flash.
V17.1 did flash but magisk manager showed device not rooted and magisk not installed.
4. Flashing any GSI (Oreo or Pie) causes problems to the system sounds, ringtones, notification tones and music which is totally distorted and very poor quality.
The camera has very poor quality as well.
5. Lineage OS 15.1 is the GO version, you also should flash lineage before flashing other GSIs as you can't flash most GSis over stock.
6. You can use the full Google apps on a couple of android 9 gsis which makes your device a normal android, not an android Go device, but I would recommend not to bother with Android 9.0 GSis for this device as they are very buggy and very slow, and they use three times more battery than android 8.1 Go.
Also, live wallpaper and notification access still don't work on android 9.
Just remember as well the US E5 is much more powerful than our E5, and I assume thats why android 9 runs so crap on our E5.
7. You have a very complicated process to get your Google account working on any GSI, if you do it wrong, you will not be able to use your Google account at all and will get spammed with never ending notification from Google of using an "uncertified device"
8. If you run into problems and decided to return to stock, you cannot download the "retail_GB" stock firmware (SIM unlocked) for PETTYL unless you pay for it....the EE and Tesco SIM locked firmware is free to download, but neither work on the SIM unlocked version if you use non EE or non Tesco SIM cards.
9. Someone has posted a twrp back up of rooted stick for PETTYL.
It did not boot on my device and just kept boot looping.
That could have been a twrp issue and nothing to do with the shared back up - I couldn't get back into a gsi or stock to test it.
My post is warning to other PETTYL users- with my own experience.
What you choose to do is up to you but I really would not bother tampering with it, leave it be.
Stock android Go 8.1 is way better than anything else that's currently available for PETTYL right now, every gsi I tried had an issue of some description that affected performance so badly they were practically unusable.
Even though I'm back on stock now I still have sound issues, and many graphic glitches that makes my screen flash and glitch out randomly.
I'm sorry it's such a long reply, I wanted to give you as much information as possible so you have some idea of what's involved for our device., And let's just hope the situation for our device will get better soon.
Thanks for your detailed reply, I only asked if this was correct as I was aware of the differences between models etc.
I wouldnt say im new to rooting cfw etc, I have been flashing phones since 2002 lol.
But I dont want to brick this device as its currently my only phone, so I will wait and see if the situation improves in the future.
Its not a bad phone as it is you get quite a lot of phone for £65 nowadays.
Oh and im using simlocked tesco model so free to download, I find it stupid that you have to pay for stock firmware its beyond belief
mac_d4di said:
Thanks for your detailed reply, I only asked if this was correct as I was aware of the differences between models etc.
I wouldnt say im new to rooting cfw etc, I have been flashing phones since 2002 lol.
But I dont want to brick this device as its currently my only phone, so I will wait and see if the situation improves in the future.
Its not a bad phone as it is you get quite a lot of phone for £65 nowadays.
Oh and im using simlocked tesco model so free to download, I find it stupid that you have to pay for stock firmware its beyond belief
Click to expand...
Click to collapse
Just like you, I've been rooting and flashing phones since like forever, and this device is the first I've ever had issues with.
It's entirety possible that as I'm a "noob" to flashing system images and fastboot flashing as apposed to flashing "ROMs" I may have messed up the procedures or made mistakes.
But not to be outdone, I have just before typing this reply tried again to root my E5 and flash a GSI, and again the process failed for me.
I could not boot into lineage OS 15.1 due to a "decryption error" and also couldn't get twrp to flash anything.
I've read now my issues are down to the DM Verity kernel which seems to be causing a lot of confusion amongst users and It now seems the process to remove forced encryption is what's causing all my issues.
I don't understand the process if I'm honest (it's an age thing lol) and worse, there is a lot of conflicting information, as a few people are saying the DM Verity process isn't necessary!!!
So unfortunately I've given up completely for now and stand by my original advice.
It's best to leave this particular device well alone until we have a proper procedure and tutorial in place for our own devices rather than trying to follow procedures for the US version.
I'm jealous though you only paid £65, as I paid £79.99, but I still think this Moto E is better than the Nokia 3 it replaced.
If any one can send me any issues they have with pettyl xt1920-15 rooting/twrp/etc I will try to test everything I can and see what works don't expect anything till January cause got college till the 23 and no time now
plscotland said:
If any one can send me any issues they have with pettyl xt1920-15 rooting/twrp/etc I will try to test everything I can and see what works don't expect anything till January cause got college till the 23 and no time now
Click to expand...
Click to collapse
That's very generous of you.
Like you, I don't get much time (due to work) but I have two weeks off from 21/12 and can supply as much information as you want.
I would like root if it's possible.
If some can check this twrp in fast boot by booting it and tell me dose it work on thier phone i be thankfull https://github.com/TwrpBuilderTests...s/tag/TWRP-3.2.3-TwrpBuilder-2018-10-28_04-33
plscotland said:
If some can check this twrp in fast boot by booting it and tell me dose it work on thier phone i be thankfull https://github.com/TwrpBuilderTests...s/tag/TWRP-3.2.3-TwrpBuilder-2018-10-28_04-33
Click to expand...
Click to collapse
I have a "working" 3.2.3 version for PETTYL but I'm not sure it's the version you linked
The one I have "works" in that it boots to TWRP fine from fastboot but obviously it doesn't flash.
I can't flash GSIs through that version, where they do flash no problems through fastboot......
Finally, I can flash magisk through that as even though magisk flashes successfully, magisk manager shows magisk is not installed and asks to flash it again.
@plscotland
TWRP - won't flash to recovery partition.
Cannot mount vendor to flash Fstab
Magisk flashes but magisk manager shows not installed.
I tried the twrp I sent you and the James version.
Lineage - I can successfully flash and boot lineage over stock (Phhusson version) but I have issues with "device not certified by Google" and get spammed by constant notification from Google
Cannot use for daily driver due to no nav bar orfind any settings to enable nav bar.
Descendants 1.0.5 - I have successfully flashed and booted this "rom" and used it but the sound from system ringtones and notification tones is awful and distorted
Lots of graphical glitches and system UI has stopped errors
Pixel experience - cannot flash - error whilst flashing that system IMG is bigger than target.
If I wipe data, it just bootloops and won't go past splash screen.
Resurrection remix - cannot boot
Bootleggers 3.0 - cannot boot
Hope some of this information helps you.
XT1920 - 15 retail GB firmware (SIM unlocked) stock android 8.1 go currently
bubba1601 said:
@plscotland
TWRP - won't flash to recovery partition.
Cannot mount vendor to flash Fstab
Magisk flashes but magisk manager shows not installed.
I tried the twrp I sent you and the James version.
Lineage - I can successfully flash and boot lineage over stock (Phhusson version) but I have issues with "device not certified by Google" and get spammed by constant notification from Google
Cannot use for daily driver due to no nav bar orfind any settings to enable nav bar.
Descendants 1.0.5 - I have successfully flashed and booted this "rom" and used it but the sound from system ringtones and notification tones is awful and distorted
Lots of graphical glitches and system UI has stopped errors
Pixel experience - cannot flash - error whilst flashing that system IMG is bigger than target.
If I wipe data, it just bootloops and won't go past splash screen.
Resurrection remix - cannot boot
Bootleggers 3.0 - cannot boot
Hope some of this information helps you.
XT1920 - 15 retail GB firmware (SIM unlocked) stock android 8.1 go currently
Click to expand...
Click to collapse
Thanks I check and send u how to boot resurrection remix later cause there are extra steps for it to work and fstab also has to be done in another way once IM off work I do a guide for it /Info helped a lot
plscotland said:
Thanks I check and send u how to boot resurrection remix later cause there are extra steps for it to work and fstab also has to be done in another way once IM off work I do a guide for it /Info helped a lot
Click to expand...
Click to collapse
Great, thanks
Qestion do u just want working magisek root on pettyl ?
There 2 ways
One download magisek manager
Get a twrp buckup of your boot image
Go to magisek manager choose patch boot image and choose your twrp buckup boot image (turn off compression of buckup when taking it ) after it finishes go find the patched boot image it should be in downloads or magisek folder can't remember then go to twrp and flash the patched boot image
/
Second way is to add the fstab or whater its called skip the adb mount part and only do the adb push part (look in tread for exact) https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323 then flash the magisek 18.0 tell me did it work after. here the twrp that should work for every ones pettyl [ https://drive.google.com/file/d/1VsZRGkBujHay02a1M14eJM87H_RHFE9J/view?usp=drivesdk ] !Im not responsible if u brick your phone
!!try to boot twrp before u flash do fastboot boot (twrp image just drag the file to cmd to avoid path erors )
plscotland said:
Qestion do u just want working magisek root on pettyl ?
There 2 ways
One download magisek manager
Get a twrp buckup of your boot image
Go to magisek manager choose patch boot image and choose your twrp buckup boot image (turn off compression of buckup when taking it ) after it finishes go find the patched boot image it should be in downloads or magisek folder can't remember then go to twrp and flash the patched boot image
/
Second way is to add the fstab or whater its called skip the adb mount part and only do the adb push part (look in tread for exact) https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323 then flash the magisek 18.0 tell me did it work after. here the twrp that should work for every ones pettyl [ https://drive.google.com/file/d/1VsZRGkBujHay02a1M14eJM87H_RHFE9J/view?usp=drivesdk ] !Im not responsible if u brick your phone
!!try to boot twrp before u flash do fastboot boot (twrp image just drag the file to cmd to avoid path erors )
Click to expand...
Click to collapse
Yeah, Ive been skipping the mount vendor and pushing Fstab via ADB whilst in twrp.
I'll give this twrp a whirl later this evening when my kids laptop is available
I've bricked my E5 and cannot get past "decryption unsuccessful."
Stock/los15/any other gsi I tried.
Reflashed stick but getting errors flashing gpt.partition.
Everything else then shows errors after each command.
Twrp- i followed your 1st step with a magisk altered boot image.
Tried second step and that failed.
I had to combine both steps into one and twrp then booted and flashed successfully to the recovery partition.
Adb pushed fstab before flashing twrp to recovery but once rebooted to stock I got "decryption unsuccessful" error and got into a bootloop.
Reflashed stock then los15.1 but same again.
Reflashed stock but gpt partition and system sparsechunk.2, 3 and 4 give errors.
Cannot flash stock or gsi currently or reboot to recovery, just keeps going back to fastboot.
bubba1601 said:
I've bricked my E5 and cannot get past "decryption unsuccessful."
Stock/los15/any other gsi I tried.
Reflashed stick but getting errors flashing gpt.partition.
Everything else then shows errors after each command.
Twrp- i followed your 1st step with a magisk altered boot image.
Tried second step and that failed.
I had to combine both steps into one and twrp then booted and flashed successfully to the recovery partition.
Adb pushed fstab before flashing twrp to recovery but once rebooted to stock I got "decryption unsuccessful" error and got into a bootloop.
Reflashed stock then los15.1 but same again.
Reflashed stock but gpt partition and system sparsechunk.2, 3 and 4 give errors.
Cannot flash stock or gsi currently or reboot to recovery, just keeps going back to fastboot.
Click to expand...
Click to collapse
in fastboot enter (use cmd powershell gives erorrs) fastboot -w
And then try rebooting it can take a while and tell me did it fix the problem
Recuperación TWRP 3.3.1-0-Pettyl
Hola buen día soy de Guadalajara México
A mí sí me funcionó está recuperación para rotear con magisk e instalar un mood de píxel.
La instalación de TWRP3.3.1-0-PETTYL Lo hice gracias a la aplicación Root essentials en el apartado flasher flasheando la imagen de la recuperación y ya dentro de la recuperación hice una copia de seguridad e instale magisk
Mi dispositivo es el Moto e5 play go pettyl XT1920-18
Heeeeeelp
(First Sorry for my bad english I'm a Brazilian boy with 17 years old only lmfao)Guys, I have only this little piece of s**** as my phone
#1 and this is not useable, it stop The apps constantely and freezes The system on simple apps (like play music and YouTube)... So I want to leave this cellphone in The trash can and walk away, but I cant make this because i have only this "bombphone"... Anywere can make an downgrade to Android 6.1 or 7.1 to this phone? Seriously I cant live with this phone in this situation. thanks and good night from Brazil
João klebão (supahjohn64) said:
(First Sorry for my bad english I'm a Brazilian boy with 17 years old only lmfao)Guys, I have only this little piece of s**** as my phone
#1 and this is not useable, it stop The apps constantely and freezes The system on simple apps (like play music and YouTube)... So I want to leave this cellphone in The trash can and walk away, but I cant make this because i have only this "bombphone"... Anywere can make an downgrade to Android 6.1 or 7.1 to this phone? Seriously I cant live with this phone in this situation. thanks and good night from Brazil
Click to expand...
Click to collapse
Unfortunately you can't downgrade android versions to 6 or 7, there's no system image / ROM on a lower android version for that device - but what you can do it's flash another GSi (ROM) to give you some usage back.
I also had the the XT1920 pettyl and android go is just awful, so I flashed several different roms to try.
The ones I got to work are
PHHussons lineage 15 (android Oreo)
ASOP 9 (android pie)
Pixel experience (pie)
Out of those lineage was the most stable.
You must remember pettyl only has 1gb ram, and does struggle with android 9 pie - but it does work without too many issues.
You got to learn a whole new process of unlocking the bootloader, flashing a custom recovery, disabling forced encryption and flashing a new ROM.
There are plenty of posts about roms for the E5 play in the threads here, I suggest you take a long read and don't try anything until you feel confident enough to begin because the process to flash roms on pettyl isn't very easy and is quite complex and complicated for a new inexperienced user.
It's quite easy to try that and completely mess up your device so it's unusable.
So, you MUST proceed with extreme caution, don't rush into anything without reading everything ten times, having a coffee and then reading it again another ten times.
Many users have tried to rush this process and then come here crying their phones don't work anymore - this happens because they've tried to rush the process, missed out steps and not read instructions properly........
Not being mean, but it happens all the time.
Edit
If you don't feel confident enough to flash a ROM (and no one will blame you if you don't) unfortunately all you can do is change the way you use your device.
I never noticed any music or you tube video freezing on my pettyl but how I used my device and how you use yours are probably very different.
You can't put lots of apps on android go devices, it doesn't like lots of apps.
You can disable most of the system / Google apps like playstore, Google play music and YouTube and install open source alternatives.
(For instance one plus music, you tube vanced and aurora store to name just three - just Google "disable system apps" or "replace Google apps")
I also tried a couple of launchers, and Librechair go edition or the android Go customised pixel launcher does make quite a significant difference to performance, depending on how much system stuff you disable and how many replacement apps you install.
Edit
I don't have my pettyl any longer so unfortunately that's the only help and advice I can offer you at this time.
Sorry.
bubba1601 said:
Unfortunately you can't downgrade android versions to 6 or 7, there's no system image / ROM on a lower android version for that device - but what you can do it's flash another GSi (ROM) to give you some usage back.
I also had the the XT1920 pettyl and android go is just awful, so I flashed several different roms to try.
The ones I got to work are
PHHussons lineage 15 (android Oreo)
ASOP 9 (android pie)
Pixel experience (pie)
Out of those lineage was the most stable.
You must remember pettyl only has 1gb ram, and does struggle with android 9 pie - but it does work without too many issues.
You got to learn a whole new process of unlocking the bootloader, flashing a custom recovery, disabling forced encryption and flashing a new ROM.
There are plenty of posts about roms for the E5 play in the threads here, I suggest you take a long read and don't try anything until you feel confident enough to begin because the process to flash roms on pettyl isn't very easy and is quite complex and complicated for a new inexperienced user.
It's quite easy to try that and completely mess up your device so it's unusable.
So, you MUST proceed with extreme caution, don't rush into anything without reading everything ten times, having a coffee and then reading it again another ten times.
Many users have tried to rush this process and then come here crying their phones don't work anymore - this happens because they've tried to rush the process, missed out steps and not read instructions properly........
Not being mean, but it happens all the time.
Edit
If you don't feel confident enough to flash a ROM (and no one will blame you if you don't) unfortunately all you can do is change the way you use your device.
I never noticed any music or you tube video freezing on my pettyl but how I used my device and how you use yours are probably very different.
You can't put lots of apps on android go devices, it doesn't like lots of apps.
You can disable most of the system / Google apps like playstore, Google play music and YouTube and install open source alternatives.
(For instance one plus music, you tube vanced and aurora store to name just three - just Google "disable system apps" or "replace Google apps")
I also tried a couple of launchers, and Librechair go edition or the android Go customised pixel launcher does make quite a significant difference to performance, depending on how much system stuff you disable and how many replacement apps you install.
Edit
I don't have my pettyl any longer so unfortunately that's the only help and advice I can offer you at this time.
Sorry.
Click to expand...
Click to collapse
thanks for the tips friend, i flashed some gases from android 9.0 and noticed that 90% of the performance improved which allowed me to played a little free fire lmfao so that unfortunately out of nowhere i faced some crashes and received the message from the user interface you are not responding, right now I am downloading the rom ressurrection remix oreo to see if it will work ... do you happen to know how to build a modified kernel? I have plans to make one for my cell phone but I don't know where to start. obrigado pelas dicas!!!! boa noite do brasil:good:
---------- Post added at 11:14 PM ---------- Previous post was at 11:09 PM ----------
bubba1601 said:
Unfortunately you can't downgrade android versions to 6 or 7, there's no system image / ROM on a lower android version for that device - but what you can do it's flash another GSi (ROM) to give you some usage back.
I also had the the XT1920 pettyl and android go is just awful, so I flashed several different roms to try.
The ones I got to work are
PHHussons lineage 15 (android Oreo)
ASOP 9 (android pie)
Pixel experience (pie)
Out of those lineage was the most stable.
You must remember pettyl only has 1gb ram, and does struggle with android 9 pie - but it does work without too many issues.
You got to learn a whole new process of unlocking the bootloader, flashing a custom recovery, disabling forced encryption and flashing a new ROM.
There are plenty of posts about roms for the E5 play in the threads here, I suggest you take a long read and don't try anything until you feel confident enough to begin because the process to flash roms on pettyl isn't very easy and is quite complex and complicated for a new inexperienced user.
It's quite easy to try that and completely mess up your device so it's unusable.
So, you MUST proceed with extreme caution, don't rush into anything without reading everything ten times, having a coffee and then reading it again another ten times.
Many users have tried to rush this process and then come here crying their phones don't work anymore - this happens because they've tried to rush the process, missed out steps and not read instructions properly........
Not being mean, but it happens all the time.
Edit
If you don't feel confident enough to flash a ROM (and no one will blame you if you don't) unfortunately all you can do is change the way you use your device.
I never noticed any music or you tube video freezing on my pettyl but how I used my device and how you use yours are probably very different.
You can't put lots of apps on android go devices, it doesn't like lots of apps.
You can disable most of the system / Google apps like playstore, Google play music and YouTube and install open source alternatives.
(For instance one plus music, you tube vanced and aurora store to name just three - just Google "disable system apps" or "replace Google apps")
I also tried a couple of launchers, and Librechair go edition or the android Go customised pixel launcher does make quite a significant difference to performance, depending on how much system stuff you disable and how many replacement apps you install.
Edit
I don't have my pettyl any longer so unfortunately that's the only help and advice I can offer you at this time.
Sorry.
Click to expand...
Click to collapse
thanks for the tips friend,
I already work in some way with custom roms since 2013 when I had my lg l1 2 lmfao... i flashed some gases from android 9.0 and noticed that 90% of the performance improved which allowed me to played a little free fire lmfao so that unfortunately out of nowhere i faced some crashes and received the message from the user interface you are not responding, right now I am downloading the rom ressurrection remix oreo to see if it will work ... do you happen to know how to build a modified kernel? I have plans to make one for my cell phone but I don't know where to start. obrigado pelas dicas!!!! boa noite do brasil
So about 3 weeks ago my 2 year old 3T just stopped working out of nowhere. I debated on whether to upgrade for over a week, but eventually decided to replace it with the same, just to have the familiar ROM, & not to have to learn anything new or mess with anything else, since I'm going through a lot of personal stuff right now. Anyway, I got the phone over a week ago and I've tried everything since then to get it running something beside OOS to no avail. Every single time it goes to sleep in another ROM, once I wake it up, touch is no longer responsive. I can't for the life of me figure out why. I have tried so many different things, in so many different ways. I know it might sound ridiculous but at this point I'm just in tears... I really need a functional phone, and I never would have bought another OP3T if I knew I'd be stuck with OOS....
The process I went through as soon as I got it:
Unfortunately I don't remember the version of OOS that it came with
- Unlock bootloader
- Flash TWRP (twrp-3.0.4-1 due to a thread I came across and was confused by)
- Wipe everything
- Flash recommended firmware for my ROM (posted in the ROM's thread)
- Flash my favorite ROM (Unofficial RR)
- Flash Magisk
- Boot, everything seems fine, screen goes off, turn it back on, unable to use touchscreen anymore.
I then used the unbrick tool, and tried again. Same problem. Used unbrick tool, unlocked bootloader, this time tried to flash this unofficial Lineage . Booted. It went to sleep. Woke up. Touchscreen nonfunctional.
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS. I go through the entire process again, this time flashing TWRP 3.2.1.0, it's the same thing. I've tried going up to open beta and then flashing my roms. I've tried flashing the rom without firmware, without magisk. With gapps. Without gapps. I always format and wipe everything. I also tried this on the off chance it might work.... I have seriously done the process every way imaginable, over twenty times since I got the phone last week.... nothing ever works. I also just tried Cyanogenmod, but it wouldn't flash at all.
I don't know what to do anymore. I just want to have a phone that I don't hate. At this point, I am too tired and I've got too much going on to figure this out on my own anymore. I would be grateful to pay someone at this point just to help me get this working honestly.... so if there's anyone out there who knows how to fix this, please let me know
Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.
Mizart said:
It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess).
Click to expand...
Click to collapse
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
SpaceOctopus said:
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS.
Click to expand...
Click to collapse
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.
Mizart said:
Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.
Click to expand...
Click to collapse
Brand new from ebay. Sealed in the box.
I did try flashing a more recent version of resurrection remix, but it failed. Any recommendations?
redpoint73 said:
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Click to expand...
Click to collapse
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case. Thank you.
hhp_211 said:
@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.
Click to expand...
Click to collapse
I did try that TWRP eventually. No change. I would probably have switched to pie a while ago, except one small thing. There's an xposed module I'm really attached to, and as far as I'm aware, xposed isn't available on pie? Or at least that's what I've heard/read. It's the xprivacy lua module that lets you control every type of data an app has access to. I think I've tried looking for an alternative and there aren't any, either. :'( You know, sometimes it's just that one small thing... lol
However, I did try to install the most recent version of RR yesterday, and it failed flashing. Don't know why. I'm going to try again after flashing the firmware. Maybe it'll work this time.
Anyway, I'm also going to try what you all have recommended and see what happens. Hopefully something happens. Thank you much for your help
Ok, well, this time it let me install Resurrection Remix latest version. It may not be exactly what I wanted, but it's pretty goddamn close, and it sure as hell isn't OOS! lol
Thanks for your help everyone! I really appreciate it. I do still really wish I knew wtf was happening honestly with it not properly running nougat ROM's, but hey, this works for me. It won't make me want to toss it in a dumpster and set it on fire every time I pick it up. :laugh: :laugh: :laugh:
Maybe I can get someone to figure it out in the future or something, I don't know. I sure wish someone would convert that xprivacy module to work with Magisk though! I'm surprised nobody has even made an alternative or an app or anything like it really.
SpaceOctopus said:
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case.
Click to expand...
Click to collapse
I think the unbrick tool does flash the full OOS. But honestly not 100% sure, as I have never actually had to use the unbrick tool (knock on wood!). Which is one reason I decided to pose that as a question.
In any case, if the unbrick did flash an old OOS, best to replace with newer version (or at least the firmware). Updated firmware typically plays better with the current custom ROMs. And old firmware is often a culprit when random bugs occur after flashing a custom ROM. So again, flashing firmware and/or the full update zip (which also flashes the firmware) is best practice in such cases. And if you are in any doubt about the OOS version or corresponding firmware that was installed, it probably doesn't hurt to flash again.
Hello everyone, try to install several custom roms, there is no tutorial that explains how the rom and twrp are installed. There are many tutorials and they all contradict, some say do this, others say do the other, but all fail.
Twrp boot, flash rom, install custom rom on SLOT A, install TWRP on slot B.
PROVEN ROMS:
PixelExperience:
Very low call volume, impossible to fix.
LineageOS:
Does not start play store, does not allow login to accounts, does not allow to install gapps.
- CURRENT ROM--
Evolution X:
Does not start play store, does not allow login to accounts.
I have been installing customs roms for years and this device is costing me my life. HELP
The most users get in trouble with A/B devices because they don't know exactly the differences between A-only and A/B partitions.
You don't know how to install TWRP? Why? On twrp.me you can find a detailed instruction for every single model.
A custom ROM is always a .zip file and you can flash a .zip file via TWRP. If you flash a ROM while slot _a is set as active you will install the ROM on slot _b. That's all. That is the meaning of semless updates.
Every new ROM must contain a own boot.img. A new boot.img will delete TWRP and Magisk. TWRP is a recovery and A/B devices don't have own partition for recovery. The recovery is merged in the boot partition.
Also Magisk uses the boot.img to patch the ramdisk. Flashing a new boot.img means you override the patched ramdisk with a new own. As a result you need a new Magisk installation.
my recommendation is starting from scratch with a clean stock 10 install then trying again...
lineage wiki probably has the best install instructions https://wiki.lineageos.org/devices/lake/install but also check its forum thread https://forum.xda-developers.com/g7-plus/development/rom-lineageos-17-1-t4076569 for other recommendations . if you want evolution X read the instructions in its thread https://forum.xda-developers.com/g7-plus/development/rom-evolution-x-4-1-69-moto-g7-plus-t4081731 as well but there pretty much the same.... you've probably went threw those threads already based upon you saying you have tried 3 diff roms already, but try again from a clean install of stock 10 (IF you want to run a 10 rom). i know it's not really a "clean/easy/simple" solution/tutorial, but with this device there is some trial and error for getting a half assed working install. however MAKE SURE you are on a stock 10 rom when installing a 10 rom, pixel experience is a 9 rom and that could be part of your problem. moving from android 10 stock, to a 9 rom, then back to a 10 rom will lead to issues. or a 9 rom, to a 10 rom, without moving to stock 10 in between will lead to problems.
as this isnt nearly a widely adopted device, custom rom development and support isnt even close to other devices, so expect bugs. i've always ran cfw's on all my devices ever since the htc g1/dream days, this is my first device i've stuck with stock due to the lack of rom development, lack of widespread use and people actually wanting to use cfw and users to bug report, and stock being more stable... but your mileage may vary. also no disrespect meant towards the hard working dev's who do work on this device, keep it up.
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
prodigy90 said:
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
Click to expand...
Click to collapse
yeah it seems to be pretty finicky getting a good install and gapps seem to have issues. reading all the posts in the lineage17 thread just make me cringe. as much as i'd love to use lineage as my daily driver (or evo X) my days of willing to put up with a buggy rom and daily dirty flashing have come and gone. this was my first, and will be my last, moto device for the the simple fact it just doesnt have the user base and its development is stunted, compared to more widely used devices.
i hope you get something working, the lineage17 thread definetly has some good advice on what people have done to get a working install, should be able to apply flash order etc to a evoX install (minus having to install gapps for evoX)
solved
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
prodigy90 said:
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
Click to expand...
Click to collapse
yup, the LMSA is a great tool for sure. glad you got back to a clean stock install.
Does anyone have any ideas on how to flash a GSI to the Dynamic Super Partition? I've been trying for a month to flash DotOS and nothing. I can get it to flash using "fastboot flash super" but flashing to system it fails. Still doesn't boot regardless, even if I flash vbmeta and stock boot. I have no idea what I'm doing wrong.
phenomenalblaze said:
Does anyone have any ideas on how to flash a GSI to the Dynamic Super Partition? I've been trying for a month to flash DotOS and nothing. I can get it to flash using "fastboot flash super" but flashing to system it fails. Still doesn't boot regardless, even if I flash vbmeta and stock boot. I have no idea what I'm doing wrong.
Click to expand...
Click to collapse
When I was testing out GSI I used this method:
I would just change the rom name in .bat(?) File. Everything flashed and booted fine. The only issue I had with GSI roms & AT&T was that I couldn't get mobile service.
Better to stick with one of the many custom roms made for Pixel 4/XL. I mean I'd rather use something made for my device than something universal. Cool to try out new things though I get it. DotOS is not too much different than anything else.. DotOS has a different look, a different theme/ui.. I'm referring to DotOS Android 11. I used DOT on my OnePlus 6t, before I got my Pixel 4XL. I'll see what I can find about what you are talking about here and if and when I do find some good reads I'll return and link to them in this same post. I would definitely search high and low and look around in PHH's GSI notes and see what all is in them about this sort of thing. How are you doing your install? What is your installation process step by step?
I haven't used a GSI since my Motorola phones a few years ago but I remember depending on what device installation varies. I'll see if I can locate anything and link it here and tag you if I do. Cheers.
Edit added: Turns out DotOS devs revamped the new Android 12 theme engine and plan on releasing it once they drop v5 2 of their DotOS rom!! Maybe someone will compile DotOS. I plan on getting another better laptop in six months. If it's not available for us then I'll take a few cracks at it and if I'm successful I'll first get permission from DotOS and show them what I have and if they okay it I'll post some Pixel 4XL coral builds. But that will be six to nine months away from now. Times are hard. May happen sooner..
@phenomenalblaze I found a tool thats supposedly made for this sort of thing here:
I'm usually not HUGE on using toolkits on Android because you don't learn anything that way you know. .But figured I'd share.