Hello guys, I had this zenfone max pro for almost two years and last week I decided to change the OS and then installed Lineage OS 18.1.
Yesterday appeared an update screen on my phone because there was a new version of the lineage OS. Then it asked if I wanted to create a backup and I clicked yes and then the phone started updating. The problem happened because after a while updating (the lineage ball was bouncing from left to right) appeared a screen of recovery saying:
"Can't load Android System. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". Version 18.1 (20210525).
Obviously, I clicked on try again a few times but it loads for a while and gets me back to this screen.
Is there a solution for this where I don't need to perform a factory data reset?
dfantonio said:
Hello guys, I had this zenfone max pro for almost two years and last week I decided to change the OS and then installed Lineage OS 18.1.
Yesterday appeared an update screen on my phone because there was a new version of the lineage OS. Then it asked if I wanted to create a backup and I clicked yes and then the phone started updating. The problem happened because after a while updating (the lineage ball was bouncing from left to right) appeared a screen of recovery saying:
"Can't load Android System. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". Version 18.1 (20210525).
Obviously, I clicked on try again a few times but it loads for a while and gets me back to this screen.
Is there a solution for this where I don't need to perform a factory data reset?
Click to expand...
Click to collapse
did u already try to dirty flash the lineage OS 18.1 again to ur phone ?
I ended up making a fresh install and it worked, but thanks for the help
Related
My i9505 was running stock KitKat from Samsung and I tried to install CM13 ROM.
So I used Odin to root the phone and installed TWRP 2.8.6.0. After that I flashed the CM13 ROM and the Gapps Nano.
I got as far as rebooting into CM13. But then the "Google Play Store has stopped working" message keeps popping up starting from the initial setup phase. I ignored the message and went on to setup the wifi but couldn't progress any further. The wifi was detected and connected but then it was stuck on the Checking Connection/Software Update step.
I tried to reflash the rom and gapps again to no avail. The third time to Format Data from TWRP before reflashing - still didn't make a difference.
What's worst is now I cannot even get into TWRP! Whenever I press Vol Up + Power + Home, it will show the small 'entering recovery' message momentarily on the top left corner but then it phone simply restarted again.
I tried re-flashing TWRP using Odin, but still didn't work.
I'm stuck now, cannot get into the OS nor the recovery. Any suggestion as to what to do?
Thank you.
vizavalk said:
My i9505 was running stock KitKat from Samsung and I tried to install CM13 ROM.
So I used Odin to root the phone and installed TWRP 2.8.6.0. After that I flashed the CM13 ROM and the Gapps Nano.
I got as far as rebooting into CM13. But then the "Google Play Store has stopped working" message keeps popping up starting from the initial setup phase. I ignored the message and went on to setup the wifi but couldn't progress any further. The wifi was detected and connected but then it was stuck on the Checking Connection/Software Update step.
I tried to reflash the rom and gapps again to no avail. The third time to Format Data from TWRP before reflashing - still didn't make a difference.
What's worst is now I cannot even get into TWRP! Whenever I press Vol Up + Power + Home, it will show the small 'entering recovery' message momentarily on the top left corner but then it phone simply restarted again.
I tried re-flashing TWRP using Odin, but still didn't work.
I'm stuck now, cannot get into the OS nor the recovery. Any suggestion as to what to do?
Thank you.
Click to expand...
Click to collapse
Format Data from twrp sometime corrupts the file system and brick the phone. (It's happened to me once)
The best way is to flash official firmware via odin and start from there.
I see - I'll try re-flashing the official rom. Btw, would you recommend CWM recovery instead then? Honestly, I'm not very proficient with this whole thing. The reason why I formatted was because I still could see all of my old folders in the phone memory. So I thought Factory Reset didn't really clean up my old rom data.
What do I have to do if I want to start with a really clean slate with CM13 (after reflashing the official one first)?
Also, I still have the issue of CM13 setup being stuck at the Software Update step (right after Wifi setup). Any clue why that happened?
Thanks for taking the time to reply.
vizavalk said:
I see - I'll try re-flashing the official rom. Btw, would you recommend CWM recovery instead then? Honestly, I'm not very proficient with this whole thing. The reason why I formatted was because I still could see all of my old folders in the phone memory. So I thought Factory Reset didn't really clean up my old rom data.
What do I have to do if I want to start with a really clean slate with CM13 (after reflashing the official one first)?
Also, I still have the issue of CM13 setup being stuck at the Software Update step (right after Wifi setup). Any clue why that happened?
Thanks for taking the time to reply.
Click to expand...
Click to collapse
CWM is outdated. Your best bet is TWRP. Try version 3.0.0.
Factory reset doesn't wipe your internal memory, if that's what you mean, you will have to do it manually.
Also, I recommend wiping data, cache, dalvik and system partitions manually from the advanced wipe menu. Factory reset only wipes data and caches, not system.
Oh, and about that stuck at setup issue, just skip that step if possible, you can still change that crap later
If you are unable to set up the ROM, you could flash back to a completely stock ROM and start over.
OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.
vizavalk said:
OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.
Click to expand...
Click to collapse
The sd card has nothing to do with it.
Sometimes gapps don't work on certain roms.
Just try another package.
If you use A-Gapps, the whole first time setup step will be skipped altogether. So that means that you won't run into the risk of getting stuck at that step again.
Or, after flashing the rom, you could use the recovery file manager to delete the setupwizard.apk after you flashed gapps. That should also prevent the initial setup process from initializing at first boot.
vizavalk said:
OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.
Click to expand...
Click to collapse
You probably used Opengapps. That also gives me a lot of errors.
Use Bankgs Gapps instead. They always work for me.
http://download.dirtyunicorns.com/files/gapps/banks_gapps/
GDReaper said:
The sd card has nothing to do with it.
Sometimes gapps don't work on certain roms.
Just try another package.
If you use A-Gapps, the whole first time setup step will be skipped altogether. So that means that you won't run into the risk of getting stuck at that step again.
Or, after flashing the rom, you could use the recovery file manager to delete the setupwizard.apk after you flashed gapps. That should also prevent the initial setup process from initializing at first boot.
Click to expand...
Click to collapse
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
Lennyz1988 said:
You probably used Opengapps. That also gives me a lot of errors.
Use Bankgs Gapps instead. They always work for me.
http://download.dirtyunicorns.com/files/gapps/banks_gapps/
Click to expand...
Click to collapse
There are two files - one says Dynamic. But the file sizes are exactly the same. Is there any difference?
vizavalk said:
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
There are two files - one says Dynamic. But the file sizes are exactly the same. Is there any difference?
Click to expand...
Click to collapse
Not that I know. Just pick the one without Dynamic.
vizavalk said:
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
Click to expand...
Click to collapse
The initial setup process is related to gapps. And I don't recall there being any software update requests during the initial setup. It tells me to wait while it scans for network and WiFis, but I always skip those steps.
Open gapps sometimes work and sometimes they don't. It varies from day to day, since they are updated daily.
Just find a gapps package that works and stick to it until another version of android.
I just want to report back that my CM13 works perfectly with Banks GApps. Thanks to everyone who has helped!
A little bit of background.
Prior to this problem I was running dirty unicorns and elementalx kernel. Given that lately I had some freezing issues I decided that iro was time to update my ROM. Being the first time that I manually update a ROM and not having found anything online I thought (dumb decision) that all I had to do was to flash the most recent version. After I did that the phone did an app optimization (idk if that's how it's called, basically it optimised all the apps for the new version of the ROM) . After that the phone wasn't booting up, the dirty unicorns loading screen was running for half an hour and nothing happened so I restated the phone. When it asked for my sequence a message popped up "it looks like your vendor image is obsolete". The phone still wasn't booting up so I decided to restart once again and install the latest vendor image. After that the phone wasn't booting up so I decided to do a backup with twrp (version 3.0.0.0) and do a factory reset.
Plot twist the twrp decryption sequence (that worked 10 minutes before) now wasn't working so I had no way to access any of the phone's files.
Basically the phone won't turn on and I have no way of accessing it's files
I'd try a factory reset but there are some photos and whatsapp messages that are important to me and I'd rather not lose them.
Any tips?
Apologies for my terrible English
JustJohnItalia said:
A little bit of background.
Prior to this problem I was running dirty unicorns and elementalx kernel. Given that lately I had some freezing issues I decided that iro was time to update my ROM. Being the first time that I manually update a ROM and not having found anything online I thought (dumb decision) that all I had to do was to flash the most recent version. After I did that the phone did an app optimization (idk if that's how it's called, basically it optimised all the apps for the new version of the ROM) . After that the phone wasn't booting up, the dirty unicorns loading screen was running for half an hour and nothing happened so I restated the phone. When it asked for my sequence a message popped up "it looks like your vendor image is obsolete". The phone still wasn't booting up so I decided to restart once again and install the latest vendor image. After that the phone wasn't booting up so I decided to do a backup with twrp (version 3.0.0.0) and do a factory reset.
Plot twist the twrp decryption sequence (that worked 10 minutes before) now wasn't working so I had no way to access any of the phone's files.
Basically the phone won't turn on and I have no way of accessing it's files
I'd try a factory reset but there are some photos and whatsapp messages that are important to me and I'd rather not lose them.
Any tips?
Apologies for my terrible English
Click to expand...
Click to collapse
The best thing to do is this guide. http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page384. Just go full stock without formating the internal. Flash twrp and see if you can get your photos. Next time back your photos up with Google photos if available in your area. Good luck
JustJohnItalia said:
A little bit of background.
Prior to this problem I was running dirty unicorns and elementalx kernel. Given that lately I had some freezing issues I decided that iro was time to update my ROM. Being the first time that I manually update a ROM and not having found anything online I thought (dumb decision) that all I had to do was to flash the most recent version. After I did that the phone did an app optimization (idk if that's how it's called, basically it optimised all the apps for the new version of the ROM) . After that the phone wasn't booting up, the dirty unicorns loading screen was running for half an hour and nothing happened so I restated the phone. When it asked for my sequence a message popped up "it looks like your vendor image is obsolete". The phone still wasn't booting up so I decided to restart once again and install the latest vendor image. After that the phone wasn't booting up so I decided to do a backup with twrp (version 3.0.0.0) and do a factory reset.
Plot twist the twrp decryption sequence (that worked 10 minutes before) now wasn't working so I had no way to access any of the phone's files.
Basically the phone won't turn on and I have no way of accessing it's files
I'd try a factory reset but there are some photos and whatsapp messages that are important to me and I'd rather not lose them.
Any tips?
Apologies for my terrible English
Click to expand...
Click to collapse
To update a ROM all you usually need to do is flash the newer version, but you also need to flash the newer vendor.img of the updated ROM is based on a newer Google build. Failure to do this is what caused the "it looks like your vendor image is obsolete" message to appear. I'm guessing you know this though as you went on to flash it later.
Not sure what happened with TWRP but you've done something else wrong at some point. Best idea (as pointed out above) is to flash the factory images. You can try it without formatting userdata in order to retrieve whatever it is that's important on your storage, but once you've retrieved whatever you need (if you even can) you'll need to format it because you really need to start fresh.
I took out my old Note 3 to upgrade the Lineage OS firmware to latest version and start using it.
I made a nandroid backup of whatever old OS firmware was inside.
Downloaded the latest Lineage OS firmware & gapps and then flashed them via TWRP.
When the phone boots up the first time, it keeps giving me "Google Services framework" error constantly. If I tap cancel on that error, it pops up right 0.5 seconds later. I am unable to proceed forward in the initial setup because that error keeps popping up.
I then tried to factory reset and reflash the nandroid backup. Now when the old backup boots, it gives me an error for a few apps that crashed on boot and then the OS itself crashes and gets stuck in a bootloop.
I've tried flashing new OS, reflashing old backup, process 2 or 3 times. It's the same errors and issues
Does anyone know what I can do now?
Also another small hurdle - The USB port is not functioning, everything and anything I can do now is via mounting the SD card and TWRP. Unless there is an alternate I am unaware of.
Thanks for reading!!
With a faulty USB port, you're missing the most easy and obvious step to fix this, flash via Odin.
I recommend getting your USB port fixed. (Is it from your PC/Laptop or phone that is faulty?) because you really need it for this and for future things that you may want to try.
Hi, first thing I'd like to say is that I used phones with other OS since 2015, first one was Cyanogenmod on HTC ONE (M7), loved the experience so when the time for new phone came I had no doubt that my next phone need to be the one that utilize LineageOS. For the three last years I used Lenovo P2 with LineageOS on it. I'm responsible for OS changes on all my phones and untill recently I had no issues with custom roms.
I am still boggled what happened. I installed LineageOS 17.1 on Redmi Note 7, all according to the LineageOS installation guide, and everything worked just perfectly.
Used redmi for 2 weeks but I had a chance to get on the cheap Asus Zenfone 6, so I grabbed the opportunity and use now Zenfone 6 with LineageOS.
The problem is I left 80% charge on Redmi note 7, shut it down and placed it comfortably back in a box for a week. After 7 days I tryed to boot the phone to reset it and give it as a gift but after redmi logo phone go black.
I could open Lineage recovery so I tryed to recover LineageOS, but result was the same, black screen after redmi logo no matter how long I wait.
So I tryed to reinstall LineageOS according to the guide, same result as above.
I though maybe there is something wrong with LineageRecovery so I changed to TWRP, went trough the installation of fresh batch of LineageOS from site this time using TWRP and had the same result phone dead after redmi logo.
Then I tryed to install MIU from xiaomi, everything went according to the manual but result was the same as mentioned above, well except for the part where I did a blunder and now the phone is locked back again, but still die after redmi logo. Oryginal Xiaomi Recovery don't help either.
Did anyone else expierience something like that?
And please correct me if I'm wrong but I think it must be a hardware issue not the software issue, right?
Arkilius said:
... And please correct me if I'm wrong but I think it must be a hardware issue not the software issue, right?
Click to expand...
Click to collapse
Did you format (not just wipe) the data partition? Try formatting the data partition (or try flashing a fastboot MIUI 11 Pie ROM with the Mi Flash tool).
DarthJabba9 said:
Did you format (not just wipe) the data partition? Try formatting the data partition (or try flashing a fastboot MIUI 11 Pie ROM with the Mi Flash tool).
Click to expand...
Click to collapse
I did format data properly, system and cache partition as it is one of the steps in LineageOS official instalation guide, before every system reinstall. I even tryed after moving to TWRP changing partition format from f2fs to ext4 but nothing helped.
Now phone is oemlocked and without opening it I can't do anything, just were wondering if anyone else had LineageOS dying on them out of nothing, even if it worked for week or two perfectly.
Arkilius said:
I did format data properly, system and cache partition as it is one of the steps in LineageOS official instalation guide, before every system reinstall. I even tryed after moving to TWRP changing partition format from f2fs to ext4 but nothing helped.
Now phone is oemlocked and without opening it I can't do anything, just were wondering if anyone else had LineageOS dying on them out of nothing, even if it worked for week or two perfectly.
Click to expand...
Click to collapse
Please be aware that Format data is different thing to Wipe data
RaizenrG said:
Please be aware that Format data is different thing to Wipe data
Click to expand...
Click to collapse
"Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one)."
Factory Reset, then Format data / factory reset are 2 separate steps not one.
Did step by step installation of LineageOS from Official LineageOS instalation guide for Redmi 7 Note.
Later on TWRP I did almost every format or wipe there is including repairing or changing partition format, nothing helped.
Still be nice to know if anyone had the same experiance of working LineageOS dissapearing from device after phone being off for full week?
I have a samsung s8 950f. I put havoc-3.9 on it and everything was great. But then I decided to encrypt the date section. I already carried out such an operation on another samsung (9505) and then everything ended in an hour quite well. Now, after the start of encryption, the screen turned off, the phone did not react in any way,despite the connected charging, the indicator did not light up, and so on. I waited like this for more than three hours and then decided to restart my phone. After rebooting, the phone demanded a pattern for decryption (what was needed), but then the interface constantly crashed (problems). It doesn't matter, I thought and did a full reset.After that, the phone refused to start at all, showing the inscription "custom binary blocked by oem lock". Google suggested that a complete flashing with the original firmware is needed. Since I'm using ubuntu, I flashed it using heimdall. Everything went well and I again saw the original samsung firmware. But I need havoc so I installed TWRP again. But now this recovery does not see the date section. I can install havoc, but it does not start because it requires formatting the date, it turns out a vicious circle. What should I do, I don't like the official samsung software.
The problem was solved this way: installing twrp, flashing havoc, installing recovery from samsung, clearing the date, and again installing twrp. After these manipulations, I got what it was before encryption.