Database Users

Best / Fastest ROM right now

Hey guys. It's been awhile since I've rooted my phone, and the only thing keeping me from flashing a new ROM was the fact that I intended to return my current Hero for one that wouldn't get dust under the screen (I have some in the lower left hand corner). Well, I've decided I'm either too lazy to go return it or I just don't care that much anymore. So, I would like to get a new ROM now In your opinion, what would be the fastest ROM right now, that is the most stable? Keep in mind, I do NOT want to use Apps2SD (I only have a Class 2 card). I also would like to eventually add those optimized APK's that have been zipaligned in the future, and I want a lock screen that is clear (displays carrier/time text though... I've seen one around somewhere), and I want a clear notifications pull-down. The only thing I've been paying attention to right now has been getting 2.0/2.1 on our phones, so I've lost track of all the ROM's that were made (maybe someone can sticky the ones BESIDES MoDaCo's?), so that's why I'm asking for your help.
Also, I've made a nandroid backup, and of course, rooted. Is there anything else I would have to do to flash a new ROM?
Thanks so much guys!

Fresh's 1.0 is my favorite
http://forum.xda-developers.com/showthread.php?t=584032
or his main site here: http://geekfor.me/
If you run the delock mod, it will remove the lock icon and make it clear:
http://bit.ly/delock
There is a known message app issue, make sure to run this update as well:
http://bit.ly/freshmsgpatch
Other than that, the apps are already zipaligned, just update via recovery.

Alright, that's pretty much what I needed to hear Thanks so much! Oh, and it doesn't have Apps 2SD right?

it does have apps2sd, but only uses it if your sd card has a EXT2/3 partition
i used fresh 1.0 as well. no complaints. however the new 2.1 rom looks tempting.

mrinehart93 said:
Alright, that's pretty much what I needed to hear Thanks so much! Oh, and it doesn't have Apps 2SD right?
Click to expand...
Click to collapse
your welcome
you don't have to restore to stock or anything, just run the install after making a backup and your existing settings/data will stay intact.
I'm not using apps2sd and running it just fine.
I think you can set it up if you prefer it, but I didn't want to.
so the option is there I believe if you do ever want it

djxstream said:
it does have apps2sd, but only uses it if your sd card has a EXT2/3 partition
i used fresh 1.0 as well. no complaints. however the new 2.1 rom looks tempting.
Click to expand...
Click to collapse
yeah it does, but I'm waiting until they get accelerometer and multi-touch working, I ran the install when it was first posted and like what I see, but I need a solid phone, lol

Oh, and this is REALLY noobish, and forgive me for not searching... but do I have to rename the ROM to update.zip?

Oh, and this is REALLY noobish, and forgive me for not searching... but do I have to rename the ROM to update.zip?
EDIT
Ok so I just watched a video on how to flash a new ROM for the HTC Hero (Euro)... do I have to Wipe Data if I'm installing Fresh ROM? Or can I just go ahead with Apply sdcard: update.zip?

no, just select choose zip

mrinehart93 said:
Oh, and this is REALLY noobish, and forgive me for not searching... but do I have to rename the ROM to update.zip?
EDIT
Ok so I just watched a video on how to flash a new ROM for the HTC Hero (Euro)... do I have to Wipe Data if I'm installing Fresh ROM? Or can I just go ahead with Apply sdcard: update.zip?
Click to expand...
Click to collapse
You shouldn't have to. Just load the zip onto your sd card and nandroid has an option to choose which zip file you want to install..

Oh, and this is REALLY noobish, and forgive me for not searching... but do I have to rename the ROM to update.zip?
edit
I don't know why this double posted.

Ok wait, so it is a NO to having to rename the ROM to update.zip, but what about about Wiping Data first? Do I have to do that or can I just skip that and flash it?

mrinehart93 said:
Ok wait, so it is a NO to having to rename the ROM to update.zip, but what about about Wiping Data first? Do I have to do that or can I just skip that and flash it?
Click to expand...
Click to collapse
No you do not need to rename it. Just select chose zip.

