yashsingh1/xdaforums huggingface dataset:
[HTC One X+] Lucky Thirteen:
Make sure you downloaded the good RUU for your CID

Boot your phone in BOOTLOADER (Volume down + Power)

Make sure your phone is responding to adb command line with the following : fastboot devices (Enter)

Relock your BOOTLOADER : fastboot oem lock (Enter)

Rebooting

Boot the phone into FASTBOOT and then connect to the PC

Again make sure your phone is responding to adb command line with the following : fastboot devices (Enter)

If you have a your serial number in return you can run the RUU

Good luck!
[HTC One X+] darkwing66:
Thank you for not giving up on me ;)

Did all the steps you said and everything went well except for the problem still remaining. Would it make any difference if I try to extract the recovery and boot from the RUU as I have seen mentioned somwhere in the forum?
[HTC One X+] Lucky Thirteen:
You can give it a shot, but how are you gonna transfer the Rom.zip on your phone then?

Usually it's something like

Run the installer of the RUU with your phone unplugged.

Stop on the automated installer and put it aside on your Desktop

Follow this path in your computer : C:\Users\your_account_name\AppData\Local\Temp\{ABC1234D-56E7-8910-F11G-123AB4C56DE7}\{ABC1234D-56E7-8910-F11G-123AB4C56DE7}\Rom.zip (Your string will be different but the Rom.zip will still be there)

Extract from this Rom.zip : boot_signed.img & recovery_signed.img

Boot to fastboot, flash boot_signed.img and recovery.img .

Boot to recovery and flash the Rom.zip
[HTC One X+] darkwing66:
I figured if I manage to extract those files from the rom.zip then I could flash them with fastboot? But at the moment I´m even struggling with extracting the darn files...:mad:

Do you Think it will make any difference doing the flashing this way or just running the RUU.exe (wich in my case doesn´t work)?
[HTC One X+] Lucky Thirteen:
Hold on I will upload the International version of both of them for you...

Give me ~5 minutes

Edit (sorry if it took longer) :

Here it is :

ENRC2B_recovery_signed

ENRC2Bbootsigned

Hoping you will be able to do something with those. I'll catch later.
[HTC One X+] darkwing66:
:D

The recovery file can´t be dl, it says "This file, folder or group is private or does not exist."

edit:

Found one but still the same black screen and no recovery...
[HTC One X+] Lucky Thirteen:
Links fixed, Sorry!

First I just want the conformation that you are doing all this manually via a command window and not throught any sort of flashing tool, right?

Lets try those...

Test 1 :

Put this FILE in your platform-tool folder of SDK and do not rename it.

Plug your phone on your computer USB cable

Open a SDK/ADB command window

Type at the prompt> adb devices (Enter) (Serial conformation)

Type at the prompt> adb reboot-bootloader (Enter)

Rebooting in BOOTLOADER

Unplug your phone while rebooting

Once in FASTBOOT plug in your phone and make sure FASTBOOT USB is highlighted

Type at the prompt>fastboot devices (Enter) (Serial conformation)

Type at the prompt>fastboot erase recovery (Enter)

Type at the prompt>fastboot flash recovery TWRPrecovENRC2B.img (Enter)

Type at the prompt>fastboot erase cache (Enter)

Unplug your USB cable and hit Power once.

Select via your Volume rocker -> Recovery

Again hit Power button again​

Results?

Test 2 :

Put this FILE in your platform-tool folder of SDK and do not rename it.

Plug your phone on your computer USB cable

Open a SDK/ADB command window

Type at the prompt> adb devices (Enter) (Serial conformation)

Type at the prompt> adb reboot-bootloader (Enter)

Rebooting in BOOTLOADER

Unplug your phone while rebooting

Once in FASTBOOT plug in your phone and make sure FASTBOOT USB is highlighted

Type at the prompt>fastboot devices (Enter) (Serial conformation)

Type at the prompt>fastboot erase recovery (Enter)

Type at the prompt>fastboot flash recovery ENRC2BstockRecovery.img (Enter)

Type at the prompt>fastboot erase cache (Enter)

Unplug your USB cable and hit Power once.

Select via your Volume rocker -> FACTORY RESET

Hit your Power button once to confirm.

The phone should enter Stock Recovery mode and wipe EVERYTHING including "SD card" but also should fix all corrupted DATA (ROM, Directory, Etc)

Once done reboot your phone by holding volume down +power to enter manually the BOOTLOADER

Plug back your USB cable

Open a SDK/ADB command window

