I'm coming from the Hero as well. I don't care if the root ends up being 1-click or if I have to do everything through adb and transferring files again.
I'm coming from the Hero as well. I don't care if the root ends up being 1-click or if I have to do everything through adb and transferring files again.
I hope at first it's really involved. More fun that way.
Also probably a soon-to-be shift user (from HeroC), if things play out right.
I'm coming from the Hero as well. I don't care if the root ends up being 1-click or if I have to do everything through adb and transferring files again.
Is there actual confirmation that somebody is actually trying to perm root this thing. Has the unrevoked team said anything?
I don't think entering a bunch of code or doing a bunch of steps is difficult or any better or worse thana 1 click method. The reason I don't want to do something like the temp rooting is because there are some people who say it isn't working and others who say it is even when doing the exact same steps. I don't like reports like that. Having a perm root be involved is fine by me as long as it is a 100% success rate if done correctly. I don't want to hope it works even when done correctly so i will gladly wait.
The ONLY reason (that I'm aware of) that people are saying it doesn't work is because the temp root process isn't 100% successful... and when it fails, people chicken out and don't try again because they are scared of damaging something. Why? I don't know... we have the official RUU folks!
After a reboot, if I try to attempt to apply temp root again and the shell seems to restart (shows the "4G" logo), I know that the process failed. I can yank the battery or "adb reboot" and try again. For me, if temp rooting fails the first time, it has ALWAYS worked the second time.
I had problems getting it to temp root until I checked the option "run vision.sh after root"
After that no issues.
Sent from my PG06100 using Tapatalk
The problem with that is, if you just click delete it comes back after a restart, where if you do the long click method it's removed completely.
Compusmurf try putting it in airplane mode before you temp root. That's the only way z4 works for me
Sent from my PG06100 using XDA App
I receive the following message after allowing Superuser and receiving confirmation of root (#)
# cannot create kmsg_shift.log: read-only file system
I'm on my way to get a root canal, so I will try later and check to see if anything has changed on here.
Thanks for checking this out for us.
Update: tried hitting enter on the HW keyboard instead of the soft and was able to generate the log. E-mail sent.