yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] novo2393:
Sorry i couldnt help. Btw my repair centre is the worst , just got mine back and they unlocked the bootloader, not good when it was supposed to be repaired. Then back in october they told me my gsII was liquid damaged, hell was! Had to wait over a month for replacement and sooooo many phone calls.
[Samsung Galaxy Nexus] droidace:
That's it ..

OK, the service center concluded that the whole board needs to be changed costing nearly the phone's price, leading to a "no brainer" decision to continue using it the way it is as there was no warranty when i got the phone as a 2nd hand :mad:

As expected, the technicians do not have a single clue why and how did this happen!

End of story .. Thanks everybody!
[Samsung Galaxy Nexus] michaelmotes:
If you cant flash, try flashing the latest stock rom, 4.0.4 and I would be curious if adb worked in CWM. You can flash CWM recovery.img from fastboot, boot into recovery and see if adb recognizes the device.

Clean wipe the phone and flash the 4.0.4 rom, especially the boot.img, as it sounds like a bad kernel to me, if fastboot still works.
[Samsung Galaxy Nexus] harveydent:
That's their default answer when they don't have a clue / they're too lazy to troubleshoot
[Samsung Galaxy Nexus] axion68:
Try a different USB cable? I believe some cables are only wired to charge, no data.
[Samsung Galaxy Nexus] fil286n:
I have same problem here. I tried every method.

The computers only recognize the bootloader.

Nothing happen when plug phone to computer when it on or in CWM recovery.

Any help?

Solved! Just re-flash your bootloader with fastboot. Everything worked. (Still don't know how lol, but who care???)
[Samsung Galaxy Nexus] bl4ck0p5:
what exactly do u mean by "reflash your bootloader"?
[Samsung Galaxy Nexus] lutyz:
1. install the suitable driver on your windows

2. check others USB port.

3. change another cable
[Samsung Galaxy Nexus] montrealguy:
Same problem here. What is he talking about? And can he provide specific directions?
[Samsung Galaxy Nexus] thegtfusion:
Download a rom, extract it, then take the bootloader.img and put it in your fastboot folder. Connect the phone in faastboot mode and run this command : fastboot flash bootloader bootloader.img
[Samsung Galaxy Nexus] bl4ck0p5:
Hey guys, I found the solution and it's not software-related at all. If you look in the USB charge port of your GN you'll see a little metal board where the USB cable makes contact with the USB pins. What happened, at least IN MY CASE, is that this little board was somehow bent almost all the way down in a way that it short circuited with the metal case surrounding the port. So I took out my pocket knife and gently, carefully pushed (bent) the metal board in a way that it doesn't touch anything else, it's right in the middle of the port now. And voilà, now everything is working as it should. DISCLAIMER: I am not responsible for any damage u may end up causing to your device, I'm just sharing something I tried on my own and in my case it worked perfectly! Good luck to all!

Edit: nevermind, it's happening again lol gonna try to replace the usb board + flat I guess
[Samsung Galaxy Nexus] omr911:
It happens when u add few drops of water in charging port.. lol

Really !

Happened to me too ..

I used every trick vacuum, hair dryer, sun-light, heat etc. but didnt work

then I dipped my phone in 100 kg rice bag for 2 days .. lol

problem resolved !
[Samsung Galaxy Nexus] ShankyJain:
Solution

Try this

http://xdaforums.com/showpost.php?p=31066425&postcount=12

Hit THANKS if I helped
[Samsung Galaxy Nexus] smcgrath1111:
I am having the exact same problem. The phone won't connect via MTP or charge from a USB port (acts like it's not plugged in). The phone charges from AC or dedicated power supply. I found out that I CAN connect to the phone via fastboot, and even temporarily boot to a custom recovery. The easiest way for me to do this was via WUG's toolkit, go to advanced -> custom recovery under boot temporary. I haven't tried, but I imagine one could manually root this way.

At any rate, I'm thinking that this issue is caused by some kind of hardware issue with the system board. In my case, it followed a shorted out USB port on the phone. I've tried replacing the USB board on the phone, twice. Both of them exhibit the same behavior (above). No one seems to sell a replacement system board as a part, the only way to get one seems to be to by a used/broken phone. To me it's not really worth the money. I'd be better off selling it for the perfectly good screen and other parts.

I'm still not 100% sure this is where the problem is. Would love to hear from people who are sure they are having this exact issue. Again:

-Won't connect via MTP or charge from a USB port (acts like it's not plugged in).

-Charges from AC or other dedicated power source.

