after making a backup of the rom and restoring again, when starting the rom it stays in the logo in a loop and I don't know why. I use orange fox.
Related
i Had Installed MIUI ROM v3.9.6 with Siyah kernel
it was working perfectly, suddenly it freezed & i had to pull out the battery.
After that the mobile dint start, just the CWM is starting & if i try to start the phone, it just freezes on Glowing Samsung logo.
Nothing comes after that.
But if i format the system & do a fresh install of MIUI Rom, it once again Works.
i Took a Backup after this incident.
But even if i restore it freezes on Samsung logo.
i Want the data back, is there any way i could get it ?
Pls. help
Extract the data from the nandroid backup.
Hello,
I'm a rather experienced Android user. Before I flashed my S3 for the first time, I made sure to back up my EFS. After about a year and a flash of the newest ArchiDroid version, I couldn't get any signal all of a sudden. It worked the days before, and I flashed nothing new or installed anything. I read online about what that might have caused, and it seems like the problem of a lost EFS partition was the problem. I restored my EFS, rebooted, and the phone won't turn on now. It is stuck on the flashing "SAMSUNG" logo on start-up. Thinking I did something, I tried to boot into Clockwork recovery, but it only shows the ClockworkMod logo for about a second, then it reboots again. What should I do?
Try flashing a full stock firmware with Odin, but sudden failure could be nand wear.
Thanks for the reply, I flashed stock firmware with Odin. No errors, but I'm still stuck at the flashing "SAMSUNG" logo.
Boot into recovery and factory reset.
Alright, got into recovery.
Got an error: "E:Failed to mount /efs". How do I restore my EFS with my efs.img now?
EDIT: Managed to get my phone back to work, However, still no signal. Mobile data and phoning does not work.
Format the efs partition then restore your backup, check the permissions then factory reset again.
Edit. If your efs backup was really old, ie. efs v1, then you might have to flash a firmware from before EMG4 to get the efs read, then update to 4.3.
Hi!
I am on Xtrestrolite 3.3 Marshmallow and made a Nandroid Restore of this. After that, I see the boot logo and then only a black screen. New installation of a fresh Xtrestrolite via TWRP doesn´t work. Any suggestions?
Assindius said:
Hi!
I am on Xtrestrolite 3.3 Marshmallow and made a Nandroid Restore of this. After that, I see the boot logo and then only a black screen. New installation of a fresh Xtrestrolite via TWRP doesn´t work. Any suggestions?
Click to expand...
Click to collapse
Use Smartswtich To reset Ur phone To factory Settings btw IT will Erase All of ur files
After that u can install twrp Then Flash The rom Again
Best of Luck
I seem to have shot myself in the foot recently. I've been on CM 13 for nearly a year now and I wanted to try out LineageOS for the hell of it since I am planning to get a new phone and I wanted to put LineageOS on that as well. So I downloaded an unofficial build of LineageOS for the G850W and followed some basic instructions: backup with TWRP, wipe with TWRP, and flash both the ROM and OpenGApps with TWRP. All three of these went well and I was able to install LineageOS. Now the problem: I tried restoring my backup (a CM 13 based backup) thinking I could restore some things from that backup and when I went to restart the CM boot screen popped up and I immediately knew I must have messed up. Checking my backup it contained boot, cache, system, EFS, modem, and a couple other folders/partitions that I can't remember off the top of my head. I then simply tried to redo everything again: backup, wipe, flash. While I am able to backup, wipe, and flash, and I am able to proceed past my device's boot screen, the Lineage OS boot screen seems to either be stuck or it is taking a long time. I've waited for 30 minutes with no change and I am sure that shouldn't be the case at all. Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever. I managed to reinstall CM 13 but it's a very buggy install as sometimes it restarts randomly and goes through the "preparing applications" thing upon restart. Furthermore data doesn't seem to work and IMEI info is not found and sometimes in the stock recovery mode it shows that the EFS partition could not be found. Same thing happens when I poke around in ADB, I do not see any EFS partition when I type in the mount command. Clearly I've really messed things up. So would there be some way to fix things considering I do have a backup of things before I messed things up? How would I use my backup to fix everything? Would there be other tools I should be trying? Any help would be appreciated.
Flash original firmware
echo124 said:
Flash original firmware
Click to expand...
Click to collapse
I did: "Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever".
Erase everything on your phone (aftet backup) and flash stock again.
echo124 said:
Erase everything on your phone (aftet backup) and flash stock again.
Click to expand...
Click to collapse
I've done that as well already, still the same issue.
:fingers-crossed:Flash stock, flash same version twrp used to backup, flash same version of cm 13 used on backup, try restore.
As the title says I always get a bootloop into recovery when the restore process finishes.
I tried everything, flashing the same rom as in the backup before restoring, however it never boots normally.
As I am on a stock MIUI 13 I flashed the stock image and then restored the backup, still a bootloop into recovery.
No matter what I do I am unable to restore my TWRP backup, so every time I want to try a new ROM I end up reinstalling everything from scratch.
Is it because my data is encrypted, or dynamic partitions? This never happened with any of my previous phones, is it possible to restore a backup on Mi10?
alfaholic said:
As the title says I always get a bootloop into recovery when the restore process finishes.
I tried everything, flashing the same rom as in the backup before restoring, however it never boots normally.
As I am on a stock MIUI 13 I flashed the stock image and then restored the backup, still a bootloop into recovery.
No matter what I do I am unable to restore my TWRP backup, so every time I want to try a new ROM I end up reinstalling everything from scratch.
Is it because my data is encrypted, or dynamic partitions? This never happened with any of my previous phones, is it possible to restore a backup on Mi10?
Click to expand...
Click to collapse
Backups and restore on the TWRP with some phone models does not work correctly either because it does not decrypt or is too old compared to the rom or you try to restore an older rom version on a more recent rom and sometimes the reverse also does not work (because of the system).
Try a more recent Twrp (just in case) but anyway the restoration will not be done with a more recent Twrp.
If you are on MIUI micloud works relatively well but obviously you can only restore the data not the system.
https://androidfilehost.com/?w=files&flid=318277
alfaholic said:
As the title says I always get a bootloop into recovery when the restore process finishes.
I tried everything, flashing the same rom as in the backup before restoring, however it never boots normally.
As I am on a stock MIUI 13 I flashed the stock image and then restored the backup, still a bootloop into recovery.
No matter what I do I am unable to restore my TWRP backup, so every time I want to try a new ROM I end up reinstalling everything from scratch.
Is it because my data is encrypted, or dynamic partitions? This never happened with any of my previous phones, is it possible to restore a backup on Mi10?
Click to expand...
Click to collapse
try flashing miui 12 rom first, then restore twrp back up (format data also before restoring)
and chose the latest version of twrp for android 11 or 12 (depends on your Rom)
maybe it will work