Hey,
I actually have a Note 10 plus, rooted with magisk and TWRP, but the Note10 and S10 are very similar, so Ill ask here too (ive waited like 15 hours and got no help in the note 10+ sub).
I have done a full nandroid backup. I restore it with TWRP, and I get stuck on boot, the note 10 screen (not samsung screen), and it never boots. If i restore only data, i get a bootloop.
I wipe dalvik and cache. No difference.
The backup IS NOT corrupted. I tried multiple backups and all is the same
What am I supposed to do? Im completely lost, and found literally nothing from google or here. Also if I flash firmware with odin after the restore, it will boot, but I lose all data, and eevrything. So thats not gonna work.
This is unbelievable and hasnt happened to me when i was doing this last time a few years ago.
I havent had access to my phone in over a day because of this now, its a complete disaster.
Please help. Thanks in advance guys.
masaforce said:
Hey,
I actually have a Note 10 plus, rooted with magisk and TWRP, but the Note10 and S10 are very similar, so Ill ask here too (ive waited like 15 hours and got no help in the note 10+ sub).
I have done a full nandroid backup. I restore it with TWRP, and I get stuck on boot, the note 10 screen (not samsung screen), and it never boots. If i restore only data, i get a bootloop.
I wipe dalvik and cache. No difference.
The backup IS NOT corrupted. I tried multiple backups and all is the same
What am I supposed to do? Im completely lost, and found literally nothing from google or here. Also if I flash firmware with odin after the restore, it will boot, but I lose all data, and eevrything. So thats not gonna work.
This is unbelievable and hasnt happened to me when i was doing this last time a few years ago.
I havent had access to my phone in over a day because of this now, its a complete disaster.
Please help. Thanks in advance guys.
Click to expand...
Click to collapse
I'm not sure, but maybe the nandroid backup isn't compatible with your device.
The thing is that these new phones have a different partition scheme. As you're rooted, you normaly boot on the recovery partition. But when you flash that backup image, maybe it doesn't take into account that partition setting, and that's what messes up your phone.
This is only a small hypothesis, but it can definitely explain your problem. As I've never done any backup myself, I'm not sure about this solution, but maybe try restoring the data on another device, then transfer it on your N10 with USB for example
masaforce said:
Hey,
I actually have a Note 10 plus, rooted with magisk and TWRP, but the Note10 and S10 are very similar, so Ill ask here too (ive waited like 15 hours and got no help in the note 10+ sub).
I have done a full nandroid backup. I restore it with TWRP, and I get stuck on boot, the note 10 screen (not samsung screen), and it never boots. If i restore only data, i get a bootloop.
I wipe dalvik and cache. No difference.
The backup IS NOT corrupted. I tried multiple backups and all is the same
What am I supposed to do? Im completely lost, and found literally nothing from google or here. Also if I flash firmware with odin after the restore, it will boot, but I lose all data, and eevrything. So thats not gonna work.
This is unbelievable and hasnt happened to me when i was doing this last time a few years ago.
I havent had access to my phone in over a day because of this now, its a complete disaster.
Please help. Thanks in advance guys.
Click to expand...
Click to collapse
I am experiencing the same issue.
Device: Tab S 10.5
I am tring to restore a Backup made with TWRP. the restore ends without any error, and when I reboot into System, it stays on Splash Boot forever!!
I though about a corrupted Backup, so went with Fresh Start install + TWRP + Root, then Backup TWRP.
Same issue, stuck on Splash Boot forever!!!
I even tried to unRoot just after the restore, it do not change anything!!!
I also noted that when the Device boot, there is a brif "double vibration", maybe notifying something is wrong.
Related
Hi guys. Yesterday night I was installing a few new apps but the seemed to be stuck installing forever. So I decided to reboot. However, after the reboot, it never goes past the second boot screen.
I know I can just flash to another rom but is there a way to save my data in the instance? I can still get into recovery mode if that helps. Thanks
I've read you can hook up to your pc and mount your sdcard from cwm. Never tried it but if it works you can save your data that way then maybe a master clear/cache or dalvik wipe will help.
Sent from my SAMSUNG-SGH-I897 using XDA App
BumRush said:
Hi guys. Yesterday night I was installing a few new apps but the seemed to be stuck installing forever. So I decided to reboot. However, after the reboot, it never goes past the second boot screen.
I know I can just flash to another rom but is there a way to save my data in the instance? I can still get into recovery mode if that helps. Thanks
Click to expand...
Click to collapse
You can mount USB in recovery and get all your stuff off of your SD that way. You can also nandroid your current ROM in CWM and re-flash it, then restore from backup. As far as saving texts and all that, Idk if you can, but I'm sure someone else does.
Also, you could try clearing dalvik, cache, and then running the kernel cleaning script. It's gotten me out of a few binds before. It might help you to where you wouldn't have to flash again.
Reposting this here…
Hi, all!
My Samsung Galaxy Ace (S5830) running under a custom ROM The Ultimatum (I've been using this custom firmware for a few weeks now, with no real problems up until now), is bootlooping with no apparent reason. On a rare occasion, most apps on the phone stopped responding and would crash upon opening, and would require a restart before they worked again. Well this happened to me a few hours ago, so I decided to reboot my phone. After coming back to check my phone, I had found it was still booting. This has gone on for several hours now, and I've tried turning it on and off, removing batteries and everything. It's stuck in bootloop. I found this was odd, as I have had no dramas with the firmware I've been using. I have not made ANY recent changes to the phone whatsoever, so I can hardly believe it would be my fault.
Now, my question is; how do I fix this without wiping all data and installing a clean ROM? I have a lot of stuff in the internal storage I can't afford to lose, and it's really important to me. A full wipe of all data would not be ideal. I can access recovery mode.
I have tried a suggestion a user here made and made a nandroid backup, did a full wipe, reinstalled the ROM (which allowed me to get out of the bootloop) and then restored the data from the backup (which stuck me back in a bootloop). Still no idea and I really don't want to lose this data. If it's too much effort to fix the loop, is it possible to extract the data from the backups on a PC and manage to restore it to a clean wipe?
Thanks in advance!
Fixed my problem by doing a clean installation, and using Titanium Backup to extract the data from my nandroid backup. It was quite a simple solution, really. No idea why no one seemed to suggest it, though.
Oh well, my problem is solved.
Been using the Toolkit 1.9.8 to root and unlock my att nexus 6. Seemed to work fine and have been running well for the past few days, however after a backup attempt (nandroid) the phone is stuck in a boot loop (spinning dots). Any tips to help me get it unstuck? I've rebooted into recovery and wiped the caches. I did successfully create a backup before it started looping so I'm trying to restore from that at the moment.
I just went and did a Nandroid too after running a few days fine after having unlocked and rooted. Now on my first boot I cant get the OS to load, stuck at the spinning dots splash screen too. I left it for about 20 minutes just to make absolutely sure it was stuck. I thought maybe it had to re-compile things or something with ART. IDK, it was a theory anyway.It seemed stuck for sure so I held down all buttons to force a turn off. I then booted into TWRP and restored my nandroid I just made, which I know shouldnt make a difference cause it is the same thing and I didnt wipe anything before anyway, just made a backup. Anyway, I restored the nandroid and tried to boot and it worked fine. Odd, but worth a try for you.
So my phone has been a little buggy for a while now, nothing major, just kind of annoying so I backed it all up, and went to recovery to wipe and fresh install android. The aroma installer got stuck on wiping cache, so after half an hour I rebooted the phone, and tried to just wipe the partitions from the recovery. same thing, got stuck and I had to reboot. the phone wont boot back up so I guess it was able to wipe the system partition at least, I'm 99% sure its the cache partition thats the problem. I tried both twrp and cwm, and nothing. phone is of course unlocked, and s-off as well. as a side note, I sent my phone in a few months back to have the camera fixed, and they said they replaced the motherboard as well, though when I got it back I was able to wipe the phone no problem. Does anyone have any suggestions?
Fixed. Mods please delete this. thanks
I'm trying to restore a backup on my phone, and it's stalled at 27% for the last 30 minutes and wont move. Is there a way to reboot the recovery and try to wipe and reflash a ROM or something?
Apoplectic1 said:
I'm trying to restore a backup on my phone, and it's stalled at 27% for the last 30 minutes and wont move. Is there a way to reboot the recovery and try to wipe and reflash a ROM or something?
Click to expand...
Click to collapse
TWRP sometimes does that. It gets really hot too. What I do is just use the hardware keys and manually reboot into recovery. If I were you just wipe the whole phone and attempt to restore again. You shouldn't have any issues the second time around.
mikeprius said:
TWRP sometimes does that. It gets really hot too. What I do is just use the hardware keys and manually reboot into recovery. If I were you just wipe the whole phone and attempt to restore again. You shouldn't have any issues the second time around.
Click to expand...
Click to collapse
Wiping and then restoring didn't work, stalled in the same place. Wiping, reflashing the ROM and then restoring did for whatever reason.
Thanks for tip!