yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] LandUzu:
I am looking to flash a ROM to my SGS3 but have to start again as a noob.

I have used mskips tool to root the phone ( i think :) ) In the tools menus it gives an option to download a stock ROM from samsung-roms i think and it gives some different versions that end in:

XXALE8

XXALEF etc, etc

What do these refer to and how do i find what is suitable for me/most up to date.

My carrier is T-Mob UK and the letters from my Device Info page is BVALE4...not sure it is the same thing yet but im guessing so. I am first looking to try a stock/rooted ROM and then i will probably move up to custom stuf once my knowledge grows a little...along with my confidence. :) Any pointers welcome.

Best Regards

LandUzu
[Galaxy S III Q&A, Help & Troubleshooting] -josh-:
Think this thread may contain the information you are looking for

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

Also for all the custom roms

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

-JOSH-
[Galaxy S III Q&A, Help & Troubleshooting] curls1:
Im also on Tmobile uk just flash the stock samsung firmware this will unbrand the phone and get rid of any tmobile bloat ware.

latest Uk unbranded firmware is XBLG6

ps Hi to J0SH another Hull member:D
[Nexus 7 General] cfh:
I was one of the early pre-orders and received my Nexus 7 last Tuesday evening (7/17).

Like most users, I checked it out for problems: screen, mic, etc.

Everything checked out fine.

I did some customization, downloaded some apps, tried out all the new features.

Everything worked well.

I had connected it to my PC, no problems. Rebooted it, no problems.

After about 6 hours, I put my Nexus 7 to sleep (not shutdown) and

started to prepare to go to sleep myself.

After about 5 minutes or so, I decided to download one more app.

I tried to wake up my device -- and it would not wake up!

I tried a long press on the power button -- still no good.

Thinking maybe the screen had gone bad, I tried to connect

it to my PC to see if it could be recognized -- no good!

Yikes, could my Nexus 7 have died? I decided to try

to charge it, plugging the charger into the wall. No little