-Can connect to the phone from a PC via fastboot loader (try WUG toolkit)

-Strange looping behavior when powered up from totally off, unless you hold the power button for a long time, then boots normally.
[Samsung Galaxy Nexus] montrealguy:
I had the exact same problem. I tried all the software solutions out there. I put a pin in the usb hole and scraped/removed the dust and tried to lift the pins. After I lifted the pins, everything went back to normal and it was recognized by computer and charged properly.

If you've read through the many various threads on the issue, you'll find that almost everyone found it to be a hardware issue in the end. So its either the pins in your USB hole on your phone or its the pins in your cable.

If it charges from AC but is not recognized by MTP/USB port, then one (or more) of your pins is not making contact.
[Samsung Galaxy Nexus] smcgrath1111:
I agree that in most cases it has turned out to be a port pin/cable issue, but you might have overlooked the fact that in this particular thread, for both the OP and myself, the phone CAN communicate via USB:

.

So there is no way this can be a simple physical problem with the data path, in the port or in the cable. Furthermore, I have changed the USB port on the phone with a brand new one, twice (to be sure I didn't screw it up), tried different cables, tried different computers.
[Samsung Galaxy Nexus] montrealguy:
I reviewed the OP's first post and I had the EXACT same problem and same issues. It too was recognized in Odin. I could have written his post myself.

I was able to solve the problem by putting a clothes pin in the USB port and scraping it around. I must have gotten lucky. If you changed the USB port and cable several times, have you considered the possibility that a) either the port was not correctly installed or b) the connection between the port and the phone hardware was defective?
[Samsung Galaxy Nexus] smcgrath1111:
Hmm. I can't imagine what kind of connection problem to the USB port could cause an issue that selectively, but perhaps I have a limited imagination.:confused: I did consider the possibility that the USB board was not correctly installed, so I replaced it a second time, with another brand new part from a different supplier. I consider it possible, but unlikely, that I did this incorrectly both times. As for the connection between the port and the phone hardware, that connector is at the system board, so if that's the issue, I guess my earlier point applies, which is that the system board is at fault somehow, and replacing it would probably solve the issue.

I do have another identical phone that functions perfectly. If enough people are interested in the results, I will swap the system board in the defective phone with one from a known working GN, and do a full report of the impact (perhaps in a Youtube video?). On the other hand, if I'm the only one who's having this problem now, it's probably not worth pulling apart a perfectly good, working GN just to prove a point.

Either way, cheers, and thanks for your time and taking this seriously. :good:
[Samsung Galaxy Nexus] Mischaseb:
This bloody worked!!!! you're a champion!!!!!
[Samsung Galaxy Nexus] MrWind:
Hi All,

I am facing the exact same issue, Any news about solutions? Mine is indeed charging on A/C but not usb and not recognized by pc. I am on stock not rooted.

the plate is not bended, I have cleaned up the connectors, it is charging on usb when the phone is off and not anymore when I turn it on...

I am lost with that thing...

Thanks a lot in advance
[Samsung Galaxy Nexus] JogeTheMan:
I had almost same problem. I was able to charge my phone on the Usb but it couldn't recognize it. The solution was to just bend the pins on the micro-usb port.
[Samsung Galaxy Nexus] MrWind:
Yes thanks I looked at but that did not solve the issue,

Any other ideas?

Thanks!
[Samsung Galaxy Nexus] MrWind:
HI all,

I am upping here, I successfully flashed the factory image with the toolkit but still same issue....

I'm About to take a hammer and destroy my GNex...

Any ideas?

Thanks
[Samsung Galaxy Nexus] arvindar_n:
Bent Pins, Damn it!!

Can't believe it was something as simple as bent pins. I must have (some time in the past) forced the usb cable in such a way that the center pin structure of the USB port on the phone got bent to such an extent that any new attempts at inserting the usb cable bent it further without making any contact.

Straightened it out with a pen knife and voila! working usb port again :victory: . I'll have to be careful when I insert the usb cable from now on.

Thanks for the suggestion guys.
[HTC One X] JDR0iD:
Hi.

It happened to me earlier and I've seen a few people in the same boat.

So you flashed a zip, rebooted and stuck at splash. When rebooting to recovery it goes and sticks on splash and the only thing to work is fastboot.....what to do?

Don't panic its not a brick.

Hold power 7 seconds to restart phone, when off hold vol down to enter HBOOT.

Once in HBOOT press power to enter fastboot.

