Hi,
After some hard work I finally got TWRP and LineageOS installed on my Galaxy A5. It now works properly except that when I try to turn it off, the screen becomes black for a few seconds and then it reboots.
Did anyone encountered this problem before? Do you have an idea of a possible fix?
gustavecoste said:
Hi,
After some hard work I finally got TWRP and LineageOS installed on my Galaxy A5. It now works properly except that when I try to turn it off, the screen becomes black for a few seconds and then it reboots.
Did anyone encountered this problem before? Do you have an idea of a possible fix?
Click to expand...
Click to collapse
Same problem here. Have you found a solution?
Hi,
Yes, I finally found a solution. The problem was that I was trying to install Lineage OS 14.1 (based on Android 7) on a phone where Android 8 was installed.
At that point, you have two solutions:
Install a stock version of Android 7 before flashing LineageOS
Find a version of LineageOS 15 that works on Galaxy A5.
I chose option 1 and it did work perfectly.
Thank you. I'll try that as soon as I can. (I will also choose option 1.)
When i try to install a stock version of Android 7 with Odin, it fails with this message on the phone in download mode : "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 7, BINARY: 4". Any idea ?
Related
Hello everyone I have a mini model GT-i9195L and it turns out that it would happen to another android but it does not work for an error 7, then try to flash it because it was in logo and I appeared the problem of the image and I had flashed Times Previous and it worked for a time that I always have to pass an android 6 with a line so in android 4 so this recently restarted is blocked by nothing and freezes, or that the error I have, plays flahear the cel with 3 files But where I get them and their son.
Error appears could not make the normal boot made clean and all with recovery but nothing.
Sty15 said:
Hello everyone I have a mini model GT-i9195L and it turns out that it would happen to another android but it does not work for an error 7, then try to flash it because it was in logo and I appeared the problem of the image and I had flashed Times Previous and it worked for a time that I always have to pass an android 6 with a line so in android 4 so this recently restarted is blocked by nothing and freezes, or that the error I have, plays flahear the cel with 3 files But where I get them and their son.
Error appears could not make the normal boot made clean and all with recovery but nothing.
Click to expand...
Click to collapse
not sure if I follow you but you can get rom from sammobile
https://www.sammobile.com/firmwares/database/GT-I9195L/
I guess you flashed wrong rom before
Hopefully someone can help me its for X800 china version
I tried to open the phone after 2 years, and tried to update it with official ROM from http://123.59.123.195/cn/download/phone/30
After updating, when I tried to reboot it, it got stuck on this black screen with a small penguin, and then after few seconds, it restarts back with the same black screen and the penguin.
I can still access TWRP recovery if I press the vol up button while it is restarting. I tried installing different custom ROM, but to no avail. I would really appreciate if you can help me fix my phone
EDIT: RESOLVED
It was looping on fastboot mode (the penguin icon)
Tried installing an older version, lollipop based, from Cuoco92 (from here https://androidfilehost.com/?w=files&flid=57901) and it worked again (thanks Cuoco92!)
Upon reading online, it seems the partition may have been corrupted since I'm trying to flash a MM ROM from a lollipop ROM ,without updating the firmware
I found out that I need to update the firmware to 16S, which I downloaded from this thread: https://forum.xda-developers.com/le...ollipop-marshmallow-firmware-x800-cn-t3463736
(thanks hugoprh!)
After that I am able to install any ROM, from MM and up (was able to install Lineage OS 14.1)
lancelotconquista said:
Hopefully someone can help me its for X800 china version
I tried to open the phone after 2 years, and tried to update it with official ROM from http://123.59.123.195/cn/download/phone/30
After updating, when I tried to reboot it, it got stuck on this black screen with a small penguin, and then after few seconds, it restarts back with the same black screen and the penguin.
I can still access TWRP recovery if I press the vol up button while it is restarting. I tried installing different custom ROM, but to no avail. I would really appreciate if you can help me fix my phone
EDIT: RESOLVED
It was looping on fastboot mode (the penguin icon)
Tried installing an older version, lollipop based, from Cuoco92 (from here https://androidfilehost.com/?w=files&flid=57901) and it worked again (thanks Cuoco92!)
Upon reading online, it seems the partition may have been corrupted since I'm trying to flash a MM ROM from a lollipop ROM ,without updating the firmware
I found out that I need to update the firmware to 16S, which I downloaded from this thread: https://forum.xda-developers.com/le...ollipop-marshmallow-firmware-x800-cn-t3463736
(thanks hugoprh!)
After that I am able to install any ROM, from MM and up (was able to install Lineage OS 14.1)
Click to expand...
Click to collapse
sir can you help me with it my Le Max is showing penguin and then black screen i cant able to access twrp please help me
Is there a problem with encryption with LOS16?
On trying to encrypt a brand new install on a 3T it goes to the black encryption screen with green android logo and then just says Android is starting. Encryption doesn't happen but Magisk is removed.
Can anyone help?
Thanks
nimicitor said:
Is there a problem with encryption with LOS16?
On trying to encrypt a brand new install on a 3T it goes to the black encryption screen with green android logo and then just says Android is starting. Encryption doesn't happen but Magisk is removed.
Can anyone help?
Thanks
Click to expand...
Click to collapse
The same happens to me in Xiaomi Mi 8.
The encryption fails.
Same on Samsung Galaxy A3 (2017) with LOS 16.0 (McFy)
Same Issue JFLTEXX
Same issue with latest nightly
nimicitor said:
Is there a problem with encryption with LOS16?
On trying to encrypt a brand new install on a 3T it goes to the black encryption screen with green android logo and then just says Android is starting. Encryption doesn't happen but Magisk is removed.
Can anyone help?
Thanks
Click to expand...
Click to collapse
Similar problem on gts210vewifi (samsung tablet s2 9.7" wifi), type in password, get green robot, black screen and back at startup screen to type password to unlock. And still not encrypted. Using latest nightly.
Related issue: 2361 (on los gitlab)
I updated to android 10 and tried following the tutorial to get TWRP on it, but everytime I try to launch TWRP it hangs on the logo.
Is it that TWRP has to be updated for a70 android 10? or am i doing something wrong?
TWRP does not work with Android 10 at the moment for the A70. I do not know about other phones. Android 10 changed the way they use recovery so it will take a while. https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Hi, I also had the same problem, the logo screen remains fixed once I enter Recovery! We have to wait for the developers to find a solution in this regard. Regards! ??
Revert back to android 9 as android 10 is unstable for A70.
But if its working fine for you then wait for twrp to get updated
I got an miui 12.0.1.0.RCOINXM update after which phone started to randomly reboot, especially when there was some drop down notification or call.
So I decided to install custom rom. I tried to install Pixel Experience Recovery but that was giving "System is destroyed press power button to shutdown". I fixed it by flashing orange fox but using orange fox pixel experience got in boot loop. So I installed Pixel Experience Recovery from orange fox recovery and the used ADB to sideload pixel experience which worked and I setting up my phone but suddenly I get a notification and the phone reboots which is similar behavior to miui 12.0.1.0.RCOINXM. is there some thing else that I can change like kernel or something which can resolve this problem.
I am using PixelExperience_ginkgo-11.0-20211216-1154-OFFICIAL.zip
pls help
PS : the phone remains in boot loop if not plugged in charging and idk why but fastboot logo didn't change to pixel experience's
GundamSierra said:
I got an miui 12.0.1.0.RCOINXM update after which phone started to randomly reboot, especially when there was some drop down notification or call.
So I decided to install custom rom. I tried to install Pixel Experience Recovery but that was giving "System is destroyed press power button to shutdown". I fixed it by flashing orange fox but using orange fox pixel experience got in boot loop. So I installed Pixel Experience Recovery from orange fox recovery and the used ADB to sideload pixel experience which worked and I setting up my phone but suddenly I get a notification and the phone reboots which is similar behavior to miui 12.0.1.0.RCOINXM. is there some thing else that I can change like kernel or something which can resolve this problem.
I am using PixelExperience_ginkgo-11.0-20211216-1154-OFFICIAL.zip
pls help
PS : the phone remains in boot loop if not plugged in charging and idk why but fastboot logo didn't change to pixel experience's
Click to expand...
Click to collapse
PixelExperience_ginkgo-11.0-20211216-1154-OFFICIAL.zip is for the original Redmi Note 8 (ginkgo)
Judging by your MIUI version (if i remember correctly the new Note 8 ships with MIUI 12.5), you are in the wrong forum, the original Note 8 forum is here.
OR
You have installed a Note 8 (ginkgo) rom to a Note 8 (2021) (biloba) witch is not compatible with the new note 8.
Thanks for reply Aninuscsalas but No my redmi note 8 is 2019 edition and even after install correct roms even downgrading the same issue persists
I think as my device is A partition only devices [Non-A/B] there might have been something wrong during the update process and that might have made some problems.
Here is my partition table can anyone pls confirm if this is Ok?[in attached]
GundamSierra said:
Thanks for reply Aninuscsalas but No my redmi note 8 is 2019 edition and even after install correct roms even downgrading the same issue persists
I think as my device is A partition only devices [Non-A/B] there might have been something wrong during the update process and that might have made some problems.
Here is my partition table can anyone pls confirm if this is Ok?[in attached]
Click to expand...
Click to collapse
Sorry i can't help. (I know almost nothing about phones.)
But if your phone is the 2019 version then you are in the wrong forum.
Maybe someone in that forum can help:
https://forum.xda-developers.com/c/redmi-note-8.9200/