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.
Related
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
I got the device two days ago and rooted it the night I got it but remained stock to get use to it a little (came from MT4G) and still not use to the lack of physical menu buttons.
Anyways, after rooting and going through the process CWM, SU, ect. everything looked good for a while but today I had two random reboots from locked screen (went to unlock the device and it rebooted, the same way both times but not full reboots they were short and quick) and I was wondering if anyone else had this same issue and if so how to correct it.
There was another thing, when I boot into recovery it loads fine but when I reboot back to ROM it says there was an improper boot and wanted to send crash log to HTC. Not sure if this is going to be the normal thing but if anyone else is having this every time they go into recovery is there a way to opt out of it by default?
Thanks for reading.....
Orical said:
I got the device two days ago and rooted it the night I got it but remained stock to get use to it a little (came from MT4G) and still not use to the lack of physical menu buttons.
Anyways, after rooting and going through the process CWM, SU, ect. everything looked good for a while but today I had two random reboots from locked screen (went to unlock the device and it rebooted, the same way both times but not full reboots they were short and quick) and I was wondering if anyone else had this same issue and if so how to correct it.
There was another thing, when I boot into recovery it loads fine but when I reboot back to ROM it says there was an improper boot and wanted to send crash log to HTC. Not sure if this is going to be the normal thing but if anyone else is having this every time they go into recovery is there a way to opt out of it by default?
Thanks for reading.....
Click to expand...
Click to collapse
If you boot into recovery or hard reset by holding the power button. It will always ask to send crash report
OK cool so it's normal, thanks for the information.
Where to start...
First, as a disclaimer, I may use language or terms that sound noobish. I have rooted and run custom ROMs on several devices in the past, however generally when I get a ROM I like I stick with it, so I'm not constantly tinkering. I've done my best to search and find solutions so please go easy on me.
17 days ago I was running stock 4.3 on my SGNII when the battery died. Upon charging I found I was stuck in bootloop and had a bad /efs mount. I searched and searched and spent around 15 hours trying this and that but to no avail. I finally threw my hands in the air and got ahold of Josh at mobiletechvideos and he was able to fix the efs mount issue. However, he left me in factory mode which required me to root to get out of, and once I did this I was unable to activate data on my carrier (Ting). I was so happy to have my phone "back" though that I used it like this for 4 or 5 days. I could get on wifi and I could call and send text messages. I had been off the grid so this felt like something I'd fix fully later.
Well I kept reading and found "fix" after "fix", flashed this and that and still no dice. FINALLY, last night, I found this thread: http://forum.xda-developers.com/showthread.php?t=2086769 which helped immensely. I was able to get TWRP flashed by unchecking the "auto-reboot" option in Odin and pulling the battery after the update took, and via TWRP I was able to install the ROM. I booted up, the device activated, I was running 4.1.2, I made and received some calls, the birds were chirping, the air was sweet...
I had struggled for so long and I had finally achieved success! Then, for seemingly no reason at all, I accepted an OTA update which bricked my Note2. Devastation.
The current state of things...
* Cannot get past the initial "Samsung Galaxy Note 2" screen
* Cannot boot into recovery
* I CAN get into dl mode,
* but, I CANNOT successfully flash anything. TWRP will flash like it took, but upon reboot I'm not able to boot into it. I'm also able to flash a ROM but it fails when it gets to sbin, and upon rebooting I'm greeted by the screen "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I try to use Kies it doesn't find the device. I've installed all of the most recent drivers and I'm running Kies as administrator. I select Tools > Emergency Firmware Recovery, THEN connect my device as instructed.
I'm at the apex of frustration. I beg thee to help!!
I updated to PA 5.1 when I got the notification and now I am stuck in a boot loop. My device is unrecognized when plugging into my computer, even when using ADB. I'm looking for a way to save my data (pictures, videos, apps, etc) while restoring my phone.
After awhile, I don't know what happened, but I tried backing up my files through TWRP and my phone booted up with everything wiped. I got a notification saying superuser needed to be downloaded (even though I had it downloaded it before) and went through the steps, now I'm stuck in the boot loop again. At this point I just want to get my phone up and running again as I think my data is all gone...
Someone said that I may have a big issue as when I open up cmd and run "adb devices" nothing shows up, any help is appreciated thanks in advanced!
Also, I do not mind a fresh wipe if necessary.
P.S. I'm a total noob with this stuff so yeah...I may need the simple stuff explained as well lol
Hi all,
I have a Verizon Xperia Z2 tablet (SGP561) that had been a Verizon store demo (fully functional). I rooted it with KingRoot to get all the Verizon crap off (I only use it as WiFi anyway), upgraded it to stock Android 5.1.1, used Super-Sume to get rid of KingRoot and set it up with my apps. I used this guide to make sure it went according to plan: https://forum.xda-developers.com/xp...z2-tablet-models-regions-5-t3415832?nocache=1
Everything was fine until I put an SD card in and installed Apps2SD. I don't know if either of those are the cause or that's just a coincidence.
Since then, the farthest I can get is the Verizon boot screen. I can get to TWRP, but my backup does not appear there. Factory Wipe does not have any effect. It can read the SD card.
When I tried to use FlashTool to get the FTF I put on there back, the log spat out an error message that USB debugging might not be switched on (it was) and then gave me the message "Upgrading, do not disconnect device from PC. SOftware Status: Modified". It then reboots and goes to the Verizon boot screen, where it stays forever.
So, to my questions:
Can someone point me to where I could find a suitable stock ROM to try?
It was suggested to me that I "adb a logcat while the phone is bootlooping". I'm afraid that one is over my head, so could anyone tell me how?
(I should add that when I run ADB in TWRP, it fails. It says "Updating partition details...done. Full SELinux support is present, Running boot script... Finished running boot script. MTP Enabled. Starting ADB sideload feature..." THen, after about 5 minutes it tells me it failed.)
Thanks!
Resolved
In case anyone else encounters a similar problem, creating a new FTF and reflashing worked for me (I had tried it before and it had not worked, but third time's a charm, I suppose). I used the instructions here: http://www.xperiablog.net/2015/03/1...peria-lollipop-using-xperifirm-and-flashtool/
I no longer have root, but I am on 5.1.1 and will see where I can go from here.