I'm having a issue in which I rooted and unlocked using Wug's toolkit. I used this successfully since Thursday that I got my phone without issues. Well today I went into twrp recovery and wiped cache and dalvic cache as I was having issues installing apps (apks) and from store. Now my phone boots but just sits at boot screen without starting up. I am able to boot into recovery but phone still won't boot after restart. I have already waited over 30 mins and have tried multiple times. I called my carrier and they want to send me a replacement, but my concern is how to set it back to stock. Any help would greatly be appreciated.
cbrvnm said:
I'm having a issue in which I rooted and unlocked using Wug's toolkit. I used this successfully since Thursday that I got my phone without issues. Well today I went into twrp recovery and wiped cache and dalvic cache as I was having issues installing apps (apks) and from store. Now my phone boots but just sits at boot screen without starting up. I am able to boot into recovery but phone still won't boot after restart. I have already waited over 30 mins and have tried multiple times. I called my carrier and they want to send me a replacement, but my concern is how to set it back to stock. Any help would greatly be appreciated.
Click to expand...
Click to collapse
wipe dalvik cache??? From what i know, Lollipop uses ART.
These are the options I have in my recovery under advanced wipe
Even though the runtime is ART now, clearing dalvik in TWRP does force a 'rebuild' of apps upon boot, so it does still have a purpose.
The 'rebuild' I'm talking about is the "android is upgrading" screen.
cbrvnm said:
These are the options I have in my recovery under advanced wipe
Click to expand...
Click to collapse
just flash the stock firmware with your recovery. I would recommend reporting this bootloop issue to twrp. Im sure it has someting to do with it.
Flash system.img
Ghettonine said:
just flash the stock firmware with your recovery. I would recommend reporting this bootloop issue to twrp. Im sure it has someting to do with it.
Click to expand...
Click to collapse
When he says "firmware" he means
Code:
fastboot flash system system.img
It won't wipe your data, but it will remove no-force encryption (NFE) and you're going to need to re-root :good:
Had the same problem a few days ago.
@Ghettonine I don't think it's TWRP, more so SuperSU
I was able to use rootkit to flash stock and unroot and it goes through the whole process and states that it was successful and to wait until it boots. The problem is that it never boots and stays in the boot screen. Also I have had it on for 30 mins multiple times and still not working. I boot into recovery but this time I don't have TWRP anymore I just have a android with red triangle with no options to choose. Any other suggestions that could help?
Re-flash stock factory images and stop relying on tool kits to flash stuff. Learn how to use adb and fastboot, or just don't bother messing with root.
Straight to the point:
Installed Xposed Lollipop, gave me low storage warnings
Rebooted to see if it would fix that, it built cache again but warning stll there
Boot into recovery, selected "Fix Permissions" in TWRP, wiped dalvik cache and cache
Booted again, goes through boot cycle but then goes straight to a black screen. Can get into bootloader. Wasn't able to go into recovery (spit out a black screen) but I plugged it into the charger and was able to get in.
I've unlocked the bootloader, rooted and that's about it. I'm rocking the Pure Edition. Anything I can do short of Factory Reset? I really don't want to lose my data for no reason.
Edit: I flashed system.img and boot.img from the toolkit in Android Development. That didn't work outside of TWRP detecting root wasn't installed. I did a Factory Reset in TWRP and that fixed things. Oh well.
Did you wiped dalvik and cache after flashing zip? ?
@jcracken: the perils of using Alpha software.
Go back into recovery and reflash xposed. Then reboot. I also used selmodechanger and set it to permissive.
This is not due to xposed. The bootloop was due to TWRP, DO NOT FIX PERMISSIONS FROM TWRP. It will cause a boot loop on lollipop whenever you do it
To uninstall xposed on lollipop go into file manager in twrp and delete xposed.prop in /system partition after mounting and also delete xposed.jar in /system/framework
If you want a toy, get an iPhone. If you want a Smartphone, get an Android
Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!
mobone32 said:
Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!
Click to expand...
Click to collapse
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again
mobone32 said:
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again
Click to expand...
Click to collapse
you should be able to install TWRP by using the command, "mfastboot recovery twrp.img"
regarding CM11, I don't think is needed anymore to go from CM10 to CM12. it was at one time, but I believe CM or TWRP made some updates so that step is no longer necessary.
but before we can help you further, let us know what ROM you are on now and what ROM you want to be on next.
also, this thread is very helpful: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
Ok I got TWRP on there. Now I would like to get to lolipop 5.1 one way or another. I've always liked CyanogenMod (of course) but want to try CyanHacker. http://forum.xda-developers.com/moto-x/development/rom-cyanhacker-lollipop-ghost-t3033367
Right now I'm on a stock sprint rom I got with kitkat 4.4.4
Here's what I was going to do: (copied from forum)
1. mfastboot flash the latest TWRP if you aren't already at that point. I won't help you on fastboot things as you should already know- look around in the forums for info.
2. BACKUP YOUR STUFF- don't want to lose things without being able to get them back, right?
3. Flash the downloaded CM11 snapshot.
(Heres where I'm stuck. This is where I soft bricked it last night. I tried just now to apply the update using twrp and it just fails. It also fails at rooting my phone.)
4. Let CM11 fully boot and go through the setup screen- just skip everything and get to the homescreen.
5. Reboot into Recovery and wipe EVERYTHING- system, data, dalvik cache, cache, etc.
6. Flash your Lollipop ROM.
7. Flash PA-gapps.
8. Flash SuperSU.
9. Wipe cache/dalvik cache.
10. Reboot.
11. ???
12. Profit.
Thanks for any help!
So I just recently received a new (to me) Nexus 6. Going through the process of unlocking the bootloader I forgot to do the command "fasboot reboot". I then installed TWRP and then booted into it. From there I rebooted the system and was brought to a screen that says encryption unsuccessful. I hit the reset button which brought me to twrp and asked for a password. I typed in "default_password", it did it's thing and rebooted to the same "encryption unsuccesful". I tried searching XDA as well as Google to no avail. When searching Google I found some threads for other devices but I didn't want to get into a worse situation than I'm already in so I thought I'd ask here before trying anything else. Any help would be greatly appreciated!
Update: I flashed the stock image (manually as the flash-all didn't work) and I was able to get the phone to boot up into Android. But whenever I reset the device it gives me the "Your device is corrupt" screen before booting into the system. And it seems like whenever I try to flash supersu or anything I'll get that message and then it just goes to a black screen and never boots into Android. I even tried to restore a TWRP backup and it still just went to the corrupt screen and then black. I was only able to get it to boot into Android after reflashing the stock images again. Is this a problem with the hardware or is there something I can do to fix it?
Edit: I've also noticed under internal storage it's only showing 23 GB available but this is the 64 GB model.
Prozart said:
Update: I flashed the stock image (manually a.
Click to expand...
Click to collapse
Did you format/wipe the system, data and caches - a complete factory reset ?
There are several things going on here.
1. Your device is corrupt message: This is a normal message that appears whenever you attempt to customize the device. It may also appear if there is an issue with the internal storage in general.
2. SuperSU: What version? You should be using the latest (2.76) or you risk having a bootloop.
3. TWRP: What version? Latest is 3.0.2-0. Older versions will offer to flash SuperSU. Don't accept the offer or you will enter a bootloop.
4. Internal storage: When you flashed the stock ROM you also flashed the userdata image in it, which caused you to lose half your storage. Simply wipe internal storage in TWRP to fix.
Your first thing is to fix your internal storage, which should be done through TWRP. From there, you will need to do a complete factory reset, as the failed encryption is the main reason you're getting a corrupt device warning. After the factory reset, restore the stock image, but do not flash userdata.img.
Thanks guys! Doing the factory data reset in stock recovery fixed it for me. It took about 30 minutes to complete, but now I've got root, twrp, and custom ROM and kernel with no issues.
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 .