• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Okay, so get this...

jujumane

jujumane

Member
Today is a great day. Yesterday was a day of panic. Reason? Soft bricked my phone. It was tragic, but my homies here have turned this place into the best dev team of any phone I've bought.

I'm hoping those homies can help me with something... weird.
So, it's nothing drastic, but coming out of the soft brick, I flashed Masterchief's nonrooted stock ROM that's provided to all whom want to return to stock after trying out several other ROMS. After the flash, I didn't lose anything, which puzzled me. What puzzled me MORE was what comes after me doing some backing up, knowing I was not rooted, and safely triggering a factory reset.

Now, the phone does it's thing... But TWRP is helping with that. I have no clue why TWRP is still in my system when it should've been wiped. Besides that, the real problem is that now, through Kingroot, after going at it all day, simply doesn't work. When I say that, I mean it doesn't progress more than from the same percentage, and the phone doesn't reboot. It simply tells me to do it on the desktop instead.

With all this in mind, I'm still wondering how TWRP can be functional. It's convenient, I'm definitely not complaining, but if it helps me achieve root then that's a better scenario for me.

TL;DR: flashed unrooted backup, did factory reset, currently unrooted, TWRP is still able to boot up, what can i do since kingroot isn't working for me?
 
Last edited:
Since butternoob is prerooted, will that help if flashed?

And I believe TWRP is still on there because the factory reset may not format the recovery partition. Just a guess.
 
HallOfPromise said:
Since butternoob is prerooted, will that help if flashed?

And I believe TWRP is still on there because the factory reset may not format the recovery partition. Just a guess.
Click to expand...

It would help, but I'd rather avoid that. It's either stock or CM for me, and I'm not ready for CM yet.

You're probably right about that. I hope it isn't affecting the root process, though, because deleting TWRP to install again after the root is complete is probably a mission.
 
twrp does not remove if u flash another rom defeats the purpose of it if it did :/ only way it disappears if u use something like odin .
 
I flashed a backup of a nonrooted stock ROM, so I had guessed I would have had to do it over again safely. About the kingroot conflict, though, it's just odd to me. I've never heard anyone recommend the desktop version, but since it persists in telling me, should I just do it?
 
no it wont work u need to follow the instructions on the OP i herd u need to run alot of apps for it to work so just open alot of app and let them run then run kinguser but if you have twrp why not just install butternoob v2?
 
jujumane said:
It would help, but I'd rather avoid that. It's either stock or CM for me, and I'm not ready for CM yet.

You're probably right about that. I hope it isn't affecting the root process, though, because deleting TWRP to install again after the root is complete is probably a mission.
Click to expand...
butternoob is a stock ! and its not a mission once u have root just install the twrp apk
 
Your phone has a rather large number of partitions - for the bootloader, recovery, radio firmware, security and the big three for a user - the boot image (where the kernel is), system (the rest of Android), and data (where your apps, system app updates, and private app data goes).

Pretty sure that the nandroid backup you restored contained only boot and system (or in any case, at least just the system) but not the data - which is what any rom contains btw (no data).

It therefore left your data partition intact and because the three pieces (boot, system and data) were from the same logical rom, everything worked.

That's as @Masterchief87 intended it.

For other roms, you'll back up apps and data with Titanium Backup, follow installation instructions for wiping, and restore data from the Titanium Backup.

A factory data reset only affects two things (three from a user perspective) - it erases the (Android main) cache, the Dalvik cache, and data (hence, all of your apps and their data go away).

This is why I said in the other thread that no factory data reset was going to fix the system partition.

Why your data remained intact after a factory data reset probably has to do with an angel on your shoulder this time around.

Odin and Kies are Samsung oddities and like the HTC RUU oddity are all probably best left out of discussion where they don't apply, otherwise, confusion sets in.

As for this phone, the bootloader is locked, so for root operations here the boot image is being written into the recovery partition (a unique solution) at some point.

Whether that has an effect on rerooting or not via king escapes me. It probably nullifies the need for it.

Your next bet, since everything else is already cracked and in place would probably be to get the SuperSU install package from the source -

https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip

And install that from TWRP - in other words, the same final rooting step as if the catastrophic editing never occurred.

