LineageOs reinstall fails. Bootloop - Honor 9 Lite Questions & Answers

I installed LineageOS successfully. But I wanted to try Omnirom too. I made a full wipe in TWRP and then followed the OpenKirin Guide again. But after reboot i couldnt access the EMUI Factory Reset Screen (see Image of Point 14 in the guide). But the phone wont turn off anymore. It just restarts. I can still access Bootloader (Phone and FPR unlocked) when the phone is connected via usb and the TWRP screen with all options (install, wipe, ...). I tried to install LineageOS again but failed.

Reflash EMUI (you need to remember which version you were on). Then try LINEAGEOS or whatever ROM you want

PalakMi said:
Reflash EMUI (you need to remember which version you were on). Then try LINEAGEOS or whatever ROM you want
Click to expand...
Click to collapse
I read a lot of posts here and finally I used HurUpdater. Worked well!
Do you know which of the custom roms comes without any google apps for h9l?

Apfelwurst said:
I read a lot of posts here and finally I used HurUpdater. Worked well!
Do you know which of the custom roms comes without any google apps for h9l?
Click to expand...
Click to collapse
From what I know, none

Related

Help with Treble ROMs

I have the PRA-LX1 with already unlocked bootloader and got it rooted with TWRP + Magisk before the last OTA.
I'm not a beginner with rooting this phone but only got Problems with installing any Treble Rom (tried Lineage and Aosp) and every try ended with a bootloop I don't know what I'm doing wrong.
So please can anyone give me a step by step instruction?
Which Treble Rom is a good one and recommended for this phone?
Which TWRP do I need?
And how exactly do I flash them correctly? What do I wipe?
Sorry for this noob questions but I failed so many times with Treble and don't want to do the reinstall with erecovery for the 10000 time :crying:
Thanks
Try to install the stock recovery and ramdisk.
+1
I also have this problem. Wich TWRP works with treble roms? i tryed everything and everytime i get a boot loop.
Please help.
After I flashed a treble gsi, I need to flash stock recovery?
Atiqx said:
After I flashed a treble gsi, I need to flash stock recovery?
Click to expand...
Click to collapse
Yes. if u still get bootloop flash stock recovery and ramdisk first then flash gsi. make sure u factory reset on stock recovery after u flash gsi.
ppdr07 said:
Try to install the stock recovery and ramdisk.
Click to expand...
Click to collapse
ppdr07 said:
Yes. if u still get bootloop flash stock recovery and ramdisk first then flash gsi. make sure u factory reset on stock recovery after u flash gsi.
Click to expand...
Click to collapse
And which TWRP should I use for flashing?.. And how can I flash GSI with stock?
That makes no sense to me sorry
Flash via fsstboot. Stock recovery and ramdisk flash via fastboot. Im not using twrp so idk.
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
U can see a tutorial at xda how to flash gsi without twrp. Google it.
ppdr07 said:
Flash via fsstboot. Stock recovery and ramdisk flash via fastboot. Im not using twrp so idk.
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
U can see a tutorial at xda how to flash gsi without twrp. Google it.
Click to expand...
Click to collapse
I googled it, pretty much every source says that you require a custom recovery in order to flash a GSI or any custom ROM.
XDA XILFY said:
I googled it, pretty much every source says that you require a custom recovery in order to flash a GSI or any custom ROM.
Click to expand...
Click to collapse
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ u will find Flash GSI without TWRP
ppdr07 said:
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ u will find Flash GSI without TWRP
Click to expand...
Click to collapse
Oh, well that's pretty cool. Either way, I just tried flashing Official Resurrection Remix GSI with no luck. Stock recovery, attempted to flash through fastboot and it just gives me a bootloop, exactly like TWRP does. Followed the guide you linked to etc, just keeps rebooting.
XDA XILFY said:
Oh, well that's pretty cool. Either way, I just tried flashing Official Resurrection Remix GSI with no luck. Stock recovery, attempted to flash through fastboot and it just gives me a bootloop, exactly like TWRP does. Followed the guide you linked to etc, just keeps rebooting.
Click to expand...
Click to collapse
Go to openkirin.net/download download the rr beta 3
Atiqx said:
I have the PRA-LX1 with already unlocked bootloader and got it rooted with TWRP + Magisk before the last OTA.
I'm not a beginner with rooting this phone but only got Problems with installing any Treble Rom (tried Lineage and Aosp) and every try ended with a bootloop I don't know what I'm doing wrong.
So please can anyone give me a step by step instruction?
Which Treble Rom is a good one and recommended for this phone?
Which TWRP do I need?
And how exactly do I flash them correctly? What do I wipe?
Sorry for this noob questions but I failed so many times with Treble and don't want to do the reinstall with erecovery for the 10000 time :crying:
Thanks
Click to expand...
Click to collapse
Well, I finally got it all working.
You know the risks, don't blame me if something goes wrong, I did these exact steps to manage to root my phone without breaking it. C432, Dual SIM and PRA-LX1.
Have everything stock before following this short guide: Firmware, all stock recovery etc.
Installing the ROM and GApps
First, download necessary GSI files.
(Personally I got Official Oreo Resurrection Remix, here).
(Although you could find yourself using virtually any other GSI, I like the look and feel of RR, though I'll be changing my boot animation with root). Many people would probably recommend you to use something like an AOSP, or LOS which I was also considering on installing. They may also come bundled with GApps, which would negate the later need for installation or download of separate GApps.
This may include GAPPS but you should understand this from the GSI page, so for example on RR I had to download both the latest base ROM .img and the micro GApps.
So to do this I had to use the right architecture (For the P8 Lite 2017, this is ARMx64, do your good research, since my problem was getting this wrong with my PRA-LX1 (Mine was A-ONLY), this stands for the base ROM and GApps.
After this I actually didn't use TWRP as user @ppdr07 advised. I followed the guide he linked us to and did as so, without following the -u command, since it wasn't working for me (didn't affect anything, try it, if it doesn't work, just take that bit out).
The ROM ended up installing and posting through, everything set up perfectly.
After this I was like "Huh, so what now? How am I to flash GApps on this without TWRP?". I went for it and booted into fastboot where I flashed Askuccio's TWRP for hi6250 devices. At this point I worried that the ROM wouldn't post again - though it did, so from there I enabled dev options and switched on advanced power options just for ease of usage. From there I rebooted straight to recovery which posted fine, too.
At this point, you need to flash the GApps. Go for the one that the original GSI page recommends. Flash it to the System Image partition. Don't wipe anything. At this point I recommend that if you realise that you forgot to transfer any files to the SD card, you should do it from the system. It works better compared to the MTP on TWRP. Either way, that should work properly. Now, reboot the system, and it should work perfectly.
Enjoy, it took me months to get to this point lol
Rooting Your New ROM With Magisk
(Before installing this consider the other root options. I believe there's SuperSU and another possibly that I'm less aware of. Either way, in my opinion Magisk comes with the most benefits so I'll be helping you out with that).
After this I ended up flashing Magisk in order to use Snapchat and other apps similar to it. Firstly you'll want to set up Google stuff which has been newly added to the system, and then you'll want to go to chrome and download the Magisk Manager .apk from here. The main and most reliable place to get it is from the creator's project page found here, all main links stand out in the middle fairly well.
(Remember to enable downloading of unknown apps for Chrome in it's app settings, otherwise it won't download or install.)
If it still doesn't work at this point, I ended up holding down on the Magisk Manager link and pressing Download Link (or something to that effect). From this point just install it as you would any other out-of-store app.
Now, you'll need to download these two files from the Magisk page onto your computer: Stable Installer and Uninstaller. Next, while booted into Android, copy them over to either Internal or External storage and when it's done, reboot into TWRP again, either by advanced power menu or using the button commands for recovery. Personally, I think I need the power options with this phone.
In TWRP, simply go to Install, navigate to /externalsd/***[WHEREVER YOU PLACED YOUR MAGISK FILES]***, then install the Magisk installer .zip. If unchanged, the filename should be something like "Magisk-v17.1.zip". Install it, then give rebooting a go. Hopefully it'll post, if not, go back into TWRP and run the Uninstaller .zip, it's saved me a bunch of times.
Unblocking Apps That Say Something Like "Your Phone is Rooted or Modified, no access blah blah blah..."
(Snapchat is the example used here. It won't work upon login if you don't follow this step. Some apps don't work with this alone however, though somebody may have produced a separate guide or easily installable Magisk module with a solution for it. One that won't be fixed singularly with Magisk Hide is Google Pay).
After posting, if you need to unblock Snapchat or something, go to Magisk Manager (which should now be more green), open the top left context menu, tap on Magisk Hide, and search "snap" until you see the Snapchat logo pop up, then select it, then back out with the back button. It should stay selected in Magisk, and the app should now be usable and shouldn't give you any annoying errors, if not give it a reboot and see if it's solved.
Good luck!

Trouble flashing any custom ROM

Edit: Figured out the missing step! Wasn't mentioned on any guide I read, or if it was, I'm afraid it wasn't clear :'( Hopefully this guide helps other people though, I've highlighted the step I added!
Hi Mi9 Forum!
Longtime S7 user here, I've flashed (literally) hundreds of roms over the years, but unfortunately lost my device so switched to a Mi9 (Which is ****ing huge!)
Earlier today, after the (arduous 1-week wait) I unlocked my phone (now reads unlocked on boot up), and set about testing three different roms.
From what I understood, I needed to flash a Vendor image before the actual rom itself, so I installed TWRP, flashed the vendor image, then tried flashing the ROM, but alas, I got kicked back to TWRP.
The steps I've taken a listed below, perhaps I've missed something obvious, or not so obvious, but any help would be appreciated!
UNLOCKING
Unlocked phone with Mi tool (Reads unlocked on bootscreen now)
Booted into Fastbook (Vol down + Power)
Plugged in
Used MinimalADB to push TWRP (3.3.1.42) onto my device
Unplugged and rebooted (Vol up + Power)
Plugged back in and entered into TWRP (Huzzah!)
Pushed two files into my "/tmp/" folder, these were xiaomi.eu_multi_MI9_V11.0.2.0.QFACNXM_v11-10.zip, and Magisk (V20)
Went to Wipe > Format Data > "Yes"
Back to TWRP Home, went to Install, and installed the xiaomi.eu mentioned above, then installed Magisk
Once both were done, I restarted, phone loaded up perfectly fine, and had Magisk installed
It was at this point I decided to try a custom rom:
CUSTOM ROM
Booted into TWRP
[*]Selected to Wipe > Format Data > "Yes"
I wiped System, Vendor, Data, Cache, and Dalvik
Pushed the Vendor 9.8.1 file into my "/tmp/" folder, along with whatever ROM I was testing (Tried with Syberia project, AOSPExtended, and ResurrectionRemix), GAPPS, and Magisk
Flashed the Vendor file
Flashed the ROM
Flashed GAPPS (Where it wasn't included with whatever ROM I was testing)
Flashed Magisk (This began giving me ERROR-1 here, even though it was exactly the same file that worked fine earlier.)
Once all that was done, I restarted the phone, it booted up fine, I saw the "Mi" bootscreen along with the "unlocked" at the bottom...Then the phone restarted.
It went to the same bootscreen once more, before restarting once again, and kicking me into TWRP.
I've tried it several times now, with different roms, both with/without installing GAPPS/Magisk, but I always get the same result.
I've been on these forums for a while, I know usually people post without reading, but that's not what I've done, I've read up on what to do, downloaded all the necessary (I think!) files ahead of time, and documented everything I did (in-case of a cockup!). So yes, I really have tried, and I really have searched
Any help, or direction, or hints, or magic wishes anybody can give me regarding this would be much appreciated!
same problem happened to me
i face the same problem every time without any solution i can only flash miui roms not aosp roms?
maheg said:
i face the same problem every time without any solution i can only flash miui roms not aosp roms?
Click to expand...
Click to collapse
Using the above steps, I have been able to flash AOSP, and Miui roms.
Though I always go back to Miui because it has the best camera app.

Lineage OS stuck at TWRP screen

Hello,
I am new to the world of custom ROMs, I have a huawei mediapad T5. I followed the guide and successfully rooted my device. then I installed TWRP from this link:
https://forum.xda-developers.com/showpost.php?do=showpost&p=76362629
I struggled to flash lineageos 16 on my device, after couple of hours, I found the installation guide from openkirin, that mentioned they don't support TWRP. but as I had already flashed my device with TWRP, I had no backup for stock recovery image. I tried to flash it anyway as mentioned in the openkirin site.
but now it stuck at TWRP screen. I am not sure how can I remove twrp completely from my mediapad t5.
After messing around I managed to boot into eRecovery from huawei, where I got option to download the stock firmware. that saved my day.
But I really want to flash it with LineageOS 16. I am not sure what can be done about twrp. Is there any way to remove it from my Mediapad, or is there any guide to install Open Kirin's LineageOS image onto my device along with TWRP?
Please let me know.
#Update
I managed to install Lineage OS onto my Mediapad T5. But I am afraid, I didn't like it much. It is not optimized for the tablet. There're unnecessary apps like Phone App, Messaging App etc. I only got Wifi version. Plus it has issues with Audio Output.
I am reverting back to stock ROM for now, Until better ROM is available from OpenKirin.
gunpal5 said:
Hello,
I am new to the world of custom ROMs, I have a huawei mediapad T5. I followed the guide and successfully rooted my device. then I installed TWRP from this link:
https://forum.xda-developers.com/showpost.php?do=showpost&p=76362629
I struggled to flash lineageos 16 on my device, after couple of hours, I found the installation guide from openkirin, that mentioned they don't support TWRP. but as I had already flashed my device with TWRP, I had no backup for stock recovery image. I tried to flash it anyway as mentioned in the openkirin site.
but now it stuck at TWRP screen. I am not sure how can I remove twrp completely from my mediapad t5.
After messing around I managed to boot into eRecovery from huawei, where I got option to download the stock firmware. that saved my day.
But I really want to flash it with LineageOS 16. I am not sure what can be done about twrp. Is there any way to remove it from my Mediapad, or is there any guide to install Open Kirin's LineageOS image onto my device along with TWRP?
Please let me know.
#Update
I managed to install Lineage OS onto my Mediapad T5. But I am afraid, I didn't like it much. It is not optimized for the tablet. There're unnecessary apps like Phone App, Messaging App etc. I only got Wifi version. Plus it has issues with Audio Output.
I am reverting back to stock ROM for now, Until better ROM is available from OpenKirin.
Click to expand...
Click to collapse
Try LOS18.1 (very VERY smooth) --> https://forum.xda-developers.com/t/...ation-guide-for-mediapad-t5-ags2-xxx.4291431/
Fosanz said:
Try LOS18.1 (very VERY smooth) --> https://forum.xda-developers.com/t/...ation-guide-for-mediapad-t5-ags2-xxx.4291431/
Click to expand...
Click to collapse
How safe is this unofficial LOS18.1 ROM?
gunpal5 said:
How safe is this unofficial LOS18.1 ROM?
Click to expand...
Click to collapse
I use it everyday so. Very safe I'm gonna say

After rooting G9+ & installing an unofficial LineageOS 18.1, root was lost & need help getting it back

I decided to upgrade to the G9+ after finding a LineageOS ROM for the phone. Root via TWRP & Magisk worked without a hitch. Then I installed the LineageOS 18.1 ROM from here: https://www.getdroidtips.com/lineage-os-18-1-moto-g9-plus/
Next I went to install GApps via the Aroma setup, but found that TWRP was gone. There was some limited recovery from the ROM installation which didn't seem to be of any use, so I reflashed TWRP & then Magisk, but I didn't get root back.
The phone now has a working version of LineageOS, but I can't even get the Google crap I need.
When I try to flash something via TWRP I get an error saying there was a "Zip signature verification failure", so I can't even get back to stock ROM to try again. (I guess this error is related to not having root.)
(I installed TWRP & Magisk on another G9+ with stock ROM and everything seems as expected. The phone is rooted. I just want to get rid off all the Google software I can.)
Anyone got an idea how I can get root back?
------
And any reason why "ADB devices" doesn't list the attached phone? "Fastboot devices" works fine.
Have u tested lineage, is
everything working fine?
UsmanQ said:
Have u tested lineage, is
everything working fine?
Click to expand...
Click to collapse
Everything seems to be there, seems normal. Except root.
doktorspin said:
Everything seems to be there, seems normal. Except root.
Click to expand...
Click to collapse
doktorspin said:
Everything seems to be there, seems normal. Except root.
Click to expand...
Click to collapse
Have u tried superoot or something else instead of magisk?
Sapper Morton said:
The ROM that you're using is not meant to be daily driven, Erfan compiled that for experimental purposes, but that aside, there's a few things that you should take in consideration when using Lineage; It's not meant to be used with TWRP, that's why they ship their own recovery (Lineage Recovery). It's still possible to flash custom files with it (That doesn't match their original signature), you just need to skip a warning.
For Magisk, download the latest stable build from here: Download
(The .apk has the flashing script built-in, so just rename that to .zip).
One major difference from TWRP, is that Lineage Recovery doesn't support decrypting userdata, so the files must be flashed using ADB or USB OTG.
Use ADB Sideload as follows:adb sideload magisk.zip
As for me, I didn't unlocked my device yet, so if you could confirm me something: I need to know if I will lose my DRM certification, used for Netflix, Disney+, Prime Video and such.
Download Castro from Play Store, go to the DRM tab, and check the Widevine status, tell me if it remains L1, or if it downgraded to L3. That's what's holding me back from testing, or even compiling for this device.
Click to expand...
Click to collapse
Thanks for the response.
1. I'm using the Github Magisk 23.
2. Lineage Recovery is gone. I reflashed TWRP.
3. Attempting to use "ADB sideload Magisk-v23.0.zip" ADB responds "cannot read 'Magisk-v23.0.zip'"
4. I haven't got Play Store on the phone as I can't flash the aroma package (1.7GB) via TWRP.
UsmanQ said:
Have u tried superoot or something else instead of magisk?
Click to expand...
Click to collapse
I don't know anything about the other methods for getting root. I've always used Magisk.
(I'm working under the idea that as TWRP + Magisk works fine on one phone, they aren't the problem.)
Sapper Morton said:
The idea is to rollback to Lineage Recovery, you can even flash only the boot.img that it's inside the ROM flashable file, instead of reflashing the whole thing again. It's probably in payload.bin format, so you'll need a payload firmware extractor (Easily found on GitHub), in case you choose the first option.
• Aroma is not supported on Lineage Recovery, so I would recommend something smaller, like OpenGapps nano or stock.
Click to expand...
Click to collapse
<rant>
What sort of idiots build in a crap recovery when one has obviously already installed a functional recovery, needed in the process of gaining root and installing LineasgeOS? This unnecessary included recovery wasn't in previous versions of LOS I've used.
Yes, this is an unpleasant surprise and I'm ticked off. I'm an end user who wants a relatively de-Googled phone, but now to maybe get a functional recovery I have to extract stuff from a payload file, but to do that I have to install more crud so that I can run the tool that does the extracting.
And I need Aroma to be able to select what I must have from Google. My partner needs their voice tech. I could dump almost everything else and use Pico. </rant> Sorry.
Is there no way to wipe the slate clean, get rid of this Lineage, and start again?
(I don't understand how installing their recovery could ruin the functionality of another recovery.)
Sapper Morton said:
Download Castro from Play Store, go to the DRM tab, and check the Widevine status, tell me if it remains L1, or if it downgraded to L3. That's what's holding me back from testing, or even compiling for this device.
Click to expand...
Click to collapse
On the second G9+ which I rooted but left the stock ROM, I installed Castro and it indicates L3.
doktorspin said:
I decided to upgrade to the G9+ after finding a LineageOS ROM for the phone. Root via TWRP & Magisk worked without a hitch. Then I installed the LineageOS 18.1 ROM from here: https://www.getdroidtips.com/lineage-os-18-1-moto-g9-plus/
Next I went to install GApps via the Aroma setup, but found that TWRP was gone. There was some limited recovery from the ROM installation which didn't seem to be of any use, so I reflashed TWRP & then Magisk, but I didn't get root back.
The phone now has a working version of LineageOS, but I can't even get the Google crap I need.
When I try to flash something via TWRP I get an error saying there was a "Zip signature verification failure", so I can't even get back to stock ROM to try again. (I guess this error is related to not having root.)
(I installed TWRP & Magisk on another G9+ with stock ROM and everything seems as expected. The phone is rooted. I just want to get rid off all the Google software I can.)
Anyone got an idea how I can get root back?
------
And any reason why "ADB devices" doesn't list the attached phone? "Fastboot devices" works fine.
Click to expand...
Click to collapse
take a look at this group of telegram, here they can help you to return
Lolinet [English Only]
Our website: MIRRORS.LOLINET.COM Our channel: https://t.me/lolinetnews Please speak in English
t.me
Lineage is working fine, some details that will be fixed when releasing the new kernel
There is a method to root with magisk by patching the ramdisk its a way better rooting method then with twrp in fact magisk dev recommends this way of rooting if you have not tried this here is a magisk official link https://topjohnwu.github.io/Magisk/install.html
Hope This helped you bro
The ROM in the O.P. works.​
Folks, I actually made a number of mistakes in this process.
The major one was to muff the fastboot command for flashing TWRP. I had followed instructions which said to boot TWRP, which didn't install TWRP, just loaded it into phone memory. But...
The ROM cited in the O.P. doesn't seem to have any problems that I have noticed in my usage, which is basically as a hand computer, not as a phone.
LineageOS now overwrites recovery with its own recovery, which is pretty moronic, because the user has already had to install a recovery to root the device.
But fortunately, if you have your ADB/fastboot apps handy with TWRP in the same folder it's an easy fix.
You should already have this stuff, but use the following software:
sebastian3367HD has provided TWRP for G9+ users onsight here. I'll assume it's called "twrp.img".
Magisk-v23 here -- put it somewhere easy on your phone.
Also get GApps 11. I used core NikGapps here, select latest date, then the version of GApps you want. (The core version 82MB just gives you Play Store & support software.) Put it the same place on the phone you put Magisk.
Assuming you've flashed the O.P. LineageOS ROM, which overwrites trusty TWRP, put your phone in fastboot mode, either using
1. power button + volume down
until you get the droid image on its back, or get there with your phone on, sending
2. adb reboot bootloader
via the windows command shell.
You're now in fastboot mode. You can now flash TWRP back onto the phone. Note that the phone has two slots of memory, so that the phone can hold two operating systems. If you send
fastboot flash recovery twrp.img
it will be flashed to the current slot, either A or B. To be safe you should flash both:
fastboot flash recovery_a twrp.img
fastboot flash recovery_b twrp.img
That gives you the safety of having TWRP in both slots. (Incidentally, TWRP allows you to changes slots.) (Also remember if you reflash LineageOS you'll have to put TWRP back on if you want a decent recovery program.)
Use TRWP to Reboot to Recovery.
Now install Magisk using TWRP:
Spoiler: (You know this)
a) choose Install
b) if the bottom right button says Install Zip press it and it will change to Install Image
c) if you put Magisk on your external SD card Select Storage to choose the SD
d) find and select Magisk-v23.0.apk, then
e) swipe to flash.
Then install GApps, basically the same as for Magisk.
Reboot to System. You should be rooted now and should have Play Store (and whatever else you opted for).
M.Akram said:
There is a method to root with magisk by patching the ramdisk its a way better rooting method then with twrp in fact magisk dev recommends this way of rooting if you have not tried this here is a magisk official link https://topjohnwu.github.io/Magisk/install.html
Hope This helped you bro
Click to expand...
Click to collapse
Thanks for the info. My problem was simple to fix, using the right commands!
I haven't installed that rom because afaik the source tree isn't available anywhere which seems kind of fishy, if anyone knows where they are please let us know

Question Weird behavior in any custom rom

Hi guys, I'm here looking for any help
I'm having this weird behavior in any custom rom I flash.
A while after flashing some rom (some 2 or 3 cycles of battery, around 1 to 3 days) suddenly all apps start crashing, falling at that force close popup. I mean every app, when I try to launch some new app it goes to the force close immediately.
I can't take a screenshot because it fails, I can't take a screen record because it crashes.
So I have to reboot, and it boots normally, but already happened that some apps loose their cache/data, because they start from zero and I have to log in again.
Happening on any A13 build, I don't remember about A12.
Can that be a hardware issue? I doesn't happen on MIUI.
Tried PE+, LO, CrDroid, ArrowOS, CherishOS, Voltage, Spark... Well, I'm trying it all.
Tried changing recovery: Kewl TWRP, TWRP, OrangeFox
Tried leaving phone on LTE only.
Tried flash fastboot MIUI before other rom.
Flashing all of them like: wipes, install rom, format data.
Does anybody has any idea?
Thanks and sorry about my english!
Leonvrx said:
Hi guys, I'm here looking for any help
I'm having this weird behavior in any custom rom I flash.
A while after flashing some rom (some 2 or 3 cycles of battery, around 1 to 3 days) suddenly all apps start crashing, falling at that force close popup. I mean every app, when I try to launch some new app it goes to the force close immediately.
I can't take a screenshot because it fails, I can't take a screen record because it crashes.
So I have to reboot, and it boots normally, but already happened that some apps loose their cache/data, because they start from zero and I have to log in again.
Happening on any A13 build, I don't remember about A12.
Can that be a hardware issue? I doesn't happen on MIUI.
Tried PE+, LO, CrDroid, ArrowOS, CherishOS, Voltage, Spark... Well, I'm trying it all.
Tried changing recovery: Kewl TWRP, TWRP, OrangeFox
Tried leaving phone on LTE only.
Tried flash fastboot MIUI before other rom.
Flashing all of them like: wipes, install rom, format data.
Does anybody has any idea?
Thanks and sorry about my english!
Click to expand...
Click to collapse
Did you've formated DATA with yes and reboot recovery
Then flashed fw
and last the ROM?
I mean exactly like this?
Laptapper said:
Did you've formated DATA with yes and reboot recovery
Then flashed fw
and last the ROM?
I mean exactly like this?
Click to expand...
Click to collapse
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Leonvrx said:
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Click to expand...
Click to collapse
Wipe isn't enough, formating with yes is necessary.
Try exactly my procedure (fw isn't necessary for all roms / cherishos don't need, Los need)
Some ROMs installation instructions do not require an initial format of data before installation of the ROM itself, like EliteRom. Follow your ROM's installation instructions regarding required firmware. (MIUI)
​
Leonvrx said:
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Click to expand...
Click to collapse
Sheist! said:
Some ROMs installation instructions do not require an initial format of data before installation of the ROM itself, like EliteRom. Follow your ROM's installation instructions regarding required firmware. (MIUI)
​
Click to expand...
Click to collapse
Also elite rom need format data if encrypted (normally data is encrypted!)
Leonvrx said:
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Click to expand...
Click to collapse
If installing the EliteROM (for example), your formatting after installing the ROM is the correct procedure, per the declared instructions:
Installation Instructions:
- Install rom zip using TWRP/OFOX
- Format if you are encrypted, otherwise wipe data is enough
- Reboot
- Enjoy the smoothness+performance
Sheist! said:
If installing the EliteROM (for example), your formatting after installing the ROM is the correct procedure, per the declared instructions:
Installation Instructions:
- Install rom zip using TWRP/OFOX
- Format if you are encrypted, otherwise wipe data is enough
- Reboot
- Enjoy the smoothness+performance
Click to expand...
Click to collapse
@Leonvrx
according my experience it's not important if you format before ROM or after Rom installation but very important to restart recovery when you do it before ROM installation in encryption state.
If decrypted then only wiping data
Please feedback your trying and results.
Laptapper said:
@Leonvrx
according my experience it's not important if you format before ROM or after Rom installation but very important to restart recovery when you do it before ROM installation in encryption state.
If decrypted then only wiping data
Please feedback your trying and results.
Click to expand...
Click to collapse
I didn't know that; thank you for your help, guidance, and patience.
Tried your steps exactly this morning, so far so good, I'll update in the next days, for better or for worse.
@Laptapper
Yeah, same results, it crashed the same (using AlphaDroid atm).
I've rebooted it and it even started initial android setup again, after redoing it, i have all my apps like nothing happened, but my sound settings, fingerprint settings (and probably other too) reseted.
I've also already tried to remove the microSD expation slot, same results,
Tried Vanilla + NikGapps, Vanilla + BitGapps and Gapps builds.
I think it's just bad luck with this specific device :/
Leonvrx said:
@Laptapper
Yeah, same results, it crashed the same (using AlphaDroid atm).
I've rebooted it and it even started initial android setup again, after redoing it, i have all my apps like nothing happened, but my sound settings, fingerprint settings (and probably other too) reseted.
I've also already tried to remove the microSD expation slot, same results,
Tried Vanilla + NikGapps, Vanilla + BitGapps and Gapps builds.
I think it's just bad luck with this specific device :/
Click to expand...
Click to collapse
Which recovery?
Take this:
👍[SHARED] orange fox recovery with decryption for Android 12,13
Update post 9 with android 13 decryption support Here I'm sharing the nearly perfect recovery orange fox with implemented decryption for android 12 ( I've tested only pin protection) The main advantage comparing TWRP is the "beautiful" UI and...
forum.xda-developers.com
Try cherishos with exactly my procedure above. Fw isn't needed!
Laptapper said:
Which recovery?
Take this:
👍[SHARED] orange fox recovery with decryption for Android 12,13
Update post 9 with android 13 decryption support Here I'm sharing the nearly perfect recovery orange fox with implemented decryption for android 12 ( I've tested only pin protection) The main advantage comparing TWRP is the "beautiful" UI and...
forum.xda-developers.com
Try cherishos with exactly my procedure above. Fw isn't needed!
Click to expand...
Click to collapse
I think that it's exactly this version, but I will reflash to make sure and I'll try again
Leonvrx said:
I think that it's exactly this version, but I will reflash to make sure and I'll try again
Click to expand...
Click to collapse
If not working then try this:
In orange fox recovery
format data with manually typing yes
reboot recovery
install cherish gapps rom
format data/yes Again
Start system
Laptapper said:
If not working then try this:
In orange fox recovery
format data with manually typing yes
reboot recovery
install cherish gapps rom
format data/yes Again
Start system
Click to expand...
Click to collapse
Ok, I'll try if happens again. Sometimes it takes 2 or 3 days to happen.
But I have a problem in Cherish that on my bank app (C6 Bank Brazil) my facial recognition doesn't work. It stays on a black screen despite I had given camera permission.
Leonvrx said:
Ok, I'll try if happens again. Sometimes it takes 2 or 3 days to happen.
But I have a problem in Cherish that on my bank app (C6 Bank Brazil) my facial recognition doesn't work. It stays on a black screen despite I had given camera permission.
Click to expand...
Click to collapse
Playstore certified?
Rooted?
Cts matching?
Laptapper said:
Playstore certified?
Rooted?
Cts matching?
Click to expand...
Click to collapse
Non-rooted, CTS profile ok and certified.
It's a thing that just happen in this ROM.
Also this app is really annoying to hide root from, so I never root
Leonvrx said:
Non-rooted, CTS profile ok and certified.
It's a thing that just happen in this ROM.
Also this app is really annoying to hide root from, so I never root
Click to expand...
Click to collapse
Try kernelsu root
Then delete caches of playstore and Google play services.
Reboot
I've got non problems with banking and camera in cherish and kernelsu

Categories

Resources