Related
Hello all,
I managed to grab a Cricket-branded Galaxy S5. I decided this was the best area to post and ask questions because I believe this phone is locked down the exact same as the AT&T one (and might even be 1:1 other than software and the logo on the back), plus the fact that AT&T owns Cricket.
Currently, I only have the device rooted using TowelRoot.
I want to install SafeStrap, but wasn't sure if it would go smoothly, and I don't have an image to use with ODIN if I mess things up.
Can anyone suggest how to best create a stock image, or provide links/info to a stock ROM for this phone on Cricket?
Model: Samsung SM-G900AZ
Android version: 4.4.2
Baseband: G900AZTUU1ANE7
Kernel: 3.4.0-1732610 [May 29]
Build: KOT49H.G900AZTUU1ANE7
I would like to back it up, install SafeStrap, and try out some custom ROMs (I know Bootloader is locked, so I'd be limited in that regards), or possibly install Xposed to tweak some device behavior.
Can someone please advise?
Thanks.
Install safestrap, the worst that can happen is it may say installed but when you try to reboot to recovery, it will just reboot like normal and its as if the installation didn't actually 'stick'.
That's what happened to me...
After uninstalling the safeatrap installer and re-installing the app, then re-running the app, it said that safestrap was successfully installed, and this time upon tapping 'reboot to SS recovery' it actually worked.
You definitely do not need all the trouble of making a backup right now.. Just install ss and then make a full backup as usual.
Ps we have the same phone
Recently bought a s5 cricket, and what I have rooted for odin using the method cf-root, now I want to change the recovery to philz and change the kernel by one a bit more efficient and thrifty, and read about the Ss but not sure which version should I use because I can not find any for my team, I would assert that this circulating ND3 or that could use?
This is my phone
Venomdroid said:
Recently bought a s5 cricket, and what I have rooted for odin using the method cf-root, now I want to change the recovery to philz and change the kernel by one a bit more efficient and thrifty, and read about the Ss but not sure which version should I use because I can not find any for my team, I would assert that this circulating ND3 or that could use?
Click to expand...
Click to collapse
I hate to tell you that will be impossible..
Unless soneone can correct me, i am 99% sure our boooader is locked and will remain as such.
So, safeatrap is your only option for recovery/flashing, and in addition you will be limited to flashing tw-based Roms. Custom kernels are not an option unless /until the bootloader is unlocked.
Sorry to be the Bearer of bad news
Swimguy14 said:
I hate to tell you that will be impossible..
Unless soneone can correct me, i am 99% sure our boooader is locked and will remain as such.
So, safeatrap is your only option for recovery/flashing, and in addition you will be limited to flashing tw-based Roms. Custom kernels are not an option unless /until the bootloader is unlocked.
Sorry to be the Bearer of bad news
Click to expand...
Click to collapse
I understand, however I wonder what version of SS I use to at least make a backup of my current rom and to test some custom rooms? the truth is that I feel bound hand and buy the tlf a good price and would like to customize much as my S3, but hey I'll have to resign myself to use it well and lighten the version that brings factory.
Edit : in case anyone wasn't sure here is the link to safestrap http://forum.xda-developers.com/showthread.php?t=2794087
Hi, I'm kind of new to this, but I have a Cricket S5, and have some quick questions regarding rooting.
1. Is there anyway to fully unroot the cricket phone after rooting it with towelroot? (unvoid the warranty)
2. Will the bootloader ever be unlocked, so that I can flash custom roms?
Thanks for any help!
13jeremywt said:
Hi, I'm kind of new to this, but I have a Cricket S5, and have some quick questions regarding rooting.
1. Is there anyway to fully unroot the cricket phone after rooting it with towelroot? (unvoid the warranty)
2. Will the bootloader ever be unlocked, so that I can flash custom roms?
Thanks for any help!
Click to expand...
Click to collapse
1. Yes, theres an unroot option in SuperSU that ive suggested to be used or you can reflash with odin, there are guides in the general forum if you check there
2. Will it ever be unlocked? Most likely not. Can it be unlocked? Yes, but unless something pops up it would have to be by getting the decryption key.
Sent from my SM-G900A using Tapatalk
The bootloader is unlocked. From the beginning, unlocked. No need to decrypt anything or get a key or any of that hassle.
Yes, you can fully unroot if you choose
Rakuu said:
1. Yes, theres an unroot option in SuperSU that ive suggested to be used or you can reflash with odin, there are guides in the general forum if you check there
2. Will it ever be unlocked? Most likely not. Can it be unlocked? Yes, but unless something pops up it would have to be by getting the decryption key.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Rakuu,
Im attempting to UNroot my sm-900az to stock and for some reason i cant find super user in order to retun to stock via that method, do you or anyone else know where to find the Stock ROM that i could use ODIN to go back with???
Mababel05 said:
Rakuu,
Im attempting to UNroot my sm-900az to stock and for some reason i cant find super user in order to retun to stock via that method, do you or anyone else know where to find the Stock ROM that i could use ODIN to go back with???
Click to expand...
Click to collapse
There are multiple stock roms in the general section.
Sent from my twi5ted SM-G900A using Tapatalk
If you didn't know the 5.1.1 update comes with a "locked" bootloader (G920T) that does not allow you to flash custom recoveries. I would like to know what your status is if you don't mind because I think the more people who are stuck like me the more developers will say we need to come up with a fix for flashing custom recoveries issue.
The bootloader isn't locked. Twrp just needs to be updated. Won't happen til kernel source for 5.1.1 drops
Did we really need another thread about this?
Edit: Please explain how someone "accidentally" upgraded from rooted 5.0.2 to 5.1.1
mikeyinid said:
The bootloader isn't locked. Twrp just needs to be updated. Won't happen til kernel source for 5.1.1 drops
Click to expand...
Click to collapse
That is why I put "locked" in quotes and no I am not sure of that the phone blocks any custom recovery installed and I explained in another thread how cf-auto-root is just a recovery that is why it isn't working either.
se1000 said:
Did we really need another thread about this?
Edit: Please explain how someone "accidentally" upgraded from rooted 5.0.2 to 5.1.1
Click to expand...
Click to collapse
What I mean by that is if you had no knowledge of the changes in the bootloader and the fact you can't downgrade
ethanscooter said:
Accidently* wasn't really paying while typing and what I mean by that is if you had no knowledge of the changes in the bootloader and the fact you can't downgrade
Click to expand...
Click to collapse
So what you meant is, "If you downloaded a 1.3GB file and ODIN'ed back to stock just to upgrade and ignored the big bold warning that you couldn't downgrade" OR "If you downloaded a 1.3GB file and ODIN'ed to a new version of android that there was an active thread where it was CLEAR there was no root method"
"Accidentally"
ethanscooter said:
That is why I put "locked" in quotes and no I am not sure of that the phone blocks any custom recovery installed and I explained in another thread how cf-auto-root is just a recovery that is why it isn't working either.
Click to expand...
Click to collapse
You don't have to take my word for it. But I'm telling you, the bootloader is not locked.
se1000 said:
So what you meant is, "If you downloaded a 1.3GB file and ODIN'ed back to stock just to upgrade and ignored the big bold warning that you couldn't downgrade" OR "If you downloaded a 1.3GB file and ODIN'ed to a new version of android that there was an active thread where it was CLEAR there was no root method"
"Accidentally"
Click to expand...
Click to collapse
LOL some people did it look in the Q&A section people are posting things about recovery not being seandroid enabled because of the bootloader for me I was actually in a boot loop so I just downloaded the latest version from Sammobile
OH and sorry for the last typo I thought you were correcting me
mikeyinid said:
You don't have to take my word for it. But I'm telling you, the bootloader is not locked.
Click to expand...
Click to collapse
I understand it isn't locked but what I mean is for the time being it feels like it is locked considering we can't root or install a custom recovery or downgrade.
ethanscooter said:
LOL some people did it look in the Q&A section people are posting things about recovery not being seandroid enabled because of the bootloader for me I was actually in a boot loop so I just downloaded the latest version from Sammobile
OH and sorry for the last typo I thought you were correcting me
Click to expand...
Click to collapse
Of course people did it, but don't make it seem like you clicked one button and the upgrade went through and now you're stuck. You ACTIVELY went through the upgrade process to force it through.
Plus, you don't need THREE threads on the same subject.
se1000 said:
Of course people did it, but don't make it seem like you clicked one button and the upgrade went through and now you're stuck. You ACTIVELY went through the upgrade process to force it through.
Plus, you don't need THREE threads on the same subject.
Click to expand...
Click to collapse
I didn't make the 3 threads others did I just responded to all 3. Also the whole point of that one choice in the poll is for people who were expecting a normal tmobile update and didn't get what they thought they would usually tmobile let's you downgrade and you can flash a recovery right away but this time it was different and not a ton of people knew it was going to be different maybe I should've worded it better I am sorry.
ethanscooter said:
I didn't make the 3 threads others did I just responded to all 3. Also the whole point of that one choice in the poll is for people who were expecting a normal tmobile update and didn't get what they thought they would usually tmobile let's you downgrade and you can flash a recovery right away but this time it was different and not a ton of people knew it was going to be different maybe I should've worded it better I am sorry.
Click to expand...
Click to collapse
You have 2 threads in the QA section that are on this same subject.
Look, if you want to have a rooted, custom recovery, custom kernel device, don't be the first to update. That's just how things go.
From the Moderator
Redundant Thread ......... So........
..............THREAD CLOSED...........
Hi, thank you very much for reading!
I've been playing around with my new Verizon Edge 6. I had no problems obtaining root, though I'm not an Android expert whatsoever. More of a good at following clear instructions kind of guy, I guess.
Anyway, I haven't been able to flash it much else than the stock rom. Whatever else I try flashing does end up booting, but the phone won't recognize my SIM Card at all no matter what I try (I know I could likely try some more stuff, but I have no idea). When I flash the stock one back in, it behaves flawlessly again.
My guess is that this has something to do with my Current Binary Status in FlashFire being "Unknown" when it should read "Official". And my question is if you know how what the easiest way to get it that way and if you could pretty please point me out where I can get the files I'll need.
Thank you VERY much in advance!
Frannyman said:
Hi, thank you very much for reading!
I've been playing around with my new Verizon Edge 6. I had no problems obtaining root, though I'm not an Android expert whatsoever. More of a good at following clear instructions kind of guy, I guess.
Anyway, I haven't been able to flash it much else than the stock rom. Whatever else I try flashing does end up booting, but the phone won't recognize my SIM Card at all no matter what I try (I know I could likely try some more stuff, but I have no idea). When I flash the stock one back in, it behaves flawlessly again.
My guess is that this has something to do with my Current Binary Status in FlashFire being "Unknown" when it should read "Official". And my question is if you know how what the easiest way to get it that way and if you could pretty please point me out where I can get the files I'll need.
Thank you VERY much in advance!
Click to expand...
Click to collapse
Binary status in Flashfire will read unknown for all Verizon S6/edge variants, due to the bootloader being protected.
I am not sure where your problem comes from exactly. Are you on OC3 firmware, and trying to flash an OE2 rom/package? If not, could you be more specific on what your flashing in FF, and what firmware your on?
Sent from my SM-G925V
My apologies por taking so long to reply. I had no trouble installing the Firmware I wanted right after reading your post. It was in fact trying to flash an OC2 on a OC3 Firmware. I was too embarrassed to admit I had in fact no idea what I was talking about. I humbly recognize now my ignorance, stupidity and stubborness. Thank you very much for your prompt help!
Frannyman said:
My apologies por taking so long to reply. I had no trouble installing the Firmware I wanted right after reading your post. It was in fact trying to flash an OC2 on a OC3 Firmware. I was too embarrassed to admit I had in fact no idea what I was talking about. I humbly recognize now my ignorance, stupidity and stubborness. Thank you very much for your prompt help!
Click to expand...
Click to collapse
No problem with trying to help, and thank you for replying. And don't feel bad or worry about it, we all start somewhere! I certainly am no expert, but try and help where I can.
Sent from my SM-G925V
My S4 i9500 International version is shown as UNKNOWN, too in Flashfire. Why?
Project Fi Nexus 6 rooted here on 5.1.1 LVY48E
I keep getting a notice that a system update has been downloaded (29.1) megs..a tad annoying
Would like to run the update, but can't because of TWRP... Also would like to try 6.0 if it is out, just don't want to lose root, and or have to have my phone reset...
I have Wug's nexus root toolkit too
How do I update to the latest L and or/ M???
Looking for some friendly advice....
Thanks!
Forgot to mention that I have tried flashing the update manually to no avail..
Drumrjoe
You can't update your rooted phone with Ota update, only way is to flash the factory image, download latest Nexus 6 factory image from Google and flash it with the tool kit, if you don't know how to flash a factory image, you should see the main thread
And I believe , given the need for a modified boot when rooting Marshmallow, you lose the OTA anyway, no?
aiiee said:
And I believe , given the need for a modified boot when rooting Marshmallow, you lose the OTA anyway, no?
Click to expand...
Click to collapse
Thanks for the help! Been using the toolkit to try and flash stock + unroot...
It doesn't seem to be working for me... First tried to update to last version of lollipop.. runs the batch updater after downloading the factory image and extracting.. batch window closes after awhile I wait after no change to phone or toolkit and nothing has changed on phone... tried this with marshmallow too... same thing....
At a loss..
drumrjoe said:
Thanks for the help! Been using the toolkit to try and flash stock + unroot...
It doesn't seem to be working for me... First tried to update to last version of lollipop.. runs the batch updater after downloading the factory image and extracting.. batch window closes after awhile I wait after no change to phone or toolkit and nothing has changed on phone... tried this with marshmallow too... same thing....
At a loss..
Click to expand...
Click to collapse
Just do it manually using fastboot. Or since you have TWRP, find a pre-rooted rom.zip you can flash from there.
Lately half the threads are about a toolkit not working. There should be a sticky about this: Don't use toolkits on Nexus phones! Those who don't feel secure enough to enter three lines in a command line/terminal really shouldn't use toolkits either. It gives a feeling of false security for a price of being totally at loss if anything goes wrong. And things do go wrong.
istperson said:
Lately half the threads are about a toolkit not working. There should be a sticky about this: Don't use toolkits on Nexus phones! Those who don't feel secure enough to enter three lines in a command line/terminal really shouldn't use toolkits either. It gives a feeling of false security for a price of being totally at loss if anything goes wrong. And things do go wrong.
Click to expand...
Click to collapse
We try to advise people not to use rootkits or kits of any kind. It does nothing but hinder their efforts if something goes wrong. In the end it is people being lazy and then bricks happen and they have no idea what to do.
zelendel said:
We try to advise people not to use rootkits or kits of any kind. It does nothing but hinder their efforts if something goes wrong. In the end it is people being lazy and then bricks happen and they have no idea what to do.
Click to expand...
Click to collapse
I think many of us here agree with that. To avoid bashing, we have to say "use them if you like, but learn to use fastboot manually first". But all the work we collectively put in to that as a majority is easily undone when just one person replies "use a toolkit". It almost always ends up in a debate that is so long that when it reaches it's conclusion, the OP ended up using a toolkit anyway.,
danarama said:
I think many of us here agree with that. To avoid bashing, we have to say "use them if you like, but learn to use fastboot manually first". But all the work we collectively put in to that as a majority is easily undone when just one person replies "use a toolkit". It almost always ends up in a debate that is so long that when it reaches it's conclusion, the OP ended up using a toolkit anyway.,
Click to expand...
Click to collapse
I know. All we can do is advise and the lazy will still be lazy and then end up with issues. This is why you will see people post about issues and then the min they mention they have used a root kit all replies stop. There are many of us that refuse to help people that have used a root kit. It shows they should not be messing around with their devices if they dont have the time to learn to do things properly.
Duly noted -
But seriously, thanks for the info.. will be figuring this out!
Best all
DJ
Update-
Sincere thanks to all that replied.. Did not know that the toolkit's were a nono-
I did use the command line to manually update and all is well. I am on LVY48I now and rooted.. Next is to reinstall the latest xposed for 5.1.1.
Also, tried finding a stock pre-rooted marshmallow, but didn't really have any luck with that... any pointers or links?
TIA
drumrjoe said:
Update-
Sincere thanks to all that replied.. Did not know that the toolkit's were a nono-
I did use the command line to manually update and all is well. I am on LVY48I now and rooted.. Next is to reinstall the latest xposed for 5.1.1.
Also, tried finding a stock pre-rooted marshmallow, but didn't really have any luck with that... any pointers or links?
TIA
Click to expand...
Click to collapse
Not 100% sure of this but I believe that Marshmallow will not achieve root without some modification. At least I couldn't
I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?
meeniemuffin said:
.... But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot.
Click to expand...
Click to collapse
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493
meeniemuffin said:
I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?
Click to expand...
Click to collapse
-enable "OEM unlocking" in developer options
-unlock bootloader
-flash TWRP using fastboot
-flash a custom kernel
-flash SuperSU 2.52
-KEEP BOOTLOADER UNLOCKED
-KEEP "OEM unlocking" ENABLED
---------- Post added at 09:50 AM ---------- Previous post was at 09:42 AM ----------
NLBeev said:
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493
Click to expand...
Click to collapse
There's nothing mentioned there.
Droidphilev said:
There's nothing mentioned there.
Click to expand...
Click to collapse
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15
NLBeev said:
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15
Click to expand...
Click to collapse
It indeed works but i thought it would bring to a page about the court thing you have mentioned.
Droidphilev said:
It indeed works but i thought it would bring to a page about the court thing you have mentioned.
Click to expand...
Click to collapse
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Aha! i saw you posting this before but never knew that it was a joke
I didn't even need to read all this stuff. First thing I did was get into developer mode and almost instinctual that I turned on OEM unlocking before setting about unlocking the bootloader.
Sent from my Nexus 6 using Tapatalk
Yeah I bought my N6 recently and had a bad first time experience too. I ended up using a toolkit to root and all that, didn't need a custom rom so I kept it stock with TWRP and I'm very happy. Since then, I rooted some of the old devices I had laying around (you can check my signature), so I should be more prepared next time I need to update. My problem is I didn't really understand the commands, what did what and what exactly was required for root. Now that I have had plenty to practice with I'm pretty comfortable with commands and recoveries. Practice makes perfect I guess
NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.
shadowcore said:
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.
Click to expand...
Click to collapse
I hope not. Google's software and design will be the weak point. Google could not give us some simple options like a dark interface, reboot options and dpi settings.
So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?
If bootload is locked, unlock it - This will erase everything backup your device
1. Get modified boot.img for your version, flash it
2. Flash twrp
3. Flash SuperSu 2.52
meeniemuffin said:
So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!
Droidphilev said:
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!
Click to expand...
Click to collapse
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?
meeniemuffin said:
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?
Click to expand...
Click to collapse
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)
Droidphilev said:
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)
Click to expand...
Click to collapse
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.
meeniemuffin said:
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.
Click to expand...
Click to collapse
enjoy!
but DO NOT forget to keep "OEM unlocking" enabled!
(it will save you when you ever get locked out from your google acoount because you became aflashoholic)