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.
Related
Okay, as a newby poster on this forum, I can ask this question here, hopefully someone reads here that can help *smile*.
I've followed the rooting guide for my post JB OTA updated Galaxy S3. My phone is now apparently rooted, I can grant root access to apps and all. I should have a custom recovery installed as well (I chose TWRP since a lot of people seem to choose CWM, and I'm a rebel without a cause), but I'm not sure, since when I booted out of recovery after installing the SU app, I didn't see the "Disable recovery flash" prompt. And I haven't tried to boot into recovery mode yet to verify whether the TWRP version that I installed is still there. Doesn't seem to have affected the resulting root access ability one way or the other, though.
My question is that when I boot my phone normally now, I see an unlocked lock icon, and "CUSTOM". Since I re-flashed the stock boot when I was done, this is a bit disturbing, I didn't expect that. I've read that if I have a custom recovery that I'll see this even if I have stock boot. Is this true? I think that stock boot is a good idea, but am not convinced that I have it. Is there any way to tell if I have a stock boot or not?
A little puzzled, although I definitely like the rooted phone better than the non-rooted one, so thanks much for that.
Just rebooted the phone into TWRP recovery a couple of times this morning, so I guess that I still have the custom recovery installed *smile*. And I'm also assuming that flashing the stock boot at the end of rooting worked, despite the unlocked lock icon and "CUSTOM" when I boot my phone now.
I guess there's no need for a reply here, since I've answered at least part of my own questions. I'm assuming then that I'm seeing "CUSTOM" and the unlocked lock icon when I boot because I have the custom recovery installed, and when I un-root it will go away. I've already set my flash count back to 0, since I wanted to remember to do that while I still had root, in case I un-root to send the phone to Samsung, and forget to do that.
Again, thanks for the guide thread on rooting, very helpful. The only first-time snag was booting into TWRP from Odin mode so I could install the SU app. Eventually figured out how to do that, so when/if I do this again should be much quicker.
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.
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
I have successfully unlocked and am using the G930VL and installed the official verizon version rom to get rid of anything straighttalk related and it has been working great!
But....i want to install custom roms in order to do that i need CWM or TWRP. I cannot seem to get either one to install because of a "Secure check fail: recovery" message. Any suggestions?
also does anyone have a good link here on XDA for G930V/G930VL rom's?
I am rooted so this should be possible somehow what am i missing?
You can gain root but not twrp http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
peachpuff said:
You can gain root but not twrp http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
Click to expand...
Click to collapse
Is there any roms that will work? I have found things like King rom but that's for the edge. Even so...how would i install it without TWRP? Would i have functionality issues with G930VL? I haven't had to install from ADB in a long time but if someone guides me i'd still be willing. The reason why this is an issue is i can't get out of the security messages that happen in the OS. Every time i boot it keeps saying i have to reboot because it finds a problem (due to it being rooted)....1 time my phone wouldn't even boot up which is when i installed the official verizon OS and wipped everything straighttalk except the bootloader(for obvious reasons i'm not touching that!).
Ziron999 said:
Is there any roms that will work? I have found things like King rom but that's for the edge. Even so...how would i install it without TWRP? Would i have functionality issues with G930VL? I haven't had to install from ADB in a long time but if someone guides me i'd still be willing. The reason why this is an issue is i can't get out of the security messages that happen in the OS. Every time i boot it keeps saying i have to reboot because it finds a problem (due to it being rooted)....1 time my phone wouldn't even boot up which is when i installed the official verizon OS and wipped everything straighttalk except the bootloader(for obvious reasons i'm not touching that!).
Click to expand...
Click to collapse
You'll have to ask the folks in that thread, i don't have any answers for you except that thread that i looked over before.
With Qualcomm Snapdragon's security feature DM-Verify, it is extremely unlikely. Even if you took the stock image from Verizon and did nothing more than deodex it, dm-verify will not allow the ROM to boot (from what I've read). There are other security features that prevent the Bootloader form being messed with.
Root was a dream come true. An unlockable bootloader (while a developer version does exist) is a more unachievable dream.
Ziron999 said:
I have successfully unlocked and am using the G930VL and installed the official verizon version rom to get rid of anything straighttalk related and it has been working great!
But....i want to install custom roms in order to do that i need CWM or TWRP. I cannot seem to get either one to install because of a "Secure check fail: recovery" message. Any suggestions?
also does anyone have a good link here on XDA for G930V/G930VL rom's?
I am rooted so this should be possible somehow what am i missing?
Click to expand...
Click to collapse
"I have successfully unlocked" what type of unlock are you speaking of?
I noticed after taking one of the lineage updates I lost root. I tried to reroot with odin and managed to pork my phone quite good. It took me until about now to get it rooted, unlocked and finally TWRP loaded. Recovery was fighting me the most. Refused to install in odin. I finally got a working rom on it so it would boot. Used casual to root and unlock but TWRP failed in that as well. I finally tried a TWRP app (not the official one, I couldn't get that to work) and I may have my phone back now. Waiting to see if my backup is going to work. Welp, it didn't like the restore and I got the ! triangle saying go back to verizon.
While I was looking through my drives I noticed I have a ton of files but don't know exactly what they are. I've had this phone since I pre-ordered it so at one time the files were valid. What files exactly do I need to totally unpork a phone? I have odin 3.07, the VRALEC bootchain, the VRALF one but odin says it's invalid, and a file called combination_I535VRALG1_I535VZWALG1_743127_REV09_user_low_ship. Using them I can get my phone back to seemingly stock.
Is there a better way? Or at least a way to totally start from scratch and hopefully get lineage back on? I know not to take any of the OTAs since they will relock the bootloader. I don't like that it seemed that it was going to automatically install the update but I'll just keep the phone off until I can sort it. I also have a bunch of other files across 3 computers so if there is a file that's needed but isn't posted somewhere there is a chance I might have it already.
I've been searching for the past day and I've found tons of info but some things don't work and some only kinda work. Any help would be much appreciated.
More info: I am on 4.04 so the bootloader should not be locked. The phone is beat up and the USB connector is wonky. Only a few cables will work and I have to make sure it doesn't move or it will disconnect. It does mention that the secureboot is enabled in download.
I've had it rooted, running a stockish rom and managed to get TWRP on it but when I went to restore my lineage backup, it all went to hell.
So I'm now having issues with the bootloader. ON the download screen it says custom binary download yes (5 counts), Current binary samsung official, system status official and secureboot enable. Pretty sure that means casual didn't work. I have root but not bootloader. Is there another option than casual? I've seen ez unlock 1.2 mentioned but the links are dead.
Why am I remembering flashing something in stock recovery? It's been a long, long time since I've gone back this far. I feel like I'm close since I saw the unlocked screen last night but restoring screwed that all up.
This doesn't make sense. I installed TWRP but it still says the same as above leading me to think my bootloader is not unlocked. I don't get the unlocked boot screen either.
How can I install TWRP with a locked bootloader?
Well it's obious that I can get root, install TWRP but for some reason casual will not unlock the bootloader. I can't seem to find the old thread nor any files to just unlock the bootloader. I know somehow I did it last night as I saw the unlocked screen it's just damned if I can do it now. It must have been another file I had at home but don't have here on the laptop.
It's damn frustrating since this time yesterday I had a working phone running nougat and my dumb ass broke it.
I know this forum is a bit dead, as expected for a 5 year old phone but hopefully someone will see this and have some sage like advice.
Turns out It takes almost a week and a mixture of 3-4 guides here. Some Odin, some Casual, some TWRP flashing and luck. FInally I'm back to where I was before I hit the wrong button.