yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Orito:
Hello,

I've searched the S3 forums here (20 so pages for build.prop) and a ton of Google results for an answer. I cannot find anyone having failures in this particular situation.

I am trying to rebrand my S3 into a Sony Xperia Z Ultra for the purpose of purchasing and downloading a specific app. It would also work with a Nexus 7. I have managed Google's dashboard to recognize the rebrand both times, however there is an issue. When I rebrand as Sony Xperia Z Ultra, it says it's compatible but whenever I hit purchase, it says an unknown error has occurred. When I rebrand as the Nexus 7, it says that my device is not compatible - that'd be fine, but when sorting reviews by device, there are those who have reviewed it with Nexus 7.

Before all of this, I was trying to use Market Helper. It got the market to acknowledge that the device was compatible, but it was also giving me the same unknown error that rebranding as the Xperia Z Ultra did.

With all of that out of the way, I have a few questions that I cannot seem to get answered...

1) Has both the Market Helper and build.prop edit method been patched?

2) If not, why is it not working if Google's own dashboard recognizes the change?

3) If yes, is there any other possible method of accomplishing this?

Thanks in advance for taking the time to assist,

Orito

Edit:

I tried rebranding to the above devices again, and now Google doesn't even tell me it's compatible... I also went ahead and tried Nexus 9. I can still see reviews with this device, but it still says not compatible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nosmokingbandit:
I'm selling my S3, which currently has OctOS (http://xdaforums.com/showthread.php?t=2668225) installed. What is the best way to get back to 100% stock? I've found several guides but most of them talk about 4.0.4 as the latest firmware, so they are pretty outdated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Before trying to flash back to stock, you should confirm the bootloader version currently installed on your phone. If it is the mjb or newer, you cannot flash any stock ROM from sammobile.com. AT&T never released a full ROM after 4.1.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] silverlewis52:
Trying to Root a GS3 SGH-1747 on 4.4.2 with a kernal built in Oct. of 2014

I've been trying to root my phone in order to use programs that help you retrieve deleted files. I've tried a lot of the guides out there, including, MobileGo, Towelroot, Kingo, etc.. None of them have worked. The latest one was Zedomax's old guide (because I didn't see his new one). That didn't work either. After flashing my phone, I still couldn't get onto CWM Recovery Mode.

Can someone teach me how to properly root my phone? Any help would be appreciated.

P.S. I'm a complete noob. I started knowing nothing, but at least I know now what flashing, rooting, etc. means. And most importantly, different versions of 1747 require different rooting methods -_-".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nosmokingbandit:
Looks like I have the MJB loader. Is it possible to get back to any version of stock or should I just flash something ubiquitous like CM11 before I sell?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
This MJB thread may help: http://xdaforums.com/showthread.php?t=2722660
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Outlaw747:
So I recently tried to update my Slimkat from a fairly old build to their recent build and encountered issues that I believe are related to my bootloader.

I currently have I747UCALEM as my bootloader, do I need to upgrade this and if so could some kind soul either post instructions or direct me to the right thread?

Thanks in advance!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
At least on user of SlimKat 9 has stated that he had to update to MJB bootloader and modem to run the ROM. He was starting from LK3 firmware. He lists the procedures he followed to get SlimKat 9 running properly. Additionaly the OP for SlimKat 9 links to the projects webpage with installation instructions.

If you have not already done so, you may wish to use the free SIM unlock found in the forums before updating. It only works on the 4.1.1 modem. Be aware, once you have updated to the official 4.3 firmware, or beyond, you can not downgrade without bricking your device. I have noted in a number of ROM threads (CM, TW, and AOSP) that people are successfully using the leaked 4.3 firmware (MJ2) with the official 4.3 modem (MJB). I am doing this on a TW based ROM. There are links to this combo in a number of ROM threads, ROMs based on both 4.3 and 4.4 Android. This combo does allow you to downgrade.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] macdofco:
I have rooted a number of phones in my time and removed recommended bloatware. I have even loaded custom roms on phones from many different manufacturers. I have always felt that I was posing as a "phone guy" without actually knowing wth I was doing! I would like to know exactly what it means to 'exploit' a phone's OS to get root. Does anybody have any resources they could point me to ? Android Development 101?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
See if this thread can serve as a starting point.

http://xdaforums.com/showthread.php?t=1974338
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jnorlund:
I have the NJ1 loader and can't get past the att logo before it turns off. What else can be done without stock?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
A link to srx3? I can't find it. I'm on cyanidel and love it. I want to go back for a second tho. I been looking for 2 hours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
What ROM are you trying to flash? What steps did you take since you first began the process of flashing the ROM?

Or do you have a ROM that was previously working but is no longer working?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
here ya go

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

"all I can really do , is stay out of my own way and let the will of heaven be done"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jnorlund:
I obtained this phone to fiddle with (I747 AT&T) the other day and it wouldn't make it past the Samsung name. I read a ton and tried nearly everything I found. I have tried installing several ROMs both custom and Stock (clean, but likely all for previous firmware I am realizing) including the 4.3 stock and as well as the Flashable Rooted NJ1 system.img and boot.img. It will sometimes get to the musical notes and AT&T logo before turning off or rebooting.

-I can get to recovery and download mode, even tried going back to Stock recovery for the heck of it.

-The screen is fine in both modes and swipe works. It doesn't reboot all the time (just off) so I have a hard time believing it is hardware like the power switch or battery

-The phone is recognized by my computer on the cable after installing the Driver

-Kies tries to connect to it when in Download mode, but never succeeds.

-I have installed the NJ1 modem and radio

-The counter is at 3 and it says it is on custom binary.

-Tried all of the cache clearing and resetting that can be done. Battery has been left out for hours before trying again.

I am at my wit's end. No matter what, it never gets past the AT&T logo (furthest). If there is no Stock for the latest firmware, I guess I have to wait or am I screwed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
If you haven't done it yet, try a full wipe (full wipe, factory reset whatever it is called) in the stock recovery. Odin and TWRP just aren't as effective at solving some problems as a wipe with the stock recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
[MENTION=890443]jnorlund[/MENTION], you mentioned that you installed the NJ1 modem/radio. Did you also flash the NJ1 bootloader?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jnorlund:
Will try when I get home

It already has the NJ1 bootloader as I found out when trying another one. However, I think I tried to reinstall it anyway. Will double check.

I guess what my main question is is: If you have NJ1, what ROM would you use to try to get a phone working at this point? I don't care if I lose root or anything. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Enewman posted a rooted, stock AT&T NJ1 rom. That's a good place to start, but I haven't had trouble with NJ1 and any of the newer AOSP/CM based kitkat roms. I'm certain nothing with a build date later than August 2014 has given me any problems; older roms might be ok too I just haven't confirmed it.

If you've had AOSP roms on your phone, then sometimes getting a TW rom to boot can be troublesome. A full wipe / factory reset isn't enough for some people. Formatting the internal storage is recommended. As mentioned above, a full wipe in the stock recovery seems to be very thorough and can cure a lot of weirdness with this phone too.

Good luck
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
[MENTION=890443]jnorlund[/MENTION], I recommend copying the most recent CM11 to your phone or an external SD card, flash the latest Philz Touch recovery for the d2lte using Odin 3.07, boot into recovery, flash CM11, boot the phone. This should at least get the phone up and running.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jnorlund:
It's alive! I did do a factory reset on stock recovery and did the Philz Touch. Not sure which one worked but it did get to the normal screens once connected to my computer via cable only and it hasn't done that before. I suspect the battery is in fact bad despite saying it was at 85% charge because it won't stay on without the connection. Thanked you both. I may be back with a different issue but at least I'm making progress.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] macus+:
dead s3

HI read somewhere there is a condition called dead s3 or so. My wife's just passed away. Will not get past the samsung logo, which briefly appears and then it dies.

Not a battery issue. Even triyin to connect it to odin will not work.. It goes again into download for a short moment and dies on me-

that is pretty ,much all I can do with it.

any ideas?n thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xDark_:
Is Xposed working on the unofficial CM12 (5.1) ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
As far as I read there is only a few closed working mods ATM that work with 5.1 the rest boot loop but its being worked on to get it fixed will just take some time

Sent from my Nexus 6
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxkid123:
Yes, but in alpha form.

Information here: http://xdaforums.com/showthread.php?t=3034811

Note that it's a bit more difficult to get running than on KK (need to flash a few things in recovery for it to work, instead of just installing through the xposed app). Personally I haven't tried it yet, as my s3 is also my main device and I can't afford any more potential instability.

Edit: wrong links.

The link above is for 5.0 only, but I reccomend reading it.

Here's the 5.1 link (unofficial): http://xdaforums.com/xposed/super-alpha-posted-permission-xposed-t3072979

and here's some additional information: http://xdaforums.com/xposed/official-xposed-lollipop-t3030118
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g33kos:
Hi guys, I'm having my sister S3 (Rogers) to fix. I have no experience with Samsung, because I'm a Nexus user. To cut the long story short, the phone was rooted when she bought it. After factory reset, root checker indicate that root isn't properly installed and supersu doesn't work and I cannot uninstall it. Also I got a security message for unauthorized access that was blocked, which I guess is from knox. When I tap the knox icon, it says that I have to download and install the app and this confused me. I used Terminal emulator fo android to disable knox and i got a message that this app isn't found. My questions:

