C:\android-sdk-windows\tools>adb devices List of devices attached HT9C1HF03306 device C:\android-sdk-windows\tools>adb remount remount failed: Operation not permitted C:\android-sdk-windows\tools>adb shell $ su su #
- Flashed the 1.5 RUU that Flipz has had out for months. No errors
- Ran the Avalaunch PRI fix to get rid of the flipz_01 PRI name
- updated my profile
- updated my PRL (which is now 65000??)
- rooted through the normal sequence without error, I can boot to the recovery just fine, but when I adb shell into the phone I end up at $ instead of #. I have to su to get to # and at the c:\windows-sdk-windows\tools\adb remount fails with "remount failed: operation not permitted"
Is it possible that the PRI update has foiled the root exploit? I even restored a nand backup that I know had a working root and I still have the same results. This is too weird.
Anyone else have this issue? I searched the forum but I came up empty.