Database Develop

Phone has no O/S installed, cannot detect phone to put rom zip on phone. please help

I believe I overwiped my phone, it has no rom on it now, and when I plug it into the computer, it makes the noise, but will not show up in windows explorer. I am able to boot into recovery, TRWN, although I can't do anything from there because I have no rom to install. I have tried installing the latest HTC drivers, using a different cord, disabling antivirus, pretty much everything previously listed in these forums. Is there a way to use the command prompt to send a rom over to the phone? Please help.

cburch85 said:
I believe I overwiped my phone, it has no rom on it now, and when I plug it into the computer, it makes the noise, but will not show up in windows explorer. I am able to boot into recovery, TRWN, although I can't do anything from there because I have no rom to install. I have tried installing the latest HTC drivers, using a different cord, disabling antivirus, pretty much everything previously listed in these forums. Is there a way to use the command prompt to send a rom over to the phone? Please help.
Click to expand...
Click to collapse
donwload the all in one toolkit use it to erase cache then install recovery. after that either mount usb otg and copy rom to sd or sideload a rom. all in one toolkit automates everything you need to do:good::good:

I wish I could say that worked, however when I try to use the AIO toolkit, when it launces the command prompt it says 'device not found.' same problem as windows. There has to be a way to force a file on there. Any ideas? Again, I can boot to recovery but have no zip on the phone memory to flash.

cburch85 said:
I wish I could say that worked, however when I try to use the AIO toolkit, when it launces the command prompt it says 'device not found.' same problem as windows. There has to be a way to force a file on there. Any ideas? Again, I can boot to recovery but have no zip on the phone memory to flash.
Click to expand...
Click to collapse
if it says device not found press the power button once and try again. it will say once in fastboot close the first window if you close the first window and nothing happens then press power and it should start
if your in fastboot options should be----bootloader----reboot----reboot bootloader----power down

skinsfanbdh said:
if it says device not found press the power button once and try again. it will say once in fastboot close the first window if you close the first window and nothing happens then press power and it should start
if your in fastboot options should be----bootloader----reboot----reboot bootloader----power down
Click to expand...
Click to collapse
Thanks for getting me this far. Mounting didn't work, so I sideloaded rom. it is showing up on the phone as "sideload.zip" i try to run and it fails. Any ideas?

Have you used this command?
Code:
adb sideload /path/to/rom.zip
If yes, it will work.
Maybe sideload.zip contains rom and if sideload.zip don't have meta-inf it will not flashed

Guich said:
Have you used this command?
Code:
adb sideload /path/to/rom.zip
If yes, it will work.
Maybe sideload.zip contains rom and if sideload.zip don't have meta-inf it will not flashed
Click to expand...
Click to collapse
I get it sideloaded and installed android revolution. however, when I'm done installing the rom, trwn tells me "superuser is not installed, would you like to install now?" I say yes and then the phone goes blank, and reboots to bootloader. Any ideas?

cburch85 said:
I get it sideloaded and installed android revolution. however, when I'm done installing the rom, trwn tells me "superuser is not installed, would you like to install now?" I say yes and then the phone goes blank, and reboots to bootloader. Any ideas?
Click to expand...
Click to collapse
im guessing your using twrp but just select no dont root the rom is already rooted and it should boot. may take getting through a few aroma freezes but it will boot

cburch85 said:
I get it sideloaded and installed android revolution. however, when I'm done installing the rom, trwn tells me "superuser is not installed, would you like to install now?" I say yes and then the phone goes blank, and reboots to bootloader. Any ideas?
Click to expand...
Click to collapse
Change the rom or don't say yes when you have the question
Sent from ONE with Tapa4 Beta