charging icon showed up on the screen :(

I decided to just let it charge overnight and see what happens.

The next morning, the Device still would not power up :(

I called google play and told them my story and they

said they would start the process of sending me a new

Nexus 7.

I started looking on the Forums, to see if anyone had

the same experience. Some people suggested that

I hold the power button down for 30+ seconds.

I tried, 30, 60, 90 seconds ... still no good.

Over the following days, while waiting for my RMA process to play out,

I would periodically pick up my Nexus and try the power button -- no good.

Today, 9 days later, on a whim I decided to again plug my device

into the charger. Believe it or not, the charger icon went on!!!!

After charging it for about 90 minutes, I booted it up and everything

was working again!

The replacement Nexus has not shipped yet, so I have a few days

to see if this problem occurs again.

My guess is that my device got into some hardware freeze situation.

The battery finally ran out of juice which caused the machine to

completely shut down -- which allowed me to re-charge it today.

Any other thoughts?
[Nexus 7 General] e.mote:
>Any other thoughts?

Maybe you can give the hidden reset button a try the next time?

NB: For the unfamiliar, a video teardown showed a reset button at top of the unit, but no hole through the casing to access it.

http://www.youtube.com/watch?v=GoDAg8mYYz4&t=150
[Nexus 7 General] droidgenius:
I was pressing that reset button for about thirty seconds trying to find it haha
[Nexus 7 General] droidgenius:
And try holding down vol + and power... thatll do the equivalent to a battery pull
[Nexus 7 General] cfh:
I did do that at one point. However, if I did it at a point

where the battery actually had run down I still would

have needed to re-charge the device -- which I did not

even try until today. Nice to know though.
[Nexus 7 General] yaoverstand:
I haven't had any issues with my nexus whatsoever thus far. I really hope these are anomolies.
[Nexus 7 General] kieso:
Sounds like the ever so familiar sleep of death that occurs on custom Roms. It requires the reset button or let the battery die
[Nexus 7 General] No_Nickname90:
I'm kinda glad I didn't get my Nexus 7 yet. LoL!! All these issues ppL are having.
[Verizon Samsung Galaxy S III] ChadHughes:
Part 2: Complaints, Workarounds and Fixes

---------+++++-------------------+++++-------------------+++++-------------------+++++-------------------+++++----------

Q: I lost my ability to do direct call from text after flashing this rom, and a theme.

A: I'm willing to bet you didn't realize the stock mms was replaced by the AOSP version. Luckily for you, forum post #298 in the Jellybean Domination v7.2 thread has a stock MMS fix, that is also themed blue.

Q: I flashed paranoid android and i lost complete cellular service, and I have no IMEI! Why would they make a ROM like this?

A: It's a fault somewhere between flashing this rom and K-Exec doing it's job. We don't know exactly whats causing it yet.

But chances are if you would have READ you would have heard about this being the number one RISK as of right now, and backed up your EFS/IMEI accordingly.

A link on how to do just that is in the first part of this thread.

Q: SynergyROM people said that tethering works and VZW Mobile Tethering is broken. What gives?

A: I could have sworn they included a different WiFi hotspot app that works off of one touch. Look for it :p

Q: Google Now isn't working. I installed the APK and all it says is initializing.

A: As far as I know Google Now is a jelly bean addition, correct? We are on Ice Cream Sandwich. We can't really expect everything to work. A working google now can be found in the Paranoid Android ROM, which is AOSP and Jelly Bean'd.

Q: The Dev(s) of (variable) ROM haven't replied to me or addressed my issue directly. Whats the point of being a dev?

A: This is not the Devs job. The Dev makes the ROM. The Community flashes, tests, and reports bugs/problems. The dev then finds the time to fix these issues when he/she/they can. You're not a twelve year old in a ROM candystore where every ROM is a Daily Driver until this bootloader situation gets handled properly.

Q: Awesome Beats doesn't seem to be working, help!

A: Just because it's on there doesn't mean it's supposed to work. It's experimental, and some people have given the nod and others the axe. Your model may vary. I do have a modified SGSII version of a beats script I've been working on that i've test flashed on mine that works, and I'll pass that out after some more testing and after I find the creator of it and get his/her permission, at least so I can give proper credit for the original compiling.

---------+++++-------------------+++++-------------------+++++-------------------+++++-------------------+++++----------
[Verizon Samsung Galaxy S III] ChadHughes:
Hey guys, this is for you. It looks like confirmation of the efs/imei backup working on more than one person. This comes from Paranoid Android thread. I hope this helps!

It is now.. I have data AND voice. Where previously I did not.

itsmefu is correct. I used the backup from this thread: http://xdaforums.com/showthread.php?p=29201792#poststop

To elaborate, I went from:

stock rom->rooted with root66 rom->made a backup of my IMEI/EFS

I did not know this but for some reason this phone views our internal storage as SD CARD whereas the actual "physical" SD CARD is named EXT SD Card... so when i first backed it up I was unaware of this... but I had used the method I linked to back up the IMEI/EFS. So that there is an EFS.BIN on my EXT SD Card.

I than updated my kernel to the latest OTA->updated my baseband to the latest OTA (I advise rolling back to the previous baseband as this baseband is HORRIBLE...)

|_->downloaded the vzd2 image recovery from this thread->downloaded JB GAPPS->downloaded paranoid droid

|_->booted into recovery using three finger method->data wiped->cache wiped->dalvik cache wiped

|_->installed PARANOID ANDROID-> installed JB GAPPS

|_->rebooted... and my data/voice was broken.

SO:

went back to recovery->nandroided back (^ok sorry i forgot I nandroid before the whole installing process...)

|_->got back to root 66 rom with root.

|_->downloaded terminal emulator

|_->followed the instructions to push the imei/efs back into the phone.

|_->rebooted.

Working data and voice. Got 4g/3g/and VOICE (<-the MOST Important).

Repeated the appropriate steps to install Paranoid Android..

Now i have working data/voice.. 4g and 3g.. Going to roll back to previous baseband though as with this new baseband I'm dropped 4g, 3g constantly at the areas when i had constant 4g and 3g! ￼

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

I can't really confirm but I know I had ALOT of zeroes in my IMEI with broken data and voice... so I'm pretty sure I had it, as I lost connection to network in total.. basically a broken phone but a working wifi tablet? haha.
[Verizon Samsung Galaxy S III] Slic|<:
Please update and say that the backup is at least working.. so it is a verified backup in a sense. So people won't be as scared as before since then the backup was a HUGE if. I can verify this because I made the backup, lost data & voice compeltely, and than rerolled backup and now have a working phone!
[Verizon Samsung Galaxy S III] Hurleyzero1:
What about the unofficial CM10?
[Verizon Samsung Galaxy S III] Slic|<:
If its the same issue it should work.. imei independent of ROM.
[Verizon Samsung Galaxy S III] Farabomb:
May want to make sure it's confirmed on more than one device and total IMEI loss before adding to the main post.

Rather clutter than people flashing and borking phones because of bad info. Mods delete this after a solution has been found and then no more clutter.
[Verizon Samsung Galaxy S III] tonu42:
Yayyy clutter to arrange clutter....... stupid...
[Verizon Samsung Galaxy S III] pjamv5:
Are you talking about the lift to call motion here? If so, that has worked for me on both versions of nosympathy's ROM as well as the most recent synergy ROM.
[Verizon Samsung Galaxy S III] Farabomb:
Pretty sure if the stock MMS gets replaced by a theme/ROM direct call gets borked.
[Verizon Samsung Galaxy S III] ChadHughes:
Didn't say it was won completely working, but it's better to have a backup then it is to flash and then be pissed off. One if the main reasons I made the thread is just so people can be aware. There are plenty of roms and same day developers and assholes and trolls, but we need more people helping instead of demeaning. At least now they can look and SAY OK, there is a huge warning in red regarding k-exec and AOSP Roms. Instead of people dev bashing it can help. Also I don't consider this thread clutter.
[Verizon Samsung Galaxy S III] nosympathy:
It should work on any rom based off of mine. Synergy is one of those.

He is posting it mainly because there are some themes out there that default the stock ICS mms.apk instead of the TW secmms.apk that is in my bases. No one had a working deodexed secmms.apk until I released my first base.
[Verizon Samsung Galaxy S III] ChadHughes:
Absolutely. Before no sympathy it's safe to say we were stuck, in a way. His tremendous work happened after these themes were being created, and people were blaming the ROM and that's clearly not the problem, and unfair.

Great work by the way no sympathy.
[Verizon Samsung Galaxy S III] Slic|<:
Thats why I suggested the OP to update the thread with the backup to be at least confirmed working for more than 1 person-the orginal OP of the backup efs thread and me-so far... Because than at least people will be less afraid. They still have to be cautious as even getting root is not 100% safe if you don't follow anything to the T.
[Verizon Samsung Galaxy S III] ChadHughes:
Well said slic!
[Verizon Samsung Galaxy S III] pjamv5:
Gotcha. I was reading that in the wrong context.
[Verizon Samsung Galaxy S III] Slic|<:
it is more than one person.. the original OP of that thread and me.. -__-. You can check out the threads of EFS/EMEI backup and Paranoid Android to confirm... This was all posted earlier this afternoon.

Thanks glad you agree with me! Because apparently Farabomb thought it was clutter... which in my aspect I think at least having it worked twice should count as a fundementally WORKING backup vs. a "THEORETICAL" backup... Because realistically till this happened to me we only had one case which was the OP of the EFS thread.. so it wasn't only in theory that it would work.

And i'm pretty sure for a 15 numbers string theres only one way of messing this up..

Btw, thanks Chad for posting what i wrote in the other thread up. And my apologies if it's a bit long, people said they wanted a detailed transcript so I did that.. :D
[Verizon Samsung Galaxy S III] ChadHughes:
LOL!

I'm glad it's long. The way people work on xda sometimes, long descriptions and transcripts are needed. I want everyone to work together, because all we will do is benefit! :D
[Verizon Samsung Galaxy S III] Farabomb:
Slic|<, my comment was in response to the post below me. Sorry if I offended. I was in irc trying to find out if it was just you that came back. I just didn't want people flashing madly without a proven solution. I flashed aokp without issue but I was still wary of trying any other ROMs without a working backup.
[Verizon Samsung Galaxy S III] Slic|<:
Couldn't agree with you more lol! Fascinate still gives me a headache lol... I had to go back to it after I lost my INC2 in a club.. :(. I think someone stole it :crying:.

Hopefully i can get it back sometime.. until than i upgraded to my S3! :highfive:

Oh.. sorry than. Cuz the two sentences seemed to go hand in hand lol.. And it's cool man. I'm not in IRC. I'm at work lol.. no IRC on government comps! :silly: Yeah that's why I told the OP to post that the backup was working but as already stated FOLLOW EVERYTHING TO A T AND YMMV since that part of the info hasn't changed lol.

Well you can try paranoid android rom now with no worries <--less worries- since I was the unofficial guneai pig... thank god I fixed it though lol. I also just got my 4g working again, had to reset my radio to LTE/CDMA/GSM it was set to GSM/CDMA auto. Reset it with the phone info app. Now i can see if it's better than the last baseband.

Will keep you guys updated.
[Verizon Samsung Galaxy S III] sid8911:
wow i was gonna make this thread 3 days ago but ppl told me not to....:eek:. Anyway nice thread
[Verizon Samsung Galaxy S III] ChadHughes:
Heheh...

Can't listen to people all of the time. You never know who may benefit from what. :D
[HTC Titan] larsstolwijk:
Dear reader,

I got a problem with my Titan for a couple of weeks now.

A couple of times a day when I grab my Titan and want to use it -> get it out of standby, it doesn't reacts to any input/buttons etc. just nothing. No feedback from capacitive buttons. Only way is to remove battery, insert it again and boot it up. But this occurs 20 times a day. I doesn't happen all the time though. But it is very frustrating.

It started after using the DFT rom for a couple of weeks. I hard resetted it, still same problem. Then I flashed the Dynamics7 rom, still same problem. So I start to believe that it's something hardware related, or maybe the following thing;

Though some other strange thing is that every time I hard resetted my device or flashed an other rom, and then installed the Facebook app, the FB app works fine, untill the first time my phone has the above mentioned strange bug. So after I restarted my phone, the FB app crashes while starting. And never works again... (FB app version 2.7.0.0)

Anyone with the same problem or suggestions?

Any help will be appriciated.

Thanks in advance,

Lars
[HTC Titan] larsstolwijk:
It seems it has something to do with my mobile network or simcard or something. when in flightmode and using wifi it hasn't happend anymore fore some time now...
[HTC Titan] larsstolwijk:
Well, I ordered a new simcard, in the hope that the problem would be solved.. But it has no effect. Tried 3 different roms, DFT, Dynamics7 and currently the standerd rom. All three, same problem.

As the problem becomes more frequent the last days, it also happens while calling, or other use of the phone, and not only when the device is locked...

Anyone with some suggestions?
[HTC Titan] drupad2drupad:
Have you tried not installing any apps at all? Just running fresh?

Try not syncing your hotmail account either. Just let it run as a solo phone.

Also, while you factory reset what will be worth looking into is, having data connection switched off. Only using 2G.

I have had exactly same problem with my old Nokia E63. I never got around the issue. It was one specific operator (Vectone, UK) and every other company's SIM worked without causing issues. Maybe worth testing some other network provider's SIM from your friend?
[HTC Titan] larsstolwijk:
well I found the problem. It's the Facebook app (not the integrated one).

Uninstalled it, problem solved. Installed it again, problem is back.
[Desire Q&A, Help & Troubleshooting] ryanraven:
Just moved back to my Desire and was wondering what is the best kernel to use for CM Nightly? Kernel that comes with the rom?

Would like one which gives better battery if possible.
[Desire Q&A, Help & Troubleshooting] jmcclue:
Tiamat or ManU kernels for CM. never used either myself but from reading posts ManU seems to be the popular 1. i know this is not quite the answer but mite point u in the right direction :)

Sent from my HTC Desire
[Desire Q&A, Help & Troubleshooting] Robi959:
Im using this CM7 ROM Euroskank. http://fitsnugly.euroskank.com/?rom=cm7&device=bravo

Using default kernel, calibrate battery, age is 81 %. My battery lasts with heavy usign 1 day, display has been turn on 4 hours and 30 minutes. Just replace original ADW launcher with Xperia or some fastest launcher. This ROM is very fast and with no laggs. Try it ! ;)
[Desire Q&A, Help & Troubleshooting] ryanraven:
its not really nightly though? 15th July 2012
[HTC Rezound] Bensky91:
Let's say I wait until the official ICS OTA is on my phone. Will the S-OFF procedure work? Has anyone tried it when already on the latest leaked firmware?
[HTC Rezound] Evocm7:
I'm sure control bear has been updated. You should have no problem. Just download the file for your firmware.