Type at the prompt> fastboot devices (Enter) (Serial conformation)

Make sure FASTBOOT USB is highlighted

Type at the prompt>fastboot flash recovery TWRPrecovENRC2B.img (Enter)

Type at the prompt>fastboot erase cache (Enter)

Unplug your USB cable and hit Power once.

Select via your Volume rocker -> Recovery

Again hit Power button again
​

Can you access Recovery now?
[HTC One X+] darkwing66:
I have used both toolkit and cmd, another problem is that I cant get "adb devices" to return my device. I have tried in win 8, win 7, and now ubuntu but no serial nr returned. If I try fastboot devices it works fine. Is it important to get the adb to work or could I use fastboot instead? I dont know how I can make it work, maybe its my phone thats the problem? I will try now to flash the file you sent me in your latest post. I very very much appreciate you helping me :)

edit:

Test 1:

The fastboot erase recovery returns - erasing 'recovery'... FAILED (remote: not allowed)

Fastboot flash.. returns -

C:\sdk\platform-tools>fastboot flash recovery TWRPrecovENRC2B.img

sending 'recovery' (7370 KB)... OKAY

writing 'recovery'... INFOFormat partition SOS done

OKAY

Erase cache - OKAY

After reboot - same problem :(

Test 2:

The same result as test 1...:(

Must be something is broken in my ***** phone!?
[HTC One X+] Lucky Thirteen:
Sorry I mislead you, there is no need to try adb since you cannot boot your ROM, simply start at fastboot devices.

Could you try this command in fastboot> fastboot oem unlock and tell me the results.

When in fastboot can you picture the screenshoot and upload it?
[HTC One X+] darkwing66:
The command returned:

C:\fastboot>fastboot oem unlock

... INFO[ERR] Command error !!!

OKAY

Strange saying OKAY when it returned error...

I read somewhere about another command - fastboot oem rebootRUU

returned:

C:\fastboot>fastboot oem rebootRUU

... INFOSave data from original MSC...

INFOSave data from SIF...

INFOUpdate partition data to SIF partition

INFOUpdate partition data from original MSC...

INFO[MSG] OKAY

OKAY

this made the phone show the HTC silver on black screen but then nothing. Also a command able to push zipfiles to the phone which seemed to work but I dont know what to upload to it....
[HTC One X+] Lucky Thirteen:
I have an Original international ROM in my computer, let me upload it, you could try to push it.

Give it some time should be ready in ~30-45 minutes from this time post.

ENRC2B_Stock.zip

Once pushed to your phone try to flash from this thread with fastboot :

recovery_stock

boot_stock

then erase cache and try to reboot.
[HTC One X+] darkwing66:
Once pushed to your phone try to flash from this thread with fastboot :

recovery_stock

boot_stock

then erase cache and try to reboot.[/QUOTE]

Sorry I did not get that, what exactly should I do after I hopefully have pushed your zip to the phone? :confused:
[HTC One X+] Lucky Thirteen:
Did you kept the unlock_code.bin file that you unlocked your phone with? (Should be in your Platform-tool folder)
[HTC One X+] darkwing66:
Yes, used it a couple of times now :)

Update:

C:\fastboot>fastboot oem rebootRUU

... INFOSave data from original MSC...

INFOSave data from SIF...

INFOUpdate partition data to SIF partition

INFOUpdate partition data from original MSC...

INFO[MSG] OKAY

OKAY

C:\fastboot>fastboot flash zip ENRC2B_Stock.zip

sending 'zip' (614939 KB)... OKAY

writing 'zip'... INFOCan not find [android-info.txt] in zipped image! What if there was a recovery.zip with the missing android-info.txt?

FAILED (remote: 24 parsing android-info fail)
[HTC One X+] Lucky Thirteen:
You should have tried this variant installation but I will give it to you anyway...

Enter bootloader / fastboot mode

Flash your stock recovery.img

fastboot flash recovery recovery_signed.img

fastboot reboot-bootloader

fastboot erase cache

Flash your stock boot.img

fastboot flash boot boot_signed.img

fastboot reboot-bootloader

fastboot erase cache

Now relock your bootloader

fastboot oem lock

fastboot reboot-bootloader

fastboot erase cache

Run your correspondent RUU and follow the onscreen instructions.​

Do you still have the rom.zip you extracted form your original RUU? You could try the dirty way of flashing!

You need to have the exact RUU for your phone CID, to find out, run this command in fastboot mode : fastboot oem readcid

Stay in bootloader mode with your phone on FASTBOOT USB

Click once on the Power button and be attentive at the writing that will scroll on the screen, watch for the line that says : Checking SD then on the other line it will say something like : looking for PG63IMG.zip (that file number is for my TELUS version probably yours will be different since you have the International version.) Take good note of the numbers.

Now that you have this rename rom.zip like this: PGxxIMG.zip (xx=numbers you saw) try to push this file to your SD card, if success, then have your phone to search for it in bootloader.

I really don't know if this will work since our phone are S-ON, but it gets harder to find a trick that will work with your phone. Make sure you have the original recovery & boot installed prior this and also relock bootloader. Or try any combination of this.

Let us know.
[HTC One X+] darkwing66:
Have tried all of the above now. After the "Dirty" flash the cmd returns the following:

C:\fastboot>fastboot oem rebootRUU

... INFOSave data from original MSC...

INFOSave data from SIF...

INFOUpdate partition data to SIF partition

INFOUpdate partition data from original MSC

INFO[MSG] OKAY

OKAY

C:\fastboot>fastboot erase recovery

erasing 'recovery'... FAILED (remote: not a

C:\fastboot>fastboot flash zip PM35IMG.zip

sending 'zip' (614939 KB)... OKAY

writing 'zip'... INFOsignature checking...

FAILED (remote: 12 signature verify fail)
[HTC One X+] Lucky Thirteen:
Why are you running this in a command window?

Honestly for now I am out of idea. When did you purchase your phone?
[HTC One X+] darkwing66:
Where else would I run it?

November 2012

Im giving up on this stupid phone, will take it to a local mobile servicepoint tomorrow and hear what they have to say. :mad:
[HTC One X+] Lucky Thirteen:
If you know that your PM35IMG.zip is on your SD card, try to flash it throught the bootloader by selecting Hboot with the power button. Let the bootloader find it.

In short...

Send the PM35IMG.zip to to your sd card

Stay in bootloader

Unplug your USB cable

Click on power

HBOOT will search for "sd card"... checking for PM35IMG.zip

Update should start.

But again, I am not sure if the bootloader must be unlock or lock for this to work, so maybe trying both to be sure.
[HTC One X+] darkwing66:
Will try :)
[HTC One X+] Lucky Thirteen:
We didn't tried the CWM Recovery, so here it is InterCWM.img put it in your platform-tools folder

fastboot flash recovery intercwmt.img

fastboot erase cache

fastboot reboot recovery (may not work, so do it manually)
[HTC One X+] darkwing66:
No did not work. I think something is broken in my phone, with all the great help you have given me it should have started to work.

Update:

After loosing my patience with my bricked device I decided to void all warrantys and crack it open just to have a look inside. I figured if I could make it powerless by removing the battery something COULD happen. And it did, after I had cut the plastic that surrounds the battery I was able to shortcircuit the battery (not a good thing really but what the heck) and Everything went black, dead. I thought I might aswell put it together again and put it away for it´s eternal rest, when it suddenly started and booted into a factory reset Sense. This was looking to good to be true and so it was, because after it had installed an auto update it rebooted and my old ******* problem was back.... tried again by doing the same thing but didn´t work this time. maybe I should try to remove the battery somehow?
[HTC One X+] darkwing66:
Still no recovery or RUU working..

Could it be memory problems maybe? Is there any way that I can list the partitions or the files and maybe wipe or format them without being able to get into recovery? Adb does not work either as I mentioned earlier. I really need some hardcore help here :)