Guich said:
Change the rom or don't say yes when you have the question
Sent from ONE with Tapa4 Beta
Click to expand...
Click to collapse
OK, so I didn't say yes to the question this time after sideloading android revolution. same thing. goes blank then reboots to bootloader menu. So I tried sideloading viperrom 1.04. This time after it finished sideloading it randomly installed instelfl, and now viperrom is installed, its booting up to the phone now finally, yet before anything can initialize, it just reboots again. It's been caught in this boot loop about ten minutes now. No end in sight. Any ideas?

ViperRom from Sprint or AT&T one forum?
Your phone is branded or no-brand?
However, boot into recovery, and use this command:
Code:
adb push name_of_rom.zip /sdcard
, then flash it

Also, I have now tried flashing and installing TrickDroid which also boots to the O/S but then after a few seconds reboots and starts all over again. I just let it run, and it boots, then reboots, over, and over, and over again. Any ideas?

cburch85 said:
Also, I have now tried flashing and installing TrickDroid which also boots to the O/S but then after a few seconds reboots and starts all over again. I just let it run, and it boots, then reboots, over, and over, and over again. Any ideas?
Click to expand...
Click to collapse
Have you tried to flash the boot.img from fastboot?

I fixed it!!! I had to download the latest RUU for the HTC One. I ran the RUU after relocking, and then started the root process from scratch. RUU is the only thing that would work. Also, the best rom I have gotten to work for sprint is ViperRom, TrickDroid installed and booted but the camera wouldnt work. Thanks for the help and suggestions!

cburch85 said:
I fixed it!!! I had to download the latest RUU for the HTC One. I ran the RUU after relocking, and then started the root process from scratch. RUU is the only thing that would work. Also, the best rom I have gotten to work for sprint is ViperRom, TrickDroid installed and booted but the camera wouldnt work. Thanks for the help and suggestions!
Click to expand...
Click to collapse
Where did you find the RUU for sprint? I cant seem to find one that works with my CID: SPCS_001.

Hey, im having the same problem. I have nothing on my phone, not even root. I cant use adb commands but fastboot seems to work. Im using TWRP 2.6.3 recovery. If anyone can help that would be awesome!!

zach832 said:
Hey, im having the same problem. I have nothing on my phone, not even root. I cant use adb commands but fastboot seems to work. Im using TWRP 2.6.3 recovery. If anyone can help that would be awesome!!
Click to expand...
Click to collapse
Reflash the latest TWRP and check if adb work.
Becuase without it you can't push/sideload a rom...

Can't detect SD Card
Guich said:
Reflash the latest TWRP and check if adb work.
Becuase without it you can't push/sideload a rom...
Click to expand...
Click to collapse
Hi, I'm having sort of the same problem. My phone is stuck on a bootloop, I flashed a new recovery because the previous TWRP stopped working. When I try to wipe data/factory reset, It says that it can't detect E:\ or the SD Card. I can't even mount it. Any ideas? Please help. Thanks

[Q] Sprint One, can only access hboot and recovery

I feel like I have used up all my resources on trying to get my Sprint HTC One back to stock.
Last night I was able to unlock it with no trouble. I didn't realize this would wipe out all my media as well. (not the issue)
So I was going to go and install Benny's Cleanrom and I used Superwipe to clear all the cache and everything that was being restored from the back up. I flashed the Superwipe Rom and it seemed to have gotten the job done, but it also wiped out my OS.
So now I have been stuck with the ability of accessing bootloader and recovery, I am using TWRP right now. None of my pc's recognize my phone when I try to mount it. The phone also shows errors when I try to do so, coming up stating that it cannot mount anything except usb otg. I don't have a USB OTG cable right to use, so that option is still out the window.
I have tried this method
I have tried this method multiple times but ADB was not working. http://forum.xda-developers.com/showthread.php?t=2317989
I have tried the Fastboot method, which had me relocking the phone and running the ruu. Though since I am on the latest version 1.3, the 1.2.9 RUU I was trying to use kept on failing. When doing it through Hasoon's AIO tool it seems that the ruu works when I flash the ruu zip. Though running it the first time it would show up that it failed, but when I re-flash it the second time on the cmd line it shows successful though on the phone the green bar never completes it and it stays at like 95% and doesn't complete the install on the phone.
If someone knows how to get my phone back to stock I would be very appreciative. I am new to rooting on the HTC One, I previously rooted my Evo 3D and my girls SG2.
If someone wants to help me out with team viewer, I will gladly allow anyone to assist me in that matter. I am just hoping that this can be resolved.