Edit: misread your post. Like the others said, do it now while is guaranteed to work.
[HTC Rezound] superchilpil:
I would be cautious, your better off doing it now
[HTC Rezound] carngeX:
Agreed. Might get patched up, and you'd have to wait then.

And it looks like according to Unlimited.io, 3.14.605.5 ICS Leak is still the most recent version they have... not sure if it would work on the .12 that's been posted.
[HTC Rezound] Bensky91:
Yeah, it's probably best to do it now then. Will accepting the official ICS OTA, when it comes, remove S-OFF?

Ideally I'd like to switch between the ICS OTA and an experimental version of CM when/if a source tree becomes

available.
[HTC Rezound] AshtonTS:
No it won't remove s-off. S-off is permanent unless you switch back to the stock hboot and type In fastboot

fastboot oem writesecureflag 3

Or something like that
[HTC Rezound] carngeX:
No, once you're S-Off you'll stay S-Off unless you run the fastboot command to turn it back on. Somebody correct me if I'm wrong.
[HTC Rezound] Evocm7:
You are correct. You have to run the command that ashton posted to get s-off
[Captivate Q&A, Help & Troubleshooting] derukun:
I apologize if there is already a thread on this, but I have not found an actual solution to it yet.

My Captivate's screen is on sleep mode, and maybe 20 ish minutes later, when I press the unlock button, I find that the phone is off and I have to turn it on again. This happens every 20 minutes, and the only way for me to keep it on is to frequently unlock the phone to verify that it is still on.