1- How can I remove supersu?

2-If supersu cannot be removed, should I flash the stock rom again or maybe a custom rom without disabling knox?

Thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
To get the phone back to stock, boot into recovery and do a full factory wipe/reset. After this, use Odin to install the latest factory Rogers rom from sammobile.com.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gfinockio:
Finally decided to update my phone from 4.1.2 (custom stock ROM) to 4.4.2. I was worried about losing carrier unlock, but now I hear it's permanent after you do it once.

IN ANY CASE... now I'm looking to get another custom ROM on this good old phone. Are there any 5.0+ ROMs that are bug-free? Like, the camera/bluetooth/tether/etc work flawlessly without workarounds? Most ROM pages are like 180+ pages long, and there's no easy way to tell what's working and what isn't when the developer just says "tell me what isn't working", which is likely the most useless statement from a developer ever.

tldr - is there a bugfree Lollipop ROM for the S3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g33kos:
I rooted the phone, then i flashed TWRP via odin. After that i did try to get into recovery using the buttons combination and didn't work, just showing for short time Samsung logo and some blue text in the upper left corner. So i did that using the command prompt (adb reboot recovery) and shows the same thing but now, the phone cannot be reboot to system. Is this soft bricked? If i try to boot it into download mode, the phone just buzz every 4-5 seconds, but doesn't start.

LE: I got into download mode, but when i try to flash the stock image via odin, fails

<ID:0/007> Firmware update start..

<ID:0/007> sbl2.mbn

<ID:0/007> NAND Write Start!!

<ID:0/007> sbl3.mbn

<ID:0/007> aboot.mbn

<ID:0/007> FAIL! (Auth)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
It is failing because your are flashing a ROM with an older bootloader. You have the i747?

Are you flashing via Odin? If you are, try this: open Odin, uncheck everything in Odin except f.reset time, flash TWRP, when you see the word Reset in the status window, remove USB cable, remove battery, replace battery, use button combo to get into TWRP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g33kos:
I have i747M. And yes, I was flashing via Odin. Now i have this message: "firmware upgrade encountered an issue. please select recovery mode in kies & try again"

Should i do it with kies, or to follow your instructions? I don't understand why the bootloader was old and gave me this issue since the phone works fine untill i flashed TWRP? I thought the culprit is TWRP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
Just flash a nandroid in recovery before the issue began
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g33kos:
I cannot access recovery, only download
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
Are you sure you have the correct firmware? Also, if the device has a 4.4+ bootloader that was updated while she had the device active with Rogers, you'll need a Kk ROM instead of JB. That would have been in the OTA i 'think', but dont hold me to that. I wish you could check. Flash a stock firmware 4.4.x+ to the device amd see if iy recovers it. Added info from you would greatly help here. Go to terminal emulator, free on market, and type in 'su' without the quotes, then 'getpeop'

Okay scratch the last part since you pave Odin mode only. You're device in SGH-I747M.... Correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g33kos:
Yes, i'm sure about firmware. It was 4.3 and then i got update to 4.4.2 via OTA. The phone works. Then, I root it and the phone has no problem. The problem appears after flashing custom recovery TWRP. So now, I'm enable to get into recovery mode, only into download mode. The terminal emulator has to be used on the phone and since I cannot boot the phone i can't do it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
TWRP? Were you running Cyanogenmod at the time?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g33kos:
No, no cyanogen. It was stock firmware.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
Wait a sec... You're stuck with 4.4+ ROMs I believe... As I said before. Download a totally stock nonrooted 4.4.x firmware, and you should recover the device. You u may have to flash it several times.

---------- Post added 30-07-2015 at 12:04 AM ---------- Previous post was 29-07-2015 at 11:59 PM ----------

Read previous post... That should fix device. I always watch this thread, and I'll use the amazing and magical 'search forums' button ;) While downlanding new firmware find Philz Touch Recovery... Its an enhanced version of CWM and will work on any ROM. Use it to root device, and you'll be set. I'm pretty sure the new firmware will recover the S3 for you. If this helps, please hit the thanks button :)

---------- Post added at 12:08 AM ---------- Previous post was at 12:04 AM ----------

