yashsingh1/xdaforums huggingface dataset:
[HTC One S] Wallya:
Oh I assure you fast boot and adb are set up correctly its the S3 model that's having issues getting the super CID I had noticed it didn't matter if it was on or off for the S4 version but other than that it didn't work for me and a few others. I read in the super CID thread.
[HTC One S] usaff22:
Haha you're on Optus, I used to have a contract with them.

Instead of SuperCID which doesn't work for some reason on S3s, try changing your CID to HTC__001. You do this by typing fastboot oem writecid HTC__001. If that succeeds, you should be able to use an unbranded RUU to take your device back to stock.

Sent from my locked, tampered ville
[HTC One S] Wallya:
You sure that will work? I'll give it a shot, but does that mean I can use any RUU from the list? Any you can recommend?

[Edit] Ok I tried and it failed, I tried about 4 times and it basicaly just gives me this:

C:\Users\Administrator>fastboot oem readcid

...

(bootloader) cid: OPTUS001

OKAY [ 0.010s]

finished. total time: 0.011s

C:\Users\Administrator>fastboot oem writecid HTC__001

...

(bootloader) villec2_init_sd, SD card already power on

(bootloader) [SD_HW_ERR] SD: No device attached

(bootloader) 902910 902E20

FAILED (status read failed (Too many links))

finished. total time: 1.318s

Its like it crashes the bootloader and i have to restart the phone after doing that command... Any ideas?
[HTC One S] tadaha:
Is your boot loader locked or unlocked?
[HTC One S] Wallya:
Unlocked offcoures...
[HTC One S] tadaha:
ok sorry, cos i've only seen that failed status when i tried to flash something thru fastboot with my bootloader locked (and yes i did that before).

sorry pal, don't think i can help much.
[HTC One S] Wallya:
All good I didn't know you could get into the boot loader when when its locked, heh you learn something new everyday.
[Galaxy Tab 2 Themes and Apps] Sean_Seany:
Taken from various ROMs. Copy to SD card and then extract to system/media/audio. These are

NOT

flashable.

Straight from a Nexus 4 sysem dump.

Alarms 8 sound files

Notifications 15 sound files

Ringtones 20 sound files

UI sounds 13 sound files

Nexus4_Sounds.zip - 3.28 MB

Straight from stock HTC Evo 4G

Alarms 16 sound files

Notifications 43 sound files

Ringtones 68 sound files

UI sounds 17 sound files

HTC_Evo_4G.zip - 18.92 MB

Straight from stock Nexus 7

Alarms 20 sound files

Notifications 70 sound files

Ringtones 94 sound files

UI sounds 13 sound files

Nexus_7_Sounds.zip - 6.69 MB

Straight from Samsung Galaxy Note II stock

Alarms 16 sound files

Notifications 43 sound files

Ringtones 68 sound files

UI sounds 17 sound files

Samsung Galaxy Note II sounds.zip - 18.94 MB
[Galaxy Tab 2 Themes and Apps] Sean_Seany:
More soon.
[Galaxy Tab 2 Themes and Apps] Sean_Seany:
Reserved for more.
[Galaxy Tab 2 Themes and Apps] ldaniel-jmz:
Excellent!

Excellent post! I would like Xperia series sounds too.
[Galaxy Tab 2 Themes and Apps] scottx .:
Why post those old evo files?

Good post though. I'm sure someone will want them.
[Galaxy Tab 2 Themes and Apps] krupukalengan:
Good job. Thanks. But I need to convert from ogg to m4a to make it works on my tab. Way to go.

Sent from my GT-P3100
[Galaxy Tab 2 Themes and Apps] Devin.Morris.007:
In for more!
[Samsung Galaxy Nexus] CallumMarks77:
does anyone know where i can find the images for the default nav bar.... i love the baked rom version 6 soft keys but i love the jbsourcery rom and i want to find the images for the nav bar on bb6 and use them on jbsourcery so does anyone know the file location of these images?
[HTC Wildfire S] Jayson Woodham:
Im surprised no one thought of it, i mean if there are people with ics roms and that is still buggy, then 3.0 should work, and then we can maybe make sense 3.5 run on android 3.0 so it'd be better, so devs I hope ur reading this.
[HTC Wildfire S] asdot:
Why? Because wfs isn't tablet.

