Database Info

GS3 problems..

I own a t-mobile g2x that is rooted and has been flashed multiple times. However, rooting and flashing on that device is extremely different than the GS3. My buddy owns a verizon GS3 and has an unlocked boot loader (an unlocked lock appears under "samsung" logo at boot). Does this mean that it is rooted? I was able to install titanium backup and ROM manager and flash CWM 5.x.x.x on it without any problems so I am assuming it is rooted. However, he is having trouble downloading anything from the internet. For some reason anytime he attempts to download something on his phone an error shows up saying "download failed." Any idea why this is happening? Also, there are a few ROMS in the dev section that he's interested in flashing. I'm not very knowledgeable about this device....but if it has an unlocked boot loader and is rooted, is he all set to flash a custom ROM?

Pain-N-Panic said:
I own a t-mobile g2x that is rooted and has been flashed multiple times. However, rooting and flashing on that device is extremely different than the GS3. My buddy owns a verizon GS3 and has an unlocked boot loader (an unlocked lock appears under "samsung" logo at boot). Does this mean that it is rooted? I was able to install titanium backup and ROM manager and flash CWM 5.x.x.x on it without any problems so I am assuming it is rooted. However, he is having trouble downloading anything from the internet. For some reason anytime he attempts to download something on his phone an error shows up saying "download failed." Any idea why this is happening? Also, there are a few ROMS in the dev section that he's interested in flashing. I'm not very knowledgeable about this device....but if it has an unlocked boot loader and is rooted, is he all set to flash a custom ROM?
Click to expand...
Click to collapse
The unlocked lock means that the bootloader is locked but a custom recovery is installed. Make sure he used the 1.2 version of ez unlock.
If you flash a custom rom without it being unlocked you'll have to Odin back to stock. Anyways, he should be exactly sure what he's doing and how he'd go about fixing it if something does go wrong. There are many guides that are stickied that should help him recover from any situation.
Before flashing anything, I'd make an IMEI backup since the guide to fix it has been pulled.
The download error usually happens with either a weak Internet connection or it eventually timing out. He's most likely trying to download large files. Make sure he downloads under a strong wifi or 4g connection.
Sent from my SCH-I535 using Tapatalk 2

Gotcha. Appreciate the help in the right direction. Ill go through the stickies when i have some time.
-custom sig.

Questions about updating from 4.1.2 to 4.3. What Do I loose?

So I tried reading some other threads, but honestly, alot of it just sounds waaaaaay too technical to me. I have a rooted 4.1.2 Verizon S3. Im getting the OTA notification to instal 4.3, but I cant install it until I go back to stock and then install it after Im unrooted. But I dont know if doing any of this is what I'm getting for what Im loosing. I dont know what a difference in modems will make, or things like that, but the big one I see is that it locks out Bootloader and able to install custom roms. Does that mean I also loose my ability to boot into Clockwork Mod? Or the ability to boot to the rom installation screen (Vol Down, Home and Power, then Vol Up)?
So can someone just help me out, and to pull a phrase from the reddit book, explain it to me like im 5.

MattDusza said:
So I tried reading some other threads, but honestly, alot of it just sounds waaaaaay too technical to me. I have a rooted 4.1.2 Verizon S3. Im getting the OTA notification to instal 4.3, but I cant install it until I go back to stock and then install it after Im unrooted. But I dont know if doing any of this is what I'm getting for what Im loosing. I dont know what a difference in modems will make, or things like that, but the big one I see is that it locks out Bootloader and able to install custom roms. Does that mean I also loose my ability to boot into Clockwork Mod? Or the ability to boot to the rom installation screen (Vol Down, Home and Power, then Vol Up)?
So can someone just help me out, and to pull a phrase from the reddit book, explain it to me like im 5.
Click to expand...
Click to collapse
OK, if you update to 4.3, it will lock your bootloader and you CAN NOT install custom rom/kernel or recovery (CWM/TWRP) any more. Your phone will be just like stock phone with stock recovery. The only option is you still can root. Just FYI, there is a work around called safestrap, basically it allow you to install custom recovery (CWM/TWRP) on a separate partition and so is your custom rom, don't want to get into this too much). Hope you got your answer.

Thanks. Thats really what I wanted to know. Do you know if this is something that will most likely forever be permanent or something that a fix or workaround to re-implement that ability back in the future?

