Hello all, ran into a SNAFU when trying to root my S7 Edge. Used the tutorial this site provided (https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039) and everything works great all the way up until applying the fixes to prevent the phone from nagging at me about unauthorized changes. I ran thru every step afterwards again to make sure I didn't miss anything, but after it boots, it acts fine for 5 minutes, then the icons up top change and it nags at me. I've tried installing them both at once, and one at a time, nothing is working. I found this guide quite confusing in the way it seemed to jump around, I have yet to do anything under the XPosed application, however nothing there looks relevant and the guide never specified what to do once XPosed *was* installed. Flipped thru a few pages on that tutorial looking for someone who had the same issue, but never saw anything. Any help would be gladly appreciated. It's as if FlashFire does what it needs to do then something undoes those changes.
Nevermind, was able to un-root the device. I've heard Vzw phones are a major pain to root, but I didn't think it'd be this difficult. So much for that..
Related
I'm very sad to admit that I updated from 4.2.2 to 4.3 on my Verizon Galaxy S4 and lost root. I made the terrible assumption that someone would root 4.3 quickly after release, but didn't want to wait to see the updates. So far, the only two solutions are:
1. Root on 4.2.2 and upgrade through this method
2. Use VROOT to root stock 4.3
This thread and this article both make me VERY wary of using VROOT, but this seems to be the only option once you do the OTA update.
Has there been any additional investigation into VROOT? Is it safe to use again, or is it a lost cause?
As of right now, that is the only option that I am aware of. I am no dev, but I have been tinkering with my phones for quite some time. I personally have not encountered a single ill effect from using vroot. There is a script which completely wipes it off your phone and installs the supersu app. Ultimately, it is up to you...I did it and I'd do it again. No ill effects what so ever and it's been a few weeks-nothing wonky to report.
bjoostema said:
As of right now, that is the only option that I am aware of. I am no dev, but I have been tinkering with my phones for quite some time. I personally have not encountered a single ill effect from using vroot. There is a script which completely wipes it off your phone and installs the supersu app. Ultimately, it is up to you...I did it and I'd do it again. No ill effects what so ever and it's been a few weeks-nothing wonky to report.
Click to expand...
Click to collapse
I'm really on the fence... My fear is that I don't want to compromise my Google Account, since my whole life goes through that thing. Did you find that hidden app was installed after using VROOT?
Why is there yet another thread asking the SAME question about rooting MJ7??????
Read the other threads...
http://forum.xda-developers.com/showthread.php?p=47566483
http://forum.xda-developers.com/showthread.php?t=2535416
thethotbot said:
I'm really on the fence... My fear is that I don't want to compromise my Google Account, since my whole life goes through that thing. Did you find that hidden app was installed after using VROOT?
Click to expand...
Click to collapse
Not a single thing was different on my phone. There were even some folks who ran an md5 checksum on all apps and reported that nothing was altered what so ever on any system level. I understand your concern, it took me a couple weeks before finally doing it. I really weighed it out and decided that root was important to me. Also, a good dev on the forums did it with no ill effects. I have faith in him and thus far, nothing has happened. I don't want to push you into it though. I don't even worry about it anymore since the script wipes all traces of the chinese superuser app off the phone.
bjoostema said:
Not a single thing was different on my phone. There were even some folks who ran an md5 checksum on all apps and reported that nothing was altered what so ever on any system level. I understand your concern, it took me a couple weeks before finally doing it. I really weighed it out and decided that root was important to me. Also, a good dev on the forums did it with no ill effects. I have faith in him and thus far, nothing has happened. I don't want to push you into it though. I don't even worry about it anymore since the script wipes all traces of the chinese superuser app off the phone.
Click to expand...
Click to collapse
I did the same thing. My life runs through my google account and I was very weary. I dont see anything strange occurring and ran malware scans on both the PC and phone and didnt find any trojans. I am assuming it is safe with the removal script posted on Rootjunky.com
I'm going for it.
Alright.... I just did it. I used Sandboxie on my computer to temporarily install the Chinese program (just to be safe), and everything on my phone now looks like it's fine. I'll keep a close eye on my accounts, and have enabled Two Step Authorization on my Google Account. I'll still be super bummed out if it ends up VROOT is collecting personal data, but I just couldn't bring myself to wait for root any longer.
I'm curious to know if the developers of vroot have removed the data mining features from the more recent versions?
THANK!YOU OK guys once again and at the same time, in advanced, THANK!YOU
so i am in serious need of some help or someone to just give it to me straight and just put me out of my misery. its been a couple weeks now and ivr put in huge amounts of time trying to search out a solution. Now it's just cruel, if I were and animal they would have put me down weeks ago
I already apologize, I'm going to do my very best to keep this short ( as possible ) and to the point, I have a tendency ( more like debilitating compulsive disease ) of rambling while simultaneously over descriptive, and my effin' phone is broken!!! Give me a break. Ok here we go I promise
This is my first thread / post, believe me I have searched independently, finding a TON on parts but no real conclusion or fix, or of it was there I meed my hand held. So I am, was, running a Verizon galaxy s4, rooted (king root), lollipop 5.1.1
Situation of my phone right now
Ultimately the phone won't boot past the Verizon logo / loading screen, whatever that phase ( if it even is one ) is called. No amount of time has done anything for it. It leaves me with only 3 different options ( attempting to boot normally being the first )#2 I can get info "Odin mode" <holding Vol Down + Power + Home>as its named at the top of the prompt. Where basically I've deduced that it's trying to update or install a custom operating system, from where? I'm not sure, the cloud I reckon, since it warns me not to turn it off and I dont have it plugged in, or anything else provided for it to do much of anything, don't think I even downloaded Odin that I know of. I'm thinking I forgot to mention I do not have access to a computer currently. Quick update: or I just forgot to mention but if you haven't guessed it, I have no immediate access to a computer, and while I'm here I also was not far enough to save a backup. Thanx
continuing. . 3rd and final pathway open to me Recovery Booting<holding Vol Up + Power + Home> I'm sure you guys know the one, where I have tried every option ( more than twice ) to, unnecessary to say I'm realizing, no avail. Had even come to terms with what appeared to be my only hope in sigbt and attempted the wipe / factory boot. And if that worked and changed anything I guess I misunderstood the whole concept of factory wipe. So that's about where I stand currently.
Events leading up to disaster. ..
I was in the overall process of installing xpose of course! I had already performed a successful Root thanks to kingroot, verified with root checker. Had moved onto the slow going process of learning to get TWRP going, here's where it starts to get a little messy... So it goes without saying that I was having.. let's say difficult time with TWRP. I went through one of the pains of the overall process and located my version of framework ( or so I had thought, quite a few people thought actually ( ok so thinking back on it I never really looked at the date on any of the threads so this whole chain of events could have been last year for all I know, and I just started at the beginning and got the full ride and experience everything those in this community running lollipop 5+ had to go through. And when I say chain of events I'm talking about the first rounds of xposed for Samsungd and lollipop. And the nightmare left in its wake. Evident in the step by step UPs and DOWNs left in the threads) so being not 100% correct i had the right framework I put that on hold awaiting a few replies. I then began to attempt twrp once again, this time for a backup . Once again I found myself hating twrp. Defeated I put it all aside for a few days.. upon retire I began reading up on everything all over again. Came across a very helpful ( helpful now, very much not so in the time I'm currently speaking of ) app I bought "Super-Sume". Which sounded like it was going to help out and make things not only easier but get me back on track and going in the right direction again. Well somehow as it was performing it's first stage of removing kingroot and all the extra goodies that they have been accused of adding in as well, the app froze. Not sure I I froze exactly but it had not moved or gained any progress in quite a while, I believe some or most of this to be caused, I recently found out as I was attempting the whole adventure over again on another ( older, less expensive) phone. The one I'm currently on. Just a galaxy lite or something. But come to find out you cannot use the latest , or those after like 4.90 versions of kingroot, or the super-sume won't work, and possibly do what it did to me maybe? ?? But after it froze or whatever it restarted when I shut if off and we find ourselves having come around full circle now.
Once Again ! Thank You I really just want to thank those of you that made it all the way through this never-ending thread. Just being dedicated / motivated enough to get this far, gives me high hopes we will be able to get through this ! The hard parts over, right?
Once Again ! Thank You
Greetings, all of you who know better than to do what I did . . .
I could use some advice from someone who's been around the block with the HDX 8.9 Apollo, 3rd Gen. Kindle. For my part, I'm usually adept enough to avoid problems that should be foreseen, but I was outclassed by whatever was going on here, and I unwittingly dug myself a hole. In a matter of days, I went from having a mostly-stock, rooted FireOS that played nice with Google, to a device with weird quirks, to soft-but-hardening brick. And yes, I've been all over here, reading all kinds of threads. What I usually find is that my situation applies partly, but not fully, to the problems that have already been addressed here.
Back when things were good, the status was:
Rooted with Kingroot, replaced with SU, proper Safestrap installed, XPosed Framework running with the HDX module, seamless integration with Google, disabled OTA according to the instructions provided in the thread on that topic, etc. I had one strange incident where various apps were saying I wasn't rooted, so I repeated the Kingroot/SU process and all was good for several months.
Then suddenly, after the device had sat on my dresser unused for a few days, I picked it up and it started doing some quirky stuff again. Sorry, I can't be more specific than that, because I don't remember--except for one thing: instead of getting a message plainly indicating that I wasn't rooted, anything that sought root access seemed to either hang or crash. I thought it was that same mysterious problem again, so I attempted to do another round of Kingroot/SU, but I kept getting hangs and crashes. At that point, I was still able to reboot into the OS with no difficulty. Until one day, that hung too. Then I was in the same boat as many people here, i.e., "Kindle stuck at boot screen."
I tried all kinds of stuff that's been explained around here. I still had Safestrap for a few boots, but not enough room for a backup. After following some instructions to attempt a fix using the ADB/Fastboot environments, though, Safestrap disappeared. In retrospect, I believe that if I had gone straight to getting the system mounted R/W, I might have saved myself some grief. But maybe not. By the time I got to attempting that, all I got was "permission denied" anyway. Finally, I tried some of the brick recovery/re-root solutions offered here, and I managed to get one of them to wipe my system out, only to be told that it had no permission to write anything in its place.
So here I am: ADB/Fastboot access still intact, but no system, which means no solutions that involve shell commands. (I can still push files, so I'm wondering if I could push a shell in there or something, but I'm definitely out of my depth at this point. My bootloader is locked and I appear to have no root access. (The command "adb root" actually disconnects the device from my computer, so I have to start-server after that, and I don't know if it comes back with root or not . . . but I think it's safe to say, not. I can't seem to do anything that requires special permissions.)
So . . . now that I've exposed myself as a complete turd, is there anyone out there who might have some advice that would lead me in the direction of reviving my Kindle?
I'll keep an eye out as often as I can--got some pre-holiday craziness with my work schedule, so I'll address any responses ASAP.
Thanks!
KT71
KilgoreTrout71 said:
Greetings, all of you who know better than to do what I did . . .
I could use some advice from someone who's been around the block with the HDX 8.9 Apollo, 3rd Gen. Kindle. For my part, I'm usually adept enough to avoid problems that should be foreseen, but I was outclassed by whatever was going on here, and I unwittingly dug myself a hole. In a matter of days, I went from having a mostly-stock, rooted FireOS that played nice with Google, to a device with weird quirks, to soft-but-hardening brick. And yes, I've been all over here, reading all kinds of threads. What I usually find is that my situation applies partly, but not fully, to the problems that have already been addressed here.
Back when things were good, the status was:
Rooted with Kingroot, replaced with SU, proper Safestrap installed, XPosed Framework running with the HDX module, seamless integration with Google, disabled OTA according to the instructions provided in the thread on that topic, etc. I had one strange incident where various apps were saying I wasn't rooted, so I repeated the Kingroot/SU process and all was good for several months.
Then suddenly, after the device had sat on my dresser unused for a few days, I picked it up and it started doing some quirky stuff again. Sorry, I can't be more specific than that, because I don't remember--except for one thing: instead of getting a message plainly indicating that I wasn't rooted, anything that sought root access seemed to either hang or crash. I thought it was that same mysterious problem again, so I attempted to do another round of Kingroot/SU, but I kept getting hangs and crashes. At that point, I was still able to reboot into the OS with no difficulty. Until one day, that hung too. Then I was in the same boat as many people here, i.e., "Kindle stuck at boot screen."
I tried all kinds of stuff that's been explained around here. I still had Safestrap for a few boots, but not enough room for a backup. After following some instructions to attempt a fix using the ADB/Fastboot environments, though, Safestrap disappeared. In retrospect, I believe that if I had gone straight to getting the system mounted R/W, I might have saved myself some grief. But maybe not. By the time I got to attempting that, all I got was "permission denied" anyway. Finally, I tried some of the brick recovery/re-root solutions offered here, and I managed to get one of them to wipe my system out, only to be told that it had no permission to write anything in its place.
So here I am: ADB/Fastboot access still intact, but no system, which means no solutions that involve shell commands. (I can still push files, so I'm wondering if I could push a shell in there or something, but I'm definitely out of my depth at this point. My bootloader is locked and I appear to have no root access. (The command "adb root" actually disconnects the device from my computer, so I have to start-server after that, and I don't know if it comes back with root or not . . . but I think it's safe to say, not. I can't seem to do anything that requires special permissions.)
So . . . now that I've exposed myself as a complete turd, is there anyone out there who might have some advice that would lead me in the direction of reviving my Kindle?
I'll keep an eye out as often as I can--got some pre-holiday craziness with my work schedule, so I'll address any responses ASAP.
Thanks!
KT71
Click to expand...
Click to collapse
Unfortunately, locked bootloader, no root access, missing/invalid permissions, non-operational rom and no recovery leaves few (effectively no) options short of board replacement on this device. Once could find a glimmer of hope using fastboot/factory cables on early generation Amazon devices; they have proven largely ineffective on 3rd gen and above. Wish there was a better answer.
Davey126 said:
Unfortunately, locked bootloader, no root access, missing/invalid permissions, non-operational rom and no recovery leaves few (effectively no) options short of board replacement on this device. Once could find a glimmer of hope using fastboot/factory cables on early generation Amazon devices; they have proven largely ineffective on 3rd gen and above. Wish there was a better answer.
Click to expand...
Click to collapse
Well, truth is better than endless, repeated frustration. Thanks for the answer. But don't get me wrong . . . I'd love a second opinion that proves you wrong somehow. I just won't get my hopes too high.
KT71
KilgoreTrout71 said:
Well, truth is better than endless, repeated frustration. Thanks for the answer. But don't get me wrong . . . I'd love a second opinion that proves you wrong somehow. I just won't get my hopes too high.
Click to expand...
Click to collapse
No worries mate; I welcome other opinions and would love to be proven dead wrong!! No faux pride here...if your device can be resurrected through shared knowledge (and perhaps a bit of luck) everyone wins.
Hey guys,
Sorry if this is posted in the wrong place, if this post needs to be moved just let me know. Anyway, I have a Samsung Galaxy Express 3, it's a neat little phone. I have been an iPhone user almost since the dawn of smart phones. I did not like how I was being "told" to use a phone that I paid for. That being said, I am new to this rooting business. I understand what rooting is suppose to do. The model of the phone is a J-120A. I have found a video online that showed me how to install Kingroot on the phone, and use the software to root the phone. The video is on that exact model. I have checked the build versions on the phone, and made sure that I had the exact version of the software that he was using in the video. The reason I am wanting to root the phone is because it has so much bloatware on it, that installing a hand full of apps eats up the internal storage, I have placed an SD card in the phone to try and move the apps over to, but I have found that I can only move certain apps. My main issue is this, Kingroot installs just fine following the video to a "t." However when it makes it to 70% during the rooting process and fails. I have attempted root access several more times, but it never goes past 70%. In the meantime, I am now getting popups that state "Security Notice, Unauthorized actions have been detected" then the phone wants to restart. Overall the phone is still functioning well, but I know it could be way better if I could just get the factory installed junk off of it from Samsung and ATT. As I said, I am new to this process, so you might have to spoon feed me. Could my issue be with Knox?
Thanks,
littlekatfish2003
littlekatfish2003 said:
Hey guys,
Sorry if this is posted in the wrong place, if this post needs to be moved just let me know. Anyway, I have a Samsung Galaxy Express 3, it's a neat little phone. I have been an iPhone user almost since the dawn of smart phones. I did not like how I was being "told" to use a phone that I paid for. That being said, I am new to this rooting business. I understand what rooting is suppose to do. The model of the phone is a J-120A. I have found a video online that showed me how to install Kingroot on the phone, and use the software to root the phone. The video is on that exact model. I have checked the build versions on the phone, and made sure that I had the exact version of the software that he was using in the video. The reason I am wanting to root the phone is because it has so much bloatware on it, that installing a hand full of apps eats up the internal storage, I have placed an SD card in the phone to try and move the apps over to, but I have found that I can only move certain apps. My main issue is this, Kingroot installs just fine following the video to a "t." However when it makes it to 70% during the rooting process and fails. I have attempted root access several more times, but it never goes past 70%. In the meantime, I am now getting popups that state "Security Notice, Unauthorized actions have been detected" then the phone wants to restart. Overall the phone is still functioning well, but I know it could be way better if I could just get the factory installed junk off of it from Samsung and ATT. As I said, I am new to this process, so you might have to spoon feed me. Could my issue be with Knox?
Thanks,
littlekatfish2003
Click to expand...
Click to collapse
I have resolved my own issue... For anyone out there having the same issue, download the latest version of Kingroot, and make sure that you do not have an antivirus installed and running on the phone. I was able to get the phone rooted. Now on to installing a custom ROM.
I have spent literal hours trying to figure this out. I eventually found out that the most optimal way to do this is with Magisk, but the method that uses an APK requires rooting, since you need to be able to get the boot.img.
So...I need to root my device to be able to root my device? I've never been this frustrated while trying to do something like this before as with my Huawei phone I could do it easily with KingRoot (and it actually worked). On top of all of this, I have no idea what "flashing" is, let alone how to do it, and literally everything I've seen today that seems to properly work requires "flashing" at least one thing.
So has literally no one got an answer for this?