yashsingh1/xdaforums huggingface dataset:
[Xperia Play Q&A, Help & Troubleshooting] sdojoin:
U'll find out once u plug-in ur phone. Just follow the guide n do what it tells ya. Do it from start to finish. After that just pm me with the result. N mybe u could at least hit thanks for anybody that has help in any way. Lol:p
[Xperia Play Q&A, Help & Troubleshooting] AthrunIJ:
i have attached a file. could you check whether it is allright and i've already click thanks to everybody that help me. :)
[Verizon Samsung Galaxy S III] mike86325:
Such a great post :good:

I totally agree and I think this will catch their attention way more than anything we can do online. I'm in.
[Verizon Samsung Galaxy S III] Elite49:
Wont do anything different. They'll tell you the same thing they told me after I filed a BBB complaint against thrm for my X2. "Your totally right our phones blow, so let me early upgrade you or do ypu want to terminate your contract for X amount of money?"
[Verizon Samsung Galaxy S III] Boss428man:
Thank you for the kind words, Its the same angle I talk to Verizon about on the 28th the day that they said the Unlimited Data was gone.. I told them that I found out from everyone but them and how they didn't inform me in any way.

We need to get more people on the non informed purchase angle. They make no mention online or anywhere. Sure Pocketnow and like sites do but they are not selling us the phone. Their image is even worse now that Corp and Tech release 2 different statements.

I really hope this gets unlocked easily because I really like the phone really nice feel to it.
[Verizon Samsung Galaxy S III] ponyboy82:
This is a good approach. As someone who pitches in with customer service/support for a tech company, it's often the "nice" people who get better responses, and the quantity of requests can have a bigger affect.... way more than one angry person ranting and raving that you can just write off and ignore.

Also, it's still a person at the other end of the line. They probably are not aware of the situation or don't like it either, but it's their job. It's the people at the top that usually push down these horrible policies, the bean counters and such that don't have to deal with the angry public.
[Verizon Samsung Galaxy S III] manchild83:
I work at a major utility. Please remember that if you call be nice to the customer service representative you are taking to. They are only the messenger, please remember that. They are not allowed too much latitude with what they can do for you. The reason for your call is logged and reviewed by the management of the company so if you call constantly and take up customer service minutes over the locked bootloader you WILL have an impact on daily business and cause management of the company to fix the problem. Calling customer service works.
[Verizon Samsung Galaxy S III] Skizzy034:
I feel for you guys. I really do. We've tried everything with the One X but to no avail. Good luck with your attempts. These carriers need to remember who gives them their money.
[Verizon Samsung Galaxy S III] Boss428man:
Thank you for the comment and good to hear your advise!
[Verizon Samsung Galaxy S III] Boss428man:
Ok now we really have been miss sold. The answers I have recieved from support are well making there position worse they said that not only the bricking of devices but that these open devices would take down their data networks do to use. If that is the case why release the "Developer Edition". Everything will break lose anyway. We all pre-ordered thinking we got a unlocked Galaxy S3 and now with out any word of additional editions they try and fix things...?
[Verizon Samsung Galaxy S III] zaisaroni:
Where was an unlocked phone advertised or even realistically expected?

It sucks but VZW is so big and doesn't care at all, and won't suffer much from it.

Sent from my AT&T Galaxy SIII (SGH-i747)
[Verizon Samsung Galaxy S III] drksilenc:
yes it was expected since EVER model that has been released thats att tmo sprint international korean and us cellular ALL are unlocked.
[Verizon Samsung Galaxy S III] Boss428man:
Thats it it wasn't printed that it was locked it was advertised just like the other Galaxy s3's... They were sell you the same Galaxy S3 with the same experience you would expect unless other wise noted... which it wasn't... They should just offer to unlock our phones and void the warranty. Simple fix and essentially the same thing they have done with the Developer Edition and it would save them some returns..
[Miscellaneous Android Development] Jo3yParasit3:
About a week ago or so, my mom told me to root her LGC800 since my Galaxy Nexus is rooted and fully customized by me. I installed all the required drivers, my PC recognizes it well. I rooted the LGC800 with Super One Click, the latest one that doesn't require the ADB commands, and it rooted fine. Then I downloaded a recovery.img or boot.img and installed through Root Explorer. After that I installed ROM Manager and flashed the wrong Recovery and since that moment it stays stuck on the LG boot screen. I can only access the 3e Recovery (A [QWERTY] + F [QWERTY] + Vol Down + Pwr) and S/W Upgrade (E [QWERTY] + Vol Up + Pwr). At the 3e Recovery I tried doing a Factory Reset and, still, it won't go past the LG boot screen, I downloaded an update.zip and tried to install it and it didn't work, it says "Installation Aborted". I put it on S/W Upgrade mode and I then downloaded the LG Update Tool and it says phone or "Software Not Supported". Then I downloaded the KDZ Updater and the V10D_00.kdz file and it doesn't work. Either it's not the one for the phone or I don't know what's wrong. So I tried using the AndSDK file on my PC and so I open CMD, changed the directory to AndSDK and typed "adb devices" and it doesn't list any device. I put the phone in S/W Upgrade mode and still it doesn't list the device. But, I put the phone in Recovery mode and it listed it as LG_ANDROID_C800, so I typed "adb shell" then "su" to gain root access and it says "permission: denied". I tried to push files through "adb push"command and, again, "permission: denied".

