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!
Related
Ok guys it looks like Jcase did it again he created an exploit that gets write protecton off for good or until an OTA. He states this will survive even an FXZ or factory data reset.
Here is what I did took about 15 min. go here ---->http://forum.xda-developers.com/showthread.php?t=2551113 down load the exploit follow the instructions it's very easy the exploit does it all. I am not sure if I needed to do this or not but I did to be safe I used fastboot and put stock recovery back. Just take the recovery.img from the FXZ and open a command prompt type in this command------> fastboot flash recovery recovery.img
You must be in fastboot obviously it will flash recovery back and you lose WP off. You then run MotoWpNoMo and it bypasses WP protection for ever or until OTA from what I have read. Open a command prompt and type in this command------> adb shell getprop ro.boot.write_protect to check if write protection is disabled it will return a value of "0". No more having to boot into recovery to make system changes that require writer protection off this is true root. Great job Jcase!!!!!!!!!!!!!!!!!!!!
Oh and we have stock recovery back and I beleive that voodoo ota root keeper works on 4.2.2 so I think we will have a very easy time upgrading to 4.4 and not have to re-root this is just a theory at this point.
I just tweeted Jcase looks like he tested this method it was the rumrunner team (beaups and fuses) that created this exploit.
Why couldn't this come at the beginning of a weekend, instead of a week? Aaaarrrrrggghhhh!
fat-fingered and Maxx-ed out.
Einsteindks said:
Why couldn't this come at the beginning of a weekend, instead of a week? Aaaarrrrrggghhhh!
fat-fingered and Maxx-ed out.
Click to expand...
Click to collapse
It actually did but I worked all weekend and was not able to try it until today but it is SUPER EASY TO DO.
The other plus to this is voodoo still protects root on 4.2.2 so since we have stock recovery back we SHOULD not guaranteed but should be able to download the update to our sdcard an install 4.4 through stock recovery and keep root. The only question is if we would need to run the exploit again to get write protection off. I don't know if it would survive the OTA but I am leaning on it not surviving. Not that it matters this works on 4,4 anyway.
Another quick way to see if WP is off is to uninstall then re-install SS recovery we could not do that before unless we booted in to recovery with WP off. I just tried it and it works great.
Worked perfect on my Mini. Just be patient and keep an eye on it for granting superuser permission and unlocks after reboots.
should i just wait for kitkat to come out? because i dont feel like refreshing everything and starting over lol.. since i went back to stock and not able to save data XD
bigv5150 said:
Ok guys it looks like Jcase did it again he created an exploit that gets write protecton off for good or until an OTA. He states this will survive even an FXZ or factory data reset.
Here is what I did took about 15 min. go here ---->http://forum.xda-developers.com/showthread.php?t=2551113 down load the exploit follow the instructions it's very easy the exploit does it all. I am not sure if I needed to do this or not but I did to be safe I used fastboot and put stock recovery back. Just take the recovery.img from the FXZ and open a command prompt type in this command------> fastboot flash recovery recovery.img
You must be in fastboot obviously it will flash recovery back and you lose WP off. You then run MotoWpNoMo and it bypasses WP protection for ever or until OTA from what I have read. Open a command prompt and type in this command------> adb shell getprop ro.boot.write_protect to check if write protection is disabled it will return a value of "0". No more having to boot into recovery to make system changes that require writer protection off this is true root. Great job Jcase!!!!!!!!!!!!!!!!!!!!
Oh and we have stock recovery back and I beleive that voodoo ota root keeper works on 4.2.2 so I think we will have a very easy time upgrading to 4.4 and not have to re-root this is just a theory at this point.
I just tweeted Jcase looks like he tested this method it was the rumrunner team (beaups and fuses) that created this exploit.
Click to expand...
Click to collapse
you mean i can keep the root by flash back the stock recovery.img ? so i can still receive the ota , and have the root after update ?
I doubt that you can keep your root and take the OTA. It caused a whoping lot of problems last time around, and I don't see it being any different when we take KitKat either. Best to flash a stock version of the ROM, then take the update. You may still keep write protection off.
fat-fingered and Maxx-ed out.
Einsteindks said:
I doubt that you can keep your root and take the OTA. It caused a whoping lot of problems last time around, and I don't see it being any different when we take KitKat either. Best to flash a stock version of the ROM, then take the update. You may still keep write protection off.
fat-fingered and Maxx-ed out.
Click to expand...
Click to collapse
That is not necessarily true. The issue with the last update was taking the ota with root still installed. Voodoo still works on 4.2.2 so if you protect root and then unroot with voodoo you should be able to take the update and then restore root after the update. I used voodoo on the last update and kept root what screwed me was I lost write protection off. When I tried to run pwnmymoto it saw I was already rooted and wouldn't run the exploit so I was stuck till I could fxz and run pwnmymoto again. That won't happen here since we have write protection off script now. So you use voodoo then restore root then run motowpnomo and you will have root and write off protection.
bigv5150 said:
That is not necessarily true. The issue with the last update was taking the ota with root still installed. Voodoo still works on 4.2.2 so if you protect root and then unroot with voodoo you should be able to take the update and then restore root after the update. I used voodoo on the last update and kept root what screwed me was I lost write protection off. When I tried to run pwnmymoto it saw I was already rooted and wouldn't run the exploit so I was stuck till I could fxz and run pwnmymoto again. That won't happen here since we have write protection off script now. So you use voodoo then restore root then run motowpnomo and you will have root and write off protection.
Click to expand...
Click to collapse
root vs running your phone without a recovery. 2 different things , wouldn't you say? root was maintained through the OTA without any steps to hide it. rooting your phone doesn't mess up system updates. running without a recovery does.
Ok, so I am right in that when root is in place, it causes problems during updates (due to recovery used for WP off mode. Prob'ly the reason for most noob problems.). I wasn't aware that voodoo still worked. I certainly would've used it last time! I'll try it next time. So, theoreticaly, having a clean root, run the WP script, flash the OE recovery back on, and, using voodoo, KK should take, as long as the factory ROM isn't altered? Ideally then, we should be able to restore root, and still have a WP off after KK? I'm guessing, to be on the safe side, safestrap should temporarily be uninstalled. Probably not necessary, but it couldn't hurt.
Edit: looks like voodoo wont work into 4.4, due to KK.
fat-fingered and Maxx-ed out.
mistermojorizin said:
root vs running your phone without a recovery. 2 different things , wouldn't you say? root was maintained through the OTA without any steps to hide it. rooting your phone doesn't mess up system updates. running without a recovery does.
Click to expand...
Click to collapse
I don't understand what you are trying to say we have full root now and stock recovery like any other android device. Taking an OTA root wont survive the reason why people boot looped had nothing to do with root as much as not having recovery. Once the OTA tried to install itself there was no recovery to install it hence the bootloop.
Einsteindks said:
Ok, so I am right in that when root is in place, it causes problems during updates (due to recovery used for WP off mode. Prob'ly the reason for most noob problems.). I wasn't aware that voodoo still worked. I certainly would've used it last time! I'll try it next time. So, theoreticaly, having a clean root, run the WP script, flash the OE recovery back on, and, using voodoo, KK should take, as long as the factory ROM isn't altered? Ideally then, we should be able to restore root, and still have a WP off after KK? I'm guessing, to be on the safe side, safestrap should temporarily be uninstalled. Probably not necessary, but it couldn't hurt.
Edit: looks like voodoo wont work into 4.4, due to KK.
fat-fingered and Maxx-ed out.
Click to expand...
Click to collapse
Correct but most of us have probably altered the system in one way or another and will have to fxz for a clean system to take update.
Voodoo wont work on 4.4 it works for 4.2.2 but I see what you are saying it may not restore root once on 4.4. That I am unsure of since I don't believe any one has tried it. Worst case scenario it doesn't restore root and you have to re-root then install stock recovery then run motowpnomo. I can't see the harm in trying.
this is not a root tool correct just RW tool?
StankFiss said:
this is not a root tool correct just RW tool?
Click to expand...
Click to collapse
Yep
fat-fingered and Maxx-ed out.
bigv5150 said:
Ok guys it looks like Jcase did it again he created an exploit that gets write protecton off for good or until an OTA. He states this will survive even an FXZ or factory data reset.
Here is what I did took about 15 min. go here ---->http://forum.xda-developers.com/showthread.php?t=2551113 down load the exploit follow the instructions it's very easy the exploit does it all. I am not sure if I needed to do this or not but I did to be safe I used fastboot and put stock recovery back. Just take the recovery.img from the FXZ and open a command prompt type in this command------> fastboot flash recovery recovery.img
You must be in fastboot obviously it will flash recovery back and you lose WP off. You then run MotoWpNoMo and it bypasses WP protection for ever or until OTA from what I have read. Open a command prompt and type in this command------> adb shell getprop ro.boot.write_protect to check if write protection is disabled it will return a value of "0". No more having to boot into recovery to make system changes that require writer protection off this is true root. Great job Jcase!!!!!!!!!!!!!!!!!!!!
Oh and we have stock recovery back and I beleive that voodoo ota root keeper works on 4.2.2 so I think we will have a very easy time upgrading to 4.4 and not have to re-root this is just a theory at this point.
I just tweeted Jcase looks like he tested this method it was the rumrunner team (beaups and fuses) that created this exploit.
Click to expand...
Click to collapse
Am I the only one who noticed that this is totally missed credited? Jcase had nothing to do with this exploit. He is thanked for his contribution of root access that allows for it but that is all.
Sent from my XT1080 using XDA Premium 4 mobile app
TheWhiteChallenger said:
Am I the only one who noticed that this is totally missed credited? Jcase had nothing to do with this exploit. He is thanked for his contribution of root access that allows for it but that is all.
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I guess so because everyone else knows how to read maybe you should read the WHOLE POST!!!!! is says at the end that "I just tweeted Jcase looks like he tested this method it was the rumrunner team (beaups and fuses) that created this exploit". I mean it's actually in your post where you quoted me "reading comprehension it's a wonderful thing".
Crud. Just tried this, and it says driver errors and some junk. I KNOW everything IS installed, I put stock recovery back first. Security things/firewall off, to. Any ideas?
Edit: scratch request...was starting in fastboot mode...oops.
fat-fingered and Maxx-ed out.
Einsteindks said:
Crud. Just tried this, and it says driver errors and some junk. I KNOW everything IS installed, I put stock recovery back first. Security things/firewall off, to. Any ideas?
Edit: scratch request...was starting in fastboot mode...oops.
fat-fingered and Maxx-ed out.
Click to expand...
Click to collapse
Lol can't tell you how many times I have made that mistake. Also using the wrong USB port for rsd and it doesn't see my phone.
I'm getting confused reading all of the posts that seem to be more about upgrading and rooting than this actual exploit. But my question is this.... I am rooted through jcase's exploit ("pwnmymoto" i think it's called) and still on the original firmware (pre camera update) with no recovery. Can i run this permanent WP killer from where my phone is now? Or do i have to flash the stock recovery back first? Also, will this wipe data?
To be honest, it's been a while since i flashed anything and i'm not real comfortable with the FXZ process just yet. All of my other phones have been highly supported by the devs and i have always had a utility to do all of the work for me. I'm hoping this will be pretty easy. I just want to know what i'm getting into before i soft brick my phone and have to wait days to figure out how to fix it.
I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?
Claghorn said:
I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?
Click to expand...
Click to collapse
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.
madbat99 said:
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.
Click to expand...
Click to collapse
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.
Claghorn said:
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.
Click to expand...
Click to collapse
Since lollipop it is very sensitive to anything different or missing in system. Just flash the 5.1 factory image with the ~w removed from the flash-all.bat file so it doesn't wipe data. Or use wugs to flash stock 5.1 image with "no wipe" enabled. Or like I said in previous you can always flash a clean system image of 5.0.2 then take ota. Either way will update you without wiping data.
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !
neo5468 said:
... I don't get it why people bother with OTA all the time ...
Click to expand...
Click to collapse
I'm not really bothering with it - it just showed up and started bothering me .
1.Backup everything.
2.Flash 5.1 with nexus root toolkit.
3.Restore all the data.
4.Change your build in NRT to android 5.1
5.Root it and flash TWRP/CWM if you want.
6.?????
7.Profit! duh
neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root.
Click to expand...
Click to collapse
... or wait for a week until someone will release a rooted 5.1 update
sensboston said:
... or wait for a week until someone will release a rooted 5.1 update
Click to expand...
Click to collapse
Why would you wait a week, we already waited too long for offical 5.1 to come out for our tablet. It is 5minutes of work, works 100% and also fasboot is the safest way to flash. Also you download the image straight from developers.google.com so there is no bs. I much rather flash that. But to each his own.
There is already a recovery flashable "stock rooted 5.1" thanks to scrosler (cleanrom Dev).
5.1 rooted ROM
neo5468 said:
Why would you wait a week
Click to expand...
Click to collapse
Agree, week is too long. A few days - better words And "one click" solution is much better in case of possible mistakes during flashing separate partitions, rooting etc...
neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !
Click to expand...
Click to collapse
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?
beall49 said:
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?
Click to expand...
Click to collapse
Custom recovery is fine. There is also a new boot loader to flash as well I think. You can also run the flash all batch file in the factory image and just remove the -w from it so it doesn't wipe data. But what you posted is also correct, but flash the boot loader too. If your rusty at it just use wugs toolkit, it will run the commands for you.
Solid, removing the -w was what I was forgetting. I knew there was something else.
Thanks!
Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL
nlinecomputers said:
Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL
Click to expand...
Click to collapse
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.
madbat99 said:
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.
Click to expand...
Click to collapse
No big deal really. I don't keep important data on it. It's mostly used for Kindle and games. Easy to fix.
Ok guys, bear with me.
I haven't done much "developing" or anything but I was able to get Xposed to install and now have Gravity Box running on my stock and locked Maxx. I used the KingRoot described and provided in the thread http://forum.xda-developers.com/droid-ultra/general/root-kingroot-4-4-4-su-6-7-t3117552 by @aviwdoowks. I had installed SuperSU Pro, KingRoot from the aforementioned thread, and the Xposed framework. After getting root with KingRoot, I went into SuperSU and checked survival mode (don't know if this does anything or not). Then, I went into Xposed and had it set to classical installation.
Now, this is where some persistence and effort went into effect. Through multiple attempts, of rebooting , KingRoot rooting, and trying to install Xposed, it finally took. Where aviwdooks, says to wait after booting to run KingRoot, I ran it immediately. As soon as root was obtained I would go into Xposed and run the Classical install. When it finally took, and asks to reboot, HIT CANCEL. Then from the Xposed menu, hit soft-reboot. So far I have survived multiple soft-reboots with Xposed running.
hope this helps someone.
@teerout
Kudos
Does it all go to data? Or rather once installed is system not utilized?
Btw the synchronization to gdrive is all sorted out now. My entire sd excluding 0/TiBU AND including legacy/TiBU!! Using Drive AutoSync.
Ti does tower above He in both convenience and allowing all user apps. I thought I would say it here as my thread is rather a mess
Avi,
I don't know how to answer that about data or system being utilized. Good work with getting the backups to work. I should do something similar.
teerout said:
Avi,
I don't know how to answer that about data or system being utilized. Good work with getting the backups to work. I should do something similar.
Click to expand...
Click to collapse
Still working?
How long now?
yes, still working. I had it running the other day, but wanted to make sure I could recreate it before posting on here. So from installing it this morning around 830, its past noon now, still working and surviving the soft-reboots. it looses functionality on a hard reboot, but can always be re-activated. hope to hear others can get it too.
@teerout
Hi,
You on su6-7.2?
We are all waiting to hear from you at 9:41am sharp.
Yes this is a known effect of a soft boot. You can change anything you want in /system (with root) as long as you only do soft boot. Only the user apps get initialized from terminating zygote.
You are better flashing in root per CrashXXL's thread. It would be nice to bake xposed in so it survives a KK OTA like root does but I suspect the only way is to image and flash the entire 6-72 /system partition.
aviwdoowks said:
@teerout
Hi,
You on su6-7.2?
We are all waiting to hear from you at 9:41am sharp.
Click to expand...
Click to collapse
No, SU6-7.
Yea, Ive been debating if I want to take the steps to work through the method crash put together. Got essentially the same results. Im tempted to try the "crash" method with an older fxz from Moto, but don't want to destroy my device.
teerout said:
No, SU6-7.
Yea, Ive been debating if I want to take the steps to work through the method crash put together. Got essentially the same results. Im tempted to try the "crash" method with an older fxz from Moto, but don't want to destroy my device.
Click to expand...
Click to collapse
Have many bricked that way? I just thought it was damn arduous.
Soooo how long?
aviwdoowks said:
Have many bricked that way? I just thought it was damn arduous.
Soooo how long?
Click to expand...
Click to collapse
don't think anyone has reported they bricked, im just hesitant to force my phone to brick through the process. im also trying to determine from this other thread by littletoslo in the QA section, if they used an older fxz file and got it to work.
xposed is still running with the gravity box mods, no hiccups.
On 6-7, the crashxxl method survives a hard reboot for both su and xposed. Using an older or newer fxz with the crash method will brick your device. Furthermore, just flashing an older version may result in serious gpt version issues.
Sent from my XT1080 using XDA Free mobile app
larsdennert said:
On 6-7, the crashxxl method survives a hard reboot for both su and xposed. Using an older or newer fxz with the crash method will brick your device. Furthermore, just flashing an older version may result in serious gpt version issues.
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
To verify: I took the OTA this morning after a quick skim of xda, much to my chagrin, as I learned xposed didn't survive. To fix this, I can just reflash the 6-7 back using rsdlite and I'm back in business? Is anyone working on a fix for surviving hard reboot with baked in xposed on the 6-7.2? Thanks!
Yes the keys didn't update. You can do a full rsd flash of 6-7 and go back through the root/xposed process. If I find some time I will tackle making a system image of 6-7.2 with root and xposed. It may come down to root on the G4 though. If it doesn't have a R/O system image, I'm jumping ship from many years of Motorola.
larsdennert said:
Yes the keys didn't update. You can do a full rsd flash of 6-7 and go back through the root/xposed process. If I find some time I will tackle making a system image of 6-7.2 with root and xposed. It may come down to root on the G4 though. If it doesn't have a R/O system image, I'm jumping ship from many years of Motorola.
Click to expand...
Click to collapse
How this pertains to the op?
aviwdoowks said:
How this pertains to the op?
Click to expand...
Click to collapse
Basically just reaffirming that you can temp install xposed if you have some sort of root as long as you only soft reboot. Problem is you can only soft reboot so many times before it locks up and then you have to cold boot (Vol up + Vol Dn + Power). A better way is to bake it in to the r/o system image like CrashXXL and the Moto X. An even better way is to be done with Motorola LOL.
larsdennert said:
Basically just reaffirming that you can temp install xposed if you have some sort of root as long as you only soft reboot. Problem is you can only soft reboot so many times before it locks up and then you have to cold boot (Vol up + Vol Dn + Power). A better way is to bake it in to the r/o system image like CrashXXL and the Moto X. An even better way is to be done with Motorola LOL.
Click to expand...
Click to collapse
.... Reboot is hold power on X, Ultra & newer
Ok. :good:
I think I've just successfully extracted a modified 6-7.2 system image for flashing back. This should be interesting.
larsdennert said:
I think I've just successfully extracted a modified 6-7.2 system image for flashing back. This should be interesting.
Click to expand...
Click to collapse
you had my curiosity, now you have my attention.
See next post
Save for pics
used here
A contributor is reporting success rooting 5.3.2.1 with Kingroot. No immediate confirmation...simply reposting for visability and comment. Report your results here for community benefit.
https://forum.xda-developers.com/am...-5th-gen-supertool-root-t3272695/post70784402
Reminder: Do not attempt to rollback FireOS 5.3.2.1; you will likely be rewarded with a brick.
No success for me. I have assumed "Gave both king root and purify full access via setting" as enabling these apps in accessibility under services?
I have tried KR 4.9.2, 4.9.6, 4.9.7, 5.0.0 and 5.0.3 numerous times. Also done a factory reset and followed the steps stated to no avail.
Maybe I am just unlucky.
stonedpsycho said:
No success for me. I have assumed "Gave both king root and purify full access via setting" as enabling these apps in accessibility under services?
I have tried KR 4.9.2, 4.9.6, 4.9.7, 5.0.0 and 5.0.3 numerous times. Also done a factory reset and followed the steps stated to no avail.
Maybe I am just unlucky.
Click to expand...
Click to collapse
Not having any luck with it either.
This is just a quick overview for testing purposes. As always, there is an extreme chance of the undesired "Bricked Device". You are warned...
1. Make sure adb and fastboot drivers are enabled and working to the 5th gen Fire. Extremely important.
2. Once connection is working follow the "Super Tool" setup directions.
3. Disable ota, disable ads and install GPlay. Somethings can only be done after root.
4. Once you have Gplay setup, use Super Tool to install KingRoot.
5. When you first run KingRoot, it will advertise "Purify Battery Saver" install it.
6. Afterwards run KingRoot. It will reboot 3-5 times before applying root. This process of rooting consumed over an hour and may need to be restarted if KingRoot fails.
7. Please keep in mind it is just an overview in order to determine the steps correctly.
If necessary I will start from square one and document all my steps. After rooting, I downgraded to 5.3.1 and verified 2 roms worked (Fire Nexus and CM Fire.)
My apologies for not providing more accurate details, its just an overview.
TechDad378 said:
This is just a quick overview for testing purposes. As always, there is an extreme chance of the undesired "Bricked Device". You are warned...
1. Make sure adb and fastboot drivers are enabled and working to the 5th gen Fire. Extremely important.
2. Once connection is working follow the "Super Tool" setup directions.
3. Disable ota, disable ads and install GPlay. Somethings can only be done after root.
4. Once you have Gplay setup, use Super Tool to install KingRoot.
5. When you first run KingRoot, it will advertise "Purify Battery Saver" install it.
6. Afterwards run KingRoot. It will reboot 3-5 times before applying root. This process of rooting consumed over an hour and may need to be restarted if KingRoot fails.
7. Please keep in mind it is just an overview in order to determine the steps correctly.
If necessary I will start from square one and document all my steps. After rooting, I downgraded to 5.3.1 and verified 2 roms worked (Fire Nexus and CM Fire.)
My apologies for not providing more accurate details, its just an overview.
Click to expand...
Click to collapse
Are you sure it was 5.3.2.1 you where on ? I only ask because downgrading to 5.3.1 from 5.3.2.1 should result in a brick as the boot loader used in 5.3.1 and 5.3.2 changed from on 5.3.2.1 and the anti-roll back measure amazon have should have kicked in to give you a brick.
How did you roll back ? Through ADB or placing the update file in the internal SD ?
Correct it was 5.3.2.1. While playing around with it I hit a black screen while booting. Upon reading some posts, I thought there was no return because of the version. Since the device responded via usb on pc, adb sideload worked causing downgrade to work.
Don't get me wrong this may have been just pure random luck. But hopefully my results my lead to "Fire Lineage OS".
No luck with this method. Will keep trying.
Zero Luck yet as well. Will try again. Hopefully something more reliable will come about soon.
Sorry to hear you have had no success. Will revert everything back and document each step. Once the method has been identified as successful, the information will be provided.
You still need to provide us with one of the most important tips, what version of kingroot you are using.
Thank you
TechDad378 said:
... But hopefully my results my lead to "Fire Lineage OS".
Click to expand...
Click to collapse
Quick side note: No LineageOS for this pup while the bootloader remains locked. LineageOS begins with Android 6 (Marshmallow); the current suite of Android 5 (Lollipop) ROMs is all we'll see due to FireOS 5 kernel restrictions. Unless Amazon releases and back ports FireOS 6 to older devices. Highly unlikely IMHO ... economics don't square.
If someone succeeds, could they try to post the kmPlugins.zip from their downloads folder? If we can get that from a successful root, then we could probably skip all the repeated failures and just get KingRoot to use that method immediately.
What ever happened to the guy that had rooted it? I knew he was bs.
Geek Surfer said:
What ever happened to the guy that had rooted it? I knew he was bs.
Click to expand...
Click to collapse
Hmm...
Interesting response.
With a full time job and a family, this is a hobby I do for fun in my spare time. Most mods are done with patience and diligence.
Recommending following command,
C:/yourself/ adb sideload patience.zip
---------- Post added at 03:20 AM ---------- Previous post was at 03:09 AM ----------
Davey126 said:
Quick side note: No LineageOS for this pup while the bootloader remains locked. LineageOS begins with Android 6 (Marshmallow); the current suite of Android 5 (Lollipop) ROMs is all we'll see due to FireOS 5 kernel restrictions. Unless Amazon releases and back ports FireOS 6 to older devices. Highly unlikely IMHO ... economics don't square.
Click to expand...
Click to collapse
Point taken. Just hoping LineageOS will be as widespread.
As for the root, I reverted back to original. Trying to recreate the environment which allowed success.
Geek Surfer said:
What ever happened to the guy that had rooted it? I knew he was bs.
Click to expand...
Click to collapse
Nice. If you bothered to read his post history you might think differently. Well presented/documented with all the appropriate caveats.
Geek Surfer said:
What ever happened to the guy that had rooted it? I knew he was bs.
Click to expand...
Click to collapse
What a shame that people can't be considerate online anymore.
@TechDad378 Could you verify what supertool version you are using . I'm trying to figure what version of gapps got installed, and can you recall if you installed any apps from playstore like chrome ?
I don't have a tablet with 5.3.2.1 but it occoured to me that kingroot may have found a backdoor to root in playstore or another installed app. I've tested on a tablet with previously unrootable 5.1.4 and the difference in root behaviour pre/post play store installion is very noticable. The tablet reboots several time during root with playstore installed , it only rebooted once without it installed.
Ive not managed to root it yet but kingroot now stuck on verifing root status, it previouly detected it as unrooted, something has changed
My router is blocking OTA so going keep playing with this
5.1.4 Rooted !!!!!
Mr McBoatface said:
@TechDad378 Could you verify what supertool version you are using . I'm trying to figure what version of gapps got installed, and can you recall if you installed any apps from playstore like chrome ?
I don't have a tablet with 5.3.2.1 but it occoured to me that kingroot may have found a backdoor to root in playstore or another installed app. I've tested on a tablet with previously unrootable 5.1.4 and the difference in root behaviour pre/post play store installion is very noticable. The tablet reboots several time during root with playstore installed , it only rebooted once without it installed.
Ive not managed to root it yet but kingroot now stuck on verifing root status, it previouly detected it as unrooted, something has changed
My router is blocking OTA so going keep playing with this
Click to expand...
Click to collapse
Well it may not be the news most visiting this thread are looking for but I've rooted the previously unrootable 5.1.4 !!!!
I played around with various play store installations as suggested in my post above looking for a back door to root. 3 hours and got no where. Decided to downgrade to 5.1.2 and use supertools to root it the tablet. For the life of my I couldn't root this rootable OS..... six attempts failed each with multipul reboots. Then I read up a bit more and use kingroot 4.8.2 as suggested in this thread - https://forum.xda-developers.com/amazon-fire/general/flashing-kindle-5-1-2-using-kingroot-t3346300. This time 5.1.2 Rooted first time one reboot using Kingroot. I had always thought the Kingroot edition used didn't really matter that the files it used came from the online database. This result put that assumption into doubt.
Decided to go back to 5.1.4 and retry using the kingroot as above....... Didn't work. Not being someone who gives up easy i tried the impressively long-named "NewKingrootV5.0.1_C165_B377_xda_release_protected_2016_12_22_20161222120332_105243_signed.apk" from here https://forum.xda-developers.com/devdb/project/?id=9793#downloads
Rooted first time !!! It did reboot a few times, I had to manually restart the root process each time it rebooted but it picked off at the % point where it rebooted.
Moral of the story never give up and try some kingroot versions from the xda links above
Going to reset the device and confirm it's repeatable.
Mr McBoatface said:
Well it may not be the news most visiting this thread are looking for but I've rooted the previously unrootable 5.1.4 !!!!
I played around with various play store installations as suggested in my post above looking for a back door to root. 3 hours and got no where. Decided to downgrade to 5.1.2 and use supertools to root it the tablet. For the life of my I couldn't root this rootable OS..... six attempts failed each with multipul reboots. Then I read up a bit more and use kingroot 4.8.2 as suggested in this thread - https://forum.xda-developers.com/amazon-fire/general/flashing-kindle-5-1-2-using-kingroot-t3346300. This time 5.1.2 Rooted first time one reboot using Kingroot. I had always thought the Kingroot edition used didn't really matter that the files it used came from the online database. This result put that assumption into doubt.
Decided to go back to 5.1.4 and retry using the kingroot as above....... Didn't work. Not being someone who gives up easy i tried the impressively long-named "NewKingrootV5.0.1_C165_B377_xda_release_protected_2016_12_22_20161222120332_105243_signed.apk" from here https://forum.xda-developers.com/devdb/project/?id=9793#downloads
Rooted first time !!! It did reboot a few times, I had to manually restart the root process each time it rebooted but it picked off at the % point where it rebooted.
Moral of the story never give up and try some kingroot versions from the xda links above
Going to reset the device and confirm it's repeatable.
Click to expand...
Click to collapse
Nice! While you can downgrade 5.1.4, this mean it may be possible to root without using a PC to downgrade first. I'm going to try on 5.3.2.1, and see how it works.
Sent from my Amazon Fire using XDA Labs
Repeated root on 5.1.4, replace the kingroot in supertools with the "NewKingrootV5.0.1_C165_B377_xda_release_protected _2016_12_22_20161222120332_105243_signed.apk" version and ran the script.
It needed 2 attempts this time but it rooted. The supertools script removed it and replaced with supersu.
See attached video in zip to confirm
I've really reached the end of the road here and I don't know anything else to do other than throw the phone in the bin. I bought an X Play XT1562 in the UK last year and I made the stupid, stupid mistake of flashing LineageOS on to it.
I followed all of the instructions to the letter, did all the necessary android upgrades, unlocked the bootloader, rooted it e.t.c... and it worked fine.
When it came time to restore it to a stock rom, I found out that I couldn't downgrade it and return it to stock due to LineageOS being a newer version of Android - either that or something to do with the bootloader. I've spent so long trying to rectify this situation, my memory is starting to get a bit fuzzy !
Anyway, I eventually found this thread with instructions on how to use ADB to flash the UK stock rom. I got errors on the partition flashing but I read somewhere else that you needed to keep going and enter all of the commands, which i did.
The phone did reboot and it did appear to be returned to stock, but when I went to check if it was still rooted, Super Su kept giving me the error "root access is not properly installed in this device".
And I simply cannot correct this, no matter what I try. I've tried flashing different versions of TWRP, re-rooting it with different versions of Super Su and even King Root and then using Super Su to remove root.
I've even tried re-rooting it and flashing the @osm0sis unSU script which flashes in TWRP and says it's removed root, but when i reboot and re-run Super Su, it still gives me "root access is not properly installed in this device". It's almost like it's burnt in to the rom of the phone at this rate.
If i can't remove this or correct it, the phone is as good as junk to me because I can't sell it otherwise so i'm really hoping someone has an idea or suggestion as to what might correct this situation.. thankyou if you can help.
That's the message SuperSU gives you when it's unrooted. Uninstall SuperSU again (or flash unSU again since it'll do that too), `fastboot format userdata` and you're done.
Thanks for the reply. Funnily enough I'm just waiting for the phone to boot up at the moment and optimise the apps after running your script so i'll try what you've suggested.
I was told in the second hand shop i tried to initially sell the phone in that when they run root checker, it shouldn't come up with any message regarding root, so if i can just get to that point then i can sell the damn thing.
It didn't work. The phone booted up and i ran root checker and still got the error "root access is not properly installed in this device".
I rebooted to TWRP and re-flashed it. I then rebooted back to the bootloader to try the erase userdata command but i kept getting an error saying something about it couldn't erase the date on a filesystem marked as "raw". I thenk rebooted the phone again and ran rootchecker again and it still gave me the error.
I used super su to unroot after that, rebooted and still got the error.
That all said, I've found another second hand shop that will take the phone as long as it works - the root error won't be an issue. as long as the phone is ok with receiving OTA updates (which it is, as i'm doing them at the moment) and is properly unlocked (which i'll test shortly) then I can sell it for some much needed money.
I've really run out of patience, energy and enthusiasm to try and fix this issue now so i'll take it to the other shop tomorrow. I just wish i'd never flashed LineageOS on it - i would have easily been able to return it to unrooted stock if i hadn't.
Try searching for any su folder in general. Due to systemless root, root goes away after a reset. I am guessing you flashed a version which was not systemless on MM and that caused the **** up. Why don't you try flashing the custom ROM and be happy with it ? The stock ROM are bloated and crap anyway. If you are planning to give your phone for updating/repair, it's futile anyway. Upgrade your phone to N or use other custom ROMs.
If you are still hell bent on getting rid of those files, root the phone using magisk and rule out any su files that you can find.
Sent from my SM-J730GM using Tapatalk