I followed this guide for flashing TWRP 2.8.7.0.
It flashed wonderfully, boots properly in and out of recovery mode. However, I'm having issues doing a system backup. It gets about 90% done with system, about 1GB of 3.7GB and suddenly acts like the phone died, putting it into charger state (always hooked up to charger when doing backups or flashing).
If I unplug charger, I can boot the phone normally. Also can shut down and boot into TWRP normally. No negative repercussions. Why is TWRP crashing when trying to make a backup?
EDIT: Also happening in Grand Prime CWM. I suppose SM-G530T just isn't ready for this?
Same here. I have the same issue. It installs OK but when you try to backup it shuts down the phone itself in the middle of the process.
For cwm, it looks like it's backing up but when you restore from it, it wipes the phone.
Sent from my SM-G530T using XDA Premium 4 mobile app
Related
Okay heres what happened: I was attempting to flash a ROM. After making a new backup and flashing that new ROM the device would not boot. So like any normal person would do I then went back into recovery and attempted to restore my backup. Upon restoring the backup, halfway through the device just decides to reboot and boot into the ROM (which was a half restored backup). I tried to boot back into recovery and start the process over however now the device will not boot into the recovery at all. It continues to loop the bootloader logo over and over. Is this a soft brick? Either way, all I want at this point is to be able to restore that backup so I can atleast have it working again. All help is much appreciated.
EDIT: okay i managed to get the recovery loaded, what i may end up doing is loading a saved ROM up and starting from scratch there (TWRP continues to Stop my restore halfway through and reboot the recovery --very frustrating tbh). My question then however would be is there a way to get my data back from my backup once I start fresh? Does tibu allow this or something comparable? I really don't want to lose all that data. Thanks again.
Edit 2: managed to fully resolve issue. delete if neccessary.
HarmonyFlame said:
Okay heres what happened: I was attempting to flash a ROM. After making a new backup and flashing that new ROM the device would not boot. So like any normal person would do I then went back into recovery and attempted to restore my backup. Upon restoring the backup, halfway through the device just decides to reboot and boot into the ROM (which was a half restored backup). I tried to boot back into recovery and start the process over however now the device will not boot into the recovery at all. It continues to loop the bootloader logo over and over. Is this a soft brick? Either way, all I want at this point is to be able to restore that backup so I can atleast have it working again. All help is much appreciated.
EDIT: okay i managed to get the recovery loaded, what i may end up doing is loading a saved ROM up and starting from scratch there (TWRP continues to Stop my restore halfway through and reboot the recovery --very frustrating tbh). My question then however would be is there a way to get my data back from my backup once I start fresh? Does tibu allow this or something comparable? I really don't want to lose all that data. Thanks again.
Edit 2: managed to fully resolve issue. delete if neccessary.
Click to expand...
Click to collapse
How did you get back into recovery? I had paranoid android flashed and i did a factory reset like an idiot. Now i cant boot into recovery - "teamwin" logo freezes and reboots into a continuous loop. I can get into the bootloader but nothing works?
sashennaidoo1 said:
How did you get back into recovery? I had paranoid android flashed and i did a factory reset like an idiot. Now i cant boot into recovery - "teamwin" logo freezes and reboots into a continuous loop. I can get into the bootloader but nothing works?
Click to expand...
Click to collapse
I'll tell you what I literally did.
When the device was bootlooping the teamwin logo, I booted into fastboot and powered my device completely off. I then waited an hour as I was a little tired with what was happening to take care of something. After that hour I turned it on and it suddenly booted into teamwin recovery. That's exactly all I did. So what I would do is turn the device off for a little bit then try to see if it boots the recovery. If not you will likely have to use the nexus 10 toolkit to reflash the recovery.
Hope that helps.
HarmonyFlame said:
I'll tell you what I literally did.
When the device was bootlooping the teamwin logo, I booted into fastboot and powered my device completely off. I then waited an hour as I was a little tired with what was happening to take care of something. After that hour I turned it on and it suddenly booted into teamwin recovery. That's exactly all I did. So what I would do is turn the device off for a little bit then try to see if it boots the recovery. If not you will likely have to use the nexus 10 toolkit to reflash the recovery.
Hope that helps.
Click to expand...
Click to collapse
Thanks mate! really appreciate it! I have no clue what i did but on one of the reboots, it booted into TWRP and i re-flashed the paranoid android rom and gapps and it worked.
Thanks for above response. Much appreciated!
Just for future reference, both TiBU and ROM Toolbox will restore from a Nandroid backup.
Sent from my Nexus 10 using Tapatalk HD
bruce7373 said:
Just for future reference, both TiBU and ROM Toolbox will restore from a Nandroid backup.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
So I am in this same boat and will probably have to use some toolkit since I have not been able to boot up TWRP. I know I am on 2.4.4.0 or something for TWRP, not 2.5 but would CWM be a better choice since I have run into this now a couple of times? This is the first where it hasn't stopped the recovery boot loop.
So i have the korean variant of the LG G2 (F320K)
I installed CWM which went fine. I then did an OTA update and it screwed up my phone. Basically my phone no longer boots into Android. It keeps going into CWM recovery. I cannot get into download mode at all. The phone no longer charges when turned off (It boots into CWM whenever i plug in the USB cable). So basically i'm stuck in CWM.
Tried factory reset etc... but nothing works. Tried flashing a different ROM but that doesn't work.
Can anyone help?
One thing i noticed is that under mounts, System is unmounted and every time i mount it and reboot i go straight to CWM again and system is unmounted again.
Hello all, I have a mess here. I just got a 935f, rooted with dm-verify installed. It has worked fine for about a week. Then I decided to try a Nougat beta. So I went to twrp to make a backup. I noticed that it failed because the data partition was not mounted. So I went to Google to see how to mount the data. There were various videos that said I needed to format the data partition to a different file system. So I tried EXT4 first. That didn't work so the video said to try exFat next. So I did. There were no error messages but no progress either. I let it run all night thinking that it might take a while to change a large partition. But now it is morning and there has been no change. There were no visible buttons to interrupt the process so finally I tried Powee and Vol Down. That forced a reboot which brought me back to the Twrp splash screen. This is all I can get from the buttons. If I could get to Odin, I'd flash a stock rom.
Gurus? I'm plugged into the charger and the Teamwin screen won't turn off....
UPDATE : I was able to access download mode so I can flash a stock rom... But I would still appreciate advice on what I should have done about the failure to mount the data partition...
Sent from my SM-N910F using XDA-Developers mobile app
After flashing the stock rom, the phone works fine, but how can I unencrypt the internal storage (data) so that TWRP can see it and include it in a backup?
Sent from my SM-G935F using XDA-Developers mobile app
Yo
How did you get to download mode?
I'm totally stuck in twrp!!!
Thanks
Hey guys,
Not sure what I screwed up... I recently tried installing chainfire root via ODIN onto my Note 4 (trltexx) running 6.x and it got stuck on trying to boot recovery.
Then I flashed back to stock 6.0.1, and rooted by installing TWRP 3.0.2-0 via Odin, then flashing latest SuperUser.
So now I'm on 6.0.1 stock, rooted, but whenever I plug the device in while it's powered off it just fires up TWRP. I don't have the charging icon screen anymore...
Does any body know what partition I messed up and how I would fix that? I'd rather it not launch TWRP whenever I plug it in to charge. (Doesn't do this when it's already on, just when it is powered off).
Thanks,
Levi
Levistras said:
Hey guys,
Not sure what I screwed up... I recently tried installing chainfire root via ODIN onto my Note 4 (trltexx) running 6.x and it got stuck on trying to boot recovery.
Then I flashed back to stock 6.0.1, and rooted by installing TWRP 3.0.2-0 via Odin, then flashing latest SuperUser.
So now I'm on 6.0.1 stock, rooted, but whenever I plug the device in while it's powered off it just fires up TWRP. I don't have the charging icon screen anymore...
Does any body know what partition I messed up and how I would fix that? I'd rather it not launch TWRP whenever I plug it in to charge. (Doesn't do this when it's already on, just when it is powered off).
Thanks,
Levi
Click to expand...
Click to collapse
Looked into the chainfire root package and saw that it flashes not only recovery but also the cache partition. So I went into TWRP and wiped the cache. Looks like problem solved, charging screen is back.
Hopefully this post helps somebody else in the future!
Hey guys,
i messed up i think, but i hope you can help me out of this...
Today i flashed a SM-G950F with TWRP version 3.3.1-0 using heimdall.
It went without any issues and i can boot into the recovery just fine.
The only reason for this was me wanting to backup the whole phone using adb pull /dev/block/sda.
After i was done with this command i tried rebooting back into the system, but now it is stuck in a bootloop.
The phone turns on, shows the logo, vibrates and the screen turns of again and the cycle repeates.
Does this have anything to do with me flashing the recovery? If so, what can i do now? This is not my phone and i'd like to
prevent any data loss.
For the record:
I messed up, because i did not make an backup of the original recovery since i thought keeping TWRP would be fine. Which was stupid, but what's done is done...
I also cannot easily backup the internal storage, as it is encrypted.
Any help would be highly appreciated.
bakaschwarz said:
Hey guys,
i messed up i think, but i hope you can help me out of this...
Today i flashed a SM-G950F with TWRP version 3.3.1-0 using heimdall.
It went without any issues and i can boot into the recovery just fine.
The only reason for this was me wanting to backup the whole phone using adb pull /dev/block/sda.
After i was done with this command i tried rebooting back into the system, but now it is stuck in a bootloop.
The phone turns on, shows the logo, vibrates and the screen turns of again and the cycle repeates.
Does this have anything to do with me flashing the recovery? If so, what can i do now? This is not my phone and i'd like to
prevent any data loss.
For the record:
I messed up, because i did not make an backup of the original recovery since i thought keeping TWRP would be fine. Which was stupid, but what's done is done...
I also cannot easily backup the internal storage, as it is encrypted.
Any help would be highly appreciated.
Click to expand...
Click to collapse
delete the folder names "Android" on the internal storage in the file manager in TWRP and reboot