The only thing I haven't done, not because I haven't tried it, is putting it in fastboot mode. I read it was pressing the Home button in the QWERTY keypad and Pwr, but when I try that it takes me to 3e recovery right after I press the Touch Home button, if I don't press anything at all it shows the Android with package and the arrow and it reboots, so it gets stuck in LG boot screen again.

I've been in the problem for about a week and I'm running out of resources. I only want it to be stock or at least stable. If anybody could help I would GREATLY appreciate it! Thanks in advance! :fingers-crossed:
[Miscellaneous Android Development] Jo3yParasit3:
I really need help on this. Any help would be appreciated.
[Miscellaneous Android Development] mr arrieta:
fix

check this post, here are mentioned some hard brick fixes.

http://xdaforums.com/showthread.php?t=2169722
[EVO 4G Q&A, Help & Troubleshooting] postwick:
I changed the lock screen camera icon to Vignette but after a while it disappears and becomes a blank icon. Anyone have any idea why?
[Samsung Galaxy R i9103] Adam77Root:
Hi everybody!

This is my first thread here on XDA. I would like to share this recovery with you. I compiled it from the (almost) newest CM9 sources.

Most of the functions work. You can make backups to internal and external SD card perfectly.

Known issues:

- You cannot install updates from external SD card, because it is mounted to /emmc, not /sdcard/external_sd. This is mainly because I use adb mostly for transferring files and it is more practical for me to push my files into /sdcard. However, it is not so hard to fix this.

Install:

- Put the attached file to your SD card and flash with CWM. I don't know if it works with CWM v4.0.0.2, it is fine with v5.5.0.4 :D I will upload the img if the zip doesn't work.

UPDATE:

I have successfully compiled CWM v6.0.0.0 Touch using http://builder.clockworkmod.com

However, I do not recommend it, because the default compilation environment set up by the site is not the most appropriate for our device (For example: It compiles for generic armeabi, not armeabi-v7a). But it works. You have to wait some seconds before it gets responsive for touch.

It is uploaded into attachments now.

UPDATE 1:

I fixed the home button (there was a typo in the source :o) and the internal and external SD card swap. The new zip is attached. My versioning starts with v0, but it isn't marked. This is the v1 version.

UPDATE 2:

Touch version updated with internal and external SD card swap fix. The old versions are removed.

UPDATE 3:

I've just compiled v6.0.0.3 from sources. I haven't noticed any big changes compared to v5.5.0.4 yet. It seems very stable after some initial testing. Added to attachments.

Every custom modification to devices have risks. Flash this at your own risk!

Have fun and enjoy! :)
[Samsung Galaxy R i9103] 4eLLka:
Does your CWM have touch support?
[Samsung Galaxy R i9103] 1337SereniTyx3:
Has anyone tried this?! Is it working fine?
[Samsung Galaxy R i9103] Adam77Root:
No, unfortunately I haven't managed to make it work yet.

It should work on every device, including yours.
[Samsung Galaxy R i9103] bhargav143:
Sorry friend... It has some bugs.. The centre key does not work.. And the soft keys toggle automatically...making it difficult to use...

I would prefer going back to cwm 4... Which has no bugs at all...for our galaxy r....
[Samsung Galaxy R i9103] D™:
hey buddy, as per Bhargav143, this CWM has some bugs & Home botton is not working..so try to fix these bugs..please..& if you can, please make it touch..:highfive:
[Samsung Galaxy R i9103] xlm13x:
he already posted bugs, y repeating it and making useless posts :confused:
[Samsung Galaxy R i9103] D™:
Can you read second one what I have asked..?? "hey buddy, as per Bhargav143, this CWM has some bugs & Home botton is not working..so try to fix these bugs..please..& if you can, please make it touch.

