I was on CleanROM 1.5 for AT&T, but decided to switch to ARHD for continued updates. Flashed the ROM and the problem began. I've since tried to go back to cleanrob via pushing the rom with adb, no go. I've wiped the phone countless times. I've erased the fastboot cache. I've switched TWRP/CWM neither changed anything. Fixed permission, flashed the boot images associated with each rom. Let it hang on the HTC screen for 30 minutes. I've exhausted the extent of google. Can anyone help?
Did you try adb sideload. Open clockwork and click install from sideload. Then go to command prompt, the adb directory and type adb sideload romname.zip.
Try Cleanrom, works for me.
zsamuels28 said:
Did you try adb sideload. Open clockwork and click install from sideload. Then go to command prompt, the adb directory and type adb sideload romname.zip.
Try Cleanrom, works for me.
Click to expand...
Click to collapse
I've tried everything, apparently something is wrong with partitions. No one seems to know how to fix it.
Related
I did not backup because I thought I had already done so. Apparently it was wiped at some point and I didn't add the right file to my phone. I just need some way to add the ROM to my internal sdcard
install TWRP recovery and use "sideload" or "push" the rom across to your phone
http://forum.xda-developers.com/showthread.php?t=1995002
adb push rom.zip /data/media/
Click to expand...
Click to collapse
sometimes sideloading is a pig to get working but just select sideload from recovery and push your file across. Trust me it does work I always wipe everything on my phone between rom flashes.
Would you be able to give me some steps? I have TWRP installed already.
I clicked ADP sideload on my toolkit. Im in recovery, I typed in "adb sideload <Ubuntu.zip>", "adb sideload Ubuntu.zip", "adb push Ubuntu.zip" and it's still not working
Well, I got the file on there, but now it's still freezing at the same screen. I'll give another ROM a try and see what happens..
I can't get sideload to work now.....
"Starting ADB sideload feature..." is all it says when I go Advanced/ADB sideload
I'm not sure how I got it to work before.... Now I can't even get the device to show up...
YYYYYYYYYAAAAY!!! I fixed it. Thanks for the tip man. You showed me the path and it was rough, but everything works great now.
yep sideload takes a while before it shows up on your pc
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
I am yet another idiot that wiped my tab 10.1, and then went to flash the ROM I had downloaded to it. So of course now I'm left with no OS installed and no files on board. I have TWRP installed and can still get to that. I can get to advanced > Adb Sideload. I can type adb devices in the command prompt, and my device is found successfully. But when I type adb Sideload ROM.zip, it states transferring then immediately says 0.00x transferred in the command prompt, and failed in red on the device.
I have never run into this and have googled to no end, but every post I find is related to Nexus devices. Can somebody please offer some insight so I'm not forever stuck in TWRP purgatory
Rather than use adb sideload, why not just use adb push to transfer the .zip file and then flash it normally?
As a last resort, you can also use Odin to flash a stock Samsung ROM or one of Pershoot's old Odin-friendly CM Roms too.
Sent from my GT-N5110 using Tapatalk