Hi,
Few days ago I bought used Nexus 6, which was come with locked bootloader and stock Android 7.1.
I wanted to flash some custom ROM. First I tried to unlock a bootloader.
I was using an XDA Video Tutorial showing how to unlock and root the Nexus 6 and a tutorial on LineageOS site. I could unlock the bootloader quite easily but unfortunately I forgot to reboot the device (eg. with command "fastboot reboot") and I strightly tried flash a custom recovery.
It flashed well (as described in command line window) but couldn't get into TWRP recovery. Device showed dead green android with description.
System is booting normal and the bootloader is unlocked. But unfortunately I can't flash the custom recovery. I reinstalled all android drivers (I installed full Android Studio with packages suggested by the tutorial). After flash there is no custom recovery - still dead android and possibility to launch stock recovery. Once I could launch TWRP, when I do not reboot phone after flashing recovery and strightly go to recovery (from bootloader). But when I reboot to system and try launch TWRP again - again no custom recovery...
There is also a problem when I try to root the device using CF-Root - it shows some error and device is still not rooted, also without a SU icon in system.
Is there any solution for that? Are these problems a reason of my mistake with not rebooting the phone after unlocking the bootloader?
Thanks a lot for any suggestions and help. If it necessary I can update my post with more details.
Wysłane z mojego Transformer TF101 przy użyciu Tapatalka
Well, the first thing that stands out is you using CF-Autoroot. Kind of putting the cart before the horse there. Also unnecessary, for once TWRP is installed you can simply flash a root solution through it.
Anyway, when you have the N6 in bootloader mode, what happens when you type "fastboot flash recovery recovery.img"? Any error messages? The output of the command will be useful here.
The fact you didn't reboot between commands does not mean you did any damage. Simply start over again.
I am adding photos of bootloader and command line windows after flashing the recovery. It looks that there aren't any errors.
Maybe this is happening because of encrypted device? I saw that my phone is encrypted but i don't doing this before, I restored it to factory settings.
Your images are unreadable. Perhaps it's my data connection.
Encryption has nothing to do with this. Regardless, if you didn't see any errors, what happens now when you enter the bootloader, scroll down to recovery mode, and press power?
OK, I add this images again and I hope it would be readable now.
When I entered the recovery from bootloader a dead android appears with description "No command" below. Then I could press and hold the power button to reboot the device or press and hold for a second VOL+ and POWER to enter the stock recovery...
Maybe your twrp is installed correctly, and you just use the wrong method to start it?
The best way to start it is to reboot with all buttons pressed, and then select recovery.
Edit: didn't see you new post
Hmm, maybe something is wrong with the drivers and maybe with Windows. Maybe I will try flashing recovery on Linux.
I'll tell you right now, nothing is wrong with the drivers. Apparently you typed everything correctly, but humor me on this one please? Rename your TWRP image from its current name to "twrp.img", then flash it via fastboot. What I'm trying to see is if a potential keypunch error is causing your problem. "fastboot flash recovery twrp.img" is a lot easier to type than the default.
Also, what happens when you execute the command, "fastboot boot twrp.img"?
Your bootloader screen looks like mine, except that your serial number has a different structure.
Mine is dd123456 (real numbers replaced). Notice the small letters at the beginning, whereas yours has capitals mixed with numbers, and is longer.
I don't know if we can conclude anything from that.
@runekock: You can't. Mine is ZY222***** and installing TWRP here has never been a problem. I'm almost certain this is a simple userspace issue.
After flashing TWRP are you going directly into recovery mode before rebooting? I seem to recall that some ROMS will replace a custom recovery with the stock recovery unless you boot in to TWRP before booting into the OS.
I have already tried many combinations like flashing older versions, renaming (twrp.img and recovery.img) and rebooting device after flashing or going strightly to recovery after flashing. Only the last option could launch TWRP recovery, but even if I swipe to allow modifications the recovery is missing after reboot. It looks exactly like the original stock ROM is still replacing this custom recovery.
I also tried flashing on Linux and without any changes. I also tried updating recovery on my old Moto G and it was succesful operation - so it is probably not a problem with a computer or with drivers.
Maybe I should do something like that - flash TWRP, go to it directly after flashing, copy custom ROM or SuperSU file to the memory, wipe and flash ROM or SuperSU. Maybe that could help? What do you think, is it safe to try?
Wysłane z mojego Transformer TF101 przy użyciu Tapatalka
fastboot boot recovery.img doesn't install the recovery, but does let you conduct recovery operations on the device. In this case it also verifies that the TWRP image isn't somehow corrupt.
Unfortunately, after confirming that there's nothing at fault with the PC, nothing at fault with ADB and Fastboot, and nothing at fault with the device itself, the only thing that is left is...you.
If you haven't taken a look at the Nexus 6 All-in-one Flashing Guide in Nexus 6 General, I suggest you do so. It's a very good thread and has a lot of advice that might be useful to you.
In this guide there's the note about how important is rebooting the device after unlocking bootloader...
But I see on the Internet similar problems as mine.
0sA said:
I have already tried many combinations like flashing older versions, renaming (twrp.img and recovery.img) and rebooting device after flashing or going strightly to recovery after flashing. Only the last option could launch TWRP recovery, but even if I swipe to allow modifications the recovery is missing after reboot. It looks exactly like the original stock ROM is still replacing this custom recovery.
I also tried flashing on Linux and without any changes. I also tried updating recovery on my old Moto G and it was succesful operation - so it is probably not a problem with a computer or with drivers.
Maybe I should do something like that - flash TWRP, go to it directly after flashing, copy custom ROM or SuperSU file to the memory, wipe and flash ROM or SuperSU. Maybe that could help? What do you think, is it safe to try?
Wysłane z mojego Transformer TF101 przy użyciu Tapatalka
Click to expand...
Click to collapse
Occasionally I have had the same issue of the ROM replacing TWRP with the stock recovery. At that point I just do:
adb reboot bootloader
fastboot flash recovery recovery.img (twrp renamed to recovery.img)
adb reboot bootloader
press the down arrow twice to reboot into recovery
I DO NOT allow modifications
select reboot and reboot into recovery again
select reboot and boot into the OS (reboot system)
Some of those steps may not be necessary but that is what has worked for me.
It looks like I found a solution. I flashed TWRP, reboot bootloader and entered recovery directly from bootloader. I copied Chainfire's SuperSU to the phone, unplugged it from PC and flashed this SuperSU (and also wipe cache after flash). Reboot the phone and system is rooted! I updated TWRP Official App from Play Store and permited root privileges, downloaded latest TWRP recovery and flashed it from this app. When I entered the recvery (from bootloader) it was TWRP! Even if I reboot the device, the TWRP recovery seems not missing.
Wysłane z mojego Transformer TF101 przy użyciu Tapatalka
Related
I'm what you'd call a super noob at this stuff and I've got my poor little SP in a crazy bootloop... I've tried LITERALLY EVERYTHING the internet has told me to try; wiping every cache out there, flashing custom roms, stock roms, you name it. It began when I just got CWM (don't ask me why it happened then, I have no clue why) and this is even BEFORE I put a ROM on! (I was all ready to put a ROM after getting CWM but bootloop happened).
Note: I have CWM recovery, I think I have lost my stock recovery, if I try some ROMS (ex. CM 12) they give me this error 7, once I found certain ROMS (PACMAN ROM, unofficial stock ROM) that would flash and install, they did but still left me with a bootloop, I have tried wiping so many caches it's not even funny, I've tried flashing the original firmware, nothing works... so I'm here for help.
I have looked at every google link and every method possible in trying to fix this thing! I really can't afford a new phone and I just love this one too much... please help!
farahtasnim said:
I'm what you'd call a super noob at this stuff and I've got my poor little SP in a crazy bootloop... I've tried LITERALLY EVERYTHING the internet has told me to try; wiping every cache out there, flashing custom roms, stock roms, you name it. It began when I just got CWM (don't ask me why it happened then, I have no clue why) and this is even BEFORE I put a ROM on! (I was all ready to put a ROM after getting CWM but bootloop happened).
Note: I have CWM recovery, I think I have lost my stock recovery, if I try some ROMS (ex. CM 12) they give me this error 7, once I found certain ROMS (PACMAN ROM, unofficial stock ROM) that would flash and install, they did but still left me with a bootloop, I have tried wiping so many caches it's not even funny, I've tried flashing the original firmware, nothing works... so I'm here for help.
I have looked at every google link and every method possible in trying to fix this thing! I really can't afford a new phone and I just love this one too much... please help!
Click to expand...
Click to collapse
please state your current bootloader status. Is it unlocked or still locked?
TechnoSparks said:
please state your current bootloader status. Is it unlocked or still locked?
Click to expand...
Click to collapse
I have unlocked my bootloader. Thank you for replying!
farahtasnim said:
I have unlocked my bootloader. Thank you for replying!
Click to expand...
Click to collapse
Splendid! Knowing that your BL state is unlocked, this will make the whole process A LOT easier!
http://forum.xda-developers.com/xperia-sp/development/ubl-twrp-f2fs-support-xperia-sp-huashan-t3150230
Please go to the above link to get TWRP. Also, please keep in mind that TWRP is now the only still supported recovery around. CWM and PhilZ are both really outdated and no longer maintained due to the introduction of Cyanogen Recovery which is very minimal in features.
Once you get yourself the download, extract the files from the zip and get the twrp.img file. We will need this to flash into the boot partition of Xperia SP, granting you a direct boot into recovery once it is flashed. Please then copy the original zip to your sd card, as we will be flashing the original zip via TWRP later to give you access to TWRP in the future.
Using your preferred tool, flash the twrp.img file into the boot partition.
Connect your Xperia SP via fastboot. Make sure SP is shut down, hold volume up key and connect the SP with your computer.
If you're using a fastboot tool via command prompt, the command would be
fastboot flash boot twrp.img
If you're using flashtool, hit the lightning icon in the toolbar, select fastboot mode. Then select "Select kernel to flash". Make sure the file type is "img" else you won't able to find your TWRP img file. Navigate to mentioned img file and select it.
Afterwards, when flashing complete, you may insert sdcard and start the device. It will boot directly into TWRP as we flashed a recovery to the boot partition.
Clean wipe data, cache, dalvik cache, system. You may leave internal storage.
Flash the ROM zip you acquired (make sure file integrity is checked beforehand!) then the TWRP zip earlier. Flashing the TWRP zip grants you a persisting recovery, as explained in the linked thread.
You may now reboot and enjoy
Hello,
I am new to this forum, but have done a bit of unlocking and installing custom roms on other phones (mostly OPO's, both my old one and friends). But this new OP 3T I just got is giving me some troubles I have not encountered before. I would LOVE to put this into the correct forum, but of course with my being new to this forum...rules...
I am following the standard install over on the TWRP site and on the OP3T, the install finishes and then I reboot and I get a screen that says:
"Your device has been unlocked and can't be trusted. If you don't want to see this screen, please lock your device by "fastboot oem lock" an erase userdata..."
I have never seen this before. Can someone give me a idea what could be going on here? Do I need to re-lock it? What did OP do to their phones!!?!
Oh and also, I am planning on installing LineageOS. Any reason I shouldn't?
Thanks!
Blenderite said:
Hello,
I am new to this forum, but have done a bit of unlocking and installing custom roms on other phones (mostly OPO's, both my old one and friends). But this new OP 3T I just got is giving me some troubles I have not encountered before. I would LOVE to put this into the correct forum, but of course with my being new to this forum...rules...
I am following the standard install over on the TWRP site and on the OP3T, the install finishes and then I reboot and I get a screen that says:
"Your device has been unlocked and can't be trusted. If you don't want to see this screen, please lock your device by "fastboot oem lock" an erase userdata..."
I have never seen this before. Can someone give me a idea what could be going on here? Do I need to re-lock it? What did OP do to their phones!!?!
Oh and also, I am planning on installing LineageOS. Any reason I shouldn't?
Thanks!
Click to expand...
Click to collapse
Is nothing wrong with your device ..What you get is a warning that your bootloader is unlocked ...
You gonna get this every time you want to boot to your ROM or to twrp....
You can proceed further to install any ROM that you like...
I think you can find a guide on XDA forums to disable this warning if you want...
cultofluna said:
Is nothing wrong with your device ..What you get is a warning that your bootloader is unlocked ...
You gonna get this every time you want to boot to your ROM or to twrp....
You can proceed further to install any ROM that you like...
I think you can find a guide on XDA forums to disable this warning if you want...
Click to expand...
Click to collapse
Ok I tried that and a new problem came up!! When I try to reboot into recovery, I do not get TWRP, but the stock recovery that was there originally! Unless they have completely changed the look of TWRP. I will try to upload a picture of it if that helps.
You can't get rid of the bootloader-unlocked warning without re-locking your bootloader, which you really should not do while you have a custom recovery installed.
Are you sure you've flashed TWRP and not just booted it it from a local file on your computer? Try using fastboot to wipe recovery first before flashing TWRP.
Anova's Origin said:
You can't get rid of the bootloader-unlocked warning without re-locking your bootloader, which you really should not do while you have a custom recovery installed.
Are you sure you've flashed TWRP and not just booted it it from a local file on your computer? Try using fastboot to wipe recovery first before flashing TWRP.
Click to expand...
Click to collapse
I followed the Fastboot method on this page (rules won't let me post the link normally): twrp. me/devices/oneplus3t.html
Blenderite said:
I followed the Fastboot method on this page (rules won't let me post the link normally): twrp. me/devices/oneplus3t.html
Click to expand...
Click to collapse
Right on that page (last paragraph of fastboot install method), you will see:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
I had a heck of a time with this myself (even reading the above). Even rebooting (after flash TWRP) to recovery (power+vol down), the TWRP install would still not "stick". Had to try multiple times. I also rooted with SuperSU 2.79 at some point in that process, which may or may not have helped TWRP to finally "stick".
redpoint73 said:
Right on that page (last paragraph of fastboot install method), you will see:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
I had a heck of a time with this myself (even reading the above). Even rebooting (after flash TWRP) to recovery (power+vol down), the TWRP install would still not "stick". Had to try multiple times. I also rooted with SuperSU 2.79 at some point in that process, which may or may not have helped TWRP to finally "stick".
Click to expand...
Click to collapse
I tried this once before, but after your suggestion to try it several times, it finally worked! Thanks!!
Flash TWRP, reboot, press the volume down key before the phone boots, go into recovery, you should see TWRP flash screen, that usually works but I'm glad you got it going
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.
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 .
My phone keeps getting stuck on fastboot mode.
I'll flash the standard MIUI ROM using the MiFlash Tool, then I flash a custom recovery and a custom ROM(EvolutionX in this case), everything works and I can set up my phone, but as soon as I reboot I can no longer boot into android or recovery. i've tried flashing multiple recoveries using fastboot and straight up booting a recovery using "fastboot boot recovery.img" but it still always go to fastboot. The only solution is to start the process all over again, and obviously that's just not an option since I can never turn my phone off after that.
Any tips?
I think I got it solved, at least I got it to reboot into Android and TWRP.
I used this guide, but I'll write the steps I took here in case you're having the same issue. I wound up using xiaomi.eu MIUI rom, but it shouldn't matter what you use, I'll assume you're stuck in fastboot.
Do "fastboot flash vendor vendor.img", you get this vendor.img from the fastboot version of the official MIUI ROM, after you decompress the .tar.gz it should be in the "images" folder
Do "fastboot flash recovery twrp.img" then "fastboot boot twrp.img", this should flash twrp as your recovery and then boot into it, for some reason it only worked with the official twrp, not orange fox.
Assuming you got into TWRP you should now flash the latest firmware(I got mine from xiaomifirmwareupdater.com) make sure you download just the firmware not the entire rom, mine was named something like fw_raphael_miui... .zip
Format data (not wipe, format, it's a separate option in TWRP), it should ask you to type yes, so do that.
Flash whatever ROM you want
Hopefully this helps you, I hate finding forum posts marked "solved" but with no instructions. I also tried the "vbmeta_dv_shivsom.img" method some threads mentioned but it didn't work
Here's a pastebin of the guide I used in case the original link goes down
You can get all the files I mentioned from xiaomifirmwareupdater.com and the official TWRP site
Out of all that, the one instruction that solves it is the format data step. This is the magic step required. You always need to do this when flashing over MIUI.
Flashing vendor was totally irrelevant.
This will tell you what you need to do.
Simple Guide to flashing successfully
Here's a quick guide to some of the basics. Which recovery. ---------------------------- Use the latest from here. https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363/post79823568 Do not use Orange...
forum.xda-developers.com
Thanks a lot man! I'm having this issue and it is beyond annoying. I've lost so much time with this BS.
Edit: Does not help actually
I just had the same problem with my Lamentablet.
I was trying stuff up and restarted it in fastboot mode and got stuck there.
So, ways to deal with it:
adb reboot recovery
rebooted the tablet in recovery mode. All I had then was to press the power button to activate Reboot. Solved! From now on it boots normally.
Meanwhile I had discovered that by typing
fasboot continue
the tablet would resume, but at the next reboot cycle, power down + up cycle or reboot after a crash, the tablet would reboot into fastboot mode...
And I found this out when it crashed (it's not called a Lamentablet for nothing!).
Luckily I had a PC with Linux around. It didn't have the software installed but drivers were already in the Kernel and installing adb and fastboot was a matter of mere seconds. If I didn't have an easily ready PC at hand, this tablet would have become a brick until plugged in and rebooted...
OMG Thanks dude.... I'm literally working to installing custom rom on redmi 7a from stock rom but I don't know what reason that make my phone always stuck on fastboot when format data, before this was fine.
Osga21 said:
I think I got it solved, at least I got it to reboot into Android and TWRP.
I used this guide, but I'll write the steps I took here in case you're having the same issue. I wound up using xiaomi.eu MIUI rom, but it shouldn't matter what you use, I'll assume you're stuck in fastboot.
Do "fastboot flash vendor vendor.img", you get this vendor.img from the fastboot version of the official MIUI ROM, after you decompress the .tar.gz it should be in the "images" folder
Do "fastboot flash recovery twrp.img" then "fastboot boot twrp.img", this should flash twrp as your recovery and then boot into it, for some reason it only worked with the official twrp, not orange fox.
Assuming you got into TWRP you should now flash the latest firmware(I got mine from xiaomifirmwareupdater.com) make sure you download just the firmware not the entire rom, mine was named something like fw_raphael_miui... .zip
Format data (not wipe, format, it's a separate option in TWRP), it should ask you to type yes, so do that.
Flash whatever ROM you want
Hopefully this helps you, I hate finding forum posts marked "solved" but with no instructions. I also tried the "vbmeta_dv_shivsom.img" method some threads mentioned but it didn't work
Here's a pastebin of the guide I used in case the original link goes down
You can get all the files I mentioned from xiaomifirmwareupdater.com and the official TWRP site
Click to expand...
Click to collapse
thanks bro. flashing vendor after a format from twrp did the good