Hi, to all.
I know that this has been ask many times,but....
I did search and try almost a every solution i could find on XDA fórum.
I did i complete wipe and voilá, no OS on my Droid DNA, i was rooted but on S-ON, and i had the Venon 3.0.1
I was installing the new Viper 3.1.0 but did the full system wip,and now only can acess my Bootloader and Recovery (TWRP).
Also when rebboting or turning off from recovery it says that there's no root app instaled,and try's to install but it can find it.
I can connect to fastboot, but no adb (when i do adb devices it shows a blank on the device) but on Fastboot it shows the device number.
I try to upgrade drivers and android adb /fastboot, but no luck, in sideload or push the Rom to the phone.
Also i can navigate on the recovery, and try to mount system etc,but also with no luck.
I tryed on Linux and Windows 8, but still no luck.
I'm trying right now another thing that i found on this question and answer thread (that is install pdaneta4126) but still nothing.
Can anyone provide me some insight or light on this matter?
I know that if i have acess to recovery not all is lost, so after a lot of fight and banging with my head, i would like some assistance if it would be possible)
I'm rooted since the 1.15 and didn´t upgrade Hboot or Radios, if this helps and i was in TWRP 2.63, but now flashed 2.7.
Or can i RUU back to stock, and re-root, or what i can do to solve this?
Thank you for all the help you can give me.
sued said:
Hi, to all.
I know that this has been ask many times,but....
I did search and try almost a every solution i could find on XDA fórum.
I did i complete wipe and voilá, no OS on my Droid DNA, i was rooted but on S-ON, and i had the Venon 3.0.1
I was installing the new Viper 3.1.0 but did the full system wip,and now only can acess my Bootloader and Recovery (TWRP).
Also when rebboting or turning off from recovery it says that there's no root app instaled,and try's to install but it can find it.
I can connect to fastboot, but no adb (when i do adb devices it shows a blank on the device) but on Fastboot it shows the device number.
I try to upgrade drivers and android adb /fastboot, but no luck, in sideload or push the Rom to the phone.
Also i can navigate on the recovery, and try to mount system etc,but also with no luck.
I tryed on Linux and Windows 8, but still no luck.
I'm trying right now another thing that i found on this question and answer thread (that is install pdaneta4126) but still nothing.
Can anyone provide me some insight or light on this matter?
I know that if i have acess to recovery not all is lost, so after a lot of fight and banging with my head, i would like some assistance if it would be possible)
I'm rooted since the 1.15 and didn´t upgrade Hboot or Radios, if this helps and i was in TWRP 2.63, but now flashed 2.7.
Or can i RUU back to stock, and re-root, or what i can do to solve this?
Thank you for all the help you can give me.
Click to expand...
Click to collapse
Can you get into recovery and sideload a rom to install?
RLGL said:
Can you get into recovery and sideload a rom to install?
Click to expand...
Click to collapse
I can go to the recovery, and connect the sideload, but the Linux and the Windows 8 but when i try to adb sideload viperDNA.zip to the internal storage, it just says "error device not found"
But if i do in fastboot (fastboot devices) the pc detects and returns the number.
In adb (adb devices) the system returns a blank space where it should be the device number.
Also i unable to push a file to sdcard.
Try this thread::: Even if you have accidentally formatted your internal storage and you have no files on your phone, this section is down the bottom of the thread. Only follow this if you have no access to your phone and have nothing installed on your sdcard. For everybody else simply follow from step 1.
above is an excerpt from the text.
sued said:
I can go to the recovery, and connect the sideload, but the Linux and the Windows 8 but when i try to adb sideload viperDNA.zip to the internal storage, it just says "error device not found"
But if i do in fastboot (fastboot devices) the pc detects and returns the number.
In adb (adb devices) the system returns a blank space where it should be the device number.
Also i unable to push a file to sdcard.
Click to expand...
Click to collapse
Download PdaNet and it will reinstall your adb drivers and you should be able to find your device.
Adb push can push a rom to the phone and then just flash it and your good.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Related
Hello
i managed to unlock my bootloader, flashed twrp recovery, flashed super user.
Tried to install dirty unicorn and got status 7 error.
And now i dont have a rom/os installed.
I tried to move over .zip files through twrp but cant mount drives.
Any help?!?
I TRIED TO PUSH ZIP WITH SIDELOAD AND NO LUCK
BUMP!
i really need to get this fixed please help
xr1charxx said:
BUMP!
i really need to get this fixed please help
Click to expand...
Click to collapse
I did the same thing yesterday, as it was my first time using TWRP (always been a CWM guy), All you have to do to fix it is go into advanced and go into adb sideload, put your rom in you adb folder and run this command
adb sideload nameofzip.zip
Then the zip will be placed in internal storage named sideload.zip and you can flash it.
dsf767 said:
I did the same thing yesterday, as it was my first time using TWRP (always been a CWM guy), All you have to do to fix it is go into advanced and go into adb sideload, put your rom in you adb folder and run this command
adb sideload nameofzip.zip
Then the zip will be placed in internal storage named sideload.zip and you can flash it.
Click to expand...
Click to collapse
Already tried this. when i run adb devices my device does not show up. and when i try to sideload any files i get error:closed
xr1charxx said:
Already tried this. when i run adb devices my device does not show up. and when i try to sideload any files i get error:closed
Click to expand...
Click to collapse
I would try to plug in the USB after your already in recovery.
If you cant get that to work you can always buy this:
https://shopmeenova.appspot.com/st/order.html
its a microusb to microsd its a good worst case and will get you up and running.
do you still have the rom that errored out on you on your internal storage? if so you can always try a fresh wipe and try to install again.
Alright lads, I got a major issue that is kicking my ass. I need your help please.
Basically the HTC ONE X+ keeps getting error closed in ADB sideload whenever I try to sideload a rom or do anything else for the matter.
adb usb = Error Closed
Adb push and pull = Error Closed.
I can get my device listed but thats about it.
The Issue goes further. I relocked the bootloader in order to install the RUU. Yet I get the error 131 custormer ID error.
I can't access the SD partition on the my computer screen as it doesn't show.
I can't get back to stock rom.
I can't install a new rom.
I can unlock and relock my bootloader.
I can install TWRP and CWM.
I can use fastboot usb. [Very limited]
The issue with fastboot usb is that it keeps saying error device not found and then it refuses to do anything.
I have installed and reinstalled the ADB drivers, SDK manager and htc sync manager.
The biggest issue at the moment is that I can't install any rom whatsoever.
Which basically means, its a potato.
HALLLLP. The htc one x is a international version. UK Vodafone more specifically. Hboot-1.35.0000
Oh yeah, the mount does not work in TWRP and CWM.
I tried different USB ports, cables and even a different computer.
Everything has been wiped. I factory reset it and wiped out other parts in TWRP and CWM in an effort to start from scratch.
Nothing seems to work though...
Edit: I narrowed down the issue
It seems that i can't flash boot.img when my bootloader is unlocked as:
'boot.img'...FAILED (command write failed (Unknown error))
therefore I can't load roms without it crashing on me.
I can however put things into the 'sd card' by loading a broken rom [crashes to process android]. But thats about it. so far.
Oh I also updated the hboot to 1.72
NinjaKenZen said:
Alright lads, I got a major issue that is kicking my ass. I need your help please.
Basically the HTC ONE X+ keeps getting error closed in ADB sideload whenever I try to sideload a rom or do anything else for the matter.
adb usb = Error Closed
Adb push and pull = Error Closed.
I can get my device listed but thats about it.
The Issue goes further. I relocked the bootloader in order to install the RUU. Yet I get the error 131 custormer ID error.
I can't access the SD partition on the my computer screen as it doesn't show.
I can't get back to stock rom.
I can't install a new rom.
I can unlock and relock my bootloader.
I can install TWRP and CWM.
I can use fastboot usb. [Very limited]
The issue with fastboot usb is that it keeps saying error device not found and then it refuses to do anything.
I have installed and reinstalled the ADB drivers, SDK manager and htc sync manager.
The biggest issue at the moment is that I can't install any rom whatsoever.
Which basically means, its a potato.
HALLLLP. The htc one x is a international version. UK Vodafone more specifically. Hboot-1.35.0000
Oh yeah, the mount does not work in TWRP and CWM.
I tried different USB ports, cables and even a different computer.
Everything has been wiped. I factory reset it and wiped out other parts in TWRP and CWM in an effort to start from scratch.
Nothing seems to work though...
Edit: I narrowed down the issue
It seems that i can't flash boot.img when my bootloader is unlocked as:
'boot.img'...FAILED (command write failed (Unknown error))
therefore I can't load roms without it crashing on me.
I can however put things into the 'sd card' by loading a broken rom [crashes to process android]. But thats about it. so far.
Oh I also updated the hboot to 1.72
Click to expand...
Click to collapse
If you can push files on sd card, use the TWRP back-up from here to restore to stock.
http://forum.xda-developers.com/showthread.php?t=2414238
You'll at least get it working again.
Thanks, somehow when I updated the bootloader, the boot.img restriction got lifted after I just entered the command again when 'unknown failure' came up. I was at this point able to access the sd card under a buggy rom start-up.I used TWRP to flash a new rom.
Fixed.
Hi..
I also can't connect my device to PC
I need help ..
fastboot not working never
loaybilal said:
Hi..
I also can't connect my device to PC
I need help ..
fastboot not working never
Click to expand...
Click to collapse
To anyone in the same situation adb sideload does not transfer the file to the sdcard permanently. To sideload correctly, you need to pick that option from the recovery first and then when the phone is waiting for the sideload type:
adb sideload <PACKAGE>
after some hours of research mine worked (TWRP v2.7.0.1)
imcontreras said:
To anyone in the same situation adb sideload does not transfer the file to the sdcard permanently. To sideload correctly, you need to pick that option from the recovery first and then when the phone is waiting for the sideload type:
adb sideload <PACKAGE>
after some hours of research mine worked (TWRP v2.7.0.1)
Click to expand...
Click to collapse
I am in the same situation and my phone in TWRP is waiting for Sideload...
but adb gives error: closed
roshak said:
I am in the same situation and my phone in TWRP is waiting for Sideload...
but adb gives error: closed
Click to expand...
Click to collapse
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
imcontreras said:
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
Click to expand...
Click to collapse
So now! I could get my devices connected and listed with updating the drivers (Win 8.1) ...
Then I could push the SuperSU.zip and install it... Is there any way to check if it's ready for flashing a ROM?
roshak said:
So now! I could get my devices connected and listed with updating the drivers (Win 8.1) ...
Then I could push the SuperSU.zip and install it... Is there any way to check if it's ready for flashing a ROM?
Click to expand...
Click to collapse
Im not sure if this will answer your question:
When you upload your rom using sideload will automatically flash it to your device
imcontreras said:
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
Click to expand...
Click to collapse
Thank you!
Ok long story short, I deleted my OS and everything but I somehow got CM10.2 working and flashed with no problem.
What I want to know now is go back to 4.4.2 via flash and STOCK ROM from AT&T. I don't think there's a RUU for 4.4.2 yet so can anyone help me find the rom? All I can find are custom roms..
btort1 said:
So basically I have no OS, where can I get a rom or stock rom that has beats audio driver that has decent battery life?
Click to expand...
Click to collapse
As far as I know all the roms for the htc one have beats audio
are you trying to get away from a Sense Rom or just any working rom will do ?
clsA said:
As far as I know all the roms for the htc one have beats audio
are you trying to get away from a Sense Rom or just any working rom will do ?
Click to expand...
Click to collapse
right now ANY will do, I been trying to figure out why adb won't work but it keeps saying it can't find the device. I installed and reinstalled drivers and no luck, the only time it showed the serial number was when I was in recovery mode, I rebooted and tried to go on fastboot but no luck.
I I tried RUU and locked my phone again but no luck because stupid netbook always freezes at the last step before it tries to restore the stock rom -_- then I unlocked it again and kept trying with ADB
btort1 said:
right now ANY will do, I been trying to figure out why adb won't work but it keeps saying it can't find the device. I installed and reinstalled drivers and no luck, the only time it showed the serial number was when I was in recovery mode, I rebooted and tried to go on fastboot but no luck.
I I tried RUU and locked my phone again but no luck because stupid netbook always freezes at the last step before it tries to restore the stock rom -_- then I unlocked it again and kept trying with ADB
Click to expand...
Click to collapse
theirs nothing wrong
adb only works in recovery
sideload my rom while your in TWRP / Advanced / Sideload / swipe to sideload
put this in the same folder as adb
http://www.androidfilehost.com/?fid=23329332407580474
and from command prompt on your PC
adb sideload <name.of.rom>.zip
clsA said:
theirs nothing wrong
adb only works in recovery
sideload my rom while your in TWRP / Advanced / Sideload / swipe to sideload
put this in the same folder as adb
http://www.androidfilehost.com/?fid=23329332407580474
and from command prompt on your PC
adb sideload <name.of.rom>.zip
Click to expand...
Click to collapse
I have TWRPv2.6.3 and when I try advanced-adb sideload it asks me if I want to wipe dalvik cache and wipe cache, when I slide it, it says ADB sideload complete failed
Unable to mount data
bump
So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Ok, I am an idgit. Could a mod move this to the Q&A forum? Apologies.
EqualOpportunityDork said:
So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Click to expand...
Click to collapse
ADB works in an OS or in custom recovery and fastboot works in the bootloader. ADB doesn't work if the phone is in bootloader. I think you will have to run a RUU then go into stock recovery and do a factory reset. Let the phone boot normally then you can start the custom routine. You might also check to see if your ADB & fastboot are up to date. To run the RUU you will have to relock your bootloader since you are S-ON.
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
EqualOpportunityDork said:
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
Click to expand...
Click to collapse
Another quick thought, you wouldn't happen to be using Win 8 are you? If so, Win 8 doesn't see hboot 1.44 you are going to have to use a Win 7, Mac or Linux machine. Sorry, I didn't catch it earlier. Here is a how to for Linux and you don't have to install it permanently on your computer:
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
Click to expand...
Click to collapse
Dude, you are my hero. I couldn't get fastboot to work, because I had missed the part where I needed to preface it with sudo. I had adb and fastboot running a couple of days ago on my Mint install, but I didn't realize I was missing 4 freaking letters to get it right. Just flashed latest twrp and booted into recovery, no problem.
Thanks again, for the help, even if I should have found that on my own, sooner. I thought I had really hosed something on my phone. Now I can move on to hopefully not screwing something else up.
You could have used flashify to flash a recovery.IMG. free app from app store
I mentioned trying Flashify in the OP.
Hello, please help me! I have a droid turbo and wiped all partitions out using TWRP's advanced wipe. Now its stays on unlocked bootloader warning screen. Every time I try to reboot system through TWRP recovery mode it states that I have no OS installed and when I tried to connect the USB to my laptop it states that it doesn't recognize the device. I have no idea what to do! how can I install or recover my OS so the phone starts up. I was trying to wipe data before doing a factory reset so I can send it back to verizon as part of my new upgrade. However, I wanted to erase all existing information before doing so.
Thank you for your time, patience and effort in this matter, it will be greatly appreciated!!!
The Truth01 said:
Hello, please help me! I have a droid turbo and wiped all partitions out using TWRP's advanced wipe. Now its stays on unlocked bootloader warning screen. Every time I try to reboot system through TWRP recovery mode it states that I have no OS installed and when I tried to connect the USB to my laptop it states that it doesn't recognize the device. I have no idea what to do! how can I install or recover my OS so the phone starts up. I was trying to wipe data before doing a factory reset so I can send it back to verizon as part of my new upgrade. However, I wanted to erase all existing information before doing so.
Thank you for your time, patience and effort in this matter, it will be greatly appreciated!!!
Click to expand...
Click to collapse
This is asuming you have ADB and fastboot set up.
Open TWRP and click advanced, then hit adb sideload, now you should be able to sideload your stock ROM via ADB in this command "adb sideload nameofthezip.zip". Then reboot and you should be good to go!
Thanks for the assistance Razor but I tried adb sideload 4 times and it failed Everytime. Is there any other way I can resolve this issue?
The Truth01 said:
Thanks for the assistance Razor but I tried adb sideload 4 times and it failed Everytime. Is there any other way I can resolve this issue?
Click to expand...
Click to collapse
Well, what error messages do you get when doing adb sideload? If it is "severe" you can always do fastboot flash.
Sent using a ks01lte (gt-i9506) running cm 13
Right under "ADB Sideload Complete" at the top of the screen it says "Failed" in red.
Okay, lets flash it via fastboot. In the TWRP reboot screen, there should be a "bootloader" option. Now get the images for your device and since you said that you had the verizon model, you'll have to get the verizon images. Once you got them, put them in your fastboot folder and DON'T UNZIP THE SYSTEM FOLDER!!! Now open fastboot and type "fastboot flash boot nameoftheimg.boot.img" Notice how it ends with boot so in the command you have to do "fastboot flash whateveritendswith nameoftheimg". You don't do fastboot flash img mkay. Now that you know that, flash them in this order, boot, fastboot, recovery, "fastboot reboot-bootloader" then system.