I installed E on a Galaxy A5 2016 with image e-0.13-p-2020120789008-dev-a5xelte.zip (I think 0.14 was not available, although it is now…) and it works fine. There is also an update (OTA): e-0.14-p-2021012698470, but when I update, it hangs in a bootloop.
Is there some sort of solution for this? Or should I try reinstalling with e-0.14-p-2021012698470-dev-a5xelte.zip ?
Any one with a device where the OTA did not work can you try and do a clean install of the v0.14 and check if that build boots. This would require data backup first.
Wanted to confirm if it is the OTA part that is broken.
I am sure it works on your testing-device, like on every device, but on a daily professional or personal device, a factory reset is a not an anecdotic step
Yes, a factory reset has consequences. But if the device is stuck in bootloop after an OTA update, I try the above revival options first before doing …
Data format removes the encryption and deletes all files stored in the internal memory. This is often the key to a successful installation.
Ok , just modify the firsts lines of your post n*5 please, it could easily be understand as a workaround solution for the OTA fealure more than a test description.
Hi ! I have the exact same issue (A5 2016), but the problem is that I don’t know how to get out of the loop. It keeps showing the samsung logo, then black screen, then logo again, etc. Long press on power button does nothing, same for power + volume up / down…
A suggestion to try is not a workaround solution for me.
You know as well as I do that one and the same action on two same device models do not have to have the same success. Even if there are no component differences on the manufacturer’s data sheet of the device, there may be an unknown associated with a different production date of devices.Only devices with one and the same production date can be considered 100% identical.
I actually reinstalled the e-0.13-p-2020120789008-dev-a5xelte.zip version, so the phone works fine again. I’m still in testing phase and it’s not my main phone, so I don’t mind erasing data so much, although next time I will test some of the other possible fixes.
So I had already downloaded the file. So I tried an install to see if there would be a bootloop as well. Indeed there is also a bootloop after manual install e-0.14-p.
Installing a custom recovery or unlocking the bootloader will erase all data on your device! Take a backup of your data before proceeding!!
So if you read the backup guide it reads:
Backups are fairly large, so if you get an error about there not being enough space, you may have to delete some things on your internal storage or SD card before continuing
So I guess it’s ok the save the backup to internal storage, right? I would think, this might not be smart, because it could be overwritten somewhere in the process, but if the guide says so…
So I backup to internal storage, then follow the install guide:
In TWRP return to main menu, then tap Wipe
Now tap Format Data and continue with the formatting process.
This will remove encryption as well as delete all files stored on the internal storage. Remember to take a backup first. Check Requirements section above.
Return to the previous menu and tap Advanced Wipe.
Select the Cache and System partitions to be wiped and then Swipe to Wipe
I took a backup, so everything should be save, right? I did above steps and after that the backup was gone.
p.s. I guess you could say it is lazy of me to not just use an sd-card which I had laying somewhere, but I was just curious what would happen.