Related
The device must be unlocked with the bootloader and preferably be installed with the Lollipop.
Download the recovery rom the gapps
Recovery: http://skrilax.droid-developers.org/cm12quark/recovery.img
Rom: http://download.cyanogenmod.org/?device=quark
Gapps: https://mega.co.nz/#!m0YWEQDb!nlhiOQppxQHOQmBgwuxipXExb8N48V0mkqL37ajgtD4 or here http://forum.xda-developers.com/showthread.php?t=2943330
Gapps central http://forum.xda-developers.com/and...gn=Feed:+xda-developers/ShsH+(xda-developers)
Place the device in fastboot (turn, turn holding volume - and power)
In the fastboot mode go put the downloaded file in the same past that run the fastboot and type in cmd
Fastboot flash recovery recovery.img
After that select the recovery option
Within the recovery knife cm one factory reset (will delete all apps and the official rom) will take a time up to 10 minutes
Now choose apply update and select the folder of the download, install the rom, at the end install gapps.
A wipe cache and select reboot now.
The rom is still beta and contains bugs.
Cyanogem now is oficial for our device, know as quark.
Oficial topic is here http://forum.xda-developers.com/dro.../moto-maxx-xt1225-cm12-0-pre-release-t3060089
Great Thanks for @Skrilax_CZ from bring this awesome rom.
matheus_sc said:
The device must be unlocked with the bootloader and preferably be installed with the Lollipop.
Download the recovery rom the gapps
Recovery: http://skrilax.droid-developers.org/cm12quark/recovery.img
Rom: http://skrilax.droid-developers.org/cm12quark/cm-12-20150320-SKRILAX-PUBLIC-quark.zip
Gapps: http://d-h.st/s6IB
Place the device in fastboot (turn, turn holding volume - and power)
In the fastboot mode go put the downloaded file in the same past that run the fastboot and type in cmd
Fastboot flash recovery.img
After that select the recovery option
Within the recovery knife cm one factory reset (will delete all apps and the official rom) will take a time up to 10 minutes
Now choose apply update and select the folder of the download, install the rom, at the end install gapps.
A wipe cache and select reboot now.
The rom is still beta and contains bugs.
Cyanogem now is oficial for our device, know as quark.
Oficial topic is here http://forum.xda-developers.com/dro.../moto-maxx-xt1225-cm12-0-pre-release-t3060089
Soon we have first nightly will be found here http://download.cyanogenmod.org/?device=quark
Great Thanks for @Skrilax_CZ from bring this awesome rom.
Click to expand...
Click to collapse
Nice!
Waiting for release Nigh
Guys now oficial build is up
matheus_sc said:
The device must be unlocked with the bootloader and preferably be installed with the Lollipop.
Download the recovery rom the gapps
Recovery: http://skrilax.droid-developers.org/cm12quark/recovery.img
Rom: http://download.cyanogenmod.org/?device=quark
Gapps: http://d-h.st/s6IB
Place the device in fastboot (turn, turn holding volume - and power)
In the fastboot mode go put the downloaded file in the same past that run the fastboot and type in cmd
Fastboot flash recovery.img
Click to expand...
Click to collapse
I might be wrong, but I think syntax should be:
fastboot flash recovery recovery.img
And thank you for this.
Simplifies things a lot.
poncespr said:
I might be wrong, but I think syntax should be:
fastboot flash recovery recovery.img
And thank you for this.
Simplifies things a lot.
Click to expand...
Click to collapse
You are right Thanks , i update topic.
Shouldn't this be a sticky so it is easy to find?
Maybe, today we have more bugs fixed i see em cmxlog.com
issues
i'm having issues with installation...
"install failed" and a lot of errors with "E: failed to mount [...] (invalid argument)"
what this should be?
Can be, bad download or dont be in Lollipop
Question
Hey guys, I was meaning to ask this question in the Moto Maxx forum (here) but I thought it might be more appropriate to post it as a general question for all Android users.
I am using Xposed for now but thinking about going the CM way on my Moto Maxx. Therefore I posted this discussion post. What do you guys think?
http://forum.xda-developers.com/general/general/discussion-custom-rom-using-xposed-t3065201
Kiwironic said:
Hey guys, I was meaning to ask this question in the Moto Maxx forum (here) but I thought it might be more appropriate to post it as a general question for all Android users.
I am using Xposed for now but thinking about going the CM way on my Moto Maxx. Therefore I posted this discussion post. What do you guys think?
http://forum.xda-developers.com/general/general/discussion-custom-rom-using-xposed-t3065201
Click to expand...
Click to collapse
I use cm without xposed here, i think be more stable, xposed is alpha yet.
matheus_sc said:
I use cm without xposed here, i think be more stable, xposed is alpha yet.
Click to expand...
Click to collapse
I think you're right. I will flash it now.
Update:
I had my backup done and everything in order, but didn't go through with it as I am not sure if the official Moto apps still work ?? Moto assist, voice, etc....? Anybody wants to help with this?
I use the wave to action(s) using the IR sensors a lot as well as the Moto voice and the rest of the much appreciated Moto feature and would hate to lose them.
Kiwironic said:
I think you're right. I will flash it now.
Update:
I had my backup done and everything in order, but didn't go through with it as I am not sure if the official Moto apps still work ?? Moto assist, voice, etc....? Anybody wants to help with this?
I use the wave to action(s) using the IR sensors a lot as well as the Moto voice and the rest of the much appreciated moto feature and would hate to love them.
Click to expand...
Click to collapse
No yet , I love them too ;(
Sent from my quark using XDA Free mobile app
Kiwironic said:
I think you're right. I will flash it now.
Update:
I had my backup done and everything in order, but didn't go through with it as I am not sure if the official Moto apps still work ?? Moto assist, voice, etc....? Anybody wants to help with this?
I use the wave to action(s) using the IR sensors a lot as well as the Moto voice and the rest of the much appreciated Moto feature and would hate to lose them.
Click to expand...
Click to collapse
No moto apps dont work in cm yet
Topic update with gapps central link
Moto apps will not work themselves in CM12. The goal with CM12 is to (aside from fixing Wifi AP, already found where the problem is, but unsure of how to fix it right now):
1) Get the IR gestures to work (currently WIP, waking the phone from sleep is first task (monitor http://review.cyanogenmod.org/#/c/92647/ - 95% of the work will be here, current status is that IR sensor works, but isn't configured properly and doesn't wake the device), silencing ringtones will come afterwards)
2) Get Nexus 6 Voice Recognition to work.
btw. if you place your phone to dark, you can see the IR leds (top right, bottom left, bottom right ).
Skrilax_CZ said:
Moto apps will not work themselves in CM12. The goal with CM12 is to (aside from fixing Wifi AP, already found where the problem is, but unsure of how to fix it right now):
1) Get the IR gestures to work (currently WIP, waking the phone from sleep is first task (monitor http://review.cyanogenmod.org/#/c/92647/ - 95% of the work will be here, current status is that IR sensor works, but isn't configured properly and doesn't wake the device), silencing ringtones will come afterwards)
2) Get Nexus 6 Voice Recognition to work.
btw. if you place your phone to dark, you can see the IR leds (top right, bottom left, bottom right ).
Click to expand...
Click to collapse
Great, if you can, after that work, could you look in battery optimizations.
I followed some tutorial in this site https://goo.gl/fz0bIx and now i can't fix the wi-fi mac address (appears as 02:00:00:00:00) and it can't find the wifi networks
Can anyone help me?
Please tell what you have flashed
garva1 said:
Please tell what you have flashed
Click to expand...
Click to collapse
I followed the tutorial and flashed this: https://dl.twrp.me/athene
followed the next steps on the tutorial and flashed this: https://drive.google.com/file/d/0B3TKzy1UugHNT1RvNURsWmRoMVk/view
and then installed the supersu as described there: https://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip
The wifi does not work (gives me the strange address) and i don't know if this is related to a corrupted /persist partition. The wifi folder inside it has no files.
----
I think the issue may be related to this (not sure tho): the ROOT files are for "athena 1641/1643" model. I have "athene 1626" model.
If it is related to the files i pointed above, how do i fix it? Is Returning to stock rom the right way?
----
DTV module is faulty too. Probably the thing i flashed corrupted it too.
I have the same problem!
May I make the claim that there's no working root available for Moto G4? I had this problem as well.
I jumped from Moto G1 to Moto G4 a couple of weeks ago. I tried to root it immediately after I received my device. I came across with several posts talking about the rooting process. By following those instructions, I got a clean backup after installing TWRP and before doing anything else. Then I tried to install SuperSU for a couple of times with different versions from 2.36 to the latest one 2.74 - NONE of them worked. It left you a non-bootable Moto G4. it stopped at the Moto logo - no animation of changing to Lenovo logo. I have to restore my phone over and over again.
Suddenly, I found the one posted above and flashed the modified boot.img. It can boot the device. However, before I tried to check if the root was successful or not, I noticed the wifi problem. Then I realised that the modified boot.img might be ONLY suitable for Moto G4 Plus (I don't know if it really works, I have not G4 Plus to test - it's just a guess!). So I make a full restore and get the wifi working now.
That's my attempts on rooting Moto G4 till now. If anyone has a working root, please tell us the process.
libralibra said:
May I make the claim that there's no working root available for Moto G4? I had this problem as well.
I jumped from Moto G1 to Moto G4 a couple of weeks ago. I tried to root it immediately after I received my device. I came across with several posts talking about the rooting process. By following those instructions, I got a clean backup after installing TWRP and before doing anything else. Then I tried to install SuperSU for a couple of times with different versions from 2.36 to the latest one 2.74 - NONE of them worked. It left you a non-bootable Moto G4. it stopped at the Moto logo - no animation of changing to Lenovo logo. I have to restore my phone over and over again.
Suddenly, I found the one posted above and flashed the modified boot.img. It can boot the device. However, before I tried to check if the root was successful or not, I noticed the wifi problem. Then I realised that the modified boot.img might be ONLY suitable for Moto G4 Plus (I don't know if it really works, I have not G4 Plus to test - it's just a guess!). So I make a full restore and get the wifi working now.
That's my attempts on rooting Moto G4 till now. If anyone has a working root, please tell us the process.
Click to expand...
Click to collapse
I did not make a backup (stupid, i know). I'm trying to find a rom that works but had no success. The one i've found is giving me an error in twrp. I just want to get it back to original :/
lokinmodar said:
I did not make a backup (stupid, i know). I'm trying to find a rom that works but had no success. The one i've found is giving me an error in twrp. I just want to get it back to original :/
Click to expand...
Click to collapse
Try to search in this page: wwwDOTfilefactoryDOTcom/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Remember that our Moto g4 is XT1622. there're some on that page. I did download them in case something went wrong while rooting. but i never flash them - thanks to the backup. There's one said XT1622 specifically in the file name but it also said TESCO. I'm not sure if it's for TESCO network only or not - better to try. Someone mentioned that the file 'XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip' contains the XT1622 image and thought to be correct as it appears in the file name. I also tried 'mfastboot.exe getvar all' before the modification. The saved txt file from that command has the same version information: Athene 6.0.1, MPJ24.139-23.4.
Anyway, try to get the stock rom and flash it. Reboot to see if the wifi worked. If so, fastboot and flash TWRP and that's it - do not proceed any further. For the time being, we have to be patient for a working root method on Moto G4. I just cannot understand why people are writing some 'INSTRUCTION' they don't know if it worked or not.
libralibra said:
Try to search in this page: wwwDOTfilefactoryDOTcom/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Remember that our Moto g4 is XT1622. there're some on that page. I did download them in case something went wrong while rooting. but i never flash them - thanks to the backup. There's one said XT1622 specifically in the file name but it also said TESCO. I'm not sure if it's for TESCO network only or not - better to try. Someone mentioned that the file 'XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip' contains the XT1622 image and thought to be correct as it appears in the file name. I also tried 'mfastboot.exe getvar all' before the modification. The saved txt file from that command has the same version information: Athene 6.0.1, MPJ24.139-23.4.
Anyway, try to get the stock rom and flash it. Reboot to see if the wifi worked. If so, fastboot and flash TWRP and that's it - do not proceed any further. For the time being, we have to be patient for a working root method on Moto G4. I just cannot understand why people are writing some 'INSTRUCTION' they don't know if it worked or not.
Click to expand...
Click to collapse
I'll search this site. My phone box says XT1626 (Brasil version with DTV)
Update:
Flashed the 1626 version from the site using mfastboot and this sequence: This Post
Now it seems to be working fine (gotta test DTV. It found the channels but my signal is bad so...)
WIFI is alive and well ^^
lokinmodar said:
I'll search this site. My phone box says XT1626 (Brasil version with DTV)
Update:
Flashed the 1626 version from the site using mfastboot and this sequence: This Post
Now it seems to be working fine (gotta test DTV. It found the channels but my signal is bad so...)
WIFI is alive and well ^^
Click to expand...
Click to collapse
How you solved the WiFi issue.
garva1 said:
How you solved the WiFi issue.
Click to expand...
Click to collapse
Just flashed the entire XT1626 firmware using the sequence i posted above. No issues at all. Phone working completely fine
Help!
I have the same Issue, my MAC-Adress shows some bull***t and my WiFi wont show anything. I already tried to flash two different XT-1622 ROM's but it did NOT help me at all. I now will also try to flash the XT-1626 ROM, hoping that it will somehow fix my device. If anyone who sees this has an idea how to fix this or encountered the same problem and already fixed it, please notify me.
Thank you.
EDIT:
Turns out, that I am the biggest retard and not worth living on this world anymore.
I always executed the different ROM-Flashes by using the default batch-file given by the "how to reset" post creater... But instead of putting it in the core directory of the extracted zip i just put it in the mfastboot folder. Ofcourse, it executed very fast, i couldnt read the error codes, but my device always just resetted itself, and restarted. I thought it already was a new rom flashed, but it actually was the same over and over again. Now i found out, flashed one xt-1622 rom and its back up, working
God I feel stupid now.
TomasWilson said:
I have the same Issue, my MAC-Adress shows some bull***t and my WiFi wont show anything. I already tried to flash two different XT-1622 ROM's but it did NOT help me at all. I now will also try to flash the XT-1626 ROM, hoping that it will somehow fix my device. If anyone who sees this has an idea how to fix this or encountered the same problem and already fixed it, please notify me.
Thank you.
Click to expand...
Click to collapse
Which model is in the phone box barcode? I followed that and managed to make my phone come back to life following the steps i posted above
Sent from my Moto G (4) using Tapatalk
lokinmodar said:
Which model is in the phone box barcode? I followed that and managed to make my phone come back to life following the steps i posted above
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
I cant actually look at the box, because I dont know where it is right now. I am actually pretty sure it was an XT-1622.
There is a tag on the phone's battery. Model is in there too. What country are you?
or you can use the command I posted above: mfastboot.exe getvar all
there's a line said something like: (bootloader) sku: XT1622
that's the model. it's better to make backup and record as many information as possible before doing any modifications.
Hi, i have same problem. Please, can you tell me any way around not installing stock rom again or another custom rom to see if it has wifi fixed or if all fails, install stock rom
Please any way to fix the wifi problem?
Yudi313 said:
Hi, i have same problem. Please, can you tell me any way around not installing stock rom again or another custom rom to see if it has wifi fixed or if all fails, install stock rom
Please any way to fix the wifi problem?
Click to expand...
Click to collapse
Where do you see this bogus address?
I;ve unlocked and rooted 2 Moto G4 XT1625 phones that show this bogus address in a wifi widget I use on my home screen. I don;t seem to have a problem connecting to wifi. When I go to Settings about phone status I see the correct address
I used to see it on the advance settings in wifi.. however, I like Android so I play alot with it if you ever get any problem make sure you have a stock mpj or npj Rom with fastboot flash compatibility. And flash all the. Image sparse chunk :good:
After updating to Nougat, the bogus 02:00:00:00:00:00 address still displays on my wifi widget but displayed correctly in settings. No problem getting connected to wifi networks.
Sent from my Moto G (4) using Tapatalk
Hi guys,
So, this is a last resort. I've followed a number of different guides and methods, but nothing has worked. The closest "success" I've had is with a Chainfire auto root; it flashes, it breaks Knox, but I still don't have SU. Could it be because I don't have an SD card? I saw it as a prerequisite in some guide but didn't really put much stock in it as that was a single mention which also involved loading it with verity, which I'm more interested in removing.
I've also tried twrp, which that looked like it had bricked my device, though I managed to recover it by flashing the auto root again. I'm speculating that it's something to do with the latest updates, but really I'm just clueless and frazzled after 4+ hours of wracking my brains. I'm not sure what other info you'd find helpful anymore without going full splurge, so I'll keep it sweet and let you question me or berate me for my vile, witholding ways as you see fit. Any help is greatly appreciated!
Edit:
My SU checker says that I've not got the binaries or root user account. The .tar from firmware.mobi is only 54mb. I tried turning off suhide, but changed no other options. Trying to use fastboot straight up fails, the device isn't recognised after adb booting (despite having tried the correct drivers and some random others multiple times over.) I've been unable to locate a release for the T585 on twrp site, though a version is out there on these forums from a year or so back.
Smellfungus said:
Hi guys,
So, this is a last resort. I've followed a number of different guides and methods, but nothing has worked. The closest "success" I've had is with a Chainfire auto root; it flashes, it breaks Knox, but I still don't have SU. Could it be because I don't have an SD card? I saw it as a prerequisite in some guide but didn't really put much stock in it as that was a single mention which also involved loading it with verity, which I'm more interested in removing.
I've also tried twrp, which that looked like it had bricked my device, though I managed to recover it by flashing the auto root again. I'm speculating that it's something to do with the latest updates, but really I'm just clueless and frazzled after 4+ hours of wracking my brains. I'm not sure what other info you'd find helpful anymore without going full splurge, so I'll keep it sweet and let you question me or berate me for my vile, witholding ways as you see fit. Any help is greatly appreciated!
Edit:
My SU checker says that I've not got the binaries or root user account. The .tar from firmware.mobi is only 54mb. I tried turning off suhide, but changed no other options. Trying to use fastboot straight up fails, the device isn't recognised after adb booting (despite having tried the correct drivers and some random others multiple times over.) I've been unable to locate a release for the T585 on twrp site, though a version is out there on these forums from a year or so back.
Click to expand...
Click to collapse
The only way I know of to successfully root a Tab A is by flashing TWRP and then using it to flash SU or Magisk. What version of TWRP are you using and what version of Odin? Using the correct ones won't brick a T585.
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Nimueh said:
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
I am about to try this.... was you device on Android 7 (nougat) or Android 8 (Oreo) when you did this?
Thanks for your time.
webzo said:
I am about to try this.... was you device on Android 7 (nougat) or Android 8 (Oreo) when you did this?
Thanks for your time.
Click to expand...
Click to collapse
I honestly don't remember
But it should work on either one - only difference now is that we have an official recovery that can be downloaded from twrp.me directly :highfive:
Nimueh said:
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
webzo said:
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
Click to expand...
Click to collapse
Ok, so I went ahead and tried with the latest TWRP (3.3.1.1), RR (v7.0.2).
Everything seemed to go well..... except, tablet is now stuck in boot animation. It won't startup.
I double checked and I don't think I missed any steps.... Any ideas on what I can try?
Thanks.
webzo said:
Ok, so I went ahead and tried with the latest TWRP (3.3.1.1), RR (v7.0.2).
Everything seemed to go well..... except, tablet is now stuck in boot animation. It won't startup.
I double checked and I don't think I missed any steps.... Any ideas on what I can try?
Thanks.
Click to expand...
Click to collapse
Update:
I tried to restore the backup via TWRP and ended up with a "unable to mount /system" error.
My /system partition was showing zero size.
Many wipes and restores didn't help.
Eventually, what seemed to help was to choose repair the system partition, change file system to FAT, change file system back to ext4. Saw it in a youtube video- https://www.youtube.com/watch?v=T-7neHzSIvc
After /system error was fixed, I did an install of RR again and it went smooth.
All is well now.
Hope this helps someone.
webzo said:
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
Click to expand...
Click to collapse
Back then we had no working official version and the Omni6 one was the only one without issues. Now we have the official and it should work just fine.
No idea why you had those problems, but I'm glad you got it all sorted
Looking for any help or at least clues about what is wrong.
I was on ArrowOS 10, updated OTA to latest build two days ago, all was fine. Tonight it suddenly rebooted and when I unlock it, the desktop says the OS is loading, but it hangs, and then eventually reboots, bootlooping.
I had a working Nandroid backup, so I restored that from TWRP. Still cannot get the OS loaded. Wiped everything, even internal storage, backup still had same issue.
Then I tried reinstalling an older build of the ROM that I knew worked for me and I get stuck on the "Just a sec" after choosing a language. Eventually it reboots and hangs on the "Just a sec" before rebooting again. Wiped everything again and I tried another build of the same ROM, same problem. More wiping, tried Pixel Experience, same problem.
I'm thinking something is corrupted but I don't get any specific error messages so I'm not sure what to do. I repaired the data partition in TWRP, thinking that was the issue, but still cannot get any ROMs to load.
Any guidance is greatly appreciated as the phone is useless in this state. Thank goodness I have all my data backed up, but I really hope the phone is salvageable. Thank you.
twasbrillig12 said:
Looking for any help or at least clues about what is wrong.
I was on ArrowOS 10, updated OTA to latest build two days ago, all was fine. Tonight it suddenly rebooted and when I unlock it, the desktop says the OS is loading, but it hangs, and then eventually reboots, bootlooping.
I had a working Nandroid backup, so I restored that from TWRP. Still cannot get the OS loaded. Wiped everything, even internal storage, backup still had same issue.
Then I tried reinstalling an older build of the ROM that I knew worked for me and I get stuck on the "Just a sec" after choosing a language. Eventually it reboots and hangs on the "Just a sec" before rebooting again. Wiped everything again and I tried another build of the same ROM, same problem. More wiping, tried Pixel Experience, same problem.
I'm thinking something is corrupted but I don't get any specific error messages so I'm not sure what to do. I repaired the data partition in TWRP, thinking that was the issue, but still cannot get any ROMs to load.
Any guidance is greatly appreciated as the phone is useless in this state. Thank goodness I have all my data backed up, but I really hope the phone is salvageable. Thank you.
Click to expand...
Click to collapse
Sounds not so good. I would try to fastboot flash the latest signed Motorola firmware.
Here's a link where you can find it and how to do it:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
Sounds not so good. I would try to fastboot flash the latest signed Motorola firmware.
Here's a link where you can find it and how to do it:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Thank you! That fixed it. Any idea what happened? Could it have been from the OTA update two days prior? I'd like to prevent it from happening again if possible.
twasbrillig12 said:
Thank you! That fixed it. Any idea what happened? Could it have been from the OTA update two days prior? I'd like to prevent it from happening again if possible.
Click to expand...
Click to collapse
First of all good to hear you've got everything up and working again. Difficult to say what caused the problem, best would be to give these informations to the ROM maintainer/developer because he knows best what is changed in his custom ROM/OTA compared to the original stock firmware.
I would think it has been the OTA update that caused the trouble, OTA's are problematic for manufacturers and even more for custom ROMs with a smaller userbase and less employees.
My advice would be to avoid OTA updates if possible, often it's better to (dirty) flash the whole ROM by hand if available.
But the exact reason is not easy to find out, as said check the ROMs thread or PM the maintainer.
If you're in a situation like you've been it's always a good idea to flash original stock firmware, it brings the device to the most stable and recommended state.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
First of all good to hear you've got everything up and working again. Difficult to say what caused the problem, best would be to give these informations to the ROM maintainer/developer because he knows best what is changed in his custom ROM/OTA compared to the original stock firmware.
I would think it has been the OTA update that caused the trouble, OTA's are problematic for manufacturers and even more for custom ROMs with a smaller userbase and less employees.
My advice would be to avoid OTA updates if possible, often it's better to (dirty) flash the whole ROM by hand if available.
But the exact reason is not easy to find out, as said check the ROMs thread or PM the maintainer.
If you're in a situation like you've been it's always a good idea to flash original stock firmware, it brings the device to the most stable and recommended state.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Okay, I was planning on dirty flashing the next update anyway. I usually do since OTA's often don't work for me, but this last one seemed like it was. I'm definitely notifying the developer. Thanks again!
I really need help. I don't have a usable phone.
It's a long sad story but I had a working rooted phone with stock Android 9 and Magisk. Because I could not get OTA updates I wanted to update the old version installed, but never succeeded. To make a long story short, since I had a recent Twrp backup so I did a twrp restore.
Rebooting after that caused a boot loop. I finally flashed a stock boot.img using adb and ended with either a boot loop or just the Moto image staying static.
I gave up and decided to do a factory restore.
TWRP is no longer available as recovery. I now get the dead android with red exclamation mark. I got to the options and selected factory restore with wipe user data. Reboot now gives me a static Moto image and nothing further.
I repeated factory restore with wipe user data 2 more times with same result.
How do I get a working phone again?
Please help. Thank you.
Hi there,
I had a similar problem with my phone a few days ago.
Did you try to flash back your stock os with a blank flash? for me this worked, I just had to make sure that ALL files of the Rom image were included in the batch/shell script. For me with a reteu image one was missing (I think the vendor.002 or something like that), otherwise my phone was also stuck at boot.
Maybe that helps! good luck!
Blankflash can be complicated; at least it was for me. Do a Google search, maybe, for LMSA. It's a software program from Lenovo (make sure when you find it that it is lenovos website) and download this app on your windows PC. Normally, and with a little luck, you can put your phone in fastboot mode (it instructs you through all this, too), go-to Restore and LMSA will download the most recent firmware and flash you back to stock. Hope you have some luck! if not I can try to be more helpful with blank / because it took me months to figure out and find a compatible one but I still have it somewhere.
DrHelicopter said:
Hi there,
I had a similar problem with my phone a few days ago.
Did you try to flash back your stock os with a blank flash? for me this worked, I just had to make sure that ALL files of the Rom image were included in the batch/shell script. For me with a reteu image one was missing (I think the vendor.002 or something like that), otherwise my phone was also stuck at boot.
Maybe that helps! good luck!
Click to expand...
Click to collapse
I finally was able to flash stock rom again, re root and restore my apps with Titanium backup. I remembered a partially broken old phone I had and got it working. That relieved the stress of not having a phone and allowed me to work more calmly on my main phone. Still don't know why the twrp restore messed the phone up. Makes me bother why I'm using twrp for backups.
clintongsan said:
Blankflash can be complicated; at least it was for me. Do a Google search, maybe, for LMSA. It's a software program from Lenovo (make sure when you find it that it is lenovos website) and download this app on your windows PC. Normally, and with a little luck, you can put your phone in fastboot mode (it instructs you through all this, too), go-to Restore and LMSA will download the most recent firmware and flash you back to stock. Hope you have some luck! if not I can try to be more helpful with blank / because it took me months to figure out and find a compatible one but I still have it somewhere.
Click to expand...
Click to collapse
I tried LMSA. It had entries for several Moto G7 phones (plus, etc) but not the plain G7. Strange.
maybeme2 said:
I tried LMSA. It had entries for several Moto G7 phones (plus, etc) but not the plain G7. Strange.
Click to expand...
Click to collapse
I don't know if you still want to flash via fastboot, but there is a good guide for the g7 plus here .
You just need the last part, if your bootloader is working. Just keep in mind you need another image from lolinet, the standard G7 is codenamed 'river' as far as i know, so this should be the place for you.
And remember to check if all files (of the extracted image) are included in the 'flashfile.bat' to ensure the flash is complete, otherwise it maybe won't boot.
Hope this helps recovering your phone!
RE:
maybeme2 said:
I tried LMSA. It had entries for several Moto G7 phones (plus, etc) but not the plain G7. Strange.
Click to expand...
Click to collapse
Hmm, okay. That is strange but maybe you have the G7 Plus variant? I don't know that model but the regular G7 is codenamed to (river) xt1962-1. So if you boot into fastboot (from power off; volume down and power held until the fastboot screen appears), look for the third or fourth line down, it will read something like "Product/Variant: river XT1962-1 64GB..." just to ensure that you are looking at the right forum/device. If you are still having issues and if all else does not prove successful, let me know and I can share the blankflash that worked for me along with the best instructions from memory on how I did it. My phone was once bricked to the point where no screen came on at all and I thought it was a goner (actually did it to two seperate G7s as I was learning why Lineage isn't my favorite custom ROM at the time lol) so I know the blankflash I have will work but I would recommend it as a last measure due to the fact that any and all data will be wiped so you won't be able to hold onto anything that is on the device's storage, itself. Hope you got it fixed and wishin you luck!
---------- Post added at 11:13 PM ---------- Previous post was at 11:10 PM ----------
DrHelicopter said:
Hi there,
I had a similar problem with my phone a few days ago.
Did you try to flash back your stock os with a blank flash? for me this worked, I just had to make sure that ALL files of the Rom image were included in the batch/shell script. For me with a reteu image one was missing (I think the vendor.002 or something like that), otherwise my phone was also stuck at boot.
Maybe that helps! good luck!
Click to expand...
Click to collapse
Hey there; do you happen to have a page or website handy that explains blankflash and how the script runs? I remember there being so much confusion over it such as some people had me thinking I needed to find an external firehose program, codes, etc., and as it turned out I only needed the correct blankflash. I was able to fix my devices a couple of months ago but I was just still a bit curious as to the behind-the-scenes details that the software runs in order to be such an awesome fix. Thanks, in advance. Take care!
Fortunately I was finally able to download the latest stock android 9 from Lolinet and flash it to the phone with fastboot. I rooted again with Magisk, flashed copypartitions, and restored my apps and data from a recent Titanium Backup. So I am good now. But, it was very stressful for 2-3 days because I'm not an expert.
Yes the phone is river XT1962-1 64GB, but for some reason my LMSA did not recognize it. Extremely strange but unimportant now since I'm now back in business. I don't know for sure what happened but I suspect it may have had something to do with Moto G7's A / B partitions getting mixed up.
LMSA needs to be updated if there is no Moto g7 option. I just checked on my install and the option was there.
Has anyone ever actually used a TWRP restore? I have tried numerous times to no avail. It's rather annoying but I hope it'll get fixed one day to do backups/restores...same goes for adb backups.
clintongsan said:
Has anyone ever actually used a TWRP restore? I have tried numerous times to no avail. It's rather annoying but I hope it'll get fixed one day to do backups/restores...same goes for adb backups.
Click to expand...
Click to collapse
I've successfully used twrp restores several times on previous phones. Saved me many times. But they were all on Nexus phones and earlier android versions.
The only time I used it on the Moto G7 I got stuck in a bootloop. Maybe it's the newer A B dual partitions causing my problems. Don't know for sure. But without a dependable system restore capability, twrp loses its value to me.
Now I am even afraid to try another twrp restore as a test in case I get thrown back into a boot loop. See my note on
https://forum.xda-developers.com/g7-plus/development/recovery-twrp-3-3-0-moto-g7-plus-t3930050/page9