Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,777,785 Members 47,173 Now Online
XDA Developers Android and Mobile Development Forum

Error closed on ADB sideload. Device not found on Fastboot. HALP!!!!!

Tip us?
 
NinjaKenZen
Old
(Last edited by NinjaKenZen; 22nd January 2014 at 05:43 PM.)
#1  
Member - OP
Thanks Meter 5
Posts: 31
Join Date: Apr 2012
Default Error closed on ADB sideload. Device not found on Fastboot. HALP!!!!!

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
 
ady2pak
Old
#2  
Junior Member
Thanks Meter 1
Posts: 11
Join Date: May 2011
Quote:
Originally Posted by NinjaKenZen View Post
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
If you can push files on sd card, use the TWRP back-up from here to restore to stock.

http://forum.xda-developers.com/show....php?t=2414238

You'll at least get it working again.
The Following User Says Thank You to ady2pak For This Useful Post: [ Click to Expand ]
 
NinjaKenZen
Old
#3  
Member - OP
Thanks Meter 5
Posts: 31
Join Date: Apr 2012
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.
 
loaybilal
Old
#4  
Junior Member
Thanks Meter 0
Posts: 10
Join Date: May 2011
Location: Damascus
Hi..

I also can't connect my device to PC

I need help ..

fastboot not working never
 
imcontreras
Old
#5  
imcontreras's Avatar
Junior Member
Thanks Meter 0
Posts: 22
Join Date: Oct 2008
Location: Chicago
Quote:
Originally Posted by loaybilal View Post
Hi..

I also can't connect my device to PC

I need help ..

fastboot not working never
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)
EVO 4G
http://www.lightbox.com/wall/imcontreras
gingerbread-evo-deck 1.3
(always read before to ask)
 
roshak
Old
#6  
Member
Thanks Meter 1
Posts: 41
Join Date: Dec 2007
Quote:
Originally Posted by imcontreras View Post
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)
I am in the same situation and my phone in TWRP is waiting for Sideload...
but adb gives error: closed
 
imcontreras
Old
#7  
imcontreras's Avatar
Junior Member
Thanks Meter 0
Posts: 22
Join Date: Oct 2008
Location: Chicago
Quote:
Originally Posted by roshak View Post
I am in the same situation and my phone in TWRP is waiting for Sideload...
but adb gives error: closed
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
EVO 4G
http://www.lightbox.com/wall/imcontreras
gingerbread-evo-deck 1.3
(always read before to ask)
 
roshak
Old
(Last edited by roshak; 23rd July 2014 at 03:02 AM.)
#8  
Member
Thanks Meter 1
Posts: 41
Join Date: Dec 2007
Quote:
Originally Posted by imcontreras View Post
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
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?
 
imcontreras
Old
#9  
imcontreras's Avatar
Junior Member
Thanks Meter 0
Posts: 22
Join Date: Oct 2008
Location: Chicago
Quote:
Originally Posted by roshak View Post
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?

Im not sure if this will answer your question:
When you upload your rom using sideload will automatically flash it to your device
EVO 4G
http://www.lightbox.com/wall/imcontreras
gingerbread-evo-deck 1.3
(always read before to ask)

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes