Related
Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
vettejock99 said:
Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
Try the alternative method in my guide with rage instead of visionary and see if that helps. One thing is does is reinstall su and busybox. Also, make sure that you have deleted the PD15IMG.zip from your sdcard so that this doesn't happen again.
Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!
just either use the stock rom in the downgrading post, or flash one of the new ones i.e. icedglacier or Gorillas's. iceglaciers seems to be pretty functional right now gorillas is awesome just has a few kinks he's working on
vettejock99 said:
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
try this (you should be s-off) and assuming you have busybox already installed.
run rage to get su in your terminal then run the following command in the terminal
busybox mount -o remount,rw /system
busybox chown 0 /system/bin/su
busybox chmod 4755 /system/su
install the superuser.apk if it's not already installed
make sure everything is working by opening a adb shell and typing "su" to verify.
use your phone normally and try rebooting after a few hours. hopefully the fs cache flushed and root is fixed permanently.
mrpanic7 said:
Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!
Click to expand...
Click to collapse
Okay, first things first - guess I have to try to see if I can even get S-OFF again or if I've completely screwed myself.
Going to try the alt root method, but I think I have been and it wasn't working. So unless me being tired at 1am was the cause, I may need some more help. Thanks.
Okay, followed the s-off guide, and ran the busybox commands posted above, and I am back to S-OFF and now I get "permission denied" instead of "unknown user root". I think this is progress, but still can't flash because I don't have root. I noticed opening Superuser keeps FC'ing...
Please post questions in Q&A section.
just follow this guide here, which you are already familiar with. it's for temp root using rage. but since your phone has the eng hboot with s-off it should become permanent once the FS flushes out to disk (flash)
http://forum.xda-developers.com/showthread.php?t=797042
follow the guide for root and mainly to get the su files installed just in case your's didn't instal properly prior. when you are done just type "sync" multiple times in your terminal
wait a while an hour or so. then reboot to verify that it's permanent.
Same thing happened to me with the unknown root user. What finally fixed it for me, was redoing the adb commands that put those files on your device so you could use rage. Once it re put the files on my phone, I did the rage commands again and it worked
Sent from my HTC Glacier using XDA App
Thanks, everyone! I am working again, and I cannot tell you how much I appreciate the help. I was THIS CLOSE to giving up on this phone.
Thanks again.
Mark
It's done. After almost 2 hours, 3 factory resets, a great deal of anxiety, fears that I'd be stuck with a locked phone that I just upgraded to, and a general desire to repeatedly beat my head against the wall to make it all go away, I finally have my bootloader unlocked.
At first I tried Mofo, but the verify app said my phone was incompatible. I guess Mofo doesn't work with the latest OTA. Oh well, I guessed it saved me a bit of dough, though if I knew I was going to have so many problems with Kingroot, I wouldn't have been celebrating yet.
Kingroot. I just don't trust this app, but it's a necessary evil. Because Kingroot relies on an internet connection to work, a person has absolutely no way of knowing if sensitive data is being sent to lord-knows-where, especially considering the app is headquartered in China. I'm wondering if the "free" part of it isn't just bait. Since the app grants root privileges, there's no way of telling what it's doing in the background. The app is also a pain in the arse. At first it worked, or at least it said it did. Then I decided to to follow a guide I came across (I can't remember the exact guide, so don't ask) to replace Kingroot with SuperSU. This might have been where all my problems started, but I can't be sure. Suddenly, a barrage of FCs. Powered off, rebooted, same thing. Settings FC'ed so no way to uninstall except for the launcher, which was also FCing. The only way was to reboot and uninstall before Kingroot auto launched. Finally, back to square 1, or so I thought.
Just to cover my bases, I did a factory wipe, and started over. I didn't set up anything on the phone, just skipped everything in the wizard. Then I downloaded Kingroot and Sunshine. Installed Kingroot, it didn't work. Tried again several times, rebooted, tried again, no luck. Factory reset again. Repeat. Same results. I once managed to get it working, but by the time I tried to install Sunshine, I got a system error that there wasn't enough space. Strange, since I was coming from a factory wipe.
So it was time to start over. This time, however, the phone became so unstable after running Kingroot that the phone was absolutely unusable. I couldn't get into the settings to do a factory reset. I couldn't get into the launcher or the settings to uninstall Kingroot. I felt absolutely hopeless. I literally felt like I was going to vomit. I thought I had possibly bricked my new phone delivered less than 2 hours ago by FedEx. Then I remembered, "Hey, dumbass, you can do a factory reset through fastboot.
Just in case anyone is curious, the exact fastboot commands are:
./fastboot erase userdata
./fastboot erase cache
(Winblows users, omit the ./)
Powered up the phone, in the setup wizard I got a message that the phone had been reset, which didn't appear the previous 2 times I had factory reset the phone. Very interesting. Skipped through the rest of the steps, opened Chrome, downloaded Sunshine and Kingroot. Wouldn't you know it, the first time I ran Kingroot after that reset using fastboot, it worked! Fingers crossed, I ran Sunshine. Same thing!
My theory is that Kingroot must have preserved files in the cache, which leads me to believe that the app truly isn't trustworthy. Anyhow, now that I'm unlocked, TWRP is installed, and I've got a stock backup of the system partition, it's time to flash SuperSU.
The lesson learned: if you're having problems getting root with Kingroot in order to unlock via Sunshine, you might have to do a hard reset through fastboot. Additionally, I would recommend wiping the data and cache partitions after getting unlocked, just to be sure Kingroot isn't leaving any residual files lurking around and doing lord-knows-what on your phone.
Huge thanks to @jcase for Sunshine, and feigned thanks to Kingroot, after all, I couldn't have done it without them. No thanks, however, for the 2 hour nightmare.
I don't get why so many are having issues I unlocked my wife's turbo few weeks ago. Then today said screw it and unlocked my daughter's. Literally took 10 minutes. Had to do one reboot and try kingroot again and I was rooted. Ran sunshine and bam unlocked.
Sent from my XT1585 using XDA Premium 4 mobile app
pastorbennett said:
It's done. After almost 2 hours, 3 factory resets, a great deal of anxiety, fears that I'd be stuck with a locked phone that I just upgraded to, and a general desire to repeatedly beat my head against the wall to make it all go away, I finally have my bootloader unlocked.
At first I tried Mofo, but the verify app said my phone was incompatible. I guess Mofo doesn't work with the latest OTA. Oh well, I guessed it saved me a bit of dough, though if I knew I was going to have so many problems with Kingroot, I wouldn't have been celebrating yet.
Kingroot. I just don't trust this app, but it's a necessary evil. Because Kingroot relies on an internet connection to work, a person has absolutely no way of knowing if sensitive data is being sent to lord-knows-where, especially considering the app is headquartered in China. I'm wondering if the "free" part of it isn't just bait. Since the app grants root privileges, there's no way of telling what it's doing in the background. The app is also a pain in the arse. At first it worked, or at least it said it did. Then I decided to to follow a guide I came across (I can't remember the exact guide, so don't ask) to replace Kingroot with SuperSU. This might have been where all my problems started, but I can't be sure. Suddenly, a barrage of FCs. Powered off, rebooted, same thing. Settings FC'ed so no way to uninstall except for the launcher, which was also FCing. The only way was to reboot and uninstall before Kingroot auto launched. Finally, back to square 1, or so I thought.
Just to cover my bases, I did a factory wipe, and started over. I didn't set up anything on the phone, just skipped everything in the wizard. Then I downloaded Kingroot and Sunshine. Installed Kingroot, it didn't work. Tried again several times, rebooted, tried again, no luck. Factory reset again. Repeat. Same results. I once managed to get it working, but by the time I tried to install Sunshine, I got a system error that there wasn't enough space. Strange, since I was coming from a factory wipe.
So it was time to start over. This time, however, the phone became so unstable after running Kingroot that the phone was absolutely unusable. I couldn't get into the settings to do a factory reset. I couldn't get into the launcher or the settings to uninstall Kingroot. I felt absolutely hopeless. I literally felt like I was going to vomit. I thought I had possibly bricked my new phone delivered less than 2 hours ago by FedEx. Then I remembered, "Hey, dumbass, you can do a factory reset through fastboot.
Just in case anyone is curious, the exact fastboot commands are:
./fastboot erase userdata
./fastboot erase cache
(Winblows users, omit the ./)
Powered up the phone, in the setup wizard I got a message that the phone had been reset, which didn't appear the previous 2 times I had factory reset the phone. Very interesting. Skipped through the rest of the steps, opened Chrome, downloaded Sunshine and Kingroot. Wouldn't you know it, the first time I ran Kingroot after that reset using fastboot, it worked! Fingers crossed, I ran Sunshine. Same thing!
My theory is that Kingroot must have preserved files in the cache, which leads me to believe that the app truly isn't trustworthy. Anyhow, now that I'm unlocked, TWRP is installed, and I've got a stock backup of the system partition, it's time to flash SuperSU.
The lesson learned: if you're having problems getting root with Kingroot in order to unlock via Sunshine, you might have to do a hard reset through fastboot. Additionally, I would recommend wiping the data and cache partitions after getting unlocked, just to be sure Kingroot isn't leaving any residual files lurking around and doing lord-knows-what on your phone.
Huge thanks to @jcase for Sunshine, and feigned thanks to Kingroot, after all, I couldn't have done it without them. No thanks, however, for the 2 hour nightmare.
Click to expand...
Click to collapse
Jcase has vouched for kingroot in the past after analyzing the data that is sent to their servers. He's a professional security researcher and obviously knows his way around android security, so I trust him. I suspect that your attempt to replace kingroot with supersu is what caused the added headache and instability. Kingroot, when it works, only provides root access temporarily, and it does not disable write protection of the system partition, so attempting to write the supersu files to the system partition was probably not well-received. I'm sure you know this now, but you could have performed a factory reset by booting into recovery mode. Anyway, glad it worked!
For some reason when mine unlocked it rebooted and Kingroot decided to make itself into a /system app or is that normal behavior?
Sounds like the OP didn't read the instructions well. Being kingroot is a temp root before unlock trying to replace it with supersu before unlocking is what caused the vast majority of his problems and force closes. Simply not u derstanding instructions before doing something will always lead to problems.
I used it to get temproot, but I wouldn't trust keeping any trace of it on my system.
TheSt33v said:
Jcase has vouched for kingroot in the past after analyzing the data that is sent to their servers. He's a professional security researcher and obviously knows his way around android security, so I trust him. I suspect that your attempt to replace kingroot with supersu is what caused the added headache and instability. Kingroot, when it works, only provides root access temporarily, and it does not disable write protection of the system partition, so attempting to write the supersu files to the system partition was probably not well-received. I'm sure you know this now, but you could have performed a factory reset by booting into recovery mode. Anyway, glad it worked!
Click to expand...
Click to collapse
That's good to know. I was very hesitant to use Kingroot. Knowing that jcase has vetted it makes me feel a lot more at ease.
And you're right, my problems most likely started when I tried to switch to SuperSU. What boggles my mind is that after doing multiple factory resets, something was still incredibly screwy.
What's even stranger is that once Sunshine unlocked the bootloader, I did a factory reset once again, then flashed TWRP and SuperSU. Guess what? Kingroot was still showing in my app drawer. I tried to use Rom Toolbox to remove it, but it wouldn't. I was successful though in freezing it.
Do you help me unlock bootloader?
pastorbennett said:
What's even stranger is that once Sunshine unlocked the bootloader, I did a factory reset once again, then flashed TWRP and SuperSU. Guess what? Kingroot was still showing in my app drawer. I tried to use Rom Toolbox to remove it, but it wouldn't. I was successful though in freezing it.
Click to expand...
Click to collapse
Kingroot has to be uninstalled from the app's options menu. I learned that one the hard way when I unlocked my Turbo. However, the accompanying Purify app can be removed via the normal uninstall method.
rnwalker7 said:
Kingroot has to be uninstalled from the app's options menu. I learned that one the hard way when I unlocked my Turbo. However, the accompanying Purify app can be removed via the normal uninstall method.
Click to expand...
Click to collapse
Ahh. Thanks for that. It's been well over a year since the last time I had to go through the process of rooting, but it's worth it when I'm getting download speeds of 22Mbps when I live out in the boonies. I'm far enough outside of town that I can't even get DSL.
xuanhac87 said:
Do you help me unlock bootloader?
Click to expand...
Click to collapse
You have to be on the latest OTA.
Download and run Kingroot.
Once Kingroot says that you have root access, download and run Sunshine v3.2 beta.
You will need to cough up the $25 for Sunshine to unlock your bootloader.
And whatever you do, don't try what I did. Once you have Kingroot working, don't attempt to replace Kingroot with SuperSU.
As always, you're doing this at your own peril. If you brick your phone, there's no one to blame but yourself.
Nitefire77 said:
Sounds like the OP didn't read the instructions well. Being kingroot is a temp root before unlock trying to replace it with supersu before unlocking is what caused the vast majority of his problems and force closes. Simply not u derstanding instructions before doing something will always lead to problems.
Click to expand...
Click to collapse
It's not about not understanding instructions. I initially wasn't going to go with unlocking the bootloader because I only wanted root for the purpose of enabling tethering and being able to restore my app backups with Rom Toolbox, but I didn't want Kingroot to be that solution because I was a bit leery about using it. I had wanted to use Mofo, but my phone couldn't be verified as rootable with Mofo. Once everything went to crap with trying to replace Kingroot, that's when I said the heck with it and decided to unlock the bootloader anyway.
GreaterLesser said:
For some reason when mine unlocked it rebooted and Kingroot decided to make itself into a /system app or is that normal behavior?
Click to expand...
Click to collapse
With the exception of the experimental marshmallow method that is floating around, you cannot have root access without modifying /system, so it makes sense that kingroot would make itself a system app.
pastorbennett said:
You have to be on the latest OTA.
Download and run
Once Kingroot says that you have root access, download and run
You will need to cough up the $25 for Sunshine to unlock your bootloader.
And whatever you do, don't try what I did. Once you have Kingroot working, don't attempt to replace Kingroot with SuperSU.
As always, you're doing this at your own peril. If you brick your phone, there's no one to blame but yourself.
Click to expand...
Click to collapse
Thanks you!
But i don't have credit card to pay
Brg
Moforoot only worked on4.4.4 that's why it didn't work
pastorbennett said:
That's good to know. I was very hesitant to use Kingroot. Knowing that jcase has vetted it makes me feel a lot more at ease.
And you're right, my problems most likely started when I tried to switch to SuperSU. What boggles my mind is that after doing multiple factory resets, something was still incredibly screwy.
What's even stranger is that once Sunshine unlocked the bootloader, I did a factory reset once again, then flashed TWRP and SuperSU. Guess what? Kingroot was still showing in my app drawer. I tried to use Rom Toolbox to remove it, but it wouldn't. I was successful though in freezing it.
Click to expand...
Click to collapse
When you do a factory reset, what you're basically doing is just wiping the partition that contains data that is modifiable by the user. All that's left are the apps that are on the /system partition, which by default is not modifiable by the user. However, when you used kingroot and later supersu, both of these apps attempt to place themselves into /system so that they can control root access. It sounds like Kingroot was successful. A factory reset does nothing to /system since Motorola assumes that /system cannot be modified.
If you really want to start fresh and undo whatever damage you might have done with your previous root attempts, do the following:
1. Download the official Verizon SU4TL-44 image here: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
2. Unzip the archive and copy all of the system image sparsechunks somewhere convenient on your computer.
3. Boot into bootloader mode and flash the first sparsechunk using the following command: fastboot flash system <name of first sparsechunk file>
4. Repeat step 3 with the other sparsechunk files until all sparsechunks have been flashed in numerical order
5. Wipe cache and userdata using fastboot as you did before.
6. Boot the phone normally.
7. Boot TWRP and flash supersu.
same here mine worked on the first try... this can easily pass as the next great horror story.
TheSt33v said:
With the exception of the experimental marshmallow method that is floating around, you cannot have root access without modifying /system, so it makes sense that kingroot would make itself a system app.
Click to expand...
Click to collapse
What's this?
Sent from my DROID Turbo using XDA Free mobile app
mrkhigh said:
What's this?
Sent from my DROID Turbo using XDA Free mobile app
Click to expand...
Click to collapse
A forum post.
TheSt33v said:
When you do a factory reset, what you're basically doing is just wiping the partition that contains data that is modifiable by the user. All that's left are the apps that are on the /system partition, which by default is not modifiable by the user. However, when you used kingroot and later supersu, both of these apps attempt to place themselves into /system so that they can control root access. It sounds like Kingroot was successful. A factory reset does nothing to /system since Motorola assumes that /system cannot be modified.
If you really want to start fresh and undo whatever damage you might have done with your previous root attempts, do the following:
1. Download the official Verizon SU4TL-44 image here: http://www.rootjunkysdl.com/getdownload.php?file=Droid Turbo/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
2. Unzip the archive and copy all of the system image sparsechunks somewhere convenient on your computer.
3. Boot into bootloader mode and flash the first sparsechunk using the following command: fastboot flash system <name of first sparsechunk file>
4. Repeat step 3 with the other sparsechunk files until all sparsechunks have been flashed in numerical order
5. Wipe cache and userdata using fastboot as you did before.
6. Boot the phone normally.
7. Boot TWRP and flash supersu.
Click to expand...
Click to collapse
Thanks! I'm wanting as clean a system as possible, and this definitely helps!
First off, I have little knowledge about rooting, custom recoveries.. etc. I'm a noob.
My problem is that I do have my Samsung Galaxy E5 (S978L) rooted with King Root (verified with root checker).
But I am trying to get rid of King Root and replace it with SuperSU. I have the SuperSU-Me app installed, but it
doesn't get past "Processing, please wait...". The regular SuperSU app gives me an error when I try to install it,
and it says "The SU binary needs to be updated. Continue?" I have to select normal? Since my device is not listed
under TWRP's install menu... and the normal install fails leading me to "Installation failed! please reboot and try again"
which obviously doesn't work for me. I think I read something about unlocking bootloaders, but I am not sure where
to go from that, since samsung is harder to do that with? Correct me if I'm wrong. Also I don't think it helps that this E5
is the straight talk tracfone model.
Bottom line is I am trying to replace King Root with SuperSU, and install TWRP onto my POS phone. Any help is appreciated. Once again, I have no clue about anything really. Trying to learn this stuff
Try this SuperSu Me version, it worked like charm for me,
https://userscloud.com/krqm5cr96eby.
Google Drive link: https://drive.google.com/file/d/0B-dC_jprJYfYRTVnd0R2b2dRRzQ/view?usp=drivesdk
Hit Thanks if it's helpful!! ?
Sent from my SM-E700H using Tapatalk
I started a thread about thishere.
Has some useful info for you. Supersume got rid of king root for me, version 6.7 did it I'll try to upload it later. Also as far as a custom recovery, we are still working on making a permissive kernel which I feel like I am getting closer, but not having a computer to test with if I brick I'm out the game for a little bit lol. Also in my thread at my latest post I explained how to find the proper partitions to dump with dd in terminal emulator, to make a proper nandroid. Many useful articles on this site. Good luck. Maybe you should merge this with the other thread I linked and started for our sneaky straight talk phones. Also, once we get the permissive kernel, we can get the custom recovery going probably, bootloader needs to be unlocked too. Anyways ya, be easy.
Just a little update: I finally have SuperSU installed. For some reason, supersu me wasn't working with my king root, however once I uninstalled it, and installed KINGOroot supersu me worked...
Maybe I can now assist in your process since I have a powerful computer and a decent paying job. But my days are pretty busy. But shortly I'll be trying to make a nandroid backup after doing some reading. Have to learn some of this stuff. But my next couple days are packed. Anyways thanks for pointing me in the right direction
firmware galaxy e5 s978L!!!
the cure
need
-Odin
-drivers samsung
and download this firmware :
firmware.gem-flash.com/index.php?a=browse&b=category&id=8395
Andough said:
First off, I have little knowledge about rooting, custom recoveries.. etc. I'm a noob.
My problem is that I do have my Samsung Galaxy E5 (S978L) rooted with King Root (verified with root checker).
But I am trying to get rid of King Root and replace it with SuperSU. I have the SuperSU-Me app installed, but it
doesn't get past "Processing, please wait...". The regular SuperSU app gives me an error when I try to install it,
and it says "The SU binary needs to be updated. Continue?" I have to select normal? Since my device is not listed
under TWRP's install menu... and the normal install fails leading me to "Installation failed! please reboot and try again"
which obviously doesn't work for me. I think I read something about unlocking bootloaders, but I am not sure where
to go from that, since samsung is harder to do that with? Correct me if I'm wrong. Also I don't think it helps that this E5
is the straight talk tracfone model.
Bottom line is I am trying to replace King Root with SuperSU, and install TWRP onto my POS phone. Any help is appreciated. Once again, I have no clue about anything really. Trying to learn this stuff
Click to expand...
Click to collapse
I installed super su on my Galaxy On5, flashed super su and rooted it with Odin too. Today i hit full unroot on supersu then rebooted and snapchat worked which told me it's been unrooted. Then figuring I'd be safe with installing magisk (since super su said it reverted to the stock image or something like that) I flashed magisk 13.3 but after it finished succesfully i rebooted but can't find anything magisk related installed on my phone. Could someone point me in the right direction?
Mike_77712 said:
I installed super su on my Galaxy On5, flashed super su and rooted it with Odin too. Today i hit full unroot on supersu then rebooted and snapchat worked which told me it's been unrooted. Then figuring I'd be safe with installing magisk (since super su said it reverted to the stock image or something like that) I flashed magisk 13.3 but after it finished succesfully i rebooted but can't find anything magisk related installed on my phone. Could someone point me in the right direction?
Click to expand...
Click to collapse
I had one time where I got Magisk working with the Superstarz ROM on the SM-G550T1. I don't remember what I did tbh, but it took hours of rebooting, frustrating hanging, etc.. Upon one of the Magisk modules I flashed after it did work, of course to my sadness it stopped working. Nandroid backups are so crucial and I just stopped making so many changes before a backup these days. Sure you can't speed demon through and get all your wildest fantasies to come true overnight, but I find making incremental progress with backups to me more sustainable. Anyways, I tried many times, many setups, and ultimately wasted many hours trying to "win" with this phone. I'd honestly highly recommend sticking with SuperSu by Chainfire as it has always just worked. That means no Android Pay, no Pokemon Go, and prolly others I haven't considered. I too wanted to have my cake and eat it... For Safetynet to pass and la la la. Truth be told, it is a royal pain in the arse!!! If YOU STILL DARE, you would definitely want to make sure you start with a stock ROM boot image and BACK IT UP #1. If you are using a custom ROM it may not allow you to fully unroot and go back to a stock img because it doesn't find one to revert to. For Magisk to pass SafetyNet and work at full capacity, you must start there. If you go to the trouble of going all the way back to stock, please upload one for all of us and make sure to include your phone/os specs from about phone. From stock, flash custom recovery BEFORE ROOT, within recovery back up boot, upload for us and yourself. Now, you have a legit revertible img to go back to in case you can't from Magisk/SuperSu. Phh's Superuser was a nightmare btw, never worked correctly. There's no way to unroot and go back to a stock boot img that I found unless you first back up from TWRP or custom recovery. Long answer, more than you bargained for no doubt, but hopefully something to be gained from. Really though... if all you want is for Snapchat to work and can live without Android Pay/Pokemon Go. Here's an easier method: uninstall Xposed, unroot, log into Snapchat (let it save a login token), root, re-install Xposed, Titanium Backup Snapchat, it should hold up from there. Did it once, forget if that's entirely right, but search and ye will find exact threads. I just said to hell with Snapchat, Pokemon Go, and Android Pay. I'd rather settle for Chainfire's Superuser's stability, Xposed (more mods), & less overall B.S. Sorry if that isn't the best possible answer, or what exactly you were sought. I did however want to share some of my experience (many, many, many hours of tinkering). All in all, I finally decided to order a new digitizer/lcd to repair an old OnePlus One that I have had laying around. I plant to fix it and migrate because I'll tell ya right now... ppl just aren't gonna do much more for this model than what you see out there. Perhaps I'm being a pessimist, but also realist... I've been waiting around looking for something to come, too lazy to attempt re-compilation of code myself, and no one else has yet. Magisk can be a nightmare to the ninth gate's extreme degree. It is possible, not saying it can't be done. Have patience, or it won't that's for sure. Just really have to mess up... lots of times... over and over, and over and over and over again. Learn, read XDA, and be stubborn/patient as hell until you get there. Document your progress so you know what you did and maybe you can help someone else. Other times it's more advantageous pick what matters, settle, and focus on something else. :good:
From my understanding you need a clean install, unroot with SU (or install SU as systemless (?)),wipe internal, and follow instructions to install Magisk... I'm not totally sure though, also install the Magisk module.
Mike_77712 said:
I installed super su on my Galaxy On5, flashed super su and rooted it with Odin too. Today i hit full unroot on supersu then rebooted and snapchat worked which told me it's been unrooted. Then figuring I'd be safe with installing magisk (since super su said it reverted to the stock image or something like that) I flashed magisk 13.3 but after it finished succesfully i rebooted but can't find anything magisk related installed on my phone. Could someone point me in the right direction?
Click to expand...
Click to collapse
I just successfully rooted with Magisk & modded a few things out with it, only issue seemz to be systemless xposed but ill crack that shell when need be . Let me know if any1 is in need of help doing the same.
woahOppO999 said:
I just successfully rooted with Magisk & modded a few things out with it, only issue seemz to be systemless xposed but ill crack that shell when need be . Let me know if any1 is in need of help doing the same.
Click to expand...
Click to collapse
Can you please share the steps you followed to root ON5 pro using magisk.
Also if you can list the modules u have from magisk.
Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice
tbonedude said:
Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice
Click to expand...
Click to collapse
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk
donc113 said:
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply, as of edit 3, I am back on OB6, and cannot seem to get root. Are my chances better with OF1?
Ive tried yemen tools (says 5.0 not found)
I've tried kingo root (says successful, never reboots, and shows "this phone root isnt properly setup" when checking with root checker from joey kilm (think thats his name)
Does it matter my emmc ID is ending with 43100?
https://cdn.discordapp.com/attachments/221482708063223809/378367914388094981/image.png <- image from unlock_n3 after success, emmc checker shows same value AFTER odin ob6 (this held, nothing else did)
Edit: After taking donc's recommendation of OF1, I am now able to run yemen tools. As a side note, I seem to have more bars of service with OF1... coincidence?
Edit2: I HAVE ROOT! on OF1 using yemen tools (downgraded from PL1 to OB6 finally to OB1 and it worked.) Now to re-unlock bootloader. Thanks guys for the support thus far, this is a journey and having qualified accomplices makes this SOOOO much easier.
So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:
tbonedude said:
So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:
Click to expand...
Click to collapse
You're welcome. Just an FYI, the ending of the CID doesn't matter, it's the first 2 numbers that count, and they MUST be 15
I used Flashify (available on Google Play) to load TWRP... worked great (but you must have root and busybox installed to use it to flash TWRP)
Sent from my SM-N900V using Tapatalk