Develop Bugs

[Soft Brick] No OS Installed

Hi everyone, i have medium to advanced experience with flashing tools, android drivers, adb, fastboot, recovery mode and so on.
This evening once i installed the OTA Update for my Galaxy Nexus (which was running Android 4.2) the process failed at the end (as usual -.-) and i got stuck at bootloader.
I've wiped it completely ending up with no OS installed on it, nothing on SDCARD (Internal storage in this case).
The problem is that, i have no drivers installed on my PC for this phone.
I've already downloaded the latest version of Android 4.2 to flash (.zip), but there's no way i can transfer the file to the phone without the drivers.
I already tried GNex toolkit but it's stuck on "waiting adb device" (i have no fastboot drivers installed and can't install them because i can't find a easy way to do so).
NexusRootToolkit fails on pushing the zip to the phone and flash also won't work.
Any idea of what can i do now?
I may even pay on paypal for a quick help to get my phone back on working

Get into the bootloader and use fastboot, or if you have a custom recovery installed (sounds like you don't) then you can adb push from there. ADB doesn't exist in the bootloader, only fastboot. Those are your options.

ttabbal said:
Get into the bootloader and use fastboot, or if you have a custom recovery installed (sounds like you don't) then you can adb push from there. ADB doesn't exist in the bootloader, only fastboot. Those are your options.
Click to expand...
Click to collapse
Actually i do have a custom recovery which is CMW, but i can't seem to get my internal storage mounted using i'ts options.
I will try to push the .zip using the ADB on the recovery mode.
After checking the logs i can now see :
Enable to mount /usb-otg
(Using NexusRootToolkit i just flashed TWRP as recovery mode)
Solved : adb push <romname.zip> /sdcard/<romname.zip>
After the push was completed, i flashed the new .zip using TWRP in recovery mode.

Has anyone found a solution to this? Same thing has happened to me and I'm freaking out.

NPasta said:
Has anyone found a solution to this? Same thing has happened to me and I'm freaking out.
Click to expand...
Click to collapse
You mean besides the post right above yours?
Solved : adb push <romname.zip> /sdcard/<romname.zip>
After the push was completed, i flashed the new .zip using TWRP in recovery mode.
Click to expand...
Click to collapse

Save the pain, just flash the stock ROM from fastboot already....

Mach3.2 said:
Save the pain, just flash the stock ROM from fastboot already....
Click to expand...
Click to collapse
This. I don't see what the problem is here.

marcelloLins said:
i have medium to advanced experience with flashing tools, android drivers, adb, fastboot, recovery mode and so on.
I already tried GNex toolkit but it's stuck on "waiting adb device" (i have no fastboot drivers installed and can't install them because i can't find a easy way to do so).
NexusRootToolkit fails on pushing the zip to the phone and flash also won't work.
Click to expand...
Click to collapse
If you have the experience you say you have why do you use a Toolkit? Just learning for myself.
Look for efrant posts, they are the best and most comprehensive even for medium-advanced experience.
With him you will learn everything you need to know, including getting out of trouble and out of.............toolkit.
Just in case (you never know in life) do you have android-sdk installed on your pc?
Good luck in your learning curve ( I am still and will always be in it)

help-a-noob
Having similar problem: no OS installed. Got bootloader and TWRP. adb push doesn't work: computer can't find device. how do I get to fastboot? HALP!

HALP...
That's classic..
Read this:
http://forum.xda-developers.com/showthread.php?t=1812959
Then follow this:
http://forum.xda-developers.com/showthread.php?t=1626895

gunner1937 said:
If you have the experience you say you have why do you use a Toolkit? Just learning for myself.
Look for efrant posts, they are the best and most comprehensive even for medium-advanced experience.
With him you will learn everything you need to know, including getting out of trouble and out of.............toolkit.
Just in case (you never know in life) do you have android-sdk installed on your pc?
Good luck in your learning curve ( I am still and will always be in it)
Click to expand...
Click to collapse
Yep, i do have it installed, mainly because i'm a developer myself ; )
I've solved it already, as i've said, pushing the rom using ADB.
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Thanks for all the support and links by the way

marcelloLins said:
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Click to expand...
Click to collapse
You are mistaken, root doesn't stop a system update. I can vouch for that myself, even though i know that it doesnt matter just from reading some people's posts around here.
You weren't exactly explicit on your first post, so I presume you didnt/dont have the correct baseband version for that specific OTA to apply. Very common.
Oh and if you've never been able to OTA update successfully, it's not "usual" for the rest of us. You should work towards becoming more verbose and objective when troubleshooting. That will make you more experienced.
Sent from my i9250

marcelloLins said:
Yep, i do have it installed, mainly because i'm a developer myself ; )
I've solved it already, as i've said, pushing the rom using ADB.
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Thanks for all the support and links by the way
Click to expand...
Click to collapse
Hey, I have this exact problem. My os is gone and all i have is my cwm.
I am also having trouble installing adb, my comp doesn't recognize my nexus.
Please help, thanks!

dicksonjoe said:
Hey, I have this exact problem. My os is gone and all i have is my cwm.
I am also having trouble installing adb, my comp doesn't recognize my nexus.
Please help, thanks!
Click to expand...
Click to collapse
Try installing the ADB Drivers manually in order for your PC to recognize it.
Have you tried putting it other modes such as Download Mode and check if your pc installs any driver?
You will have to ADB PUSH the OS image to your internal memory and use CW to flash the rom from the sdcard, but you will need the drivers installed or adb wont be able to see your phone

i have the same problem you had...
i read some stuff and installed adb, sdk and whatever...
im trying the " adb push" command, but i think im doing something wrong.
the rom is on c:\users\edgar\downloads
rom name is abc.zip (i renamed)
what is the correct command format i must type??
thanks guys...

edgarzin said:
i have the same problem you had...
i read some stuff and installed adb, sdk and whatever...
im trying the " adb push" command, but i think im doing something wrong.
the rom is on c:\users\edgar\downloads
rom name is abc.zip (i renamed)
what is the correct command format i must type??
thanks guys...
Click to expand...
Click to collapse
Use "adb sideload c:\users\edgar\downloads\abc.zip". "adb push" is for transferring files from PC to phone, not flashing.

AndyYan said:
Use "adb sideload c:\users\edgar\downloads\abc.zip". "adb push" is for transferring files from PC to phone, not flashing.
Click to expand...
Click to collapse
thanks, but isnt it what am i supposed to do? transfer the zip file to sdcard and then flash using twrp?

for example usb mount via twrp dont work for me

edgarzin said:
thanks, but isnt it what am i supposed to do? transfer the zip file to sdcard and then flash using twrp?
Click to expand...
Click to collapse
adb sideload does both transferring and flashing within a single command. The "sideloaded" ZIP gets saved as "sideload.zip" under the root of the storage.
Sent from Samsung Galaxy Nexus @ CM11

AndyYan said:
adb sideload does both transferring and flashing within a single command. The "sideloaded" ZIP gets saved as "sideload.zip" under the root of the storage.
Sent from Samsung Galaxy Nexus @ CM11
Click to expand...
Click to collapse
Thanks!! Now its working! in twrp, advanced mode, adb sideload, then i executed the command you told me!!! saved my phone

HELP pushing files

hey guys i need some serious help here. so i accidentaly erased my sd card with my custom roms on it. im sitting at the "google" screen right now and my computer (windows 8 64) recognizes the phone in adb, if i go into CWM i cannot install drivers windows 8 will not let me no matter how i try. but this is my huge dilemma im trying to push the rom to my sdcard with adb and i keep getting either permission denied, or failed to copy..... is a directory. what command am i missing? i have done this plenty of times before and it worked. currently i have tried the directories on the device: /data/media/sdcard, /sdcard/, /sideload, /mnt/sdcard/ and all come back with a similar error. please help i cant figure out what is wrong.

Chyrio said:
hey guys i need some serious help here. so i accidentaly erased my sd card with my custom roms on it. im sitting at the "google" screen right now and my computer (windows 8 64) recognizes the phone in adb, if i go into CWM i cannot install drivers windows 8 will not let me no matter how i try. but this is my huge dilemma im trying to push the rom to my sdcard with adb and i keep getting either permission denied, or failed to copy..... is a directory. what command am i missing? i have done this plenty of times before and it worked. currently i have tried the directories on the device: /data/media/sdcard, /sdcard/, /sideload, /mnt/sdcard/ and all come back with a similar error. please help i cant figure out what is wrong.
Click to expand...
Click to collapse
Try /storage/sdcard0
But if that doesnt work, reboot to bootloader and flash stock userdata.img through fastboot; reboot to recovery right after that, push rom.
Sent from my i9250

I ran into the same problem, I erased my internal memory and i'm now stuck with the google screen
i have TWRP recovery but there is nothing on the sd card to flash from, how do i push files to the sd card from the computer?
I tried use the nexus root toolkit but i get "fastboot device not found" even though the bootloader says that it is in fastboot mode.
please help

nope that didnt work either but i found a work around. i had never played with CWM's sideload feature. FOR FUTURE GOOGLE GOERS
NOTE: you need CWM 6.0.1.5 and above i think
reboot into recovery
select install from sideload
make sure drivers are installed (i used the universal android drivers here: http://forum.xda-developers.com/showthread.php?t=1514942)
open up adb in cmd (hopefully you have adb in your com)
and type "adb sideload <filename.zip>" without quotes or the little arrows
and you should see it start copying
I would like CWM and TWRP for using this in their recovery!!!!!

Chyrio said:
nope that didnt work either but i found a work around. i had never played with CWM's sideload feature. FOR FUTURE GOOGLE GOERS
NOTE: you need CWM 6.0.1.5 and above i think
reboot into recovery
select install from sideload
make sure drivers are installed (i used the universal android drivers here: http://forum.xda-developers.com/showthread.php?t=1514942)
open up adb in cmd (hopefully you have adb in your com)
and type "adb sideload <filename.zip>" without quotes or the little arrows
and you should see it start copying
I would like CWM and TWRP for using this in their recovery!!!!!
Click to expand...
Click to collapse
I tried to use your sideload command but it didn't work. It said "ERROR: CLOSED"
i'm really anxious and worried if i can get the phone to work at all:crying:. any help will be greatly appreciated!

Download Wugfresh Galaxy Nexus Tool. You can't possibly have a bricked phone after using that tool

italbomber said:
Download Wugfresh Galaxy Nexus Tool. You can't possibly have a bricked phone after using that tool
Click to expand...
Click to collapse
Thank you. I tried doing that but it wasn't any help. however, i figured how to sideload using the TWRP setting. It took a little trial and error but finally got it to work.

i don't see how can you guys not get it to work through normal adb, other than you're using Windows, but glad you got it to work.

Glad to hear you are up and running again. Sorry i just always had great luck with his toolkit. Adb was always failsafe too.
Sent from my Galaxy Nexus using Tapatalk 2

Just a note you were probably getting an error because you didn't Mount the sdcard in recovery before trying to push to it.
Sent from my Galaxy Nexus using xda premium

I did a full wipe of the phone and SD card and was unable to see my phone in adb while in CWM recovery.
I run the push command any way and it did push to the file to the phone.
I push the file to /data/media/ no need to mount SDcard as it doesn't have a real one, in the past (while using ics) I have had to mount data to push files to /sdcard/

closed

closed

Read this whole thread. THE WHOLE THING. Preferably thoroughly.

edited

AJThePwnapple said:
Even though I have a factory cable, do you want me to go into fastboot using your method?
I tried flashing the images but my computer doesn't recognize the device (can't install otter2-prod-04) and stays at <waiting for device>. Will it be different using your method?
Sorry if I come off a bit noobish, I'm brand new to this.
Click to expand...
Click to collapse
you need the drivers (should have been mentioned on that thread.)
If you have a fbcable, use it. on windows, device manager, uninstall the current driver if there is any, and use KFU to install the fastboot driver. (only use kfu for the driver, don't do anything else.)

Nevermind, I resolved the problem. It was much easier than I thought, after hours of pulling my hair out.
I now have cm10.1 on my kindle.
Thanks so much anyway.

AJThePwnapple said:
Nevermind, I resolved the problem. It was much easier than I thought, after hours of pulling my hair out.
I now have cm10.1 on my kindle.
Thanks so much anyway.
Click to expand...
Click to collapse
No problem, i'm happy to help

I had a similar problem when I did mine. (forgot to transfer the rom before wiping)
I could boot into TWRP so i just changed the permissions of the download folder and pushed the rom over from my PC

Same here...
obsolete1 said:
I had a similar problem when I did mine. (forgot to transfer the rom before wiping)
I could boot into TWRP so i just changed the permissions of the download folder and pushed the rom over from my PC
Click to expand...
Click to collapse
I did the same. I wiped the rom when I was prepping for flash... I forgot I didn't have an SD card for the rom... Took me a few days to get ADB working on a Linux PC, then I sideloaded the rom.
Patience was key...

yudanjah said:
I did the same. I wiped the rom when I was prepping for flash... I forgot I didn't have an SD card for the rom... Took me a few days to get ADB working on a Linux PC, then I sideloaded the rom.
Patience was key...
Click to expand...
Click to collapse
I deleted my data and so I can't install my ROM, my device read as Amazon Kindle Fire2 (I already installed CM10 and I'm just trying to update)and I can't sideload via TWRP since my device is not detected in adb, I can boot in fastboot, can I push the zip file from there? or any steps on how adb can recognize my device? I tried installing driver from KFU and updated my android SDK tools but still no devices found. I also tried to kill and restart adb and even amazon driver in extras via Android SDK.
Thanks for your help.

melvsmis ster said:
I deleted my data and so I can't install my ROM, my device read as Amazon Kindle Fire2 (I already installed CM10 and I'm just trying to update)and I can't sideload via TWRP since my device is not detected in adb, I can boot in fastboot, can I push the zip file from there? or any steps on how adb can recognize my device? I tried installing driver from KFU and updated my android SDK tools but still no devices found. I also tried to kill and restart adb and even amazon driver in extras via Android SDK.
Thanks for your help.
Click to expand...
Click to collapse
I deleted my os with no backup and wiped all files but i could boot into twrp. I couldn't see my kindle or files when plugged into my computer. I booted into twrp and hit advanced then adb side load, I downloaded cm10 ROM into a new file named kindle on my computer renamed the ROM file cm, opened a command prompt in the file " kindle" and typed adb sideload cm.zip then enter and it pushed the file over rebooted and it was fixed. Not sure if anyone else recommended this, I did it about a month ago hope i didnt forget anything, good luck

gnandez said:
I deleted my os with no backup and wiped all files but i could boot into twrp. I couldn't see my kindle or files when plugged into my computer. I booted into twrp and hit advanced then adb side load, I downloaded cm10 ROM into a new file named kindle on my computer renamed the ROM file cm, opened a command prompt in the file " kindle" and typed adb sideload cm.zip then enter and it pushed the file over rebooted and it was fixed. Not sure if anyone else recommended this, I did it about a month ago hope i didnt forget anything, good luck
Click to expand...
Click to collapse
My main problem with adb is it didnt recognize my device even i tried the ff:
-install driver from kfu
-install driver from amazon in extra via android sdk
-remove driver in device mngr then plug device to auto install driver
My fastboot is working but i didnt know the syntax to flash. Im thinking can i flash zip to system partition then just copy it to sd card via twrp file mngr? Or extract rom from zip then flash boot.img but im worried that twrp might be overwrtten?

melvsmeister said:
My main problem with adb is it didnt recognize my device even i tried the ff:
-install driver from kfu
-install driver from amazon in extra via android sdk
-remove driver in device mngr tn plug devicle to auto install driver
My fastboot is working but i didnt know the syntax to flash. Im thinking can i flash zip to system partition then just copy it to sd card via twrp file mngr? Or extract rom from zip then flash boot.img but im worried that twrp might be overwrtten?
Click to expand...
Click to collapse
Sorry, I posted that because I'm just learning fast boot and adb and I looked for another way.. So I used the cmd prompt on windows to push my ROM onto my kindle sorry if I gave the impression I could help with fastboot. our problems seemed the same so I thought another way could help

gnandez said:
Sorry, I posted that because I'm just learning fast boot and adb and I looked for another way.. So I used the cmd prompt on windows to push my ROM onto my kindle sorry if I gave the impression I could help with fastboot. our problems seemed the same so I thought another way could help
Click to expand...
Click to collapse
I guess I'm missing some steps here or maybe I need to do something to make it work since my adb is not detected in TWRP but I can have it if I let it boot to blue kindle logo. I'm still having a hard time in pushing ROM due to "No space left on device" error and even though I can push gapps I can't find it in TWRP. I'll just wait for someone who might had the same issue and have other solution to resolve this problem. Thanks for your help!:good:

[Q] boot loop installing paranoid 4.0 beta, can't fastboot

Hi everyone,
I have a Nexus 4 and I just managed to get it in a boot loop after trying to install Paranoid Android 4.0 beta (pa_mako-4.0-BETA-20131223.zip).
I saw an update come up in goomanager so I downloaded and tried to install it, but after rebooting and starting the update from recovery mode it failed with the following message:
Code:
...
set_metadata_recursive: some changes failed
E:Error in /sdcard/paranoidota/pa_mako-4.0-BETA-20131223.zip
(Status 7)
Error flashing zip '/sdcard/paranoidota/pa_mako-4.0-BETA-20131223.zip'
Updating partition details...
After this the phone doesn't boot, it stays with the Google logo for a while, and then automatically reboots and goes to recovery.
I'm not sure what that happened. After researching a bit I found out that I may have had to update the recovery first (I'm using TWRP 2.4.4.0).
Therefore I downloaded the last version and tried to install it, but I've found another problem. When I connect the phone to the computer with a microusb cable, the phone is not recognized at all by the computer. I tried both fastboot (booting the bootloader in the phone) and ADB Sideload from the recovery. I use Ubuntu, and the phone should be listed with the command lsusb, but it's not. It's something similar to the device not coming up in the device manager on Windows. It's not listed when running either adb devices nor fastboot devices. I thought it may be a problem of having disabled USB debugging in the phone, but I read somewhere that fastboot should work nevertheless.
I tried 3 different microusb cables, 3 USB ports, 2 kernel versions in my computer and 2 different computers.
Can anybody give me some hope? :crying: Also ideas on how I may solve the problem would be really helpful.
Thanks a lot.

sepha said:
Hi everyone,
I have a Nexus 4 and I just managed to get it in a boot loop after trying to install Paranoid Android 4.0 beta (pa_mako-4.0-BETA-20131223.zip).
I saw an update come up in goomanager so I downloaded and tried to install it, but after rebooting and starting the update from recovery mode it failed with the following message:
Code:
...
set_metadata_recursive: some changes failed
E:Error in /sdcard/paranoidota/pa_mako-4.0-BETA-20131223.zip
(Status 7)
Error flashing zip '/sdcard/paranoidota/pa_mako-4.0-BETA-20131223.zip'
Updating partition details...
After this the phone doesn't boot, it stays with the Google logo for a while, and then automatically reboots and goes to recovery.
I'm not sure what that happened. After researching a bit I found out that I may have had to update the recovery first (I'm using TWRP 2.4.4.0).
Therefore I downloaded the last version and tried to install it, but I've found another problem. When I connect the phone to the computer with a microusb cable, the phone is not recognized at all by the computer. I tried both fastboot (booting the bootloader in the phone) and ADB Sideload from the recovery. I use Ubuntu, and the phone should be listed with the command lsusb, but it's not. It's something similar to the device not coming up in the device manager on Windows. It's not listed when running either adb devices nor fastboot devices. I thought it may be a problem of having disabled USB debugging in the phone, but I read somewhere that fastboot should work nevertheless.
I tried 3 different microusb cables, 3 USB ports, 2 kernel versions in my computer and 2 different computers.
Can anybody give me some hope? :crying: Also ideas on how I may solve the problem would be really helpful.
Thanks a lot.
Click to expand...
Click to collapse
From what I gather you can get into recovery mode without issue.
Simply restore a backup or try reflashing the previous version of the ROM

Anu6is said:
From what I gather you can get into recovery mode without issue.
Simply restore a backup or try reflashing the previous version of the ROM
Click to expand...
Click to collapse
Thanks Anu6is for the reply. Yes, recovery mode works, but no backups appear in the "restore" option and I can't find any either if I manually browse the file system at /sdcard. I thought I made one when first installing PA but nothing is there.
Also, no previous versions of the ROM are currently in the file system. I never thought I would need them again so I removed them to free space.
Is there a reason why ADB and fastboot would be inaccessible through USB besides a hardware failure?

Your problem is the antiquated recovery. Update your recovery
Sent from my Nexus 5

sepha said:
Thanks Anu6is for the reply. Yes, recovery mode works, but no backups appear in the "restore" option and I can't find any either if I manually browse the file system at /sdcard. I thought I made one when first installing PA but nothing is there.
Also, no previous versions of the ROM are currently in the file system. I never thought I would need them again so I removed them to free space.
Is there a reason why ADB and fastboot would be inaccessible through USB besides a hardware failure?
Click to expand...
Click to collapse
Boot into fastboot instead of recovery and update your recovery via fastboot

Pirateghost said:
Your problem is the antiquated recovery. Update your recovery
Click to expand...
Click to collapse
Thanks Pirateghost and Anu6is for confirming that the problem is an old recovery. Updating the recovery is what I'm trying to do, but as I commented in my first post I can't use fastboot, since even when I'm in the bootloader the phone is not detected by the computer when plugged.
Any idea how to fix that?
Thanks

sepha said:
Thanks Pirateghost and Anu6is for confirming that the problem is an old recovery. Updating the recovery is what I'm trying to do, but as I commented in my first post I can't use fastboot, since even when I'm in the bootloader the phone is not detected by the computer when plugged.
Any idea how to fix that?
Thanks
Click to expand...
Click to collapse
When in fastboot mode, try the command
fastboot devices
see if you computer returns anything

Anu6is said:
When in fastboot mode, try the command
fastboot devices
see if you computer returns anything
Click to expand...
Click to collapse
As I commented in my first post, adb devices and fastboot devices don't return anything. My phone doesn't even appear in the device manager. I tried different cables, different USB ports and different computers.

sepha said:
As I commented in my first post, adb devices and fastboot devices don't return anything. My phone doesn't even appear in the device manager. I tried different cables, different USB ports and different computers.
Click to expand...
Click to collapse
Yeah, sorry...that was too much to read, just scanned it.
I don't know...That's always my fallback, not sure why it wouldn't show
Sent from my Nexus 4 using Tapatalk

So I'm guessing wiping the phone is a no-no for you. Going through basics here.
So you've made sure that the daemon service is running.. .well friend i hope you get throug
Sent from my ONE TOUCH 4033A using xda app-developers app

D_Dio said:
So I'm guessing wiping the phone is a no-no for you. Going through basics here.
Click to expand...
Click to collapse
I've tried wiping caches and doing a factory reset after doing a backup (of the system already in the boot loop condition) but it didn't change anything.