I know that haha. But do I have to wipe the data first? Thanks for your replies guys

mrinehart93 said:
Ok wait, so it is a NO to having to rename the ROM to update.zip, but what about about Wiping Data first? Do I have to do that or can I just skip that and flash it?
Click to expand...
Click to collapse
No, just flash over what you have now. It *should* work just fine.

to be honest, I can't recall.
try it without first, if it never boots all the way and sticks,, then power off and wipe data through recovery.

Ok, thanks And then if anything bad happens, all I have to do is Reboot back into the recovery, and then press Wipe Data? Sounds good. Oh, and I should probably put my nandroid backup on my sdcard.

mrinehart93 said:
Ok, thanks And then if anything bad happens, all I have to do is Reboot back into the recovery, and then press Wipe Data? Sounds good. Oh, and I should probably put my nandroid backup on my sdcard.
Click to expand...
Click to collapse
your backup from recovery is on your sdcard, that's where mine are.
I make a backup of that to my laptop from time to time just to be safe.
have fun!

N0J said:
your backup from recovery is on your sdcard, that's where mine are.
I make a backup of that to my laptop from time to time just to be safe.
have fun!
Click to expand...
Click to collapse
I know, the file is big (like 288mb), so I just cut it off my sdcard and put it on my desktop. But I'm going to put it back now

cool...
check this link out, I think the see-thru notification bar is something you were looking for, plus there are a couple of extra goodies
http://forum.xda-developers.com/showpost.php?p=5120678&postcount=1

