Related
Hello,
I have my G watch R for a week and because there was no update, i've tried to install it by myself after reading some posts on XDA.
I've tried that :
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot flash recovery filename.img)
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
All this works until the "sideload" part because ADB can't see my watch when it's on recovery mode.
So i have locked again the bootloader and i thought to give up, when yesterday, OTA arrived...
But it hasn't worked : a bar has loaded and it arrived on a red triangle with an exclamation mark, i've clicked on it and i had the recovery mode menu (reboot, install from adb, etc)
What can I do to make work this OTA ?
Thanx for help !
have you tried to flash the original recovery?
Yes, I've tried several times, I think that is why i can't update with OTA.
But is there a solution ? Is it possible to reinstall original recovery and will it solve my problem ?
Or must I install the update with ADB ? Because I still don't know how make the watch recognized when in recovery mode (not even recognized with a yellow triangle, like it was unplugged )
I had the same problem but with 4.4w.2 and I solved it flashing the stock recovery. unfortunately I can not find your recovery version, I would have linked. to manually update do not know ... I'm sorry. Find your recovery and flash it!
Thanx for your answer,
I thought to do that, but I neither have found 44w1 stock, i'm trying with 44w2 stock and it doesn't work.
I'll try to find 44w1 stock, thanx for confirmation about this way.
So, while I can't find 44w1 stock (i think nobody has uploaded it on the internet because nobody wants to put 44w1 on his watch ^^ ), I've tried TWRP Recovery
When I try to launch the 5.5.1 zip install , I have this error message on the watch in TWRP Recovery :
"this package is for device: lenok. this device is dory"
I've made some research and found that Dory is for G Watch and not for G Watch R, so what ?
I don't understand...
Anyway, if someone knows where to find 44w1 stock...
Did you enabled the debugging mode and gave permission for it on the watch?
sounds like you are missing the ADB drivers on your PC
and be careful with sideloading the update to select the correct one, e.g. the last update is an incremental one and won't flash on 4.4 (or if you get it to flash, it will probably not worke)
good luck!
Have a look here... http://4pda.ru/forum/lofiversion/index.php?t647135-20.html.
It's not English, but the links are all there. I recently updated a watch from 4.4 to 5.11 using these images. Put the watch into Bootloader and install the ADB drivers, then start with 4.4w2 and work your way up. It takes time as you'll need to restart the watch each time.
Genna7 said:
Did you enabled the debugging mode and gave permission for it on the watch?
Click to expand...
Click to collapse
Yes I did : I could flash a recovery because I've given permission and enabled debugging mode
2k4ever said:
sounds like you are missing the ADB drivers on your PC
and be careful with sideloading the update to select the correct one, e.g. the last update is an incremental one and won't flash on 4.4 (or if you get it to flash, it will probably not worke)
good luck!
Click to expand...
Click to collapse
No I'm not, same answer : I could flash a recovery without any problem : it's only when I'm on recovery that I can't communicate with the watch : It's working when android wear is started and when I'm on bootload. Thanx for the warning
dunjamon said:
Have a look here... *url*
It's not English, but the links are all there. I recently updated a watch from 4.4 to 5.11 using these images. Put the watch into Bootloader and install the ADB drivers, then start with 4.4w2 and work your way up. It takes time as you'll need to restart the watch each time.
Click to expand...
Click to collapse
Thank you but i have all those images, I think I need 44w1 recovery and only this one
Thank you all
what happens if you just flash the 4.4w2 full image? I remember there being issues with the 4.4 recovery and I had to manually update to the 5.0.1 recovery before then upgrading further.
edit...what drivers are you using? I think you need the adb composite ones and not the normal adb ones.
I'm using the naked ones I think.
What image are you talking about ? System or recovery ?
Ze_Pend said:
I'm using the naked ones I think.
What image are you talking about ? System or recovery ?
Click to expand...
Click to collapse
The OTA ones from my link.
Ze_Pend said:
Yes I did : I could flash a recovery because I've given permission and enabled debugging mode
No I'm not, same answer : I could flash a recovery without any problem : it's only when I'm on recovery that I can't communicate with the watch : It's working when android wear is started and when I'm on bootload. Thanx for the warning
Click to expand...
Click to collapse
flashing a recovery happens in fastboot mode, which requires an unlocked bootloader, but not enabling the debugging mode
sideloading however happens (once the recovery has been loaded) through ADB - and ADB requires the right drivers on your PC as well as the right tools/developer environment
try to connect your normally booted watch to your PC and run
PHP:
adb devices
if that lists your watch, you are good to go, otherwise ADB isn't set up properly
The watch is listed by adb devices when on work mode or in bootloader mode, but not when in recovery mode.
That's what I said first
dunjamon said:
The OTA ones from my link.
Click to expand...
Click to collapse
Either I can't if with 44w2 recovery, or it says ""this package is for device: lenok. this device is dory" if with TWRP recovery.
Ze_Pend said:
Either I can't if with 44w2 recovery, or it says ""this package is for device: lenok. this device is dory" if with TWRP recovery.
Click to expand...
Click to collapse
Do you have the G Watch R (round) or the G Watch (Square)?
"The watch is listed by adb devices when on work mode or in bootloader mode, but not when in recovery mode."
I had this problem too. When you're in recovery mode you have to open the windows device manager and windows should tell you something about an uninstalled driver. You need to right click this device and install the adb drivers.
When I first purchased this phone I was able to boot to the default recovery that came with the phone ( which clearly had a *fastboot option*), it came with stock 5.1, and a bunch of bloatware.
I downloaded the one click root method for the h811 which was perhaps the easiest root i've ever done. great. i also had to flash my recovery to twrp 2.8 for some reason.
Rocked out to a newely rooted device on 5.1 until the t mobile bloatware and system update notification kept bugging me, so I said * eff it, i've been holding out for a while*
So I get to the cm 13 wiki for my device, I managed to install the cm recovery ( cant remember how i did this for some reason) and then i was able to flash cm13 to my phone. CM13 is sleek, and smooth but is presenting problems.
First of all, no google play store and the gapps zip wont install through cm recovery ( fails and tells me to use twrp instead which is a problem because i can't boot this phone into fastboot mode)
I am unrooted and can not figure out how to properly root a T mobile h811 running cm13, so the twrp manager doesn't work because it "requires root" then shuts down. ( enable root access in the cm13 developer options does nothing at all and yes, for adb and apps)
FAST BOOT MODE DOES NOT SEEM TO EXIST ANYMORE ON MY PHONE - Following the many tutorials, which goes long the lines of using adb/fastboot, adb devices can see my device, but fastboot devices can't ( figures) because its not in fastboot mode. Any fast boot reboot bootloader or any variant of that command only reboots the phone, to... swipe the screen.
I've installed the lg bridge crap ( which installed an updated usb driver) that doesn't even recognize my phone " no mobile device connected". tried uninstalling and reinstalling, but nothing. When putting the phone in download mode, to see if adb would rcognize it, windows sees this as a new device , installs drivers but says " device can not start, code 10 * in device manager. :silly:
is there anything that can be done?? google searches result in obvious solutions that SHOULD work but don't, or threads where a person coincidentally has the same exact problem as I do, but their response is usually the last response in the thread that goes unanswered
summary : I've install cm13 on my lg g4 h811, I do not have root access, I can not install twrp due to ( no fastboot mode) in effect, i cant install gapps, cant root phone etc..
any help?
did you ever unlock the phone....?
Yes, unlocking the phone is one of the first things you would need to do. In Developer Options > OEM Unlock. Then in bootloader, run the unlock command. This will delete /data and internal storage so back up your files so you can transfer them back via adb or fastboot.
Then you're probably going to need to temp boot TWRP, then flash the TWRP recovery image in TWRP. THEN you can flash properly.
Carefully read through this thread:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Good luck.
Edit: oh and this thread belongs in Q&A.
Alright. Am I only to read the first post or all 30+ pages? ( not that i have a problem, just curious)
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
aoaleman said:
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
Click to expand...
Click to collapse
"ARE YOU HAVING TROUBLE WITH LGUP NOT SEEING YOUR MOBILE?
Try this....... take the back off your mobile so you can get at the battery. Connect your mobile via USB. Start LGUP, if it does not see your phone DO NOT DISCONECT, DO NOT RESTART OR TURN OFF LGUP. Take out the battery and then put it back in.......let the phone restart on its own. LGUP should now see it."
didn't work, very frustrating. any clues? on windows 8.1 by the way. tried two computers. none can see this phone. I can connect the phone to the computer and see its storage, lg usb driver is installed
You probably need to reinstall the drivers. It might be the fastboot driver. That's what worked for me.
I've reinstalled the official drivers, uninstalled them... Jusst the mobile USB driver, a combo of both, plenty of times. Don't understand why this software doesn't see my phone
Lgup, lgair, lg bridge, lg USB driver (skinned down) .. Nothing works tested on my gaming rig., and work laptop both running win 8.1 64 bit
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
TacoTuco said:
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
Click to expand...
Click to collapse
This section does get more views though haha.
Anyway I feel that the 811 is one of the more finicky devices to get into fastboot at least in my experience. I had to enable and disable dev options while plugging and unplugging device and it finally worked. No idea if that'll work for everyone though.
I reasked the question in Q and A. Please help some one.
You start over. LG bridge.
Having the same issue. I'm on Windows 10. What developer settings did you mess with to get it working, tiskewlio?
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Sunaj1 said:
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Click to expand...
Click to collapse
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
thevirgonian said:
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
Click to expand...
Click to collapse
silly question maybe, but is there a specific tutorial in getting this to work with the files provided given my situation? (commands, etc..) will this somehow bypass the the lge mobile mtp device that wont install ? I had installed the system wide adb/fastboot drivers, and already had a folder with just the minimal install of the adb but didnt have a few files in the one you provided ( lg root, busy box, etc) so not quite sure what to do with them.
Again, if possible want to flash twrp recovery to my device but can't due to * waiting for any device* and the ( device cannot start ) error
Thanks
* waiting for device* when putting phone in download mode and pushing fastboot flash twrp-2.8.7.1-h811.img.
Any help would be appreciated as I need to get the driver to work first. see attached picture.
Cha h
the issue is largly resolved as i've been able to flash the recovery and install another rom. But i'd still like to know how to get the download mode driver properly working in the event i need a computer and can't do a self contained install.
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
travisd4est said:
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
Click to expand...
Click to collapse
i dont know man, i did all that a million times over, but recently i was able to just flash the stock MM rom to the device using LGup. Think i'll just stick with stock rom and root for a while as all this stuff is a little finicky at times. Thanks for your help.
I bought a new canvas a1 for one of my family member . it's not booting up and currently running on mm 6.0.1 .
Here's from which problem started -
I updated Android system web view app after which it took optimising app at every reboot (more than 80 apps) .
I went to stock recovery and wiped data , phone stuck in bootloop , after trying 3-4 times I again went to stock recovery and factory reseted phone ....now also it's not booting up ....what to do ????
Condition: never rooted
Never installed custom recovery
Bootloader locked.
devil anand said:
I bought a new canvas a1 for one of my family member . it's not booting up and currently running on mm 6.0.1 .
Here's from which problem started -
I updated Android system web view app after which it took optimising app at every reboot (more than 80 apps) .
I went to stock recovery and wiped data , phone stuck in bootloop , after trying 3-4 times I again went to stock recovery and factory reseted phone ....now also it's not booting up ....what to do ????
Condition: never rooted
Never installed custom recovery
Bootloader locked.
Click to expand...
Click to collapse
Hey, just try to unlock its bootloader and flash a custom recovery, then get official zip of 6.0 from the thread, and do Clean wipe flash it! It'll works
sachin n said:
Hey, just try to unlock its bootloader and flash a custom recovery, then get official zip of 6.0 from the thread, and do Clean wipe flash it! It'll works
Click to expand...
Click to collapse
Already tried that ! Stuck in waiting for device in cmd and Android one toolkit app freezes .....??
devil anand said:
Already tried that ! Stuck in waiting for device in cmd and Android one toolkit app freezes .....
Click to expand...
Click to collapse
Firstly connect your phone to PC and update device drivers. Then PC should be able to recognize your phone and you should be able to unlock bootloader of your A1 via cmd or ANDROID ONE TOOLKIT.
Try this : http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
It will install adb & fastboot on your PC and also google usb drivers.
Just connnect your phone and update the drivers from Device Manager.
After that you can try all that stuff
Good luck.:good::good:
Utkarsh_Tiwari said:
Firstly connect your phone to PC and update device drivers. Then PC should be able to recognize your phone and you should be able to unlock bootloader of your A1 via cmd or ANDROID ONE TOOLKIT.
Try this : http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
It will install adb & fastboot on your PC and also google usb drivers.
Just connnect your phone and update the drivers from Device Manager.
After that you can try all that stuff
Good luck.:good::good:
Click to expand...
Click to collapse
Will give it a try and tell.
Utkarsh_Tiwari said:
Firstly connect your phone to PC and update device drivers. Then PC should be able to recognize your phone and you should be able to unlock bootloader of your A1 via cmd or ANDROID ONE TOOLKIT.
Try this : http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
It will install adb & fastboot on your PC and also google usb drivers.
Just connnect your phone and update the drivers from Device Manager.
After that you can try all that stuff
Good luck.:good::good:
Click to expand...
Click to collapse
It worked ....thnnxxx .....???
devil anand said:
It worked ....thnnxxx .....
Click to expand...
Click to collapse
Hello to everyone.
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Its possible to fix? or my phone its ****ed, or there is one form to installl the gapps from anoter form?
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
i offer some pay.
Update:
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
Help me pls:crying:
I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli
Gravemind2015 said:
I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.
vmmiguel said:
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.
Click to expand...
Click to collapse
My windows cmputer says that my device doesnt works properly, i read all night about this and i think when i some point i made wipe /system so i delete the twrp and the rom doesnt have usb adb i think so hahaha, i think now my x4 will stuck on only aosp 9.0 without g services :crying::crying::crying:
id start with a flash all of the latest stock firmware to clean it up. then start over
edufur said:
id start with a flash all of the latest stock firmware to clean it up. then start over
Click to expand...
Click to collapse
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...
vmmiguel said:
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...
Click to expand...
Click to collapse
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.
Comby_sk said:
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.
Click to expand...
Click to collapse
Hello Buddy, i tried that but doesnt work, recently i discover that my usb default mode is gray so i think i cant switch beetwen the usb option, and i tried ADB over network, in terminal emulator to run adbd service but it crash :c
@erfanoabdiadbi plz you cant help me, i really i was enjoying you excelent deveploment, but now in stuck in this without essencial apps like whatsapp, my smartphone works like only phone without been smart jajaja:crying::good:
Anyone?
vmmiguel said:
Anyone?
Click to expand...
Click to collapse
Read through this thread carefully...
https://forum.xda-developers.com/moto-x4/development/rom-lineage-16-0-developer-preview-t3849699
I have more or less the same problem.
I am stuck in LineageOS 15.1 and for some reason Windows does not recognize my phone (it does with other x4 phone from a friend).
I also don't have GApps installed and also don't have root access. Since I can't connect my phone, I can't root or flash some custom recovery.
I really need some help.
I installed Evolution X rom 4.7 on my Mi A2 device with twrp and also installed magisk.Then I flashed Agni Kernel for performance after some days.When the update of evolution x came I decided to update it via dirty flashing the zip file.Then the device booted and the kernel was reverted back to evo-x main kernel.But then I realized that twrp recovery and root permission are completely gone after the boot.Still I ran the device for some time and after some day I had to reset my pc in which adb,fastboot etc. were previously installed.But now when I connect the phone with pc on fastboot mode,it doesn't show my device's name.And now I cannot manually install the adb drivers of the phone.I thought factory resetting evolution x will solve it but it did't.Now my phone has no recovey,and no os .I also tried to use MiFlash to flash stock rom but the device disappears from the list after selecting flash.I cannot find any solution for this device.Please help me.
(When I unlocked bootloader for the first time I used fastboot flashing unlock and unlock_critical both)
i think u use adm cpu cause this happens mostly there nly ...dw just flash a good and stable firmware via otg and this should fix this
IrazShahriar said:
I installed Evolution X rom 4.7 on my Mi A2 device with twrp and also installed magisk.Then I flashed Agni Kernel for performance after some days.When the update of evolution x came I decided to update it via dirty flashing the zip file.Then the device booted and the kernel was reverted back to evo-x main kernel.But then I realized that twrp recovery and root permission are completely gone after the boot.Still I ran the device for some time and after some day I had to reset my pc in which adb,fastboot etc. were previously installed.But now when I connect the phone with pc on fastboot mode,it doesn't show my device's name.And now I cannot manually install the adb drivers of the phone.I thought factory resetting evolution x will solve it but it did't.Now my phone has no recovey,and no os .I also tried to use MiFlash to flash stock rom but the device disappears from the list after selecting flash.I cannot find any solution for this device.Please help me.
(When I unlocked bootloader for the first time I used fastboot flashing unlock and unlock_critical both)
Click to expand...
Click to collapse
If you have another Android phone and an otg adapter use bugjaeger app and use adb and fastboot in that device instead of your pc
IrazShahriar said:
I installed Evolution X rom 4.7 on my Mi A2 device with twrp and also installed magisk.Then I flashed Agni Kernel for performance after some days.When the update of evolution x came I decided to update it via dirty flashing the zip file.Then the device booted and the kernel was reverted back to evo-x main kernel.But then I realized that twrp recovery and root permission are completely gone after the boot.Still I ran the device for some time and after some day I had to reset my pc in which adb,fastboot etc. were previously installed.But now when I connect the phone with pc on fastboot mode,it doesn't show my device's name.And now I cannot manually install the adb drivers of the phone.I thought factory resetting evolution x will solve it but it did't.Now my phone has no recovey,and no os .I also tried to use MiFlash to flash stock rom but the device disappears from the list after selecting flash.I cannot find any solution for this device.Please help me.
(When I unlocked bootloader for the first time I used fastboot flashing unlock and unlock_critical both)
Click to expand...
Click to collapse
I had a same issue today, i tried to install Android 12 into my device witch was a success, but then the rom keeps reboot. Then I booted into fastboot mode, then i realised the icon of the fastboot has changed and the other roms also keeps crashing. After I tried to restore the original firmware, but it was went wrong, after the flasher installed the system_b the phone restarted, and wont start booting up, then I was put the device into fastboot mode and the pc didn't recognised my phone.
Solution: I dissasembled my phone and i tried to boot my phone to edl mode this video helped me a lot. He forgot to mention, when you short this 2 pins in the motherboard you need to connect the battery AND hold the power button as well to enter edl mode. After you need to install the Qualcomm edl driver then you can install your firmware with MiFlash