I'll leave it to @Masterchief87 or @hroark13 to correct any of my mistakes here.

But I think that you flash SuperSU and move on.

A rooted rom is simply a rom with the superuser binary and a matching control app embedded into the /system partition.

Flashing SuperSU from TWRP embeds those two things.
 
that's what I was thinking..Su update...but at least the recommendation didn't come from me...more than half the time my comments are just long winded and confusing...like this one...meaning mine...
 
EarlyMon said:
Your phone has a rather large number of partitions - for the bootloader, recovery, radio firmware, security and the big three for a user - the boot image (where the kernel is), system (the rest of Android), and data (where your apps, system app updates, and private app data goes).

Pretty sure that the nandroid backup you restored contained only boot and system (or in any case, at least just the system) but not the data - which is what any rom contains btw (no data).

It therefore left your data partition intact and because the three pieces (boot, system and data) were from the same logical rom, everything worked.

That's as @Masterchief87 intended it.

For other roms, you'll back up apps and data with Titanium Backup, follow installation instructions for wiping, and restore data from the Titanium Backup.

A factory data reset only affects two things (three from a user perspective) - it erases the (Android main) cache, the Dalvik cache, and data (hence, all of your apps and their data go away).

This is why I said in the other thread that no factory data reset was going to fix the system partition.

Why your data remained intact after a factory data reset probably has to do with an angel on your shoulder this time around.

Odin and Kies are Samsung oddities and like the HTC RUU oddity are all probably best left out of discussion where they don't apply, otherwise, confusion sets in.

As for this phone, the bootloader is locked, so for root operations here the boot image is being written into the recovery partition (a unique solution) at some point.

Whether that has an effect on rerooting or not via king escapes me. It probably nullifies the need for it.

Your next bet, since everything else is already cracked and in place would probably be to get the SuperSU install package from the source -

https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip

And install that from TWRP - in other words, the same final rooting step as if the catastrophic editing never occurred.

I'll leave it to @Masterchief87 or @hroark13 to correct any of my mistakes here.

But I think that you flash SuperSU and move on.

A rooted rom is simply a rom with the superuser binary and a matching control app embedded into the /system partition.

Flashing SuperSU from TWRP embeds those two things.
Click to expand...

I really appreciate this, man. Something fishy happened, though. Right after that flash, SuperSU didn't come up on my launcher. I'm not getting anything out of root checker. I decide to manually download SuperSU. After installing, I click the TWRP kernel update and nothing happens. Out of the blue, I don't have TWRP anymore. I wouldn't be able to get it now through means of the APK since I don't have root access, so first I need root access, which would require a PC if I wasn't going to use Kingroot.

EDIT: I do have TWRP, 90% of this paragraph is invalid
 
Last edited:
Disregard everything I just said about TWRP, I DO have TWRP. It decided to appear now after powering off and holding buttons, but I'm not rooted, so there's my luck still.
 
Last edited:
k....I still want to run it...but, for some lame reason I keep running into the lame a$$ "insufficient storage" malarkey....
stupid poop...
got a link to a working dsp?
I'm being lazy
 
As stated before, download the su zip file, boot into twrp, and just run the zip file through twrp... No reason to do king again. The only reason you did king in the first place was to get temp root so you could install twrp. You already have it. A simple flash of su zip through twrp will have you rooted.
 
I think he confused twrp with the apk installer that flashes it. Since the twrp recovery itself is still on your phone's recovery partition there is no need for using kingroot again. If your system isn't rooted then you won't be able to reboot into twrp by using the app. Instead you access twrp recovery by powering off the phone and then holding power & volume up for about 4 seconds.

I'll check into the issue about not being able to root my stock ROMs. I don't know because I didn't bother to check if flashing the SuperSU zip would work simply because I've never heard of flashing the supersu zip not working. Honestly I think there is some kind of communication error here or something that is not being done right but just in case there is something to this issue I'll check it out. Honestly I haven't been doing very much other than running cm12.1 and reporting bugs because my PC is in the pawn shop right now. I will try get to the bottom of the issue with the SuperSU recovery zip not working though.
 
You must log in or register to reply here.
Back
Top Bottom