yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers HTC One X, Telstra One XL] cmorin4:
Thank you! This will help me out very much.

My one question for you is will this root process show a tampered banner once it has been done, specifically on the Rogers model?
[AT&T, Rogers HTC One X, Telstra One XL] Dakota0206:
http://thesuperusersguide.weebly.com/super-users.html

Become a Super User! Give-a-Ways are coming soon! Starting in July I will be giving away prizes monthly!

Have any ideas for the guide? Want to help write for the Guide? Let me know!
[AT&T, Rogers HTC One X, Telstra One XL] MaxGame:
Good stuff!
[AT&T, Rogers HTC One X, Telstra One XL] Dakota0206:
Added instructions for how to flash a ROM and how to flash a kernel. I will be working on the HTC One X pages this week so hopefully there will be many updates!

Let me know if there is anything you would like to see!
[AT&T, Rogers HTC One X, Telstra One XL] Dakota0206:
Added 3 more guides!

How To Install Android SDK & ADB

How To Use Face Unlock

How To Use Android Beam
[AT&T, Rogers HTC One X, Telstra One XL] mcmb03:
this is just me being a d*ck but in the list of articles.... this one >> "How To Take Use Face Unlock *NEW" :D
[AT&T, Rogers HTC One X, Telstra One XL] Dakota0206:
Good catch! Thank you
[AT&T, Rogers HTC One X, Telstra One XL] mcmb03:
no problem man! keep up the tut's. I'm sure they will be very beneficial to the noobs that at least know enough to search for something and read the stickies
[AT&T, Rogers HTC One X, Telstra One XL] Dakota0206:
I have taken down the How To Flash a Kernel links. I don't know how I forgot about the s-on with HTC devices. I should have it fixed tomorrow. Today is my birthday so I won't be getting a lot done today.
[AT&T, Rogers HTC One X, Telstra One XL] mcnutt:
Update for 2.20

Since the new exploit of 2.20 has arrived it might be beneficial for a tut on recovery, flashing boot.img and ROM installing. Which ROMs one can use might be helpful.
[AT&T, Rogers HTC One X, Telstra One XL] phishie:
Seconded.
[AT&T, Rogers HTC One X, Telstra One XL] carantinas86:
all links broken..
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Probably because this thread is ancient. I've already told you what you need to do in the thread you created.

Sent from my Evita
[HTC One X] Vitucastro:
I guess not posted here yet!

http://youtu.be/cuv0VMBkWZ0
[HTC One X] Gizmo_x:
crazy video
[HTC One X] AcoAlex:
damn,its water proff:p...BIG LIKE!!!:D
[HTC One X] MrIT:
never come s3;)
[HTC One X] Vitucastro:
I'm kinda confused, a lot of people complaining about screen being prone to scratch, a lot complaining about not being gorilla glass etc etc...

As the other guy how had his one x going down from the second window floor and still working fine.

Had switch my yellowish Xperis S to th one X that arrived at home today but i'm on a trip so tomorrow is a big day, huge expectation about it after frequenting this forum for like 2 weeks now!

Hopefully no screen flex, bad screen ripple, gps or any other issue!
[HTC One X] muamers:
How can that be possible :confused: cant belive ...:eek:
[HTC One X] stezo2k:
Wow these videos are amazing, at least i don't have to worry about my phone too much now. Especially after that one dude on here dropped his from a window and it survived
[HTC One X] farasatyarkhan:
Beat that SIII
[HTC One X] aeabilar:
Shock & awe!

just plain wow! Now I'm prouder with my HTC One X more than ever!:)
[HTC One X] Reckless187:
Next time I get into an argument with an iPhone or Samsung user, I'm gonna smash his brains in with my HOX!!!!

Even better, someone should do a phone fight off video, where they smash the phones against each other, like HOX vs SIII or HOX Vs iPhone!!!
[HTC One X] rawfa:
One day before my protective screen arrived I accidentally dropped my work phone over the HOXs' screen. It's a heavy blackberry and I was sure it would have damaged the screen. To my surprise there was not a single micro scratch there. Nonetheless the protective screen arrive and I´m happy to have it on :)
[HTC One X] Fakterr:
My HOX got run over

So today i dropped my HOX and my mates car ran it over... needless to say i was crapping my pants when i was picking it up to see the damage but to my surprise nothing!!!!! Not even a scratch, dent or anything! I am using a plastic case and a screen protector so that would have absorbed a lot of the punishment but still very happy no damage to the phone!
[HTC One X] averygagaanroid:
Yeah try this w your phone and see if its still working
[HTC One X] Fakterr:
No word of a lie bro! im not sure if it being run over the back wheel had anything to do with it but so happy my baby's alright!
[HTC One X] zkytmilad:
lol this is amazing
[HTC One X] hello00:
picture or gtfo(:

Sent from Mars
[HTC One X] Fakterr:
So you want a pic of my working phone? cause there isn't anyway that i'm going to let her get runover again haha
[Samsung Galaxy Nexus] lblacklol:
This might be a stupid question but I haven't been able to find it answered anywhere else.

I use AOKP as my rom, and AOKP by default uses Nova Launcher. Whenever you install a new rom, when you first unlock the device the first time, you're given a choice to launch the default launcher or nova. I of course pick nova and set as default, but I got to thinking, if you chose the default, there are widgets and things on that launcher. So, would it make sense to launch the stock launcher to clear out the unused widgets and icons and such off that launcher before switching to Nova?

For all I know those unused widgets aren't held in memory so it doesn't matter, but if it does, is it worth clearing them out?
[Samsung Galaxy Nexus] Herman76:
The launcher you select well reside in memory, and the other one will eventually be shut down. So there is no need to clear the other launcher.

If you're still unsure it should be quick to clear data on the unused launcher.
[Samsung Galaxy Nexus] martonikaj:
Only the launcher you select will run.
[HTC One X] sgh42:
Taking my HTC One X (unlocked) to the US on holiday for 3 weeks, can I get a prepaid micro sim & does anyone recommend one ?
[HTC One X] joshnichols189:
You can get a prepaid sim for AT&T at Best Buy or straight talk at Walmart. Either will work, but straight talk uses AT&T as well as T-Mobile so if you get a T-Mobile one you will only get 2G. In terms of Microsim you will have to have someone at an AT&T or T-Mobile store to cut the sim for you because prepaid sims are full size.
[HTC One X] jonshipman:
I would recommend the Straight Talk from walmart, but I haven't tried seeing if they sell sims in the store. Thought they were online only.
[HTC One X] 99RedB:
I've had great success with the T-Mobile USA PAYG SIMS from SIM Card Guru - takes a week or so for delivery. They'll even ship it pre-cut to micro-SIM size.
[HTC One X] drunkenclown:
Prepaid SIMs

Straight Talk offers a micro sim but it is only available online. You can choose either AT&T or T-mobile (I have the AT&T flavor). I have found their service to be very reliable. Good luck!
[HTC One S] vestasan:
Hello!

I recently bought HTC ONE S - amazing phone! Really like it so far!

But now I'm thinking - is it worth flashing custom rom, or leave it as it is...

I heavily use my phone - so stability and battery are a must! I do not use social networks - so ideally I would have them removed - i.e twitter, facebook, etc.

Can people please share their thought and experience.

I'm sure, this can become useful for all new owners.

Please sharу your expirience on using different custom ROMs.

And I do like HTC Sence very much, so ideally my ROM should be very close to stock ROM.

Thank you very much, look forward to your thoughts and answers :)
[HTC One S] jriv:
Flame flame flame flame...... Wrong section

sent from a guy living in a van down by the river
[HTC One S] torxx:
.. reported :)

BTW, all ROMs here are great, just test them ;)
[HTC One S] jriv:
I suggest trickdroid

:rolleyes::rolleyes::rolleyes:

sent from a guy living in a van down by the river
[HTC One S] torxx:
Me, too :)
[HTC One S] O_G:
Moved To Q&A​

This is a development section, its not for questions​
[HTC One S] azzledazzle:
if your gonna start a thread like this, why not add all the ROMs out there ? BinDroid ? ZyDroid ? Zero One S ??

And if your serious about this thread, Please change the OP and State that you do NOT want to cause a flame war, You just want to know what people prefer and why !?!?

Do NOT say which is better ? as this will cause upheaval and end up with the thread being deleted
[HTC One S] vestasan:
Thank you!

I really did not want to cause flame war! It;s not a funboy question - it's just a matter of choosinng between flashing custom rom or using stock rom.

I do appreciate all the developers here and I'm sorry about not mentioning you.

I since edited my post.

Not sure how to edit poll, so please, no flame wars.