& also If I mentioned something which earlier asked by someone, so what bad in this:confused:, I need that so I mentioned:D, many times few things repeats, so dont be panic buddy:cyclops:..just try to be chilled buddy..:p

I never try to spam the thread..just making thing compalsory..
[Samsung Galaxy R i9103] Adam77Root:
Thanks for the feedbacks! I will fix the home key today. I totally forgot it, because I got used to the power key and the back button. I will also fix installing from external SD.
[Samsung Galaxy R i9103] chandrus1983:
Creating thread problem ok, fine, writing post is also problem ???

the MOD himself is not telling anything but others are !!

Dnt knw what is problem in writing comments/post
[Samsung Galaxy R i9103] ZeXzr:
Problem is that some just write and write and write and most of what it does not make sense. The point is not just something to write and write, but write that makes sense. Write when you can help and when you will say something smart, not to write to each thread as soon as someone write something.
[Samsung Galaxy R i9103] chandrus1983:
i am not gonna reply here anymore, i think there is no problem in commenting :|
[Samsung Galaxy R i9103] ZeXzr:
This does not apply to you, or to anyone in this thread, browse for a bit and will understand what I am talking about.
[Samsung Galaxy R i9103] Adam77Root:
Does anybody know where can I find sources for CWM touch? I'm trying it now with the online builder, but doubt that it will work.

It says ICS kernel is needed.

Update:

It works! The first post has been updated! Check out CWM Touch v6.0.0.0!:)
[Samsung Galaxy R i9103] 'cooleagle':
Hi buddy,

Thanks for developing for our device. :) I don't know how much this will help but you could have a chat with Chainfire or 'codeworxx'(Cyanogen MOD ROMs ). They have successfully made recoveries for many devices. Both of them post in Galaxy S2 & S3 Development section.

I'm not doubting your work but you could solve the bugs faster if they help / guide you from their experience. :)

Cheers !
[Samsung Galaxy R i9103] D™:
See bro, First of all what I gonna write, will not pointing to u or to anybody in XDA.:o

What if we are forcing somebody to write..??:silly: You can check in Any section we have lots of comments / replies over same topics were strached & when we are in need & asking someone it doesn't mean we are spaming the threads. several times in "DEV section" or any section, we just asking DEVs to provide the "whatever we are in NEED". it doesn;t means we are making nonSense comments. so, there is need to understand the comments & requirement of the user.

please dont mind it. I am not pointing anyone..just making understand that what are we doing now a days.:(

---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------

Nice suggestion buddy..:D
[Samsung Galaxy R i9103] mj.vikram:
About ClockworkMod Recovery 6

The recovery builder (Koushik Dutta) is now building version 6 of the recovery. The main changes are as follows:

Backups are much faster. 4-5x faster. (Bug fix due to excessive status updates of the UI and new backup technique)

Incremental backups are smaller. Way way smaller. Only 15-20MB each for each additional backup of a ROM. This is done using a new tool I wrote to dedupe the files between incremental backups to eliminate duplicates.

Source: https://plus.google.com/103583939320326217147/posts/cPF6gkmpM9m

Friend this is the latest version and only Galaxy Nexus is having this build, so we can expect some bugs...

@Adam thanks for the V6 build:good:, take your own time for fixing the Bug's ...
[Samsung Galaxy R i9103] xlm13x:
its not about communicating, its about posting useless posts which is not required. repeating thing which is already said doesnt makes any sense.

and about mod, he is handling many devices not only galaxy r so he cant provide his full attention here.

and about communicating we are on XDA not on facebook. if u r not going to post something helpful or useful information, than better dont post just for communicating. for communication there are sites like facebook and twitter not XDA :)
[Samsung Galaxy R i9103] Adam77Root:
Thanks for the advice! I'll contact them in the next days. However, I won't be at home for a week from tomorrow and thus won't have access to my files.

Sent from my GT-I9103
[Samsung Galaxy R i9103] xlm13x:
if u want to contact those devs on IRC, here are links. most of time they are there and we can chat direct online with em.

supercurio: http://webchat.freenode.net/?nick=xdauser&channels=project-voodoo&prompt=1

chainfire: http://webchat.freenode.net/?channels=#xda-devs

cyanogenmod network: http://webchat.freenode.net/?channels=cyanogenmod

---------- Post added at 06:37 PM ---------- Previous post was at 06:06 PM ----------

@adam do u have good knowledge of compiling kernels?

wkpark have made linux 3.x kernel for tegra2 SoC. but it is meant for g2x. i have contacted g2x devs and wkpark his self but those guys r not interested in our device.