This is not a very practical method of doing things though, because the phone turns off in while I'm sleeping and I'm not always able to check my phone every 20 minutes.

My firmware version is 2.3.3 and I'm running Gingerbread OS. It's a refurbished phone I received from Rogers a week ago, and I really don't want to factory reset or anything like that as I have very important information/app data on my phone I don't want to have wiped.

I've heard of flashing a custom rom to fix the problem but the thread i read was from 2011. Can anyone help me with this issue? Thanks.
[Captivate Q&A, Help & Troubleshooting] Red_81:
If you received it as a refurbished from Rogers then I would go back to them and get them to send you a new one. There was a batch of Captivates that had this issue and a new motherboard was the only true fix.
[Captivate Q&A, Help & Troubleshooting] derukun:
Is that really the only way to fix the problem? Aren't there any custom roms that might fix the problem?
[Captivate Q&A, Help & Troubleshooting] Red_81:
They might help the issue but they will not fix it. It is a hardware defect. I had to send one back to At&t for the same issue.
[Captivate Q&A, Help & Troubleshooting] Nick0703:
Dude send the phone back to Rogers. Call them or go to the Rogers Plus store and explain them the problem. Tell them that you did factory reset and you're still getting the problem.
[Samsung Infuse 4G] mhays705:
Well a few months ago my infuse got stuck in a boot loop i couldn't get it to recover from. Ive got a new phone since but I want to attempt to get the phone I once loved working again. But it's probably completely bricked. The problem is it was in a boot loop that I couldnt even get it to stay it recovery mode it would just shut down then attempt to boot up again. The battery has died since then so when I plug it in it loads up the little battery charging pictures then the screen turns off then it just loops this. Any one know of a solution to this or is it just bricked for good?
[Samsung Infuse 4G] rkkaranrk:
Similar thread> http://xdaforums.com/showthread.php?t=1792848