Sent from MARVEL JellyScream
[HTC Wildfire S] sukhjit321:
Android 3.0 codename Honeycomb was developed for tablets. Hence no use.
[HTC Wildfire S] kantry123:
U should have known what's Android 3.0 is..?

Its only for tablets not for our phones..!
[HTC Wildfire S] TheProphetC3:
its for tablets dude...check it up
[HTC Wildfire S] goodguy25:
Plus the source didn't get released so the only Honeycomb ROMs are the ones that got released with it.
[Sony Xperia P, U, Sola, Go] naaney:
Hi guyz,

I'm planning to say goodbye to stock firmware and changing in cm9 . Im now wondering if i should take a stable cm9 from the cyanogenmod website or the one from fxp or are they the same.

Thanks in advance
[Sony Xperia P, U, Sola, Go] Felimenta97:
They are the same.
[HTC ChaCha] alexanderfoti:
Hi all

My HTC cha cha has died. The battery ran out and the phone turned off. My friend then turned it on again where it powers on then off. Since then it won't charge.

I have tried the PC USB cable. The wall charger and 2-3 other wall chargers but the power light won't come on and I can't get any signs of life. Any ideas?
[HTC EVO 3D] EnesGTR:
Hey Everybody...

I Downloaded a few minutes ago the App Screencaster Pro...

But it doesnt work :(

It says:"Waitung for Service"

How can i Fix this?

I'm Using CM10 -Unofficial- on my Evo3D

Any Ideas?!
[HTC EVO 3D] iron and wine:
googled your problem and it seems like there are others who are experiencing the same problem on cyanogen.

perhaps you could make a nandroid and see if itll work on a different rom? just to make sure that it's not the app.

cant help you on how to make it work on cm though
[HTC EVO 3D] EnesGTR:
Try'd another version from the app, and now works great :)
[HTC Sensation] jheysl2:
Can anyone point me in the direction of a guide or quickly explain how to return to stock rom on Sensation XE please.

Details of phone:

S-OFF

HBOOT: Revolutionary Pyramid PVT 1.27.1100

FIrmware 3.33

ROM: Bruce's JellyBean Rom
[HTC Sensation] Sh0wt1me:
Hi :)

hope this thread helps:

http://xdaforums.com/showthread.php?t=1672425
[HTC Sensation] jheysl2:
Thanks mate, I remember seeing this thread ages a go but couldn't find it again
[HTC Sensation] mad.mike:
Hi, don't mean to hijack but my question is on the same topic. I've got a Htc Sensation XE which came branded on 02 Ireland. I since installed cm9 on it but would like to return to stock now as I want to use tv-out. My question is could someone please link me to the correct rom ruu. I can give you all the info you need, I have read the guide linked above and tried installing the generic european one but I just got stuck in bootloader. Been at it all day and am just totally stumped.

My phone details are.

S-OFF

HBOOT: Revolutionary Pyramid PVT 1.27.1100

FIrmware: 4.0.4

ROM: CyanogenMod 9.0.0-Pyramid

I changed my cid to 11111111 also but that did nothing.

So if anyone could point me in the right direction the help would be much appreciated. Thanks
[HTC Sensation] malybru:
Hi,

You have s-off,so you should be able to run an European RUU

You also have supercid,so it is just a question of getting into bootloader,plug in your USB cable,and run the RUU from your PC.

:)
[HTC Sensation] mad.mike:
Thanks,I'll give it another go. And while I have your attention could you point me towards the ruu that you would use? I can't put any links in my post as I'm only new but there are a few on the filefactory website and I wasn't sure which one I should be using.
[HTC Sensation] malybru:
Hi,

Try :

RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R2_Radio_11.69.3504.00U_11.22.3504.07_M_release_253443_signed.exe

Don't worry if it's the wrong one,it will just give you an error.

Then,just try another.

:)
[HTC Sensation] mad.mike:
Sound, I'll give it a go. Thanks again.
[HTC Sensation] kaloenneli:
Hi everyone

