Database Develop

Help me please, I don´t have gapps installed...

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.

Mi A2 not detected in fastboot after flashing custom rom on stock oreo

Hello so i was on stock oreo then i tried to flash ACIP 9.0 everything was going fine i switch to A so i can install gapps then rebooted to fastboot then tried to boot recovery the phone wasn't detected on PC so now my phone isn't getting detected on fast boot tried diff pc nothing i can only boot to fastboot but can't do anything..

Are you the same guy on telegram. Which had problem due to USB debugging off?

Install Qualcomm_USB_Driver_V1.0

i'm having the same problem. i wonder if the phone got fixed

Xiaomi Mi 9 stuck in a bootloop, now with no OS. Help needed

Yeah, I'm not feeling very smart right now.
Short story:
Accidentally wiped OS in TWRP, now only seem to have access to fastboot. Can I fix this? Flash another ROM? Anything? Bootloader is unlocked, can't seem to get into TWRP anymore. Power + Volume up only takes me to fastboot again.
Long story:
Magisk module caused a bootloop. Wanting to try and avoid a factory reset, I tried sideloading Magisk for TWRP which didn't work, ultimately gave up and wanted to perform a factory reset via TWRP, but I've been working late and ticked the wrong box without thinking. Bad idea, I know. Wiped system, yes.
Aside from feeling exceptionally stupid, can this situation be salvaged? The phone doesn't switch off, it just sits in fastboot. I have Minimal ADB and Fastboot on my PC. Any help will be greatly appreciated, really.

Just in case anyone else ends up with a similar problem, the resolution was fortunately rather straightforward - I needed to grab the Mi Flash tool (as it turns out, this version worked best), stock firmware for my version, go into fastboot (which was no issue as that was the only thing my phone would do) and then open the Mi Flash tool and flashing the firmware was pretty straightforward from there. I even managed to get a BSOD during the process, but it's not like it could get any worse, anyway. Rebooted, restarted the process and about 10-15 minutes later, my phone was happily booting again.

divided by zero said:
Just in case anyone else ends up with a similar problem, the resolution was fortunately rather straightforward - I needed to grab the Mi Flash tool (as it turns out, this version worked best), stock firmware for my version, go into fastboot (which was no issue as that was the only thing my phone would do) and then open the Mi Flash tool and flashing the firmware was pretty straightforward from there. I even managed to get a BSOD during the process, but it's not like it could get any worse, anyway. Rebooted, restarted the process and about 10-15 minutes later, my phone was happily booting again.
Click to expand...
Click to collapse
With Fastboot mode and Mi flash as fail safes , we can flash to our hears content with no worries !
Also a more automated tool is a custom mi flash tool by a developer called XiaimiToolV2 ,which has a dedicated mode for bricked phones or downloads the latest fastboot roms for you.

crs951 said:
With Fastboot mode and Mi flash as fail safes , we can flash to our hears content with no worries !
Also a more automated tool is a custom mi flash tool by a developer called XiaimiToolV2 ,which has a dedicated mode for bricked phones or downloads the latest fastboot roms for you.
Click to expand...
Click to collapse
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?

mstaglicic said:
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
Click to expand...
Click to collapse
I had excaxtly that witha my mi5 , completely dead .
Leave it on the charger for a little bit,mine after an unsuccessful flash with mi flash (catastrophic error message) it turned back on.
IF not download XiaomiTool V2 and try the option for bricked phones.

I tried that yesterday but that option is still in development. Only the modifications one is supported currently. As for the issue mentioned, maybe it's really just a matter of charging the phone first. Can't hurt either way.

mstaglicic said:
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
Click to expand...
Click to collapse
Try to use the EDL mode

How to force it to EDL by key combination or maybe deep flash cable ?
My Mi account is authorized for EDL flash but I cant get Mi9 into EDL mode on my PC ( Windows10 )

No OS, but working TWRP
Hi,
I have a similar problem with my mi 9.
I followed a really bad description for the update xiaomi.eu from MIUI10 to MIUI11.
https://www.chinahandys.net/xiaomi-eu-rom-update/
It recomended to wipe alvik / Art Cache, Cache AND System :crying:
So I do not have no OS any more. However, TRWP is still working.
I have a Backup but it did not work :crying:
Is there a better option than the Mi Flash tool?
Please help me!

Since you already have TWRP, download the latest Xiaomi.eu custom ROM available for the Mi 9, which is 9.11.7 to your computer.
Also download the latest TWRP by Mauronofrio from XDA which is 3.3.1-42.
Then use adb to transfer both the ROM and TWRP to your Mi 9.
In TWRP, install TWRP first and manually reboot to twrp using the vol up + power button.
In TWRP, install the ROM, do a factory reset, then finally reboot.
Sent from my MI 9 (Cepheus) using Tapatalk

