Related
Anyone know how to re-lock the bootloader Moto X.
NOTE: After you unlock it I am not able to download additional game data via Wifi.
Thanks!!!
Kuyuri said:
Anyone know how to re-lock the bootloader Moto X.
NOTE: After you unlock it I am not able to download additional game data via Wifi.
Thanks!!!
Click to expand...
Click to collapse
Not answering your question but unlocking your bootloader is not what is preventing you from downloading game data via WiFi, something else is the culprit and you should look for that.
Unlocking the bootloader just unlocks the bootloader, and in no way affects the Android system OS.
1. Write a normal title for your thread, don't beg around like this. Explain what the EXACT question is [e.g.: How do I re-lock the bootloader on XT105x?].
2. Search for your problems before asking.
3. I don't even want to help you, if you have this attitude.
Kuyuri said:
Anyone know how to re-lock the bootloader Moto X.
NOTE: After you unlock it I am not able to download additional game data via Wifi.
Thanks!!!
Click to expand...
Click to collapse
Boot into fastboot.
In a console session navigate to where the fastboot.exe binary is.
execute 'fastboot oem lock'
But this isn't going to solve your problem.
Coop9 said:
Boot into fastboot.
In a console session navigate to where the fastboot.exe binary is.
execute 'fastboot oem lock'
But this isn't going to solve your problem.
Click to expand...
Click to collapse
Actually you have to do fastboot OEM begin lock
Then flash the factory image followed by
Fastboot OEM lock
So this morning I was lazy and tried rooting with the kingroot app, because I didn't want to factory reset. It went okay and I had root but I wanted to use SuperSU as my root manager. Well the binary wouldn't update so I figured i'd unroot from the kingroot app and remove kingroot from my phone, and root the proper way later. I pressed the unroot button and my phone rebooted, but now it's stuck in a bootloop.
I don't have an unlocked bootloader or a custom recovery, and I never checked the enable oem unlock in developer options so flashing stock isn't an option.
I tried sideloading the OTA for the build I was on, but I guess kingroot didn't actually unroot me, because it told me I needed to reflash.
I tried factory reset and wiping the cache in the stock recovery, and tried 'fastboot format userdata' and 'fastboot format cache' but that didn't work either.
The only thing I could find that might help is this post http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
but since I don't think you can run adb commands in stock recovery or bootloader this won't work.
So is there any way to fix this or am I boned?
As far as I know the only fix is the one in that link but it does require custom recovery. I'm assuming the fastboot boot command doesn't work when locked but I've never tried, if it does then you could temp boot into twrp. Worth a shot I guess.
Hindsight's 20/20 but NEVER touch anything other than your data or cache partition with a locked bootloader. Google's security jump with lollipop has caused nothing but havoc for us.
ChaosDr0id said:
So this morning I was lazy and tried rooting with the kingroot app, because I didn't want to factory reset. It went okay and I had root but I wanted to use SuperSU as my root manager. Well the binary wouldn't update so I figured i'd unroot from the kingroot app and remove kingroot from my phone, and root the proper way later. I pressed the unroot button and my phone rebooted, but now it's stuck in a bootloop.
I don't have an unlocked bootloader or a custom recovery, and I never checked the enable oem unlock in developer options so flashing stock isn't an option.
I tried sideloading the OTA for the build I was on, but I guess kingroot didn't actually unroot me, because it told me I needed to reflash.
I tried factory reset and wiping the cache in the stock recovery, and tried 'fastboot format userdata' and 'fastboot format cache' but that didn't work either.
The only thing I could find that might help is this post http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
but since I don't think you can run adb commands in stock recovery or bootloader this won't work.
So is there any way to fix this or am I boned?
Click to expand...
Click to collapse
If you already installed the drivers and know how to run fastboot commands skip to step 4. Otherwise, start at the beginning
1.) Install the Wugfresh Toolkit from here: http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 so that the drivers you need get installed along with fastboot and adb commands.
2.) Open Nexus Root Toolkit after it has finished installing. Under advanced utilities click "Launch" then choose launch command prompt for manual mode.
3.) Put your device in bootloader mode (pwr+vol down) and connect it to the computer. Type: "adb devices" into the command prompt and it should list a device serial number. If it does, go to step 4. If it doesn't, unplug the phone and plug it back in and re-run command.
4.) Then run the command "fastboot oem device-info" and tell us what the output is.
Hopefully when you rooted it, it unlocked your bootloader automatically. If you successfully rooted and rebooted it should technically be unlocked. We won't know until you run fastboot oem device-info
or, you can grab the factory image of whatever version of android that you were on, "unzip" it, grab the system.img, and flash it via fastboot. its the same thing as if was a "custom recovery", youre just reflashing the rom, and wont lose your data
first thing id do is flash a custom recovery and unlock my bootloader, and make a backup in recovery.
AlkaliV2 said:
If you already installed the drivers and know how to run fastboot commands skip to step 4. Otherwise, start at the beginning
1.) Install the Wugfresh Toolkit from here: http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 so that the drivers you need get installed along with fastboot and adb commands.
2.) Open Nexus Root Toolkit after it has finished installing. Under advanced utilities click "Launch" then choose launch command prompt for manual mode.
3.) Put your device in bootloader mode (pwr+vol down) and connect it to the computer. Type: "adb devices" into the command prompt and it should list a device serial number. If it does, go to step 4. If it doesn't, unplug the phone and plug it back in and re-run command.
4.) Then run the command "fastboot oem device-info" and tell us what the output is.
Hopefully when you rooted it, it unlocked your bootloader automatically. If you successfully rooted and rebooted it should technically be unlocked. We won't know until you run fastboot oem device-info
Click to expand...
Click to collapse
Hi, thanks for the reply.
It says
'device info' is not a supported oem command. See fastboot oem help.
FAILED <remote failure>
However I'm fairly certain the bootloader is still locked as I was unable to flash TWRP, or a stock image of android, as it tells me to unlock before doing those things.
AFAIK when you have this problem together with a stock recovery and a locked bootloader means bricked. >repair
Your bootloader is lock and you can't boot android to enable OEM unlock to unlock it. You have ruined your phone and there is no known fix.
RMA time for you.
Literally no solution unless you can invent one on your own.
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
Click to expand...
Click to collapse
yes
CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc?
Click to expand...
Click to collapse
Absolutely. Otherwise anybody with a notebook could swipe your phone, download everything you've got on it, then return it without you knowing, and that would mean more nekkid selfies on reddit.
CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
Click to expand...
Click to collapse
The entire concept of a locked bootloader is that you can't flash images through it.
Alright, I somewhat hate Android 6.0, and that's because of my hard time rooting my Nexus 6, which is, at this point, becoming immensely irritating. If I'm allowed to do so here, since this is a Q&A board, I need to ask how the hell to root this thing, because of Android's new thing where I have to install a custom kernal to get root.
All I really know, now, ids that I need to unlock the bootloader of the phone, which I've been trying to do (installed SDK's platform tools, made sure my Nexus 6 Windows drivers are installed, but when I open a command prompt to unlock the bootloader, I'm met with a, "no devices found," response, so I have no clue what to do, and need some help, because with how many tutorials I've looked up for how to do this, and none of them working, I'm about heady to break my monitor. If anyone can explain what the **** I'm doing wrong, or link to a tutorial for how to unlock the bootloader, that actually explains what's needed to do so, it'd be appreciated.
Da-JesuZ said:
Alright, I somewhat hate Android 6.0, and that's because of my hard time rooting my Nexus 6, which is, at this point, becoming immensely irritating. If I'm allowed to do so here, since this is a Q&A board, I need to ask how the hell to root this thing, because of Android's new thing where I have to install a custom kernal to get root.
All I really know, now, ids that I need to unlock the bootloader of the phone, which I've been trying to do (installed SDK's platform tools, made sure my Nexus 6 Windows drivers are installed, but when I open a command prompt to unlock the bootloader, I'm met with a, "no devices found," response, so I have no clue what to do, and need some help, because with how many tutorials I've looked up for how to do this, and none of them working, I'm about heady to break my monitor. If anyone can explain what the **** I'm doing wrong, or link to a tutorial for how to unlock the bootloader, that actually explains what's needed to do so, it'd be appreciated.
Click to expand...
Click to collapse
This is how i always root the phone:
- Enable usb debugging and ENABLE OEM UNLOCKING in developer options
- Reboot into the bootloader and type fastboot oem unlock and let the phone boot up
- Flash TWRP in fastboot
- Go to recovery and flash a modified boot.zip (all custom kernels will do)
- Flash the latest superSU.zip, also in recovery
- Done
Here is a tut for the adb setup (Windows) http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/.
- Reboot into the bootloader and type fastboot oem unlock and let the phone boot up
That's my problem. Opening up the command prompt and typing, "fastboot OEM unlock," does absolutely nothing. No prompts come up on the phone. It just sits there, and doesn't do anything.
Da-JesuZ said:
- Reboot into the bootloader and type fastboot oem unlock and let the phone boot up
That's my problem. Opening up the command prompt and typing, "fastboot OEM unlock," does absolutely nothing. No prompts come up on the phone. It just sits there, and doesn't do anything.
Click to expand...
Click to collapse
Do you see a serial number in fastboot if you type: fastboot devices? If not your drivers aren`t installed correctly or adb isn`t setup correctly.
gee2012 said:
Do you see a serial number in fastboot if you type: fastboot devices? If not your drivers aren`t installed correctly or adb isn`t setup correctly.
Click to expand...
Click to collapse
I'm using Windows Vista, so I had to add an underscore, and type, "fastboot oem_unlock," to get the bootloader unlocked. Everything is restoring, now, however, I'm wondering if I'll have to do something similar with flashing TWRP, and the kernal I'm attempting to install. I don't know programming or cmd commands.
Da-JesuZ said:
I'm using Windows Vista, so I had to add an underscore, and type, "fastboot oem_unlock," to get the bootloader unlocked. Everything is restoring, now, however, I'm wondering if I'll have to do something similar with flashing TWRP, and the kernal I'm attempting to install. I don't know programming or cmd commands.
Click to expand...
Click to collapse
You only have to flash the TWRP.img file in fastboot, the rest (boot/superSU) are zip files to be flashed in recovery. I have no experience with Vista so can`t help you there, maybe there is some info about it on Google/YouTube.
Hi
I've been so stupid that i locked the oem setting, without any OS an recovery.
By all that, i've been searching online for a solution for days, without any luck...
So now im back with a phone that's oem locked and can't unlock it because i can't allow oem unlocking in developer settings, and can't do adb push because i do not have any recovery on the phone.
Is there anybody that can help me?
Recyclebin. said:
Hi
I've been so stupid that i locked the oem setting, without any OS an recovery.
By all that, i've been searching online for a solution for days, without any luck...
So now im back with a phone that's oem locked and can't unlock it because i can't allow oem unlocking in developer settings, and can't do adb push because i do not have any recovery on the phone.
Is there anybody that can help me?
Click to expand...
Click to collapse
Can't you get to the bootloader and fastboot the stock google images? This is a N6, right?
@ktmom: He can get to the bootloader, but it's locked, which means fastboot is not an option. Worse, he apparently has no recovery installed so he can't sideload an OTA.
The OP is screwed.
Strephon Alkhalikoi said:
@ktmom: He can get to the bootloader, but it's locked, which means fastboot is not an option. Worse, he apparently has no recovery installed so he can't sideload an OTA.
The OP is screwed.
Click to expand...
Click to collapse
Yeah, spaced
What about running recovery on the pc? I've never done that. I guess it requires an unlocked bootloader also.
I dunno, this is an N9 thread as is this one, but if I was in this position, I think I'd read through these.
I didn't think of that. It may work. Then he can sideload.
Recyclebin. said:
Hi
I've been so stupid that i locked the oem setting, without any OS an recovery.
By all that, i've been searching online for a solution for days, without any luck...
So now im back with a phone that's oem locked and can't unlock it because i can't allow oem unlocking in developer settings, and can't do adb push because i do not have any recovery on the phone.
Is there anybody that can help me?
Click to expand...
Click to collapse
Power up arrow to get into bootloader mode
might have to unlock bootloader at this point (dont remember the exact process you can google it) should be another fastboot command
fastboot flash recovery preferably twrp
then you should be able to load up a rom
ktmom said:
Yeah, spaced
What about running recovery on the pc? I've never done that. I guess it requires an unlocked bootloader also.
I dunno, this is an N9 thread as is this one, but if I was in this position, I think I'd read through these.
Click to expand...
Click to collapse
How can i make a running recovery on a pc?
Tried to search for it, but i cant find anything on it
Code:
fastboot boot recovery.img
The above command sends the device into recovery mode using an image stored on a PC's hard drive. From there the owner of the device can use the recovery just as if it were installed in the /recovery partition of the device's internal storage. Files that the owner of the device wishes to use are stored in the device's internal storage.
It won't help the OP however. An unlocked bootloader is one of the pre-requisites.
Cant boot up a live recovery either, because of tge locked bootloader...
Anyone got other ideas? Im really lost with this one
Contact Lenovorola and pay for the privilege of having your device serviced. You're totally screwed.
My mi A2 is currently running on the September update, the bootloader is locked, it's fresh and clean.
From the Mi A1 Gcam experience, I'm not having that much satisfying results on the default A2 stock camera. On my A1 I used that gcam toolkit for enabling Camera2Api. So the process was pretty clean and hassle free. OTA updates were nice and fine as well.
On my A2 the case is different. So far I haven't found any sort of things like that. Most of the processes include unlocking bootloader and root then magisk. And that'd be the last thing I'd ever try to do.
So is there anyway to get Google camera working on Mi A2 without losing OTA, BOOTLOADER UNLOCK AND ROOT?
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
I've found this link. But I'm not clear about the processes.
Anybody in the community with a kind heart will be generous enough to help me out? That'd be a big help. ?
Search and read read and read ... you need to have knowledge if you want to mess with this phone, and if you are afraid of flashing, then don't do it, if you are lazy, don't do it.
There is no way to enable camera2 without unlocking botloader, and then after enabling camera2, bootloader needs to stay unlocked.
Unlocking bootloader
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484
And then, there are two ways of enabling camera2, via twrp, and with magisk install and then uninstall.
Read and learn...
TWRP method
https://forum.xda-developers.com/mi-a2/how-to/tutorial-camera2api-gcam-root-t3842475
Magisk method
https://forum.xda-developers.com/mi-a2/help/how-to-install-ota-magisk-rooted-google-t3846324
Good luck.
minnuss said:
Search and read read and read ... you need to have knowledge if you want to mess with this phone, and if you are afraid of flashing, then don't do it, if you are lazy, don't do it.
There is no way to enable camera2 without unlocking botloader, and then after enabling camera2, bootloader needs to stay unlocked.
Unlocking bootloader
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484
And then, there are two ways of enabling camera2, via twrp, and with magisk install and then uninstall.
Read and learn...
TWRP method
https://forum.xda-developers.com/mi-a2/how-to/tutorial-camera2api-gcam-root-t3842475
Magisk method
https://forum.xda-developers.com/mi-a2/help/how-to-install-ota-magisk-rooted-google-t3846324
Good luck.
Click to expand...
Click to collapse
for me it's no problem To stay bootloader unlock but i don't want to root & don't want to lose ota successful installation.
Sohailsamdani said:
for me it's no problem To stay bootloader unlock but i don't want to root & don't want to lose ota successful installation.
Click to expand...
Click to collapse
Use this tool. I used today with September update, camera api enabled and the tool only use temporary root. You have to unlock the bootloader and leave unlocked.
Good luck
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585/page12
Daniesz said:
Use this tool. I used today with September update, camera api enabled and the tool only use temporary root. You have to unlock the bootloader and leave unlocked.
Good luck
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585/page12
Click to expand...
Click to collapse
I don't want to sound silly (sorry if i do) i am on the September update, unlocked bootloader and wanting to enable camera2 api, is it as simple as pressing the corresponding number that enables the unlock or do you have to do something before and after, regards
daveparki said:
I don't want to sound silly (sorry if i do) i am on the September update, unlocked bootloader and wanting to enable camera2 api, is it as simple as pressing the corresponding number that enables the unlock or do you have to do something before and after, regards
Click to expand...
Click to collapse
Sure, just choose the right option and choose the not rooted option
Daniesz said:
Sure, just choose the right option and choose the not rooted option
Click to expand...
Click to collapse
you mean 1st i select Option 1 lock/unlock bootloader then number 7 enable camera 2 api then number 10. exit then reboot my phone. Right?
Sohailsamdani said:
you mean 1st i select Option 1 lock/unlock bootloader then number 7 enable camera 2 api then number 10. exit then reboot my phone. Right?
Click to expand...
Click to collapse
Yes, if your bootloader still locked. Remember, if you unlock your bootloader, you will loose your data, so you have to wait to boot the phone and set it up. And than option 7.
Follow the instructions in the toolkit
If I unlock and relock the bootloader, do I lose my warranty? It's the single most deciding factor for me.
Daniesz said:
Use this tool. I used today with September update, camera api enabled and the tool only use temporary root. You have to unlock the bootloader and leave unlocked.
Good luck
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585/page12
Click to expand...
Click to collapse
Would you please share the processes you've gone through using this tool? ?
I follow the instruction and I installed the Gcam, put with Camera2 api app shows only Level_3, is that normal or I did something wrong.
ali7_has said:
I follow the instruction and I installed the Gcam, put with Camera2 api app shows only Level_3, is that normal or I did something wrong.
Click to expand...
Click to collapse
Lvl 3 is camera2 api enabled :good:
minnuss said:
Search and read read and read ... you need to have knowledge if you want to mess with this phone, and if you are afraid of flashing, then don't do it, if you are lazy, don't do it.
There is no way to enable camera2 without unlocking botloader, and then after enabling camera2, bootloader needs to stay unlocked.
Unlocking bootloader
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484
And then, there are two ways of enabling camera2, via twrp, and with magisk install and then uninstall.
Read and learn...
TWRP method
https://forum.xda-developers.com/mi-a2/how-to/tutorial-camera2api-gcam-root-t3842475
Magisk method
https://forum.xda-developers.com/mi-a2/help/how-to-install-ota-magisk-rooted-google-t3846324
Good luck.
Click to expand...
Click to collapse
I tried to go on with the twrp method using that toolkit. Unlocked my bootloader manually. The when I tried to use the toolkit to temporarily get access of twrp and run cmd from computer. When I enter the command adb shell, that showed my devices wasn't found. But when the phone is turned on then that shows my devices there. So I failed to figure out that. And on the other hand it want twrp as well. It was pitch black recovery something.
Secondly when I tried to go with the command 7 to enable camera2Api, it asked to temporarily root. I kept continued with Y. It came up with a note that allow USB debug with the phone will turn on again and make sure to keep phone connected. After that my phone never turned on again :") ♥. It was bricked and I wasn't even able to flash using miflash tool. So I had to go to the repair shop to get my phone fixed.
I wonder why the process is so ugly and annoying on A2 when it was the easiest thing on the A1.
Trust me? I had enough trouble. My wholes night's sleep was gone thinking that I've just got this phone 7 days ago! ?
afridishamsofficial said:
I tried to go on with the twrp method using that toolkit. Unlocked my bootloader manually. The when I tried to use the toolkit to temporarily get access of twrp and run cmd from computer. When I enter the command adb shell, that showed my devices wasn't found. But when the phone is turned on then that shows my devices there. So I failed to figure out that. And on the other hand it want twrp as well. It was pitch black recovery something.
Click to expand...
Click to collapse
With TWRP you have to enter the commands "setprop persist.camera.HAL3.enabled 1" and "setprop persist.camera.eis.enable 1" inside TWRP's terminal on your phone screen.
afridishamsofficial said:
Secondly when I tried to go with the command 7 to enable camera2Api, it asked to temporarily root. I kept continued with Y. It came up with a note that allow USB debug with the phone will turn on again and make sure to keep phone connected. After that my phone never turned on again :") . It was bricked and I wasn't even able to flash using miflash tool. So I had to go to the repair shop to get my phone fixed.
I wonder why the process is so ugly and annoying on A2 when it was the easiest thing on the A1.
Trust me? I had enough trouble. My wholes night's sleep was gone thinking that I've just got this phone 7 days ago!
Click to expand...
Click to collapse
To "unbootloop" your phone, you should enter "fastboot flashing unlock" and "fastboot unlock flashing_critical" (without quotes) in fastboot command line prompt and proceed with MIFLASH tool. Worked twice with me and I'm pretty sure can work for you.
But another advice: the process with Majisk (with the tool -> number 7) doesn't worked with me at all. I tried twice and had to MIFLASH before just bcz of Majisk. So, for a while, I recommend keep a distance from it.
kadu20es said:
With TWRP you have to enter the commands "setprop persist.camera.HAL3.enabled 1" and "setprop persist.camera.eis.enable 1" inside TWRP's terminal on your phone screen.
To "unbootloop" your phone, you should enter "fastboot flashing unlock" and "fastboot unlock flashing_critical" (without quotes) in fastboot command line prompt and proceed with MIFLASH tool. Worked twice with me and I'm pretty sure can work for you.
But another advice: the process with Majisk (with the tool -> number 7) doesn't worked with me at all. I tried twice and had to MIFLASH before just bcz of Majisk. So, for a while, I recommend keep a distance from it.
Click to expand...
Click to collapse
Please correct me if I'm going wrong.
1) unlock my bootloader.
2) put the phone in fastboot and connect to pc while USB debug enabled.
3) open the toolkit and proceed to twrp, only boot but not install method.
4) now I've to come to my phone. On the twrp I've seen an option called terminal. I've to click and enter there.
5) now I've to enter this command on my twrp terminal.
Setprop persist.camera.eis.enable 1
setprop persist.camera.HAL3.enabled 1
6) and then reboot to phone?
kadu20es said:
With TWRP you have to enter the commands "setprop persist.camera.HAL3.enabled 1" and "setprop persist.camera.eis.enable 1" inside TWRP's terminal on your phone screen.
To "unbootloop" your phone, you should enter "fastboot flashing unlock" and "fastboot unlock flashing_critical" (without quotes) in fastboot command line prompt and proceed with MIFLASH tool. Worked twice with me and I'm pretty sure can work for you.
But another advice: the process with Majisk (with the tool -> number 7) doesn't worked with me at all. I tried twice and had to MIFLASH before just bcz of Majisk. So, for a while, I recommend keep a distance from it.
Click to expand...
Click to collapse
i tried with the terminal method. and phone was not booting. It was on bootloop again. Now again stuck with the miflash thing! please help me!!!!
afridishamsofficial said:
Please correct me if I'm going wrong.
1) unlock my bootloader.
2) put the phone in fastboot and connect to pc while USB debug enabled.
3) open the toolkit and proceed to twrp, only boot but not install method.
4) now I've to come to my phone. On the twrp I've seen an option called terminal. I've to click and enter there.
5) now I've to enter this command on my twrp terminal.
Setprop persist.camera.eis.enable 1
setprop persist.camera.HAL3.enabled 1
6) and then reboot to phone?
Click to expand...
Click to collapse
Reboot and test if the camera settings that requires camera2api are working. If they are, I recommend to torn off and go to fastboot mode again and replace the modified boot (TWRP) to the stock one.
So, you setted partition b to TWRP, restore the original boot in place of it.
---------- Post added at 08:51 ---------- Previous post was at 08:11 ----------
afridishamsofficial said:
i tried with the terminal method. and phone was not booting. It was on bootloop again. Now again stuck with the miflash thing! please help me!!!!
Click to expand...
Click to collapse
There are (probably) some files missing with the tool. As you can see in the error message, the required bat to the process is missing. Download the complete tool with its .bat files and try again.