I have a questions related to this topic

I successfully managed to S-On my phone with the stock ROM

But now i have 2.3 android installed. When i tried to update it it said: software new, nothing to add...

how do i manage to get it over my phone ? or do i have to flash everytime from now on the new RUU ROm ?

Greets

(Sensation XE)
[HTC Sensation] ganeshp:
now that you are on stock rom

you will get software updates based on your cid

verify the cid and also verify the devices with same cid have got ICS or not
[HTC Sensation] kaloenneli:
so it is now what ? when i rooted it i changed it to 111111. Is it now still 11111 ?

To what do i change it to be able to get OTA updates ? Is there a guide ?

Thx for your help, appreciate it very much :)
[HTC Sensation] malybru:
Hi,

Try CID Getter from the market,and see what that throws up.

:)
[HTC Sensation] kaloenneli:
CID getter tells me "CID is [11111111]

so what now ?
[HTC Sensation] malybru:
Hi,

OK,

To find your original cid:

Type

getprop ro.cid

in a terminal on your phone .

:)
[HTC Sensation] usaff22:
CID 11111111 will not receive OTA updates, HTC__001 and others will
[HTC Sensation] kaloenneli:
terminal tells me 111111 too ? oO

---------- Post added at 06:55 PM ---------- Previous post was at 06:09 PM ----------

changed it to HTC__001 but still unable to OTA updates ...
[HTC Sensation] malybru:
Hi,

Look for your's HERE

:)
[HTC Sensation] kaloenneli:
i have a unbranded HTC Sensation XE, carrier:orange

so i would asume i would have to take HTC__001

but i tried ORANG104 but i get this

and getvar cid gives me HTC__001 as answer
[HTC Sensation] ganeshp:
Once you change the cid

Do a reboot of bootloader using

fastboot reboot-bootloader

Then check the cid
[Galaxy S II Q&A, Help & Troubleshooting] ghadap:
Hello everyone..

Sorry if this thread is similar any other intro available here. My previous device was LG O2X, and now SGS2 (GT-I9100, Malaysia). My mind still stuck with LG's environment (ROM tools, region firmware and so on). I've tried to understand all the device properties, but still i can't understand any of it. Here is my questions:-

1) Can someone teach me how to read and understand all the numbers+alphabets in the "About Phone"? How to know my ROM is specific for

SEA region?

2) For stock firmware, is it only available at SamMobile website, or also available here (XDA Development area)?

3) Is the firmware update different with other region? Like mine is 4.0.3, but red there is 4.0.4..

Thanks in advance to whoever answer this thread. Really appreciate it. Thank you again. :angel:
[Galaxy S II Q&A, Help & Troubleshooting] Sun90:
Here is my questions:-

1) Can someone teach me how to read and understand all the numbers+alphabets in the "About Phone"? How to know my ROM is specific for

SEA region?

U can check the build number in 'About phone' and serach on XDA to no more about the same or google it

2) For stock firmware, is it only available at SamMobile website, or also available here (XDA Development area)?

Alternatively u can dwnld the same from HERE

3) Is the firmware update different with other region? Like mine is 4.0.3, but red there is 4.0.4..

Connect ur phone to 'Kies' and see if any update is available for ur region
[Galaxy S II Q&A, Help & Troubleshooting] ghadap:
Thanks Sun90...

Ok, mine shown XXLPQ.. does it means "international ROM"?
[Galaxy S II Q&A, Help & Troubleshooting] Sun90:
AFAIK it is a MultiCSC rom so has to be an international one:)
[Galaxy S II Q&A, Help & Troubleshooting] theunderling:
There is a thread which breaks the numbers/letters down to show countries/versions etc.
[Galaxy S II Q&A, Help & Troubleshooting] ghadap:
Well.. feels like having "culture shock" right now.. thanks everyone for the reply.. just want to make sure which ROM is for my region..
[Galaxy S II Q&A, Help & Troubleshooting] theunderling:
Theres dozens of variants and loads of roms.Your hit with all that and its daunting.

You just post the info you see in settings>about phone or dial *#1234# and you get faster/more accurate help.