First try 'fastboot erase cache' and then 'fastboot reboot-bootloader' this should do the job, if this don't work, reboot into fastboot and try below.

On your pc open cmd and change directory to where your adb and fastboot are. Once there use 'fastboot oem lock' your bootloader should now say Relocked I think.

After that download RUU specific to your handset and run. This should install fine and return you to stock.

After done you may need unlock bootloader again, I did via HTCDEV and then reflashed recovery with 'fastboot flash recovery *recovery name*

Job done, phone restored, panic over :-)
[HTC One X] JDR0iD:
Hope this helps
[HTC One X] torxx:
So here a method which always works (many people have issues with flashing RUU's etc. having a bootlop.)

Download a RUU from here, thanks to Football!

Now open the .exe and make sure that it fully started.

Don't click anything, just go to windows icon and search for %temp%.

You will now find some folders, just search through these folders for the ROM.zip.

If you found it, you can copy it to your desktop or somewhere else.

Extract it with WinRar,7-zip or something like that and take the boot_signed.img and system.img.

Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)

Plug in your One X, go into the bootloader and go into fastboot mode.

Navigate with the cmd in the folder with the fasboot.exe and the two .img's.

Now type in that:

fastboot flash boot boot_signed.img

After that:

fastboot flash system system.img

If everything worked, just reboot:

adb reboot
[HTC One X] JDR0iD:
+1
[HTC One X] broncogr:
ok thanks for the thread

after fastboot erase cache

Do also a fastboot reboot bootloader.

Usually works after that
[HTC One X] JDR0iD:
Cheers mate op updated
[HTC One X] eggyenergy:
Hey guess who's got an one x broxD
[HTC One X] JDR0iD:
He got it has he?? After answer back to topic lol :) welcome aboard T
[HTC One X] mrwookie6379:
OP Just to save countless questions think you have missed a dash between reboot and bootloader as command should read fastboot reboot-bootloader if im not mistaken.
[HTC One X] JDR0iD:
Nort that I'm aware of buddy. I could be wrong but I don't ever remember using a - ??
[HTC One X] mrwookie6379:
Ok unless i'm using a wonky version of fastboot as just brought up list of command variants when I tried without....?:confused:

Heres a screengrab...
[HTC One X] JDR0iD:
Perhaps I'm wrong then
[HTC One X] broncogr:
EDIT: Sorry yes fatboot reboot-bootloader is the correct command

Sent from my HTC One X
[HTC One X] JDR0iD:
Op updated :)
[HTC One X] leventccc:
If your cid is none. You can't flash ruu because of 131 error. :(
[HTC One X] PG101:
This is what I did..

Flashed the official recovery from Bronco's thread.

Flashed LeeDroid... was at 50%.. then flashed ROMeOS, was down to 35%.. started setting up.. came down to 15% when all of my settigs were complete...

Rebooted to recovery for wiping cache and dalvik so I could just put the phone to charge.. did not reboot.. just went into Splash loop...

Can go into bootloader/fastboot... tried erasing cache.

Panick-stricken, reflashed the interim recovery, as I knew for a fact that I could charge it while off - charged over night.. this morning still on splash-loop.

Just flashed the stock recovery and turned off and put it on charge. Locked the bootloader (says "re-locked")

Downloading the stock rom.. i am hoping this is the exact stock as CID may not let me flash it..

I think now the only way left is to hope that the stock flashes and the phone boots..

Any thoughts?

EDIT: Can you effing belive it... sleepless night.. countless downloads... A simple factory reset - and its fixed!!!!!!
[HTC One X] wizard123:
+1 to this. Hit factory reset from Hboot and you will get into recovery to run a wipe/factory reset.

Many thanks ;)
[HTC One X] mick1475:
When I got into one I just restored stock from recovery. I did the long power press and then volume- .After that it was straightforward :)

Sent from my dishwasher
[HTC One X] Compie:
Dank U Wel werkt Perfect

Thanks work Perfect.
[HTC One X] Selech:
I did this today! Was about to freak out, but read it somewhere before this thread. I remember this happened to an older phone aswell..

Does anybody know what causes this? I know most people won't care as long as it helps, but I'm a little interested..

Sendt fra min HTC One X med Tapatalk2
[HTC One X] amacrobie:
+1

I've just gone through the unlock, factory reset, update recovery, install rom, update boot image, hang scenario. Was starting to get mildly annoyed but currently halfway through uploading the original EU 1.26 firmware.

Will try again shortly, of course!
[HTC One X] bece65:
Hello everyone,