MattDusza said:
Thanks. Thats really what I wanted to know. Do you know if this is something that will most likely forever be permanent or something that a fix or workaround to re-implement that ability back in the future?
Click to expand...
Click to collapse
Based on history, we never hack the bootloader, the reason we could unlock the bootloader is there a leaks. So I won't hold my breath on this...However, currently we have a work around which called safestrap, an app that use a separate partition to install custom recovery and rom, kind of dual O/S. The negative is it support limited custom rom and cut down the storage space.

buhohitr said:
Based on history, we never hack the bootloader, the reason we could unlock the bootloader is there a leaks. So I won't hold my breath on this...However, currently we have a work around which called safestrap, an app that use a separate partition to install custom recovery and rom, kind of dual O/S. The negative is it support limited custom rom and cut down the storage space.
Click to expand...
Click to collapse
I have faith that loki will work for our phone. If it does all we would need to do is lokify our aosp rom after we flash them in safestrap or have a pre edited rom. I think all we need to do is have the right aboot.img or someone who knows more about what to do than myself.

Is there a version of safestrap for the S3? I can only find ones for the s4 and the note 3 for samsung products.

MattDusza said:
Is there a version of safestrap for the S3? I can only find ones for the s4 and the note 3 for samsung products.
Click to expand...
Click to collapse
Its in the development section. And just a FYI I was wrong Loki will not work with safestrap unless hash code applies the Loki patch to safestrap. I have a strange feeling Loki exploit is patched for our boot loader but we will see.

Verizon Galaxy S3 4.4.2 Rooted Custom Recovery Question

Looked through google, looked through threads, can find nothing whatsoever to help.
Have Verizon Samsung Galaxy S III Unlocked running Straight Talk VIA sim card. Everything works.. as a regular old phone with root. (rooted with Kingoroot - basically I googled "root galaxy s3" and followed those steps.. that much works fine, though it is not to be confused with the chinese king root. I tried the trick of swapping out king root for SU and, well.. yeah didnt work.)
Problem is I'm running 4.4.2 (the dreaded locked bootloader) and everything I try when it comes to installing custom recovery either doesn't work, bootloops the phone, or hard bricks it. v_v
so as someone who backs up their backups, (thank you OCD fairy), running around with a phone I can't backup puts me on edge, to say the least.
tried safestrap (says not secured. still says not secured after install. does nothing.)
tried various CWM and TWRP via apk installs (whatever that app is you install then tell it to install cwm) ..wouldn't install
Odin, depending on which version I install (e\ not which version of odin, which version of custom recovery), either gives me errors or hardbricks my device.
SO.. I'm looking for someone who has a Verizon Galaxy S III and who has a custom recovery on it to tell me how the devil they managed that one.
Cheers all!!

Drach0n said:
Looked through google, looked through threads, can find nothing whatsoever to help.
Have Verizon Samsung Galaxy S III Unlocked running Straight Talk VIA sim card. Everything works.. as a regular old phone with root. (rooted with Kingoroot - basically I googled "root galaxy s3" and followed those steps.. that much works fine, though it is not to be confused with the chinese king root. I tried the trick of swapping out king root for SU and, well.. yeah didnt work.)
Problem is I'm running 4.4.2 (the dreaded locked bootloader) and everything I try when it comes to installing custom recovery either doesn't work, bootloops the phone, or hard bricks it. v_v
so as someone who backs up their backups, (thank you OCD fairy), running around with a phone I can't backup puts me on edge, to say the least.
tried safestrap (says not secured. still says not secured after install. does nothing.)
tried various CWM and TWRP via apk installs (whatever that app is you install then tell it to install cwm) ..wouldn't install
Odin, depending on which version I install (e\ not which version of odin, which version of custom recovery), either gives me errors or hardbricks my device.
SO.. I'm looking for someone who has a Verizon Galaxy S III and who has a custom recovery on it to tell me how the devil they managed that one.
Cheers all!!
Click to expand...
Click to collapse
A custom recovery can only be flashed on an unlocked bootloader. Trying to flash a custom recovery on a locked bootloader will result in a brick. The only available recovery on it is safestrap
Sent from my Nexus 5