You have loads of choices what to do next.You can just upgrade to 4.0.4 and leave it at that.Or do that and only root(means you can remove bloatware and use apps that only work on root).

Theres also a couple of things you may need to know if your planning on not solely staying on stock stuff.

eg 4.0.4 brickbug/efs backup/nand backup.

Just post if you need more info.
[Galaxy S II Q&A, Help & Troubleshooting] ghadap:
Now im getting really3x confused.. Attached is my phone abouts and versions, but seems i cant find my factory default firmware versions. And also my Kies says "your device does not support software upgrading via kies".. :confused:

Note: My plan is to use totally stock ICS, root, remove unused apps and services, use CPUEditor (force dual-core) and edit framework to AOSP ICS.. Firmware to look for is for SEA region (Malaysia)
[Galaxy S II Q&A, Help & Troubleshooting] -Grift-:
Ok mate a small break down :)

Getting Malaysian firmware

Singapore and Malaysia both use DX for firmware. For example i am using

DXLPA

Red section stands for the region in this case Malaysia Singapore

Green stands for the firmware version there are lots e.g. LP9 LPB

The latest one is DXLPF for Malaysia.

So from what i see the one you are using is not for Malaysia so this is what you do. (THIS WILL WIPE AWAY ALL YOU APPS)

1. Check this out Flashing Firmware with Odin

2. Download Odin

3. Download Malaysia latest firmware here

4. Boot into stock recovery ( When phone is off press

Home+Vol up+Power buttons

)

5. Do a factory reset

6. Now take battery out and boot into download mode ( When phone is off press

Home+Vol Down+Power buttons

)

7. Follow the steps to use odin

8. Now when update is done phone should run the proper Malaysia firmware

9. Download this into the phone here

10. Make sure CSC is set to XME

11. Done. Now you got pure Malaysia firmware

Ok now for rooting

DO NOT USE ROM MANAGER FOR THIS PHONE!!!

Im not sure about the 2X but samsung phones are different. Think of it as the recovery and kernel as one package. Some phones the recovery is a img while the boot is a whole other img but for samsung phones its all in one. To "root" your phone you must flash a kernel which will at the same time give you CWM. (but after doing this you can no longer get official samsung updates, so i recommend you rather jump straight to custom rom)

For getting custom rom:

1. Download any version of CWM from here

2. Download your desired Rom/kernel or both

3. Place files in externel SDcard

4. Boot into stock recovery (Press Home + Power + Vol Up) when phone is off

5. Flash the temp recovery from the stock recovery

6. Do a backup

7. Wipe the usual stuff data/cache

8. Flash accordingly

9. Reboot

10. Now you got custom rom + stock rom backup

For getting root/custom kernel + CWM only:

1. Download any version of CWM from here

2. Download desired kernel

3. Place files in externel SDcard

4. Boot into stock recovery (Press Home + Power + Vol Up) when phone is off

5. Flash the temp recovery from the stock recovery

6. Flash kernel

7. Reboot.

8. Now you got root + CWM

My recommended

kernel : Dorimanx

Rom : Resurrection Remix (ICS or JB)
[Galaxy S II Q&A, Help & Troubleshooting] ghadap:
Thanks grift.. Now i understand.. No wonder there are lots of users using custom kernel.. Will try your methods and link tonight..

Edit: There is no way on earth to maintain the stock kernel, when i root and use CWM is it? I HAVE TO USE custom kernel, by hook or by crook. I can't just root, then install CWM from PlayStore right?

Sent from my Thoughts using Telepathy :banghead:
[Galaxy S II Q&A, Help & Troubleshooting] -Grift-:
Rom manager is not compatible with the i9100... yes its in the app but it bricks phones. Another method... http://xdaforums.com/showthread.php?t=1746794 no recovery but has root and BB. I never tried that before
[Galaxy S II Q&A, Help & Troubleshooting] ghadap:
Is it because of "Insane chip" brickbug thingy? Now Im worried what Im going to do..

Sent from my Thoughts using Telepathy :banghead:
[Galaxy S II Q&A, Help & Troubleshooting] ghadap:
The firmware you linked for me, to use in Odin, just select at "PDA" section right?