Maybe I should set up a reward (Paypal) for the one that gives me the answer to my problem ;)
[HTC One X+] kingofnice:
fastboot erase cache

does the trick
[HTC One X+] darkwing66:
Unfortunately it doesn´t do the trick for my phone :(

What can keep my phone from starting after I have successfully (?) flashed stock RUU? At least everything seems to go well, but I suppose it does not because my problems are still there.

Anyone know someone in Sweden who can help me?
[HTC One X+] ratcom:
you are going to believe this but I've now got the same issue :crying: messing around in fastboot I've managed to get recovery working again by flashing cwm then back to twrp but no matter which rom I try to flash the phone always resets when writing to system? going to give it a few more tries before I give up :crying:

Oh and I cannot go the RUU route as my bootloader is higher than the only copy of vodafones RUU that available..... not happy at all

---------- Post added at 11:34 AM ---------- Previous post was at 11:14 AM ----------

OK after a hour of frantic panic I've managed to get it working again :D here's what I did.....

Flashed CWM to get recovery working ( fastboot erase cache everytime)

then from cwm I formatted system and factory reset

Then once I got recovery working I reflashed back to TWRP 2.4.4.0

from there I formatted data (internal sdcard area) this left the phone totally blank

I then sideloaded my rom from within twrp which work!

So although my error was with writing to the system it took formatting the data partition to clear things up :confused:

Give it try it may you with your problem?
[HTC One X+] darkwing66:
I am sincerely happy for you that you got your device back from the dead! :good:

Unfortunately the problem for me is that I just cannot get a recovery that works om mine :(

I have tried both CWM and TWRP and the flashing goes well but there is no difference when I boot. All my efforts stops at the quietly brilliant screen...

I will however not entirely give up, (I have just ordered a Samsung Galaxy S4) and I will gladly try any suggestions that you or anyone else may have. :)
[HTC One X+] darkwing66:
I just cant stop thinking about WHAT it is that makes my phone stop and shut off after the quietly brilliant screen?

Can it be only software problems or did my phone become damaged when it by accident dropped to the floor?

How is it possible that it started ONCE and then never more?

What is keeping the stock RUU from working as it should be returned exactly as it was when first bought?

Please share your thoughts with me and maybe we can solve this :confused:
[HTC One X+] ratcom:
I've got to think its the file system that becomes currupt, that explains why I was able to repair mine. With you not being able to boot into recovery I think the format commands that recover run should work from fastboot
[HTC One X+] darkwing66:
Could you please explain how? It feels like I have tried everything :)
[HTC One X+] ratcom:
i wonder if the following would clear any issues and allow recovery to work

