Galaxy Tab A stuck in TWRP reboot loop. - Samsung Galaxy Tab A series Questions & Answers

SM-T550 I have used TWRP for over 4 years now, have never had an issue when restoring a backup.
Now i just restored a backup and when i hit reboot, it just keeps opening TWRP over and over.
I cannot power down or anything. What can i do to get this fixed?

Try to go into Download mode and flash TWRP again
volume up + volume down + plug usb cable to computer

bishftl said:
I have used TWRP for over 4 years now, have never had an issue when restoring a backup.
Now i just restored a backup and when i hit reboot, it just keeps opening TWRP over and over.
I cannot power down or anything. What can i do to get this fixed?
Click to expand...
Click to collapse
When you post your model as Tab A, you might as well just say I have a Samsung tablet. All that "Tab A" indicates is that Samsung classes it the less expensive line of tablets. There are a lot of tablets in the Tab A line that have very little in common except their price. So to get good advice on fixing problems, state the actual model number, such as SM-T580 or SM-T250. Both are Tab A but are entirely different tablets.
As to your current problem, I'd recommend that first you try to restore from another backup, if you have one, or restore the current one again. If that doesn't work, you may have to do a fresh install by wiping and flashing a ROM and gapps and Magisk.

Related

[ROGERS SGH-1337M] Wont Reboot Without FULL WIPE

INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
Which ROMs are you installing? On I337M your best bet is T-Mobile ROMs and Kernels. I have Bell I337M and have no issues.
Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
Are you wiping with TWRP? I heard there are issues with using it to wipe and restore or loading a new rom after wipe. Just restore using Odin and then load a new rom (or restore a backup) without wiping. See if that solves your problem of bootlooping
kiru said:
Are you wiping with TWRP? I heard there are issues with using it to wipe and restore or loading a new rom after wipe. Just restore using Odin and then load a new rom (or restore a backup) without wiping. See if that solves your problem of bootlooping
Click to expand...
Click to collapse
i just went through this all last night what a pita , problem is twrp , if you do a full wipe when you type the word yes , you can only bootup 1 time then it gets stuck next time you boot , theres no way to fix it , even going back to old version of twrp wont do it , you have to compleatlly remove root and return to stock , re root and install twrp again , then if your luck your nandropid backup will work , it took me 5 hrs to fuger this all out , stupid twrp drove me nuts .,...
in short , return to stock and reroot , then never do a full wipe where you have to type yes
Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
i had the same problem, im with rogers so i downloaded the rogers rom 4.2 and i cant make any phone calls or listen to music or watch videos. my phone came with 4.3 does anyone have any ideas to help me?

[Q] Galaxy S5 android 5.0 and recovery

Hi guys
I'm using samsung galaxy S5 (4.4.2) and recently upgraded to 5.0 using custom rom which I found here. It was working just great. I created 2 Nandroid using TWRP. One after a fresh installation another one after restoring my file contents from Helium and Titanium backup..
However something went wrong and i decided to restore my nandroid backup to revert back my changes. To my surprise both nandroid backup failed. I got a success message (using recovery mode) however when i reboot my phone im getting tons of messages like "System failed to start" "process failed to start" wait or press ok.
When I reflash the custom rom, it works fine, however i couldnt recover my system from nandroid backup.
I repeated several times but both nandroid gave me this same error. I even tried fixing permissions but no use. Then I used odin to flash a stock rom (BOA3) and rooted that using TWRP and most recent SU binaries. Its working great now, however I just wanted to know what is the best method to take a nandroid backup now? I'm afraid TWRP will bail out on me once again.
All the while I used CWM and it was great however 5.0 requires latest binaries and only can be rooted via TRWP recovery. Any suggestion? I just want to take a complete nandroid backup and save it in case if something goes wrong.
Thanks
sam20e said:
when i reboot my phone im getting tons of messages like "System failed to start" "process failed to start" wait or press ok.
Click to expand...
Click to collapse
I'm being plagued by this problem since I updated, flashing stock Lollipop using odin.
The problem first appeared after trying to restore my app+data using Titanium.
I went back to the beginning and flashed again but my phone is still unstable and I still occasionally get the '"System failed to start" "process failed to start" wait or press ok' issue that you have. A reboot generally sorts it out but the update has made my phone very unstable.
I also have big problems entering recovery and download modes using the buttons.
Cleaning my cache/davlik hasn't solved it either.
Hopefully someone can help us.
Anyone?
Got "Reactivation Lock" disabled?
Settings > General > Security
*Detection* said:
Got "Reactivation Lock" disabled?
Settings > General > Security
Click to expand...
Click to collapse
Yes. Thanks for the suggestion though.
Trouble in Galaxy town
Hi, I'll try make myself short.
1) Back when I had an Galaxy S2 i modded it a little bit but I haven't done it at all since then.
2) Now a few years later I got bored/sick of the stock ROM that comes with the S5 so I wanted to install something I knew had a good reputation, Cyanogenmod.
3) Getting a new recovery was an nightmare itself but eventually I got it working and made an backup so I could roll back if needed to.
4) Now, 24 hours of using CM12 I can only say one sentence: "What kind of crap is this?!" It's so unstable it's almost ridiculous. Bluetooth hangs up all the time thus requiring a reboot which leads to most-annoying-thing-ever-#2. The clock resets itself upon EVERY boot which makes WhatsApp go bananas. Doesn't matter if I previously set the time/date manually or let the phone do it automatically. Then there are the random hang ups that occur all the time and one third thing. Hardware acceleration in BS Player doesn't work AT ALL!
5) Said and done I reversed to the back up but oh man the phone wasn't happy about this (yes I made a wipe before recovering the backup). Nearly every basic service malfunctioned and were forcibly shut down. A factory reset made no difference...
6) For some reason I opened KIES and found out that an update with android lollipop was available so I (in a moment of despair) installed that hoping for salvation.
7) The phone boots properly and everything seems to be going wonderful until I realize that my network connection is high on something. Loses connectivity to my provider all the time thus the phone is totally useless.
8) I HAD to have a working phone for work and since no support is given on Sundays from Samsung I again installed CM12 just for the day.
Now to the good part!
9) When trying to recover the backup once again it's gone corrupt! Can't recover so now I'm stuck with buggy-as-h*ll-cyanogemmod12 with no means of reverting.
What-the-actual-****-do-I-do? Been trying to make some sense from the thread "Galaxy S 5 Original Android Development" but I feel so lost. So if someone could point me in the right direction I would be very grateful!
EDIT: What I want is to reverse back to original stock ROM. Screw the bloatware. I just need the phone stable and working!
EDIT2: After some more googeling I've figured out I need a stock ROM with the right CSC. I use a swedish carrier other than 'tre'. Shall I look for ROMs with CSC 'HTS' anyway? Can't find any info about other carriers in sweden.
EDIT3: Now I've found what I think is right on sammobile.com/firmwares/database/ (search query: 'g900f', first hit 'Sweden' CSC 'VDS'). Worried thou as it's Android Lollipop which made my phone go nuts. Can't find the KitKat version on that site...
EDIT4: Found the KitKat version on samsung-updates.com. The download speed is sooooooo slow (~6 hours)! Download limits should be illegal...
Thanks! //R

Nexus 6P stopped booting, nothing I do is now working. PLEASE HELP ME.