Now I see when I type ADB devices in cmd, it shows FA33ZS907479 recovery. I don't know if this has any relevance in that it sees the TWRP recovery.
BiGsMiLeSKyLe said:
I feel like I have used up all my resources on trying to get my Sprint HTC One back to stock.
Last night I was able to unlock it with no trouble. I didn't realize this would wipe out all my media as well. (not the issue)
So I was going to go and install Benny's Cleanrom and I used Superwipe to clear all the cache and everything that was being restored from the back up. I flashed the Superwipe Rom and it seemed to have gotten the job done, but it also wiped out my OS.
So now I have been stuck with the ability of accessing bootloader and recovery, I am using TWRP right now. None of my pc's recognize my phone when I try to mount it. The phone also shows errors when I try to do so, coming up stating that it cannot mount anything except usb otg. I don't have a USB OTG cable right to use, so that option is still out the window.
I have tried this method
I have tried this method multiple times but ADB was not working. http://forum.xda-developers.com/showthread.php?t=2317989
I have tried the Fastboot method, which had me relocking the phone and running the ruu. Though since I am on the latest version 1.3, the 1.2.9 RUU I was trying to use kept on failing. When doing it through Hasoon's AIO tool it seems that the ruu works when I flash the ruu zip. Though running it the first time it would show up that it failed, but when I re-flash it the second time on the cmd line it shows successful though on the phone the green bar never completes it and it stays at like 95% and doesn't complete the install on the phone.
If someone knows how to get my phone back to stock I would be very appreciative. I am new to rooting on the HTC One, I previously rooted my Evo 3D and my girls SG2.
If someone wants to help me out with team viewer, I will gladly allow anyone to assist me in that matter. I am just hoping that this can be resolved.
Click to expand...
Click to collapse

BiGsMiLeSKyLe said:
Now I see when I type ADB devices in cmd, it shows FA33ZS907479 recovery. I don't know if this has any relevance in that it sees the TWRP recovery.
Click to expand...
Click to collapse
Check pm :thumbup:
Sent from my HTCONE using xda app-developers app

I need help too
bigdaddy619 said:
Check pm :thumbup:
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Im having the same problem I have nothing on my phone and adb sideload wont work and I also tried the RUU and I have the .31 version so i can't use it either

rj54271 said:
Im having the same problem I have nothing on my phone and adb sideload wont work and I also tried the RUU and I have the .31 version so i can't use it either
Click to expand...
Click to collapse
I work weird hours so if you can wait and I'll help or you can try to do it yourself look here Q21

[Q] Emergency! NEED HELP IMEDIATELY!!

Ok so how do I start this? Well I got an htc one for christmas and I wanted to root it. Everything was fine until I decided to flash a custom kit kat rom. The rom was stuck in a boot loop so I went back to twrp and flashed my recovery. I thought I fixed everything but then I stopped getting phone service. It kept saying looking for service. I thought it was a bad recovery so I downloaded cm from rom manager. While it was downloading, the phone just randomly rebooted. It kept doing this and still is.so then, being the idiot I am, flashed clockwork recovery to see if it would change anything. I tried downloading cm from rom manager again and finally finished downloading before it started rebooting again. I went into clockwork recovery and flashed cm and now it keeps rebooting and I have no phone service. I have no idea what to do. By switching from twrp to clockwork, I lost my recovery. Im totally screwed. I need help please!What do I do!!!!????

Run an RUU to fix and only flash roms that are made for Sprint or have Sprint support.
Sounds like you flashed a GSM rom that's why everything is jacked up.

BD619 said:
Run an RUU to fix and only flash roms that are made for Sprint or have Sprint support.
Sounds like you flashed a GSM rom that's why everything is jacked up.
Click to expand...
Click to collapse
Thanks a bunch! I'll check this out and see if it works

Rom Update Utility
It will get you back to 100% stock
If you need help PM me I'll be happy to help

roflcopter1212 said:
Ok so how do I start this? Well I got an htc one for christmas and I wanted to root it. Everything was fine until I decided to flash a custom kit kat rom. The rom was stuck in a boot loop so I went back to twrp and flashed my recovery. I thought I fixed everything but then I stopped getting phone service. It kept saying looking for service. I thought it was a bad recovery so I downloaded cm from rom manager. While it was downloading, the phone just randomly rebooted. It kept doing this and still is.so then, being the idiot I am, flashed clockwork recovery to see if it would change anything. I tried downloading cm from rom manager again and finally finished downloading before it started rebooting again. I went into clockwork recovery and flashed cm and now it keeps rebooting and I have no phone service. I have no idea what to do. By switching from twrp to clockwork, I lost my recovery. Im totally screwed. I need help please!What do I do!!!!????
Click to expand...
Click to collapse
Try this tutorial from BD619 http://forum.xda-developers.com/showthread.php?t=2503646&highlight=tutorial

roflcopter1212 said:
Thanks a bunch! I'll check this out and see if it works
Click to expand...
Click to collapse
I tried it with your tut. but when I try to reboot into RUU it says fastboot isnt a valid win. 32bit application. What now?

BD619 said:
Run an RUU to fix and only flash roms that are made for Sprint or have Sprint support.
Sounds like you flashed a GSM rom that's why everything is jacked up.
Click to expand...
Click to collapse
I put in the failed 90 hboot.... command and it says its an invalid command

roflcopter1212 said:
I put in the failed 90 hboot.... command and it says its an invalid command
Click to expand...
Click to collapse
You *have* to get your Android SDK setup properly. All the commands your run end up on "command not found" of "invalid exe" and that suggests a few things:
First -- make *sure* you install the correct SDK for your computer. If you can't find them, let us know what your computer is (32-bit, 64-bit, windows, etc.). Further, it seem possible:
1) You did not yet install the Android SDK (or ADT bundle if that's what you grab);
2) If just the SDK, you did not run the 'android' app and let it update all the platform-tools apps (that's adb, fastboot, etc);
3) You did not open a command shell in the <sdk>/platform-tools directory, or you did not add your <sdk>/tools and <sdk>/platform-tools to your path. Further:
Finally -- make sure you have your USB drivers loaded if you're using Windows.
Don't run 300 miles per hour trying to fix things -- it'll kill your phone. Relax, take a breath and get the SDK setup. That will solve most of your problems (if not all). At least that's what it looks like from afar.
Before you run any of the RUU, you should be able to type either of:
adb devices
or
fastboot devices
The latter works only when you are at the bootloader with your USB plugged in and you selected 'fastboot'; the former runs only when your phone is booted fully.

The Sprint 3.05.651.5 RUU is available here: http://www.htc.com/us/support/htc-one-sprint/news/ (Install at your own risk!)

[Q] sideloading of 5.0.1 OTA fails

