Previous Fields

mbroeders's Activity

Paul, Lenny, I thought SuperSu had to be altered in order to work with Switch, right? If so, could the automatic updating of SuperSu (which I believe is enabled by default) be the cause of some of the problems that are reported? Just thinking...

I was not suggesting you are an idiot and i do read your posts. I gave you an answer to your question: what does the adb command do (it removes the S-on package script). Anyway, I was just trying to help. With the permission denied issue: in linux you could start adb as root (adb kill-server, sudo adb start-server), in windows I don't exactly know. Make sure you have enabled USB debugging in developer options. But seeing as you're being quite rude, I will let others try to help you.

Edit: honestly, i don't know why i even bother, but make sure you are in recovery mode when trying these commands. And maybe you have to mount data (using recovery) for it to work, but I'm not sure as I'm not working on a windows machine.

If you have already flashed everything, including the S-on package, and you would like to avoid switching via recovery, then you can flash the update Paul provided, but you will need to do the adb command to remove the S-on package.

Yes, indeed. I believe that would be the fastest way. I backed everything up using Titanium Backup and restored my apps with their data after a full wipe. Everything working now as it should. Good luck!

I'm not really sure what you're asking, but I think you want to install the latest Switch and I assume that you are S-on. Then you have 2 options:
1) Perform a factory reset (full wipe), flash beta 12, then beta 13, root package (if you want root), and then the update.zip from this post: http://www.modaco.co...20#entry2155136 (This will simulate S-off and bypass recovery when switching).

Paul, so far no reboots, fastboot keeps disabled. Only thing I've noticed so far is the pertaining message that an update is available (beta 12), while my rom version is Beta13 (2sep 2013 19:00:00). But I guess I can disable that message, so no biggie :) Thanks for the fast updates!

Okay, so this is the first time for me using pastebin, hope it's ok :)

Wiped, installed beta 12 and s-on package. In Sense disabled fastboot and enables wifi, that's all. Rebooted into GPe, enabled Wifi and set up my google account. Then booted back into Sense, and back to GPe. I was able to boot into Gpe, but I kept getting an error message saying com.android.phone stopped working, see: http://pastebin.com/sPsf2AHj
Next, I booted back into Sense, that didn't work: http://pastebin.com/n393mxXX

Hope this helps! It's different than what I experienced last time, don't know why. Will try to recreate that as well. Tnx.

- full wipe, install beta 12 and S-on package
- booted into sense, skipped the setup (except for Wifi). Disabled fastboot and booted into GPe.
- in GPe I waited for the welcome screen. During setup I turned on Wifi and setup my Google account. Then I booted back into Sense
- in Sense I turned on Wifi and disabled fastboot again. Google account was syncing, but I disabled Magazines and Movies because those are not available in Holland. Then I booted back into GPe.
- Bootloop, I see the pin screen and 1 second later the phone reboots.

Those were the exact steps I took. Note that my device is S-on with radio version: 4A.17.3250.14_10.39.1150.04L
Right now I don't know what else to do or try.