Related
Hello, I'm in a bit of a confusing situation so I hope that someone can shed light on it.
Last night I got a notification that my phone is ready to install the 4.4 update. I didn't have the time or the battery to install it then, so I just left my phone until today. Today, I happily pressed the update button, my phone restarted, it started to update and when the bar was a little more then a third full it stopped and said "Error!" (Thanks for a very informative error message Google! ) I restarted my phone, and now my phone reports that it's up to date?! I tried tapping the Check now, but it keeps saying it's up to date. I checked my cache folder, and there is a .zip file containing the update.
My phone is rooted, I used the Nexus 4 Rootkit, but I DIDN'T install a custom recovery or try to install any custom ROMs. (I'm happy with the stock one) I only installed SuperSU so I can grant root access to some apps and that's it. I didn't install any tweaks.
Now if I'm not mistaken, the OTA update should have worked on my phone, because everything is stock. So why did this happen and why I'm not receiving the update prompt again?
Also as a side note: When I went into the fastboot mode and tried to launch the Recovery mode, it said "No command!" and I had restart my phone.
No, you're wrong. You should've gone to SuperSU app and pressed the "full unroot" button before trying to OTAupdate. This would've replaced the modified bin files for root by the original files, allowing the OTA to be applied successfully.
This happens because the rooting process modifies some system files, so the OTA detects a non-stock scenario and aborts its installation. Also when the OTA fails, a flag marks this update as a "fail update" so your system will continue to show you that it's "updated" as he thinks the only update available isn't suitable for you. He is just waiting for the next OTA update.
Now you have to install the OTA via sideload / adb. I would recommend to make a full nandroid backup before everything else. Then fully unroot your phone and apply the OTA using adb.
This is exactly what happened to me when trying to update from 4.2.2 to 4.3. I was root (obtained with Nexus 4 Toolkit from WugFresh) with stock recovery. Just root, nothing else. Then I tried to install OTA, because with older versions to be root was not a problem. But now it is, and my OTA failed as it failed to you.
Then I managed to manually apply the OTA doing what I told you: first backup, then unroot, and finally using the sideload / adb process button present in the toolkit, following its advices at each pont (very VERY well explained for non-experts). You will need to manually download the OTA update to 4.4. Look for that in these forums.
Hope this helps!
LORD MJ said:
Hello, I'm in a bit of a confusing situation so I hope that someone can shed light on it.
Last night I got a notification that my phone is ready to install the 4.4 update. I didn't have the time or the battery to install it then, so I just left my phone until today. Today, I happily pressed the update button, my phone restarted, it started to update and when the bar was a little more then a third full it stopped and said "Error!" (Thanks for a very informative error message Google! ) I restarted my phone, and now my phone reports that it's up to date?! I tried tapping the Check now, but it keeps saying it's up to date. I checked my cache folder, and there is a .zip file containing the update.
My phone is rooted, I used the Nexus 4 Rootkit, but I DIDN'T install a custom recovery or try to install any custom ROMs. (I'm happy with the stock one) I only installed SuperSU so I can grant root access to some apps and that's it. I didn't install any tweaks.
Now if I'm not mistaken, the OTA update should have worked on my phone, because everything is stock. So why did this happen and why I'm not receiving the update prompt again?
Also as a side note: When I went into the fastboot mode and tried to launch the Recovery mode, it said "No command!" and I had restart my phone.
Click to expand...
Click to collapse
nyepo said:
No, you're wrong. You should've gone to SuperSU app and pressed the "full unroot" button before trying to OTAupdate. This would've replaced the modified bin files for root by the original files, allowing the OTA to be applied successfully.
This happens because the rooting process modifies some system files, so the OTA detects a non-stock scenario and aborts its installation. Also when the OTA fails, a flag marks this update as a "fail update" so your system will continue to show you that it's "updated" as he thinks the only update available isn't suitable for you. He is just waiting for the next OTA update.
Now you have to install the OTA via sideload / adb. I would recommend to make a full nandroid backup before everything else. Then fully unroot your phone and apply the OTA using adb.
This is exactly what happened to me when trying to update from 4.2.2 to 4.3. I was root (obtained with Nexus 4 Toolkit from WugFresh) with stock recovery. Just root, nothing else. Then I tried to install OTA, because with older versions to be root was not a problem. But now it is, and my OTA failed as it failed to you.
Then I managed to manually apply the OTA doing what I told you: first backup, then unroot, and finally using the sideload / adb process button present in the toolkit, following its advices at each pont (very VERY well explained for non-experts). You will need to manually download the OTA update to 4.4. Look for that in these forums.
Hope this helps!
Click to expand...
Click to collapse
Thanks. Unfortunetly the OTA update failed even when I tired ADB sideload, so I had to flash the factory image. Now it works like a charm.
LORD MJ said:
Thanks. Unfortunetly the OTA update failed even when I tired ADB sideload, so I had to flash the factory image. Now it works like a charm.
Click to expand...
Click to collapse
It failed because you have modified files in your system, such as modified gps.conf or build.prop, custom kernel and non-official radio will give errors too.
I did a "flash stock+unroot" and relocked my device via the Wug app and it still errors
eksasol said:
It failed because you have modified files in your system, such as modified gps.conf or build.prop, custom kernel and non-official radio will give errors too.
Click to expand...
Click to collapse
I really have no idea how did that happen. Maybe some app modified it or I messed some things up. I'm now going to make a full backup of my phone, so I can apply the next OTA with much less pain.
LORD MJ said:
I really have no idea how did that happen. Maybe some app modified it or I messed some things up. I'm now going to make a full backup of my phone, so I can apply the next OTA with much less pain.
Click to expand...
Click to collapse
The OTA update can fail for many reasons, it could be due to any changes to the /system partition which is what root does, such as changes to gps.conf file, changes in build.prop, different kernel or radio.
If you're going to make a full backup, what you should do is flash a full factory image (link in my signature, and provided you already backup your data.) Then boot into a custom recovery to make a full backup, (not flash the recovery, but: fastboot boot twrp.img) When you do the backup make sure the boot (kernel) and recovery partition are selected. However, you can't backup the radio partition, but that should be fine unless you intend to use the LTE radio.
I have a similar problem. I have ROOTED device with TWRP recovery and stock 4.3 android (obtained OTA before rooting), and I just got notification that my OTA update to 4.4 is ready to be installed.
So I clicked Restart and Install button and the phone restarts(as it should) but after that it went in TWRP recovery and waited for some instruction I suppose. I didn't know what to click exactly, so I clicked Reboot from TWPR menu and it went in fastboot mode. From fastboot I chose Start and phone turns on. Updating didn't even start..
So, were there something that I could do when I was in TWRP recovery that could initiate updating process, or I never had a chance?
What exactly I should do to get that update on my phone? Sorry for my English and if was unclear.
Does anyone know how I can update when having TWRP installed and rooted ?
The phone says there is an update but doesnt install.
So I used yotaflasher to download the new firmware and took the recovery.img from the folder
and flashed via fastboot the stock recovery.img.
But the phone always says there is an update and reboots. then the green android is displayed but only for five seconds. then it boots and says again that there is an update and if I want to install it.
And so on...
Do I have another chance to update my 5.0 Firmware.
I donĀ“t want to lose my apps and userDAta.
Can I still flash with yotaflasher and NOT lose all my settings and updates ?
Thanks in advance.
yotaflasher
is what I used. I was rooted, but still with stock recovery.
yotaflasher writes all partitions, and asks for user data. if you answer no all apps and settings are preserved.
maybe there is still the update file in /firmware ? try deleting.
good luck,
Stefan
I'm in the same boat. Rooted, twrp 2.8.5, got the OTA notification. After it downloads, phone shutsdown and boots to twrp and sits there. From twrp, what can I do to help it along?
Thanks
terraformer said:
I'm in the same boat. Rooted, twrp 2.8.5, got the OTA notification. After it downloads, phone shutsdown and boots to twrp and sits there. From twrp, what can I do to help it along?
Thanks
Click to expand...
Click to collapse
The easiest way was to download yotaflasher, let it load the latest firmware and boot your mobile phone into bootloader mode (via quickboot app).
Connect your phone, then let yotaflasher flash the new firmware but say "NO" to overwriting UserData.
Thats it...
After all was setup again (and rooted) I reflashed TWRP and made a backup.
terraformer said:
I'm in the same boat. Rooted, twrp 2.8.5, got the OTA notification. After it downloads, phone shutsdown and boots to twrp and sits there. From twrp, what can I do to help it along?
Thanks
Click to expand...
Click to collapse
You need stock recovery to be flashed for auto-update...
Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. Reflash TWRP and SuperSU if needed
Step 10. Enjoy!
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Skwerl23 said:
Here is how you fix it.
Step 1. download OnePlus3t toolkit (note: don't attach the phone to PC yet)
step 2. reboot your phone into bootloader (if in twrp hit restart -> bootloader) if not in twrp try turning phone on and as you see the oem unlock screen hit volume up and down and choose fastboot (or bootloader)
step 3. open oneplus3t toolkit
step 4. choose option 8 (flash stock recovery)
step 5. hit enter and when it says waiting 4 devices attach your device to pc
step 6. let it finish
step 7. when recovery comes up, hold power button for 10 seconds or hit exit (if you can choose it) and reboot into system
step 8. if it keeps rebooting into a stock recovery and you cant decrypt... then when your phone first boots and goes into oem-unlock error hit volume up and click restart.
step 9. enjoy!
Click to expand...
Click to collapse
Can TWRP be installed afterwards or will it come back when TWRP is installed?
Michalko5896 said:
Did not work for me. Stock recovery, stock nougat, locked bootloader and I still have dm-verity error.
Click to expand...
Click to collapse
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Skwerl23 said:
Try flashing TWRP and back to stock recovery.
If all keeps happening you may need to follow the guide to unbrick the phone.
I'd personally keep flashing different things if data is important. Sorry to hear this happened. Sounds like dm-verity should never have been a thing. So frustrating. Please update us on what you find. You can always erase system and all then reflash image.
Click to expand...
Click to collapse
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
I feel your frustration. There is this forum
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Michalko5896 said:
I have tried everything. DM-verity error every fricking time.. Tbh, I really hate oneplus. They are not releasing factory images, with factory images I could fix every issue in 5 minutes.
Click to expand...
Click to collapse
I used the hard brick fix to go back to 3.5.1? I let the system update to 3.5.4. Go into developer settings and check allow oem unlock. Went into bootloader and oem unlocked. It will erase everything. Downloaded and put the OTA patch(940gb~not full) and supersu 2.79 on the device somewhere and did a local update with the patch through stock recovery. Went into bootloader and flashed TWRP 3.0.2.0(not 3.0.3.0). Do not exit bootloader. In bootloader I fastboot BOOT the 3.0.2.0 TWRP(3.0.3.0 would not boot up and screwed the dm-verity). If it(3.0.2.0) doesn't want to boot then quickly hold the power button in and wait till it starts rebooting and go into recovery menu option). Swipe to allow modifications and flash the supersu 2.79 that was placed on the device somewhere. This worked for me and no dm-verity error with f2fs.
Long process but it worked.
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
PaKii94 said:
does dm-verity error mean anything? I have it also currently but nougat seems to be running fine...
Click to expand...
Click to collapse
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
What causes the dm-verity issue in the first place?
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
saberzaid said:
guys if my device is unlocked will i still get the ota updates?
how about root ? if my device rooted willi still get ota updates?
Click to expand...
Click to collapse
Yes to first. No to second, It will try but will fail.
Sent from my ONEPLUS A3000 using Tapatalk
Mine is unlocked and rooted. The update failed. Then it redownloaded the full 1.4gb. That's how I found the URL. Then it flashed fine but brought recovery to stock and wiped root. Had to use the toolkit to get TWRP and root back.
So yes, even rooted gets the update
noahvt said:
Go to TWRP>Wipe>Advanced Wipe>Select system>Repair or change file system>Change filesystem>EXT4>Flash your ROM
That fixed it for me
Click to expand...
Click to collapse
I did a system restore previously and it set system to ext4. Maybe that's why I didn't have issues.
This dm-verity issue could be showing the instability of f2fs. Hmmm
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
jejemc said:
Hello, just reset original rom under 6.0.1 and the problems and then twrp then flash rom custom
Click to expand...
Click to collapse
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
lanbingxuanyi said:
Hi guy, I followed your instruction, however, it still has the problem.
When I use the stock recovery to flash the beta1 package, it could not be flashed in.
Click to expand...
Click to collapse
Hello, I am going under the beta with the message in red dm-verity for the removed I returned under original rom then I handed twrp then rom custom
card13 said:
https://source.android.com/security/verifiedboot/
In a nutshell, extra security on the boot partition to "ensure chain of trust" one of the possible requirements for Android Pay backend.
********EDIT***********
This method didn't work on the newest beta, and the OP3T ToolKit way has never worked for me on any version of OOS.
Click to expand...
Click to collapse
PaKii94 said:
I see thanks. I guess it doesn't matter to me cause I haven't started using android Pay and since I'm rooted currently
Click to expand...
Click to collapse
I'm running 7.0 stable, unlocked bootloader and dm-verity warning. Android Pay still functions with the workaround.
So this morning I got an update to fix the voLTE bug. I'm unlocked with twrp installed and rooted. Just for the sake of experimenting I tried installing it. Well that didn't work. Just gets stuck in twrp recovery and you have to power the phone off completely to get it to boot. I guess my question (even though it's a little early) is there a way to install the update without reverting back to stock?
EDIT: Link to the zip
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
I don't believe so.
In the past you either had to go back to stock or wait on someone to create a compatible update for rooted devices.
Can you post link to zip?
If you are rooted, you can find the zip in cache folder in recovery.
Can you add what variant and build you are using before the update? Also the build afterwards?
KapilFaujdar said:
Can you post link to zip?
If you are rooted, you can find the zip in cache folder in recovery.
Click to expand...
Click to collapse
I got the update, but all I see on my magisk rooted G5+ in /cache/recovery are log files and the fstab files. Anywhere else to look?
gghose said:
I got the update, but all I see on my magisk rooted G5+ in /cache/recovery are log files and the fstab files. Anywhere else to look?
Click to expand...
Click to collapse
Yeah I can't find anything in that folder either.
I received the update and applied it. I am not rooted.
I have the XT1687 model.
My current build number is NPN25.137-35
My device BL unlocked, TWRP installed and rooted with magisck.
I'm getting the update notification and splash screens several times daily.
Anyone rooted try installing the update with Flashfire app?
bvsbutthd101 said:
So this morning I got an update to fix the voLTE bug. I'm unlocked with twrp installed and rooted. Just for the sake of experimenting I tried installing it. Well that didn't work. Just gets stuck in twrp recovery and you have to power the phone off completely to get it to boot. I guess my question (even though it's a little early) is there a way to install the update without reverting back to stock?
Click to expand...
Click to collapse
If you have systemless supersu, you should just be able to apply the update after reverting to stock recovery.
So I found where the zip downloads. I wonder what flashing it in twrp would do?
EDIT: Here's the link to the zip and I've put it in the OP.
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
glight0 said:
My device BL unlocked, TWRP installed and rooted with magisck.
I'm getting the update notification and splash screens several times daily.
Anyone rooted try installing the update with Flashfire app?
Click to expand...
Click to collapse
OK, so I tried flashing recovery.img from stock firmware build 33. But the OTA update will not install, instead I get an error after downloading and rebooting (red triangle at recovery mode).
So I tried fully reverting to stock firmware but I decided to skip over erasing userdata. Afterward the OTA downloaded and installed successfully. Keeping userdata does not seem to have caused an issue.
My problem now though is how to get root back without having to wipe userdata after re-flashing TWRP.
Or is this not possible and if I want to root I must first wipe userdata so that TWRP can read internal memory?
bvsbutthd101 said:
So I found where the zip downloads. I wonder what flashing it in twrp would do?
EDIT: Here's the link to the zip and I've put it in the OP.
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
Click to expand...
Click to collapse
Just tried flashing it with TWRP and no luck:
Verifying current system....
E3002: Package expects build thumbprint of 7.0/NPN25.137-35/37:user/release-keys or 7.0/NPN25.137-33/35:user/release-keys; this device has .
Updated process ended with ERROR: 7
which doesn't make much sense since I rooted the stock ROM (Build number reads NPN25.137-33).
If your using a custom recovery flash the stock recovery, then go to the stock recovery and using your computer flash using adb sideboard command. I assume you already know how to do this. Hope that helps.
gghose said:
Just tried flashing it with TWRP and no luck:
Verifying current system....
E3002: Package expects build thumbprint of 7.0/NPN25.137-35/37:user/release-keys or 7.0/NPN25.137-33/35:user/release-keys; this device has .
Updated process ended with ERROR: 7
which doesn't make much sense since I rooted the stock ROM (Build number reads NPN25.137-33).
Click to expand...
Click to collapse
I'm stuck in the same boat... no idea how to flash the stock recovery and sideboard, what that even means, or if that would break root. I just followed the step-by-step "how to root" video when I first got the phone
There's a workaround to disable the "advanced LTE" or whatever it was called, so I did that. But in the meantime until a more "user friendly" means of updating is available, is there a way I can get rid of this nag screen? Way back on an earlier device (Samsung Charge?) I remember manually editing a "build.prop" file or something to match the latest version so I wouldn't keep getting the software update nag. Is there something that will do the same here, or is there a system app I can freeze in TiB?
My best guess is freezing "Moto Actions 03.022.1.4-N" because it's showing "(updated)" on the side.
rellim113 said:
I'm stuck in the same boat... no idea how to flash the stock recovery and sideboard, what that even means, or if that would break root. I just followed the step-by-step "how to root" video when I first got the phone .
Click to expand...
Click to collapse
What he means is you need to download the stock rom, unzip it, then boot phone to bootloader mode and connect to PC. Then flash the recovery.IMG from the stock rom folder with command prompt:
Fastboot flash recovery recovery.img
Then you can on the phone tell it to boot to recovery mode. This will be a screen with Android on his back and the words NO Command on the bottom. Then plug to PC and use adb command to sideload the update zip like this:
adb sideload [nameofupdatefile].Zip
glight0 said:
What he means is you need to download the stock rom, unzip it, then boot phone to bootloader mode and connect to PC. Then flash the recovery.IMG from the stock rom folder with command prompt:
Fastboot flash recovery recovery.img
Then you can on the phone tell it to boot to recovery mode. This will be a screen with Android on his back and the words NO Command on the bottom. Then plug to PC and use adb command to sideload the update zip like this:
adb sideload [nameofupdatefile].Zip
Click to expand...
Click to collapse
Strange, reflashed the stock recovery and adb can't see it (adb devices returns nothing). And when trying to install it via the normal OTA way, the stock recovery tries to install but ends with an error.
That's what happened to me when I tried reverting to stock recovery and then trying to install update from phone Settings app.
I ended up having to revert to stock rom to get ota to apply with settings app. But now I am trying to root again but after installing TWRP data is encrypted again. So looks like I will have to wipe data before re-rooting.
I received the May OTA update earlier today, and since I'm rooted I decided to flash it with Flashfire. As soon as I opened Flashfire I was prompted to click a button to install the OTA. However, I then recieved a warning message "warning: it has been detected that you may be trying to flash a block-level ota, but your /system, /vendor, or /oem partition has been modified. This will likely cause the flash to fail!"
However, I clicked "ignore" and continued anyways, since I interpreted "flash to fail" to mean "will either not update (abort and stay the same) or update correctly." However, now my phone is stuck on the booting screen. I should at least still have TWRP installed, since I believe the "preserve recovery" box was automatically checked.
What can I do to fix the issue? I'm thinking if I download the full OTA and flash in recovery, maybe that will work?
If you can still boot into the bootloader (not recovery), do that and run through the manual install of the factory image (via the fastboot command - see the install instructions in the general forum). Again, do this manually (which requires downloading the factory image, extracting the files out, and manually flashing each file (bootloader, boot, etc.)) as that's really the only way you're going to get back to normal. You will have to re-root, etc., but that isn't that much work and saves the pain of going through what you just went through.
jeffrey123987 said:
I received the May OTA update earlier today, and since I'm rooted I decided to flash it with Flashfire. As soon as I opened Flashfire I was prompted to click a button to install the OTA. However, I then recieved a warning message "warning: it has been detected that you may be trying to flash a block-level ota, but your /system, /vendor, or /oem partition has been modified. This will likely cause the flash to fail!"
However, I clicked "ignore" and continued anyways, since I interpreted "flash to fail" to mean "will either not update (abort and stay the same) or update correctly." However, now my phone is stuck on the booting screen. I should at least still have TWRP installed, since I believe the "preserve recovery" box was automatically checked.
What can I do to fix the issue? I'm thinking if I download the full OTA and flash in recovery, maybe that will work?
Click to expand...
Click to collapse
Fixed
johnhazelwood said:
If you can still boot into the bootloader (not recovery), do that and run through the manual install of the factory image (via the fastboot command - see the install instructions in the general forum). Again, do this manually (which requires downloading the factory image, extracting the files out, and manually flashing each file (bootloader, boot, etc.)) as that's really the only way you're going to get back to normal. You will have to re-root, etc., but that isn't that much work and saves the pain of going through what you just went through.
Click to expand...
Click to collapse
Thanks, I actually just flashed the full factory OTA and now everything is working fine once again. I did lose root access though, so I have to reflash superSU as well. Thank you for trying to help though! If flashing the full OTA in TWRP had also failed, my Plan B was to just flash the factory image as you suggested.
jeffrey123987 said:
Thanks, I actually just flashed the full factory OTA and now everything is working fine once again. I did lose root access though, so I have to reflash superSU as well. Thank you for trying to help though! If flashing the full OTA in TWRP had also failed, my Plan B was to just flash the factory image as you suggested.
Click to expand...
Click to collapse
Or next time just use the full image (not OTA) with FF (with select flash firmware package). You won't have any issues plus will retain root/recovery. You'll be back up and running in one minute.
Glad you got it back up and running. Also, as mentioned, you could flash the full package via flashfire, just don't flash the bootloader using it.