ShapesBlue said:
A custom recovery can only be flashed on an unlocked bootloader. Trying to flash a custom recovery on a locked bootloader will result in a brick. The only available recovery on it is safestrap
Sent from my Nexus 5
Click to expand...
Click to collapse
..I gathered that. I was basing my attempts off the threads I found where the OP "forgot" to mention which android OS he was using on his (or her) galaxy s3 and then omigawd installed custom recovery on it. Where nobody has yet been able to unlock the 4.3 and 4.4.2 bootloader for the galaxy s3 as yet (to my knowledge; if I'm wrong please correct me) this leaves me with safestrap, the custom recovery that doesn't touch the bootloader during install. I know this as well. Perhaps I should have clarified this, but I thought it was obvious to the folks at xda. *shrugs*
And the part where I said safestrap isn't working for one reason or another is where I was hoping to attract someone who knew how to help instead of someone who only knows how to make generic statements (+1) [e\ ftr, attempting to flash non-safestrap recoveries resulted in an error 4 times out of 5, not a brick.]
that said, I will ask again, if someone has 4.4.2 on their s3 as well as custom recovery, please come post here.
sadly, inb4 more +1ers

When you ask a question that's been asked and answered dozens of times before, you're going to get the same "generic statement" in response, because it's the right answer to your question. Your bootloader can't be unlocked, and therefore you can't install a custom recovery on your phone.

Jacquestrapp said:
When you ask a question that's been asked and answered dozens of times before, you're going to get the same "generic statement" in response, because it's the right answer to your question. Your bootloader can't be unlocked, and therefore you can't install a custom recovery on your phone.
Click to expand...
Click to collapse
*sigh* another illiterate. Try reading before posting yeah? I *know* my bootloader cant be unlocked, and I know that a custom recovery /can/ be installed, or are you saying safestrap doesn't exist? look I'm asking for help here not drivel.
..rerolling..

Q: What did you have for breakfast today?
A1: last week, I had breakfast in Deleware!
A2: Last night's dinner was good!
...
xda: the community where post count means more than relevant answers.
*sigh*
looks like I'm going to have to figure out safestrap on my own. whether there is another method for installation besides via apk, why it failed to install, whether safestrap is the only custom recovery that works by not touching the bootloader, why it hardbricked my phone.. etc
guess I'll post the answers somewhere intelligent like Android Authority.
have fun with your +1s
now go die in a fire. cheers

Drach0n said:
Q: What did you have for breakfast today?
A1: last week, I had breakfast in Deleware!
A2: Last night's dinner was good!
...
xda: the community where post count means more than relevant answers.
*sigh*
looks like I'm going to have to figure out safestrap on my own. whether there is another method for installation besides via apk, why it failed to install, whether safestrap is the only custom recovery that works by not touching the bootloader, why it hardbricked my phone.. etc
guess I'll post the answers somewhere intelligent like Android Authority.
have fun with your +1s
now go die in a fire. cheers
Click to expand...
Click to collapse
Honestly I answered your question. It's hard to talk about safestrap other than what I've learned about it. The other member was right, it gets tiring answering the same questions all the time and once in awhile people don't appreciate the answers they are given.
There are threads for safestrap as well as most of the options here on xda. And feel free to go to another forum, your posting questions in a dying forum for the VZW S3. There's not many people who are really that interested in the locked down version anymore. It's very sporadic as far as people and questions go. But to be rude about it just isn't needed.
It's not about post count at xda it's about helping the community. I've been around here long enough to know this. And if you feel someone isn't helpful there's something called a PM instead of calling them out here on the forums. I grow tired of people not being appreciative of anything when someone takes the time to do there best to explain something to someone else
Sent from my Nexus 5

running 4.4.2
PM sent. I might be able to help with that.

lost recovery

I rooted my stylo last month and shortly after I flashed a twrp recovery in which I thought it was for my ls770. Well after I did that I got that error 1003 thing when I try to boot into recovery. So I now can't boot into recovery So I found a factory recovery file and flashed it also and I still can't boot into recovery. Can someone help please and thanks..

What version of Android? I did the same thing and luckily I had backed up a recovery with Flashify. I can see if I still have the backup. The recovery was for 5.1.1 ZV5

The one I found I think was for 5.0 but I'm on 5.1.1. That would be great @mabry

mabry said:
What version of Android? I did the same thing and luckily I had backed up a recovery with Flashify. I can see if I still have the backup. The recovery was for 5.1.1 ZV5
Click to expand...
Click to collapse
Do you have the stock recovery or what cause I need it asap

My bad bro. When I updated to Marshmallow I formatted my external SD in hope of the new storage feature. I lost it. I am sure 6th Hokage, or Dominick might have one laying around. They the main devs on the Boost Stylo.

did you ever get the stock recovery, I have the same problem...

ShonPu said:
did you ever get the stock recovery, I have the same problem...
Click to expand...
Click to collapse
No I have been trying like a mad man to get the recovery back but nothing is working. And I can't find anyone that can help me. It is driving me insane...

ShonPu said:
did you ever get the stock recovery, I have the same problem...
Click to expand...
Click to collapse
Add me to the list. I can't get anything but secure boot error 1003.

Me too..
Add me as well....
Rooted and went to install twrp..secure boot error 1003.
Anybody get any news on this?

The TWRP that is available out there right now with all the tutorials isnt for our devices (LS770). Theres not much going on with our devices because of the locked bootloader that lg seems to know nothing about; let alone any support for this devices alongside marshmallow. My goal is to port TWRP to our phones and find a backdoor in but im caught up in a bunch of different projects right now and juggling it with work. Plus ive gotta learn how to build these things. If anybody could tell me anything about our phone that i cant figure out thatd be wonderful. Ill try to get the recovery image posted on my drive when i go on my computer next.

Lg lls770
So I've read even just using King root it will lock up your phone, i had done that with my other lg ls770 and tried installing the twrp recovery. Any ideas if i will run into the same problem just using King root? And how would i go about making a back up of my stock recovery?

The ls770 has a locked bootloader. You can't just put any twrp recovery on it. You may be able to use kingroot temp, but I bricked twice using it, and can't offer any advice. If you have read enough of the ls770 brick stories including mine, you'll see there is no real pattern to bricking with kingroot. I successfully used it and restarted and re temp rooted for days, changing build.prop uninstalling google apps, then WHAM, brick out of thin air. Some were bricking straight away after kingroot with only restarting. If you do use kingroot to temp root I hope you'll report back and tell us how it is going, Thanks

So any idea if checking the oem unlock box in developer options and then going to fastboot/download mode would unlock the bootloader? I'm not very advanced with tinkering with android but i can go about the basics i guess

Finallyrooted said:
So any idea if checking the oem unlock box in developer options and then going to fastboot/download mode would unlock the bootloader? I'm not very advanced with tinkering with android but i can go about the basics i guess
Click to expand...
Click to collapse
The oem unlock will not unlock the bootloader.The bootloader is locked by Boost/sprint/virgin. It's probably not going to be unlocked. The only LG's I know that have unlocked bootloader are Tmobile/metropcs. I hope kingroot gets this worked out as we know they have no future without being able to root phones. I made a post on the kingroot page here at XDA asking about what they might do now with marshmallow. I haven't heard from the main @Kingxteam but I keep hearing they are working on it

Help rooting Samsung galaxy j3 (sm-J337a)

It seems everywhere I go there is no root for this phone (sm-J337a) it's an at&t phone. I used kingoroot, kingroot and basically any root out there. nothing has worked. So this seems that it has no root made for it yet? is there any possibility for someone to do this? Sorry, I'm not too good at rooting as a whole. But I've used Odin and things like that before.
there doesn't even seem to be CWM or TWRP for this phone either.
it's running Android 8.0 and was made in 2018.

Right?
I'm having the same issue. I can't figure out how to root mine either and I've got the same phone and carrier.

nickthekid said:
It seems everywhere I go there is no root for this phone (sm-J337a) it's an at&t phone. I used kingoroot, kingroot and basically any root out there. nothing has worked. So this seems that it has no root made for it yet? is there any possibility for someone to do this? Sorry, I'm not too good at rooting as a whole. But I've used Odin and things like that before.
there doesn't even seem to be CWM or TWRP for this phone either.
it's running Android 8.0 and was made in 2018.
Click to expand...
Click to collapse
Details of your current ROM Please..?
Build number etc...

Hi all.. I know this thread is a little old but thought id add this.. As of this date Ive found no ROOT solution for the SM-J337A - AT&T variant either.. I have found a lot of other software and such and as soon as I can get it all sorted, cataloged, and uploaded to the cloud I will see about placing some links here somewhere to all of them.. Not sure how long it will be..Stay tuned...
I happen to inherit a J337A with a cracked screen but was working fine until I updated it and tryed ROOTing it.. Im still Playing with it to see if I can revive it.
Having issues finding a UB compatible Firmware set that I dont have to pay for.
Am needing "J337AUCSBBTI1" or maybe "J337AUCSABTE1" to see if I can bring it back to life.. I may end up pitching it tho...
My Device:: SM-J337A
FCC-ID : A3LSMJ337A
Samsung/j3toplteuc/j3toplteatt
CURRENTLY STUCK ON COMBINATION ROM : (8.0.0/R16NW/J337AUCUBATH1/user/release-keys)
BINARY/BOOTLOADER : UB

iamoz said:
Hi all.. I know this thread is a little old but thought id add this.. As of this date Ive found no ROOT solution for the SM-J337A - AT&T variant either.. I have found a lot of other software and such and as soon as I can get it all sorted, cataloged, and uploaded to the cloud I will see about placing some links here somewhere to all of them.. Not sure how long it will be..Stay tuned...
I happen to inherit a J337A with a cracked screen but was working fine until I updated it and tryed ROOTing it.. Im still Playing with it to see if I can revive it.
Having issues finding a UB compatible Firmware set that I dont have to pay for.
Am needing "J337AUCSBBTI1" or maybe "J337AUCSABTE1" to see if I can bring it back to life.. I may end up pitching it tho...
My Device:: SM-J337A
FCC-ID : A3LSMJ337A
Samsung/j3toplteuc/j3toplteatt
CURRENTLY STUCK ON COMBINATION ROM : (8.0.0/R16NW/J337AUCUBATH1/user/release-keys)
BINARY/BOOTLOADER : UB
Click to expand...
Click to collapse
I can help you with that if you still need it. I have my j3 rooted with magisk, although there is no twrp or any custom recovery for that matter..
I can give you the exact files along with the patched magisk file and you'll have to flash it with patched odin and you should be good. Let me know.

rip21skinz said:
I can help you with that if you still need it. I have my j3 rooted with magisk, although there is no twrp or any custom recovery for that matter..
I can give you the exact files along with the patched magisk file and you'll have to flash it with patched odin and you should be good. Let me know.
Click to expand...
Click to collapse
Yes I would be interested in having those files please... Either upload them here or I can give you an email if you prefer... Let me know..

rip21skinz said:
I can help you with that if you still need it. I have my j3 rooted with magisk, although there is no twrp or any custom recovery for that matter..
I can give you the exact files along with the patched magisk file and you'll have to flash it with patched odin and you should be good. Let me know.
Click to expand...
Click to collapse
Instead of sending a patched magisk file would you mind sending over the method you used to root? If you did what I think you did I'm very confused. The phone is OEM locked although this hasn't stopped others from accessing root before. If you can confirm you have the phone we have, the SM-J337A ATT then you can pull out the boot and recovery images using a root app. Then I could develop a working TWRP for our device. But ofc this is only possible if you explain how you went about rooting the device. Thanks in advance.

NonStickAtom785 said:
Instead of sending a patched magisk file would you mind sending over the method you used to root? If you did what I think you did I'm very confused. The phone is OEM locked although this hasn't stopped others from accessing root before. If you can confirm you have the phone we have, the SM-J337A ATT then you can pull out the boot and recovery images using a root app. Then I could develop a working TWRP for our device. But ofc this is only possible if you explain how you went about rooting the device. Thanks in advance.
Click to expand...
Click to collapse
I have both SM-J337P/A and it works the same on both. I'm not sure why you wouldn't be able to be oem unlocked? You mean greyed out? Or does it not show up at all or what? If I go into developer options I have the oem unlock option, which then allows me to unlock the bootloader. If yours is greyed out I saw a solution on XDA a long time ago, maybe a year ago. I'd have to look for it in my files, I know I saved it somewhere. Let me know what you meant by that and we can go from there

rip21skinz said:
I have both SM-J337P/A and it works the same on both. I'm not sure why you wouldn't be able to be oem unlocked? You mean greyed out? Or does it not show up at all or what? If I go into developer options I have the oem unlock option, which then allows me to unlock the bootloader. If yours is greyed out I saw a solution on XDA a long time ago, maybe a year ago. I'd have to look for it in my files, I know I saved it somewhere. Let me know what you meant by that and we can go from there
Click to expand...
Click to collapse
I do not have the option to OEM Unlock the phone period. It is not in my developer options unfortunately. If you do find something of that nature please do contact me. Also if you would like a TWRP for your device I'd be up to developing it, although I wouldn't be able to maintain bugs... All I need is the kernel and I can get it done.

Any updates on this?