as PG101 my phone wasn't booting anymore and i had only access to bootloader and recovery and didn't had any rom on the sdcard .

I finaly was able to flash the RUU by flashing the stock recovery and relocking it otherwise i had an error message during the progress : "battery lower than 30%".

If this can help.
[HTC One X] F4M0U569:
Everytime I run the ruu.exe it gives me an error saying that it cannot find my device..i have access to fasboot and recovery. I have no roms
[HTC One X] hkfriends:
you need install htc sync driver
[HTC One X] blueacidic:
my phone keeps rebooting into the bootloader, any idea how to solve? able to relock phone but not able to flash stock RUU because battery is low. I do know that charging is not support in recovery, but I plugged it to the ac adapter for sometime and tried flashing stock RUU it still says I do not have enough battery, any advice?
[HTC One X] hisham2k:
Same problem here....
[HTC One X] torxx:
I will write a little tutorial which always works.

You will find it in the 3rd post..

---------- Post added at 05:44 PM ---------- Previous post was at 04:55 PM ----------

For everyone who has issues with installing a RUU after troubles..
[HTC One X] Raz0rX:
can i downgrade with this "trick" from 1.28 to 1.26 ?
[HTC One X] jureca:
I have a same question with comantos the third post, some may say, pleaseee ....
[HTC One X] Raz0rX:
can someone test it ?!

I have a 1.28 Device in a bootloop and i will repair it.