Hes 747M, Rogers, he tried to go 4.4 to 4.3.... With stock ROMS. Only other option is he has the wrong or a corrupted .img for twrp. I use safestrap on this one, but never twrp. My fix should resolve the issue either way I think.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g33kos:
Yes, you are right< I forgot that it is a new ROM, and I was trying and trying to flash the old 4.3. I'm checking the roms on sammobile and I realize that I'm running into another problem - which Canada (Rogers) should I download?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
Oh boy... You didn't read my post. Okay, GET 4.4 FIRMWARE NOW. Try to get the device to show on Odin. It can be recovered, but its a real pain now honestly and its not a 100% shot here. First download 4.4 firmware and try to get it to show on Odin. Reply when done, and I'll find my list that has possible recovery of device methods. Wrong firmware version... I wish you had read in time.

Edit: You possibly overwrote bootloader partition. I'm not sure, but its in my old notes. I had AT&T SGH-I747. Very similar, but very different also. If I find a forum that has a step by step way to recover device I'll share the link.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g33kos:
So if i know the old rom I747MVLUEMK5, can i find which new rom i have to download?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
Amy that are 4.4+, I'd go with the oldest KitKat stock ROM. Best chance for recovery, since you've injected 4.3 files into the device. If you get it on Odin, you got a chance. No promises. My last fix was 100%... This one is not. Its down to getting the 4.4 ROM into the device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g33kos:
Ok, i started downloading the first one from the top of this list
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
Make sure this is an official firmware from Rogers... 'Stock ROM'. Not a ROM created and posted on xda by a dev. You need original firmware to have amy chance to recover
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g33kos:
It is from sammobile and it takes 1 hour :(

But good you mention that :good: because I was thinking earlyer why not to flash a custom rom instead of stock one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
OK :) is the device connected to PC and showing up on Odin currently? If it is DO NOT DETATCH IT! Its really tough to get them to show up in this state. You may need to flash it several times to get it to work. You need recovery partition to work, and then FLASH Philz recovery and AFTER PHILZ IS SUCCESSFULLY FLASHED USE IT TO flash a custom ROM with a 4.4+ kernel... You're set then, but it might be a bumpy road or may not be able to get recovery to flash and boot. EDIT: Caps are an edit. Be 100% certain Philz Recovery is the right one for 747M, same with ROM and be 100% certain its a 4.4+ KitKat Kernel, at yjs point obviously a custom ROM is okay. As long as that kernel, modded or not, is a 4.4+ version. I added these things because I made a lot of assumptions to your abilities and knowledge of this. I hope this clarifies things. If you need help, there are tons a great devs and users here that'll do their best, but use the search button. If you had, youd have never flashed that ROM :\
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g33kos:
Yes, I think so., because i see the message "added". and the ID COM window from left upper corner is blue

---------- Post added at 02:01 AM ---------- Previous post was at 01:37 AM ----------

So, if the recovery partition is broken, since is not part of android os, can be re-write when i flash the os, or separately? What i mean is recovery coming with os in the same package?

And another question - my problems start from a corrupted custom recovery or maybe not compatible (and after that I was doing the stupid things with flashing wrong rom)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Flashing the stock Rogers ROM via Odin will flash the stock recovery to your phone.

If your phone still doesn't boot, boot into stock recovery, do a factory wipe/reset, and you should be good to go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g33kos:
:fingers-crossed:eek:K guys, download will be done in a minute, I'll be back after flashing

---------- Post added at 03:01 AM ---------- Previous post was at 02:25 AM ----------

@Lt1streconbn and [MENTION=4673498]audit13[/MENTION], thank you for helping me out. It is 5 am, I'm going to sleep, but I can sleep peacefully because of you.

The phone is back and perhaps tomorrow i'll start over with new room and philz, so stay tuned in case disaster strikes:D

Thank you thousand times!:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
Hey man... That's what's this place is all about. I'm glad you were able to recover the device. Hit that thanks button for me is all i ask :) and be more careful in the future. If unsure on a custom ROM, ask a question in that thread. Its better than a softbrick or potential hardbrick. Good Night!

Edit: In Philz, there is an option to clean up for flashing a new ROM thru recovery. AFTER YOUVE CONFIRMED YOU HAVE A COMPATIBLE ROM ON YOUR SD CARD ALONG WITH A NANDROID BACK JUST IN CASE, hit that option. It formats everything you need with one touch. Ya just can't beat that! Then you're set to flash. Be sure you make a backup... that's the biggest mistake ppl make. Being in too big of a hurry. Use that search button, and you'll find tons of ppl that'll help. Luckily you got me, and I knew what to do :) Good Job!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g33kos:
I have tried to flash Philz recovery but it soft bricked the phone. Because last time it happens the same with TWRP recovery, i think it is something wrong with the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
How are you flashing TWRP and Philz? You're using the d2lte version for both?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Olalaekan:
plzzz help....

can a gt-i9300 board work in sgh-i747 .............................

my s3 att is bricked and i happen to have a working gt-i9300 board...

plzzzz . i love my phone