I just spent the past hour looking up roots and solutions for my phone. Today, I completely wiped the phone and I decided to root it. I have little to none rooting experience except rooting my htc inspire which was a breeze. However, I've tried multiple rooting options and neither have seemed to work. "UnlockRootPro"(lol this sucks). Bin4ry and Motochopper. Motochopper seems like the best solution out of all the roots I've picked out. But even if I specifically follow all the directions that I'm given. Motochopper will not work. It just pushes the exploit and then. "rooting phone..." "this may take a few minutes" "failure" "cleaning up" "exploit complete". I didn't notice that at first and I thought to my self "wow that was a fast 2 second root". I opened up my apps and there was superuser! I was happy that this root turned out so well but when I went pulled up terminal to check if my phone was actually rooted. It couldn't "find" su. So I'm sure my phone is rooted since I can't open anything that requires super user. Im on android 4.1.2 and it was the version before the july patch so I'm not sure what is wrong with my rooting process. Can anyone help me?
tl;dr: Samsung Galaxy Express i437 pre july patch 4.1.2 won't root. "failure" Motachopper
Related
Ok, so first off I rooted my previous phone (a Verizon Motorola Droid X2) without any problems ever. I dropped Verizon as my carrier and switched to Straight Talk and I bought the Samsung Galaxy S4, after a few months of having it I decided to look for a way to root it. After a few days of browsing and reading about I found and root option that worked. (http://forum.xda-developers.com/showthread.php?t=2565758) This saferoot worked and i had superuser and was able to do everything i wanted to.
I then went on the Google play store and installed apps that I previously had on my old device for rooted phones. Well I installed chainfire3D and opened it up and clicked install the drives (which then requires a reboot) after a sort time I noticed my phone was stuck on the loading screen and I can't get past it.
I then start looking for a unroot/unbrick option in order to restore my phone to default firmware and factory settings to get it to work again.
Now here is the dilemma...
Like it says in the title, the phone model is SGH-S970G and for the life of me I can't find this model's firmware anywhere.
plz help me asap!!!!
Thank you in advance for any useful information to help point me in the right direction or give me a solution!
Chuggalo said:
Ok, so first off I rooted my previous phone (a Verizon Motorola Droid X2) without any problems ever. I dropped Verizon as my carrier and switched to Straight Talk and I bought the Samsung Galaxy S4, after a few months of having it I decided to look for a way to root it. After a few days of browsing and reading about I found and root option that worked. (http://forum.xda-developers.com/showthread.php?t=2565758) This saferoot worked and i had superuser and was able to do everything i wanted to.
I then went on the Google play store and installed apps that I previously had on my old device for rooted phones. Well I installed chainfire3D and opened it up and clicked install the drives (which then requires a reboot) after a sort time I noticed my phone was stuck on the loading screen and I can't get past it.
I then start looking for a unroot/unbrick option in order to restore my phone to default firmware and factory settings to get it to work again.
Now here is the dilemma...
Like it says in the title, the phone model is SGH-S970G and for the life of me I can't find this model's firmware anywhere.
plz help me asap!!!!
Thank you in advance for any useful information to help point me in the right direction or give me a solution!
Click to expand...
Click to collapse
If you get your phone fixed, I suggest you skip reinstalling Chainfire 3D. It specifically says it's not for Jelly Bean devices.
Hi guys. I've rooted and flashed my s2 countless times and never had any problems, but i've now upgraded to my s4 and every time i've tried to flash a rom on it something has gone wrong. The first time i tried flashing fox hound and my 3G wouldn't work. I then tried flashing my backup and ended up bricking my device. After many long hours I managed to get my phone back to factory setting. A few weeks later I tried again with the google edition Kit Kat Rom, but then the play store wouldn't work. So I tried flashing my back up and yet again bricked my device and spent even longer fixing it. I don't know what I'm doing wrong.. I'm doing everything exactly as I'm told. So I thought I would give it one last try. So I've had to root my phone again, but now after I rooted it I'm not getting Superuser, SU or BusyBox... I'm running Root Checker and it;s not coming off the "Checking for root access" display. As you can probably tell I'm not the best when it comes to technology. If there's someone you can help get me on the right track I would be very grateful.
Oh and also, I've been hearing the words (Verizon and AT&T) etc and I don't know what type of phone i Have. All i know is it is an S4
04/17/2015 Update to this posting; -24A OTA rooted 1st time using Stump after dozens of Brute Force fails on 23A-
Can anyone else confirm Stump Root working for 24A on their own devices?
Original Stump Thread; http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
New OTA software update VK81024A just released this week. From what I've read and VZW's PDF, the only thing that was changed was 4G LTE coverage. In my experience with Verizon, they only release updates for this device to patch root methods and add bloat. This would have been my 3rd update to my GPad (had I accepted) without measurable positive impact. I personally cannot believe that they spent the time and money to fix LTE coverage that, in my experience, had no noticeable issue to begin with.
I would still be waiting for Lollipop on my VZ G3, if I didn't go ahead and root/ROM just last month. With the Lollipop ROM being available to the Korean G3 as early as November of LAST YEAR, my faith in Verizon getting us the updates we want and deserve (I purchased a flagship phone, and a popular tablet) is nonexistent.
Okay, I'm done ranting (for now) about the "Great Satan" that is VZW...the only carrier with good coverage here in my area of NY. Does anyone have any experience with this update? Anyone try rooting it (maybe Stumproot will start working again)? I am tempted to accept it if I could assist the community by doing so. Please tell me your thoughts.
VK810 OTA update from 23A to 24A keeps root
For both of my VK810 tablets on 23A:
Previously rooted 4.4.2 w/ Stump.
SuperSU marked w/ "survival mode". Given my history with the LG G3 keeping root w/o needing "survival mode", I doubt that setting "survival mode" was necessary. However, given the pain I went through to root one of my VK810 tablets right out of the box, I decided to keep it set.
The OTA update (still v4.4.2) to VK810-24A kept root.
The referenced Verizon web page ( http://www.vzw.com/lggpadsupport ) for update info shows very minor changes: http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-gpad-83-4-1-15.pdf
Just got mine this morning. Hadn't been using the tablet for a few days. Would not take OTA. Downloaded the file but kept kicking an error. Ended up hooking it up USB and using the upgrade assistant. Paranoia got the better of me and I "unrooted" first. Brute force stump (climbed to 6800 I think) did the trick just like before. Must say I was disappointed. I had not read what the "upgrade" consisted off but figured since they jumped from 23A to 24A it would be something substantial. I notice some minor cosmetic changes but that's about it. The 4gLTE "Update: or "Upgrade" isn't going to make much difference in my neck of the woods. 3G is about the best you can hope for here in this little town for the time being.
DeanGibson said:
For both of my VK810 tablets on 23A:
Previously rooted 4.4.2 w/ Stump.
SuperSU marked w/ "survival mode". Given my history with the LG G3 keeping root w/o needing "survival mode", I doubt that setting "survival mode" was necessary. However, given the pain I went through to root one of my VK810 tablets right out of the box, I decided to keep it set.
The OTA update (still v4.4.2) to VK810-24A kept root.
The referenced Verizon web page ( http://www.vzw.com/lggpadsupport ) for update info shows very minor changes: http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-gpad-83-4-1-15.pdf
Click to expand...
Click to collapse
Did the same thing as you, OTA installed and still rooted
This did not happen to me, I am using this same tablet and rooted with TWRP installed. When I tried to let the OTA install I got stuck in a boot loop and had to use some terminal commands inside of TWRP to fix the issue. I keep getting bothered with this upgrade notice and I don't know how to stop it. I am pretty sure if I try to let it update I will be stuck in a boot loop again. I don't want the damn update.
Anthony-m said:
This did not happen to me, I am using this same tablet and rooted with TWRP installed. When I tried to let the OTA install I got stuck in a boot loop and had to use some terminal commands inside of TWRP to fix the issue. I keep getting bothered with this upgrade notice and I don't know how to stop it. I am pretty sure if I try to let it update I will be stuck in a boot loop again. I don't want the damn update.
Click to expand...
Click to collapse
On every Android device, if you want to take an OTA, you have to either be 100% stock, or at least have stock recovery, kernel, bootloader, and other partitions, and only have done minor things with the system partition - not have debloated at all.
Sent from my VK810 4G
Anthony-m said:
This did not happen to me, I am using this same tablet and rooted with TWRP installed. When I tried to let the OTA install I got stuck in a boot loop and had to use some terminal commands inside of TWRP to fix the issue. I keep getting bothered with this upgrade notice and I don't know how to stop it. I am pretty sure if I try to let it update I will be stuck in a boot loop again. I don't want the damn update.
Click to expand...
Click to collapse
If the LG Mobile Support Tool factory restores the whole phone (recovery included) then this may be the best option till someone posts the KDZ with rooted 24A. This was my root method and it may work for you.
After searching through forums for weeks looking for viable root options (rollback and Purplerake or Towelroot, ADB scripting, and all others) and running Stump as often as I remembered (probably 30 times on 23A) I finally have it! I didn't see any up to date threads on rooting the VK810 and all the old threads had too many broken links to actually perform the steps.
Here's how it went down;
1.) Installed the latest LG USB drivers from LG's site ( http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00520120427 ).
2.) Download LG Mobile support tool ( https://docs.google.com/file/d/0B687...p2NlhhalU/edit ).
3.) Run the LG Mobile Support Tool program.
4.) Switched tablet USB mode to "Internet Connection / Ethernet" and after a few moments the LG Tool recognized my VK810.
5.) In LG Tool, click on "Options -> Upgrade Recovery" on the upright corner.
6.) It should start downloading stock firmware right away, if it says "Downloading" but there is no file size or progress, then you need to disable firewall.
7.) After the download, it will start "Upgrading".
8.) When the tablet rebooted I was on the latest VZW VK81024A which shocked me because I thought it was going to put the factory image (JB 4.2), but not to give up hope, I retried Stump...1st time rooted the thing!
9.) Followed Stump Root's directions (Reboot after app tells you to, Install SuperSU APK from market, Uninstall StumpRoot) and poof!
10.) Enjoy rooted 24A KitKat
It is very possible that 24A broke the fix VZW had for 23A (even though many people had success with 23A) and one need only take 24A OTA to Stumproot if they were not able to prior, but this is how my experience went down.
MANY thanks to @roirraW "edor" ehT, @jcase, & @jim380 for producing the threads and software that led to my rooting.
So hi all, this is my first post on XDA. Finding information these days you think would be easy but alas it's been one big waiting game.
A little background, I've wanted for the longest time to link my ps3 controller (WIRELESSLY) to my s4, but Verizon forced an upgrade to Lollipop, I hate it and it's been a nightmare for me.
I learned I would have to be root to get the controller to work wirelessly, but I wanted root access for other reasons well such as bloatware removal and interface customization.
So I've been skulking around forums like a hawk, finally I found king root but it wouldn't root my phone and I wasn't about to install it on my PC, too risky... so I waited and waited and waited.
several months pass...
New update for King root will now work to root my phone, and I was able to replace it with super-sume, root checker showed I was rooted and Bazinga! Off I was at last. I removed a couple pieces of bloatware but before I continued I thought it might be wise to reboot the phone while rooted to make sure everything is kosher.
Phone comes back up, no problems. but now ROOT ACCESS IS GONE. I read up and discovered that in some cases the boot-loader will unroot the phone everytime you reboot. I don't want to have to re-root my phone over and over again, that's a pain in the arse.
I read up on some laws felt confident if I called Verizon they wouldn't be able to give me a hard-time, I just wanted to know how to disable the boot-loader locking things up.
I ended up with tier two, who they stated all their 4G devices are unlocked... when I got into the nitty gritty regarding the bootloader the techs I spoke with were lost.
I just want to be able to root my phone and KEEP root. I wish I had Kit-Kat because this wouldn't even be an issue but I don't. Can anyone help? I'm so sick of this crap.
HALP PLZ :crying: :crying:
Another small caveat I should mention, when I reboot my phone, it has an unlocked padlock but root checker states that root access in no longer properly installed and I can't do anything that I'd be able to do rooted either. Before the reboot, root was showing as properly installed.
Wrong forum, there is a Verizon subsection.
Verizon phones are all unlocked...... meaning you can insert whatever SIM card you feel like putting into it.
The bootloader, however, is locked. It will remain locked and it's more than likely never going to be unlocked. Write access is dependent on an unlocked bootloader. The security checks are set up as such that if you attempt to alter the system files, they'll just all return to normal on a reboot.
You can use a temp root method on Android 4.4, but as you figured out.... when you reboot, Bye Bye Root!
There is not, nor has there been, nor will there be a bootloader unlock unless somebody cracks Samsung's encryption keys. You have a better chance of winning the Powerball jackpot than doing that.
Use CF root if you wanna perm and thing solved..
Ok,so this is my first thread,don't expect it to be perfect! Let's get straight to the point. I have a Samsung Galaxy J5 (Thank you,Captain Obvious)-J500FN,on the official Android 6.0.1 firmware! I tried to root it,using One Click Root methods! (A good thing to know,I enabled OEM Unlock,just in case). As expected,none worked... So,I fired up Odin to resolve my issue. However,I couldn't find ANY root files for 6.0.1. I ended up going back to 5.1 just to root it,and my root was succesful. Kind of...
After a while,my phone went nuts. My stock apps(Contact Storage,Weather,Hangouts etc.) were almost all the times "Not Responding",meaning every 5seconds I would get a message "App is not responding",even if I wasn't using them.
Conclusion: What other ways are there to root it without messing it up?
Thank you for reading this! :cyclops: