Unable to remove root verification on Chrome OS v70 #10
Comments
|
Yes, the rootfs verification check in the script got broken due to a change in Chrome OS. The RootandSEpatch.sh script has just been updated with a fix - if you try it again now, it should work this time. |
chronos@localhost / $ curl -Ls https://raw.githubusercontent.com/nolirium/aroc/onescript/RootandSEpatch.sh | sudo sh |
|
Should be fixed now. |
cheers, so I did that and it still didnt work the chromebook running chromeos v70 is still unrooted for some reason even after doing this. |
|
Did you happen to notice if there were any error messages in the script's output? Are Android apps working now (but no root), or not loading at all, or ...? |
normal android apps that require no root work fine, everything is still working just fine as normal but everything that requires root and any root checks come up as device unrooted still, and there were no error messages but I can do it again now and screenshot the logs for you |
|
Got an error |
|
Yeah, that'll happen if for example you try to run the script twice over without rebooting between times. It's expected, in that case. Try rebooting again, and if still working and unrooted, can you paste the following into the Chrome OS shell and see if anything comes up: |
|
I ran the script the first time then I rebooted and it wasnt rooted so I went in shell and tried again so I can check if there were any errors for you and thats the error that I got :) But I did reboot right away the first time I ran the script |
infinite loading on apps now wont seem to work anymore |
|
OK well, give it a couple of minutes (it takes some time after the first reboot), and then if apps are still not loading, the command to restore the unrooted Android container is If you paste that into the Chrome OS shell and then reboot, you should have the normal unrooted Android system back. I may not be able to respond back until tomorrow now, but if you do end up unrooting and running the script again, it might be useful if you could copy the script's output to text (or screengrab), so we could check if there were any errors running the script. |
|
I keep getting ERROR: No running Android system found. Unable to patch sepolicy. thats the only error |
|
|
|
But everything else (file copying etc) looks like it worked OK. Hmm... If you do
does it get you into an Android shell like it's supposed to? (you would see the prompt change from "chronos@localhost: " to "something_cheets:") Or does it just give an error message? |
|
it takes me to edgar_sheets:/ |
|
OK that's good. Now, at the edgar_cheets prompt, can you put in |
|
|
|
So daemonsu isn't running. Can you try to start it (see if it is present)? Again in the edgar_cheets prompt, do
|
|
|
|
Try a root app now - see if it asks for permission. |
|
opening root checkers and supersu and theyre all still saying that device is unrooted, should I try to reboot and then check? |
|
|
|
Something's not right, clearly. Maybe we should try to patch the SE Linux policy file manually, to rule out SE Linux being the problem (since one of your screenshots showed the rooting script erroring out at the point, right near the end where it's supposed to patch the sepolicy file). Here's a script which is just the SE Linux policy patching part. (you can run it in the Chrome OS shell) |
|
|
|
Maybe you could double check the contents of /system/xbin in Android: Also in the Android shell (the edgar_cheets prompt), could you do
(It should say "2.82:SUPERSU") And also at the edgar_cheets prompt, if you just do
and see if you get an error there or if the edgar_cheets prompt changes at all (if any number shows up). |
|
Would turning this on make a difference? Just wondering. |
|
update on your last comment btw |
It shouldn't do any harm, but unless something has changed very recently, it shouldn't affect Android either way. |
|
would turning that on fix our issue or what do you recommend? |
At the moment we don't know what the exact cause of the issue is, but turning on Linux apps is unlikely to affect it. Feel free to try it though, it shouldn't do any harm...
So, it looks like the files for SuperSU are all present and correct. The "1|edgar_cheets" that appears at the front of your last command indicates an error, but at least Android is booting and the files appear to be in the right place. I'm going to go look through some of the comments from my blog, as I remember some people had similar problems a while ago, with various causes (and resolutions). I'm thinking perhaps the modification to init.rc is at fault, but perhaps it's something else entirely. One last easy thing that comes to mind to maybe try is to disable enforcing SELinux completely (then reboot).
|
|
|
|
Oh, forgot to mention that you'll need to |
|
sweet dude it's working now we got it done!! 👍 |
|
Good stuff! Glad we could get it sorted. I'll still have to try and work out out why it wasn't working initially. Possibly the script still needs tweaking somewhat. For the moment though, it might be helpful towards figuring out the initial cause if you could do one more thing now, which is to redo the SE Linux patching command mini script in the Chrome OS shell, and see if it succeeds this time : (If it tells you to reboot, just ignore that). |
|
OK just an update before I do what you told me to do, after I took the screenshot that I showed u I rebooted and now that I'm back on it it seems like apps aren't opening anymore it's just an infinite loading loop |
|
Just ran the script that u sent me btw |
Well, that appears to have worked, which is something. Did the previous command stick? If you type into the Chrome OS shell, does it show 'Permissive' or 'Enforcing'? How are you rebooting, by the way? I mean, are you just typing |
|
I reboot by pressing the power button + the spin button on my keyboard and I did what u told me ran the command it says permissive |
|
When you say the spin button, do you mean the 'refresh' key (F3)? If so... Don't do that. Just use the power button (or type Pressing the power and refresh keys both together can potentially do a hard reset if you keep them held down for too long, which can really mess things up if you've just made some changes, as the system will completely 'forget' the changes. |
|
I didn't hold it down for too long though I only pressed them twice together once and it restarts, what should I do now though? because when I do reboot in a root shell it says command not found |
|
after checking im pretty sure power button + refresh key is fine btw Im only clicking it for a millisecond |
Yeah, it was probably fine then - you would have had to have been holding them down for a moment to hard reset, and IIRC the screen normally flashes white briefly, so you'd have probably noticed. But there's no need to press the refresh button anyway, so...
Were you doing it in a root shell, or as chronos@localhost, though? Just to clarify, within the Chrome OS shell terminal: This is the Chrome OS regular user shell prompt: This is the Chrome OS root user shell prompt: (If you try to run a command and you get a permission error, or if it says command not found, sometimes it's because you're in the shell as a regular user (in this case, chronos). If so, you can change to root with Apologies if this is all stating the obvious. Anyway... Are you still in the same situation? Have you rebooted (either way) since you ran the last script? |
|
yup still having the same issue guess its time to reset and start over.. god. |
|
did a powerwash and now I cant get playstore working again it's getting really annoying, even though I ran the command to restore the unrooted android container |
So Android isn't loading at all after a powerwash? What is happening, just the loading graphic constantly spinning?
just to see if it is looping or frozen (normally it's constantly updating). You could also try double checking that the restore command worked (by listing the files in /opt/google/containers/android)
The nuclear option would be to either switch release channel, or do a restore with the Recovery Utility. Recovery should pretty much always work, as it'll download the whole OS again, and the release channel change usually works (but in certain situations can fail). A powerwash only deletes user files, mainly. |
|
google services just wont work anymore for some reason I attached 2 pictures of how the playstore is behaving, if I close it and try to reopen it, it simply doesnt open and goes into infinite loop |
|
Should I try going into the dev channel? |
|
In your first image there, you are trying to run the command
That should work, but first you could maybe just try toggling between Enforcing and Permissive SELinux again, then rebooting. Again in a root Chrome OS shell, If you do
|
|
alright give me a bit I'll get it sorted now I'll go into dev channel then back to stable that should work and then when google services work again I'll go through all the steps again to root it okay? I'll keep you updated |
Seems like a good plan. Although, without wanting to add a whole other layer of potential confusion, I should also just mention in case you weren't aware that Chrome OS uses an A/B partition system for updates, i.e. lets say you start off on partition 3, the next update sets a kernel flag so you will be using partition 5 after rebooting, and after the next update on partition 3, and so on. They do this so they can apply updates smoothly, and in normal use for the most part it works fine, but occasionally it can lead to messed up/confusing situations when removing root verification/modifying system files & rebooting. Going stable>dev>stable should be fine, but I thought I'd mention the A/B partition system just in case. |
|
ok man its all good now I went stable>dev>stable and then ran the rootandsepatch script rebooted and it just worked this time didnt have to do anything else, and also about the A/B partition how will this affect me in the future? and is there anyway I can just make it go back to normal or something |
|
I'm too scared to restart or turn off my chromebook now btw. lol :D |
Good. That's how it's supposed to work.
Oh, it is normal, it's how they've designed the update system. It most likely won't affect you ever unless if, for instance, you were running the rooting script while you had an update waiting, or maybe you are hacking around on the OS, changing other stuff around, then e.g. you change channel a few times real quickly. Even in that case, all that would likely happen would you'd need to re-do the thing you changed (it's just that if it does happen, it can be completely confusing at the time).
haha, yeah I can understand that after all of this. Although if you reboot it once, and everything still works, then at least you'll know it'll be OK from there on. Normally once it works, that's it, everything's fine (until the next major Chrome OS update, anyway). |
|
when i do sudo android-sh |
I would like some help because I am unable to remove root verification on this version, when I run the command: sudo /usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification --partitions$(( $ (rootdev -s | sed -r 's/.*(.)$/\1/') - 1)) everythings appears to be okay but when I restart my chromebook and try to run RootandSEpatch.sh I get the error "Error!
Unable to modify system!
In order to modify system files, the Chrome OS system partition needs to have been mounted writeable (i.e. rootfs verification disabled)."
I would like some help with this please.
The text was updated successfully, but these errors were encountered: