LG G6 (US997)
Bootloader is unlocked
Stock ROM (assumed to be 21C as I only have the zip and kdz files for this version)
Stock Recover; however, I can install "temporary" TWRP (due to encryption issues)
Issue: Stuck in fasboot mode after Magisk update (seems to be an issue with many).
Received a notification of a Magisk Manager update, so I updated it. Once completed, I opened the manager, and noticed there was an update to Magisk, so I updated it also before roboot. Tapped on the "Reboot" button, watched an error-free flash, and then the phone rebooted into Fastboot. All subsequent reboots are identical. All prior similar updates produced no issues, and I've not added any new modules since my last update. I have access to the stock recovery, but I've not tested its factory reset (yet) to determine if it's working properly, but on the surface it seems to be an option.
Note: My phone isn't recognized in ADB, but it is listed using "fastboot devices" so I assume I can use whatever fastboot commands are available.
UPDATE: Managed to install TWRP temporarily, and my low battery situation is resolved. That said, I flashed the latest Magisk uninstaller, wiped cache and dalvik, rebooted, and it went into fastboot. Went back into TWRP, flashed Magisk 20.1, rebooted, and it went back to fastboot.
What's next? Flash the ROM and boot.img?
And for what it's worth, I still cannot see my phone via "adb devices" but can via "fastboot devices"
Note: I'd rather perform a method that doesn't wipe my data, but my critical data is backed up, so nothing would be lost in a clean flash, even if a full restore would entail some work. From what I've read - and because I have the ROM-21C zip and kdz files - I apparently have other options; however, I'm not entirely sure what issues might arise, but I'm guessing I could 1) extract and flash the boot.img, then reinstall Magisk, or 2) flash the entire 21C ROM kdz, then reinstall Magisk, but I don't know what the pros and/or cons are to either approach.
Any suggestions or links that might prove helpful given I'm stuck in fastboot without access to ADB would be appreciated.
Thanks.
Edited to remove now-irrelevant information from my original post (resolved) that weren't specifically related to the Magisk update.
I thought i am the only one stuck in fastboot after updating magisk on my LG V20. I clean flash rom that i am currently using. Guess i have to stay on previous version of magisk
Faced the same problem with my stock LG G5 H850 8.0.
Using the LG tool "LG Bridge" and performing an update using it repaired my device and i was able to boot again without any data loss.
I'm now trying to install the 20.2 on a second H850 using latest TWRP with no success. (Digest failed to natch on... .Aborting zip install: Digest verification failed Error installing zip file ...)
Is this because I'm running 8.0?
toot-217 said:
Faced the same problem with my stock LG G5 H850 8.0.
Using the LG tool "LG Bridge" and performing an update using it repaired my device and i was able to boot again without any data loss.
I'm now trying to install the 20.2 on a second H850 using latest TWRP with no success. (Digest failed to natch on... .Aborting zip install: Digest verification failed Error installing zip file ...)
Is this because I'm running 8.0?
Click to expand...
Click to collapse
LG Bridge indicates no device connected in my instance, so I can't do much with it, although I've read where it will recognize my device if I can get into download mode. Unfortunately, it will take my battery several days to die in order to effectively turn it completely off to gain access to that mode.
fletcher969 said:
LG Bridge indicates no device connected in my instance, so I can't do much with it, although I've read where it will recognize my device if I can get into download mode. Unfortunately, it will take my battery several days to die in order to effectively turn it completely off to gain access to that mode.
Click to expand...
Click to collapse
Had the same problem, try powering the phone down, then pressing volume up and then connect the usb cable (connected to your computer).
Magisk Update - stuck in fastboot
I have an LG G6 US997 - tried to update to Magisk 20.2 today 1/3/2020 using the typical magisk manager. Now my phone only boots into fastboot. I can get into twrp recovery. I have tried using magisk uninstaller and I can still only get to fastboot.
toot-217 said:
Had the same problem, try powering the phone down, then pressing volume up and then connect the usb cable (connected to your computer).
Click to expand...
Click to collapse
In my case, powering down requires I either remove the battery (not an easy option), or letting the battery die which will take several days. I have fastboot, stock recovery, and the 21C ROM files (zip and kdz), and I assume can install TWRP temporarily, so I'm wondering what my non-LG Bridge options are currently.
Exactly the same vith my LG V20.... I can't flash TWRP neither, says FAILED (remote: 'unknown command')
UPDATE: Using TWRP(recovery mode still worked fine), you can just Install your ROM again and it will repair the issue. It does not wipe anything!! Although I had removed some of the bloatware from the rom originally, so that all came back. You may also need to run the magisk uninstaller from TWRP.
LG G6 US997
**If you are stuck in fastboot mode..(and want to get to recovery mode/TWRP)
1.Hold Volume Down+Power Button(it will restart after 5 seconds) KEEP HOLDING
2. when you see the first LG screen, release power button and hold again
3. Phone will enter recovery options(if you have twrp, just choose to wipe data(this wont wipe anything, its just how you get to TWRP)
4. Reinstall Rom File or use magisk uninstaller
Here is the ultimate solution https://forum.xda-developers.com/showpost.php?p=81378123&postcount=13 Don't panic!
placidns11 said:
UPDATE: Using TWRP(recovery mode still worked fine), you can just Install your ROM again and it will repair the issue. It does not wipe anything!! Although I had removed some of the bloatware from the rom originally, so that all came back. You may also need to run the magisk uninstaller from TWRP.
LG G6 US997
**If you are stuck in fastboot mode..(and want to get to recovery mode/TWRP)
1.Hold Volume Down+Power Button(it will restart after 5 seconds) KEEP HOLDING
2. when you see the first LG screen, release power button and hold again
3. Phone will enter recovery options(if you have twrp, just choose to wipe data(this wont wipe anything, its just how you get to TWRP)
4. Reinstall Rom File or use magisk uninstaller
Click to expand...
Click to collapse
I can get to my stock recovery using my buttons, so I'm assuming I can fastboot twrp.img over to my recovery partition, and reboot to twrp (via stock recovery screen). I just won't have access to my data partition (encryption issue), but I really don't need to access it anyway. I 'think' I have the Magisk 18.0 zip on my SD card, and if so, I thought maybe I could flash it, and see if that fixes the fastboot issue. Just not sure if that idea is sound, and I don't want to make the problem worse, so I'm holding out for some opinions on that idea. I would consider uninstalling Magisk, but I can't see my SD card when it's in my backup phone, and ADB won't recognize my phone (only fastboot does), so I can't copy anything to it unless there's a way to copy files to the SD card using fastboot. I'm thinking it's either a factory reset in stock recovery (if in fact that will fix my fastboot issue), or possibly fixing the issue by reinstalling the older Magisk 18.0 I installed initially.
pendgy said:
Here is the ultimate solution https://forum.xda-developers.com/showpost.php?p=81378123&postcount=13 Don't panic!
Click to expand...
Click to collapse
I'll look into that when I get done working. So long as my PC can see my external SD card while in (temporary) TWRP, I should be able to pull the archived boot.img, copy it back to my SD card, and flash it via TWRP (or fastboot). If not, I can't access my SD card while the phone is in fastboot or stock recovery, and my backup phone doesn't recognize the SD card.
Daaamn, I'll lose my mind.. mean, after couple of hours trying to resurect my LG G5.. I tried, so many methods and nothing. uninstal magisk, wipe dalvik, install magisk 20.1, wipe data - nothing etc. I even tried to use my TWRP backup from June and.. It didn't work. I used this backup some time ago, so it has to be good. That's so fcuked up.. Did someone has common problems or someone has got the solution for this situation? When I'm thing about doing all the stuff again. Clean ROM, bootloader, all the ****.. I hope someone will help me or I'll find solution.
Another LG V20 (H915 turned US996 turned H910 - the only way to root the device and keep the radio ) user here. Can confirm, latest Magisk boots straight to fastboot, even when uninstalling magisk. I suspect the boot partition and its backup are thrown out in some devilish bug designed to make us reinstall our ROMs. Very annoying: I can't do a crossword now as I use the toilet!
I'm having the same issue with my H918, but reflashing the ROM did not solve my issues now it says: Secure start-up
Decryption unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
I never entered a password, or encrypted my data.
When I select the only option which is to factory reset, it goes back into recovery again.
Any ideas?
Thanks,
Rob
I DID IT! I did backup of my broken system from TWRP. Copy it to the hard disk. Then I replaced boot files (boot.emmc and same with .sha) from another backup which didn't want to restore in full option. After this i flashed backup with changed boot files and phone started. Bootlader remain, root remain, my camera mod for G5 is working. Now I'll have to install apps. Daaamn, so many hours.. I hope this solution will work for someone. Greetings from Poland!
EDIT: root and recovery aren't working but my camera mod reamins working. It's weird. So now I'll have to do root, recovery and then install apps which I used.
EDIT2: Recovery is working, sorry for chaos. Now I'm doing backup and then I will instal magisk 20.1
pendgy said:
Here is the ultimate solution https://forum.xda-developers.com/showpost.php?p=81378123&postcount=13 Don't panic!
Click to expand...
Click to collapse
I can confirm that this worked perfectly on my LG G6, and is much easier than the machinations everyone else is trying. Thanks @pendgy!
frohro said:
I'm having the same issue with my H918, but reflashing the ROM did not solve my issues now it says: Secure start-up
Decryption unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
I never entered a password, or encrypted my data.
When I select the only option which is to factory reset, it goes back into recovery again.
Any ideas?
Thanks,
Rob
Click to expand...
Click to collapse
I got it fixed. The Data partition had to be formatted, not just wiped.
RESOLVED: For whatever reason, and after one of several temporary flashes of TWRP (mostly to allow my phone to charge), it started mounting the /data partition, something it had never done before due to the encryption issue on Oreo I could never get past despite several suggested solutions. I even managed to create a backup of my /data. In any event, I uninstalled Magisk, but it left my ramdisk corrupted, which forced it to fastboot (probably why all other attempts to fix this failed into fastboot after the Magisk update). Decided to flash my ROM which fixed the ramdisk, flashed the no-verity/no forced encryption, then reinstalled Magisk v20.1. All was well and good after that with no loss of data, and TWRP persisting in recovery.
[HTC ONE M9] magisk error ,cant uninstall or install again
Hi, I need some help with the my phone was have problematic work on magisk .zip. When I rooted my phone I installed the best latest version of magisk - 20.1. Beta for HTC and Android 10 but installation is not going well, probably not installed or something wrong, because when restarted phone, magisk is not exist in the phone and is not rooted .
So I trying to make sure and use magisk uninstall zip in twrp 3.1.1 but is not possible to uninstall, so trying terminal and unimod and/or mm commad - not found this command , module etc.
Try install 19.0 version magisk but all install metod finishes wit errors .
Dont have magisk now .
Related
Hey guys so I'm panicking right now, so I just unlocked the bootloader, flashed TWRP and rooted my phone but now the phone won't boot it's just stuck at the boot icon with the two circles chasing each other, am I screwed and is my phone useless now ?
Don't worry, this is a common problem that occurs when you use an older version of SuperSU.
Flash SuperSU v2.79 to root. You won't even have to reflash the OS. Your phone should reboot once during the booting process.
Alternatively, you can reflash the stock OS and root with Magisk v11.1, which will also root your phone.
Anova's Origin said:
Don't worry, this is a common problem that occurs when you use an older version of SuperSU.
Flash SuperSU v2.79 to root. You won't even have to reflash the OS. You phone should reboot once during the booting process.
Alternatively, you can reflash the stock OS and root with Magisk v11.1, which will also root your phone.
Click to expand...
Click to collapse
Okay so can you tell me how to remove 2.78 before I flash 2.79 ? thanks
You don't need to remove it. Flashing the newer one should replace the older one. I had the same problem when I first rooted following a slightly outdated guide. Flashing the newest version fixed it without a problem.
Anova's Origin said:
You don't need to remove it. Flashing the newer one should replace the older one. I had the same problem when I first rooted following a slightly outdated guide. Flashing the newest version fixed it without a problem.
Click to expand...
Click to collapse
My phone isn't showing up on my pc as a removable storage and when I type adb devices my phone isn't showing up either
If you have a usb-C OTG adapter, the easiest way is to copy it onto a flash drive and flash from the drive in TWRP.
TWRP should also have a way of mounting your phone to your PC, though I've personally never managed to get it to work.
Also, I believe adb works while you're in recovery mode. You can use adb to push the superSU zip to your phone's internal storage. If you aren't sure how to use adb, the toolkit consolidates all of the useful commands together.
Anova's Origin said:
If you have a usb-C OTG adapter, the easiest way is to copy it onto a flash drive and flash from the drive in TWRP.
TWRP should also have a way of mounting your phone to your PC, though I've personally never managed to get it to work.
Also, I believe adb works while you're in recovery mode. You can use adb to push the superSU zip to your phone's internal storage. If you aren't sure how to use adb, the toolkit consolidates all of the useful commands together.
Click to expand...
Click to collapse
I managed to flash 2.79 but I don't think it worked, still stuck booting, will leave it for a few minutes though to see if anything changes, any suggestions if that wasn't the issue ?
Dirty flash whatever version of OOS you're on, wipe delvic/cache, then immediately flash SuperSU without rebooting recovery.
Anova's Origin said:
Dirty flash whatever version of OOS you're on, wipe delvic/cache, then immediately flash SuperSU without rebooting recovery.
Click to expand...
Click to collapse
I have no idea how to do any of that, I'm a beginner could you explain to me please ?
stefinho said:
I have no idea how to do any of that, I'm a beginner could you explain to me please ?
Click to expand...
Click to collapse
1) Download the full ROM of OOS from OnePlus (ignore their instructions, they are assuming that you have the stock recovery installed).
2) Transfer the full zip onto your phone.
3) Boot into TWRP
4) Find where you've put the full ROM on your internal storage and flash it
5) Once TWRP finishes flashing it, tap the "wipe dalvik/cache" button, DO NOT REBOOT (if you reboot at this point, your TWRP will be replaced with stock recovery)
6) Press back on TWRP, find your SuperSU.zip and flash that
7) Reboot
This process replaces any non-user files that may have been damaged. You won't lose any data or the apps that you have downloaded. This will replace the recovery with stock if you do not root immediately before rebooting.
Anova's Origin said:
1) Download the full ROM of OOS from OnePlus.
2) Transfer the full zip onto your phone.
3) Boot into TWRP
4) Find where you've put the full ROM on your internal storage and flash it
5) Once TWRP finishes flashing it, tap the "wipe dalvik/cache" button, DO NOT REBOOT (if you reboot at this point, your TWRP will be replaced with stock recovery)
6) Press back on TWRP, find your SuperSU.zip and flash that
7) Reboot
Click to expand...
Click to collapse
Thanks, will try that now.
Anova's Origin said:
1) Download the full ROM of OOS from OnePlus (ignore their instructions, they are assuming that you have the stock recovery installed).
2) Transfer the full zip onto your phone.
3) Boot into TWRP
4) Find where you've put the full ROM on your internal storage and flash it
5) Once TWRP finishes flashing it, tap the "wipe dalvik/cache" button, DO NOT REBOOT (if you reboot at this point, your TWRP will be replaced with stock recovery)
6) Press back on TWRP, find your SuperSU.zip and flash that
7) Reboot
This process replaces any non-user files that may have been damaged. You won't lose any data or the apps that you have downloaded. This will replace the recovery with stock if you do not root immediately before rebooting.
Click to expand...
Click to collapse
DUDE, it worked thank you so much man really appreciate the help
UPDATE: I was able to install stock recovery through BOOTLOADER (it started working again) and I tried sideload 4.1.7.zip that way. It seemed to work for a while, but unfortunately, sideloading crashed. Same for 4.1.6, update fails around 45%. Phone says INSTALLATION FAILED. Any thoughts?!
Hi guys,
I'm a longtime flasher of phones, but my wife today jacked up her 3T beyond the point that I know what to do. In short:
Her phone was rooted, had an unlocked bootloader and TWRP installed. She updated (despite my endless begging never to do that) the OTA, which crashed her phone. Duh. Not smart. The problem: the phone would not restart the OS anymore. Upon restarting, the phone immediately jumped to TWRP and hung at the splash screen (which takes a while to load, but she doesn't know that). She panicked, rebooted the phone a bunch of times before giving it to me.
I was able to get into TWRP eventually, and figured I'd manually install the newest 3T firmware. This is what I did:
First, I updated TWRP through TWRP, to the most recent version. This was successful. Then, this happened:
Downloaded 4.1.7 from the OnePlus website
Placed it on the phone's internal storage
Went into TWRP, wiped Dalvik, Cache, System etc. (leaving Internal Storage in tact)
Flashed the firmware
I've done this thousands of times, never fails. Except now.
After flashing (which was supposedly successful, as I did not receive error messages), I hit 'reboot' and TWRP told me 'NO OS INSTALLED - WANT TO REBOOT ANYWAY?'
That is bad, right? So, I did not reboot, stayed in TWRP and ended up trying to wipe internal storage, thinking I could then add the .zip with the firmware again later and try flashing again. Just a clean phone, you know? I was wrong. I cannot copy anything to the phone right now, so I can't flash anything (because I can't put anything on the phone).
I'm trying to sideload things now through TWRP (adb sideload) and regular fastboot (either the firmware 4.1.7 or 4.1.6 - I've even tried flashing the stock recovery through fastboot to try and get the stock back, so I can sideload the firmware through there), but nothing works.
If anyone knows what to do, or can give me an outline on what to try, I'd be very helpful. The situation right now:
3T, without OS or ANYTHING on the phone
With functioning TWRP
Only recognized in the command prompt when in TWRP, not when in BOOTLOADER
Phone does not allow things to be copied to the phone via my laptop.
On behalf of my extremely upset wife, I thank you!
@Donaghy
copy the downloaded 4.1.7 to a usb pendrive.
connect it to the phone using otg cable.
wipe Dalvik, Cache, System in TWRP.
select install, storage (pendrive), click on the OOS 4.1.7 zip file.
After the flashing is completed, reboot to recovery (not system).
Phone will boot again to TWRP.
Wipe cache and dalvik, reboot. (ignore NO OS INSTALLED - WANT TO REBOOT ANYWAY?)
If you see the rotating red dot, then all's ok. leave it for 5-10 mins to boot.
Siddk007 said:
@Donaghy
copy the downloaded 4.1.7 to a usb pendrive.
connect it to the phone using otg cable.
wipe Dalvik, Cache, System in TWRP.
select install, storage (pendrive), click on the OOS 4.1.7 zip file.
After the flashing is completed, reboot to recovery (not system).
Phone will boot again to TWRP.
Wipe cache and dalvik, reboot. (ignore NO OS INSTALLED - WANT TO REBOOT ANYWAY?)
If you see the rotating red dot, then all's ok. leave it for 5-10 mins to boot.
Click to expand...
Click to collapse
Thanks for your response. Unfortunately, as per my update (in green, above the post) I have returned the phone to stock recovery. I have tried sideloading 4.1.7 and 4.1.6, but both installations (via adb sideload, via stock recovery) crash around 46%. Phone says installation failed.
Donaghy said:
Thanks for your response. Unfortunately, as per my update (in green, above the post) I have returned the phone to stock recovery. I have tried sideloading 4.1.7 and 4.1.6, but both installations (via adb sideload, via stock recovery) crash around 46%. Phone says installation failed.
Click to expand...
Click to collapse
Try connecting ur phone to a different usb port and then sideload.
If stills fails, get back from stock to twrp recovery and follow the steps i mentioned.
Sent from my OnePlus3T using XDA Labs
Siddk007 said:
Try connecting ur phone to a different usb port and then sideload.
If stills fails, get back from stock to twrp recovery and follow the steps i mentioned.
Click to expand...
Click to collapse
Thanks, I will. I did just realize my bootloader is still unlocked, so this may be causing the crashing of the sideloading of the official firmware (who knows). I am now going to try to lock the bootloader again, ADB sideload the firmware, and then unlock the bootloader again.
Donaghy said:
Thanks, I will. I did just realize my bootloader is still unlocked, so this may be causing the crashing of the sideloading of the official firmware (who knows). I am now going to try to lock the bootloader again, ADB sideload the firmware, and then unlock the bootloader again.
Click to expand...
Click to collapse
Check this, if in stock recovery there is option to install from USB? It it does, then update using otg pendrive
Sent from my OnePlus3T using XDA Labs
Siddk007 said:
Check this, if in stock recovery there is option to install from USB? It it does, then update using otg pendrive
Click to expand...
Click to collapse
I don't own an OTG cable. The only USB option there is, is within the ADB menu in the recovery.
EDIT: locking the bootloader seemed to have made things worse, as I now cannot get the .zip files with the firmware on it to be accepted by ADB/the phone... God, this is a gigantic mess..
I remember there was some adb version (don't remember which one exactly) that had sideloading of large files broken. Try using the newest version from Android SDK.
Edit: just realized you locked your bootloader. Not a good step at all.
C3C076 said:
I remember there was some adb version (don't remember which one exactly) that had sideloading of large files broken. Try using the newest version from Android SDK.
Edit: just realized you locked your bootloader. Not a good step at all.
Click to expand...
Click to collapse
Yeah, some douche somewhere else on the internet said it should be locked. In someone else's thread... I'm trying to unlock it now again through fastboot.
UPDATE: alright, bootloader is unlocked again. I think I have the most recent minimal ABD and fastboot, but I'll check to be sure.
Donaghy said:
Yeah, some douche somewhere else on the internet said it should be locked. In someone else's thread... I'm trying to unlock it now again through fastboot.
UPDATE: alright, bootloader is unlocked again. I think I have the most recent minimal ABD and fastboot, but I'll check to be sure.
Click to expand...
Click to collapse
Btw, which stock recovery are you using?
It should be of the version 4.1.7 you are going to sideload
Sent from my OnePlus3T using XDA Labs
Siddk007 said:
Btw, which stock recovery are you using?
It should be of the version 4.1.7 you are going to sideload
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Whichever is the most recent one that is on the OnePlus website. I downloaded the .img off of their website.
I've had a similar issue, and I tried a billion times on trying to reflash Stock OOS 4.1.0, and sadly nothing happened. I then tried LineageOS by SultanXDA, nada.
So then, I said "Scr*w my data, I'm going to start anew", and I tried the Unbrick Tool, and Voila, new phone with OOS 3.5.X. Not the latest, but it's working.
I suggest you try that mate, you can find it over here.
Cheers!
P.S. - Love your profile pic.
If you sucessfully flashed 4.1.7 then I'd just reboot into system. TWRP sometimes says "No OS installed" if /system was wiped prior to flashing.
Regardless, I recommend you do these things now (if you havent already) and report back:
-Unlock bootloader (fastboot oem unlock)
-Flash TWRP* recovery, not stock. (fastboot flash recovery twrp.img)
-Boot recovery (fastboot boot twrp.img)
-Wipe data + system + cache + dalvik from TWRP
-ADB sideload in advanced section of TWRP
-from your PC: "adb sideload oos417.zip"
-from TWRP: reboot into system (ignore "No OS installed")
If you follow this and its succesful, everything will be fixed
* flash the twrp by xda member eng.stk, not the official one: the only place I can find his TWRP is in the 3/3t toolkit zip. So extract the v5 zip and use the "TWRP_recovery.img": https://drive.google.com/drive/u/0/folders/0B1cephDrsyt_ZzJ1cXpUUlVhSzg
Edit: Instead of doing all this manually, you may want to use the toolkit. See if your device is recognised
Thanks for the help, everybody!
I used the unbrick tool, which worked! I got the phone 'alive' again.
New problem: Right after successfully booting the phone again, I set up the phone (so: clean install, no root, stock recovery, straight out of the box, you know what I mean) and then proceeded to download the OTA that OnePlus pushed to the phone (4.1.7). It downloaded quickly, but the installation has been stuck for almost an hour.
The phone says 'Updating, please wait - do not turn off your phone', and the blue bar is filling. Well, not filling, as it has been stuck at about 10% for an hour.
Is this normal? If not, what can I do? Thanks again!
I turned the phone off and was able to successfully sideload 4.1.7 via ADB. Upon updating, the phone gave me a notification (blue and white letters) that the "DECRYPTION IS UNSUCCESSFUL. The password you entered is correct, but you have to perform a factory reset to use your phone".
So I did another factory reset in recovery, rebooted, and it's up and running, with 4.1.7 on it! I can't believe we got it back from the dead. Thanks everyone, for your help! Really appreciate it!
Hello, I've been trying to bring back to life this old XT1068.
In the past years, I had installed several ROMs until one day the phone stopped working (probably I made some mistakes like flashing something not supposed to be flashed on this device, probably) and since that moment if I turn it on it remains stuck on the boot animation (the coloured google dots moving...).
I tried everything. I have TWRP 3.1 installed, I tried to wipe everything, I tried factory reset, I tried to erase the internal storage, I tried to install new ROM, including a stock ROM and the stock recovery. The result is always the same: no errors at all in TWRP, but it's like nothing changes. It does not boot and if I go to TWRP I can still see files that I put in the phone years ago, after I tried every possible wipe. Imagine that I still see the WhatsApp folder of years ago.
As I already mentioned, I also tried to flash a stock recovery: the process finishes without errors but if I reboot to recovery, I always end up in TWRP.
The only thing I can do is to reboot into recovery or fastboot.
The phone is recognized by the computer ("adb devices" / "fastboot devices").
Does anyone of you guys ever experienced something like this?
Thanks in advance.
I have exactly the same issue. Did you find a solution?
I never got that problem, is pretty strange, i think some zip you flashed before is still installed automatically, for example, there is some option on supersu called survival mode, if you enabled that, i think an supersu uninstaller zip could work, also you can try to install any rom, install supersu and check on supersu settings
---------- Post added at 07:15 PM ---------- Previous post was at 07:14 PM ----------
Also probably some partition got damaged or anything, i recommend to flash an stock rom that flashes many things except for nvdata and nvram partitions because it could make you can't get signal if those partitions are from another zone
Get your device into fastboot mode and flash the stock IMG.
https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
My device is also bricked of you are able to revive, can you extract mmcblk0.img of your device and share please
eagledipesh said:
Get your device into fastboot mode and flash the stock IMG.
https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
My device is also bricked of you are able to revive, can you extract mmcblk0.img of your device and share please
Click to expand...
Click to collapse
Hello!
I`ve done the process to install via mfastboot the stock IMG, no errors at all. When the phone reboots it goes into the previous installed rom boot animation and stays there at bootloop.
I even tryed to install an updated TWRP recovery (3.4) via fastboot. Is shows "OK" but when it loads it is still the previous version.
It looks like the phone is "write pretected".
Any further suggestion?
Thanks in advance.
Allisson
Same problem here. I can accces the fastboot menu via "VOLUME DOWN + POWER" but whatever I try, the red error message comes up. I can boot into twrp via USB/PC but i cannot install it. I cannot factory reset.
when I reboot from TWRP I come to lineageOS boot loop.
ANY IDEAS?
Hello guys!
Yesterday I tried to flash the newest Lineage-built to my new G7+ (XT1965-3, bought in Germany via Amazon), but something went wrong and now I'm afraid, I bricked my phone.
It's not my first flash of Lineage, as I did this in the past already on some older Phones (SII, SIII, S5), but it's the first time, that I have a major issue.
So I followed all the steps on the Lineage-Wiki (on Win10).
After flashing the recovery (the lineage-recovery, not TWRP) I wasn't able to enter the recovery-mode, so the phone booted to StockRom. And probably this was the problem: As it didn't react to VolumeDown+Power, I reflashed the recovery a second time. After that the touch-screen is not working any more.
I am able to enter the recovery-mode and I can boot to Stock-Rom, but in both modes the phone does not react to touch, so I can only use the Volume- and Power-Buttons.
Probably I made more mistakes after that: I thought, that a factory-reset would help, but It didn't. I also relocked the bootloader, but as I saw, that it also did not bring any solution, I unlocked it a second time.
Conclusion: I have a brand new phone, with lineage-recovery, an unlocked bootloader but without touch working.
I also tried to flash Lineage, but the sideload got stuck at 47%. So Lineage is not installed and it boots into Stock, where I can not get any further without touch.
Has anyone any idea, what could be the issue and how I can fix it? I would like to start from scratch, but I don't know, what is the exact problem and if i can for example return to stock recovery.
Thank you!
---- EDIT ----
If it helps: I am able to boot TWRP via "fastboot boot twrp-xxx.img". And in TWRP the touch works!
I could flash lineage directly via TWRP from external sd-card, but i am afraid that after that I won't be able to return if something goes wron.
probably your best bet is to go right back to stock using the LMSA tool and starting fresh. I've seen others encounter similar issues on different devices and always the cleaneast solution was just to role back everything and start over.
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
joglxv said:
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
Click to expand...
Click to collapse
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
digitaljeff said:
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
Click to expand...
Click to collapse
I'm having a similar problem. At first touch was fubar but I was able to return to stock using LMSA and now touch works. I can load TWRP with fastboot and even install a custom ROM and TWRP, but installing any custom ROM results in a boot loop during the finding and installing updates part of the phone setup during first boot. I'm tried Evolution X which I was running previously(for about a month, and then a boot loop started yesterday), PixelOS 10, and AncientOS, but all result in the boot loop on first boot after connecting to wifi.
Fixed
I fixed this somehow by manually flashing the latest stock firmware to slot a, and then extracting the evolution x Rom and manually extracting the IMG files inside and manually fastboot flashing those to slot b. I then set b as the active slot and booted up, patched the boot image with magisk, flashed that, and everything works. Not sure why twrp wouldn't do the trick.
Finally had the time to install Lineage. Now everything works.
I followed the instructions someone posted in the [ROM][OFFICIAL] LineageOS 17.1 [nightlies]-thread and the instructions of the lineage-wiki:
1. fastboot boot TWRP
2. sideload the copy-partitions.zip from lineage-wiki
3. factory reset via TWRP (wipe cache, dalvik and data)
4. sideload lineage
5. reboot bootloader
6. fastboot boot TWRP
7. sideload magisk
8. reboot system
Had a little bootloop the first time rebooting the system, but that was because I forgot to wipe data-partition in step 3. Wiping data and rebooting did it for me.
So I have a working Lineage17.1 with root via Magisk.
Thank you for the help!
I had exactly the same problem like you had. Bought a brand new moto g7 plus and after recovery flash, Touchscreen was not working anymore. I could manage to go back to the bootloader, sideloaded TWRP, but side loading lineage worked for me then. It seemed to be stuck on 47 percent, but this seems to be a normal issue, the file was there and after installing, touchscreen worked normally.
Since I never had a problem with an update in years, and I'm also a very stupid person, I didn't backup my data before my latest custom rom (Pixel Experience Plus) update.
I got the notification for the November security patch updates, and I downloaded the zip as usual. For the actual installation I usually reboot my Mi 9T Pro into TWRP, flash both the OS update and Magisk, etc. and reboot. Everything seemed to go smoothly as usual: TWRP asked me to input my unlock sequence, then the usual stuff. Problem is, when I tapped 'Reboot system', it didn't reboot normally: it went into Recovery mode again, and from that moment on there's been no way to do otherwise. But now TWRP doesn't ask me the unlock sequence anymore and looks like there's no way to access the data. I tried injecting the recovery from fastboot, I wiped everything except internal storage (I don't give a damn about the OS anymore at this point); I also tried to reinstall the same old rom from OTG after wiping System, but nothing. Whatever I do, it always boots up in Recovery, and it doesn't ask me the unlock sequence. I know my stuff is still there, it's just that the contents of sdcard aren't accessible and look like random alphanumeric sequences from the TWRP file manager. And yes, that's the whole point of encryption, but I was used to TWRP asking me to unlock/decrypt so in the worst case scenario I would be able to access my data and copy via OTG. But now, with the system unable to boot and the recovery not decrypting my stuff, I'm starting to losing hope. I'm sure here on XDA there are much smarter / knowledgeable people than me, and I hope somebody can help me find a way to break the cycle and return in possession of the data that I stupidly didn't backup.
Any help would be greatly appreciated!
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
V0latyle said:
Try reflashing the boot image. Failing that, you should be able to ADB sideload the update via TWRP.
Click to expand...
Click to collapse
I think I tried both. I say 'I think' since my knowledge could fail here.
I tried re-flashing the TWRP img from OTG, nothing changed.
I successfully sideloaded the OS through ADB, but I'm still stuck.
Should I try both? (In which order)?
Thanks a lot.