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
Related
So, I figured my mistakes can save some others some grief. Part of the problem is that this phone is relatively new and information is scattered all over so it is hard to find all that is necessary at a singe source.
I had the Amazon Prime 8 gb with 6.1 firmware. I first installed the SP Flashing tool and flashed the TWRP_Scatter_R1_Prime.zip. I already had the MTK preloader drivers installed. I then flashed the TWRP scatter file, Download Only, and all went well. I did a complete back up to my SD card. I wanted to run the debloating scripts at this point, but I had missed installing them on the SD card, so I installed SuperSU from TWRP after pressing Vol+ and power to reboot. Then I did a regular reboot. The phone booted just fine so I added the scripts to the SD card. I then rebooted into TWRP and ran all three debloating scripts and rebooted. Again, all went well.
Here is where I made my First Error. I reset the phone to factory defaults so I could go through the setup procedure. One of the video guides suggested this. I am assuming that one of the debloat scripts deleted the setup procedure since I now wound up in a perpetual loop where the phone kept telling me it could not run set up.
So, as I had made a complete backup in TWRP, I rebooted into TWRP and did a restore from my back up file. FAIL. No idea why. I then went to the video outlining the procedure for restoring a bricked phone using SP Flash and the correct txt file for flashing the default 6.4 firmware, being told that updating was OK. ERROR. SP Flash said I needed to re-run using the setting Format+Download.
Second Mistake. Half way through, another ERROR. And I now had a total brick. No recognition on a PC; no TWRP boot; no power up no matter how long I held the power button. DOA.
Please weigh in on anything I am missing or am mistaken on. Also, help other users in pointing out anything I did wrong and missed. At least this is only $50. But I am skipping this phone and staying with my old model.
chas0039 said:
So, I figured my mistakes can save some others some grief. Part of the problem is that this phone is relatively new and information is scattered all over so it is hard to find all that is necessary at a singe source.
I had the Amazon Prime 8 gb with 6.1 firmware. I first installed the SP Flashing tool and flashed the TWRP_Scatter_R1_Prime.zip. I already had the MTK preloader drivers installed. I then flashed the TWRP scatter file, Download Only, and all went well. I did a complete back up to my SD card. I wanted to run the debloating scripts at this point, but I had missed installing them on the SD card, so I installed SuperSU from TWRP after pressing Vol+ and power to reboot. Then I did a regular reboot. The phone booted just fine so I added the scripts to the SD card. I then rebooted into TWRP and ran all three debloating scripts and rebooted. Again, all went well.
Here is where I made my First Error. I reset the phone to factory defaults so I could go through the setup procedure. One of the video guides suggested this. I am assuming that one of the debloat scripts deleted the setup procedure since I now wound up in a perpetual loop where the phone kept telling me it could not run set up.
So, as I had made a complete backup in TWRP, I rebooted into TWRP and did a restore from my back up file. FAIL. No idea why. I then went to the video outlining the procedure for restoring a bricked phone using SP Flash and the correct txt file for flashing the default 6.4 firmware, being told that updating was OK. ERROR. SP Flash said I needed to re-run using the setting Format+Download.
Second Mistake. Half way through, another ERROR. And I now had a total brick. No recognition on a PC; no TWRP boot; no power up no matter how long I held the power button. DOA.
Please weigh in on anything I am missing or am mistaken on. Also, help other users in pointing out anything I did wrong and missed. At least this is only $50. But I am skipping this phone and staying with my old model.
Click to expand...
Click to collapse
With format+download make sure preloader is not checked....
For anyone interested, BLU really doesn't want to repair the phone. Their regular rep said that I needed to send it back to Amazon as it was too early for them to repair it even with the warranty voided. I got a supervisor and they said that actually, they would fix it and the current cost with no physical damage would be $28.50. So with $4 shipping on my part I am back in business.
So anyone with a 6.6 brick has an option that is not too bad.
chas0039 said:
For anyone interested, BLU really doesn't want to repair the phone. Their regular rep said that I needed to send it back to Amazon as it was too early for them to repair it even with the warranty voided. I got a supervisor and they said that actually, they would fix it and the current cost with no physical damage would be $28.50. So with $4 shipping on my part I am back in business.
So anyone with a 6.6 brick has an option that is not too bad.
Click to expand...
Click to collapse
If you had a Prime version and it was within the first 30 days of purchase, you could've send it back to Amazon to get a replacement, no questions asked, for free (this only works once by the way). Either way, glad to see Blu is willing to fix our mistakes. Maybe request that your R1 is restored with older, non-6.6 firmware. Probably won't work, but it's worth a try.
But do note that if you send it back to Blu for repair, it is very likely that when you get it back it will have the latest 6.6 update on it that disables SPFT so you won't have root, be able to disable ads, flash non-prime rom or any of that stuff.
yaconsult said:
But do note that if you send it back to Blu for repair, it is very likely that when you get it back it will have the latest 6.6 update on it that disables SPFT so you won't have root, be able to disable ads, flash non-prime rom or any of that stuff.
Click to expand...
Click to collapse
My guess is, they will load it with the factory shipped image, unless QA loads the update during testing, but perhaps they wont.... Kinda like a roll of the dice on this one...
I found a similar problem on an other mtk device thread. Where either through formating or failed flashing that you end up in am appearently dead device. If it is the same, it is from the battery stats getting woped out. And the solution is to leave it plugged in for two to three days then try to connect to spft again.
I am skepticle but what harm could if do to try.
I beleive the boot ROM section is not writeable and not formatable. (The first 2mb of device chip) so, it should be seen by PC as some kind of com port
I did not have success flashing pree loader with spft but @Persuasion89 has recovered his phone and as soon as he replies to my request for a file list you should be all set for a repair.
This is why I just paid the extra $50 and bought the ad free version. $110 is still a great price for the device, and no hassles with any ad removing nonsense
mrmazak said:
I found a similar problem on an other mtk device thread. Where either through formating or failed flashing that you end up in am appearently dead device. If it is the same, it is from the battery stats getting woped out. And the solution is to leave it plugged in for two to three days then try to connect to spft again.
I am skepticle but what harm could if do to try.
I beleive the boot ROM section is not writeable and not formatable. (The first 2mb of device chip) so, it should be seen by PC as some kind of com port
I did not have success flashing pree loader with spft but @Persuasion89 has recovered his phone and as soon as he replies to my request for a file list you should be all set for a repair.
Click to expand...
Click to collapse
Im sorry for the delay, ive been trying to drop a transmission into my car but I'll try to get a list together for you tonight. I did some manual tinkering with my scatters and frankenstein work with file lists so i'll need some time, but ill get back to you when i can.
I wish I have seen this before bricking mine......
How did you brick it? I have rooted and twrped two of them now without any issues. What did you do that people need to be careful to NOT do?
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was the first boot I expected a decently long wait, after about 25 minutes I followed the guide's instructions for Verizon since it did say some Verizon users were experiencing long first boot times. I took the battery out like it said, put it back in, then proceeded to fastboot boot2.img, like the guide said. After letting it sit for an hour this time, I got the idea that something was obviously wrong. After multiple attempts with no success I tried to fix it myself. So far I have learned that on the fastboot screen it says my bootloader is locked again, even after unlocking it. I have tried flashing TWRP as a recovery, just to at least have a recovery boot, that does not work either unfortunately. So as of right now, all I have is a v20 that has no OS, a locked bootloader, no way of booting recovery, I can fastboot with no ADB, and its virtually a paperweight. If anyone has a solution to at least get back to Stock, I would greatly appreciate it! Thanks!
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Did you get it fixed?
frome901 said:
Did you get it fixed?
Click to expand...
Click to collapse
He has not responded to my pm
What roms can we use with dirty santa root?
me2151 said:
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Click to expand...
Click to collapse
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
TheDantee said:
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
Click to expand...
Click to collapse
In his case we needed to redo from step 3.
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc) http://www.hardreset.info/devices/lg/lg-v20/
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Bricked T-Mobile v20
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was flash a new rom on it then i get boot loop with TWRP. so i decide to OEM LOCK again after that everything was stuck on my phone just boot loop with LG so any solutions please help me...... THx u for help me.
Kinda nerve wrecking to read about all these "bricked" phones popping up after trying this method lol.. Perhaps I'll just wait until a more tried and true way comes out...
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
For anyone that isnt on sprint that has "bricked" their phone. There are kdz's that will allow you to reflash back to 'stock". Someone had an issue with the kdz, but it was an easy fix. If you failed the process, it can be restored. Just if it doesnt want to boot, just lock and unlock the bootloader...
If your phone doesnt have a kdz, I know TeamDev is working on a custom kdz for such phones. Don't bug him if it isn't finished as I type this.
Anyone that can't get into TWRP, or has failed the process. Either start back at step 3, or if you have TWRP installed but can't get to it, the manual way to get into TWRP is a pain.
Keep your back cover off and hold the volume down button for ease. Now press the power button and as soon as you see an LG logo, let go and repress the power button. Its tricky.... If you get the corrupted screen, pop your battery out and put it back in quick and repress volume down and power. Usually if Im quick enough the first LG logo will hang a lot longer than usual and that gives me time to enter TWRP. A factory reset screen will pop up. Hit Yes twice.
Please help urgent
lcovel said:
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc)
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Click to expand...
Click to collapse
Please can u help ke unbrick mine i bought this mobile in my country its expensive and has no support. I have tried all tools but still getting the error model unknown please help sir
Jaistah said:
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
Click to expand...
Click to collapse
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
yuppicide said:
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
Click to expand...
Click to collapse
it means dirty santa root got a high posibility rate of bricking a device compared to other root methods for other devices and if you have no experience in bricking phones before then you're screwed if it happens to you
Actually, if you follow the directions, almost none of the problems create a true brick-- which means unrecoverable. For most of the cases, you might get a soft brick, meaning you have to back out, use a KDZ to repair it or reflash something else, or start over from scratch and try again-- but usually (maybe with some help from here) you can pull the phone back into a usable state.
I would hazard to guess for the vast majority the process works fine, maybe with a hiccup, but I've not seen many reports of a truly unrecoverable brick from this method. It's complicated, yes, and you need to be ready to read a LOT to understand what's going on, but it seems pretty difficult to end up with a $700 paperweight with this.
So i have been trying tonroot my sprint lg v20 and everytime i try and go to the phone on mobile terminal to enter id
Then enter the apply patch /system/bin/atd /storage/emulated/0/dirtysanta i get this message and i cant go to step 2 to boot into recovery
Any help would be appreciated: i have a sprint v20 and i wanted to know if i have to flash the stock sprint rom or can i just flash lineage rom following this guide? I have it running on AT&T and i want to keep it on AT&T...
can you please assist
Could you help out, please? I don't believe I have hard bricked my LG V20 H910. However, I have read and tried all of the unbrick info out. It seems my screw up is unique. I completed dirty Santa then went to flash a custom. in the boot between that. I get a black screen and cant do anything even download mode will not come up. My PC does make its usual noises when i connect or disconnect, but my phone does nothing.
Ok, I managed to brick mine too. It's a VS995, it was running stock 1AC. I used the LGUP tool to downgrade it to VS99512A, and then did Dirty Sanata and TWRP. After booting into TWRP I decided to try lineage OS with Android 8.0, I did not make a backup of the Stock ROM, which was very stupid. Lineage OS 15.1 flashed but I had no cell service so I panicked and instead of wiping it in TWRP and using the backup of stock I should have created, I just opened LGUP and tried to downgrade it back to stock VSS99512A. Well LGUP said it worked, but when it went to boot it would hang at the Verizon logo with 4 pastel dots. Device manager could see an ADB device and I could connect to it with ADB. So I did and read the logcat. I could see it was trying to update as part of the rollback, but it appeared that some components from Android 8x could not be "upgraded" to Andoird 7.x. There was a repeated error about failing to update SQLite instance version from 3 to 1.
The one feature that could fix this is if the refurbish function worked with any of the VS995 KDZ files we all have access to. But alas, none work instead we only get the upgrade function... or so I thought. Somewhere in my search for the past 2 weeks I found a modified LGUP https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
**Please be warned what I did was absolutely ****ing stupid, and it was sheer luck I didn't screw anything up.**
From what I can tell if you only flash ("LGUP Upgrade") the KDZ from the same model it never clears the partition it just adds to it. My problem was there was stuff from lineage OS 15 stuck on one of the partitions that was making the rollback to stock fail because it kept saying it couldn't update the SQLLite DB from 3 to 1. So no "upgrade" within LGUP would work because the upgrade function does not clear internal storage. But the link above is to a version someone modded so you can force a partition update from any KDZ onto the system. So I started playing around with forcing KDZs from other models onto my VS995, and I noticed when using the Partion DL function with non-VS995 KDZ files it would say something about the partition changing. All I can assume is that the partition layout is so different on each model and it forces LGUP to re-partition the storage.
**Again I state for the record this was stupid, and I'm only fortunate it worked.**
I forced Partion DL of H91510d_00_VTR_CA_OP_1110.kdz, then H990N10b_00_OPEN_HK_DS_OP_1017.kdz, then back to VS99512A_06_1114_ARB00.kdz, then when it booted it gave the Verizon hello, and moved on finally but the setting service kept crashing while it was trying to load the Secure Boot screen. So I yanked the battery and went into the boot menu and did the Factory Reset function, and it worked.
Lesson learned, always make a backup and don't be so hasty to use tools that aren't fully functional (LGUP).
Perhaps what I've done may help others, maybe I've found out how to reimage or unbrick our V20s. Or maybe I just got really stupid lucky.
My tmobile LG k20 plus phone has a boot loop and will not start, this happened when I copied a file to the main directory of my phone, instead of merging the files it deleted the system folder, I tried to fix it by reinstalling twrp and it worked, after flashed twrp I installed a fresh SuperSU ROM and when I did the boot loop did not go away and in addition to this my computer will no longer find my phone through ADB or fastboot, if you can help I will be amazed and quite happy, I'm new here so any help is appreciated
bump:fingers-crossed:
megamind994 said:
My tmobile LG k20 plus phone has a boot loop and will not start, this happened when I copied a file to the main directory of my phone, instead of merging the files it deleted the system folder, I tried to fix it by reinstalling twrp and it worked, after flashed twrp I installed a fresh SuperSU ROM and when I did the boot loop did not go away and in addition to this my computer will no longer find my phone through ADB or fastboot, if you can help I will be amazed and quite happy, I'm new here so any help is appreciated
Click to expand...
Click to collapse
did u ever get it figured out? i am in the same boat grr
I found a program called lgup which was able to fix the phone, it's capable of flashing a new rom onto a soft bricked phone. Sadly I don't recall any specifics but on a quick search for "lgup lg k20 plus" you should be able to find what you're looking for with relative ease. Also, you may want to consider making your own thread on the future... It has been 3 years
megamind994 said:
I found a program called lgup which was able to fix the phone, it's capable of flashing a new rom onto a soft bricked phone. Sadly I don't recall any specifics but on a quick search for "lgup lg k20 plus" you should be able to find what you're looking for with relative ease. Also, you may want to consider making your own thread on the future... It has been 3 years
Click to expand...
Click to collapse
thanks
Yeah. Sorry for the late reply given you guys found the fix by now, but yes, generally with the sort of severe mishaps from editing or accidental deletion of certain system files or directories, sometimes a dirty flash or even a totally clean flash after performing data ave system partition wipes, will just not fix or restore the device.
You would then need to do a complete stock image reflash either using LGUP or the official LG software recovery tool. If you know what you're doing, you could skip over reflashing stock in its entirety, if say you know the problem has only to do with a particular protected partition like modem, EFS, etc. But generally good practice to just recover all the stock partitions, refresh the device software to factory conditions, reflash your bootloader and recovery images, root STOCK or install custom ROM, so on and so forth.
If you're a frequently curious tinkerer, making backups will be crucial to your sanity.
Problem is in the title. Here are the Cliff's Notes:
1) got Moto E4 from Textnow
2) fastboot boot TWRP.img (cant recall which image I used but pretty sure it was proper. if this makes a difference I can dig out the TWRP I used and attach it, but I really cannot recall which one it was. Pretty sure I got it from xda though, not the official TWRP page)
3) took TWRP backup of bone-stock device.
4) unlock bootloader at Motorola.com
5) check out the custom roms and found out about the LTE problem. Seanstars fix didnt work for me on several roms, but in his defense I may have done something wrong. I didnt want to mess with it anymore and decided to go back to stock.
6) I found out that I lost my bone-stock-TWRP backup through my own idiocy. I honestly have no idea how I got back to stock but I managed it. Seems to be awful hard to get a stock rom to work with. I must not be looking hard enough but it seems like all the links for Perry stock roms here are dead.
Now to the problem.... after all that I cant get OTA updates. I get notifications, the update downloads,, but no joy.
Device does *not* restart after the update downloads.
Manual restart begins the update process, but then I get the Android on the Operating Table screen. I relocked the bootloader thinking that might be the issue, but now I fear that there is some sort of signature verification issue that is stopping the update.
Trying to give relevant info from the bootloader:
Baseband: M8920_15000.280.06.58.02R PERRY_NA_CA_CUST
Product/Variant: perry XT1766 16GB P3B
I really dont know where to go from here though. Any help is appreciated, thanks in advance.
knoober said:
Problem is in the title. Here are the Cliff's Notes:
1) got Moto E4 from Textnow
2) fastboot boot TWRP.img (cant recall which image I used but pretty sure it was proper. if this makes a difference I can dig out the TWRP I used and attach it, but I really cannot recall which one it was. Pretty sure I got it from xda though, not the official TWRP page)
3) took TWRP backup of bone-stock device.
4) unlock bootloader at Motorola.com
5) check out the custom roms and found out about the LTE problem. Seanstars fix didnt work for me on several roms, but in his defense I may have done something wrong. I didnt want to mess with it anymore and decided to go back to stock.
6) I found out that I lost my bone-stock-TWRP backup through my own idiocy. I honestly have no idea how I got back to stock but I managed it. Seems to be awful hard to get a stock rom to work with. I must not be looking hard enough but it seems like all the links for Perry stock roms here are dead.
Now to the problem.... after all that I cant get OTA updates. I get notifications, the update downloads,, but no joy.
Device does *not* restart after the update downloads.
Manual restart begins the update process, but then I get the Android on the Operating Table screen. I relocked the bootloader thinking that might be the issue, but now I fear that there is some sort of signature verification issue that is stopping the update.
Trying to give relevant info from the bootloader:
Baseband: M8920_15000.280.06.58.02R PERRY_NA_CA_CUST
Product/Variant: perry XT1766 16GB P3B
I really dont know where to go from here though. Any help is appreciated, thanks in advance.
Click to expand...
Click to collapse
A number of partitions need to be pure stock for OTAs to work on Moto devices - including many that are not normally mounted. Likely one or more was altered by previous tinkering. Obviously system (never mounted r/w) and recovery; data must not have had dm-verity disabled. Etc, etc.
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!!)