if u r interested in kernels than look at his repos at github and if possible try to port it to galaxy r. we have ardatdat, who is only kernel dev in our community right now and great thing is he is also owner of sgr. if u need some help he will surely help u.
[Samsung Galaxy R i9103] Adam77Root:
Interesting idea. I have been thinking about building a kernel for our device, but haven't take the effort to unzip the sources yet. I will look into this as soon as I come home.
[Samsung Galaxy R i9103] mj.vikram:
In your build you have used Stock kernel only for CM but i heard like we need to build the different kernel for CM/AOSP, so how you managed CM to Boot with stock kernel :confused:.
[Samsung Galaxy R i9103] Adam77Root:
I don't think CM needs a special kernel. As far as I have seen, they didn't change so much in the base Android system (I mean especially the libc and the linker). Since the stock kernel is for AOSP and the base layer is almost the same, the original kernel is good to go. Somebody pls correct me if I'm wrong, I didn't look into those sources a lot.

Little update to CWM: I fixed the home button, there was a typo in the source. :o Now I'm looking into that toggle thingy.

UPDATE:

Edited first post. Fixed internal and external SD card swap too.
[Samsung Galaxy R i9103] maheepmaurya:
I Came here just to say that CWM 6.0 is out and Tada You already compiled it for us. Great Job man. :D

(⊙o⊙)Android & iOS Superuser!←_←
[Samsung Galaxy R i9103] gitanshu:
So all bugs resolved or still something left?
[Samsung Galaxy R i9103] mj.vikram:
Adam which is the latest Build and can you please add version number for them so that it will be easy for us ..

ex: CWM 5.X.X.X_V1
[Samsung Galaxy R i9103] Adam77Root:
Most of the bugs are resolved in my opinion. (Not sure about the display toggle one.)

Good idea. Now the latest is referred as CWMv5.5.0.4_with_fixes.zip
[Samsung Galaxy R i9103] bhargav143:
The zip has some error...downloaded twice... gave error while installing... "Error in file"..some error like this......
[Samsung Galaxy R i9103] maheepmaurya:
I just flashed the CWM v6.0.0.0 and it is working fine. Yes touch works after few seconds but works great. I tried all the common functionality and found no Bug. Thanx man!:laugh:
[Samsung Galaxy R i9103] bhargav143:
I will also try....
[Samsung Galaxy R i9103] gitanshu:
Is the late touch responsiveness thing normal ( also happens on gnex)?
[Samsung Galaxy R i9103] Adam77Root:
Sorry for the problematic zip. I forgot to add updater-script back. :o Updating first post (with a reasonable versioning :D).
[Samsung Galaxy R i9103] bhargav143:
Ok..waiting buddy.....

Could you just upload the cwm6 as an attachment....the link is not working on mobile...
[Samsung Galaxy R i9103] Adam77Root:
It's already up:) CWMv5.5.0.4_v1.zip is the file name.

Uploading CWMv6 :)
[Samsung Galaxy R i9103] kunaal2580:
Are there any bugs in the cwm 6.x.x.x?? Is it ok to flash this version now??
[Samsung Galaxy R i9103] Adam77Root:
There is only one bug in v6. Internal and external SD cards are swapped. I'll upload a fixed in 10 minutes.

UPDATE:

It is up.

Sent from my GT-I9103
[Samsung Galaxy R i9103] technonerd92:
Thanks works perfectly. No issues on my end. :) Great job.

Edit:

For those of you who are complaining about late touch response. As you as you boot into CM 6.0.0 give it about 15-20secs your touch should work perfectly.
[Samsung Galaxy R i9103] mj.vikram:
Tested CWM V6 and it's working fine (Touch is little lazy like me :p) but enjoying the CWM Touch :cool:.....

Good Job Adam :good:...

Backup's are little confusing whole system backup took only 14 MB :confused:, but some files are created under clockworkmod\blobs what is this...
[Samsung Galaxy R i9103] maheepmaurya:
HAHA Dude that is the Biiggest Catch. This is the biggest Advantage of CWM v6.0.0 over Previous Versions. Nandroid Backup will be around 15-20 MB only.:D

CHECK This Source Out for Details!!!:p
[Samsung Galaxy R i9103] gitanshu:
Isn't that the size of incremental backups? How can full nandroid be this small? Doesn't seem possible to me.

"Humka ICS de dyo babua!"
[Samsung Galaxy R i9103] mj.vikram:
Backup is taking same time as v4, ok i need to dig more i feel to understand this.....

14 MB is just Index buddy then main backup is done under clockworkmod\blobs which is around 1 GB, hope you understand it now...