sangbuana said:
Since you already have TWRP, download the latest Xiaomi.eu custom ROM available for the Mi 9, which is 9.11.7 to your computer.
Also download the latest TWRP by Mauronofrio from XDA which is 3.3.1-42.
Then use adb to transfer both the ROM and TWRP to your Mi 9.
In TWRP, install TWRP first and manually reboot to twrp using the vol up + power button.
In TWRP, install the ROM, do a factory reset, then finally reboot.
Sent from my MI 9 (Cepheus) using Tapatalk
Click to expand...
Click to collapse
Thank you very much for your reply.
When I tried to make my TWRP backup work I had several problems.
First was "vendor read only". So I went in TWRP to "mount" and unticked the "mount vendor partition read-only" (sounds easy, took me some time to find out)
Then I was able to do the restore without error message. However just boot loop and only the possibility to access TWRP.
After some while I realized that this restored the wiped system partition.
So I flashed the aktual MIUI 11 9.11.7 again and rebooted.
And it worked perfectly! :victory:
I did no Factory reset all the time, it seems that everything is perfect!
No lags, no problems with the camera, no issues with auto rotation.
Tom

Stuck in fastboot, phone not visible on USB

Left my phone to charge, found it in fastboot mode. When I try to reboot it, no matter what key combination I use, it reboots in fastboot mode. The problem is that the phone is not detected at all over USB. I tried to connect it to both Linux and Windows computers and plugging and unplugging the phone is simply not detected. Any ideas on how to proceed?

I only have a 24-hour period of experience with this phone, but it's strange that it wen't into fastboot during charging.
I will try to point out the main procedures I had to follow after my wife's Mi8 SE freezed after updating with recovery from MIUI 9 (from 2018) to MIUI11 (2020). I had to use platform tools for MacOs to use fastboot commands (mainly fastboot flash recovery to install a new recovery with English language; installed this: https://forum.xda-developers.com/mi-8-se/development/recovery-sky-hawk-recovery-project-2-1-t4051645).
Even after installing this recovery in fastboot mode on a MacOS computer, I had to flash a fastboot firmware downloaded from the Xiaomi Mi8 SE firmware site, only provided for Chinese only firmwares. Had to install the MiFlash and the Qualcomm driver provided for the phone by Xiaomi in a Windows computer, in order to flash the Chinese ROM using MiFlash. After several tries, discovered that I could not let the phone start with the Chinese ROM otherwise, after installing a Global ROM the phone, went back to fastboot... After flashing the Chinese ROM, installed the previously referred recovery in MacOS using the necessary command and afterwards booted into recovery mode (power and volume +), mounted the internal storage, and copied the Global ROM to the phone. Still in recovery mode wiped Cache and Dalvik cache, and installed the Global ROM. After doing this, the phone started correctly with MIUI 11.
I just want to let you know this, in MiFlash I used the mode "Install and delete all". Don't know if this works flashing in mode "Install and keep user data", if you need to maintain your data in the phone.
Hope this helps (I lost our solving my problem).

Strange Error: No USB Connection, only Fastboot possible, TWRP does not load

Hello everyone.
My dad sent me his Mi A2 to have a look after not booting into the (rooted) stock ROM. So I have done some "repairs"...
First, I managed to flash the latest LineageOS for the Mi A2. This worked, but after the next LOS update was released, I could only update the system after a factory reset.
So I began the whole procedure again: I flashed TWRP (version 3.5.2_9.0) on the active slot (using an Intel PC, an USB 2.0 port, a good cable), installed the system (LOS 18.1) again, changed the active slot, installed TWRP on this one and rebooted to recovery. The phone booted to the TWRP splash screen and then... nothing. It stays in a (very dark) TWRP splash screen. Then I changed to fastboot mode, tried to boot a temporary TWRP, but it refused to. I tried the latest Mi Flash tool, but although it recognized the phone, it couldn't flash the latest stock ROM. After that the PC suddenly said that the device cannot be recognized and now I cannot access the phone via USB, although PC, USB port and cable did not change. I tried to acces EDL by using test points - nothing. The phone charges, but nothing else works. I cannot boot into recovery, I cannot boot into the system, I only can boot into Fastboot, but have no USB connection.
Is this a hardware error? Did I mess up something at some point? What else can I do (except putting it into the recycling bin)?
Thanks for your help in advance
Nufan