I accidentally flashed a magisk_patched.img thinking that it is going to Install Magisk into my phone.
I entered the following command: fastboot flash boot magisk_patched.img (Not specifying the boot slots)
Once I rebooted, it says system UI is not responding.
I went back to fastboot mode, and entered the following commands knowing it had worked previously before:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
I tried switching boot slots, but both shows the same error once I am rebooted "System UI not responding".
I have no TWRP installed and I just want to start FRESH. I have the OOS 10.3.1 Zip file ready. I just do not know how to install it.
It also seems like my phone does not want to boot into recovery mode. It is currently stuck in fastboot. Both slots have this error.
Pleasee help me out!
Use MSMDownloadTool to reflash stock image. Follow directions of that. Can be found easily here on forums.
Alternatively, since fastboot is working you can try and use a fastboot version of OOS rom and flash without relocking bootloader.
AdlietMeyer said:
I accidentally flashed a magisk_patched.img thinking that it is going to Install Magisk into my phone.
I entered the following command: fastboot flash boot magisk_patched.img (Not specifying the boot slots)
Once I rebooted, it says system UI is not responding.
I went back to fastboot mode, and entered the following commands knowing it had worked previously before:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
I tried switching boot slots, but both shows the same error once I am rebooted "System UI not responding".
I have no TWRP installed and I just want to start FRESH. I have the OOS 10.3.1 Zip file ready. I just do not know how to install it.
It also seems like my phone does not want to boot into recovery mode. It is currently stuck in fastboot. Both slots have this error.
Pleasee help me out!
Click to expand...
Click to collapse
I still don't understand why people are so eagerly desperately searching to use patch img method.... We have a working TWRP you just have to fastboot boot temporarily twrp and flash Magisk zip installer....
Anyway, why did you mess with slots? 90% of time it leads to soft brick. You don't need to specify slot when fastbooting an img, it's flashed automatically on active one.
In your situation, try to fastboot flash the ROM, there is a thread in Guide News section providing OOS in fastboot format.
Or use MSMdownload to put your phone in factory fresh state, there is a thread in same section about that it's called 'collection of unbrick tools'
And my thread in same section explains how to root 10.3.1
Related
I don't really want to flash TWRP if it's not necessary to and I can just boot into it. And i'd rather see that I can boot into it before I flash it.
I understand that if i'm in the boot loader screen then I can issue the command fastboot boot twrp.img and it should go into the twrp boot loader without me needing to flash the boot loader to be twrp.
But it seems for some reason that when I issue that command I get a blank screen. The phone restarts and goes to a blank screen.
My phone is a nexus 4. I have android 4.3
I have downloaded twrp, from https://dl.twrp.me/mako/ I've tried the latest, that's
twrp-3.0.2-0-mako.img and i've tried the oldest, that's twrp-2.3.2.3-mako.img and I face the same issue
TIA
The bootloader is unlocked?
Yeah, bootloader is unlocked.
In the end I decided to forget about that command (fastboot boot twrp.img) and just flash the recovery. so, this command fastboot flash recovery twrp.img
I made sure to have the stock recovery too (recovery.img from an archive file from https://developers.google.com/android/nexus/images )
so I could flash that it back to stock, if flashing twrp recovery didn't work. But it worked.
I guess maybe the reason why I got/would get/get a black screen with my command, was because fastboot boot blah.img is to boot a kernel, not to boot a recovery? (I don't know if my terminology is all wrong?)
Hi there.
I'm trying to update my phone to Oreo January patch, I'm currently with December patch that is such bugged. Well as I read I have to download the update and before installing it I have to uninstall Magisk restoring the boot image and then after the update installing the boot image of Magisk again, I tried to flash the ROM with MiFlash saving the user data to solve it, and I did it but all my data just gone I don't know why, well the thing is that I updated, I thought, and then I flashed the patched boot image of Magisk in fastboot mode, and there is where I missed the boot image and I lost the update maybe...
Is there an option to flash JUST the boot image and not all the ROM or put the stock boot image just into a Magisk folder to have it?
If you install magisk using magisk manager, it will backup your original boot image and when you uninstall magisk, it will restore your boot image.
If you want to manually flash your boot image, you can do that in fastboot mode.
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
You can get your stock boot image from the rom files that you used in MiFlash tool. (boot image is inside that rom folder/zip file)
In miflash, you need to make sure you select the"save user data" option in the lower right corner. The file it will use is the "flash all except storage" file. Then, don't flash magisk. Update, them worry about rooting.
RavinduSha said:
If you install magisk using magisk manager, it will backup your original boot image and when you uninstall magisk, it will restore your boot image.
If you want to manually flash your boot image, you can do that in fastboot mode.
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
You can get your stock boot image from the rom files that you used in MiFlash tool. (boot image is inside that rom folder/zip file)
Click to expand...
Click to collapse
Hey, thanks for your answer, I manually flashed my boot image to update my phone to January Update but it didn't work, when I try to install the update it says "Couldn't install the update, try again later"
Any idea to solve this?
Hi,
I have a problem with a Moto G4. I tried to root the device and think I f***** up a bit.
After successfully installing TWRP I tried to install SuperSu using adb sideload and afterwards the device wouldn't boot anymore. Only fastboot and the recovery are still working. If I try to boot the device it just turns off. A factory reset didn't help.
I tried installing a LineageOS but nothing changed. It still boots into fastboot.
Can anybody help?
squanch123 said:
Hi,
I have a problem with a Moto G4. I tried to root the device and think I f***** up a bit.
After successfully installing TWRP I tried to install SuperSu using adb sideload and afterwards the device wouldn't boot anymore. Only fastboot and the recovery are still working. If I try to boot the device it just turns off. A factory reset didn't help.
I tried installing a LineageOS but nothing changed. It still boots into fastboot.
Can anybody help?
Click to expand...
Click to collapse
I forgot to say that I at first didn't install supersu systemless.
After I noticed that the device wouldn't boot anymore I tried installing it again systemless.
squanch123 said:
I forgot to say that I at first didn't install supersu systemless.
After I noticed that the device wouldn't boot anymore I tried installing it again systemless.
Click to expand...
Click to collapse
Hmm, did you wipe your system and data in TWRP before flashing LineageOS? You do not require root to flash LineageOS, just an unlocked bootloader and a compatible TWRP recovery (taking care to note if you need the 32 bit or 64 bit TWRP recovery for the respective custom ROM).
Also, with rooting on our G4/Plus, if you are on stock Nougat, you must flash a custom kernel (e.g. ElementalX) before you root. You'll otherwise experience the boot failures you're experiencing. Thus, to root on stock Nougat, unlock bootloader, flash/boot TWRP, backup, then flash ElementalX, then flash SuperSU/magisk.
Without knowing the current state of your device, I would suggest re-flashing your device with the stock firmware. Can you remember what stock firmware you had on your device before rooting initially?
echo92 said:
Hmm, did you wipe your system and data in TWRP before flashing LineageOS? You do not require root to flash LineageOS, just an unlocked bootloader and a compatible TWRP recovery (taking care to note if you need the 32 bit or 64 bit TWRP recovery for the respective custom ROM).
Also, with rooting on our G4/Plus, if you are on stock Nougat, you must flash a custom kernel (e.g. ElementalX) before you root. You'll otherwise experience the boot failures you're experiencing. Thus, to root on stock Nougat, unlock bootloader, flash/boot TWRP, backup, then flash ElementalX, then flash SuperSU/magisk.
Without knowing the current state of your device, I would suggest re-flashing your device with the stock firmware. Can you remember what stock firmware you had on your device before rooting initially?
Click to expand...
Click to collapse
Hi, thanks for your reply
Yes, I wiped system data and cache before flashing lineage. I just tried it again and I am still stuck in fastboot.
Unfortunately I don't remember the stock firmware version. Should I just try to flush the custom kernel and supersu afterwards?
squanch123 said:
Hi, thanks for your reply
Yes, I wiped system data and cache before flashing lineage. I just tried it again and I am still stuck in fastboot.
Unfortunately I don't remember the stock firmware version. Should I just try to flush the custom kernel and supersu afterwards?
Click to expand...
Click to collapse
Hmm, did you know if the flash of LineageOS reported okay within TWRP? Just out of interest, which TWRP and which build of LineageOS are you flashing (e.g. are you using the 32 bit TWRP or 64 bit TWRP, and are you flashing the 32 or 64 bit Lineage OS)?
That's confusing that even pressing 'start' in fastboot reboots your device rather than booting, even with a custom ROM... What happens if you boot to TWRP and try to reboot via TWRP? Is there a system to boot to?
Without the stock system on your device, there's no point to re-flashing the custom kernel/SuperSU, since you should have LineageOS on your device. Do you have a TWRP backup you could restore before you tried to root? If not, then what's your device model number (and if you can remember it, what software channel you're on, e.g. retus, reteu etc). ?
echo92 said:
Hmm, did you know if the flash of LineageOS reported okay within TWRP? Just out of interest, which TWRP and which build of LineageOS are you flashing (e.g. are you using the 32 bit TWRP or 64 bit TWRP, and are you flashing the 32 or 64 bit Lineage OS)?
That's confusing that even pressing 'start' in fastboot reboots your device rather than booting, even with a custom ROM... What happens if you boot to TWRP and try to reboot via TWRP? Is there a system to boot to?
Without the stock system on your device, there's no point to re-flashing the custom kernel/SuperSU, since you should have LineageOS on your device. Do you have a TWRP backup you could restore before you tried to root? If not, then what's your device model number (and if you can remember it, what software channel you're on, e.g. retus, reteu etc). ?
Click to expand...
Click to collapse
Yes, everything was ok with the flash.
I am using lineage-14.1-20180516-nightly-athene-signed and twrp-3.2.1-0-athene. I didn't see any options to choose between 32 and 64 bit. (Download pages: https://download.lineageos.org/athene#!name https://eu.dl.twrp.me/athene/)
It doesn't matter how I try to boot (powerbutton, fastboot, recovery) I always directly end up in fastboot.
No I don't have a backup. When I got the device it was resetted so I saw no point in making one :/ It is an XT1622 and it should be reteu.
squanch123 said:
Yes, everything was ok with the flash.
I am using lineage-14.1-20180516-nightly-athene-signed and twrp-3.2.1-0-athene. I didn't see any options to choose between 32 and 64 bit. (Download pages: https://download.lineageos.org/athene#!name https://eu.dl.twrp.me/athene/)
It doesn't matter how I try to boot (powerbutton, fastboot, recovery) I always directly end up in fastboot.
No I don't have a backup. When I got the device it was resetted so I saw no point in making one :/ It is an XT1622 and it should be reteu.
Click to expand...
Click to collapse
Okay, so they should both be 32 bit, so no worries there. There do seem to be a few reports of boot issues on the more recent official LineageOS builds https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101/page280 but I don't know if they are still existing on the build you've flashed.
As it's likely your device has been reset when you flashed LineageOS (I don't know if there are still files on your internal storage, which you can view in TWRP, so back up if you do have files), you may wish to look into a stock firmware flash. Here's the April 2018 NPJS25.93-14-18 firmware, which appears to be the build released to EU devices: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You do not have to re-lock your bootloader if you don't wish to - if you wish to leave your bootloader unlocked, then flash the stock firmware via fastboot with the following flashing commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Flashing these files via ADB should put a fresh copy of the latest firmware onto your device, which should then boot. If it does boot, then you can proceed with rooting (flash TWRP, then back up, then flash ElementalX or vegito, then flash SuperSU or magisk).
echo92 said:
Okay, so they should both be 32 bit, so no worries there. There do seem to be a few reports of boot issues on the more recent official LineageOS builds https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101/page280 but I don't know if they are still existing on the build you've flashed.
As it's likely your device has been reset when you flashed LineageOS (I don't know if there are still files on your internal storage, which you can view in TWRP, so back up if you do have files), you may wish to look into a stock firmware flash. Here's the April 2018 NPJS25.93-14-18 firmware, which appears to be the build released to EU devices: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 You do not have to re-lock your bootloader if you don't wish to - if you wish to leave your bootloader unlocked, then flash the stock firmware via fastboot with the following flashing commands:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Flashing these files via ADB should put a fresh copy of the latest firmware onto your device, which should then boot. If it does boot, then you can proceed with rooting (flash TWRP, then back up, then flash ElementalX or vegito, then flash SuperSU or magisk).
Click to expand...
Click to collapse
Thanks for the help!
I can boot the stock rom and I have root access. However if I start or shut down the device it goes to fastboot. From there I can boot or shut down the device and everything seems to work Do you know how I can boot directly without fastboot?
squanch123 said:
Thanks for the help!
I can boot the stock rom and I have root access. However if I start or shut down the device it goes to fastboot. From there I can boot or shut down the device and everything seems to work Do you know how I can boot directly without fastboot?
Click to expand...
Click to collapse
Hmm, try booting back to the bootloader, attach your device to your computer, then open ADB. In ADB, type 'fastboot oem fb_mode_clear' without the quotes. Press enter to submit, then reboot and see if your device boots to system rather than to fastboot.
This command should clear fastboot mode (though useful when flashing).
echo92 said:
Hmm, try booting back to the bootloader, attach your device to your computer, then open ADB. In ADB, type 'fastboot oem fb_mode_clear' without the quotes. Press enter to submit, then reboot and see if your device boots to system rather than to fastboot.
This command should clear fastboot mode (though useful when flashing).
Click to expand...
Click to collapse
Yes that worked
Thank you very much for your help :victory:
I flashed 3.3.1-2 twrp and then installed a couple different roms to compare. Then I'm not quite sure what happened, I know I formatted and tried to install another, then I lost access to twrp. Even though it says I'm successful at flashing it, it won't boot into twrp or any recovery for that matter. What should I do? I've tried two different twrp's and neither will boot up. I've tried the .bat and volume+ and power, and I even tried with the fastboot boot twrp.img command.
willineedhelp said:
I flashed 3.3.1-2 twrp and then installed a couple different roms to compare. Then I'm not quite sure what happened, I know I formatted and tried to install another, then I lost access to twrp. Even though it says I'm successful at flashing it, it won't boot into twrp or any recovery for that matter. What should I do? I've tried two different twrp's and neither will boot up. I've tried the .bat and volume+ and power, and I even tried with the fastboot boot twrp.img command.
Click to expand...
Click to collapse
What do you see exactly when you try to enter recovery mode? Stock recovery? Or fastboot? Which recovery have you tried? (provide links)
willineedhelp said:
I flashed 3.3.1-2 twrp and then installed a couple different roms to compare. Then I'm not quite sure what happened, I know I formatted and tried to install another, then I lost access to twrp. Even though it says I'm successful at flashing it, it won't boot into twrp or any recovery for that matter. What should I do? I've tried two different twrp's and neither will boot up. I've tried the .bat and volume+ and power, and I even tried with the fastboot boot twrp.img command.
Click to expand...
Click to collapse
Hello, download fastboot rom and flash this files
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
For twrp use bat file to install for u don't do it manually..
SomethingWentWrong said:
What do you see exactly when you try to enter recovery mode? Stock recovery? Or fastboot? Which recovery have you tried? (provide links)
Click to expand...
Click to collapse
Fastboot mode
farhan20 said:
Hello, download fastboot rom and flash this files
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
For twrp use bat file to install for u don't do it manually..
Click to expand...
Click to collapse
I'll give that a shot, thanks!
farhan20 said:
Hello, download fastboot rom and flash this files
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
For twrp use bat file to install for u don't do it manually..
Click to expand...
Click to collapse
Oh man you're a life saver! Worked perfectly! Thanks so much!
willineedhelp said:
Oh man you're a life saver! Worked perfectly! Thanks so much!
Click to expand...
Click to collapse
Glad to know I was able to help, it happens with me and this is how I fixed ?
Hello! Had the same problem and the procedure let me access recovery, yet everytime I reboot to system, the phone opens recovery instead.
I tried restoring a backup but rom is unstable and stuff keeps crashing. Any ideas?
EDIT: did a fastboot flash of .9 ROM and at got it back to work.
farhan20 said:
Hello, download fastboot rom and flash this files
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
For twrp use bat file to install for u don't do it manually..
Click to expand...
Click to collapse
So I tried to go back to MIUI and it did it again, I did the default wipe and tried to install it. It got stuck in a bootloop and wouldn't go into TWRP again. Tried what you prescribed again, but that didn't work. I tried using the command (fastboot boot recovery.img) and it just shut off. It's clearly not flashing TWRP, but I have no idea why. I tried both 3.3.1-2 and 3.3.1-3, neither worked. I tried flashing more of the fastboot ROM images, but that did nothing either. Any suggestions? I'm having to use my old moto g5 until I get this fixed, so help ASAP would be amazing. Thanks in advance!
willineedhelp said:
So I tried to go back to MIUI and it did it again, I did the default wipe and tried to install it. It got stuck in a bootloop and wouldn't go into TWRP again. Tried what you prescribed again, but that didn't work. I tried using the command (fastboot boot recovery.img) and it just shut off. It's clearly not flashing TWRP, but I have no idea why. I tried both 3.3.1-2 and 3.3.1-3, neither worked. I tried flashing more of the fastboot ROM images, but that did nothing either. Any suggestions? I'm having to use my old moto g5 until I get this fixed, so help ASAP would be amazing. Thanks in advance!
Click to expand...
Click to collapse
Nvm, I just had a junk TWRP version.
willineedhelp said:
So I tried to go back to MIUI and it did it again, I did the default wipe and tried to install it. It got stuck in a bootloop and wouldn't go into TWRP again. Tried what you prescribed again, but that didn't work. I tried using the command (fastboot boot recovery.img) and it just shut off. It's clearly not flashing TWRP, but I have no idea why. I tried both 3.3.1-2 and 3.3.1-3, neither worked. I tried flashing more of the fastboot ROM images, but that did nothing either. Any suggestions? I'm having to use my old moto g5 until I get this fixed, so help ASAP would be amazing. Thanks in advance!
Click to expand...
Click to collapse
What MIUI version you have tried to go back?
Got this working with Lineage ok but decided to go back to stock. I downloaded the stock recovery rom from NV and set everything up. Inside the recovery bundle is a bat file. Usually I would flash all files manually but this time I used the bat file. It manged the first 3 or 4 commands then came up with error. The box is now stuck in a boot loop and I am unable to access over adb.
Can anyone please suggest a way around this.
Thanks
Here is the bat file
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash dtb mdarcy.dtb.img
fastboot flash vbmeta vbmeta.img
fastboot oem lock (optional step: required for certain functionality)
fastboot reboot
EDIT:
Eventually managed to flash lineage zip again. Used USB keyboard to access recovery
may i ask, what kind of keyboard did u use?
thanks in advance