If you've already got root. Can try recovery tools app to install the new recovery
ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ

plegdroid said:
If you've already got root. Can try recovery tools app to install the new recovery
Click to expand...
Click to collapse
the problem is that I cannot copy a new recovery to the phone's memory, since Android won't boot, and ADB and fastboot won't work, and it doesn't have a microsd slot

sepha said:
the problem is that I cannot copy a new recovery to the phone's memory, since Android won't boot, and ADB and fastboot won't work, and it doesn't have a microsd slot
Click to expand...
Click to collapse
My much bad. Hope you get it sorted
While iam here thou, have you updated your computers drivers for the n4? Incase that's the reason its not finding your phone.
ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ

sepha said:
the problem is that I cannot copy a new recovery to the phone's memory, since Android won't boot, and ADB and fastboot won't work, and it doesn't have a microsd slot
Click to expand...
Click to collapse
Try cleaning your USB port on the phone with some alcohol
Sent from my Nexus 5

Pirateghost said:
Try cleaning your USB port on the phone with some alcohol
Click to expand...
Click to collapse
Thanks Pirateghost. I tried but it didn't work. I'm more and more convinced there's something wrong with the hardware. Maybe I dropped it one too many times. It was just a strange coincidence and really bad luck that I realized it didn't work just after the problem installing a new ROM.
Anyways, I ordered a replacement for the PCB that holds the microusb connector. Let's hope that works.