Okay, I have the Nexus 6 (T-Mobile), rooted stock. I also have the Nexus 10. On both, I tried to sideload the 5.0.1 OTA update... and it failed in the exact same manner.
Obviously, I'm doing something wrong, but I have no idea what.
I did the Nexus 10 on a Windows 7 box, and I'm trying the Nexus 6 on a Linux machine. Same. Exact. Problem.
What I'm doing is this:
adb reboot bootloader
Arrow up to recovery, hit the power button to select
Hold down the power button and press the up button
Select "Sideload from ADB" (can't remember the exact wording, but basically, that)
adb sideload <verylongfilename.zip>
The update starts... and gets to 48% on my computer, and then ends. (I don't mean that it pauses or hangs, I mean it "finishes" -- it's done and back at the prompt). On the phone, at that time, it says "system has been remounted r/w; reflash device to reenable ota updates"
So that's where I'm at. On my Nexus 10, I ended up wiping it and just doing the full stock image install to get 5.0.1 -- that worked fine. On my phone, though, I really don't want to lose my entire setup just to get the bump from 5.0 to 5.0.1.
Can anyone tell me what the heck I'm doing wrong? It has to be something I'm doing or something I have configured wrong or ... I don't know. But the process clearly works for many, many people, and the fact that I have the same problem with two different devices on two different computers... it has to be my process, or something I've done to my devices.
Both devices are rooted stock, with stock recovery.
Any help you guys can provide would be greatly appreciated!!

you cant update it via your phone. you need to flash the update via fastboot, while you are in your bootloader.

simms22 said:
you cant update it via your phone. you need to flash the update via fastboot, while you are in your bootloader.
Click to expand...
Click to collapse
Right, I'm not trying to do it from my phone, I'm doing it from my computer. What am I doing wrong with my adb sideload process?

commonplace said:
Right, I'm not trying to do it from my phone, I'm doing it from my computer. What am I doing wrong with my adb sideload process?
Click to expand...
Click to collapse
then why are you trying to sideload it???
download it via your computer, extract the files from the zip, boot your phone into the bootloader, connect it to your computer, run fastboot devices(to make sure that the computer sees your device, then run the flash-all script.

simms22 said:
then why are you trying to sideload it???
download it via your computer, extract the files from the zip, boot your phone into the bootloader, connect it to your computer, run fastboot devices(to make sure that the computer sees your device, then run the flash-all script.
Click to expand...
Click to collapse
I was following directions found elsewhere (AndroidCentral and another site). I see now that adb sideload is not the answer, and that fastboot flash IS.
Phone = upgraded. Thanks for steering me in the right direction!

I had rooted 5.0 and read on Google+ that update over the air would not work. I used this guide to update to 5.0.1 and lost no data, nor had to reinstall anything.
http://forum.xda-developers.com/nexus-6/help/help-5-01-wipe-t2970924

OnePlus 3T full wiped, not able to flash a new ROM via ADB

I wanted to go back from Oxygen OS 5 to 4. And started with making a full wipe, data and system. Now I know that was my mistake. But I did it anyways because it worked the same way before as i upgraded to Oxygen OS Beta xx (An Oreo one).
For refreshing 1I did go trough some tutorials but the process was how I remembered it. I did not change the computer or reseted it since the last time. So I was confidend I still got everthing istalled properly. Driver for my OnePlus 3T seemed to have been installed, too, because I drag&dropped the files I wanted to save on my computer from my OP3T priviously.
But then I starttyped everything in cmd this came up. https://i.imgur.com/Zmo1qeD.png?1
Here is the Installation Folder of ADB with the new Rom inside: https://i.imgur.com/9RD20Ac.png
I already tried this workaround: https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
As I researched on my own the idea came to my mind that adb/windows does not recognize my device. This thing is listed in my device manager: https://i.imgur.com/VO86zuw.png
Thank you in advance! Hope u guy can help me.
Edit: After some digging depper I think I found my mistake. ADB only works when the devices is booted into OS. Which is not possible anymore for me. Now I need to find a way around that.....

You will need a recovery for adb sideload. Easiest is to use twrp, first flash twrp, and when in twrp click on sideload so the device is able to receive the files. If you are trying to sideload stock rom, you can also flash stock recovery and click sideload from there.
I guess you are now trying to sideload a rom in fastboot mode?
Edit: excuse me, i think i misunderstood you.

knijntjes said:
You will need a recovery for adb sideload. Easiest is to use twrp, first flash twrp, and when in twrp click on sideload so the device is able to receive the files. If you are trying to sideload stock rom, you can also flash stock recovery and click sideload from there.
I guess you are now trying to sideload a rom in fastboot mode?
Edit: excuse me, i think i misunderstood you.
Click to expand...
Click to collapse
At the moment I am trying to find a way to install TWRP without an OS installed and OEM locked. In research I recognized this as the easiest way to install a new ROM. The only thing I need TWRP now.

If I were you, I'd flash the phone using the unbrick method and unlock the bootloader, so you won't lock yourself out in the future

TaddyQuup said:
I wanted to go back from Oxygen OS 5 to 4. And started with making a full wipe, data and system. Now I know that was my mistake. But I did it anyways because it worked the same way before as i upgraded to Oxygen OS Beta xx (An Oreo one).
For refreshing 1I did go trough some tutorials but the process was how I remembered it. I did not change the computer or reseted it since the last time. So I was confidend I still got everthing istalled properly. Driver for my OnePlus 3T seemed to have been installed, too, because I drag&dropped the files I wanted to save on my computer from my OP3T priviously.
But then I starttyped everything in cmd this came up. https://i.imgur.com/Zmo1qeD.png?1
Here is the Installation Folder of ADB with the new Rom inside: https://i.imgur.com/9RD20Ac.png
I already tried this workaround: https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
As I researched on my own the idea came to my mind that adb/windows does not recognize my device. This thing is listed in my device manager: https://i.imgur.com/VO86zuw.png
Thank you in advance! Hope u guy can help me.
Edit: After some digging depper I think I found my mistake. ADB only works when the devices is booted into OS. Which is not possible anymore for me. Now I need to find a way around that.....
Click to expand...
Click to collapse
This might help:
http://www.oneplusbbs.com/thread-3203158-1-1.html
I can translate this for you if you need.

You need to flash a special build of Oreo beta to be a more to downgrade to Nougat according to the thread here below.
https://forums.oneplus.net/threads/guide-how-to-go-from-oreo-to-stock-nougat.661713/
But since you've deleted everything your best bet now is the Qualcomm factory restore recover method.
https://www.google.se/amp/s/forum.x...ick-unbrick-tutorial-oneplus-3t-t3515306/amp/

TaddyQuup said:
I wanted to go back from Oxygen OS 5 to 4. And started with making a full wipe, data and system. Now I know that was my mistake. But I did it anyways because it worked the same way before as i upgraded to Oxygen OS Beta xx (An Oreo one).
For refreshing 1I did go trough some tutorials but the process was how I remembered it. I did not change the computer or reseted it since the last time. So I was confidend I still got everthing istalled properly. Driver for my OnePlus 3T seemed to have been installed, too, because I drag&dropped the files I wanted to save on my computer from my OP3T priviously.
But then I starttyped everything in cmd this came up. https://i.imgur.com/Zmo1qeD.png?1
Here is the Installation Folder of ADB with the new Rom inside: https://i.imgur.com/9RD20Ac.png
I already tried this workaround: https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
As I researched on my own the idea came to my mind that adb/windows does not recognize my device. This thing is listed in my device manager: https://i.imgur.com/VO86zuw.png
Thank you in advance! Hope u guy can help me.
Edit: After some digging depper I think I found my mistake. ADB only works when the devices is booted into OS. Which is not possible anymore for me. Now I need to find a way around that.....
Click to expand...
Click to collapse
Some things you've missed:
1. Your first screenshot shows that ADB connects successfully to your phone because it shows the device ID. So drivers and ADB are ok.
2. ADB reads files from the directory it is invoked in. Your command shell is starting in c:/windows/system, so that's the directory ADB is looking in for OP.zip. you can either cd to the correct directory or specify the full path of the OP.zip file.
So, if you reboot your phone into recovery and select install from ADB then start ADB and verify its connected then run the sideload command pointing to the correct director it should flash the ROM successfully.
Sent from my OnePlus3T using XDA Labs