>fastboot erase system

>fastboot erase data

>fastboot erase cache

then >fastboot flash recovery recovery.img

better still would be the commands recovery use to format the system, data ect
[HTC One X+] darkwing66:
The fastboot erase recovery returns - erasing 'recovery'... FAILED (remote: not allowed)

Same thing with the other commands. Not allowed to format i guess.
[HTC One X+] ratcom:
:( we need to find out the commands recovery run then... I'll keep researching
[HTC One X+] Lucky Thirteen:
The method for an S-ON device I think should be made via fastboot.

At the prompt type >fastboot oem format-all

or individually

>fastboot erase boot

>fastboot erase system

>fastboot erase data

>fastboot erase cache

Try to add this command if they don't work e.g. >$ sudo fastboot erase boot

Try to relock bootloader >fastboot oem lock and try again running RUU

or

Flash TWRP Recovery

adb sideload SuperSU.zip (install)

sideload rom_of_your_choice.zip (install)

flash boot.img

erase cache

reboot
[HTC One X+] darkwing66:
Sorry but these commands only returns FAILED (remote: not allowed) and the ADB is still not working :(

It feels like something has corrupted the filesystem and not even the RUU can get it right. I´m thinking about opening it up again and cut a wire from the battery and make the device powerless as a last attempt to revive it. It is bugging me that it started once when I had shortcircuited the battery.
[HTC One X+] ratcom:
Wow just had to follow my steps again after the same problem raised its head again this morning. On both occasions I had a freeze up while installing a rom then stuck at bootup :crying: clearly theres a bigger issue which seems to corrupt the file system randomly ?
[Galaxy Ace S5830i Q&A, Help & Troubleshooting] sdr1982:
I was following an old guide that showed an Odin screenshot that had Re-Partition checked and a PIT file selected.

Unfortunately, the text (which I skimmed past) said not to do either of those things.

Now my S5830i is stuck in a boot loop. I get the boot splash, then the glowing SAMSUNG text, then it goes back to the boot splash.

Stock Recovery and CWM both show errors mounting /cache, so I'm guessing I really killed the partition table. However, I can still get into Download Mode, so I'm really hoping there is a chance to save my phone!

All the guides I can find now say not to check Re-Partition or use a PIT ... but what do you do if you did? I can't find that answer anywhere on the forum.

If it helps to diagnose the problem, I used the following Odin setup:

Options:

X Re-Partition

X Auto Reboot

X F. Reset Time

PIT: cooperve_0623.pit

PDA: PDA_S5830iXXLH3_S5830iOXXLH1_RST_S5830iXXLH3_HOME.tar

PHONE: MODEM_S5830iXXLH3_S5830iOXXLH1_RST_S5830iXXLH3_HOME.tar

CSC: CSC_S5830iXXLH3_S5830iOXXLH1_RST_S5830iXXLH3_HOME.tar

Really hoping someone can help me out with instructions on how to rewrite the partition table and get back to stock. Thanks!

After trying it a second time, there are no errors mounting cache, but it now says (on first boot): "Failed to mount /data (invalid argument)"

If it helps, I am using Odin3 v1.87
[Galaxy Ace S5830i Q&A, Help & Troubleshooting] amogh420:
Use ODIN v3.07.

Get USB drivers if you dont have 'em.

Now once detected,

flash this PDA: http://www.4shared.com/file/Ls2CAsHv/PDA.html

P.S.: Do not touch any other option in ODIN, just flash the PDA file.

AND,

Redirect your questions here next time,

http://xdaforums.com/showthread.php?t=2089279
[Galaxy Ace S5830i Q&A, Help & Troubleshooting] ChelebiTech:
Ynt: [Q] Need debrick help: accidentally checked repartition in Odin on S5830i

I use pit file more than once and it did not brick the phone. Try to wipe everything in cwm inc dalvik cache. If it still gives errors try another firmware from samfirmware, last one is MB2 one i think. The italian one MB2 works fine in my phone.

S5830i Stock + Root + init.d + LightSpeed Intervention + Link2SD
[Galaxy Ace S5830i Q&A, Help & Troubleshooting] devo.dce:
Thank you

Thank you so much.. that PDA.tar really did help..

I was stuck at boot loop.

now it's fixed!!
[One (M7) General] pierrekid:
Don't flame, just points of notice...

But after reading some of the reviews about the battery life ( and it not being removable), reservations about blink feed, no sd card and the dexterity of the aluminum, the serviceability in case of malfunction and overall UI reservations, I think I will be sticking with the Galaxy note 2 and wait for either the s4 or note 3.

I have so much respect for htc [ had the one x, g2 and sensation) but I had to make the jump to Sammy after all the reports about the amazing note 2 ( I still consider it one of the, if not the, best phone on the market still) I had to make the jump. There is no denying the beauty of the of the htc one, but issues like no sd card ( basically have to plug phone into computer for efficient transfer of files, backup and restore), and no removable battery ( wtf htc? What if the phone freezes? What if I want/need extra battery life?) I just can't justify jumping from a great phone with amazing software in the note 2 to one with so many unfixable issues.

I want nothing more than to see great competition between these two power house Android manufacturers. Competition breeds progress in my eyes. But htc can't come up short on simple issues like serviceability, battery and lack of sd card and expect to compete with Sammy. Craftsmanship can only get you so far (look at the nexus 4, droid razor, DNA etc... already they are a thing of the past). You have to deliver on all fronts and htc, in my opinion, just missed the ball on this one.

Craftsmanship, serviceability, software, hardware, convenience and customer customization are the most important areas I think htc needed to focus on. Although they nailed some of these with flying colors, they dropped the ball hard on others. ..

What do you guys think?
[One (M7) General] ste1164:
I had the note 2 great idea but it was too big for me, I didnt like the feel of the device or the screen. The battery life has been fantastic for me personally most have said this. I think sense 5 is refined and a lot closer to googles holo than touchwiz will ever be. Blinkfeed isnt an issue just move it off to the side and remove feeds. Getting rid of it altogether would be a nice option. 32GB for me is fine I can use a Nexus 4 with no problem. Don't see anything wrong with the aluminium and serviceability by HTC will also be fine. I dont see why they would make a phone thats impossible for them to repair.
[One (M7) General] Reckless187:
Battery life is definitely an improvement over my One X. I can last a whole day of use, using the One in the same way as the One X.

I've personally never needed more that 32GB, I've always had about 10GB free on the One X. Not fussed about a removable battery as I drive quite a lot and can just top up the charge level in the car, although this is something I haven't needed to do with the HTC One!

It all comes down to personally preference and how you use the phone, which is why I've preferred the HTC's to the plasticy, although very nice Samsungs. Form AND function over function for me...
[One (M7) General] YoungAceAtlanta:
The choice is all up to you.. If you feel that Samsung is more your cup of tea than stick with Samsung if that's the brand you trust.

I don't think the battery is a huge issue being that I have a battery bank and plan on buying the mophie juice case AT&T have in their video.

And most my files is in the cloud so lack of SD slot doesn't bother me.

And if your phone freeze no matter what, if you hold the power button for 3secs it will reboot the phone.

All flagship phones will become a thing of the past once the latest and greatest comes out. The S3 is in the past just as the Note 2 will be once the Note 3 comes out. Not having a removable battery or sd slot doesn't shorten any device popularity if it was the flagship.