BUT!!! Your expirience is highly appreciated!
[HTC One S] HighRoIIer:
I prefer any custom rom over the stock rom.

First Reason: I prefer to lower the density (210) and afterwords use more icons in the grid. at the moment 6x8

Second Reason: Free RAM. Around 150mb on stock rom and more than 250mb on custom rom

Actually i am on Leedroid. But was also on Trickdroid, CM9 and AOKP. I would prefer AOKP because of all the modding but at the moment i find the Stockbased like Lee and Trick more stable and better to use as a daily driver....

I realy like the Rom Cleaner script. It is so easy to make a no Sense rom out of any custom rom =)
[Eee Pad Transformer Q&A, Help & Troubleshooting] ramy_Maia:
Sorry if this may look like a long post, but i just tried to list all of the details, I really appreciate any help here :(

- It all started with the latest 9.2.1.24 OTA update, I went through the updates just fine, restarted and back in business.

- Been busy for few days, and didnt touch my tablet, it went out of charge, after recharging it, It started the reboot loop, it powers up , shows the Nvidia logo, then the ASUS logo with the spinning circle for 2 seconds or so then reboot again, ..

- When i lost hope I went into the cold reboot menu and chosen "Wipe All data" , the droid with the rotating cube came up and the loading bar is active under it, i thought it may take a while so i left it "OVER NIGHT" to find it the next morning in the same screen and very hot, restarting it would return to that same droid screen

- My final attempt was using nvflash , and flashed the stock blob.SOS , blob.SOS, blob.LNX, blob.APP (unpacked from asus stock US_epad-user-9.2.1.24.zip file)

- Now it's powering up then get stuck in the ASUS logo screen with the spinning circles (which are actually spinning), and sometime being on this screen it reboots on its won

Notes:

- It's a B90

- It was never rooted, and always updated with ASUS stock OTA updates.

- I didnt face such problem with the previous ICS updates

- I must have tried cold reboot like 6 or 7 times, left it to go out of charge and recharged it again, still the same.
[Eee Pad Transformer Q&A, Help & Troubleshooting] C4SCA:
Allways worked for me

1) http://xdaforums.com/showthread.php?t=1622628 (method 2/3)

2) http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html

make both steps and root/ unroot/ unbrick your TF101 easily (worked 9.2.1.21/ 9.2.2.3)
[Eee Pad Transformer Q&A, Help & Troubleshooting] Thing O Doom:
Try NvFlash for windows, it's easier and *will* work. Boot into APX mode with power+volume up. Flash the firmware.
[Eee Pad Transformer Q&A, Help & Troubleshooting] gee one:
So after it started bootlooping, it never went back into any rom?

I'm surprised that nvflash didn't work, but perhaps the bootloader isn't compatible. The nvflash part seems like a classic symptom of bad bootloader mojo. Be sure to flash the appropriate bootloader/EBT, as in, the one that came packaged up with the stock .24 rom. Update the bootloader - depending on your nvflash version it will be bootloader.bin or specified in the flash.cfg file.

sent from my transformer
[Eee Pad Transformer Q&A, Help & Troubleshooting] ramy_Maia:
Thanks for pointing this out, I was trying the linux version.

So .. I just used your new Windows version .. It looks like it flashed just ok ! I used stock blob.* files (I used stock .24 blob file)

D:\My Folders\Desktop\wheelie>"wheelie.exe" -2 --bct transformer.bct --bl boot
oader.bin --odm 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================

Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------

[=] Chip UID: 0x299506994287477335
[=] RCM Version: 0x20001

[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash

D:\My Folders\Desktop\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct -
configfile flash.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT sent successfully
sending file: blob.SOS
\ 4284416/4284416 bytes sent
blob.SOS sent successfully
sending file: blob.LNX
/ 4151296/4151296 bytes sent
blob.LNX sent successfully
sending file: blob.APP
/ 536870912/536870912 bytes sent
blob.APP sent successfully

D:\My Folders\Desktop\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]

after rebooting it's stuck at the same ASUS logo screen with the spinning circles (not in a rebooting loop, it's just spinning there for ages)
[Eee Pad Transformer Q&A, Help & Troubleshooting] ramy_Maia:
ftlast Laura,

No it kept restarting over and over