At this point I have completely run out of options. I AM CALLING UPON THE XDA COMMUNITY TO PLEASE HELP ME. Little bit of background info, nexus 6p was rooted and modified through xposed. Had some modules installed, mostly quality of life and visual/theme modules, as well as the latest version of SuperSU.
These past few days my Nexus 6P has completely stopped responding at times. Extremely laggy and could not do **** with it, systemui kept restarting over and over and over again for no reason. Had to keep force rebooting (holding down the power button for 10 seconds) multiple times over and over again, to the point where it suddenly stopped booting into the OS, it just kept giving me the boot animation loop, i could only access the TWRP recovery i had installed. Before all of this **** went down, I had created a TWRP backup because it would be my safety net if i could somehow miraculously get it to work. Now i have a backup of my TWRP BACKUP FILE on my desktop.
I have wiped caches more times than i can count, have tried factory restoring and formatted the data, and tried flashing the stock google image (the same one that i originally flashed at the time that I got the phone when i started to root) as well as flashed the old TWRP version i had, as well as the current latest version of TWRP, and then transferred the backup i made back onto the phone's internal storage. Tried restoring the old backup from TWRP, and each time it restores, it just reboots without reaching 100% and once it reboots, it still gives me a bootloop, this time, no boot animation, it just gets stuck at the Google text with a little "unlocked" logo at the bottom. I have completely run out of options, and have A LOT of EXTREMELY IMPORTANT information i have saved on the phone.
I will say it again. I am EXTREMELY DESPERATE to get my data back, to the point where i am even willing to offer a cash reward for any help to get my phone working back to the way it used to, or even at least to extract the information through the backup, if at all possible.
Additional information about the files and images I used:
angler-mdb08k is the name of the google image i had back when i had the phone and have flashed again
twrp-2.8.7.2-angler is the TWRP version i had back when i had the phone originally at the time
I had flashed and followed guides online through adb method.

My rooted samsung galaxy s4 is soft bricked, Can I save the data?

Yes this post is correctly dated. I've had this device a LOOOONNNGGG time.
The device has been rooted since shortly after I bought it new years ago. I've had very few problems since... which is why it's never been replaced.
I believe I have the stock ROM, sorry it's been a while.
When I start the device it gets stuck at the splash screen with the sprint logo.
I can get the device to "download mode" but I don't know what to do once there and I'm not sure I can do anything from here.
I can get the device to "android system recovery."
I know I installed TWRP when I rooted and installed the rooted ROM but when I boot to recovery it doesn't go there.
I've wiped the "cache partition" but the problem remained. I'm not sure what else to do from here and still be able to salvage data.
I'm trying to salvage the data on the internal storage. I'm pretty sure I could successfully "wipe data/ factory reset" and get it to "function" again but that's not the priority. I'm going to replace it regardless of success or failure. Data recovery is the priority here. (pictures and videos of my young children as well as less important stuff like contacts.)
I have an old laptop with an old version of ubuntu I can use or a newer one with windows 7 to work with. I mention this in case it makes this easier to help?
Thank you very much if you try to take a stab at this or refer someone that might!
Update:
So I managed to install TWRP via Odin.
I booted to this recovery and my data partition appears to be empty?
When I try to back up I get the error message "unable to mount '/data'"
I tried doing a wipe, not one of the fancy extra options ones just the regular wipe and it failed.
Any guidance will be extremely appreciated.
Edit:
So I've come to the conclusion that the data isn't accessible because of encryption and my pass code. Is there any way to enter it via recovery and access this info?
Is anybody out there?
Edit 2:
I hope this helps someone someday. I haven't solved the problem but I think I'm making progress.
First I had an old version of TWRP. I installed the latest for my device and tried backing up again. I'm not sure but I think it's working. TWRP dosen't seem to need my password for the backup. I imagine I'll just need it to access the data later.
Edit 3:
No sooner did I save the last edit and my backup failed.
Process ended with error : 255

Bootloop: Upgrading Verizon Note 4 from 5.1.1 w/ root to 6.0.1 w/ root