Edit/Update: Tested CWM V5 its working fine until now i didn't find any issue (Tested: Taking back up's, Restore backup's, Install from Internal & External SD and Clear cache & Dalvik cache) hope i've tested all the features and everything is working fine for me...

Install from Zip is not working i feel in CWM V6 (eg: Tried to install CM7 Zip from CWM V6 it gave Error Status 7, But same Zip worked fine with CWM V5)

Good Job Adam :good: happy to see you on board...
[Samsung Galaxy R i9103] technonerd92:
Ok I am facing the same Status 7 problem with CWM6 should I go back to CWM5 to flash the update?

Edit/Update:

As mj.vikram mentioned going back to CWM5 and installing CM7.2 works.
[Samsung Galaxy R i9103] gitanshu:
I flashed the cwm6v1 Through cwm6v0. Didnt get any error, then why for cm7 ?

"Humka ICS de dyo babua!"
[Samsung Galaxy R i9103] D™:
Do think you are only smart one

Hey Cooleagle / Red5,

Dont know why now a days few People are provoking us to dont do / or forcing us to do. See, few are here who are thinking that what they are writing are compalsory & are keep on arguing.. ever after explaining each & everything..they are keep on writing to provoke. They are saying our requirement & suggestions are USELESS, if we are repeating it one time... please send the suggestion to members not to spam the thread via there comments that "what are they thinking is not like that".

We are here to getting help & Vice versa. Members are following as per suggestions & Rules by MODs..

---------- Post added at 11:44 AM ---------- Previous post was at 11:39 AM ----------
[Samsung Galaxy R i9103] mj.vikram:
Bro i didn't get your point, The problem is with CWM V6 so I've wrote it hear....
[Samsung Galaxy R i9103] Adam77Root:
I have just realized, why CM install with CWM6 doesn't work. The CM build system automatically puts assertion into the updater-script to make sure we are flashing for the proper device. This will only be resolved if CWM6 sources get released. However, there is a temporary solution. You can unzip the update, find the updater-script under META-INF/com/google/android and remove the first row (where the assert is).

Of course you have to put it back to the zip.:D When CWM6 sources get released, I'll definitely build a version with key fixes (however, you don't use keys with a touch recovery :D)

Sent from my GT-I9103
[Samsung Galaxy R i9103] D™:
You are in NEWs

Hey dear you are in NEWS now..just checked it out... new are saying these 6V is only working for NEXUS, but due to the great ADAM, Galaxy R is getting the same..thanx a ton buddy..

The ClockworkMod recovery is what makes it possible for millions of Android users all over the world to install their own custom ROMs in a pretty user-friendly way. Every phone has basic recovery software installed on one of its partitions, to perform some simple tasks, but the CWM recovery can replace that stock recovery and can offer you some more advanced functionality.

That includes being able to back-up and restore a ROM, to install a different ROM on the phone, or to partition the microSD card. For example, use the Link2SD app to make your phone use a microSD partition as its default “internal storage” for apps. This gives the benefit of using 512 MB, 1 GB or more, for your apps, instead of the measly 150 MB you usually get on lower end phones. Google should really force manufacturers to give at least 1 GB of free space to users of such phones, so this won’t be necessary anymore, but that’s whole different topic we won’t discuss here.

The ClockWorkdMod recovery has been by far the most popular recovery for custom ROM’s, and its developer Koushik Dutta is already working on version 6.0, which is now in alpha stage, and promises to bring new improvements such as much faster back-ups of your ROMs (4-5x faster), and smaller sizes for the incremental back-up files. It’s only 15-20 MB now for an additional back-up of a ROM, so it will save you space on the microSD card.

Right now you can only get these alpha builds for the Galaxy Nexus.

---------- Post added at 12:42 PM ---------- Previous post was at 12:41 PM ----------

sorry buddy, actually i have opened 3 pages of chrome & replied over this one..I have removed that one..thanks:cyclops:
[Samsung Galaxy R i9103] emanoj.i9103:
Hi All,

Now that we have the latest CWM for our Royale, Will it be possible to get ROM Manager support for our device?
[Samsung Galaxy R i9103] Aquethys:
@adam:

Same thing here... Can you modify this a little bit to work with the Glide? What needs to be changed? We have mostly the same hardware yet when I tried to flash it gave the same error after flashing cm7: a thin red bar on the right of my screen (like 0.2cm)
[Samsung Galaxy R i9103] Adam77Root:
I'll contact Koush in the following days to get Rom Manager support. (at least for v5.5.0.4)

Sent from my GT-I9103