It's the Wheelie package , i am not sure what's the bootloader version coming with it
[Eee Pad Transformer Q&A, Help & Troubleshooting] Thing O Doom:
Please no credit to me, I'm not part of androidroot.mobi and did no work on this. All credit to them :3

--

Anyway

That's unheard of for it still not to work, try reflashing each partition individually, and make sure all of your parts start witn MSM - RADIO UPDATE.

EDIT: I attached a bootloader EBT blob that I know works, remove the fileexts and you should be good. blob.ebt.asus is the one you want. the other blob has my changed bootlogo lol.
[Eee Pad Transformer Q&A, Help & Troubleshooting] ramy_Maia:
Still thanks for making it in one package :)

Which parts exactly ? the blob.* files "these are binaries"

I am planning to do it manually using commands similar to the Linux ones ... are these correct ?

Starting the NVFlash mode manually with this command
D:\My Folders\Desktop\wheelie>wheelie.exe -2 -o 0x300d8011 --bl bootloader.bin -c transformer.bct

Flash separate blob.* files
D:\My Folders\Desktop\wheelie>nvflash.exe -r --download 4 blob.EBT
D:\My Folders\Desktop\wheelie>nvflash.exe -r --download 5 blob.SOS
D:\My Folders\Desktop\wheelie>nvflash.exe -r --download 6 blob.LNX
D:\My Folders\Desktop\wheelie>nvflash.exe -r --download 9 blob.APP
[Eee Pad Transformer Q&A, Help & Troubleshooting] Thing O Doom:
Use the get-partition table command to verify those numbers are correct. (Idk off the top of my head)

Open the blob with a hex editor and there's some intelligible text in there (along with a whole lot of gibberish code too xD)

The one I attached should be fine.
[Eee Pad Transformer Q&A, Help & Troubleshooting] ramy_Maia:
The blob file in extracted from ASUS zip has the MSM - RADIO UPDATE. string ... But the blob.* files generated by blobunpack does NOT have them

I get this error with your file :(

D:\My Folders\Desktop\wheelie>wheelie.exe -2 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================

Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------

[=] Chip UID: 0x299506994287477335
[=] RCM Version: 0x20001

[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash

D:\My Folders\Desktop\wheelie>nvflash.exe -r --download 4 blob.EBT
Nvflash started
[resume mode]
sending file: blob.EBT
| 1454788/1454788 bytes sent
blob.EBT sent successfully
[COLOR="Red"][B]bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: flags: 0
command failure: bootloader error[/B][/COLOR]
[Eee Pad Transformer Q&A, Help & Troubleshooting] ramy_Maia:
I take this back, i get the error with the manual flash. I restarted and ran the script reflash_sbkv2.bat, and it reflashed ok without errors

But again stuck at the ASUS logo screen

Now i am starting to think the problem is not with the bootloader but rather the other blob.* files which dont have the "MSM - RADIO UPDATE" in them.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Thing O Doom:
if they don't, then that's the inherent problem right there.
[Eee Pad Transformer Q&A, Help & Troubleshooting] ramy_Maia:
I downloaded other blob files from here

http://xdaforums.com/showthread.php?t=1683311

both the .21 and .24 blob.* files do NOT have that MSM... string at the beginning.

Any idea where i can download valid files ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] Thing O Doom:
Idk, and those should work. I'm atm totally ???

Try blobtools, boottools. To make your own from a stock one.
[Eee Pad Transformer Q&A, Help & Troubleshooting] gee one:
The individual blob parts, such as blob.SOS and blob.LNX are packed android images and should start with ANDROID!. These pieces are packed up into a blob, which starts with MSM Radio Update and a bunch of header information.

You can use nvlfash to flash the blob parts to individual partitions or you can use the staging partition to flash the whole blob, which will then flash the individual parts to their various partitions, specified when the blob was packed (EBT/SOS/etc.) and the partition table (from the flash.cfg file that was used when the tablet was nvflashed with the --create flag).

Be careful!

EDIT: Not all the blob parts will have the ANDROID! header- I think only SOS and LNX will have them. APP will be an ext4 filesystem. EBT will be a binary file.
[HTC Wildfire S] Raidillon:
i searched many many sites but didn't find anything.

im trying restore my wfs to stock rom and stock recovery.

s-on or s-off don't important.

ruu didn't work, i get error messages.

what i must do?
[HTC Wildfire S] pat da punk:
There is many how to's if you look

Try this...

http://xdaforums.com/showthread.php?p=21891784

If I helped hit thanks:)
[HTC Wildfire S] _Blizzard:
As my first post here, I wanted to make it something helpful. Anyway, you will need to find the stock recovery and use fastboot to put it on. Sorry, don't know where you would look to find one, maybe someone has one here?
[HTC Wildfire S] grayhawk11:
well as i understand you need to revert to device's stock condition