The methode seems to be very nice, but im scared :(
[HTC One X] neo-kamui:
I tried it just now with 1.26 base. Cant flash the system.img due to some error...
[HTC One X] Chartist:
THank you!!! I am usually calm about boot loops.... but I have never had a sealed battery before. You are an absolute star.
[HTC One X] JDR0iD:
Its happened again when testing a rom and i have bootloop. the strange thing is fastboot cant find my device to run commands such as flashing boot.img or erasing cache now. will look into this i have no idea why
[HTC One X] JDR0iD:
does anyone know why I cant find my phone in fastboot (waiting for device) even when sat in fastboot on the phone
[HTC One X] JDR0iD:
now I get ***RELOCKED****

*****SECURITY WARNING****

edit :fixed install ruu in fastboot
[HTC One X] Onepagebook:
thanks in advance everyone if you have solution for the following situation :

I have exactly situation like the link here @ here:

http://xdaforums.com/showpost.php?p=24867611&postcount=16

after I relocked the phone, download RUU, but it says that I don't have battery over 30%..

so I shut down the power and put it on charge, (not charge from computer but wall-jack), but it automatically boot up into boot loader, then after like couple hours, the phone was shut down then no charge led on that. so what should I do for that?

the phone now is ike this shown on the picture,is that charging?

any suggestion is highly appreciate that.
[HTC One X] jureca:
There must be some command to enter the sd card, no one knows, something has to be.
[HTC One X] S2kT68m:
@ Onepagebook

which Recovery use you? On CWM you cant charge, only with Stock-Recovery. Even if the LED lights, it does not mean that the phone is charged. My bricked OneX (with CWM Touch Recovery) looks also if charged, but it does not. The battery was charged less than 30%, so I could flash no stock recovery. That was it. The phone was bricked. No ROM or Backup on SD, **** happens :(

i mean, the phone must "power off" to charge....
[HTC One X] neo-kamui:
I had the same issue. Just follow what is described in the third post. You have to use a Ruu specific for your phone though. O2 Germany in my case.
[HTC One X] Onepagebook:
OK, I have PG101 gave me lots of hints that finally I have got all that done.

Yes you have to flash stock recovery back before you relock the phone.

so once if you flash back that stock recovery.img, then immediately relock the phone

and then back to bootloader, power done, and then insert your USB into wall jack, not computer USB port. and you are 4 hours away to get you back to RUU.

my One-x is completely back as normal and happy flash again:)
[HTC One X] Transi:
"So here a method which always works (many people have issues with flashing RUU's etc. having a bootlop.)"

c:\ABD>fastboot flash system system.img

sending 'system' (957496 KB)...

FAILED (remote: (00000006))

finished. total time: 0.002s
[HTC One X] adrian522:
I have the same problem with the same error, I think we need the updated RUU for 1.28
[HTC One X] incident:
How did you flash the stock recovery without power in tbe phone?
[HTC One X] incident:
How did you flash the stock recovery without power in tbe phone?

from my HTC Sensation XE with Beats Audio using xda premium
[HTC One X] JKaye:
Hi,

I have the same problem and had insufficient power to write the .img file. (At least thats what the error message said)

So from the HBOOT menu I chose SHUTDOWN. The phone didn't try restart and I plugged it into my charger. When the charging light changes to green, you're fully charged and can write again.

Hope that helps.
[HTC One X] JKaye:
Recovered - all details in the link

Hi,

I managed to recover my phone, all the details are in my link:

http://xdaforums.com/showpost.php?p=25137469&postcount=39
[HTC One X] arnie105:
Dead One X

So I was using my phone and lost signal...initially I thought it was no network but after sleeping and waking to find I still had no signal I was a little concerned. So I pull the sim card out and get an error message to say no sim card inserted. Put sim card in another phone and it works perfectly ok.

So I reflash my rom, LeeDrOid V4 rom and still no network signal. I reflashed the nandroid backup, do fastboot erase chache and reboot. Phone gets stuck at the boot image...phone eventually goes flat. Put it back on charge and eventually the red light flashes. Leave it over night and the phone is still flat. Eventually get it to boot into the bootloader and and only have the option of Hboot showing...with a message underneath saying 'checking for sd card update...'

Nothing else happens - HELP!!!!

Phone will either boot to the HTC screen or to the bootloader but only has the Hboot option and nothing else.

Any ideas?? Any help much appreciated or I'm going to have to bin the phone....
[HTC One X] jmpmjmpm:
Even so, have you checked the phone can't be seen by fastboot by doing "fastboot devices" long shot but worth a try. If not my guess would be the flash memory inside the phone has failed somehow and would have to return to HTC.

This is why not having an removable sd and battery on this phone makes me so nervous
[HTC One X] arnie105:
Managed to get the phone to bootloader correctly, flashed it back to stock and it still does not work... I think there is a fault with the mainboard in the phone as the back of the phone is almost untouchable due to the heat coming from it from below the camera.

New phone coming via o2 under their phone faulty in the first 28 days...HTC will not talk to me coz the phone is unlocked via the official tool, as stated when you unlock...
[HTC One X] rohitbaba:
will this method work on phones with hboot 0.94.000?

its vodafone UK phone, I am trying to flash 1.26 RUU but it keeps giving error 140 bootload version error.

and everytime i relock my bootloader i get

RELOCKED

SYSTEM WARNING

should this work

thanks
[HTC One X] JDR0iD:
Why 1.26 why dint you flash latest? Relock bootloader and flash ruu that's what I did
[HTC One X] rohitbaba:
The Main reason for me relock and flash vodafone ROM as i wanted to send the phone to them for return but i guess relocking will still be seen as it was rooted and unlocked so no point flashing voda ROM, i will just keep using customer ROMs.

MY one of the issues was Multitasking but i guess i will have to leave with it, second issue was my phbone wasent working with vodafone sure signal box but with insertcoin's latest ROM its working fine.

however if there is a way to put phone back to how it came on day one then do let me know so I maybe able to send it back them.

thanks

Dev
[HTC One X] Nic.Nebude:
I try to flash system.img, but have same error like Trransy and adrian

Solution:

I flashed on relocked phone this rom by exe (not single system.img)

RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.401.9_Radio_1.1204.103.14_release_256469_signed.exe
[HTC One X] MattyOnXperiaX10:
Charge your battery for 11mins then try again

Sent From Nothing more Than my DROID RAZR
[HTC One X] zFr3eak:
just had the same and erasing cache didnt help. me helped booting temporarily into recovery with: fastboot boot xxx.img

maybe you want to add it ;)
[HTC One X] djkaija:
Stuck on android 'loop'

I wasn't holding vol down for long enough. D'oh!
[HTC One X] butters149:
how do i tell waht the correct RUU to get for my device?
[HTC One X] 4K_Dohc:
Hi, I've bootloop issue also. I've downloaded Renovate 3.0.0 rom... After install have this bootloop issue. What shud i do and where to start? Can provide all the link for me to download or steps to follow? I've tried fastboot flash boot boot.img, erase cache but not successful... how now?
[HTC One X] stevengw:
happened to me 2 times recently.. Thanks for the info.. It may hopefully cut down on the sweating when it happens lol.
[HTC One X] 4K_Dohc:
How to flash stock recovey? Where to get stock recovery? From stock RUU?

What command to type in cmd?

---------- Post added at 03:57 AM ---------- Previous post was at 03:06 AM ----------

Someone help me plz... battery couldn't charge to 30%... always in hboot & fastboot... restart and restart...