I am creating this thread because I have not found another ZACT rooting/flashing thread yet and I am hopping that a dev will pop in and start working on this, or help walk me through what I can do to get the ball rolling. Check out my first thread, The future of phones is coming
I received 2 phones a few weeks ago now. I wasn't thinking and just jumped the gun and updated to 4.3 on one of them (the other is my fiances and have instructed her NOT to do the update). I am unable to cf-auto-root with the sprint s3 method, so no root. I read if I get the recovery.img from the phone I can post in on Chainfire's cf-auto-root page and he can make a cf-auto-root for the zact s3. I can not get a recovery.img to send in because it is my understanding that to adb pull the recovery I need root. cant get root because I dont have a recovery.img?
I spoke with zact team members a few times. I told them I was having issues with 4.3 and wanted to go back to 4.2.2. A few people were helpful at first. Unfortunately, they are so small, I seem to keep running into the same people, and then they stop trying to help. What I have learned is, they "have confirmed with there Team, that if you process the software downgrade, the Zact software will not work on your phone. This is based upon how our software interfaces with the firmware." SO, that being said we would need to find out what software they have installed and have it integrated into any roms made. Does that sound right?
They also WILL NOT share the MSL. Which is another reason I want root. I still plan on cloning the phone as a backup if I have issues with flashing. but without the msl, i cant change the qualcomm settings to connect to dfs/cdma to back clone it.
I am not a developer, I could use some direction. I feel ZACT will start growing once people realize how much you can save compared to a sprint plan. I have noticed that I get better service then a lot of the people I work with. I am on prl version 24017, which I have not seen before either.
devildogwillbur said:
I am creating this thread because I have not found another ZACT rooting/flashing thread yet and I am hopping that a dev will pop in and start working on this, or help walk me through what I can do to get the ball rolling. Check out my first thread, The future of phones is coming
I received 2 phones a few weeks ago now. I wasn't thinking and just jumped the gun and updated to 4.3 on one of them (the other is my fiances and have instructed her NOT to do the update). I am unable to cf-auto-root with the sprint s3 method, so no root. I read if I get the recovery.img from the phone I can post in on Chainfire's cf-auto-root page and he can make a cf-auto-root for the zact s3. I can not get a recovery.img to send in because it is my understanding that to adb pull the recovery I need root. cant get root because I dont have a recovery.img?
I spoke with zact team members a few times. I told them I was having issues with 4.3 and wanted to go back to 4.2.2. A few people were helpful at first. Unfortunately, they are so small, I seem to keep running into the same people, and then they stop trying to help. What I have learned is, they "have confirmed with there Team, that if you process the software downgrade, the Zact software will not work on your phone. This is based upon how our software interfaces with the firmware." SO, that being said we would need to find out what software they have installed and have it integrated into any roms made. Does that sound right?
They also WILL NOT share the MSL. Which is another reason I want root. I still plan on cloning the phone as a backup if I have issues with flashing. but without the msl, i cant change the qualcomm settings to connect to dfs/cdma to back clone it.
I am not a developer, I could use some direction. I feel ZACT will start growing once people realize how much you can save compared to a sprint plan. I have noticed that I get better service then a lot of the people I work with. I am on prl version 24017, which I have not seen before either.
Click to expand...
Click to collapse
WARNING!! If you process that downgrade, you will trip KNOX security, then your phone will be bricked. Also, ESN cloning is illegal to talk about on XDA.
sent from my GS3
I will trip knox security? What exactly does Knox do, and what do you mean by that? I though Knox just makes it read 0x1 on the odin screen if you flash now? If thats what you mean, I already did that by flashing cf-auto-root. Its my understanding that the boot loader is the issue when downgrading. but on this site, they say that only at&t users should not try it, and technically this is a sprint phone I believe. Just with added software.
If I am wrong please let me know.
Also, I think you mean that it is not acceptable, not illegal. Illegal would imply I could get arrested for commenting about phone cloning on this site. And although cloning your personal phone for your own uses is not illegal, I will not mention it again on these forums. Thanks for the warnings.
sent from my GS3
Also, I guess I am not necessarily trying to downgrade, just trying to find out what needs to be done so that I can flash or ANYTHING to get away for 4.3 issues. Since the upgrade, my fiance sent me an mms and it has popped up in my messages 5 times, so it looks like she keeps sending it, but I am unable to open it because it wont download.
The more important issue is root. I want to be able to use my root apps to backup, re install my old backups from my last s3, and attempt to get my msl to try and fix the mms issue.
sent from my GS3
Today has been a productive day so far... using Skunk Ape1's root method "[Tutorial] Rooting the Sprint GalaxyS3 the Easy Way" I was able to get twrp recovery installed. (I wasn't able to do this before because prior the only method i knew was to go to goo.manager and that didn't recognize my device) SO, with twrp installed, i flashed the zip file from Skunk Ape1's root method. Following the instructions to the T everything seemed to work fine. After reboot, I had a knox message popped up, saying "SECURITY NOTICE: Unauthorized access to a secured area has..." I relive that root has been installed but knox is keeping locked up still. I am going to look for this mysterious "Knox remover script" that you will see in the first post on that page, then I will attempt root again.
I have officially given up on root currently. I have tried every root method I can find, my flash counter is somewhere around 13. I was able to use the knox removal script from here If anyone has suggestions for root, I am open to ideas. Thanks.
Finally did it
So, today i was just realizing the lack of space i had on my phone from downloading stuff and photos so i wanted to clean it up. I moved all the important stuff off, and though it would be a good time to factory reset and just have a clean new phone to start over again. ( I missed flashing and this was the closest thing I had) So, during the process of factory resting i wanted to clean everything so i click data, cach, internal external.. system.. yeah well bad idea. my phone rebooted and go stuck on the boot. So i restarted in recovery and reset again and this time is warned me that there was no OS installed... F*ck... Zact customer service wont give me the "custom software" that they installed so im screwed.
After hours of thinking and trying to do stupid odd ball things that i knew wouldnt work. I downloaded a sprint stock 4.3 tar file and odined to my phone. started up fine. works great. so... what zact said about flashing roms bricking this phone was BS.. the only custom thing i have seen was in the zact mobile app that came installed had some extra features used to send usage info and reboot stuff for zact troubleshooting. so with stock sprint rom, and zact mobile app im back to my phone working. AND with that, im going to move on to the rooting, and flashing of this piece of crap. Ill be back with more details later.
I have installed CyanogenMod with full root!!!
well first off, i had the CMinstaller set up but it did not recognize my device so after a while i decided to attempt to cf_auto_root, which seemed to work but failed root checker. I wanted to try another method. I had CMinstaller still up* I was attempting THIS method to root. I was using philz_touch_6.15.4-d2spr.tar.md5 that I flashed using Odin 3.07 (that I have had for a long time on my pc. so google that one)https://www.google.com/search?q=odin+3.07&oq=odin+3.07&aqs=chrome..69i57.3464j0j1&sourceid=chrome&ie=UTF-8 After i installed Philz touch, i noticed CMinstaller noticed my phone and started downloading system files. I continued what i was doing with the root method and installed DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0 and UPDATE-SuperSU-v1.93 just as CMinstaller finished its download, so i said what the hey, and clicked install. next thing i knew i was running cyanogenmod with full root!!! please someone else verify this and let me know if you get it going too.
Deleted
Stock 4.3 with root
so yeah, just for to check i flashed back to stock 4.3 (not sure who uploaded it but it works) It does have knox so be warned. I then followed the root method in my previous post and it worked fine. i have stock with root. If someone can try it without using that tar file, let me know. Cant really go back once you do it so i cant try the root method with the zact "custom software" myself. Let me know what you find out. Hope this helps someone.
Thanks
Thanks for posting your struggles and successes. With Zact shutting down I was curious about what I could do with my kids' S3s if I don't like the Sprint plan that they are rolling us into. I may be trying this in a couple weeks...
Zact to Ting
Barnsie said:
Thanks for posting your struggles and successes. With Zact shutting down I was curious about what I could do with my kids' S3s if I don't like the Sprint plan that they are rolling us into. I may be trying this in a couple weeks...
Click to expand...
Click to collapse
What I would do and have done for my fiance and myself, get on Zact.com live chat ask them to Deactivate your phones. and give them the DEC on the back of the phones. It takes about one min for it to complete per phone. Then go on over to Ting.com and start up a new account with them using your old zact phone. Ting also lists the MSL that i struggled so much trying to get. I would recommend flashing a stock rooted rom debloated, to get all that ZACT crap off your phones. and start out fresh.
Related
What's the best way to get rooted. I've tried te avalauncher way, they tell me I have to be rooted to use it. I've tried the simple root OTA, but when it's suppose to take you to factory restore, my phone goes to a backup/restore screen, so it fails cause I can't restore it. Please give me assistance.
I am running 2.2 from a manual install. No root.
You have to wait until the guys here find a way for p eople to root once they have 2.2 . That could take anywhere from a few days to a few weeks
Most likely you are NOT going to be able to root since you ran the OTA update for 2.2....
That is why you should read what you are flashing and know the consequences prior to doing so. Every thread that contained the download for the 2.2 leak said that it will make you lose root and the ability ( for now ) to gain root status.
You need to wait until one of the geniuses figure out a way to do it.
Sorry about your luck.
The best way is toast method...
Good luck!
Sent from my PC36100 using XDA App
UND3RTAK3R said:
The best way is toast method...you can email me if you have any problems [email protected]
Good luck!
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Not gonna work since he used the 2.2 update man.
EVOme said:
What's the best way to get rooted. I've tried te avalauncher way, they tell me I have to be rooted to use it. I've tried the simple root OTA, but when it's suppose to take you to factory restore, my phone goes to a backup/restore screen, so it fails cause I can't restore it. Please give me assistance.
I am running 2.2 from a manual install. No root.
Click to expand...
Click to collapse
1. wrong forum, should be in Q&A
2. if you did the manual update from Sprint, you will have to wait until the devs here create a root method for stock 2.2 is developed. Any existing root method will not work at all.
EVOme said:
What's the best way to get rooted. I've tried te avalauncher way, they tell me I have to be rooted to use it. I've tried the simple root OTA, but when it's suppose to take you to factory restore, my phone goes to a backup/restore screen, so it fails cause I can't restore it. Please give me assistance.
I am running 2.2 from a manual install. No root.
Click to expand...
Click to collapse
You installed the plain OTA update? The one that says "not rooted yet" on the thread title?
For each new update, HTC tries to protect its software from being rooted. The last update required users to exploit a Flash Lite vulnerability and took a while. You will probably have to wait a long time before you can root this, since it doesn't have Flash Lite.
For future reference, root first THEN update to a rooted rom released by our devs. You can't just install Ava's rom on top of stock 2.2, it prevents you from doing so.
I'm sorry but HOW MANY posts were there saying if you want to keep root, DO NOT INSTALL THE UPDATE?? Ugh...
And yes I know this isn't constructive but sometimes people just need a slap on the back if the head.
Sent from my PC36100 using XDA App
I'm in the same boat. After trying hard to resist the urge, I gave in and installed the leak. After finding the rooted version, I tried to use the 1.47 RUU to go back but it error-ed out. I'm so bummed I can't go back. Oh well; I knew the risk I was taking though so I guess I have to live with it...
Hours my my day wasted....HOURS!!!
Where's my AR-15
Wow, just wow.
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Here we go again
Sent from my PC36100 using XDA App
bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
By digging thru it and finding an exploit.
Which will most likely happen for the 2.2 update as well, just not as of yet.
bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
With a ROM, you can run through the zip file and essentially take out the parts that would remove root and modify as you see fit to put on an already rooted device -- the device isn't running all the security checks on the ROM, since it's already been rooted to remove those. Much easier, almost trivial.
If you have a non-rooted device, though, you have to find a way to get the device, not the ROM, rooted. The device isn't going to take an unofficial ROM. Big difference, since you have to exploit something already on the device somehow. With the last OTA update, it was Flash Lite that could be exploited for root access to the device. With this one, no one has found a method to root the device once the OTA has been applied (and probably won't really try that hard until the official version is released, in case it closes any exploits that are in the version floating around now).
xeno314 said:
With a ROM, you can run through the zip file and essentially take out the parts that would remove root and modify as you see fit to put on an already rooted device -- the device isn't running all the security checks on the ROM, since it's already been rooted to remove those. Much easier, almost trivial.
If you have a non-rooted device, though, you have to find a way to get the device, not the ROM, rooted. The device isn't going to take an unofficial ROM. Big difference, since you have to exploit something already on the device somehow. With the last OTA update, it was Flash Lite that could be exploited for root access to the device. With this one, no one has found a method to root the device once the OTA has been applied (and probably won't really try that hard until the official version is released, in case it closes any exploits that are in the version floating around now).
Click to expand...
Click to collapse
Beat me to it and said it better.
bludragon742 said:
I'm in the same boat. After trying hard to resist the urge, I gave in and installed the leak. After finding the rooted version, I tried to use the 1.47 RUU to go back but it error-ed out. I'm so bummed I can't go back. Oh well; I knew the risk I was taking though so I guess I have to live with it...
Click to expand...
Click to collapse
I have no idea how it was "hard to resist" when AVA's rooted version showed up at 5:30pm and netarchy's showed up around 9pm. They showed up before any official sprint OTA. Lets also not forget the hundreds of posts warning people that this would happen.
bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
The "rooting method" allows you to get into restricted areas of the phone to install stuff. The act of rooting is breaking into the phone itself, not into the rom. The rom itself is fully accessable and can be hacked up, its just getting it onto the phone is the hard part.
Essentially your phone, stock, is a box that's locked from the inside. For older versions people figured out how to unlock it, so that you can put any hacked up rom onto it. The new OTA, no one knows how to get in yet.
Don't know if that makes sense. It's pretty easy to understand if you understand OS permissions.
EDIT: what the other guy said.
bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
Because someone takes the CONTENT of the update, and applies it piece-by-piece to an already rooted image, ignoring the bits that replace HBOOT and etc.
Mad06STi said:
I have no idea how it was "hard to resist" when AVA's rooted version showed up at 5:30pm and netarchy's showed up around 9pm. .
Click to expand...
Click to collapse
I'll tell you why. The thread gets to 200 pages. There are people saying it works, sucks, bricks, awesome, hate it, stay away, success, etc. After reading 40 pages of it you have no idea up from down. Speaking from someone that is not familiar with Android rooting. It's frustrating. Then you go to one of the other 50 threads and it's all the same.
I never saw anywhere that if I installed the leak i'd be screwed. I'm fine with that though. I have 2.2 and can wait. Just annoyed i've spent hours of my day on this.
This thread was a funny read.
Sent from my PC36100 using XDA App
I'll get this out of the way first, I'm pretty new to rooting and flashing ROMs. The only thing I've ever rooted before was a free Kindle Fire I got from Amazon, and got some version of Android on it a looong time ago. Now I want to get LiquidSmooth on my Galaxy S3 i747. I'm completely willing to follow all noob guides by myself namely http://forum.xda-developers.com/showthread.php?t=1802160]this one.
HOWEVER, since this is a phone from AT&T with a data plan, texting, and calling, and not some free Kindle with none of that, I'm extremely paranoid to do anything risking losing all these features. There's really no clear indication anywhere that this will or won't happen, since I assume this is either just extremely common knowledge, and most trouble shooting is about screwing up in general or bricking.
Rooting and flashing doesn't affect any if those things.
Think of it as a new operating system for your computer. New look, new feel same basic functions.
Sent from my SGH-I747M using XDA Free mobile app
EGSuda said:
I'll get this out of the way first, I'm pretty new to rooting and flashing ROMs. The only thing I've ever rooted before was a free Kindle Fire I got from Amazon, and got some version of Android on it a looong time ago. Now I want to get LiquidSmooth on my Galaxy S3 i747. I'm completely willing to follow all noob guides by myself namely http://forum.xda-developers.com/showthread.php?t=1802160]this one.
HOWEVER, since this is a phone from AT&T with a data plan, texting, and calling, and not some free Kindle with none of that, I'm extremely paranoid to do anything risking losing all these features. There's really no clear indication anywhere that this will or won't happen, since I assume this is either just extremely common knowledge, and most trouble shooting is about screwing up in general or bricking.
Click to expand...
Click to collapse
I have the same phone and there are a few things that are good to know that will help you and possibly keep you from making a bad choice.
Have you accepted the 4.3 OTA update from AT&T on the unit or...? If you have, then you have upgraded to a specific bootloader/modem and can no longer downgrade those items without causing problems.
audit13 said:
If you took the 4.3 OTA AT&T ROM update, your phone has the 4.3 mjb bootloader.
To confirm which bootloader is on your phone, boot into download mode and let us know what it says on your screen.
Click to expand...
Click to collapse
If you did not take the update then you dont have these new items and your options are more open i guess.
First, your going to need to root your phone, without tripping the flash counter. There are lots of guides on how to do this, and it's pretty simple.
Secondly you will need to install a custom recovery such as ClockWorkMod or TWRP. I used CWM on my i747 and installed it using "ROM Manager" from the Play Store. It was amazingly simple and did the entire process for me.
Third you will need to choose the ROM you would like to try. There are a few different kinds, so happy hunting. I chose S3Rx and I love it. It's packed full of goodies and it seems that the Dev seems pretty good at answering any posts on his thread in this forum about the ROM.
Before you do any of that, you should verify what version your are running right now so you know what bootloader/modem you have, then go from there.
I just got back into this stuff myself and I love this phone. Good luck.
38589556 507
Ed Murray said:
I have the same phone and there are a few things that are good to know that will help you and possibly keep you from making a bad choice.
Have you accepted the 4.3 OTA update from AT&T on the unit or...? If you have, then you have upgraded to a specific bootloader/modem and can no longer downgrade those items without causing problems.
If you did not take the update then you dont have these new items and your options are more open i guess.
First, your going to need to root your phone, without tripping the flash counter. There are lots of guides on how to do this, and it's pretty simple.
Secondly you will need to install a custom recovery such as ClockWorkMod or TWRP. I used CWM on my i747 and installed it using "ROM Manager" from the Play Store. It was amazingly simple and did the entire process for me.
Third you will need to choose the ROM you would like to try. There are a few different kinds, so happy hunting. I chose S3Rx and I love it. It's packed full of goodies and it seems that the Dev seems pretty good at answering any posts on his thread in this forum about the ROM.
Before you do any of that, you should verify what version your are running right now so you know what bootloader/modem you have, then go from there.
I just got back into this stuff myself and I love this phone. Good luck.
Click to expand...
Click to collapse
I had already flashed my phone after getting the verification from the last user. I was running 4.3, and am now running LiquidSmooth 3.0 Kitkat 4.4.2 now, with pretty much no problems at all. But thank you for your help.
I have a 16gb S3 which has been flashed to 4.3 (several times). My sons S3 is a 32GB but he broke the screen and bought a different phone. I thought I would like to swap out my motherboard and put his in my phone (both for the memory, and because I've set my Warranty Bit and I'm not entirely happy with 4.3's performance and his still has 4.1.2 so I can get a free reset on that). Both phones are T999's on the same account. His was bought off ebay but he was able to activate it so my assumption is that the IMEI is clean. Before I do this my questions are:
Will my IMEI change (is the IMEI locked to the motherboard)? If it changes, that's fine, as long as I can just pop my SIM in and be up and running.
Can I just do that swap, put my SIM in and go, or is there anything else I need to do with the phone after the swap? I work in a micro repair shop so I'm fine with doing all the hardware related work, just want to verify if I need to do anything extra after the swap.
The imei, and pretty much everything will be on the motherboard. Just swap it out and insert your SIM. Should be all you need to do.
Sent from my SGH-T999 using Tapatalk
OK, got the swap done, and a hard factory reset on 4.1.2 without issue.
So now I was planning on leaving it at that, but after reading through the [ROOT] TowelRoot - 4.3 & 4.4.2 thread today I'm thinking I'd like to try that. My goal is:
1. Update to latest 4.3 via OTA
2. Use the Towelroot tool to root and de-knox it
3. NOT set the warranty bit in the process (hopefully)
4. Create a debrick.img for T999 with clean NC2 (if it's still needed)
1,2, and 4 I'm good. Just curios if I OTA update 4.1.2 and follow all the steps for using towelroot, is there anything more I should be cautious or aware of about the warranty bit. My hope is that I don't do something stupid that will set it on this motherboard. I'd love to have 4.3 rooted but not set the bit.
I'm not concerned so much about the "modified" system or other counter(s)... triangle away was still working to clear those on my root66 NC2 load.
I think flashing the firmware via Odin is a better option. Too many people often seem to have trouble with OTA's. Thst and I personally just feel clean flashing the build you want is better than patching them up from a previous version.
In the end its what you are more comfortable with though. Just offering an alternative.
I'm comfortable doing an Odin flash but I thought that would set the warranty bit. I would've used root66, so am I off by thinking that? At any rate, I OTA'ed last night, ran towelroot and that worked, but I had some issues with the Supersu portion. It updated binaries, and then when it ask about disabling knox, I got a message saying Supersu install failed (or something similar). When I root checked it, it said it was rooted, and supersu was working, but all the knox related files were still on my phone. So I rebooted and ran supersu a second time and it just came up as it would if it were fully installed and working.
I never did figure out why, I even completely cleaned up/removed supersu from it's settings menu, re-installed it and tried again. At that point, it updated binaries without a hitch but didn't give me any prompt to do anything with knox. So does supersu somehow just disable knox, but leave all the files intact? I manually went in and deleted all the knox files myself at any rate and it didn't appear to screw anything up so far.
I also wondered if supersu issues had anything to do with the fact that when I installed it, I had not yet set Selinux to permissive.
Anyway, all that probably belongs in the threads for towelroot, so I got a little off topic .
Root66 apparently trips the warranty bit for some, but not all people. It did not trip mine. Since you've already done the OTA it doesn't really matter, but what I would've suggested next would've been to flash stock firmware via Odin, then Towelroot.
As for SuperSU, everyone has to reboot (or kill the process) before it'll properly disable Knox. And yes, that's all it does is disable it. Didn't have anything to do with seLinux.
OK, cool. So I guess it worked exactly as intended. Thanks for all the good info.
Interesting about the warranty bit.
Good afternoon guys,
I have a few set of questions and I will be glad if someone is able to kindly help me out. Please keep in mind that I am not an android expert as far as rooting, custom roms, etc... So I ask for patience from you guys!
Now... into the questions. I got my LG G2 2 weeks ago from Sprint. Great solid phone with killer specs. I previously had a Galaxy Epic 4G Touch. I was looking into rooting my LG G2 phone. However, somewhere in an article online, I read that, if I were to root my LG, I would no longer receive OTA software updates... Like an updated android version for example.. Is that true? I dont care about loosing root after updating. I just dont want to root my phone, receive an OTA update and then mess up my phone.. So thats my first question.
Next... I've done quite a few research online on how to root the G2 from sprint. What i am currently having issues with is finding the drivers. I know I must install them prior to attempting anything else. I read that I could use the Tmobile version drivers even though I am on sprint. But no luck finding those either. Could someone provide me with a link to download the drivers? Thanks! (Windows 8)
And last... I've seen many methods on rooting this device, that at the end, was confused on which one to use. Soo.. could someone share a link of a working method to root the LG G2 from Sprint (Android 4.4.2)
Thank you guys and I will be very grateful for any help. :good:
Any change of the android operating system with ota can fail. They are looking it seems note for any excuse to break the phone if you do anything. Best idea is to make sure you can unroot, then take ota.
Best way to root is go with ioroot25. I believe it is in lg g2 general.
Sent from my Nexus 7 using Tapatalk
Thank you for your reply.
How would I unroot my G2? Would I use ioroot25? Or is there some type of app that I would have to download? Correct me if I'm wrong, but... Is it possible to unroot with SuperSU ones is installed on your phone after a sucessful root?
Thanks.! :good:
SuperSU can unroot (and temp unroot, though anybodies guess if it'll survive an OTA). There's several other temp unrooters, I often use Hide My Root (try to get some perspective on what the device *actually* works like). Otherwise, removing su, supersu, busybox (if installed) and whatever else until /system looks unmodified works. If there's custom recovery, you (as well as I) probably need to flash that back to stock as well. Or.. quite likely there will be a version around to flash without taking the actual OTA update if there isn't already (haven't checked the other thread). That'll likely be the easiest rather than bother with redoing the work to fix it up again.
Nothing is risk-free of course, but unrooted and flashed back to stock recovery it should be at least fairly unlikely to hurt anything. Of course that's often the stuff I mess up.
Robles23 said:
Good afternoon guys,
I have a few set of questions and I will be glad if someone is able to kindly help me out. Please keep in mind that I am not an android expert as far as rooting, custom roms, etc... So I ask for patience from you guys!
Now... into the questions. I got my LG G2 2 weeks ago from Sprint. Great solid phone with killer specs. I previously had a Galaxy Epic 4G Touch. I was looking into rooting my LG G2 phone. However, somewhere in an article online, I read that, if I were to root my LG, I would no longer receive OTA software updates... Like an updated android version for example.. Is that true? I dont care about loosing root after updating. I just dont want to root my phone, receive an OTA update and then mess up my phone.. So thats my first question.
Next... I've done quite a few research online on how to root the G2 from sprint. What i am currently having issues with is finding the drivers. I know I must install them prior to attempting anything else. I read that I could use the Tmobile version drivers even though I am on sprint. But no luck finding those either. Could someone provide me with a link to download the drivers? Thanks! (Windows 8)
And last... I've seen many methods on rooting this device, that at the end, was confused on which one to use. Soo.. could someone share a link of a working method to root the LG G2 from Sprint (Android 4.4.2)
Thank you guys and I will be very grateful for any help. :good:
Click to expand...
Click to collapse
Well I took a OTA update this morning not thinking.....rooted but stock rom and now my phone wont come out of recovery.....Trying to fix this now...ugg! Not fun
This is an open discussion about the Straight Talk Galaxy S6. Here I want to discuss about possible root access along with a possibility to downgrade. Looking for any volunteers to help me with this phone.
I own a red magic 3, a G6, and an old S6 with straight talk firmware. I usually use my G6 and S6 to play around with for development purposes.
So awhile back, I managed to root my galaxy S6 straight talk with a third-party rootkit. Not long after that I wanted to upgrade this thing to marshmallow. I managed to succeed in doing it, only to be left with a useless phone.
Upon my research, you can flash an SM-S907VL firmware which appears to be a TracFone firmware for the S6. However, the 907VL appears to not support straight talk users. I attempted to downgrade back to the S906L but the strict SBoot prevents me from going back.
A half year later, I'm still messing with this phone. I want to see about finding a way to gain root access or look for any loop holes (possible exploits) that we could do with this phone. I managed to find a way to root the SM-S907VL. Here's how:
I first did some deep digging on the internet and found combination firmwares for this particular model. Combination ROMs are (what I believe are test ROMs for phones). I managed to flash a combination firmware to it. After that I rooted it with kingroot, uninstalled kingroot SU and switched to SuperSU. Then I installed Flashfire and I tried to flash the SM-S906L but no luck.
However, upon even FURTHER searching, I managed to flash the SM-S906L by ONLY flashing the system.img by extracting it from the md5 and adding it to a tar archive.
Well here is where things get complicated, since I only flashed the system, the kernel is running on a later kernel security patch. Which means rooting it with Kingroot fails. Also, the CVC and modem is still running on the SM-S907VL so even if you put a straight talk sim card into it, it won't work. Bummer
I'm wanting to see how far we can go into this phone and hopefully find a way to somehow get it unlocked somehow.
I'm all ears for y'all!
EDIT: Crap, posted in the wrong category. I should have posted in the general forum.