Stuck with cm recovery and no bootloader Xperia Z1 - Xperia Z1 Q&A, Help & Troubleshooting

Hello everybody,
I rooted my Xperia Z1 about 8 months ago in order to install the 5.1.1 update which didn't roll out for my device probably because it was a global version (5.0.1 was the last OTA). I did a clean install with no problems, flashed DualRecovery, SuperSu, and BusyBox was working just fine. Everything was working perfectly.
About 3 months ago, I tried updating BusyBox, only to tell that the update failed (couldn't install in the path it used to be try changing the path), I read and read, and found that the solution was to delete a certain file from root that prevented me from modifying certain folders and their content(even with root access), and then do a clean install in a different path than the former one. However, I couldn't gain root access to my files, no root explorer worked! It bugged me, but I was busy at that time, so I couldn't resolve it.
Few weeks later I tried rebooting into recovery, but no method worked, no apps, no key combination, no adb, nothing at all worked! After 2 hard days I managed to install TWRP recovery using NUTS recovery project. I rebooted several times, and it was still working. I then installed BusyBox with no problems, and everything was back to perfect. Later I decided to install CM 12.1 because I always used on my Samsung Galaxy Nexus and I always loved it. So using my now working recovery, I backed everything up on a USB and then flashed CM 12.1 WITHOUT its recovery along with a GAPPS package.
CM was installed, which then rebooted into its recovery and tried to install the GAPPS package. The GAPPS installation was a fail. CM recovery asked me to try using TWRP to do such installation ( go figure! ); in fact, CM recovery couldn't flash anything besides another CM 12.1 update. After this point I wasn't able in any possible way to enter TWRP nor install it. Even if I want to flash using fastboot I couln't! adb reads my device just fine, and can use it to reboot into flashmode, which doesn't seem to be functioning properly. The blue light turns on but there isn't a thing on the screen, fastboot can't recognize is it and hence I can't flash anything using fastboot.
Should I reflash partitions if this could be done on Z1? ( I did it before on my Nexus ) Can I use Odin? I even doubt I can enter download mode on my phone
Any help would be much appreciated.
Thanks in advance!

Anyone?
No?
Ok! :sad:

Is your bootloader unlocked? To run cm on our z1 you need an unlocked bootloader because cm needs a custom kernel.
You can try Sony companion app or androxydes flashtool in combination with a pre-rooted ftf to reach stock again.

The thing is even Sony flashtool (Emma) is not reading my phone, it detects a device in the USB port, but not the device!
I managed to install TWRP using TWRP Manager app that I downloaded from APKmirror website. I installed GApps and it is working fine right now.
TWRP Manager said that I should have a FOTA recovery or something like that, and if I don't have one then I am installing the recovery on my responsibility.
Still no bootloader or flash mode. Neither Emma nor Odin are identifying the phone. Although my phone lights blue, but the screen shows nothing!

Mohdhamm said:
The thing is even Sony flashtool (Emma) is not reading my phone, it detects a device in the USB port, but not the device!
Still no bootloader or flash mode. Neither Emma nor Odin are identifying the phone. Although my phone lights blue, but the screen shows nothing!
Click to expand...
Click to collapse
AFAIK, Emma hasn't been updated for a LONG time. It will remain defunct with no updates and no support. Use flashtool from androxyde if you want to continue using Sony's stock ROM.
No bootloader or flash mode detection: That usually means the drivers that interfaces with your phone is missing. Search around XDA for the correct fastboot and adb drivers for your PC's OS.
My approach for fixing your issue: Find the right drivers and put a stable Lollipop ROM on your sdcard. If you have fastboot working (make sure you have unlocked bootloader), flash boot image from the Lollipop zip and flash the recovery image found in some Lollipop threads. If everything goes well, your phone will bootloop, but you'll have working recovery. Press Vol Down when the Sony Logo appears on screen to enter TWRP. Since you saved a backup of your phone elsewhere, erase all the partitions (minus sdcard), format them to ext4, and flash the Lollipop ROM from your sdcard.

Related

[Q] Help crash after flash

First of all sorry for my English...
Yesterday I was trying to install vanir room to my p880 after 10 hours I rooted the phone and unlock the bootloader then installed cwm but after reboot I get stuck on logo so I used kdz and load LGP880AT-00-V20a-262-000-MAR-26-2013+0 with (after 4 hours ) then i try using twrp and finally load the room (vanir_p880_4.4.4.112414.zip) and Gapps after rebooting I started getting crashes ( aosp keyboard, com.google, home and back buttons etc didn't work)
so again kdz then i try other room Paranoid but the same thing..
What I'm doing wrong? I used factory reset, wipe etc but same results
what gapps you flashed?
blansh heretics
The ones that are here http://forum.xda-developers.com/showthread.php?t=2439739
But I load another rom without gapps and got same errors, wizard stopped, com.Google stopped. And keyboard.
G0ll0 said:
The ones that are here http://forum.xda-developers.com/showthread.php?t=2439739
But I load another rom without gapps and got same errors, wizard stopped, com.Google stopped. And keyboard.
Click to expand...
Click to collapse
I don't really know what happened, did you successfully flashed kdz?
Where did you get it from? Here?: http://lg-phone-firmware.com/index.php?id_mod=15
Try to flash one of these (choose correct one for you)
Than you have to install recovery again.
But before that you can try to wipe /system, /data, /cache and then flash CM11 (I know it works without problems)
And I recommend you these Gapps: http://forum.xda-developers.com/showthread.php?t=2397942
LGaljo said:
I don't really know what happened, did you successfully flashed kdz?
Where did you get it from? Here?: http://lg-phone-firmware.com/index.php?id_mod=15
Try to flash one of these (choose correct one for you)
Than you have to install recovery again.
But before that you can try to wipe /system, /data, /cache and then flash CM11 (I know it works without problems)
And I recommend you these Gapps: http://forum.xda-developers.com/showthread.php?t=2397942
Click to expand...
Click to collapse
well... yes i think I flashed kdz (LGFlashTool ?) I used kdz to recover my phone to original, I know my phone is Korean version and right now I use P88020A-EUR-XXX original firmware installed with kdz
What is CM11? and how i flash it?
so I have to root and unlock bootloader again and use twrp again right?
G0ll0 said:
well... yes i think I flashed kdz (LGFlashTool ?) I used kdz to recover my phone to original, I know my phone is Korean version and right now I use P88020A-EUR-XXX original firmware installed with kdz
What is CM11? and how i flash it?
so I have to root and unlock bootloader again and use twrp again right?
Click to expand...
Click to collapse
I think you should try with CWM first, get it: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.5-p880.img
you can flash it with this app if you are rooted: https://play.google.com/store/apps/details?id=com.cgollner.flashify
then you can download CM11 from here: http://download.cyanogenmod.org/?device=p880
and gapps from last mine post
and then boot to recovery, do factory reset and wipe /system, then flash rom and gapps.
Hope it helps
Crash After Flash OTA Vanir 5.0
I had a similar experience. I was installing OTA latest update of Vanir...not realising that it was 5.0...a screen came up telling me that it needed to flash another recovery...not realising why it needed that, I ignored the request to flash. Of course, I then "bricked" the phone. I was able to install the original JB 4.12 (v20c) back onto the phone but now it won't root. I've tried almost every method in this forum to no avail.:
ADB just gives a message "error: closing" when I use the boot.exe method
o4xr method does nothing
all-in-one method also does nothing
ADB does recognise the device. Drivers are installed. Any help is welcome!
BermiePT said:
I had a similar experience. I was installing OTA latest update of Vanir...not realising that it was 5.0...a screen came up telling me that it needed to flash another recovery...not realising why it needed that, I ignored the request to flash. Of course, I then "bricked" the phone. I was able to install the original JB 4.12 (v20c) back onto the phone but now it won't root. I've tried almost every method in this forum to no avail.:
ADB just gives a message "error: closing" when I use the boot.exe method
o4xr method does nothing
all-in-one method also does nothing
ADB does recognise the device. Drivers are installed. Any help is welcome!
Click to expand...
Click to collapse
Have you tried to flash a recovery using fastboot? You won't need to root (if you are going to use a custom ROM) and/or it will be easier with a custom recovery
Soft brick after last update.
Hello,
I seem to have a similar problem. I updated a few days ago using Vanir updater. There were no warnings re updating the recovery, just a warning regarding losing root. I checked restore root. The phone rebooted to the bootloader logo, then to a black screen. Now, I can access Cyanogen recovery, SW update mode, abd fastboot mode using buttons and the recovery options. ADB can see the phone only in recovery mode, but not in fastboot or SW update mode. CM recovery has no option to mount USB storage, so my PC cannot see the phone, and I cannot side load a new recovery and flash a new ROM.
Is there any way to use ADB if it cannot see your phone in fastboot or SW mode? Perhaps modify the settings.secure string to enable ADB? ADB can see the phone in recovery mode.
Otherwise I will try flashing a stock ROM via KDZ or LG firmware update tool, the re-root and proceed - but rooting was a major ordeal the first time, so I would like to avoid doing that again.
Thanks in advance.

Looking for help with failed flash.

Hi. I have a Xperia Z1 C6903 (honami) and I tried to install Cyanogenmod on it by following this tutorial:
http://wiki.cyanogenmod.org/w/Install_CM_for_honami
What I did:
1. Unlocked bootloader, had no problems with that.
2. Went to fastboot, flashed over Boot.img, after that I couldn't get to recovery (probably because I didn't install it first)
3. Tried another Boot.img for the Free Xperia project, after that my device had a flashing red light.
4. Reflashed the previous CM Boot.img back.
3. I was told to install recovery, so I installed TWRP (Still couldn't get to recovery mode)
http://forum.xda-developers.com/xperia-z1/general/rec-twrp-2-8-6-0-z1-honami-t3074845
Now I've downloaded Flashtool along with a general FTF file, my next plan was to flash the whole thing, but I'm asking if there was something I did wrong and how to fix up this mess?
Right now by going into recovery mode I get stuck at Sony logo, tried waiting 10 minutes but nothing.
EDIT: Tried to fix it by installing Emma, reinstalled stock lollipop ROM, and TA (I think that's recovery) and nothing, can't even see sony logo anymore
EDIT2: Flashed stock ROM with Flashtool, still doesn't work...

TWRP on z3c, flash error 7/no binary script found,no recognized by flashtool fastboot

Hello community,
I assume, I got a big problem. First of all, my z3c is stucked in away that i cant do anything right now.
I unlocked the bootloader some time ago and tried to flash cm on my phone. It didnt worked out for me and because i hadnt time, I was flashing via flashtool the concept android.
Yesterday I thought to try it once more. I was downloading the newest twrp for z3c and tried to flash cm from sd card and internal storage. Before I flashed, wiped th chache and personal etc.. But it says always there is a error 7, so I deleted the assets line in the update-script. Now if I want to flash cm or any other rom with the same change, it says that it couldnt find the binary-uptade (but actualy it is in the same folder). Afterwards I thought maybe it is because of the twrp and I wanted to change to the cm recovery via flashtool. I recognized that is impossible for me, because flashtool doesnt recognized my phone anymore. Win 7 says te driver is installed correctly, but shows the device as unknown! So I am stucked with twrp on my phone and cant flash via flashtool or twrp any rom.
Anyone got some help which I can do? Anything to get working rom on my phone for daily use? Thanks a lot in advance for your answer. And I am sorry if this problem was already posted.
Bests, Philipp

Fixing the "boot" partition instead of recovery

Hey there!
I am trying to flash TWRP 3.1.1-0 into my Xperia SP using ADB and apparently it cannot find the "recovery" partition. I've found out I can flash into "boot" instead but my question is, is there a way ( or should I even try) to fix this? I've tried Emma but my device is not supported. It's bootloader is unlocked and I am using Lineage OS 7.1
As far as I've searched in the forums ( https://forum.xda-developers.com/xperia-z-ultra/help/recovery-partition-xz-ultra-flashing-t3453568 ), at least for Xperia Z, it means the bootloader I originaly flashed used a "boot" partition instead of "recovery", right?
The final goal of this quest is to relock my bootloader so Sony Companion can reinstall the original firmware and get it as original as possible.
I am new here and, I hope I am posting this in the right section and I did my research right. This forum is so big it is a little overwhelming.
Thanks in advance!
flash recovery into boot
Hi,
I have a similar question: I want to flash LineageOS 14.1 to my Xperia SP Android 4.3 Build 12.1.A.1.205. I have unlock the Bootloader with the Code from developer.sonymobile.com/unlockbootloader
When I want to flash "fastboot flash recovery twrp-3.1.1-0-huashan.img" , it can not find the recovery partition.
Is it really possible to "fastboot flash boot twrp-3.1.1-0-huashan.img"??? After I have done this, I can reboot normally and TWRP will start? Then I will be able to install LineageOS?
Thanks!
FuchsXSP said:
Hi,
I have a similar question: I want to flash LineageOS 14.1 to my Xperia SP Android 4.3 Build 12.1.A.1.205. I have unlock the Bootloader with the Code from developer.sonymobile.com/unlockbootloader
When I want to flash "fastboot flash recovery twrp-3.1.1-0-huashan.img" , it can not find the recovery partition.
Is it really possible to "fastboot flash boot twrp-3.1.1-0-huashan.img"??? After I have done this, I can reboot normally and TWRP will start? Then I will be able to install LineageOS?
Thanks!
Click to expand...
Click to collapse
Yeah that's pretty much where I'm at right now. Whenever I flash TWRP into my Xperia SP using " fastboot flash boot twrp****.img" it works but when the phone boots the TWRP is all that is on the phone. It will not boot into the system. But then, when I install the OS using TWRP, the OS overwrites TWRP and I am back to the old cyanogenmod bootloader.
So answering your questions:
FuchsXSP said:
Is it really possible to "fastboot flash boot twrp-3.1.1-0-huashan.img"???
Click to expand...
Click to collapse
Yeah that's pretty much how it is done. At least on my Xperia SP. ( I love this phone btw XD)
FuchsXSP said:
After I have done this, I can reboot normally and TWRP will start?
Click to expand...
Click to collapse
Yeah it will only boot into TWRP. You probably wont have access to to your system anymore.
FuchsXSP said:
Then I will be able to install LineageOS?
Click to expand...
Click to collapse
Yeah, just press Install, select the file, and swipe that cool looking safety slider and it should be fine. Beware though older versions of LineageOS had some problems with zip signatures, just make sure to have the newest nightly version (07/12/2017 I guess) and you should be fine.
I have to say though, as anything with android modding, do at your own risk =p.
Here is the solution (at least, the one that worked for me)
I had similar problem - my phone was booting either into Lineage or TWRP, but I had to switch these using ADB commands.
Then I found an application in the Google Play store which can repair this. Look for "TWRP Manager (Requires ROOT)" - from Jmz Software. Free version is good enough.
I installed it and then when I tried to select the option to install TWRP, it tried to install, then complained that there is some problem with my configuration and it looks that it has been repaired. (I'm sorry for not repeating exact messages here, I was doing this about month ago, but when you install this application, the rest is quite self - explanatory).
Anyway, try this. Now my Xperia SP is booting flawlessly - Lineage or TWRP, of course "Reboot to Recovery" option in Lineage also is working correctly !
Xperia SP does not have a dedicated recovery partition like most of other Android phones and a newer Xperia variant. To workaround, the developers of this device have been using different ways of implementing recoveries, the latest and working one is by loading the recovery into our FOTAKernel partition, which is a partition that plays an important role during Stock OTA updates.
Since such a partition serve absolute no purpose when you ventured into custom ROMing, the idea of making use of it for recovery is quite neat. This "feature" is Adrian DC's implementation.
To answer to your question, no, you cannot flash a recovery using fastboot (or any other tools that makes use of fastboot). The options provided by the tool is only limited to partition names, not addresses. You can though, download the FOTA zip from the TWRP thread, and then flash them in the recovery (the one that you booted into because it was installed in /boot). Then re-flash the ROM zip so that the boot image of the ROM gets flashed properly.
It works
Hi,
I have success. On my Xperia SP is now LineageOS 14.1
1. Unlock Bootloader via Sony
2. fastboot flash boot twrp-3.1.1-0-huashan.img
3. reboot SP into twrp
4. wipe and install lineagesOS and opengapps
5. reboot
Now, i can access twrp with second recovery mode (FOTA)
Thanks for your help!! :good:
solved !
sorry to need to bump this thread, but i am having similar issues - i have successfully flashed twrp-huashan as shown in the post above, but on rebooting into twrp, wiping and installing adrian's oreo build, i lose access to twrp
attempting to boot to recovery shows a very brief droid on its back, and then tells me to choose to boot to system or recovery, neitherof which get me back to twrp
any suggestions, as i do not understand why this is so
edit : all is revealed !!
[Recovery][OFFICIAL][UBL] TWRP 3.2.1 Touch Recovery for Xperia SP
https://forum.xda-developers.com/xperia-sp/orig-development/recovery-twrp-3-0-0-touch-recovery-t3309938
Xperia z wont go into recoverymode. blue light with black screen
Hi im having a problem with my xperia z. i have rooted it fisrt then unlocked the bootloader but it wont show a recovery screen when i try and go into recovery mode to flash abd install lingeage. it just shows a blue light with black screen every time i try and go into recovery mode. cant seem to install twrp either. what do i do?
Blue light indicating fastboot mode on Sony Xperia Z5
Karimano24 said:
Hi im having a problem with my xperia z. i have rooted it fisrt then unlocked the bootloader but it wont show a recovery screen when i try and go into recovery mode to flash abd install lingeage. it just shows a blue light with black screen every time i try and go into recovery mode. cant seem to install twrp either. what do i do?
Click to expand...
Click to collapse
Well, that's it. The blue light indicates fastboot/recovery mode on the Xperia Z. You can now connect the Xperia to a computer via USB, then run e.g. 'fastboot devices' and it should list your Xperia. Or run 'fastboot flash recovery <image filename>' to flash TWRP onto the Xperia.

Stuck in fastboot after update today

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 .

Categories

Resources