Big problem with my sgs2 :(

Everything have worked fine until now..
Latest things i did was update firmware on the camera, then rebooted and the camera worked just as fine as before.
I had two framework-res.apk's that i have moded from my own frameworkfile in kitchen, i did try both out and they worked just fine before, i did rename them and hade both in my bluetooth folder on the phone.. one circle and one guage battery framework modfile.
I wanted to go back to the guagefile, so i copied the file (it was renamed framework-res..guage.apk) and pasted it in the framework folder on the phone, renamed it and now it seamed i had two framework-res.apk files... thought one would overwrite the other, but no it didnt. So i checked what file was oldest and deleted that and rebooted, now i cant get by the samsung logo have tried everything and it just wont go any further
Could anyone help me with what to do pleeeeeease ? i can flash with odin, and i have tried flasing kernels unsecure and original with no effect, please help me !! i really hope this phone isnt bricked now

Put phone in download mode or cwm and flash a rom. Use a stock rom made for your phone.

I would prefer not to flash a new rom as there is many things on my phone that i dont want to get wiped away. I have some movies in the camera folder that i havent made a backup for yet and i just cant live without them, if they are lost i could just as well throw away the phone

boarne71 said:
I would prefer not to flash a new rom as there is many things on my phone that i dont want to get wiped away.
Click to expand...
Click to collapse
root it , then buy titanium backup from the market and backup what you want , then flash rom , then install titanium again , then reinstall back up , easy peasy
your phone will have what you want on it still and hopefully be working again
have a good day
flashing a rom shouldnt clear your mass memory mate , your videos etc should remain unless you use the android restore function in settings or format it via pc

buxz777 said:
root it , then buy titanium backup from the market and backup what you want , then flash rom , then install titanium again , then reinstall back up , easy peasy
your phone will have what you want on it still and hopefully be working again
have a good day
Click to expand...
Click to collapse
It is rooted, and i cant get past the bootlogo.

boarne71 said:
It is rooted, and i cant get past the bootlogo.
Click to expand...
Click to collapse
sorry didnt read post properley my fault :-(
still flashing a new rom wont delete your mass memory files
it never has on mine , as the other user said , wipe , wipe cache , wipe dalvik cache , if this still doesnt boot then flash a rom of your choice it may bring it back fine and your mass memory should be intact
leomar2.4 / 2.5 / 2.6 / doesnt touch the mass memory files anyways so your videos would be fine and you would have one of the best roms going

No worries
As it is now i can only get into odin mode.. down volume,home button,power button and get connected to the odin flashprogram, that is the only thing i can do
So even if my pictures and movies are on phones internal sd-card it wont be deleted ?? i just need to know this before i do something major like new rom.
I have a external sd-card to and i guess that wont be effected, but i dont know about the internal sd-card
Can i flash a rom without do those wipe cleaning stuff i read about that seams to be important to do before flashing a new rom ?
If it is just the framework-res.apk file thats wrong, cant i flash a new framework file with odin ? if for some reason there was something wrong there.

What rom do you use now? Wiping data wipes everything, wiping cache and dalvik cache shouldn't delete any personal data.

Im running original stock rom with unsecure kernel..

boarne71 said:
Im running original stock rom with unsecure kernel..
Click to expand...
Click to collapse
Just flash a stock ROM with Odin.
It won't remove anything, it'll all br there.
Sent from my GT-I9100 using XDA Premium App

Wipe will only wipe /data and /system which will be user and system apps and data.
You wont lose anything on the internal sd card and ext sd card.
You can always flash the same rom as you had before over the top which should fix the framework.

just flash non wipe rom from intratech topic, it will fix it for you
or boot into recovery, do backup there, flash new rom and then restore advenced only data in recovery
and as was mentioned before, reset/wipe/new rom through odin will not touch pictures/movies/music on internal sd card only apps and app setup with data will be erased
sent from my GalaxyS2

Thanks everyone for your help, you are really a great bunch of people here, so fast and very helpful, thank you all so much !
I must admit that my heart stopped for a moment when i couldnt get it restarted, forgot to breath but i did as you said only thing is i didnt flash a stock rom, i flashed a very nice rom called lightning and im much more happy with my phone now then i was before... in the end it was a good thing maybe that this happen to me today, otherwise i would probably never have gone from stock rom, now im glad i did it's faster and everything is better, and i could just now flash a new bootanimation that i couldnt do before, i tried the cool pc bios boot and im very happy with that, overall it feels like a new improved phone
Thanks everyone !!! Have a great eavning !

All you had to do was boot in recovery, and adb a stock frameworkres.apk to the phone and it wouldve booted fine! Or made a flshable zip that copies the stock frameworkres.apk and flash that through clockwork!
...and on the 8th day he created the SGS II!

Flash the lastest stock rom, then a cutom one?

as captioned, whats the advantage of doing so?
what are updated by the stock rom that are not updated by the cutomised rom?
recovery.img? i have manually replaced with CWM one..
amss.mbn? i have also manually replaced with the B162 version..
what else then?
now im with oxygen rom (was with B136 stock rom), say if there are indeed certain files from the latest stock rom that i should have, what is the best way to get them updated?

Have a look at this.

XphX said:
Have a look at this.
Click to expand...
Click to collapse
yeah thx.. i read that topic previously..
what im expecting is a bit more technical, such as what actually are being covered by stock rom while not touched by custom roms, where those files in "dev', "etc", "sbin", "sys" come from (since seemingly they are not included in oxygen rom when i check the zip file content), etc..
if these files are from the stock rom im using before flashing a custom rom (oxygen + B136 in my case), then im not just experiencing oxygen, rather a mixed experience of oxygen & B136..
if this is the case, the problems/issues i encountered might not be solely related to oxygen and might actually related to the stock rom..
anyway im very new on linux and smartphone stuff.. any information to enlighten would be much appreciated..

It won't be a mix of two ROMs at the same time, if you install your custom ROM with that instruction:
In Recovery menu: Choose Wipe Data /Factory Reset, then go back to main menu. Choose Wipe Cache Partition, then go back to main menu. Go to Advanced and choose Wipe Dalvik Cache, then go back to main menu. Then install the ROM by using the zip-file you placed on the sd-card earlier. That will delete what's left of the previous ROM. If you don't do this, you will run into problems eventually. But if you just wipe everything before flashing the old ROM cannot interfere.
Do not extract the zip-file of a custom ROM, just install it as it is.
iamelton said:
what actually are being covered by stock rom while not touched by custom roms
Click to expand...
Click to collapse
Updates for baseband, maybe also for other components.
iamelton said:
where those files in "dev', "etc", "sbin", "sys" come from (since seemingly they are not included in oxygen rom when i check the zip file content), etc..
Click to expand...
Click to collapse
Well Android does some stuff at the first boot and it does install some files (I do not know what it does exactly). If you followed the instructions these files cannot be from another ROM.
What other questions do you have? You just wrote "etc.", I cannot know what you want to ask...

u already helped a lot.. thx.. 8)
[edit]
oh just one more question, whats an "update to baseband" then?
amss.mbn? or can i even find it in the form of a file in root explorer?

I don't think that all the data gets replaced even when wiping both caches and doing a factory reset before applying new ROM. I just did that yesterday with new MIUI release, but I can still find data from my very first stock-ROM! In cust_backup/image/cust_data is folder called elisa(finish network provider, from which I originally bought the phone) with all the bloatware(gameloft installerinstallers for example), finish swype and more (folders are: app, lib, logo, prop, wallpaper, xml). Yesterday, I deleted it (the whole "elisa" folder with Root explorer (since I thought that: I have this new ROM, I don't need this old remnant crap of froyo). Well, as it turned out, I DO NEED this old crap, since after reboot phone just froze after operator logo( I honestly don't know how the logo was even possible, since it was in the folder I deleted). Had to restore from recovery and now it is back again..
Q: if I update to latest official rom, will the data in cust_backup be updated? Is this the point of applying latest stock-release once in a while?
Sent from my u8800 using xda premium

Vk_ said:
In cust_backup/image/cust_data is folder called elisa(finish network provider, from which I originally bought the phone) with all the bloatware(gameloft installerinstallers for example), finish swype and more (folders are: app, lib, logo, prop, wallpaper, xml).
Click to expand...
Click to collapse
I have the same folders, but for Estonia Elisa. I don't understand why is it there, when I have a totally different ROM.
Sent from my Huawei u8800 using XDA App

Well that is not surprising Vk_, I have all those apps and stuff too and if you delete the wrong file there, well... good thing that you cannot brick your phone
The partition mounted to cust_backup won't be overwritten by the wiping that is usually done before installing a new ROM. This is because it contains the files needed for entering recovery-mode etc.
This Elisa-folder contains stuff that is needed, maybe even the bootlogo (I just thought about this for a few minutes now, so I don't know what it is for). This has nothing to do with the ROM previously installed or with the Huawei-ROM. This folder is necessary for every u8800-device to work properly regardless of which Android-ROM is installed. Mine is called 2020 instead (that might depend on where you got it from).
Vk_ said:
if I update to latest official rom, will the data in cust_backup be updated? Is this the point of applying latest stock-release once in a while?
Click to expand...
Click to collapse
The point of applying the newest release is that you can make sure to get the latest baseband-firmware and maybe even updates for other parts. I do not know if these updates are installed via cust_backup but that could just be the case. It isn't important though; at least I get great reception everywhere so I do not need to update the baseband.
iamelton said:
oh just one more question, whats an "update to baseband" then?
amss.mbn? or can i even find it in the form of a file in root explorer?
Click to expand...
Click to collapse
The baseband updates the program that controls the radio-chip. This firmware has its own area on the radio-chip, this firmware won't be stored on the device. But a file to update this firmware will be on the device (maybe it is deleted automatically after updating).

now i think im much clearer.. thx..
then probably i dont need to update to B138 as i have good signal reception everywhere, and can sleep well since i know my phone is not with sub-perfect firmware.. 8)
for the cust-backup discussion, i also had similar doubt before..
glad that i didnt really go ahead to remove this useless "/cust_backup/image/cust_data/pccw/hk/" folder tree..
i just wonder how it manage to survive between rom wipes and installs..
this pccw folder came from the provider where i bought my phone, and in B136 rom its "/cust_backup/image/cust_data/hw/ideos_x5/"
after flashing B136, my phone could boot but things like custom boot animation, ring tones were lost..
i had to rename "hw" to "pccw", "ideos_x5" to "hk" to make them re-appear..
thus the linkage to this special folder tree seems to survive after complete wipes..
anyway before anyone tells me how to remove the whole tree, i shall leave them there..

Yes I wrote that this partition never gets wiped or anything, so that is why it survives every wipe and ROM-install.

XphX said:
Yes I wrote that this partition never gets wiped or anything, so that is why it survives every wipe and ROM-install.
Click to expand...
Click to collapse
actually it gets wiped (probably by the update_cust.app part in the B136 stock rom)..
before its "/cust_backup/image/cust_data/pccw/hk/"..
and after flashing B136 it changes to "/cust_backup/image/cust_data/hw/ideos_x5/"..
thus its updated, but somehow i have to manually rename "/hw/ideos_x5/" back to "/pccw/hk/" in order to make my custom boot animation and ring tones work again..
they were put in "media" folder under the tree, but somehow they wont work until i change the folder names back to "/pccw/hk/"..
thats why i said the "linkage" to these folder tree got survived between rom installs, but not the folder tree itself (which was updated by update_cust.app)..

No it does not get wiped. The stock ROM (and for that matter, every ROM can do that) simply changed the files in the directory you specified in your post. It does not matter anyway (so why am I writing this?;D).

XphX said:
No it does not get wiped. The stock ROM (and for that matter, every ROM can do that) simply changed the files in the directory you specified in your post. It does not matter anyway (so why am I writing this?;D).
Click to expand...
Click to collapse
just for the sake of discussion, maybe?!

Android is starting... Optimising app xx of xx on every boot

Hi all,
Have had my Nexus 10 with a few years now and rooted it not long after I got it, stuck with stock rom though.
All was fine until I updated to the latest LMY49H Build using NRT (Nexus Root Toolkit) which I always do and it has never let me down.
But with this update I get the swirling balls, Android boot screen then about 10 minutes of "Android is starting... Optimising app xx of xx". I have wiped via settings, via recovery (TWRP and stock), Flash Stock and Unroot (NRT), Root (NRT which wipes data), cleared cache, dalvik, data using TWRP but every time I end up with this optimising apps screen.
I have tried restoring previous versions at setup (apps, wallpapers etc.) and I have skipped all setup options for a clean fresh copy but always with the same result.
I have been looking around but didn't find someone running stock rom with the same problem, If I missed it then I'm sorry.
Please someone help me as I'm going on a trip soon and will need my tablet!

Could be your flash memory is wearing out. When you are using TWRP try copying a file then reboot into TWRP and see if the file is still there. If it is gone it is bad flash memory and you need a new motherboard...
Sent from my LGLS991 using Tapatalk

psiphi said:
Could be your flash memory is wearing out. When you are using TWRP try copying a file then reboot into TWRP and see if the file is still there. If it is gone it is bad flash memory and you need a new motherboard...
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
Sorry I don't get what you mean. do you mean to flash a file? (or at least see if TWRP finds the file?)
e.g. copy a file, supersu.zip or something in downloads folder, then boot into TWRP to see if its in the folder ready to flash?
Oh I hope its not the motherboard, the tablet has hardly been used compared to others I know of.
Do you know if its safe to revert to a previous version of android using NRT? LMY49H or even G? I was happy enough with those versions and only updated thinking it would clear the security update (7.2mb) which I ended up doing manually anyway (Unroot & Update, install security update, Root).
I had a problem like this years ago when I flashed a ROM to my old Galaxy S4, flashing a different ROM fixed the problem then, I'm hoping it will now too!
Thanks for your help

fado5ster said:
Sorry I don't get what you mean. do you mean to flash a file? (or at least see if TWRP finds the file?)
e.g. copy a file, supersu.zip or something in downloads folder, then boot into TWRP to see if its in the folder ready to flash?
Oh I hope its not the motherboard, the tablet has hardly been used compared to others I know of.
Do you know if its safe to revert to a previous version of android using NRT? LMY49H or even G? I was happy enough with those versions and only updated thinking it would clear the security update (7.2mb) which I ended up doing manually anyway (Unroot & Update, install security update, Root).
I had a problem like this years ago when I flashed a ROM to my old Galaxy S4, flashing a different ROM fixed the problem then, I'm hoping it will now too!
Thanks for your help
Click to expand...
Click to collapse
Not flash your memory but check your: https://simple.wikipedia.org/wiki/Flash_memory
And yes it is safe to restock (another) ROM.

fado5ster said:
Sorry I don't get what you mean. do you mean to flash a file? (or at least see if TWRP finds the file?)
e.g. copy a file, supersu.zip or something in downloads folder, then boot into TWRP to see if its in the folder ready to flash?
Oh I hope its not the motherboard, the tablet has hardly been used compared to others I know of.
Do you know if its safe to revert to a previous version of android using NRT? LMY49H or even G? I was happy enough with those versions and only updated thinking it would clear the security update (7.2mb) which I ended up doing manually anyway (Unroot & Update, install security update, Root).
I had a problem like this years ago when I flashed a ROM to my old Galaxy S4, flashing a different ROM fixed the problem then, I'm hoping it will now too!
Thanks for your help
Click to expand...
Click to collapse
Right, I mean just copy a file to it that is not already there and rebooting it and seeing if the file is still there.
If it works then you probably don't have a hardware issue.
It is always worth trying to flash a known working rom, though you may need to hard reset to get it working.
Sent from my LGLS991 using Tapatalk

mr.natural said:
Not flash your memory but check your: https://simple.wikipedia.org/wiki/Flash_memory
And yes it is safe to restock (another) ROM.
Click to expand...
Click to collapse
Sorry, I know what flash memory is, I mean I didn't know what he meant by copy using TWRP.
I may try flash the previous LMY49H ROM then
psiphi said:
Right, I mean just copy a file to it that is not already there and rebooting it and seeing if the file is still there.
If it works then you probably don't have a hardware issue.
It is always worth trying to flash a known working rom, though you may need to hard reset to get it working.
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
OK cool, thanks for clearing that up..
This literally just started when I updated to the new ROM (LMY49J). I have done a full wipe already so hard reset shouldn't be a problem, nothing left on it now anyway. Think I may have done it already tho
Before the update I had a full TV series and a few movies saved into it and it had no problems playing/saving anything. Think I may try stock flash & unroot with LMY49H and see how that goes.. I'm away from it at the moment so hopefully will try tomorrow.
I have a feeling it is saving files though, displayed my old wallpaper when I restored from previous tablet option on setup. Must be saving this picture somewhere after initial download at setup. It is booting up eventually like, just after it optimizes the apps, maybe 5-10min.
What other issues could I be having?

You really have to create or copy something new and reboot the tablet to test. Files and setting will stay in the cache and so give the illusion working unless you reboot.
Also are you doing a clean shutdown via the menu after hitting the power button for no more than 2 seconds? Doing power off without going through menu can cause your behavior.
Sent from my LGLS991 using Tapatalk

psiphi said:
You really have to create or copy something new and reboot the tablet to test. Files and setting will stay in the cache and so give the illusion working unless you reboot.
Also are you doing a clean shutdown via the menu after hitting the power button for no more than 2 seconds? Doing power off without going through menu can cause your behavior.
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
OK I will try copy something tomorrow.. A TV show or something..
Yes I always hit power button and select "Power Off" and let it shut down, have since day 1!
Will keep you updated,
Thanks again

fado5ster said:
OK I will try copy something tomorrow.. A TV show or something..
Yes I always hit power button and select "Power Off" and let it shut down, have since day 1!
Will keep you updated,
Thanks again
Click to expand...
Click to collapse
You have to copy something in recovery mode with twrp. From a different directory (or usb stick to your device) and then reboot to see if it is still there.

Soft Reboots Leading to Bootloop

Hey guys, not exactly sure where to post this since this has happened to me both with AICP and now once with Dark Rom. So simply put I am just using my phone and then randomly it soft reboots. I hurry and take some logs before the next. Then the next. Then it keeps doing this with each time between getting shorter until it just won't fully boot up without wiping dalvik and cache.
I am using Dark Rom at the moment with A2017U version and the stock kernel that comes with Darkrom. However I believe I did have it with LlamaSweet as well. The only modifications I have done are magisk and trying out jococ v2 tweak which I doubt either is the cause.
Has anyone had ant issues like this or does anyone know how to fix it? I hate knowing it's random and it may make my alarm clock not go off if it is in a bootloop.
Hope to get some help with this! Thanks!

JTruj1ll0923 said:
Hope to get some help with this! Thanks!
Click to expand...
Click to collapse
Just realized the zip posted has only files that are blank.... So here is a log I grabbed from TWRP. Hopefully this will help instead!

JTruj1ll0923 said:
Just realized the zip posted has only files that are blank.... So here is a log I grabbed from TWRP. Hopefully this will help instead!
Click to expand...
Click to collapse
No idea, not a dev. But I've read somewhere that Magisk 14.5 might be the culprit. I had this exact same problem on LineageOS. I made a backup of the system that was doing this, then wiped system and data, flashed LOS, booted it, then went to TWRP, wiped system and data, and restored the backup (only system, boot and data backed up). That solved it until you rebooted or the phone just decided to reboot itself...

Choose an username... said:
No idea, not a dev. But I've read somewhere that Magisk 14.5 might be the culprit. I had this exact same problem on LineageOS. I made a backup of the system that was doing this, then wiped system and data, flashed LOS, booted it, then went to TWRP, wiped system and data, and restored the backup (only system, boot and data backed up). That solved it until you rebooted or the phone just decided to reboot itself...
Click to expand...
Click to collapse
By doing this what would be the benefit? From what I can see you are basically back at point A by restoring the files. But yeah I do have magisk 14.5 installed... I had some problems with 14 but I'll see if I can get it to work this time. Thanks!

JTruj1ll0923 said:
By doing this what would be the benefit? From what I can see you are basically back at point A by restoring the files. But yeah I do have magisk 14.5 installed... I had some problems with 14 but I'll see if I can get it to work this time. Thanks!
Click to expand...
Click to collapse
Yes, it seems like it would do nothing, but it actually fixed my phone every time.
Maybe you can try the magisk uninstaller zip, dunno

Choose an username... said:
Yes, it seems like it would do nothing, but it actually fixed my phone every time.
Maybe you can try the magisk uninstaller zip, dunno
Click to expand...
Click to collapse
Thats Interesting. Well it happened again and logs were empty again... So I moved back to magisk 14.0 if that doesn't work I'll try restoring system and data.

@JTruj1ll0923,,
Hi,
you can try to backup before hard reset your phone. Usually, the LlamaSweet and DARK ROM are not compatibile with A2017G, so ZTE stock ROM would be a better choice.

William Guo said:
@JTruj1ll0923,,
Hi,
you can try to backup before hard reset your phone. Usually, the LlamaSweet and DARK ROM are not compatibile with A2017G, so ZTE stock ROM would be a better choice.
Click to expand...
Click to collapse
Thanks but I have a a2017u. Don't know if that makes much a difference though.