Related
Hello, I have an xt1771 that does not come out of the motorola logo even if it passes several roms with sp flash tool(i tried "download only", "firmware upgrade" and "format all + download") it only turns on, vibrates, gets some seconds on the motorola logo and stays in that loop, I can not access the recovery and the bootloader is blocked, not allowing me to use any command. Any idea what to do?
Sorry for my bad English .
Unlock the bootloader and install twrp and then flash no-verity-opt-encrypt zip file to disable dm-verity.
AnonyWorld said:
Hello, I have an xt1771 that does not come out of the motorola logo even if it passes several roms with sp flash tool(i tried "download only", "firmware upgrade" and "format all + download") it only turns on, vibrates, gets some seconds on the motorola logo and stays in that loop, I can not access the recovery and the bootloader is blocked, not allowing me to use any command. Any idea what to do?
Sorry for my bad English .
Click to expand...
Click to collapse
Just curious how long are you waiting on the Moto Logo screen? I've seen it take upwards of 20 minutes on some ROMs.
TheHitMan said:
Unlock the bootloader and install twrp and then flash no-verity-opt-encrypt zip file to disable dm-verity.
Click to expand...
Click to collapse
I can't unlock bootloader, i open the prompet and write "fastboot oem unlock", in the device i see an message (img1) if i press vol + i see in the prompt "operation not allowed" and if i press vol - the phone back to bootloader screen and in prompt i look the message "OK" but the bootloader was not unlocked. I believe that be because i not flag the "oem unlock" in developer options.
bobbyphoenix said:
Just curious how long are you waiting on the Moto Logo screen? I've seen it take upwards of 20 minutes on some ROMs.
Click to expand...
Click to collapse
I think 5 or 10 minutes, but the phone not make the "hello moto" just stay in loop on the "motorola powered by android" per more or less 50 seconds, i can't acess recovery and can't unlock bootloader, believe that be because i not flag the "oem unlock" in te developer options.
AnonyWorld said:
I can't unlock bootloader, i open the prompet and write "fastboot oem unlock", in the device i see an message (img1) if i press vol + i see in the prompt "operation not allowed" and if i press vol - the phone back to bootloader screen and in prompt i look the message "OK" but the bootloader was not unlocked. I believe that be because i not flag the "oem unlock" in developer options.
Click to expand...
Click to collapse
Yes.
You are right. OEM unlock should be enabled in developer options.
TheHitMan said:
Yes.
You are right. OEM unlock should be enabled in developer options.
Click to expand...
Click to collapse
Unless it's different on the Mediatek variant, he needs an unlock code from Motorola, yes? https://forum.xda-developers.com/moto-e4-plus/how-to/bootloader-unlock-custom-recovery-t3738683
Sizzlechest said:
Unless it's different on the Mediatek variant, he needs an unlock code from Motorola, yes? https://forum.xda-developers.com/moto-e4-plus/how-to/bootloader-unlock-custom-recovery-t3738683
Click to expand...
Click to collapse
Probably NO. Only Qualcomm variant of E4 and E4 Plus requires an unlock key from motorola. Mediatek variant doesn't need it at all.
"Allow oem unlock" should be enable in developer option else if it isn't enable by default, one should enable this in custom recovery through some setprop conditions.
Sizzlechest said:
Unless it's different on the Mediatek variant, he needs an unlock code from Motorola, yes? https://forum.xda-developers.com/moto-e4-plus/how-to/bootloader-unlock-custom-recovery-t3738683
Click to expand...
Click to collapse
Qualcomm variant is different from the mediatek variant.
TheHitMan said:
Probably NO. Only Qualcomm variant of E4 and E4 Plus requires an unlock key from motorola. Mediatek variant doesn't need it at all.
"Allow oem unlock" should be enable in developer option else if it isn't enable by default, one should enable this in custom recovery through some setprop conditions.
Click to expand...
Click to collapse
I can't write unsigned softwares with flash tool. Any idea?
AnonyWorld said:
I can't write unsigned softwares with flash tool. Any idea?
Click to expand...
Click to collapse
Did you have any working recovery in your device ?
TheHitMan said:
Did you have any working recovery in your device ?
Click to expand...
Click to collapse
I do not know, because this phone is not my. The owner said that out of nowhere the phone was in this state. I do not believe the owner knows what a custom recovery is.
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.
I read today this on searching in google to enable camera2api without root in mia2..
I'm in feb update (india).
I downloaded these patch boot file & trying to go in fastboot mode..
But when i connect my phone to laptop (windows 7), there is connecting sound i heard ..
I enabled already oem unlocking option & usb debugging in phone through tapping 7 times & all ..
But when after inserting commands in adb & entered , it's saying waiting for device..
& Nothing is shown in screen in mi a2 , other than fastboot bunny..
Can anyone help me what's going on wrong here ?
Link of that site :
https://www.the***********.com/enable-camera2-api-xiaomi-mi-a2-lite-guide/
The *** is putted by xda automatically in link..
In actual in place of *** it is 'the custom Android' (without space)
Appar khandelwal said:
I read today this on searching in google to enable camera2api without root in mia2..
I'm in feb update (india).
I downloaded these patch boot file & trying to go in fastboot mode..
But when i connect my phone to laptop (windows 7), there is connecting sound i heard ..
I enabled already oem unlocking option & usb debugging in phone through tapping 7 times & all ..
But when after inserting commands in adb & entered , it's saying waiting for device..
& Nothing is shown in screen in mi a2 , other than fastboot bunny..
Can anyone help me what's going on wrong here ?
Link of that site :
https://www.the***********.com/enable-camera2-api-xiaomi-mi-a2-lite-guide/
The *** is putted by xda automatically in link..
In actual in place of *** it is 'the custom Android' (without space)
Click to expand...
Click to collapse
Try to connect the phone on USB after you see Fastboot bunny and proceed with the commands.
kadu20es said:
Try to connect the phone on USB after you see Fastboot bunny and proceed with the commands.
Click to expand...
Click to collapse
Phone is connecting to windows.. sound can be heard but still adb command saying waiting for the device
Try installing the ADB and Fastboot drivers.
XRed_CubeX said:
Try installing the ADB and Fastboot drivers.
Click to expand...
Click to collapse
Yeah i did & worked..
I installed gcam 6.1.021
But it's not stable..
Crashing most of the times
Wrong Section. Please move it to Q&A.
Thanks.
Appar khandelwal said:
Yeah i did & worked..
I installed gcam 6.1.021
But it's not stable..
Crashing most of the times
Click to expand...
Click to collapse
Try using Tolyan's v1.4a, its pretty stable to me
https://f.celsoazevedo.com/file/gcamera/MGC_6.1.021_BSG_Arnova-based_v.1.4a_TlnNeun.apk
Another help me post so please understand this is my last breath asking for guidance and advice, here goes.
I have a huawei p9 thats gotten an unlocked bootloader. in the past i added twrp and flashed a custom rom. somewhere down the line my its gotten really bad. i cannot select twrp recoverey mode nor can i manualy boot into twrp because my custom rom closes dev options in my settings. as i click it instantly closes. this happens to magisk and twrp app on the phone. so since i cannot enable oem unlock or usb debugging i cannot use my pc to harbour my device, adb shell wont recognise the device when opened in the adb directory using serveral guides.
here is a list of what i cannot do,
fastboot&rescue mode is it's only reboot function apart from loading custom firmware.
cannot access twrp thats on the device (used it to flash a firmware, also tried the .apk)
windows adb wont recognise the device neither will hisuite (huawei's windows device manager)
cannot load dev options even though i have it unlocked through clicking build 7-10 times. (opens and closes simultaneously)
i cannot enable usb debugging via dev options (custom firmware wont load it even though it's unlocked)
once phone reboot's into recovery mode it says android reason reboot; cold boot N/A (phone unlocked/FRP unlocked) no options to navigate from there.
KingBevster said:
Another help me post so please understand this is my last breath asking for guidance and advice, here goes.
I have a huawei p9 thats gotten an unlocked bootloader. in the past i added twrp and flashed a custom rom. somewhere down the line my its gotten really bad. i cannot select twrp recoverey mode nor can i manualy boot into twrp because my custom rom closes dev options in my settings. as i click it instantly closes. this happens to magisk and twrp app on the phone. so since i cannot enable oem unlock or usb debugging i cannot use my pc to harbour my device, adb shell wont recognise the device when opened in the adb directory using serveral guides.
here is a list of what i cannot do,
fastboot&rescue mode is it's only reboot function apart from loading custom firmware.
cannot access twrp thats on the device (used it to flash a firmware, also tried the .apk)
windows adb wont recognise the device neither will hisuite (huawei's windows device manager)
cannot load dev options even though i have it unlocked through clicking build 7-10 times. (opens and closes simultaneously)
i cannot enable usb debugging via dev options (custom firmware wont load it even though it's unlocked)
once phone reboot's into recovery mode it says android reason reboot; cold boot N/A (phone unlocked/FRP unlocked) no options to navigate from there.
Click to expand...
Click to collapse
There was another question and answer about the bricked phone with FRP locked in this same P9 Q&A subforum, see there for DC Phoenix
https://forum.xda-developers.com/showpost.php?p=80633145&postcount=2
zgfg said:
There was another question and answer about the bricked phone with FRP locked in this same P9 Q&A subforum, see there for DC Phoenix
https://forum.xda-developers.com/showpost.php?p=80633145&postcount=2
Click to expand...
Click to collapse
i have found it, thank you.
Hi guys so my device is on global miui 12.0.6.0 stable and whenever i check for updates it says its the latest but I know there is an android 11 already, my device is still on android 10.
So next step is to unlock adb and fastboot right so I can update my device.
I did all the steps necessary.
OEM Unlock is on
MI account is connected on (mi unlock status)
usb debugging is on
install via usb is on
usb debugging security settings is on
No password (lockscreen)
Other things I've done:
I installed the Miui 12 on the check update screen twice
I factory reset on settings
I cleared all data on recovery settings (stock recovery only of miui)
andd still no LUCK! I badly need some of you high IQ guys here to help me resolve this please My mind hurts its like the factory of fastboot of this phone has somehow got corrupted....
I can hear a sound when connecting via usb when on black screen fastboot mode
I can even access adb commands like " adb reboot bootloader & adb reboot fastboot " and they all leads to the BLACK SCREEN FASTBOOT (NO LOGO) MODE T.T
Does >fastboot devices respond with your phone?
HaveSomeCyanide said:
Does >fastboot devices respond with your phone?
Click to expand...
Click to collapse
after tweaking and tweaking it does. Fortunately MI Unlock also works even if its just a black screen fastboot mode. so weird but it is what it is
HaveSomeCyanide said:
Does >fastboot devices respond with your phone?
Click to expand...
Click to collapse
after tweaking and tweaking it does. Fortunately MI Unlock also works even if its just a black screen fastboot mode. so weird but it is what it is
I believe that this shouldn't modify fastboot, try to reflash the latest and original MIUI rom using flash_all.bat (don't use flash_all_lock.bat)
It should fix any corrupted partitions. Or it may not do anything.