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] got a soft brick after a build.prop edit

A while earlier I was trying to enable tethering on my at&t N6 by editing the build.prop and after the reboot it's stuck in a boot loop. I don't imagine that this is important but it doesn't get to the dots animation; just white Google and the unlock at the bottom. I am still able to get into fastboot and recovery (stock one). I have a backup of the correct build.prop in the /system file named build.prop.back , so I'm hoping that there's a way to revert to that without needing to wipe my device again, but I'm not sure.
I found this thread, however my computer isn't recognizing the device when it's in recovery mode. I have the fastboot drivers installed (needed to root), so that may be why but, again, I'm not sure. the adb devices command shows that there is no device, I imagine because the driver is not installed.
any help would be appreciated. thanks in advance.

Try the ADB & Fastboot installer from this thread - http://forum.xda-developers.com/showthread.php?t=2588979

jj14 said:
Try the ADB & Fastboot installer from this thread - http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Unfortunately that didn't fix the problem.
Do you know if the fastboot driver and recovery driver would be different? As far as I can tell from my research, I think they're the same, but I could be wrong. Hopefully that's the problem and you can direct me towards the correct driver.
If I select "show hidden devices" in the device manager, it shows the phone as ADB Interface, and I tried undating the driver for that but it said it was already up to date. not sure what to do from here.
Thanks for your help.

Install working drivers if you can. This is important on so many levels. If they are installed correctly you type ADB devices, you should see your device. If you do type adb reboot bootloader, it should reboot to bootloader. Type fastboot devices, you should see same device name. Pat self on back.
Once that is all good I'd install the latest TWRP img file for your whale, straight off TWRP website (do you know how to do this? fastboot flash recovery recovery/name.img) . Once you do that go to your new recovery by pushing vol-down twice then your power button, inside TWRP you mount system and go into the file manager inside TWRP and swap/rename build.prop files. At this point, please make a backup inside TWRP. This backup will be on your internal memory, also save a copy to your computer in case you accidentally reformat your internal memory like every noob that uses toolkits. Having a backup is very important when you are screwing around with your phone. Reboot and profit.

jawmail said:
Install working drivers if you can. This is important on so many levels. If they are installed correctly you type ADB devices, you should see your device. If you do type adb reboot bootloader, it should reboot to bootloader. Type fastboot devices, you should see same device name. Pat self on back.
Once that is all good I'd install the latest TWRP img file for your whale, straight off TWRP website (do you know how to do this? fastboot flash recovery recovery/name.img) . Once you do that go to your new recovery by pushing vol-down twice then your power button, inside TWRP you mount system and go into the file manager inside TWRP and swap/rename build.prop files. At this point, please make a backup inside TWRP. This backup will be on your internal memory, also save a copy to your computer in case you accidentally reformat your internal memory like every noob that uses toolkits. Having a backup is very important when you are screwing around with your phone. Reboot and profit.
Click to expand...
Click to collapse
I though I had the working drivers... Whenever I boot into fastboot/ bootloader, I can do fastboot devices and the phone shows up, but for whatever reason adb devices returns an empty list everywhere. It's empty in fastboot and recovery and while the phone is stuck in it's bootloop...
I'm fairly confident I can flash TWRP without any problems. I had an old galxy tab 2 that i flashed cyanogen onto a while ago, however i used clockwork for that recovery. I don't imagine it would be too much different though.
edit: also might be worth noting that I'm using a windows 8.1 computer for this. not sure if it matters or not, but it might be useful

momo5732 said:
I though I had the working drivers... Whenever I boot into fastboot/ bootloader, I can do fastboot devices and the phone shows up, but for whatever reason adb devices returns an empty list everywhere. It's empty in fastboot and recovery and while the phone is stuck in it's bootloop...
I'm fairly confident I can flash TWRP without any problems. I had an old galxy tab 2 that i flashed cyanogen onto a while ago, however i used clockwork for that recovery. I don't imagine it would be too much different though.
edit: also might be worth noting that I'm using a windows 8.1 computer for this. not sure if it matters or not, but it might be useful
Click to expand...
Click to collapse
You are ok w/ your problem because you can get to fastboot screen. Don'y worry about adb drivers for now. Do what I said in my earlier post in the 2nd paragraph, start w/ installing TWRP img then do the rest and it will work for you. Win 8.1 seems to have its difficulties but we'll worry about that later after you get TWRP installled.

jawmail said:
You are ok w/ your problem because you can get to fastboot screen. Don'y worry about adb drivers for now. Do what I said in my earlier post in the 2nd paragraph, start w/ installing TWRP img then do the rest and it will work for you. Win 8.1 seems to have its difficulties but we'll worry about that later after you get TWRP installled.
Click to expand...
Click to collapse
OK. twrp is making a backup as I type. is this backup the same thing as a nandroid backup? i hadnt heard of them before I decided to root.
It should boot properly now. I'll update when it's done.
Edit: IT BOOTS! thank you so much.
Edit 2: So I'm not really sure why it works now but adb recognizes it when its in twrp... odd. I tried to reinstall the drivers with the most recent version i could find, but it didn't look like it actually updated anything. maybe stock recovery was just broken? I'm not sure...

momo5732 said:
OK. twrp is making a backup as I type. is this backup the same thing as a nandroid backup? i hadnt heard of them before I decided to root.
It should boot properly now. I'll update when it's done.
Edit: IT BOOTS! thank you so much.
Edit 2: So I'm not really sure why it works now but adb recognizes it when its in twrp... odd. I tried to reinstall the drivers with the most recent version i could find, but it didn't look like it actually updated anything. maybe stock recovery was just broken? I'm not sure...
Click to expand...
Click to collapse
Cool glad it's working. Yes backup=nandroid
It's cool now I've also noticed the computer recognizes phone in TWRP. You can drag and drop files onto the phone while it's in TWRP not just booted in android, couldn't do that before unless I'm wrong which is often. This is really cool as I always forget a file or two or its location on SD card.

Cant boot properly after twrp succeeded to install, mes - shuts itself of after 5 sec

Recently on linux I unlocked the bootloader which worked out nicely. I also proceeded with installing twrp after reading that other users had succeed in installing it. I used adb through the terminal, I can confirm from the terminal twrp was successfully installed I had no errors. But when I restarted the phone I got this message: "Your device is corrupt it cant be trusted and will not boot. Your device will be powered off in 5 seconds. ".
If I did not use the recommended command from Somcom3X the twrp install would fail. I cant not boot my phone but I can enter flashboot when I connect my phone to my computer. Now when I enter flashboot and enter adb devices in the terminal my device does not show up. There has to be something that can be done through flashboot to solve this problem.
https://forum.xda-developers.com/essential-phone/help/partition-t3733811

Flash stock firmware with flashtool if device is detected.
If not try to flash fota kernel only in recovery partition.
Envoyé de mon H8266 en utilisant Tapatalk

Root after flashing TWRP or it will not boot i guess

niaboc79 said:
Flash stock firmware with flashtool if device is detected.
If not try to flash fota kernel only in recovery partition.
Envoyé de mon H8266 en utilisant Tapatalk
Click to expand...
Click to collapse
The device doe not get detected at all through the terminal, I have tried with windows 10 as well it does not find device with adb devices there either. I can not enter recovery mode when I press volume down and power on for a few seconds it just vibrates and will not turn on. But if I press the power button like normal the same corrupted message comes up. I have tried getting it detected on windows 10 have not had any success yet. Can driver Driver Signature in win 10 cause that device will not get detected.

Bofahad said:
Root after flashing TWRP or it will not boot i guess
Click to expand...
Click to collapse
This cant be right I have flashed TWRP many times before and succeed on Galaxy S3, Galaxy S3 GT-I9300, and LG G4. I have never had a problem like this before that I need to root after flashing TWRP.

I hope that not a new "security feature" of the new Sony flagship...
Which hardware revision do you own?

MartinX3 said:
I hope that not a new "security feature" of the new Sony flagship...
Which hardware revision do you own?
Click to expand...
Click to collapse
Currently the xz2. I find it really strange how TWRP did not get flashed correctly when there was no error in the terminal. Doing the flashing in linux should also work. I have always flashed TWRP after unlocking the bootloader before when I did it on Galaxy S3, Galaxy S3-GTI9300, and LG G4.
My xz2 is now being detected as an android device now in the device manager at least there is some progress. I had to go back to Windows 7 now and install adb and the android driver. When I now try to update the driver in device manager in other devices under android it fails.
https://forum.xda-developers.com/crossdevice-dev/sony/minitut-installing-adb-drivers-sony-t3185585
I would think this driver would work in windows 7 but maybe only 10. Does disabling driver signature in 10 have any effect.
https://developer.sony.com/develop/drivers/

EternalSwift said:
I also proceeded with installing twrp...
Click to expand...
Click to collapse
Where did you get xz2 twrp from?
As for your issue, I don't know if that helps out, but at least in xperia xa2, which also has new treble partition design (A/B), official twrp installation (boot/flashing) is kinda different, see here!

That's because of A/B partitioning we don't need recovery partition anymore right?
But hasn't Sony always had some issues with the recovery partition that's why we used fota recovery back in the days?

Haldi4803 said:
That's because of A/B partitioning we don't need recovery partition anymore right?
But hasn't Sony always had some issues with the recovery partition that's why we used fota recovery back in the days?
Click to expand...
Click to collapse
No, Sony hadn't issues with it.
They implemented the recovery into the boot image directly on the Xperia devices.
That has nothing to do with the alpha beta partitions.
I also work at the moment on twrp for the xz2.
I think I collected the right drivers and fstab and so on, but still need to try how to compile it with the synced Omni sources.

EternalSwift said:
Recently on linux I unlocked the bootloader which worked out nicely. I also proceeded with installing twrp after reading that other users had succeed in installing it. I used adb through the terminal, I can confirm from the terminal twrp was successfully installed I had no errors. But when I restarted the phone I got this message: "Your device is corrupt it cant be trusted and will not boot. Your device will be powered off in 5 seconds. ".
If I did not use the recommended command from Somcom3X the twrp install would fail. I cant not boot my phone but I can enter flashboot when I connect my phone to my computer. Now when I enter flashboot and enter adb devices in the terminal my device does not show up. There has to be something that can be done through flashboot to solve this problem.
https://forum.xda-developers.com/essential-phone/help/partition-t3733811
Click to expand...
Click to collapse
Can you test this twrp build for me?
https://forum.xda-developers.com/xp...recovery-twrp-3-2-2-0-touch-recovery-t3821597

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.

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