Related
Hi,
I have moto g 2014 dual sim. today I tried to reflash the os but got "Failed to validate system image" upon reboot. So I unlocked the bootloader and again reflashed the os but got bootloop.. Please tell me how to boot my moto G 2014?
Read the instructions and flash it correctly with the correct firmware. Also post your question in the correct section.
If you have winrar or 7zip you can extract the firmware and take the "boot.img" file and flash it separate from the other firmware and it should work. That's how I do mine.
Sent from my Moto G using XDA Premium 4 mobile app
Sorry for posting in different section, but I need help
eksasol said:
Read the instructions and flash it correctly with the correct firmware. Also post your question in the correct section.
Click to expand...
Click to collapse
Let me tell you the series of events that led me to have bricked Moto G 2014:
1. I had X1068 Moto G 2-14
2. Wanted to reflash firmware and followed the steps provided in 4.2 section here http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
3. I got "Failed to Validate System Image" when I tried to reboot.
4. I was advised to unlock bootloader and reflash firmware. I did the same but got bootloop when I tried to reboot.
5. Now when I power on the phone, bootloader unlocked warning message comes and the screen blinks with the same message..
Please help Bro..
Who ever told you to unlock bootloader to flash firmware is giving bad advice. It is not required to unlock the bootloader to flash the factory firmware.
Make sure you're using the driver from here: http://www.mymotocast.com/download/MDM?platform=windows
(If you have other Android ADB drivers installed, uninstall them first, before installing this one.)
Make sure you are using mfastboot.exe, not the regular fastboot.exe.
Make sure your downloaded firmware is not corrupt and you got the correct version of the firmware for your device, there are different ones.
Download the firmware from here: http://sbf.droid-developers.org/phone.php?device=36
I believe your file is "Blur_Version.21.11.14.titan_retaildsds.retaildsdsall.en.03", but check on it.
After you reflash, make sure you boot into recovery mode and do a factory wipe.
The firmware for this phone is split into 3 files, so make sure you flash all three of them.
Issue Resolved
DillonFixDroids said:
If you have winrar or 7zip you can extract the firmware and take the "boot.img" file and flash it separate from the other firmware and it should work. That's how I do mine.
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks bro.. It was my mistake not to flash all files in the firmware folder.. apart from three system files (0,1,2), we also need to flash fourth system file (3) in the firmware folder... Thanks again bro...
MotoG 2nd Gen
Folks, I got a MotoG 2nd Gen (XT1068) I'm trying to root it but not successful. The main reason for rooting is that I want to record all my calls. Any solution?
Thanks,
Raj.
4dglobal said:
Folks, I got a MotoG 2nd Gen (XT1068) I'm trying to root it but not successful. The main reason for rooting is that I want to record all my calls. Any solution?
Thanks,
Raj.
Click to expand...
Click to collapse
Please be more presice, have you unlocked bootloader, before trying to flash the recovery?
Greetings from Venezuela. Just recently, I bought a new Moto G since my old S3 got severly damaged which made it unrepairable. I loved the reviews about de Moto G, but sadly since I got it I've had no luck with it.
While being connected to a WiFi connection, just looking around the celphone's settings, the phone required a system update straight off the bat. I had noticed before the update that the phone was instantly rebooting once the inactivity timer went off locking itself. Obviously after some time I did notice it by locking the phone manually (pressing the power button). I'm not that geeky or experienced in the Android field, but by doing some research on the web I've read some stuff that makes me not lose all hope on the phone, making me want to fix it.
I've tried factory resets, recoverys and nothing has worked. It has made me really frustrated not being able to fix the issue. All I've really done refering to flashing is unlocking bootloader, but still without flashing anything yet to make sure what I'm doing is the right thing to do.
Specs
Android version: 5.0.2
Baseband version: MSM8626BP_1032.3112.97.00R
RETUSA_AWS_CUST
Kernel version: 3.4.42-gf18cb80
System version: 22.46.12.titan_retuaws.retuaws.en.US retus
Need help with this, and I'll be eternally grateful with anyone that can help me.
P.S: new to the forums. In any case that I'm missing something, let me know.
joserodriguezv said:
Greetings from Venezuela. Just recently, I bought a new Moto G since my old S3 got severly damaged which made it unrepairable. I loved the reviews about de Moto G, but sadly since I got it I've had no luck with it.
While being connected to a WiFi connection, just looking around the celphone's settings, the phone required a system update straight off the bat. I had noticed before the update that the phone was instantly rebooting once the inactivity timer went off locking itself. Obviously after some time I did notice it by locking the phone manually (pressing the power button). I'm not that geeky or experienced in the Android field, but by doing some research on the web I've read some stuff that makes me not lose all hope on the phone, making me want to fix it.
I've tried factory resets, recoverys and nothing has worked. It has made me really frustrated not being able to fix the issue. All I've really done refering to flashing is unlocking bootloader, but still without flashing anything yet to make sure what I'm doing is the right thing to do.
Specs
Android version: 5.0.2
Baseband version: MSM8626BP_1032.3112.97.00R
RETUSA_AWS_CUST
Kernel version: 3.4.42-gf18cb80
System version: 22.46.12.titan_retuaws.retuaws.en.US retus
Need help with this, and I'll be eternally grateful with anyone that can help me.
P.S: new to the forums. In any case that I'm missing something, let me know.
Click to expand...
Click to collapse
SEE POST#3 USA AWS CARRIERS for latest update - READ INSTRUCTIONS
reefuge said:
SEE POST#3 USA AWS CARRIERS for latest update - READ INSTRUCTIONS
Click to expand...
Click to collapse
I followed the inscrutions, successfully flashing stock rom. But the bug is still there since the phone keeps rebooting once the screen is locked. Still need to know if there's any fix. Thanks for the help!
A New Problem
I recently got an ~138mb OTA update, tried to install it, after downloading it, but it failed at default recovery installer, rebooting with an error message saying "Update installation unsuccessful". Hence, I tried it with a custom recovery TWRP installed in my mobile, with TWRP manager app for android (with my phone rooted obviously) So after downloading update, on giving install, it goes to TWRP recovery main menu, from there I dont know how to install the downloaded update, or where it is available to browse to... Being unsure, I rebooted it to normal boot up, but no matter what I do now, the phone after turning on in the home screen, automatically powers down(switching off) to TWRP recovery main menu, I am stuck here please help me, someone.
I dont wanna lose all my data!! Give me a suitable solution
Goutham_SRIRAM said:
I recently got an ~138mb OTA update, tried to install it, after downloading it, but it failed at default recovery installer, rebooting with an error message saying "Update installation unsuccessful". Hence, I tried it with a custom recovery TWRP installed in my mobile, with TWRP manager app for android (with my phone rooted obviously) So after downloading update, on giving install, it goes to TWRP recovery main menu, from there I dont know how to install the downloaded update, or where it is available to browse to... Being unsure, I rebooted it to normal boot up, but no matter what I do now, the phone after turning on in the home screen, automatically powers down(switching off) to TWRP recovery main menu, I am stuck here please help me, someone.
I dont wanna lose all my data!! Give me a suitable solution
Click to expand...
Click to collapse
ota can only be installed to non rooted stock roms with stock recovery
tbh you need to minimum factory reset
but I believe you will need to install stock rom from scratch
---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------
joserodriguezv said:
I followed the inscrutions, successfully flashing stock rom. But the bug is still there since the phone keeps rebooting once the screen is locked. Still need to know if there's any fix. Thanks for the help!
Click to expand...
Click to collapse
Never had or seen this all I can suggest is a factory reset twice and a few reboots to see if settles down
Guys i need help! I have the european Dual Sim Moto 2nd gen, locked bootloader and i tried to install Android Marshmallow via the indian zip (soak test) that i found in XDA. After installing the update via internal storage, it got stuck in optimizing 157 apps/158, it bootlooped and now it stucked it 1/1 optmizing ... What can i do???
Please, anything.
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
I got the T-mobile REVVLRY+ today, and naturally, I wanted to put the stock motorolla firmware on it. Partly to see if I could, partly to get rid of the T-Mobile bloat and see what Motorola features T-Mobile had removed.
Everything went swimmingly, I have PPW29.98-107 installed, I even have WIFI Calling. What I did lose, however, is VoLTE. I did use TWRP to perform a backup before flashing, so I tried restoring it to get a better look at how VoLTE works in the T-Mobile firmware. This is where things got hairy. I stupidly only backed up boot, system, and data. When I use TWRP to restore them, I get stuck in a boot loop. The built in boot loop fix in TWRP didn't help.
1. Any ideas on getting as close to stock as I can with only the boot, system, and data partitions?
2. Does anyone have access to a REVVLRY+ that would be willing to do a full backup that I may try to restore?
*Edit* SO I used the code *#*#4636#*#* and VoLTE provisioned is enabled, so maybe I do have VoLTE?
*Edit 2* Google Pay doesn't work, even after locking the bootloader. The device says that the operating system has been modified. Still trying to get it to restore.
FOUND IT!
I found a repo of firmware that has the TMO firmware! flashing now!
I can't share the external link yet.
BanterJSmoke said:
I found a repo of firmware that has the TMO firmware! flashing now!
I can't share the external link yet.
Click to expand...
Click to collapse
Where did you find it at? I would like to know because I'm trying to port Lineage OS to this phone. However, once I unlock the bootloader, I won't have an OS to use for it and i'll be screwed.
serris-chan said:
Where did you find it at? I would like to know because I'm trying to port Lineage OS to this phone. However, once I unlock the bootloader, I won't have an OS to use for it and i'll be screwed.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/lake/official/TMO/
HOW to
Hi, I just picked up the Revvlry+. Do you have step by step to install the Stock Moto firmware? I miss some of the features of the Moto. Also, was it easy to restore the TMO firmware just in case?
did you make any progress into the volte research? im on a unlocked xt1965-2 and using metro but i dont get volte in any of the stock roms or custom roms. i have tried flashing the modem from the stock tmo rom which didnt really do anything. i will probably try to flash the entire tmo rom tonight and see if it boots. im thinking if i get volte in the tmo rom and backup the persist, vendor and efs. then if i restore them onto a working cutom rom with volte enabled, volte should work.
i have also read about different scenarios in where you have to install workarounds to enable volte on treble roms. like installing the ims.apk to route the calls to volte and flashing a volte enabler to inject the correct files into the vendor partition.
my other device is a moto g5 plus which has numerous volte issues when switching between stock and custom roms or between different versions of android.
Did you use the Moto G7 Plus TWRP? I just picked up a Revvlry+ and I'm looking to root to install lawnchair or pixel launcher as a system app.
successfully unlocked the bootloader of my t-mobile revvlry which is a rebranded moto g7 i did it using this method but i'm going to be a little cautious on rooting unless i know it's safe and won't brick i could use some help with this https://www.androidinfotech.com/root-moto-g7-plus-pie/ i have the revvlry not the plus i want to try multirom installer and install ubuntu touch on it but i don't want to screw up my only phone but the only way i can try it is if i had root permissions to do so to install linux tried userland but i couldn't get unity desktop to work i'd rather have full root instead of fakeroot update: i was able to boot twrp before but now it doesn't work i think my firmware updated cause now when i run fastboot boot twrp.img nothing happens and i end up with remote failed reboot the phone and it goes directly to recovery with the only option is to do a factory reset
ghostdogg49504 said:
successfully unlocked the bootloader of my t-mobile revvlry which is a rebranded moto g7 i did it using this method but i'm going to be a little cautious on rooting unless i know it's safe and won't brick i could use some help with this https://www.androidinfotech.com/root-moto-g7-plus-pie/ i have the revvlry not the plus i want to try multirom installer and install ubuntu touch on it but i don't want to screw up my only phone but the only way i can try it is if i had root permissions to do so to install linux tried userland but i couldn't get unity desktop to work i'd rather have full root instead of fakeroot update: i was able to boot twrp before but now it doesn't work i think my firmware updated cause now when i run fastboot boot twrp.img nothing happens and i end up with remote failed reboot the phone and it goes directly to recovery with the only option is to do a factory reset
Click to expand...
Click to collapse
Are you saying with a Tmobile Revvlry, you were able to just go to the Motorola bootloader unlock page, paste your unlock codes, and presto as if it was just a normal Moto phone? If so, that is awesome!
I am thinking of swapping my Moto G7 Play with a Revvlry because of the 3gb RAM and NFC (the size of the G7 Play is perfect, I don't want to be forced to carry around a giant phone), but would love to flash the stock Moto G7 Play ROM over the Tmobile version. Not sure I'm willing to risk it, but if anyone has tried, I'd love to hear about it.
Logged into my account for this. Sorry if this is a little offtopic, but I want to see if this phone is compatible(or rather, how compatible it is) not only with Stock ROMs, but also with custom ROMs. For those REVVLRY owners, what have been your experience with this?
ultracoolguy said:
Logged into my account for this. Sorry if this is a little offtopic, but I want to see if this phone is compatible(or rather, how compatible it is) not only with Stock ROMs, but also with custom ROMs. For those REVVLRY owners, what have been your experience with this?
Click to expand...
Click to collapse
Phone works great with stock ROMs. I haven't tested out any custom ROMs, but I do have root on my REVVLRY.
tri_cchan said:
Phone works great with stock ROMs. I haven't tested out any custom ROMs, but I do have root on my REVVLRY.
Click to expand...
Click to collapse
nice man
Relocking Bootloader
Would I do the OEM lockbootloader command to lock it back
Can confirm flashing Moto g7 play firmware on T-Mobile revvlry. Caveat, you can no longer take OTA's and NFC is broken. Also can be bootloader unlocked through the Moto website.
Wouldn't you need to flash the G7 plus firmware for NFC to work?
guitardoc64 said:
Wouldn't you need to flash the G7 plus firmware for NFC to work?
Click to expand...
Click to collapse
That makes sense, the SD632 is NFC capable however I'm on the G7 play not the plus (I know, I know wrong forum)
I can't get the stock rom to work. It just bootloops every time. I tried all 3 versions. Any ideas?
Hey friends, would one of you kind sould who own the Revvlry+ be kind enough to post this Wallpaper?
Thanks in advance!
BanterJSmoke said:
I found a repo of firmware that has the TMO firmware! flashing now!
I can't share the external link yet.
Click to expand...
Click to collapse
Did you manage to restore it with firmware? Because I have a bootloop and I'm looking for a solution
quiet boy
I just solved the problem I had like 4 crazy hours with solve bootloop, the problem that I commanded automatic flash, not flashing the vendor partition and then flashed the manual vendor partition
mfastboot flash vendor vendor.img and ready
edit:
for users with Revvlry+ variant (XT1965-T) use this Flash.bat
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.
I thought I would just casually go through my installed apps and clean some up. I disabled the following...
1. Accessibility Suite
2. Gmail
3. Google TV
4. Google Music
5. Chroma
6. Razor Store
7. Logo+ (Uninstalled)
I then thought to myself that I would probably need the Accessibility Suite for apps that needed that as a permission to work. So I re-enabled it and it updated. I then rebooted and now the phone hangs at the Razor logo. I do have TWRP installed so I can get to that. I also have a complete backup from about a year ago using TWRP which I would like to use as my last resort. I am thinking that by disabling one of the above apps caused this issue. So, can I fastboot and re-enable them using adb? If so what is the command and the name for each app above? I am not an adb guru so the exact commands and names would help. Or if someone can think of another way to get my phone working besides a complete wipe I would greatly appreciate it! I am running MR1 stock with Magisk/art97. I do remember back in the day having a similar problem and I ended up re-flashing the ROM or something and it kept all my data but I think it just repaired the OS or something and that fixed a not booting issue. That was a long time ago so I cannot remember all the specifics but if that rings any bells for anyone as to another way I can approach this I am all ears. Thank you!
Logo+ - you uninstalled it. I dont think any others will prevent booting. If there is no logo, it will sit till it gets one. Reflash logo+ if at all possible. (I have a logo.img in my firmware, but different fone.
Pachacouti said:
Logo+ - you uninstalled it. I dont think any others will prevent booting. If there is no logo, it will sit till it gets one. Reflash logo+ if at all possible. (I have a logo.img in my firmware, but different fone.
Click to expand...
Click to collapse
Thanks for your reply. Logo+ is not a system app and shouldn't have anything to do with the Razor logo when booting up. Logo+ is a 3rd party app that allows to manipulate the colored logo on the back of the phone. For example when a notification comes in Logo+ can light up the colored logo on the back of the phone or make it flash. The app is from here. I've actually uninstalled and reinstalled Logo+ in the past when updating and such with no adverse effects. I can't imagine Logo+ would be the culprit here. What do you think?
I think only logo+ is capable of preventing boot, because your bootlooping. all other apps should NOT cause ANY bootloop, because they do not access anything previous to logo+, your first step in your problem.
Try this...
Logo+ if incorrect in any way will not show. This CAN cause bootloops. No other app you mention can. Perhaps your fone took a silent update, maybe it checked for the Logo+ and 'kicked' you for messing with it. Maybe google decided not to like it, so silently ordered your fone to delete the logo you installed leaving you with no logo+, and until you can see a logo+ your fone will stay there, so try my suggestion, seems your only choice. I have been flashing chips for years so can help, just go with my suggestion, reflash ONLY stock system.img/.bin using your stock flashing application, you'll be glad you did.
Pachacouti said:
I think only logo+ is capable of preventing boot, because your bootlooping. all other apps should NOT cause ANY bootloop, because they do not access anything previous to logo+, your first step in your problem.
Try this...
Logo+ if incorrect in any way will not show. This CAN cause bootloops. No other app you mention can. Perhaps your fone took a silent update, maybe it checked for the Logo+ and 'kicked' you for messing with it. Maybe google decided not to like it, so silently ordered your fone to delete the logo you installed leaving you with no logo+, and until you can see a logo+ your fone will stay there, so try my suggestion, seems your only choice. I have been flashing chips for years so can help, just go with my suggestion, reflash ONLY stock system.img/.bin using your stock flashing application, you'll be glad you did.
Click to expand...
Click to collapse
I will follow your instructions but I am needing some clarification please.
The app Logo+ never came with the stock OS or the Razor Phone 2. It is a separate app made by a 3rd party. So flashing the system.img will not bring back Logo+. So should I first attempt to flash the Logo+ app using TWRP?
If you want me to reflash the stock system.img, I don't believe I have that. How can I obtain this? And could you please provide me with the steps to reflash? Should I use TWRP or fastboot and use Windows adb?
So the Logo+ is only an app. Not a zip. So I don't believe I can flash that. Should I attempt to sideload it? Can I install an app on the phone when the phone cannot boot?
So logo+ IS your prob. Personally I would never use an app to do such work, I'd edit and flash it myself, but hey, you prob know this by now.
Go to (motorola?) Razor support, look for your firmware, it may help if you have phone plugged in while doing so in case they have a detector script to detect firmware for your fone.
Regardless, grab stock offered for your fone. This should also point you in the direction of the correct flashing frmware. once you have them, get back to me.
Or look at what I found using startpage/google:
Need help in flashing stock rom on Razer Phone 2 ! (Stuck in Bootloop)
Hello Everyone , I have ran into a very bad problem and would appreciate some help. I tried rooting my phone (Razer Phone 2 Atnt varient) with the following method...
forum.xda-developers.com
Take your pick, so many stock firmares online here:
Startpage Search Results
www.startpage.com
(I use startpage for these results)
Choose what you believe is for your fone, then read the XDA razor thread I linked to above, I will guide you once you have your files if you still need it, but read the razor thread first
Pachacouti said:
So logo+ IS your prob. Personally I would never use an app to do such work, I'd edit and flash it myself, but hey, you prob know this by now.
Go to (motorola?) Razor support, look for your firmware, it may help if you have phone plugged in while doing so in case they have a detector script to detect firmware for your fone.
Regardless, grab stock offered for your fone. This should also point you in the direction of the correct flashing frmware. once you have them, get back to me.
Or look at what I found using startpage/google:
Need help in flashing stock rom on Razer Phone 2 ! (Stuck in Bootloop)
Hello Everyone , I have ran into a very bad problem and would appreciate some help. I tried rooting my phone (Razer Phone 2 Atnt varient) with the following method...
forum.xda-developers.com
Take your pick, so many stock firmares online here:
Startpage Search Results
www.startpage.com
(I use startpage for these results)
Choose what you believe is for your fone, then read the XDA razor thread I linked to above, I will guide you once you have your files if you still need it, but read the razor thread first
Click to expand...
Click to collapse
The Razer Phone 2 is made by Razer https://www.razer.com/mobile. Motorola makes the Razr which can be confusing.
I don't know how to edit and flash the Logo+ app. Can you do this for me and I'll test? The app is located here https://github.com/CurtisMJ/LogoPlus/releases.
As I understand it as soon as I flash the stock rom it'll put me back to factory settings right? So I'll have to re-personlize my entire phone from scratch. I'd like to leave this as my last resort if possible. So if we can I'd like to flash the Logo+ if you can make that zip for me.
Hi, developer of Logo+ here
I think there's maybe some misunderstanding as to what the app does. It doesn't work on the bootloader splash in any way (this can actually cause failed boots). It's for controlling the RGB on the Razer logo on the back of the device. I named it "Logo+" to avoid any legal issues with caling it "Chroma" since thats a trademark of Razer. The app is entirely user space and is not active during boot. It modifies the lights via sysfs values (with root) that are entirely in RAM so they're cleared on boot.
You can typically just put the .apk in /data/app in recovery mode to install it. I think this may have changed slightly with newer android versions.
Ultimately I don't think Logo+ is needed for or can interfere with boot. I would suggest flashing the system image as suggested for a clean slate.
EDIT: You may end up having to use your last resort backup if you're not keen to loose *too* much data. Not booting is a difficult thing to troubleshoot because there's no feedback as to what went wrong on Android. If its a data thing and not a system thing that is. You could try fastboot flash each system image part to maybe fix any corruption
EDIT2: Take another backup before you do anything though. Titanium back can extract app data from TWRP backups so you can restore your user data at least
CurtisMJ said:
Hi, developer of Logo+ here
I think there's maybe some misunderstanding as to what the app does. It doesn't work on the bootloader splash in any way (this can actually cause failed boots). It's for controlling the RGB on the Razer logo on the back of the device. I named it "Logo+" to avoid any legal issues with caling it "Chroma" since thats a trademark of Razer. The app is entirely user space and is not active during boot. It modifies the lights via sysfs values (with root) that are entirely in RAM so they're cleared on boot.
You can typically just put the .apk in /data/app in recovery mode to install it. I think this may have changed slightly with newer android versions.
Ultimately I don't think Logo+ is needed for or can interfere with boot. I would suggest flashing the system image as suggested for a clean slate.
EDIT: You may end up having to use your last resort backup if you're not keen to loose *too* much data. Not booting is a difficult thing to troubleshoot because there's no feedback as to what went wrong on Android. If its a data thing and not a system thing that is. You could try fastboot flash each system image part to maybe fix any corruption
EDIT2: Take another backup before you do anything though. Titanium back can extract app data from TWRP backups so you can restore your user data at least
Click to expand...
Click to collapse
Thank you for taking the time to chime in here @CurtisMJ. I did end up gettijg it to boot now in partition a. I went into TWRP and switched to partition a and phone boots but no longer has root or magisk. I'm not sure how the partitions work but it looks like there are two that the Razer uses. A and b. And I guess I've been using b since the beginning and since b won't boot now I tried booting off partition a and the phone seems to work as it did. All apps and widgets are in the same place except magisk and phone isn't rooted. I could reflash the system image but the amount of time to re-personalize everything will be extensive. So I just wanted to make sure I did everything I could before that. I'll try copying the apk as suggested and see if that works.
Do you know if there is a way to enable system apps when they've been disabled like I did when phone won't boot? I am in partition a right now and booted and I reinstalled logo+ and saw that all the apps I disabled in OP are back to being enabled. So I am not sure if partition a and b share the same system and user data but everything is exactly what it looks like from partition b. So it is a good chance they share everything except magisk which I guess is flashed at the partition level. Just trying to make sense. Thanks for everyone's time.
So the A-B partition layout is a thing that was introduced by google for more reliable system updates. Effectively the phone has 2 copies of the OS, including system partition,kernel,vendor etc and the phone flip-flops between them on every update, updating the "other" partition to the one its running so if it fails it can boot to the still good one. So you effectively went a system update backwards, but using the same user data partition (or Magisk kept an old copy of the system around). System apps disabled status is stored in /data/system/users/0/package-restrictions.xml which can edited in TWRP with some effort. Magisk is likely flashed to kernel B so you're correct in that its a partition level thing.
CurtisMJ said:
So the A-B partition layout is a thing that was introduced by google for more reliable system updates. Effectively the phone has 2 copies of the OS, including system partition,kernel,vendor etc and the phone flip-flops between them on every update, updating the "other" partition to the one its running so if it fails it can boot to the still good one. So you effectively went a system update backwards, but using the same user data partition (or Magisk kept an old copy of the system around). System apps disabled status is stored in /data/system/users/0/package-restrictions.xml which can edited in TWRP with some effort. Magisk is likely flashed to kernel B so you're correct in that its a partition level thing.
Click to expand...
Click to collapse
Thank you so much for that explanation. That makes a lot of sense. My OS has been MR1 for a long time and OTA has been turned off so I guess there hasn't been any OS updates so there's been no reason to switch between partition a and b I guess. So I guess there's technically been a backup of my OS all this time with the double partition thing which is cool. And I guess I could magisk and root partition a. If I reflash the system image to partition b will that effect partition a?
I think he's talking bootloaders re: a/b partitioning, The point of A/B being if your using 'A' to boot, and you update, the updated BOOTLOADER is flashed to 'B' and when you reboot the f'n, 'B' becomes your main bootloader until next update where that update will use 'A' having been 'emptied' after the previous update sort of thing, I dont have a/b, but this is my understanding of the a/b partitioning,,,?
Opens up the options for dual booting fone with or without magisk, If I had a/b, i'd flash magisk to one and stock to the other...
Pachacouti said:
I think he's talking bootloaders re: a/b partitioning, The point of A/B being if your using 'A' to boot, and you update, the updated BOOTLOADER is flashed to 'B' and when you reboot the f'n, 'B' becomes your main bootloader until next update where that update will use 'A' having been 'emptied' after the previous update sort of thing, I dont have a/b, but this is my understanding of the a/b partitioning,,,?
Opens up the options for dual booting fone with or without magisk, If I had a/b, i'd flash magisk to one and stock to the other...
Click to expand...
Click to collapse
I was thinking the same. I believe I have the opportunity to stick with the working partition which is a, and magisk that. And then for the partition b I could put the official lineage OS on there. My only concern is if lineage had an update does it update both a and b partitions which I would lose my original OS then. I guess I'll have to research.
I think it's safe to assume that when an update takes place, upon reboot, whichever bootloader you WERE using, a OR b, is now empty... it's staring you in the face
Just remember what we agreed on. Once you magisk your current bootloader, make a backup of said bootloader, store it on main computer, because when you flash lineage, your magisk in your current slot will be wiped. Once you have installed Lineage, you will need to boot into fastboot to re-flash magisk, and then use fastboot boot a or b for dual booting until you get an app or sumat to choose in gui what you choose to boot into
What I am thinking I will do for the time being is stick with booting into partition a which is currently not rooted and I am fine with that. At least it works unlike partition b. This is my main phone, my only phone, and I need it to work right now so would rather not risk causing issues flashing stuff. I know enough about flashing to be dangerous.
Currently the official release of lineage for the Razer Phone 2 is still not stable yet according to the forum here. So camera still doesn't work and I need the camera to work. So I'll wait until the camera is fixed which hopefully will be soon.
You stated in your previous post "sumat to choose in gui what you choose to boot into" can you clarify? Are you saying there is a GUI that helps choose what to boot into? Currently I am using TWRP to select partition a or b to boot into. It takes about a minute to load into TWRP but I wouldn't be doing it often. I don't think I really have a use for dual booting.
I appreciate the help. As soon as I am ready to proceed I'll update this post and If you're still around I'll receive your assistance. Thank you for your time.