Sent from my Thoughts using Telepathy :banghead:
[Galaxy S II Q&A, Help & Troubleshooting] Many40:
Yes (for .tar or .tar.md5 rom files). In PC odin leave everything default (don't tick re-partition!)

Edit: It happens that a rom comes with 3 files - then PDA, PHONE and CSC should be selected accordingly.
[Galaxy S II Q&A, Help & Troubleshooting] ghadap:
Thanks Many40.. I have another question though..

From what I red, this Brickbug is caused by CWM that certain version is not compatible with SGS2.. This makes me feel afraid to change my rom/bb/kernel to Malaysia standard.

My plan is:-

1. Flash Malaysia rom with Odin (as

linked)

2. Root

3. CWM (this is confuse matter)

4. Bloatware removal using

RootExplorer

5. Minor tweaks (CPU Editor, init.d,

bla bla bla..)

My goal is to keep stock as possible, with my own tuning. I've played with O2X, but never heard that CWM causing total brick like this. Hope you / any experts out there can guide me about this, since Im still newbie about SGS2.

Info: The attached pics were my device firmware info (bought from a friend who doesn't know anything about SGS2 Development, and said updated ICS through Kies).

Sent from my Thoughts using Telepathy :banghead:
[Galaxy S II Q&A, Help & Troubleshooting] Many40:
Hi, Super brick bug is not caused by CWM itself but when you perform some operation from (doesn't matter) stock recovery or custom CWM recovery. This operation is eg. wipe data/factory reset.

So, you are exposed to this bug if you have a kernel based on sources where MMC_CAP_ERASE is present and your eMMC chip is insane. AFAIK all stock ICS 4.0.4 kernels are concerned.

So, if you decide to switch to ICS 4.0.4 you will be saved from the bug if you flash a kernel which has MMC_CAP_ERASE set to "0" (disabled).

Staying on stock kernel on ICS 4.0.4 is very dangerous.

In this case I recommend (still to be as close to stock as possible) to:

1. flash your rom via odin

2. just after flash this: PhilZ-CWM6 kernel via odin as well

This kernel is a stock kernel with root, custom CWM recovery and MMC_CAP_ERASE disabled (super brick bug - safe)

3. Then you can continue with point 4 and further

BTW The rom from the pictures: XXLPQ / OXALPQ it's Polish unbranded ICS 4.0.3 (not exposed to super brick bug).
[Galaxy S II Q&A, Help & Troubleshooting] theunderling:
With what Ive read it is you that is battling against yourself(if you see what I mean).If you want as close to stock as possible then

If the lastest stock malaysia rom is 4.0.4 then thats the one with the brickbug in it.

So to counteract that,you flash a kernel that protects you from that.

But you dont want to do that as then its not as close to stock.

You have a few options,but if you want 4.0.4,then its best to get away from stock kernel.

If you stay on 4.0.3 then you have nothing to worry about.

I dont know the benefits of going from stock 4.0.3>4.0.4 as I use GB.

I do know that a lot of people get nothing but trouble using 4.0.4.
[Galaxy S II Q&A, Help & Troubleshooting] ghadap:
Ok.. I understood more with this explanations.. Correct me if im wrong..

1. I've check at sammobile, latest Malaysia rom is still 4.0.3.. Does it means that this rom version is safe from "brickbug"? (for stock recovery and CWM recovery)

2. Before I begin flash, rom file from sammobile only to be used at "PDA" section, is it? At which website that gives separated rom files?

3. Is there any other methods to root, else than using Odin with custom kernel?

"Hope this post will be my last confusion matter.." :)

Sent from my Thoughts using Telepathy :banghead:
[Galaxy S II Q&A, Help & Troubleshooting] Sun90:
1) yes 4.0.3 stock ics roms are safe from Brick bug for sure ma8:)

2) yes u have to use the "PDA" section and leave "repartion" unchecked:) u have to install samsung drivers first on ur PC for it to recognise ur phone:)

3)rooting thro ODin with custom kernel like siyah or Dorimanx is the best way for u since they r tried and trusted:)

