Database Develop

[Q] PC won't find this messed up phone

Okay, so this is the status quo of my friends phone: HTC One M7 UL, S-On, HBOOT-1.55, TAMPERED, UNLOCKED
There is no OS instelled, I can only boot into recovery (while booting from the bootloader it starts Team Win Recovery Project v2.6.0.1, when I boot from the phone being off it opens ClockworkMod Recovery v6.0.4.6) or bootloader. The internal storage is wiped. My PC is not able to install the device driver software, so I cannot put any files on the phone via USB cable. Also it appears to not be rooted, as the recoveries ask me if I want to install SuperSU. But if I accept this, nothing changes and the next time I get the same question.
All in all almost erverything on this phone is deleted and I have no idea how to put a ROM back on it to flash. Can anyone help me fix this?
Update: Trying out the USB-OTG-cable I get the error "E: Can't mount /storage/usbdisk"

krausebrause said:
Okay, so this is the status quo of my friends phone: HTC One M7 UL, S-On, HBOOT-1.55, TAMPERED, UNLOCKED
There is no OS instelled, I can only boot into recovery (while booting from the bootloader it starts Team Win Recovery Project v2.6.0.1, when I boot from the phone being off it opens ClockworkMod Recovery v6.0.4.6) or bootloader. The internal storage is wiped. My PC is not able to install the device driver software, so I cannot put any files on the phone via USB cable. Also it appears to not be rooted, as the recoveries ask me if I want to install SuperSU. But if I accept this, nothing changes and the next time I get the same question.
All in all almost erverything on this phone is deleted and I have no idea how to put a ROM back on it to flash. Can anyone help me fix this?
Click to expand...
Click to collapse
What errors do you have when installing drivers (adb) on your PC?

mb_guy said:
What errors do you have when installing drivers (adb) on your PC? Without a PC the only option would be a usb OTG cable, you could hopefully install a 4.3 OS as the recovery isn't new enough for KitKat
Click to expand...
Click to collapse
oh i ment just the ordinary windows "error"
trying adb out right now, never heard of it before
Update: I don't get how to use adb. Could you maybe tell me what to do? I get the respose "List of attached devices" and thats it, doesn't find any.

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.

Fastboot can't detect my unlocked device

Hi I have a problem where my pc does not detect my unlocked device in fastboot. This is a problem because I tried to update from global V10.3.3.0 to miui 11 but that did not work probably because there is not the right recovery on the device. So I can not get into the recovery and I can not get into the system this would of course be no problem because I can get into fastboot but my computer wont detect my device. How can I get my 9t pro to be detected in fastboot?
My device is unlocked. I did all that some time ago and it says so when I try to boot into system or recovery.
USB debugging is on. Idk if that is still there because I did try to update the system to miui11 but it was not detecting my phone in fastboot even before I did that update.
When I connected my phone to my computer when the system still worked I could use "adb devices" and that worked
I could also transfer files and stuff when my phone was connected to my laptop
So only when in fastboot my unlocked device is not detected if it was I could get back up there.
I really hope that this is some driver problem or something. Please help
Edit:
So at this point magically the system worked again! But I still can not use fastboot

I seem to have this problem:
https://forum.xda-developers.com/k20-pro/help/broken-fastboot-t3972697

Op3t bricked

HI there,
a few days ago I wanted to clean flash on my OP3T Havoc OS beta (the one based on Android 11) over the current stable Havoc OS based on Android 10. I ended up making a huge mistake wiping everything including system partition and data partition including Downloads and Personal Files. So now all I have left is a functioning TWRP recovery, an unlocked bootloader; the device is encrypted but has no OS on it! I don't have a backup. My main problem is I can't fastboot or adb the device - not on the black screen I get after the oneplus symbol during boot - and not in TWRP or Bootloader mode because the telephone is not recognized in device manager on my win 10 machine, same on another linux machine, the device is not recognized by adb or fastboot. Next thing I want to try is usb stick OTG and go from there.
Anyway, thanks for reading. Do you guys have any suggestions?

realtobman said:
...So now all I have left is a functioning TWRP recovery, an unlocked bootloader; the device is encrypted but has no OS on it! I don't have a backup. My main problem is I can't fastboot or adb the device - not on the black screen I get after the oneplus symbol during boot
...
Next thing I want to try is usb stick OTG and go from there.
Anyway, thanks for reading. Do you guys have any suggestions?
Click to expand...
Click to collapse
Using OTG is the way I'd go also if the phone isn't recognised by the PC.
You said your phone has an unlocked bootloader and that you get a black screen when the phone boots.
With an unlocked bootloader you should be getting the warning screen (see picture) which disappears after 5 seconds. And you should be able to select fastboot or recovery, etc by pressing the volume button.
Sent from my OnePlus 3T using XDA Labs

realtobman said:
HI there,
a few days ago I wanted to clean flash on my OP3T Havoc OS beta (the one based on Android 11) over the current stable Havoc OS based on Android 10. I ended up making a huge mistake wiping everything including system partition and data partition including Downloads and Personal Files. So now all I have left is a functioning TWRP recovery, an unlocked bootloader; the device is encrypted but has no OS on it! I don't have a backup. My main problem is I can't fastboot or adb the device - not on the black screen I get after the oneplus symbol during boot - and not in TWRP or Bootloader mode because the telephone is not recognized in device manager on my win 10 machine, same on another linux machine, the device is not recognized by adb or fastboot. Next thing I want to try is usb stick OTG and go from there.
Anyway, thanks for reading. Do you guys have any suggestions?
Click to expand...
Click to collapse
I'm having the same problem, did you manage to fix it?

My suggestion is that you purchase an OTG (bout $10++) then place any ROM inside. After that, flash it on your phone through TWRP. If that doesn't work and somehow your partitions are all messed up, there's always the unbrick method here: https://forum.xda-developers.com/t/op3t-latest-9-0-6-collection-of-unbrick-tools.3896765/

realtobman said:
HI there,
a few days ago I wanted to clean flash on my OP3T Havoc OS beta (the one based on Android 11) over the current stable Havoc OS based on Android 10. I ended up making a huge mistake wiping everything including system partition and data partition including Downloads and Personal Files. So now all I have left is a functioning TWRP recovery, an unlocked bootloader; the device is encrypted but has no OS on it! I don't have a backup. My main problem is I can't fastboot or adb the device - not on the black screen I get after the oneplus symbol during boot - and not in TWRP or Bootloader mode because the telephone is not recognized in device manager on my win 10 machine, same on another linux machine, the device is not recognized by adb or fastboot. Next thing I want to try is usb stick OTG and go from there.
Anyway, thanks for reading. Do you guys have any suggestions?
Click to expand...
Click to collapse
get a sd card please

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