I started looking at this issue in another thread HERE. I started thinking about this and knew there were others with more info that might help.
Everyone says you can't downgrade the Knox Boot Loader once it's been loaded. I want to try and understand why/how we can modify the system to overcome that.
Here's what I know and I've done:
After MF9, the Knox Bootloader was included in the update. Unknownforce has a great thread that has the modems with or without the boot loader. What I did first was unzip the tar files for MF9 (with and without the boot loader.)
Both files have:
modem.bin
NON-HLOS.bin
rpm.mbn
tz.mbn
When I compare the files in both, they seem identical. Same creation date, same size, ect. They may or may not be the same? But the boot loader version has some extra files.
Boot Loader Version has these files:
aboot.mbn
sbl2.mbn
sbl3.mbn
Process of elimination indicates that these have the Knox Boot loader encoded in some way. The sbl files are placed in the root directory /firmware-mdm/image/ . Try as I might, I can't find aboot.mbn. I did a nandroid backup of my system, then I deleted sbl2.mbn and sbl3.mbn using ES File Explorer. When I rebooted the phone, the files were back in the directory.
Another thing I did was a nand erase and re-partition of my phone using Odin. (Don't attempt this unless you have the pit file! You can easily brick your phone. On second thought, don't attempt this at all. I just got lucky I was able to bring it back up. As it was my Data partition was corrupted because of this but I was able to fix it.) I think I did everything right in re-installing. I put a knox free boot loader and recover with Odin first. Then booted into recovery and installed a Knox free rom. Knox boot loader was still there. I was hoping re-partitioning would wipe everything out but it was a no go. Anyone else have experience in this?
Here's my questions:
If we delete those three files and can keep them from reloading, will Knox Boot Loader be disabled?
What partition is aboot.mbn located in or stored in the system? Can it be assessed with adb commands and renamed or deleted?
Where are the sbl files being reloaded from?
Does anyone know if the similar files are the exact same files? If not how do we replace them with non-boot loader versions if the system regenerates them at each boot?
Is there a way to do a nand erase and re-partitioning in order to get rid of the bootloader?
Thoughts?
My hard brick says aboot is in partition 6
Aboot is in partition 6. You can find this out by using a # heimdall print-pit command and
examining the output.
If you dd a different version of aboot.mbn atop that partition it will hard-brick the device,
meaning the screen won't come on and all it wants is a primitive USB serial connect
to some software I'm sure only Samsung has.
How do I know? I have three Dev S4s (VZW) and none of them will let me flash TWRP.
In order to try getting a "less locked aboot" I dd'd an older version (VRUAMDK) onto
that partition (mmcblk0p6). The device is now good to send back to Samsung or to
keep papers from flying -- unless someone knows the secret serial port protocol.
Sigh.
Ehud
perezmarka said:
I started looking at this issue in another thread HERE. I started thinking about this and knew there were others with more info that might help.
Everyone says you can't downgrade the Knox Boot Loader once it's been loaded. I want to try and understand why/how we can modify the system to overcome that.
Here's what I know and I've done:
After MF9, the Knox Bootloader was included in the update. Unknownforce has a great thread that has the modems with or without the boot loader. What I did first was unzip the tar files for MF9 (with and without the boot loader.)
Both files have:
modem.bin
NON-HLOS.bin
rpm.mbn
tz.mbn
When I compare the files in both, they seem identical. Same creation date, same size, ect. They may or may not be the same? But the boot loader version has some extra files.
Boot Loader Version has these files:
aboot.mbn
sbl2.mbn
sbl3.mbn
Process of elimination indicates that these have the Knox Boot loader encoded in some way. The sbl files are placed in the root directory /firmware-mdm/image/ . Try as I might, I can't find aboot.mbn. I did a nandroid backup of my system, then I deleted sbl2.mbn and sbl3.mbn using ES File Explorer. When I rebooted the phone, the files were back in the directory.
Another thing I did was a nand erase and re-partition of my phone using Odin. (Don't attempt this unless you have the pit file! You can easily brick your phone. On second thought, don't attempt this at all. I just got lucky I was able to bring it back up. As it was my Data partition was corrupted because of this but I was able to fix it.) I think I did everything right in re-installing. I put a knox free boot loader and recover with Odin first. Then booted into recovery and installed a Knox free rom. Knox boot loader was still there. I was hoping re-partitioning would wipe everything out but it was a no go. Anyone else have experience in this?
Here's my questions:
If we delete those three files and can keep them from reloading, will Knox Boot Loader be disabled?
What partition is aboot.mbn located in or stored in the system? Can it be assessed with adb commands and renamed or deleted?
Where are the sbl files being reloaded from?
Does anyone know if the similar files are the exact same files? If not how do we replace them with non-boot loader versions if the system regenerates them at each boot?
Is there a way to do a nand erase and re-partitioning in order to get rid of the bootloader?
Thoughts?
Click to expand...
Click to collapse
perezmarka said:
I started looking at this issue in another thread HERE. I started thinking about this and knew there were others with more info that might help.
Everyone says you can't downgrade the Knox Boot Loader once it's been loaded. I want to try and understand why/how we can modify the system to overcome that.
Here's what I know and I've done:
After MF9, the Knox Bootloader was included in the update. Unknownforce has a great thread that has the modems with or without the boot loader. What I did first was unzip the tar files for MF9 (with and without the boot loader.)
Both files have:
modem.bin
NON-HLOS.bin
rpm.mbn
tz.mbn
When I compare the files in both, they seem identical. Same creation date, same size, ect. They may or may not be the same? But the boot loader version has some extra files.
Boot Loader Version has these files:
aboot.mbn
sbl2.mbn
sbl3.mbn
Process of elimination indicates that these have the Knox Boot loader encoded in some way. The sbl files are placed in the root directory /firmware-mdm/image/ . Try as I might, I can't find aboot.mbn. I did a nandroid backup of my system, then I deleted sbl2.mbn and sbl3.mbn using ES File Explorer. When I rebooted the phone, the files were back in the directory.
Another thing I did was a nand erase and re-partition of my phone using Odin. (Don't attempt this unless you have the pit file! You can easily brick your phone. On second thought, don't attempt this at all. I just got lucky I was able to bring it back up. As it was my Data partition was corrupted because of this but I was able to fix it.) I think I did everything right in re-installing. I put a knox free boot loader and recover with Odin first. Then booted into recovery and installed a Knox free rom. Knox boot loader was still there. I was hoping re-partitioning would wipe everything out but it was a no go. Anyone else have experience in this?
Here's my questions:
If we delete those three files and can keep them from reloading, will Knox Boot Loader be disabled?
What partition is aboot.mbn located in or stored in the system? Can it be assessed with adb commands and renamed or deleted?
Where are the sbl files being reloaded from?
Does anyone know if the similar files are the exact same files? If not how do we replace them with non-boot loader versions if the system regenerates them at each boot?
Is there a way to do a nand erase and re-partitioning in order to get rid of the bootloader?
Thoughts?
Click to expand...
Click to collapse
you can find aboot.mbn as aboot on /dev/blocks/...
gavron said:
Aboot is in partition 6. You can find this out by using a # heimdall print-pit command and
examining the output.
If you dd a different version of aboot.mbn atop that partition it will hard-brick the device,
meaning the screen won't come on and all it wants is a primitive USB serial connect
to some software I'm sure only Samsung has.
How do I know? I have three Dev S4s (VZW) and none of them will let me flash TWRP.
In order to try getting a "less locked aboot" I dd'd an older version (VRUAMDK) onto
that partition (mmcblk0p6). The device is now good to send back to Samsung or to
keep papers from flying -- unless someone knows the secret serial port protocol.
Sigh.
Ehud
Click to expand...
Click to collapse
I have also tried overwriting a pre-Knox aboot using DD and got the same result. I found a piece of software called QPST which is a Qualcomm developer tool, that can be used to reflash the bootloader and unbrick the phone. The only problem is you need a data file for your specific model, although this possibly can be extracted from a firmware (probably in boot.img). I haven't gotten to look inside those images yet, but that tool could possibly be able to flash an older bootloader...
Related
FIxed with this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
My 64gb OnePlus One does not boot anymore.
I wiped system, data, cache, and dalvik and then flashed the 9/20 cm nightly, gapps, and supersu. The device rebooted and I saw the CM loading circle. However, next time I looked at the device, it was back at the Oneplus boot screen. After this, I have never been able to get it past this screen.
I have tried flashing the stock image using this guide (steps 1-3), as well as downloading the fastboot image from cnygn.com and flashing each img from fastboot using these commands:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Additionally I have tried flashing CM11 from TWRP, which still results in the same problem. I am able to access and use fastboot and twrp just fine.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
EDIT: I managed to install ColorOS with this guide, and it boots fine. However, I need CM with Google Play so after trying to get cm11s 33r with this guide, I'm back at square one with the phone not getting past the boot screen. Any ideas?
Hi so i guess you don't have a backup in the device,sometimes the easiest way to fix things is the right way just download this tool the one for your device 16/32gb the second version(v.2) put your phone in fastboot mode and hit cm update in the tool.
---------- Post added at 06:29 AM ---------- Previous post was at 06:26 AM ----------
http://www.youtube.com/watch?app=desktop&persist_app=1&v=5O2e_R_TbVg
android.345 said:
My 64gb OnePlus One does not boot anymore.
Click to expand...
Click to collapse
Your phone goes in fastboot mode, so you shouldn't even think it could be lost forever.
The guide you're following is the right one, so just make sure you are following it correctly. I assume you unlocked your bootloader before starting the first flashing that soft-bricked your phone, so you should be good to go.
You should just need to do everything that's in the guide you linked, except the 4th step (you don't need to lock the bootloader). Flash the factory images and just reboot (don't flash/wipe/whatever anything else), it should be fine. Make sure you're flashing the right ones though, for example, since you have the 64GB version, you have to flash the userdata image for the 64GB OPO.
I don't think you should look for "1-click" toolkits, they can be more harmful than good since you don't know what you're actually doing.
bradipovsky said:
Your phone goes in fastboot mode, so you shouldn't even think it could be lost forever.
The guide you're following is the right one, so just make sure you are following it correctly. I assume you unlocked your bootloader before starting the first flashing that soft-bricked your phone, so you should be good to go.
Click to expand...
Click to collapse
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
android.345 said:
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
Click to expand...
Click to collapse
Sorry but I'm no expert and I'm already out of ideas... The only thing that might be wrong in what you're doing is that I remember the file "userdata.img" being for the 16GB version, the one for the 64GB was called "userdata_64.img" or something like that. I don't know if this can be the problem in your case though.
I have no experience in using fastboot on Windows, so I don't know if there can be a driver problem that doesn't pop up while you try to flash.
If I were you the next things I would try are:
- See if TWRP lets you mount OTG storage, that way you can just flash a new ROM
- Double check your adb/fastboot installation (do any commands work? Does "fastboot reboot" work?)
Anyway please keep in mind I'm just guessing, you may want to wait for someone with some more experience to drop by...
bradipovsky said:
Sorry but I'm no expert and I'm already out of ideas... The only thing that might be wrong in what you're doing is that I remember the file "userdata.img" being for the 16GB version, the one for the 64GB was called "userdata_64.img" or something like that. I don't know if this can be the problem in your case though.
I have no experience in using fastboot on Windows, so I don't know if there can be a driver problem that doesn't pop up while you try to flash.
If I were you the next things I would try are:
- See if TWRP lets you mount OTG storage, that way you can just flash a new ROM
- Double check your adb/fastboot installation (do any commands work? Does "fastboot reboot" work?)
Anyway please keep in mind I'm just guessing, you may want to wait for someone with some more experience to drop by...
Click to expand...
Click to collapse
Do take a look at the update I have posted regarding ColorOS. Flashing a new rom from TWRP does not help. All fastboot commands work.
Also, I have been flashing userdata_64g.img
android.345 said:
I thought the same and wasn't scared as first, however, the commands complete with no error and the device still does not boot.
One thing to note is that when I load up twrp and try to sideload a rom I see this message in the terminal:
E:Mount: Unable to find partition for path '/sdcard'
Click to expand...
Click to collapse
Same problem for me too. Device worked for a week with SOD-s that 2 days ago just rebooted and stay in the loop of logo 1+.. ??
At the root file system on my Android phone, there's a file called default.prop. Right now that's a non-standard file because of CF-Auto-Root, but I want that file to be the stock version (1).
After what I have understood, /default.prop file is overwritten on every boot from a default.prop file within the boot partition.
My phone is rooted with CF-Auto-Root, but I've replaced the boot and bootloader partitions with factory image versions:
$ fastboot flash bootloader bootloader.img
$ fastboot flash boot boot.img
But still I get the non-stock default.prop file. What am I doing wrong?
(1) This is because I'm trying to upgrade to Android 5.1, and right now I'm getting an error because "this device has google/omni_hammerhead/hammerhead:4.4.4/KTU84P/eng.dees_troy.20150214.172938:eng/test-keys".
neu242 said:
(1) This is because I'm trying to upgrade to Android 5.1, and right now I'm getting an error because "this device has google/omni_hammerhead/hammerhead:4.4.4/KTU84P/eng.dees_troy.20150214.172938:eng/test-keys".
Click to expand...
Click to collapse
Don't bother messing with reverting everything just to update, it is extremely unlikely to work since as of Lollipop Google has changed the OTA method to check the sum of the entire partition rather than only what it cares about.
Download the 5.1 factory images, and flash system.img, boot.img, cache.img, radio.img and bootloader.img (don't flash userdata.img unless you want to wipe all your data), then boot into a custom recovery and flash the latest SuperSU (http://download.chainfire.eu/supersu).
Elluel said:
Download the 5.1 factory images, and flash system.img, boot.img, cache.img, radio.img and bootloader.img (don't flash userdata.img unless you want to wipe all your data), then boot into a custom recovery and flash the latest SuperSU (http://download.chainfire.eu/supersu).
Click to expand...
Click to collapse
Perfect, just what the doctor ordered. Thanks Elluel!
Hello.
I have a somewhat unique situation.
I have more than one unit of identical, generic (not a standard brand) tablets. They are all rooted, so I do have root access. However, they don't have a custom recovery - there isn't one readily available (I have looked far and wide).
One of the tablets has the OS (with all the Google -and other- apps) I want to replicate on to the others (this is admittedly an oldish Kitkat OS, but while I have one of them running Lollipop successfully, I am unable to get Gapps to run with Lollipop, hence the reversion to Kitkat). I only want to replicate the OS, there are no other complications such as IMEI, etc that I need to replicate.
What do I need to accomplish this? I am comfortable flashing, rooting, etc, but I am by no stretch of imagination an Android developer, so creating a custom recovery is beyond me.
What I have tried so far:
0. The tablets are already rooted. Used Kingo to ensure root access to apps if/when necessary.
1. ADB/Fastboot flashes. This is by far most successful, although I don't have a system.img/recovery.img of the 'good' tablet. The others (including Jellybean, Kitkat and Lollipop) that I do have don't have Gapps on the OS and I am unable to install them through ADB (or native tablet-based installation) with the apks. (Google play services error).
2. dd-ing the images from the 'good' tablet to the bad ones (soft bricked, had to reflash with working images in 1. to get it back up again). (dd if=<> of=<>)
3. Taking Online-Nandroid backups, but unable to flash this image through the Nandroid Manager (and can't do it through recovery since lacking a custom recovery). I can't flash this through ADB since it isn't an system.img/recovery.img type backup.
Given this background, what I need to do is create boot.img, system.img, recovery.img, cache.img, persist.img, userdata.img from the 'good' tablet and flash these to the 'bad' ones. I have searched and searched - both on XDA and over Google at large. But I haven't found an answer to this specific issue of replicating a tablet entirely through ADB. The ones I have found (dd-method) didn't work.
Here's the Flashing batch file I've been using, that I know brings up one of these tablets. I assume I can continue to use the 'modem and bootloaders' that I currently have, although I would prefer to extract them from the 'good' tablet just to be sure.
Any help greatly appreciated.
Code:
adb root
adb wait-for-device reboot bootloader
sleep 5
:: erase all the partitions
fastboot erase modem
fastboot erase boot
fastboot erase system
fastboot -w
:: flash the modem and bootloaders
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
echo Flashed the bootloaders!
:: reboot the target
fastboot reboot
sleep 1
:: flash the linux images
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash persist persist.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
echo Done flashing the images, rebooting the target!
fastboot reboot
Hello, in desperate need of help, I will sum up my problem, and after I'll give a detailed outline of everything I've done.
The main issue is: Custom binary blocked by FRP lock
I'm flashing stock firmware that I downloaded from sammobile with heimdall, using this command:
Code:
~/Heimdall/build/bin/heimdall flash --BOOTLOADER sboot.bin --CM cm.bin --RECOVERY recovery.img --RADIO modem.bin --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img
After this finishes, the phone reboots, Android logo appears and it says "Installing system updates", bar fills up very quickly, and then it says "erasing".
After that, it reboots again and The FRP message appears again.
----
That is the current problem, how I got here is the following:
1. In order to install LineageOS I disabled FRP lock by removing the device from "manage devices", and removing the google account from the phone itself.
2. Installed LineageOS SUCCESSFULLY, I was very happy. I turned off my phone at some point.
3. When I turned it back on, the boot screen displayed the dreaded FRP message. I concluded I had to install stock firmware in order to disable FRP again, which apparently enabled itself again.
4. Since I'm on linux, I'm using heimdall, and initially I could not flash the firmware, so I have to use a patch (can't paste the URL because I'm new, but it shows up in gitlab if you search for "ERROR: Failed to receive file part response!")
5. I downloaded this firmware: "This firmware has version number PDA A510MUBS7CSD9 and CSC A510MPSN7CSD4." and extracted it.
6. Used the command explained above:
Code:
~/Heimdall/build/bin/heimdall flash --BOOTLOADER sboot.bin --CM cm.bin --RECOVERY recovery.img --RADIO modem.bin --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img
7. The output is littered by "ERROR: Failed to receive file part response!" but it keeps going, session ends, and phone reboots.
I've been googling for hours now. The last thing I tried was the steps from another post here, saying to first flash all the files except hidden.img, and then flash that separately. That did not work either.
Have I bricked it? What can I do?
I just made a windows VM to use Odin3, followed the steps and I got a FAIL!
Coming from linux, I'm used to error messages and logs but this doesn't seem to have anything of the sort.
Help please!
Not that anyone's reading, but I managed to flash stock firmware with odin3 by flashing hidden.img separately, but now it is stuck on the samsung logo forever.
Flashes unpatched int.boot.img file, then got attached message cannot start device. Can anybody help? Thanks!
Did you flash it to the init_boot partition or the boot partition?
Annie the Eagle said:
Did you flash it to the init_boot partition or the boot partition?
Click to expand...
Click to collapse
Thank you for your reply. I flashed by below command: flash boot unpachedname
Did i do things wrong? Sorry im realy a newbie
Yeah you can't flash init_boot.img to boot partition.
init_boot.img must go to the "init_boot" partition.
Thankfully, there is extracted IMGs here: https://forum.xda-developers.com/t/...xtracted-images-how-to.4505061/#post-87566815
Click the SourceForge link to the FASTBOOT IMAGES.
Then make sure you repair your boot partition by flashing over the boot.img to boot partition and the init_boot.img to init_boot partition.
Usual disclaimer: No warranty, I haven't tested any of these images but give it a try.
Annie the Eagle said:
Yeah you can't flash init_boot.img to boot partition.
init_boot.img must go to the "init_boot" partition.
Thankfully, there is extracted IMGs here: https://forum.xda-developers.com/t/...xtracted-images-how-to.4505061/#post-87566815
Click the SourceForge link to the FASTBOOT IMAGES.
Then make sure you repair your boot partition by flashing over the boot.img to boot partition and the init_boot.img to init_boot partition.
Usual disclaimer: No warranty, I haven't tested any of these images but give it a try.
Click to expand...
Click to collapse
Really apprexiate your reply let me try rhen cime back witj my result
I dlowlaoded and flashed. Now got a new ereor as attached. Any way to conletely reflash all things ?
Thanks!
Did you flash the both init_boot.img to init_boot and boot.img to boot? Make sure you do both.
flashboot flash boot boot.img
flashboot flash init_boot init_boot.img
bosox284 said:
Did you flash the both init_boot.img to init_boot and boot.img to boot? Make sure you do both.
flashboot flash boot boot.img
flashboot flash init_boot init_boot.img
Click to expand...
Click to collapse
Really appreciate ur support. Looks im in big trouble: did one again then it is keeping show this screen
Now rhe device is keeping rebooting l. Then this screen showed
Cannot even turn on. Stuck on the screen now ...
No offense, but if you are a "newbie" as you say, then why in the world would you want to risk a $900.00+ device that is so new to the modding world? What possible benefit could there really be even if you were successful? Remember, it IS possible to completely brick your phone and no warranty in the world will help. SMH
Are you using the stock images? I recommend doing a --slot=all to be safe. Reboot bootloader manually (Vol Down + Power), then run the same commands as before with --slot=all.
flashboot flash boot --slot=all boot.img
flashboot flash init_boot --slot=all init_boot.img
If that still fails, wait another 40 minutes or so until Google hopefully drops the factory images and just flash those. I don't think you're hard bricked just yet.
bosox284 said:
Are you using the stock images? I recommend doing a --slot=all to be safe. Reboot bootloader manually (Vol Down + Power), then run the same commands as before with --slot=all.
flashboot flash boot --slot=all boot.img
flashboot flash init_boot --slot=all init_boot.img
If that still fails, wait another 40 minutes or so until Google hopefully drops the factory images and just flash those. I don't think you're hard bricked just yet.
Click to expand...
Click to collapse
Thank you for your patience. I will try this tomorrow it is really late in japan. Appreciate your kind help. Wish you a nice day.
Keep you informed.
bosox284 said:
Are you using the stock images? I recommend doing a --slot=all to be safe. Reboot bootloader manually (Vol Down + Power), then run the same commands as before with --slot=all.
flashboot flash boot --slot=all boot.img
flashboot flash init_boot --slot=all init_boot.img
If that still fails, wait another 40 minutes or so until Google hopefully drops the factory images and just flash those. I don't think you're hard bricked just yet.
Click to expand...
Click to collapse
Tried only boot.img i can do. Ini_boot showed no sucj file
Flashed as you instructed but still saying corrupt. Btw i downloaded this file,is it correct ? Thanks!
That just means you don't have an init_boot file with that exact name in the folder. At this point I'd suggest waiting until Google drops the factory images so you can start fresh. Without knowing your version number you're basically going in blind flashing files that may or may not be relevant to your build.
When you run flashboot flash init_boot init_boot.img, the 'init_boot.img' needs to be the exact file name in your folder. So if your patched file is magisk_init_patched-25205_EfWOu.img, you're going to run fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
In the future, I suggest downloading the stock boot/init_boot files for your build number so that if something goes haywire then you can recover. I also would suggest holding off until factory images are available, especially if you're not sure what you're doing. That'll also give you a way to recover in a worst case scenario where nothing seems to work.
bosox284 said:
That just means you don't have an init_boot file with that exact name in the folder. At this point I'd suggest waiting until Google drops the factory images so you can start fresh. Without knowing your version number you're basically going in blind flashing files that may or may not be relevant to your build.
When you run flashboot flash init_boot init_boot.img, the 'init_boot.img' needs to be the exact file name in your folder. So if your patched file is magisk_init_patched-25205_EfWOu.img, you're going to run fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
In the future, I suggest downloading the stock boot/init_boot files for your build number so that if something goes haywire then you can recover. I also would suggest holding off until factory images are available, especially if you're not sure what you're doing. That'll also give you a way to recover in a worst case scenario where nothing seems to work.
Click to expand...
Click to collapse
Thank you very much. I will wait for the dactory images. Appreciate your support massively.
The factory images are now live: https://developers.google.com/android/images#cheetah
Download the file, extract the zip, and run flash-all at a command prompt. It should give you a fresh start.
bosox284 said:
The factory images are now live: https://developers.google.com/android/images#cheetah
Download the file, extract the zip, and run flash-all at a command prompt. It should give you a fresh start.
Click to expand...
Click to collapse
thank you. I flashed the fiemware and now it is back!
I was having the same issues; "fastboot flash init_boot_a <patched magisk.img>" worked for me.