[Q] Stuck on TWRP/System Recovery. Need help.
Hello, first time posting here.
So like the title says, my phone is stuck on System Recovery. I have a Samsung Galaxy A5 (A500F model), rooted, and with TWRP installed.
The phone was running fine for 3 months without problems, so I guess it must be from recent installs, but I haven't installed anything since last week. The last action I did prior to this problem was going to System Recovery via Link2SD app, since the usual button combination didn't work. So I guess the fault lies there? At this point I have tried everything I can do, like restarting, rebooting, wiping, factory resetting, and I even restored a backup but it still goes to System Recovery after every restart.
This is my first problem on Android phones, so I hope you can help me.
If you need more information, I'd gladly provide.
Cheers.
....bump.
Related
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
m_hawkmoon said:
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
Click to expand...
Click to collapse
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Theonew said:
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Click to expand...
Click to collapse
The phone rebooted automatically. Did not give me the chance to do anything beforehand.
As you said the phone was soft bricked so when i got home that day i just fixed it. No problem. However I am really really into getting to find out how a 1 day old back up can get corrupted.
Alright, so yesterday I tried to root my tablet (Samsung Galaxy Tab 3 10.1 Wifi) yesterday by installing TWRP and then loading the Superuser zip found in their link in the play store. It worked fine--I had root access and all was going fairly well. I then tried to make a small tweak to the build.prop file by changing ro.build.version.codename from REL to L.
When I rebooted to apply that change, I could not start up, so I did a factory reset (not a big deal, no essential files on there). It then booted fine, but when I reinstalled/updated all my apps, the Google services were crashing like mad. So I reverted the build.prop file back to REL and again it would reboot, so I did another factory reset and all was good; the Google apps were fine.
Well I was still rooted and I wanted to take advantage of all that time I spent doing it, so I downloaded the bootanimation zip found on this thread and replaced my bootanimation.zip that was already on there. I restarted to see the animation, and this is when the real nightmare started happening. I could not boot now at all.
I did another factory reset, and still it wouldn't boot. I then used TWRP to do a full reset, and still nothing. I did an advanced reset and somehow managed to delete the operating system files (I have no idea how), causing TWRP to say that no operating system was installed. I still couldn't boot, of course.
Finally, I decided I had had enough of this rooting ****. I searched all over the internet looking for a North American version of my stock ROM, and finally found one posted on this forum post. I wouldn't normally trust any random file, but I was getting desperate here. I used Odin to flash that ROM, and there were no errors. Now when I go into recovery, it gives me stock and not TWRP, so I know that was probably successful.
However, I still cannot boot. I get stuck on the screen that says Samsung Galaxy Tab 3, which sometimes goes away and then comes back. I can't send it in for warranty, because it still says "custom" in the recovery mode. How can I fix this? any ideas?
I really want my tablet back :crying:
Hello community, I am new here so I don' t know where to put this.
Well I need some help, I am having problems with my old tab, A Samsung Galaxy Tab 2 10.1 GT-P5113, Flashed with custom ROM CM 10.1.3 for GT-P5110
Worked fine for a year and a Half, the issue that I am having now is that, it constantly restarts, after entering to the OS I can tweak change etc, but after a few secs it just turns of and reboots the system.
The other problem that I am having is that I tried everything that I could think of. I deleted some apps, which came back after the reboot. I booted to safemode, and deleted the last apps that I installed, still came back after the crash reboot.
I went to recovery mode (CWM) and did a Factory reset, delete cache and delete Dalvik Cache. Nothing when reboot everything was like last time.
wen't to and tried to reflash CM 10.1.3 (stable) following every procedure and nothing everything was back.
Last thing I tried is ODIN with stock ROM (which is hard to find for this tab.) but get write error after going to half. I am downloading a second stock ROM (android 4.1.1) to see how it goes.
Hope to find help here, I would be greatly thankful.
EDIT: Flashed now with the new stock ROM, ODIN says success, everything seems fine, but again I got received by the same splash and the same logon screen, and still crashes and reboots...
I really need the help
Isifth said:
Hello community, I am new here so I don' t know where to put this.
Well I need some help, I am having problems with my old tab, A Samsung Galaxy Tab 2 10.1 GT-P5113, Flashed with custom ROM CM 10.1.3 for GT-P5110
Worked fine for a year and a Half, the issue that I am having now is that, it constantly restarts, after entering to the OS I can tweak change etc, but after a few secs it just turns of and reboots the system.
The other problem that I am having is that I tried everything that I could think of. I deleted some apps, which came back after the reboot. I booted to safemode, and deleted the last apps that I installed, still came back after the crash reboot.
I went to recovery mode (CWM) and did a Factory reset, delete cache and delete Dalvik Cache. Nothing when reboot everything was like last time.
wen't to and tried to reflash CM 10.1.3 (stable) following every procedure and nothing everything was back.
Last thing I tried is ODIN with stock ROM (which is hard to find for this tab.) but get write error after going to half. I am downloading a second stock ROM (android 4.1.1) to see how it goes.
Hope to find help here, I would be greatly thankful.
EDIT: Flashed now with the new stock ROM, ODIN says success, everything seems fine, but again I got received by the same splash and the same logon screen, and still crashes and reboots...
Click to expand...
Click to collapse
It keeps with the boot loop.
Hi, thank you for using XDA Assist. After you flash with Odin go into the stock recovery and do a factory reset. If that doesn't work it may be that you're device is just getting old and giving up the ghost. There's a whole forum for your device which may also help. See this,http://forum.xda-developers.com/galaxy-tab-2
Oh, that would be bad news :/
Do you think it could be that I deleted CWM rommanager app, and then accidentally deleted the .recovery, that put me into this situation?
Isifth said:
Oh, that would be bad news :/
Do you think it could be that I deleted CWM rommanager app, and then accidentally deleted the .recovery, that put me into this situation?
Click to expand...
Click to collapse
After you flash with Odin, boot into the stock recovery and do a factory reset
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
After you flash with Odin, boot into the stock recovery and do a factory reset
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
It didn't work. I noticed that after the transferring of odin it doesn't go to the installation procedure. It just skips that and goes to the logscreen with how everything I had.
Now I went to safe mode, and deleted all apps that I could from play store. when I came back after a restart, everything was there, back. :/
Please ask any further questions you have on the q&a forum in your drives forum, the link I gave you. They are the experts on your device
Thread closed.
Earlier today, I got an error upon starting up my Samsung Galaxy S5 (T-Mobile) that says "Unfortunately, System UI has stopped." My background has been turned to black and none of the buttons work properly. The phone IS rooted (and has been for about a week), but runs on stock OS (5.0 Lollipop) and stock recovery. I have never flashed a rom on this phone. I already tried restoring from a Titanium Backup I made yesterday before this error ever showed up, but it did nothing. Perhaps it's relevant that this error first happened after I booted the phone in recovery mode (to see what stock recovery looked like), then selected "reboot phone." I also already tried wiping the cache partition, wiping the System UI cache, and rebooting is Safe Mode. None of these worked. I thought unrooting the phone might help, but I accidentally uninstalled SuperSU without removing the root. With the System UI down, I can't install any apps at all, such as SuperSU again or a file explorer that would allow me to remove the "su" folder in /system/bin/. Now I have no way of unrooting, short of wiping the phone. I DO NOT want to do that. How do I get my phone back to normal?
--EDIT-- I finally gave in and did the factory reset. I rooted it again using the same method as before (in order to use Titanium Backup), and just to see what would happen I went to recovery mode. Sure enough, I was greeted with the same error as before. I had already rebooted the phone normally multiple times before trying to use recovery mode, so I have no doubt that the stock recovery mode is the cause of these issues.
Signal2Noise said:
Personally, I don't like Titanium Backup. I seem to be in the minority with that opinion, but it's given me issues in the past. Try flashing a non-stock recovery like TWRP for your S5 and either wiping your phone or wiping and flashing another ROM.
Samsung phones seem to dislike rooted users for some reason
Click to expand...
Click to collapse
Too late, I already wiped the phone. I re-rooted using Chainfire's auto-root, then flashed CWM so that stock recovery doesn't screw me over again. Before restoring from the backup, I booted into CWM recovery and restarted the phone. No error. I hope it stays that way, this whole thing is a huge hassle. There really needs to be a disclaimer with Chainfire's auto-root telling people to get rid of stock recovery!
Hi there
You'd be best served asking for help from the experts who own your device, here:
T-Mobile Galaxy S 5 Q&A, Help & Troubleshooting
Good luck
Hey guys,
I have encountered a serious problem on my device. Today I rebooted my phone once and it has just stuck on the samsung logo. Then the phone began to reboot without ending....It could not just start. With the help of TWRP I have made a full wipe and tried to reinstall my actual firmware Superman 1.10.5, but I always stuck at 25%, the phone did not respond to any actions. I even tried to flash the stock 4-file firmware with Odin, but it did not help, the phone constantly reboots. Sometimes it manages to boot to the stage where the sign "installation of applications" appears, but a while later it stucks again and reboots. Please, help me to solve the issue, because I am begininng to think that it would be unpossible to recover the phone. I am only able to enter the download mode or recovery, anything else does not work.
Thanks....
AuroraLX said:
Hey guys,
I have encountered a serious problem on my device. Today I rebooted my phone once and it has just stuck on the samsung logo. Then the phone began to reboot without ending....It could not just start. With the help of TWRP I have made a full wipe and tried to reinstall my actual firmware Superman 1.10.5, but I always stuck at 25%, the phone did not respond to any actions. I even tried to flash the stock 4-file firmware with Odin, but it did not help, the phone constantly reboots. Sometimes it manages to boot to the stage where the sign "installation of applications" appears, but a while later it stucks again and reboots. Please, help me to solve the issue, because I am begininng to think that it would be unpossible to recover the phone. I am only able to enter the download mode or recovery, anything else does not work.
Thanks....
Click to expand...
Click to collapse
Really sad to hear that story mate. First things first, I assume your BL version is matching with the firmware your flashing right. And when you go to TWRP, can you see /system and /data partition from the mount menu? If not, you have to perform a factory reset. I had issue like that with my Galaxy S7 and usually factory reset(not wiping) helped me with that situation. Since your system can boot up, but crashes after awhile, I do suspect that some of your partition might be corrupted(at least its what happened to me). So trying factory reset can be a good bet for you.
And... I think you have to provide more information with which variant you are using, and your BL version, TWRP version too, solve the problem quicker. Hope this information helps.
CenteaOSD said:
Really sad to hear that story mate. First things first, I assume your BL version is matching with the firmware your flashing right. And when you go to TWRP, can you see /system and /data partition from the mount menu? If not, you have to perform a factory reset. I had issue like that with my Galaxy S7 and usually factory reset(not wiping) helped me with that situation. Since your system can boot up, but crashes after awhile, I do suspect that some of your partition might be corrupted(at least its what happened to me). So trying factory reset can be a good bet for you.
And... I think you have to provide more information with which variant you are using, and your BL version, TWRP version too, solve the problem quicker. Hope this information helps.
Click to expand...
Click to collapse
Yep, you are right, BL versions always matched firmwares. I tried to wipe the phone with TWRP 3.0.2.3 and also to make a factory reset with the stock recovery. The stock firmware, which I tried to flash, was G930FXXU1BPH6_G930FOXE1BPH1_SER consisting of 4 files including BL,AP,CP and CSC. After 3rd or 4th flash of the same stock firmware the phone suddenly became alive and began to boot. Wu-huuu:silly: I was happy as a child. After having successfully launched the stock rom I have again flashed TWRP 3.0.2.3, went to "wipe" option and formatted data. Then I have installed a Superman Rom 1.12 and everything went the right way. I don't understand only one thing: why after having wiped the phone several times and having reseted it through the stock as well as TWRP recovery it didn't want to boot.
As you said, I suppose that the one of partitions was corrupted. Oh damn, I thought that I won't be able to resuscitate this phone.
I have flashed about 20 phones during my life, but I have never ever encountered such serious problems.