-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pixel C and RCM-mode #27
Comments
Just because you got into rcm doesn't mean it's susceptible to the exploit |
There isn't much point on a phone anyway if it has a unlocked bootloader |
Yes it is, as stated by the author here #22 and in the original article; makes actually a lot of sense also to me, since the chipset is the same of the Nintendo Switch, i.e. Tegra X1.
Yes there is, because Pixel C is susceptible to a brick situation: even with unlocked bootloader you can't flash anything unless you set a specific NVM flag; this operation cannot be done without a working recovery (you need to run it using adb shell |
I stand corrected, I didn't realize there was a bricking issue with the C, I apologize |
To enter RCM on pixel c i did the soft reset sequence (poking some registers to reboot into rcm), instead of using hardware button combo. Maybe there is a hardware button combo but I don't know it. |
Thank you very much for the answer. I am afraid that's the recovery mode (using Android terminology). I have a situation where I am unable to boot or flash any recovery: that's why I hoped to use your exploit from the fastboot mode. |
You might have to open the device |
I got the exploit is working (by definition probably) on Pixel C too #22.
Could I ask how to put the Pixel C on RCM-equivalent mode? Is it simply the fastboot mode?
Excuse my stupid question, but I cannot find anything on README or on the original article.
The text was updated successfully, but these errors were encountered: