I downloaded the z4root app and started it. I started the install for permanent root. It appeared that everything started up fine, a screen came up stating that it was "running exploit in order to obtain root access..." this ran for approximately 10 minutes then stopped processing. The phone is now stuck on the Blue z4mod screen showing no activity. The little circular icon has stopped moving.
I have not done anything to the phone to disturb it, but......
Is it locked up? Should I pull the battery and reset? Not sure, this is my first Droid (Blackberry before).
Some help ASAP to get the phone going again would be greatly appreciated.
Thanks
Use z4root 1.1.0 instead and it will work immediately. Some bug in newer version causes it to hang like that.
Hey, thanks for the reply. I actually pulled the battery and it reset itself.
I then tried the temporary root and it worked, but...
It said there was a new version of the su binary available. Press ok to attempt to install it automatically. When I pressed ok the message came up
An error occurred and the su was not updated. A zip file (su-2.3.1-bin-signed.zip has been placed on your SDcard, please reboot into recovery mode and flash it to update your su binary.
?
How do I reboot into the recovery mode?
Thanks
Related
I tried out rooting my phone earlier today, and it was working fine, I then got the TW4 launcher, installed that and then it showed me as stuck on my contacts screen and I couldn't get off, I rebooted my phone and now I'm stuck on the galaxy s plus boot logo, but the phone is actually on in the background because I can hear it getting texts, what do I do to fix this? I'm a complete android noob and have no clue what to do now and because I've rooted it I've voided the warranty, help would be greatly appreciated!
I had exactly the same thing (4 times lol) because of TW4manager and I don't think we are the only
I just reflash the rom but you lose all your data
http://forum.xda-developers.com/showthread.php?t=1297400
Same problem.
Solution is flash new rom with odin.
Next time use this TW4 luncher, it works
http://forum.xda-developers.com/showpost.php?p=13435895&postcount=21
It seems to me there IS another way to fix this. However, I was stupid enough to make it impossible to try in my case.
If your device is rooted (has su), and has USB debugging enabled already, you may try to do the following:
pcuser$ adb shell
$ su
At this point, if you have the confirmation dialog appearing, that dialog will appear and "stop" the boot animation. You will be able to use the contacts app and the notification area...
Then, with adb, you should be able to uninstall TWManager and install the newer version. The notification area should show that a new app has been installed and you should be able to start it from there (and update the TW to a workable version).
However, I clicked Deny on the su prompt, the checkbox was checked and now I can't get su in the shell...
Could someone test this and post back results?
thank you for the replies! I flashed another rom and it fixed it and because it's on 2.3.5 now I have no battery issuses.
I seen this subject discussed but never really saw a answer, seems like everyone resorted to re installing firmware which I would like to avoid if I can.......
so, Ran into some trouble today trying to trying to do the 3e recovery mod today and had to reinstall stock firmware (using odin and gtg). Got root access and was up and running. I went to updates just to see if anything was there and a update started and completed. the phone rebooted and was on the white and red update screen for about 4 secs and the phone rebooted again. When it Got back to the home screen and got a message saying the update had failed. since then device management will not stop popping up. it stays in the task bar and if you use any process that needs it, the failed update screen pops up again and DM crashes and restarts itself. the message in the taskbar says "connecting to DM server" like its trying to get a update. how can I stop this without resetting the phone?
loulou704 said:
I seen this subject discussed but never really saw a answer, seems like everyone resorted to re installing firmware which I would like to avoid if I can.......
so, Ran into some trouble today trying to trying to do the 3e recovery mod today and had to reinstall stock firmware (using odin and gtg). Got root access and was up and running. I went to updates just to see if anything was there and a update started and completed. the phone rebooted and was on the white and red update screen for about 4 secs and the phone rebooted again. When it Got back to the home screen and got a message saying the update had failed. since then device management will not stop popping up. it stays in the task bar and if you use any process that needs it, the failed update screen pops up again and DM crashes and restarts itself. the message in the taskbar says "connecting to DM server" like its trying to get a update. how can I stop this without resetting the phone?
Click to expand...
Click to collapse
it shouldn't be a prob after you flash a new rom on it.
If it really bugs you, you can try freezing it or remove the update manager pak with TiBu
Hello there. I'm a noob and now I'm stuck in the web of the consequences of my sudden stupidity.I have been trying to update my AT&T HTC One X for the last 4 days. I had already unlocked the bootloader and installed the Supersu through the TWRP. but when I was trying to install the rom it wrote failed and I had two variants. Go back or press reboot. So I touched the reboot button and discovered that I had to install all the stuff I once had again, I noticed that I wasn't asked to connect to a wifi. so I carried on after checkin once again. Then I opened my settings through the status bar and it was written "Error" under the Wifi switch and I couldn't use any downloaded applications, they turned up to be not responding as soon as I opened them. I booted into recovery mode once more and tried to restore my backup through the TWRP.But it didn't show any files.. PLEASE help!
Hi!
So, I was perusing my phone when super user popped up and asked me to update my su binary, so I said yes, then it asked me to do it manually or automatically with TWRP or CWM, well, I have CWM installed on my phone, so I hit the automatic button.
The phone reset and rebooted into recovery, only the screen started just flashing a picture of the recovery android, and the phone is completely unresponsive, I have tried resetting the phone with the buttons, and by taking out the battery but it just goes back to automatic recovery which isn't working. I have also tried to access it through my computer but it isn't showing up even when connected to USB.
Has my phone bricked? I am pretty worried, what can I do?
I tried to drain the battery as well, which didn't work.
Thanks so much.
Hi. My S6 has been running great for a while. It's running CleanROM. I got a notification that there is an update to SuperSU. I chose to update it normally because there's no recovery since the bootloader is locked. During the upgrade, I got a message saying that Knox was detected and if I wanted to disable it (temporarily?). I chose Never not thinking about the implications. The phone rebooted as part of the upgrade but now it is stuck in a bootloop. It does boot up for a very short time. Enough time for me to draw my security pattern and for some apps to load, but then the phone reboots. Any idea what's going on? Any suggestions on recovering from this? Thanks.
UPDATE: Somehow I recovered. I was able to power down the S6 because I had that small window to do so. I booted to Safe Mode and disabled SuperSU. I rebooted normally and everything was ok except SuperSU was disabled. I uninstalled SuperSU Pro and then uninstalled all updates for SuperSU. Play Store wouldn't let me totally uninstall it. I updated SuperSU. This is where it gets a little foggy. I think I re-enabled SuperSU and then it said that Knox was detected and whether to try to disable it or never disable it. This time I chose to disable Knox. SuperSU tried to disable Knox but got stuck with the spinning arrow. It was strange because I was able to go to Settings, but when I went to Apps or Logs, I got a continuous spinning arrow. It seemed to do what was needed though because my root checker verified I was rooted again. I rebooted again and ran SuperSU again. It gave me the Knox detected message again. This time I said Never disable. Rebooted one more time, ran SuperSU and no more message. Last step was to reinstall SuperSU Pro. I am not sure exactly if I had to do all these steps and what exactly was going on, but I think I am back to normal running SuperSU Pro v2.79.