Database Users

Certain Roms will not boot anymore?

As of yesterday my phone stopped booting certain roms! Im rooted with all the latest twrp, vendor, bootloader, etc. I never encountered this problem and Ive been rooted since day one. I have several custom roms on my phone and only "Resurrection Rom" seems to boot without any problem all the other (Purenexus, benzorom, chroma, exdous) Roms get past the google screen and stay stuck in the boot up screen.. Am I missing something?? Ive checked everything I could. Ive downgraded twrp. Im stump any insight on this would be greatly appreciated..

Info
big nu said:
As of yesterday my phone stopped booting certain roms! Im rooted with all the latest twrp, vendor, bootloader, etc. I never encountered this problem and Ive been rooted since day one. I have several custom roms on my phone and only "Resurrection Rom" seems to boot without any problem all the other (Purenexus, benzorom, chroma, exdous) Roms get past the google screen and stay stuck in the boot up screen.. Am I missing something?? Ive checked everything I could. Ive downgraded twrp. Im stump any insight on this would be greatly appreciated..
Click to expand...
Click to collapse
check Kernel compatibility if you update internal rom
- reinstall kernel
:good:

big nu said:
As of yesterday my phone stopped booting certain roms! Im rooted with all the latest twrp, vendor, bootloader, etc. I never encountered this problem and Ive been rooted since day one. I have several custom roms on my phone and only "Resurrection Rom" seems to boot without any problem all the other (Purenexus, benzorom, chroma, exdous) Roms get past the google screen and stay stuck in the boot up screen.. Am I missing something?? Ive checked everything I could. Ive downgraded twrp. Im stump any insight on this would be greatly appreciated..
Click to expand...
Click to collapse
Same with me dude
https://tapatalk.com/shareLink?url=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php?t=3357580&share_tid=3357580&share_fid=3793&share_type=t
Here's my thread... I have tried everything even going back to stock MHC19Q and starting fresh... RIP 6P

MoistPicklez said:
Same with me dude
https://tapatalk.com/shareLink?url=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php?t=3357580&share_tid=3357580&share_fid=3793&share_type=t
Here's my thread... I have tried everything even going back to stock MHC19Q and starting fresh... RIP 6P
Click to expand...
Click to collapse
Never figured anything out? I think im having this same issue with my 6p i tried flashing pure nexus, xTraFactory, and Stock+ but for me it just bootloops and once out of 20 attemps pure nexus will get to the colored logo then freeze and reboot. I long deleted Ressurrection Remix because it was my daily driver and already had a backup made. That went to sh*t though when my backup bootlooped as well so now i have a 6p i can only boot into recovery and bootloader. My laptop with fastboot installed needs a new charger so i use my moms computer to put zips on my phone but i really doubt she will let me install anything on it at all :/. I dont want to flash the factory image and bootloop still though when i get a charger. Ill see if I can boot back into rros fresh.

Coeur Brisé said:
Never figured anything out? I think im having this same issue with my 6p i tried flashing pure nexus, xTraFactory, and Stock+ but for me it just bootloops and once out of 20 attemps pure nexus will get to the colored logo then freeze and reboot. I long deleted Ressurrection Remix because it was my daily driver and already had a backup made. That went to sh*t though when my backup bootlooped as well so now i have a 6p i can only boot into recovery and bootloader. My laptop with fastboot installed needs a new charger so i use my moms computer to put zips on my phone but i really doubt she will let me install anything on it at all :/. I dont want to flash the factory image and bootloop still though when i get a charger. Ill see if I can boot back into rros fresh.
Click to expand...
Click to collapse
Well this is quite an old post to awaken but to be short and Frank I had to send my device in to have the motherboard replaced because the 6p still has hardware issues whether it's Huawei's (prolly spelled wrong.) fault or Google's, regardless I just got the motherboard replaced and sold the device immediately because I didn't want to have another paper weight in my hands I now have an essential phone and it is dare I say the most comfortable phone I've ever had. That being said I hope you can Rectify your issues here but you'll have to go through either Huawei or Google, and get one of the two to help you out with a replacement.

This kind of happened to me too. I just updated TWRP and all flash are fine now. Hope this will help someone