I solved the problem.
I managed to make the phone appear on the computer. There must be something broken in the microusb port in the phone because sometimes when I connect the phone nothing will appear on dmesg (I use Linux), sometimes I get USB errors and after trying a few times I managed to make it work.
I updated the recovery through fastboot and then I was able to successfully install the new ROM from recovery and now everything works alright.
Once the replacement board I ordered arrives I'll try replacing that and see if that fixes the USB connection problems.
Thanks to everybody who helped.

[Q] Can't boot phone after upgrade - CyanogenMod 10.2 Stable

Hey guys,
So the problem I'm experiencing is that my HTC One X is stuck in a boot loop after I applied an update to CyanogenMod 10.2 Stable that I saw in the settings menu. Dumb mistake.
I've tried reading up on the issue but I'm posting here because I want to make sure I don't brick the phone. I bought the phone second hand, already rooted and flashed, so my knowledge on this stuff is extremely limited.
So here's some info:
1. I can access a boot menu when I hold the power and volume down button.
2. From there I can access ClockworkMod Recovery v5.8.4.0
3. I've tried restoring the phone
4. I found and applied the 2 zips that are already in the sd card. The old one: CM 10.1 and CM 10.2. - Both of them get stuck in boot.
5. I've downloaded Fastboot and ADB to my computer.
6. I tried to follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2617301. Fastboot can't find my device (fastboot getvar cid -> waiting for device). I should mention that I mounted /sdcard and also tried mounting 'USB storage' but that didn't seem to do anything.
I also found this thread that might be of help once I get the computer to see my phone: http://forum.cyanogenmod.com/topic/...01-to-102-if-you-get-stuck-at-boot-animation/