as far as i know only way to do it is by RUU or individually flashing every image. RUU is easily done but as you mentioned you get error messages try finding out what those error messages mean

common messages are

cant connect to device----ensure you are in fastboot usb mode

version problems----check weather you are using the right RUU (RUU is different for diferent regions) one RUU can have more than one versions so be sure which one you need

and you also need to lock you bootloader before running RUU

let me know if anything works

take a complete backup and make a goldcard just in case..you never know what may happen
[HTC Wildfire S] zedxda:
Actually, this 's-on' and 's-off' is very much important. You can flash any stock rom with s-off but not that easily with s-on. I'm a noob so I can't really explain further. Search for it!
[HTC Wildfire S] gq455402012:
which one do you need ?

http://115.com/file/e7471cfo TW2.33（download password：adbflash.com）

http://115.com/file/e7xci55n TW2.35

http://115.com/file/dpucqwbo CN2.35

just one key flash recovery（3e）and stcock rom，follow this：

http://xdaforums.com/showthread.php?t=1664533&highlight=no+recovery
[HTC Wildfire S] crossfire77:
i got same problem some days ago.cant port ruu and remove cwm.

so first of all you find your ruu from football's marvel collection or search on internet.if its in .zip file its very good extract it,you ll find recovery.img,boot.img and system.img

or if its in .exe file.first try installation wizard if its fail.again start installation wizard and then keep it on dont update bootloader just go to temp folder.(C:\Users\​[LoginName]\​AppData\​Local\​Temp​\​{82B23FCD-D5D0-45CA-A3A2-5350D3926551}) in this you will have see rom.zip file extract it.you ll find

recovery.img,boot.img and system.img then,

remove battery (power +volume down) to going in hboot then click on fastboot then plug your phone usb with computer open cmd and type:

fastboot flash boot boot.img

fastboot flash system system.img

fastboot flash recovery recovery.img

you can see fastboot file in your extracted zip.by this way you manually port stock rom.i tried it and it successfully possible.but i use my original stock rom,ages when i used europe rom it failed.

and please be careful in type commands it ll brick your phone if you doing anything wrong..maybe it ll help you

and yes one thing read this thread carefully i recommand third method which i mentioned here.

http://androidforums.com/htc-wildfi...arvel-a510e-gsm-software-version-2-3-5-a.html

good luck.:)

---------- Post added 3rd June 2012 at 12:06 AM ---------- Previous post was 2nd June 2012 at 11:54 PM ----------

and s-on or s-off.there are many difference between twos.i dont know much i m also noob here.but with s-off you can change your hboot,radio and many customization but with s-on its difficult i think.so i recommand you to flash your orginial stock rom if you are s-on.i have s-on phone so my phone wont remove cwm with any other stock roms and its got failed.so mind this thing.and know more about s-on and s-off read this.

http://xdaforums.com/showthread.php?t=1564650
[HTC Wildfire S] Raidillon:
I solved my problem using flashy program. it's very useful. I get the recovery.img from a stock rom's .zip, then flashed.

I exploited some messages in this thread, thanks guys!

Sincerely,

Kagan
[Xperia Play Q&A, Help & Troubleshooting] ignika98:
Hey guys I've been searching forever to find a solution to this but I can't seem to find one. So i'll ask here. I've recently upgraded my Xpreia play to CM9 ICS with DoomKernel to use the analog touchpads with N64oid. but the problem is, I can't overclock above 1.7 Ghz or it will crash, I've tried countless different ICS roms and kernels, but they do the same thing. I was able to overclock up to 1.9 Ghz on stock Gingerbread using DoomKernel, so whats going on?
[Xperia Play Q&A, Help & Troubleshooting] ridder215215:
I heard it depends on your phone. Some overclock to 2ghz, some to less. Mine crashes above 1.8. But I think 1.7 would be more than enough, don't you?
[Xperia Play Q&A, Help & Troubleshooting] ignika98:
It is, but it would be nice to know why it was working on Gingerbread and not ICS.