MoistPicklez said:
Well this is quite an old post to awaken but to be short and Frank I had to send my device in to have the motherboard replaced because the 6p still has hardware issues whether it's Huawei's (prolly spelled wrong.) fault or Google's, regardless I just got the motherboard replaced and sold the device immediately because I didn't want to have another paper weight in my hands I now have an essential phone and it is dare I say the most comfortable phone I've ever had. That being said I hope you can Rectify your issues here but you'll have to go through either Huawei or Google, and get one of the two to help you out with a replacement.
Click to expand...
Click to collapse
Solved it today it was because I tried restoring an old backup with an old version of twrp that has a fatal bug when you restore an EFS. I was truly relieved

Screen Not Responsive After Flash ..... +

Hey,
I've been on quite a journey since I attempted to flash the Treble rom for newbies. My phone eventually ended up as DFU'd but, I brought it back to life after a following the DFU Unbrick - Disassembly guide. After doing this, the screen was not responsive to touch at all at the Welcome screen of the EDU ROM. So, my adventure continued as I took the phone apart several times again to make certain things were connected, not damaged, etc..
After flashing TWRP I concluded the screen itself must be fine because I could use TWRP using the screen/touch. I have since tried flashing several different roms, tried many combos of unlocking the bootloader (again, because I assume it was already unlocked due to the bootloader warning screen of can not check for corruption message), tried flashing bootstack and the stock rom from DrakenFX. Used MiFlash, EDM Tool to flash various items.
Each time and currently, when it boots to the Welcome screen it does not respond to touch.
Can anyone please help me with this?
Thank you!

I remember this happened to me some years ago with a different phone, and it was a bad flash.
I resolved it by flashing the stock firmware again.
What did you flash with MiFlash? Stock firmware untouched? You must do this, try with B35 untouched. Don't flash stuff with TWRP.

Untouched? Is there anything on here like that?

https://androidfilehost.com/?fid=962187416754472312 B35 A2017U
https://androidfilehost.com/?fid=746010030569960045 B10 A2017G
https://www.androidfilehost.com/?fid=818070582850490196 B14 A2017CN
Those are "untouched" system images. Replace recovery.img with a proper TWRP version before flashing:
https://androidfilehost.com/?fid=673956719939822011

bornlivedie said:
https://androidfilehost.com/?fid=962187416754472312 B35 A2017U
https://androidfilehost.com/?fid=746010030569960045 B10 A2017G
https://www.androidfilehost.com/?fid=818070582850490196 B14 A2017CN
Those are "untouched" system images. Replace recovery.img with a proper TWRP version before flashing:
https://androidfilehost.com/?fid=673956719939822011
Click to expand...
Click to collapse
Yeah, unfortunately the very first link (since I am in the USA and have a U version) is the very stock EDL version I used with MiFlash rightg after I was successful getting the phone out of DFU. I have tried flashing it twice after and still nothing.
Thank you for helping!!!

djprez said:
Yeah, unfortunately the very first link (since I am in the USA and have a U version) is the very stock EDL version I used with MiFlash rightg after I was successful getting the phone out of DFU. I have tried flashing it twice after and still nothing.
Thank you for helping!!!
Click to expand...
Click to collapse
Sad to hear that... Maybe you can try again? Who knows, with a little bit of luck...
Or try another version, like this one:
https://www.androidfilehost.com/?fid=890129502657579386
btw, did you try every single spot in your screen while in TWRP? Maybe some pins in the connector are broken and some parts work and others doesn't?
And for the sake of it, you could try discharging your battery completely.
Last thing I can think of... is to restore the stock recovery and apply the official update via sdcard:
https://www.dropbox.com/s/xy7nd252f3rcm5y/338450B3220A2017UV1.1.0B35(SD card software).zip?dl=0
It was taken from here:
https://www.zteusa.com/axon-7#support

bornlivedie said:
Sad to hear that... Maybe you can try again? Who knows, with a little bit of luck...
Or try another version, like this one:
https://www.androidfilehost.com/?fid=890129502657579386
btw, did you try every single spot in your screen while in TWRP? Maybe some pins in the connector are broken and some parts work and others doesn't?
And for the sake of it, you could try discharging your battery completely.
Last thing I can think of... is to restore the stock recovery and apply the official update via sdcard:
https://www.dropbox.com/s/xy7nd252f3rcm5y/338450B3220A2017UV1.1.0B35(SD card software).zip?dl=0
It was taken from here:
https://www.zteusa.com/axon-7#support
Click to expand...
Click to collapse
Yeah, the entire screen works perfectly in TWRP. I disassembled it several times before when I thought I may have put it back together wrong or damaged something so, the battery was removed those several times therefore, no power.
I'll try the stock above. I'm actually trying another stock rom atm --- flashing from sdcard

djprez said:
Yeah, the entire screen works perfectly in TWRP. I disassembled it several times before when I thought I may have put it back together wrong or damaged something so, the battery was removed those several times therefore, no power.
I'll try the stock above. I'm actually trying another stock rom atm --- flashing from sdcard
Click to expand...
Click to collapse
Well, EUREKA! I found I had saved the first files you were supposed to load when the Axon was first unlocked ( file name STEP_1_3-B20_FULL_OTA). Flashed it and the screen works fine. Now, I have to remember how to update it...lol I've unlocked the bootloader in Developer mode and I should be on my way..... fingers crossed.

djprez said:
Well, EUREKA! I found I had saved the first files you were supposed to load when the Axon was first unlocked ( file name STEP_1_3-B20_FULL_OTA). Flashed it and the screen works fine. Now, I have to remember how to update it...lol I've unlocked the bootloader in Developer mode and I should be on my way..... fingers crossed.
Click to expand...
Click to collapse
Strange.
Nevertheless, congratulations. Happy for you.

Well, it's great that I now know the screen/hardware is fine but, I am unable to get any further than version B20. OTA doesn't work, the other files to flash (STEP_4-B20_to_B27 and STEP_5-B27_to_B29) won't flash and get aborted due to it expecting a certain version. I've tried DrakenFX Bootstack and then Stock System and it boots to the Welcome screen but the screen is no longer responsive again.
I have been at this all day again and it's shaping up another all night too. I am so baffled!

Restore to stock firmware your phone came shipped with.After that update trough ota or sd card package and maybe dont flash Treble again,its broken

djprez said:
Well, it's great that I now know the screen/hardware is fine but, I am unable to get any further than version B20. OTA doesn't work, the other files to flash (STEP_4-B20_to_B27 and STEP_5-B27_to_B29) won't flash and get aborted due to it expecting a certain version. I've tried DrakenFX Bootstack and then Stock System and it boots to the Welcome screen but the screen is no longer responsive again.
I have been at this all day again and it's shaping up another all night too. I am so baffled!
Click to expand...
Click to collapse
i wish i had seen this sooner, because i have this same exact problem on one of my boards. it will update perfectly to any of the MM sd card update files (see rootjunkys bl unlock video, thanks @Tomsgt) but the board/phone will not retain touch functionality on anything higher than mm b29. i had lost my imei on that board, and actually swapped to another one despite eventually regaining it simply bc i wanted to be on Oreo ROMs. if you find a fix, id love to know about it. i flashed and reflashed every update, sd card versions, edl versions, and OTA updates to no avail. Nougat or above, touchscreen didnt work... mine was a gold a2017u. good luck, man. im glad im not crazy.

Sorry to bump an old(er) thread I started. I wanted to ask if anyone has found a solution to this issue yet?
I have since tried updating using OTA to Nougat and the screen doesn't respond so, I had to flash back to Marshmallow B29. Thank you to anyone who might have an idea!

[SOLVED] Cascading failures leading to bootloop and softbrick

Hello all. I am about done with this phone. Let me give you a quick timeline.
I had a bootloader error, so I flashed the NPN25.137-35 images to get it working
I used it for about 1 week, installing all of the OTA security updates
One morning, my phone had restarted (I know because "You must enter your pattern after a restart")
Over the course of this day, google apps starting force closing and opening some of them would soft reboot the phone.
The next day, random apps were doing it too
Finally, after one crash, the OS never came back up, it was bootlooping
Upon a hard restart, the phone only boots into bootloader.
This is where I am now. I have downloaded NPN...35-5, NPNS...93-10, and NPNS...92.14. Unfortunately, trying to flash any of these give me a "prevaildation failed security update downgrade" error on every partition I try to flash. The phone just bootloops when I try to restart it.
Things I have tried:
Using fastboot to manually install one of the 3 packages mentioned above.
Using a toolkit to automate the install of the 3 packages.
Using Motorola Device Manager (Never got it to launch)
Flashing the blankflash bin (No usable image file found)
Android OEM unlock setting was not set before this crash, so I cannot unlock the bootloader.
Praying to various deities.
Unzipping the packages, editing the *info.txt file into androidinfo.txt and rezipping to use as an update package (Invalid info.txt error)
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
=~=~=~=~= SOLUTION FOUND =~=~=~=~=
This may not be a good solution for anyone else that has this issue, but recently Oreo came out and the OTA update was captured. I was able to flash the new OTA because it had a higher security level and at least got the phone bootable.

Do you know what software channel you were on? E.g. retus, retla, etc? If your phone was completely up to date with the OTA, then you can't use a firmware version of less than 92-14 or 93-14. Whether or not you use 92 or 93 depends on the channel.
Locked bootloader limits other possibilities unfortunately.

Retus. I can't guarantee it, but that looks familiar to me, like I had seen it somewhere in the "about phone" section. Is there a released Stock image that has the current security patch? I can't find it on XDA and I'm not trusting androidfixfiles.info or a link in a youtube video.

93-14 hasn't been leaked yet. So you'll be stuck for now.

Kilo__ said:
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
Click to expand...
Click to collapse
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.

pastorbob62 said:
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.
Click to expand...
Click to collapse
The phone was completely stock. It has the stock recovery and bootloader.

Kilo__ said:
The phone was completely stock. It has the stock recovery and bootloader.
Click to expand...
Click to collapse
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?

pastorbob62 said:
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?
Click to expand...
Click to collapse
I've tried that with a locked bootloader myself, it doesn't allow a non-signed image to boot. OP should give it a go as a 'hail Mary' attempt, but I wouldn't be holding my breath.

I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.

jhs39 said:
I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.
Click to expand...
Click to collapse
I agree. :good:

While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what

Kilo__ said:
While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what
Click to expand...
Click to collapse
Try flashing just the stock recovery, as it sounds like that is corrupt. Ideally you'd want to get a recovery that was the same build as you were on after all the OTAs had installed. At least you'd hope that that would give you the factory reset option.
If that doesn't work, there's fastboot commands to erase user data, cache, which would be pretty much what a factory reset would do. Hope you had your data backed up.

Oreo OTA came out recently. Someone grabbed the update file and uploaded it. I was able to flash it and get the phone to boot. The verdict is still out on if it'll be stable.

How do I fix a bootloop?

The phone is a Moto g7, Verizon river xt1962-1, rooted with Magisk and TWRP.
I wanted to update to Magisk 19.4, so I made a TWRP backup and ran the unroot patch and went back to 19.3, but I still had the problem, so I decided to restore from the backup. After the backup, I am stuck in a bootloop, the whole "Your device is unlocked and cannot be trusted" screen over and over. I can get into TWRP, but no backup that I have tried will fix the boot loop. I tried a few things that just seemed obvious to me, clearing the cache and whatnot, but I am still stuck. I have adb and fastboot at the ready, but I don't know where to go from here.
I do not even know what build I am running, I cannot get into System / About to see, and I am not savvy enough to know any other way to find out. I know that it was current stock, missing only the most recent patches.
Is there a way that I can restore my phone? I would be grateful for any help. Damn, I love this g7 so much more than the Note phones that I had been using for years, but I was at least a little familiar with them. Thanks for any help.

Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!

SmilingPerson said:
The phone is a Moto g7, Verizon river xt1962-1, rooted with Magisk and TWRP.
I wanted to update to Magisk 19.4, so I made a TWRP backup and ran the unroot patch and went back to 19.3, but I still had the problem, so I decided to restore from the backup. After the backup, I am stuck in a bootloop, the whole "Your device is unlocked and cannot be trusted" screen over and over. I can get into TWRP, but no backup that I have tried will fix the boot loop. I tried a few things that just seemed obvious to me, clearing the cache and whatnot, but I am still stuck. I have adb and fastboot at the ready, but I don't know where to go from here.
I do not even know what build I am running, I cannot get into System / About to see, and I am not savvy enough to know any other way to find out. I know that it was current stock, missing only the most recent patches.
Is there a way that I can restore my phone? I would be grateful for any help. Damn, I love this g7 so much more than the Note phones that I had been using for years, but I was at least a little familiar with them. Thanks for any help.
Click to expand...
Click to collapse
Try to flash the stock boot.img and you'll be fine. If you haven't got a stock boot.img you will find a backup of it in your /data partition (magisk does a backup of it by default). Just unpack the TWRP backup of your /data or download the latest firmware to get a boot.img