ChrisGiggles said:
Hey guys,
So the problem I'm experiencing is that my HTC One X is stuck in a boot loop after I applied an update to CyanogenMod 10.2 Stable that I saw in the settings menu. Dumb mistake.
I've tried reading up on the issue but I'm posting here because I want to make sure I don't brick the phone. I bought the phone second hand, already rooted and flashed, so my knowledge on this stuff is extremely limited.
So here's some info:
1. I can access a boot menu when I hold the power and volume down button.
2. From there I can access ClockworkMod Recovery v5.8.4.0
3. I've tried restoring the phone
4. I found and applied the 2 zips that are already in the sd card. The old one: CM 10.1 and CM 10.2. - Both of them get stuck in boot.
5. I've downloaded Fastboot and ADB to my computer.
6. I tried to follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2617301. Fastboot can't find my device (fastboot getvar cid -> waiting for device). I should mention that I mounted /sdcard and also tried mounting 'USB storage' but that didn't seem to do anything.
I also found this thread that might be of help once I get the computer to see my phone: http://forum.cyanogenmod.com/topic/...01-to-102-if-you-get-stuck-at-boot-animation/
Click to expand...
Click to collapse
Download htc sync it will install the drivers required ,then you're good to go

When you install drivers..Go to recovery wipe everything except battery stats and storage..Then flash cm10.2 zip and then gapps..Then flash boot.img and erase cache..
Sent from my HTC One X using Tapatalk 2