hope things are clear for u know;)
[Galaxy S II Q&A, Help & Troubleshooting] ghadap:
Lets say that I want to stay my default rom stock ics kernel.. Will I be able to root (without any other kernels) and install CWM (Rom Manager) as I've done to my previous phone? Just curious.. :)

Edit: Sorry guys.. Such a silly questions.. Found all the answers already.. Silly me.. :screwy:

Sent from my Thoughts using Telepathy :banghead:
[Galaxy S II Q&A, Help & Troubleshooting] ghadap:
Now I'm screwed a bit.. at Sam, it says 4.0.3.. when I done flashing, it shows 4.0.4.. Moral of the story; don't root yet+wipe anything+don't do anything.. Maybe i'll just wait for official 4.1.2? :silly:

Edit : Is it compulsory to "wipe data" when flash using Odin? I flashed my device with this ROM; I9100DXLPF_I9100OLBLPF_XME, from sammobile. It says 4.0.3, but turns out after flashing it, actually is 4.0.4 (About Phone properties).

Im not 100% sure. Is it safe for me to do this steps?

1) With Odin, I flash other official rom from sammobile (I9100DXLPB_I9100OLBLPA_XME or

I9100DXLP9_I9100OLBLP9_XME), without wipe anything..

2) If the flashing process successful, I just continue use it since data is still intact.
[Galaxy S III Q&A, Help & Troubleshooting] SPLucas26:
Ok ,so heres my problem:

My S3 (i9300) wont connect to my computer which is running windows 7. I plug it in, and there is no sound for a device connected, no confirmation, and all the gs3 does is charge. it doesnt even show the little usb symbol at the top on the status bar. i've also tried two different cables, two computers, and ive cleaned the usb port on the phone.

This is all pretty recent as well. it used to connect fine on stock and the same on cm9, but one day when i plugged it in, it said unrecognized device, and from then on, the computer doesnt even know its connected anymore. i restored back to my original stock backup that had worked fine before, but still no progress. Kies has been uninstalled and reinstalled multiple times and so have the drivers for samsung phones..
[Galaxy S III Q&A, Help & Troubleshooting] speedyjay:
Download, extract and install, then try again :)

---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------

http://db.tt/TSzlg0lI
[Galaxy S III Q&A, Help & Troubleshooting] SPLucas26:
Nope, no luck :(
[Galaxy S III Q&A, Help & Troubleshooting] SPLucas26:
Does anyone else have any input or ideas? I'd really like to solve this...
[Galaxy S III Q&A, Help & Troubleshooting] da.trute:
going to be a driver issue if it charges, install KIES first as that provides the necessary samsung drivers too. If this doesnt work then uninstall the USB controller you phone is connected to, unplug the phone and reboot. Leave the phone out and install KIES again.The try again.

Could be your cable too though, have you swap tested anything yet, does a different cable work or does the cable work ok in another PC?
[Galaxy S III Q&A, Help & Troubleshooting] SPLucas26:
I'm reinstalling KIES right now and ill try it with two different usb cables. If neither work, then ill try uninstalling the usb controller as you said and then go through the process once more. ill get back to you on it all when I'm done.
[Galaxy S III Q&A, Help & Troubleshooting] Simonetti2011:
I have a few no-brand, cheap microUSB cables that allow only for charging the phones: they don't let me get a data connection between the phone (or whatever) and the PC.

Other USB cables work ok, so I know the problem is not with the phone.

You don't need (and shouldn't) install KIES only because of the drivers.

The only drivers you should install from the only trusted source are these:

http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
[Galaxy S III Q&A, Help & Troubleshooting] leeznon:
I had the same problem.

I tried EVERYTHING. I did tons of research and tried them all, nothing worked.

I fixed my problem by sending my phone in and getting it fixed. I think they replaced the hardware.

Your phone is likely having a hardware issue, get it sent in, this is the only way.
[Galaxy S III Q&A, Help & Troubleshooting] SPLucas26:
since this option is really quick to try, ill do that right now.

As for the cable I'm using, the one that I've been trying the most is the one that would work before i started having these issues. The other cable that i have is the one that came with my phone.