WoKoschekk said:
Try to flash the stock boot.img and you'll be fine. If you haven't got a stock boot.img you will find a backup of it in your /data partition (magisk does a backup of it by default). Just unpack the TWRP backup of your /data or download the latest firmware to get a boot.img
Click to expand...
Click to collapse
Mate, I can't thank you enough, now I am back up.
I took advantage of the oppotunity to do a Titanium backup and flash the latest firmware, since I was still running old security updates.
I am not sure why the TWRP backups caused a bootloop, that concerns me. I am diligent about making one before any significant change, and now I see that none of them were good. It might be that the backup I applied included boot, and somehow that caused an issue.
In any case though, thanks a million. I would PM you a beer, but they tend to go flat when they hit the first ATM gateway. Hops and TCP encapsulation don't seem to be compatible, especially at > 9600 baud ?

zenful said:
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
Click to expand...
Click to collapse
Thanks man, I really appreciate it! I did take advantage of the opportunity to update, something that had been bugging me for a while anyway.
I had updated Magisk to the beta through Manager, but a problem came up and I needed to step back to the stable version. That was where I messed up.
In a way though, it was just as well, since it forced me to spend a little time reading about the G7 ecosystem, something I really hadn't done much of yet. It used to be fun keeping up and flashing nightlies, etc, but over the past few years, it has got away from me. If it wasn't for a few specific things, I would almost stay stock. But I get uncomfortable thinking about the ridiculous amount of personal information a stock phone releases about us, so things like Signal and xPrivacylua are important to my sense of well being. Even if some of it is placebo.

zenful said:
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
Click to expand...
Click to collapse
Thanks man, I really appreciate it! I did take advantage of the opportunity to update, something that had been bugging me for a while anyway.
I had updated Magisk to the beta through Manager, but a problem came up and I needed to step back to the stable version. That was where I messed up.
In a way though, it was just as well, since it forced me to spend a little time reading about the G7 ecosystem, something I really hadn't done much of yet. It used to be fun keeping up and flashing nightlies, etc, but over the past few years, it has got away from me. If it wasn't for a few specific things, I would almost stay stock. But I get uncomfortable thinking about the ridiculous amount of personal information a stock phone releases about us, so things like Signal and xPrivacylua are important to my sense of well being. Even if some of it is placebo.

SmilingPerson said:
Mate, I can't thank you enough, now I am back up.
I took advantage of the oppotunity to do a Titanium backup and flash the latest firmware, since I was still running old security updates.
I am not sure why the TWRP backups caused a bootloop, that concerns me. I am diligent about making one before any significant change, and now I see that none of them were good. It might be that the backup I applied included boot, and somehow that caused an issue.
In any case though, thanks a million. I would PM you a beer, but they tend to go flat when they hit the first ATM gateway. Hops and TCP encapsulation don't seem to be compatible, especially at > 9600 baud
Click to expand...
Click to collapse
I'm glad to hear that! Don't worry about the beer!
I had similar issues with my Moto g6+... Either the /data encryption or Magisk is the reason for a failed backup. Both can cause a bootloop. But it's always good to have a stock boot.img.

I'm reading this because of the same issue in a Moto G7 Power. I haven't been able to make it restore a backup at all of either stock or custom. Oh, it will restore it just won't boot. I think it has something to do with the A&B system slots. We use a TWRP that was made for system with A&B slots but then we flash a copy partition zip That I'm not sure what it does. Maybe I should take it apart and have a look. . Has anyone been able to restore a backup in the G7?

arkansawdave74 said:
I'm reading this because of the same issue in a Moto G7 Power. I haven't been able to make it restore a backup at all of either stock or custom. Oh, it will restore it just won't boot. I think it has something to do with the A&B system slots. We use a TWRP that was made for system with A&B slots but then we flash a copy partition zip That I'm not sure what it does. Maybe I should take it apart and have a look. . Has anyone been able to restore a backup in the G7?
Click to expand...
Click to collapse
Do a full restore of boot, system and data.
Is data...
...encrypted => Then format data (not wipe!!) and reboot into system. When you see the "Welcome Screen" turn off your device and boot into TWRP again. Restore data and it should be fine.
...unencrypted => Then format data and restore data (w/o reboot!!)

Phone won't boot after TWRP restore

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