Muksleo said:
Download htc sync it will install the drivers required ,then you're good to go
Click to expand...
Click to collapse
Ok, I'm back from trying that. On my old PC laptop the software just failed to install. I'm trying again... takes forever to install.
I also downloaded it for my Mac, that worked fine but it doesn't actually find the phone when connected.
EDIT: POS computers... The Windows one throws up a weird error, no explanation, just a bunch of numbers. The Mac one is just incompetent...

What windows do you have?? 7,8.1 install drivers automatically..

big noob said:
What windows do you have?? 7,8.1 install drivers automatically..
Click to expand...
Click to collapse
The PC is running Windows 7... but neither of my computers recognize the phone (or mount the storage) through the USB.
I'm f*cked I think.
EDIT: Yep, I got the HTC sync to install finally on the Windows PC. And as I suspected, it doesn't recognize my phone.

So I guess my problem now is that the phone doesn't actually mount. I've never connected it to a computer before so I don't know if this is a new problem or not.
I've tried 2 computers and 2 different cables. I guess the phone is essentially bricked now? So much for "stable" update...

ChrisGiggles said:
So I guess my problem now is that the phone doesn't actually mount. I've never connected it to a computer before so I don't know if this is a new problem or not.
I've tried 2 computers and 2 different cables. I guess the phone is essentially bricked now? So much for "stable" update...
Click to expand...
Click to collapse
Restart your computer after driver installation
after that go where u have fastboot folder press shift and right click and click on open command window here
there u can give fastboot commands

Muksleo said:
Restart your computer after driver installation
after that go where u have fastboot folder press shift and right click and click on open command window here
there u can give fastboot commands
Click to expand...
Click to collapse
Thanks but that's exactly what I've been doing.

Well,did you try to remove all installed drivers..And let Windows install drivers..That always works for me..
Sent from my HTC One X using Tapatalk 2