After attempting to upgrade my wife's Verizon Note 4 from 5.1.1 with root to 6.0.1 with root, it is now in a boot loop. I had done my exact phone earlier this month with no issues, so I was confident I could do hers. Now she's pissed because she has no phone and I'm in the dog house. Fortunately, I made a complete backup of her phone using TWRP before attempting this upgrade.
So, can I just restore her backup or are there other steps I need to perform before trying to revert it, since I did flash the N910VVRU2CQL1_PartialFirmware_DevEd.tar and the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar during the process, and also the JasmineROM_v7.0_N910VVRU2CPF3, though it was actually restored via TWRP.
The details are below if it helps determine what might have happened, but if I can just restore her backup, she'll be happy, which means I can finally get out of the dog house.
I tried upgrading my wife's phone since she has the same exact phone running 5.1.1 with root. Everything appeared to be going fine, but after performing the last step (flashing the N910VVRU2CQL1_PartialFirmware_DevEd.tar.md5.7z via Odin) and rebooting the phone, it now goes into a boot loop. It will load the Samsung logo for about 20-30 seconds, then reboot every time. I can still access TWRP from recovery and I have cleared Dalvik and Cache, but it still does the same thing. I also reflashed JasmineROM_v7.0_N910VVRU2CPF3, cleared Dalvik and Cache again, but still the same boot loop. It does still show the word Custom under the Samsung logo at boot, so I assume that is good news. Doesn't that mean the bootloader is still unlocked or something?
If it helps, the part of the process that had me concerned was after unlocking the bootloader. I powered off the phone, and then tried to load the recovery menu so I could factory reset the phone and clear the cache, but the recovery menu never appeared. It did show the Android fix-it guy for the recovery for about 10 seconds then a short progress bar under it for about 5 seconds, then it went straight to the Samsung logo. It never did give me the actual recovery menu, just the Android fix-it guy animation, which I thought was odd because I've always had the recovery menu pop up after that.
Any suggestions?
Mike
Modify_inc said:
After attempting to upgrade my wife's Verizon Note 4 from 5.1.1 with root to 6.0.1 with root, it is now in a boot loop. I had done my exact phone earlier this month with no issues, so I was confident I could do hers. Now she's pissed because she has no phone and I'm in the dog house. Fortunately, I made a complete backup of her phone using TWRP before attempting this upgrade.
So, can I just restore her backup or are there other steps I need to perform before trying to revert it, since I did flash the N910VVRU2CQL1_PartialFirmware_DevEd.tar and the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar during the process, and also the JasmineROM_v7.0_N910VVRU2CPF3, though it was actually restored via TWRP.
Click to expand...
Click to collapse
Not that I'm impatient, but I thought I had a backup phone I could put my sim card in until I resolve this issue. Only problem is I forgot it was an at&t phone. Duh!
From what I've read the Note 4 n910v is a robust and almost unbrickable phone. So I said what the heck, I'm going to restore my backup. I mean that is why before all instructions it is advised to make a full backup, so you can revert back, right!. I don't recall the instructions claiming there is a special process or order of steps to take before you can restore your backup.
So, I wiped everything and restored my full backup via twrp. Upon reboot, I finally had the "Kernel is not seandroid enforcing" and "Set Warranty Bit: Kernel" that I was accustomed to. I thought this must be a good sign, but then it went to a black screen, which I realized after about 20 mins, that it had powered itself off. So I tried it again and same thing, it doesn't reboot or even vibrate or flash the LED light. I can press the power button and it will come back on, so I know it turns itself off. So what would cause it to power off after displaying the first boot logo titled Samsung Galaxy Note 4 Custom w/ unlocked icon powered by Android?
The next thing I will try, unless hopefully someone advises me otherwise, is reflash the N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW]. I assume that should be safe to do, and I'll just follow the directions for the "Easy Guide for How to Root Verizon Galaxy Note 4 (updated links and instructions)" though technically isn't the bootloader already unlocked since I have the red "Kernel is not seandroid enforcing" and the yellow, "Set Warranty Bit: Kernel" and the custom unlocked lock on my boot screen?
This is where I'm confused, I feel like this is not the issue, that it must be something else, but I'm at a lost.
Finally got my phone working! But no WiFi
I've finally got my phone working again! I just can't get the WiFi to work. I have tried three different modems but still the WiFi will not enable: N910VVRU2BPA1_Modem, N910VVRU2CPD1_Modem, and N910VVRU2CPF3_Modem. I even tried restoring the modem I had backed up, but still no go. I noticed that even when I restored my modem from backup, it still said my baseband was N910VVRU2CQL1, but when I flashed the other modems, they each updated the baseband correctly, displaying the correct baseband version, though still no WiFi.
Any suggestions?

Categories

Resources