Related
So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.
theprof7 said:
So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.
Click to expand...
Click to collapse
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.
raptorddd said:
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.
Click to expand...
Click to collapse
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?
theprof7 said:
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?
Click to expand...
Click to collapse
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
https://drive.google.com/file/d/0B90RfjoH13UEbDFBSG5XWVA0ME0/view?usp=sharing
raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse
theprof7 said:
raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse
try a custom kernel it has superSU installed.. i say imperium kernel.
try first the custom kernel.. if not you can only downgrade to 20o. no lower or youll hard brick phone.
Click to expand...
Click to collapse
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
can you please share what guide you used to unlock and root this phone? I'm having issues on finding it, im on the newest update
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
Please, can you share what guide you used to unlock and root this phone (20p)? Can not find any complex info anywhere.
Thank you.
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"
king200 said:
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"
Click to expand...
Click to collapse
You can get the latest Imperium kernel (5.0 currently) from: http://forum.xda-developers.com/g4/orig-development/kernel-imperium-kernel-g4-v1-0-t3282915
Yes, fastboot boot from the twrp image was kind of a hack, but it worked. As for SuperSU, I tried v1.94 and SuperSU-v2.76-20160630161323.zip. Both soft-bricked the phone. Maybe the newest SuperSU will work, but I wouldn't count on it given that several previous versions didn't.
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
I need to flash twrp and root from 20p also. One question to clarify exactly what you did,
Did you originally try flashing TWRP from TWRP? You said you flashed root from TWRP but I want to verify if you tried flashing TWRP from TWRP like:
> adb reboot bootloader
> fastboot boot twrp-3.0.2-0-h811.img
then in TWRP:
> install click on image tab.. then select twrp-3.0.2-0-h811.img recovery and flash it.
> reboot recovery (should reboot to TWRP you just flashed)
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!
emailej said:
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!
Click to expand...
Click to collapse
Yes, just loads TWRP temporarily. Later I installed some apps that flashed the recovery successfully, either rashr or flashify (I don't remember which)
I hope you have all the files and pc is reading your phone in adb.
Keep the downloaded twrp file in your adb folder with dwonloaded name (Ex:1234twrp.img)
Copy the file and keep in phone internal storage with names recovery.img
adb reboot bootloader (wait for phone to boot in bootloader ofcourse)
fastboot boot 1234twrp.img (whatever your twrp img file name would be)
Now you are in twrp recovery page in the phone.
Tap Install > Images (bottom right) > select recovery.img >
Now you are in next screen where options to slect recovery or boot
Tap recovery and swipe you will see [image flash complete]
Now twrp is permeant. You can restart in recovery without PC. (Tested)
I have flashed more than 6 methods to install supersu. Keep trying and reply.
I need help, I was trying to root my Oneplus 3T, with stock OOS 4.0.2. After following all the steps, I flashed the dm-verity to keep with the steps, and that worked. But after formatting data, as it was suggested, it gave me an error. It showed like everything was encrypted which shouldn't due to the flash of the dm-verity and now I'm stucked in not a bootloop because the phone actually boots but I cant do anything because the encryption error takes me back to the recovery, which shows an error etc. Is there any tutorial to fully recover the phone from this point? Thank you very much in advance.
Did you try flashing SuperSU after flashing dm-verity? If the zip isn't on your phone at this point, you can go into bootloader mode and use adb to push the SuperSU zip on and flash it that way.
You can use the toolkit to push the files if you want, it'll be easier that way: https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
If all else fails, flashing a clean rom always works.
Anova's Origin said:
Did you try flashing SuperSU after flashing dm-verity? If the zip isn't on your phone at this point, you can go into bootloader mode and use adb to push the SuperSU zip on and flash it that way.
You can use the toolkit to push the files if you want, it'll be easier that way: https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
If all else fails, flashing a clean rom always works.
Click to expand...
Click to collapse
Now I'm stuck in a bootloop after reflashing stock recovery. If i reflash the boot.img via fastboot from the .zip of the official OOS 4.0.1, will it work? Thank you very much
Not sure why flashing recovery would cause a bootloop. Might be safer just to sideload a fresh ROM. If you're worried about losing files, you can use adb to pull whatever you need first from sdcard prior to flashing.
What I did in a similar situation was to reflash the stock recovery first using the unbrick-toolkit. When booting into recovery then, there is an option "forget password" when it asks you to enter the password. If you select that, it will simply wipe your phone completely and you can start over again.
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
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 .
Tried a bunch of things to make the TWRP installation persistent, but it just goes back to MIUI recovery when i reboot from the system.
I'm using TWRP 3.5.2 by Nebrassy.
USB debugging turned on
Correct drivers installed
fastboot devices work Using minimal ADB and fastboot
I have the file renamed as TWRP.img.
Steps i followed:
fastboot boot "TWRP.img" - Correctly boots into TWRP
install the TWRP image to the recovery partition - Happens with no errors
Reboot to system - No errors there as well
Reboot to recovery - Goes back to MIUI recovery.
Can someone please tell me what i should do?
PS: Tried with TWRP 3.6.0 as well just now. Same issue.
Helhound0 said:
Tried a bunch of things to make the TWRP installation persistent, but it just goes back to MIUI recovery when i reboot from the system.
I'm using TWRP 3.5.2 by Nebrassy.
USB debugging turned on
Correct drivers installed
fastboot devices work Using minimal ADB and fastboot
I have the file renamed as TWRP.img.
Steps i followed:
fastboot boot "TWRP.img" - Correctly boots into TWRP
install the TWRP image to the recovery partition - Happens with no errors
Reboot to system - No errors there as well
Reboot to recovery - Goes back to MIUI recovery.
Can someone please tell me what i should do?
PS: Tried with TWRP 3.6.0 as well just now. Same issue.
Click to expand...
Click to collapse
Try again to flash TWRP dirty and if it's started don't boot with software. You have to boot TWRP again by pressing volume + and power button until you'll get vibration , afterwards you'll be in TWRP again, clear dalvik and cache and restart system via TWRP menu
Laptapper said:
Try again to flash TWRP dirty and if it's started don't boot with software. You have to boot TWRP again by pressing volume + and power button until you'll get vibration , afterwards you'll be in TWRP again, clear dalvik and cache and restart system via TWRP menu
Click to expand...
Click to collapse
Sorry mate that didn't work. Still going back to stock recovery...
Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?
Helhound0 said:
Sorry mate that didn't work. Still going back to stock recovery...
Click to expand...
Click to collapse
Then you've got to do a flash with stock ROM and miflash via pc
Laptapper said:
Then you've got to do a flash with stock ROM and miflash via pc
Click to expand...
Click to collapse
Would that re-lock the bootloader? And if so do i have to wait 7 more days for it to be unlocked?
I used the Disable-Dm-Verity-Zip directly in TWRP after installation. Worked without a problem.
romuser87 said:
I used the Disable-Dm-Verity-Zip directly in TWRP after installation. Worked without a problem.
Click to expand...
Click to collapse
I read that somewhere too but that didn't help me at all... Maybe i have a bad zip file..
Can you share the zip you flashed?
Also, any idea how i could get this fixed:
Helhound0 said:
Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?
Click to expand...
Click to collapse
Helhound0 said:
I read that somewhere too but that didn't help me at all... Maybe i have a bad zip file..
Can you share the zip you flashed?
Also, any idea how i could get this fixed:
Click to expand...
Click to collapse
The attached file worked for me
Helhound0 said:
Would that re-lock the bootloader? And if so do i have to wait 7 more days for it to be unlocked?
Click to expand...
Click to collapse
1. With MiFlash there is an option at the bottom of the screen to lock bootloader. Just make sure it is NOT checked, and you will be safe to use MiFlash without relocking bootloader.
2. When installing TWRP for first time, it is essential that your first reboot is straight back to TWRP - then it becomes persistent, and future reboots to recovery will be to TWRP. If you do not do the first reboot back to TWRP, the stock MIUI ROM recovery reinstalls itself.
HiQual said:
1. With MiFlash there is an option at the bottom of the screen to lock bootloader. Just make sure it is NOT checked, and you will be safe to use MiFlash without relocking bootloader.
2. When installing TWRP for first time, it is essential that your first reboot is straight back to TWRP - then it becomes persistent, and future reboots to recovery will be to TWRP. If you do not do the first reboot back to TWRP, the stock MIUI ROM recovery reinstalls itself.
Click to expand...
Click to collapse
The first ever twrp install i did, i rebooted to system by mistake but i reflashed twrp and made sure to reboot to recovery.... That was the second try. I think i may have tried at least two dozen times since that but it just kept booting back to stock recovery...
I think I'll run with this until the end of Jan and then redo everything from scratch...
Helhound0 said:
Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?
Click to expand...
Click to collapse
I'm stuck at this stage. Have you found any solution yet?