Looks like u having the same problem......maybe its the power button.
[Samsung Infuse 4G] mg2195:
Yeah...probably another broken power button...seems like these are starting to get pretty common...

Anyways...check out this thread...http://xdaforums.com/showthread.php?t=1756467 the guy in that thread found a place that will.fix infuse power buttons
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] nilesh.remo:
http://m.youtube.com/watch?v=KwI6VYvHZ4I#/watch?v=KwI6VYvHZ4I
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] nilesh.remo:
download file here http://depositfiles.com/files/osrui8by2
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] nilesh.remo:
ICS FOR SAMSUNG GALAXY Yhttp://m.youtube.com/watch?v=UysgxC7tHKU#/watch?v=UysgxC7tHKU
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] nilesh.remo:
download ics rom filehttp://depositfiles.com/files/h08b7qrwa
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] nilesh.remo:
Ics or Jb for galaxy y installationhttp://m.youtube.com/#/watch?v=KwI6VYvHZ4I
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] Kousthubha Kumar:
Stop posting more dude. All of them are fake. Don't use them. They may look like ics or jelly bean but just looks doesn't make them the real one. There's a high probability of having viruses in those roms.
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] deathviper:
Ya

This can have TROJANS

......

BEWARE
[Android Apps and Games] GuestK0097:
Hi,

I wasn't very satisfied with the look of the original Facebook app for Android: mostly because it still doesn't follow the design guidelines of Android 4, even though ICS is already over a year old. So I decided to redesign the facebook app by myself and want now to share my results with you. You can find them in the attachments section (2 Versions, i couldn't decide with is better). Tell me what you think about it, I hope you like it :)

If you want this pictures in a higher quality or in the .xcf format let me know.

Download Link: https://docs.google.com/open?id=0B7Xo_jDGP2MvYUxaVGpMRkR0ME0