Mostly just out of curiosity I flashed a new ROM this weekend. I decided I like pure nexus better so I flashed my backup from twrp but wound up in bootloop. Even though I've never had issues restoring ROMs with MANY other devices, I still followed the directions for backing it up very carefully. I also did a full wipe before trying to restore it. In fact after the 3rd attempt I accidentally wiped internal storage. So that wasn't the issue.
Only thing I can figure is I was using elemental kernel when I made the backup so maybe that was the problem? I don't see why it would matter (or how that would work--removing the kernel, make backup, flash kernel again...) but I'm really stumped on how I went wrong.
KLit75 said:
Mostly just out of curiosity I flashed a new ROM this weekend. I decided I like pure nexus better so I flashed my backup from twrp but wound up in bootloop. Even though I've never had issues restoring ROMs with MANY other devices, I still followed the directions for backing it up very carefully. I also did a full wipe before trying to restore it. In fact after the 3rd attempt I accidentally wiped internal storage. So that wasn't the issue.
Only thing I can figure is I was using elemental kernel when I made the backup so maybe that was the problem? I don't see why it would matter (or how that would work--removing the kernel, make backup, flash kernel again...) but I'm really stumped on how I went wrong.
Click to expand...
Click to collapse
What partitions did you backup/restore?
Heisenberg said:
What partitions did you backup/restore?
Click to expand...
Click to collapse
Well Ive got the right guy to talk to Pretty sure it was what you suggested (system/data/boot/vendor boxes)
But I don't recall if I checked everyone to restore. However, I did store the backup on my computer. Even though I've since got everything back I can try again to restore it. But can you just confirm which I should check when I restore it?
I'll be certain to pay closer attention next time. Its just that this is one thing I had never struggled with. Thanks
KLit75 said:
Well Ive got the right guy to talk to Pretty sure it was what you suggested (system/data/boot/vendor boxes)
But I don't recall if I checked everyone to restore. However, I did store the backup on my computer. Even though I've since got everything back I can try again to restore it. But can you just confirm which I should check when I restore it?
I'll be certain to pay closer attention next time. Its just that this is one thing I had never struggled with. Thanks
Click to expand...
Click to collapse
I recommend restoring system, data, boot, and vendor. Just make sure you're not restoring system image or vendor image.
Heisenberg said:
I recommend restoring system, data, boot, and vendor. Just make sure you're not restoring system image or vendor image.
Click to expand...
Click to collapse
So simple. Thanks a lot!
KLit75 said:
So simple. Thanks a lot!
Click to expand...
Click to collapse
Let me know if you get it booting.
Heisenberg said:
Let me know if you get it booting.
Click to expand...
Click to collapse
Well yes. Thanks again. However, I've got something funky going on. Pin pointing is hard but yea the backup restored. Then I tweaked elemental kernel (nothing crazy, used stable profiles) maybe it was that and an xposed mod (thinking ifont because its one I only just started using lt recently). Anyway when I rebooted to install drivers for viper I got stuck in bootloop. This time I couldn't restore my backup. So I factory reset and reflashed pure nexus. Due to the time I couldn't try and restore the backup again but will try tonight. If I wasn't so hasty I could've deleted the modules list in twrp then maybe booted up but I'm not 100% it has anything to do with xposed. One other factor, it was using dark stock theme.
EVERYTHING I mentioned I've done/run on this ROM without issues but there's a combination of things that's causing the bootloop I think.
Related
Hi all... tonight I decided to try the Samurai kernel. Unfortunately, it boot-looped on me. No big deal I figured, I did a full nandroid before in ACS's CWM, so I'll just restore. Unortunately, doing so isn't working: all of my apps, data and settings are gone! It basically looks stock (although, interestingly, all the Sprint bloat I had manually removed before still seems to be gone, so the restore worked to a degree)... I've restored backups before and never had a problem so I'm guessing the kernel is somehow the culprit, but I think that got restored from the backup too so I don't know what's going on. I'm stock EI22 by the way.
Can anyone help me? I'm pretty frustrated at the moment.
Thanks,
Frank
Try restoring an older backup. If that works you can attempt an advanced restore data only from your recent backup to see if it was something in your setup.
Sent from my SPH-D700 using XDA App
That was a thought I had too... I tried TWO older backups that I still had, same problem. I also tried a factory reset and then a restore (in theory it shouldn't make any difference to factory wipe first, and sure enough it didn't, but figured it was worth a shot).
My only other thought is maybe if I odin back to stock, root & install recovery and then try the restore again... kind of a shot in the dark, really shouldn't matter, but maybe.
Did you clear cache and dalvik before flashing the new kernel? I wonder if ACS is the issue and if trying CWM 5 might help.
DroidApprentice said:
Did you clear cache and dalvik before flashing the new kernel? I wonder if ACS is the issue and if trying CWM 5 might help.
Click to expand...
Click to collapse
I was thinking the same thing D. The only other thing I can think of is bad reads from the sd card.
Well, my first venture into rom flashing hasn't been the most successful one as it's caused a really strange issue that a couple people on another thread have tried to help me solve, but I figure I had hijacked that thread long enough so this issue deserved it's own thread.
I rooted, unlocked bootloader, and installed TWRP v2.4.0.0 on Stock Android 4.1.1. Everything worked great. Until I flashed a rom. Now, I have been through wiping Cache, Dalvik Cache, Factory Reset, Flashing the rom (I've tried 4 with the same exact issue), flashing Gapps... All seems to go well and it says "success" when I flash, and I reboot into system. Run the setup of Google. Everything seems great and working fine. Here's where the problem is. When Google Play Store starts downloading for restore, and I'm on a solid wifi connection, nothing downloads. I have also tried stopping the downloads and installing apps individually. When I do that, I receive the same error message over and over for any app:
Unknown error code during application install: "-24"
I've rebooted, wiped cache, dalvik cache. Nothing installs. Same error. I did somehow, some way, get Titanium backup to install after numerous tries... when I try to restore any of that backup it just hangs on the first app. It does not restore anything. No batch apps. No single apps. No app data.
The odd thing is, the first time I flashed a rom, it seemed to load up fine. Stupidly, when I was running Titanium Backup for a restore I was not paying attention to what I was restoring. I was restoring all apps and app data... It caused an issue and a bunch of force closes, as you can probably imagine. So I rebooted into recovery and wiped and reinstalled rom and gapps. And virtually nothing has installed since. I have wiped and reinstalled AOKP, PACman, Carbon, and CM to no avail. Nothing seems to solve my issue. I'd love to at the very least be able to regularly install apps from the Play Store. At this point I'm not even concerned with restoring app data if that's too much to ask. I just want to be able to use my phone normally again as this is my "daily driver". If I have to go back to 4.1.1, that would be fine with me. I just want to get back to normal. And I'll do whatever it takes to get there. Any help at all would be appreciated.
Here is the original thread that some people have been giving me great advice on as to what to do, but none of it has fixed the issue yet unfortunately:
http://forum.xda-developers.com/showthread.php?t=2341470
Jersey846 said:
Well, my first venture into rom flashing hasn't been the most successful one as it's caused a really strange issue that a couple people on another thread have tried to help me solve, but I figure I had hijacked that thread long enough so this issue deserved it's own thread.
I rooted, unlocked bootloader, and installed TWRP v2.4.0.0 on Stock Android 4.1.1. Everything worked great. Until I flashed a rom. Now, I have been through wiping Cache, Dalvik Cache, Factory Reset, Flashing the rom (I've tried 4 with the same exact issue), flashing Gapps... All seems to go well and it says "success" when I flash, and I reboot into system. Run the setup of Google. Everything seems great and working fine. Here's where the problem is. When Google Play Store starts downloading for restore, and I'm on a solid wifi connection, nothing downloads. I have also tried stopping the downloads and installing apps individually. When I do that, I receive the same error message over and over for any app:
Unknown error code during application install: "-24"
I've rebooted, wiped cache, dalvik cache. Nothing installs. Same error. I did somehow, some way, get Titanium backup to install after numerous tries... when I try to restore any of that backup it just hangs on the first app. It does not restore anything. No batch apps. No single apps. No app data.
The odd thing is, the first time I flashed a rom, it seemed to load up fine. Stupidly, when I was running Titanium Backup for a restore I was not paying attention to what I was restoring. I was restoring all apps and app data... It caused an issue and a bunch of force closes, as you can probably imagine. So I rebooted into recovery and wiped and reinstalled rom and gapps. And virtually nothing has installed since. I have wiped and reinstalled AOKP, PACman, Carbon, and CM to no avail. Nothing seems to solve my issue. I'd love to at the very least be able to regularly install apps from the Play Store. At this point I'm not even concerned with restoring app data if that's too much to ask. I just want to be able to use my phone normally again as this is my "daily driver". If I have to go back to 4.1.1, that would be fine with me. I just want to get back to normal. And I'll do whatever it takes to get there. Any help at all would be appreciated.
Here is the original thread that some people have been giving me great advice on as to what to do, but none of it has fixed the issue yet unfortunately:
http://forum.xda-developers.com/showthread.php?t=2341470
Click to expand...
Click to collapse
2 suggestions:
1) i think others have reported having issues with TWRP 2.4, so try 2.5 or 2.3.2.3
2) I think the error could be a lack of internal storage, so certainly try the "wipe internal storage" in TWRP (after making sure that your ROM/GApp files, backups (including Tibu) are saved to your external folder
jco23 said:
2 suggestions:
1) i think others have reported having issues with TWRP 2.4, so try 2.5 or 2.3.2.3
2) I think the error could be a lack of internal storage, so certainly try the "wipe internal storage" in TWRP (after making sure that your ROM/GApp files, backups (including Tibu) are saved to your external folder
Click to expand...
Click to collapse
Ok giving this a shot. I did notice that you had mentioned a different version of TWRP than I had. I will try the wiping internal storage before I install a different TWRP then if that doesn't work, TWRP. Gotta find the external folder. Unless you just mean anything that is on the actual SD card.
Jersey846 said:
Ok giving this a shot. I did notice that you had mentioned a different version of TWRP than I had. I will try the wiping internal storage before I install a different TWRP then if that doesn't work, TWRP. Gotta find the external folder. Unless you just mean anything that is on the actual SD card.
Click to expand...
Click to collapse
i would actually recommend installing TWRP 2.5 first.
never wipe external SD card.
if you have an app called Root Explorer, that works best.
jco23 said:
i would actually recommend installing TWRP 2.5 first.
never wipe external SD card.
if you have an app called Root Explorer, that works best.
Click to expand...
Click to collapse
Ok I'll try 2.5 then. And I wasn't gonna wipe the card, just was wondering if when you said external folder you were talking about the SD card. Root explorer works great.. if i could install it.
EDIT: Since I am away from my computer, I tried the multiple wipe method. Didn't change anything. So I will be changing TWRP versions later and will post an update.
Jersey846 said:
Ok I'll try 2.5 then. And I wasn't gonna wipe the card, just was wondering if when you said external folder you were talking about the SD card. Root explorer works great.. if i could install it.
EDIT: Since I am away from my computer, I tried the multiple wipe method. Didn't change anything. So I will be changing TWRP versions later and will post an update.
Click to expand...
Click to collapse
You never mentioned using TWRP 2.4. DEFINITELY replace that. Also, just a thought. If you haven't already done so, try using the option to fix permissions. I'm fairly sure its an option in TWRP.
Sent from my XT907 using xda premium
Back in business! Wow thank you all so much! What a pain it's been but without the help I'd have never guessed how to get this running as perfectly as it is now. Here's what worked for me:
Installed TWRP 2.5 (Instead of what I had, 2.4)
Then followed jco23's precise directions:
jco23 said:
- I use TWRP 2.3.2.3 (SS has been uninstalled via it's own app, not Tibu or the system awhile ago) - but TWRP 2.5 works just fine for others
- after downloading the ROM and GApps (or any file that I intended to flash for that matter), I always place the file on the mnt/external1 directory. I
m not sure if this will make a difference, but I recall it being an issue back on my Droid Charge days
- after flashing the files, does TWRP say successful?
- perhaps you do need to a double wipe of everything prior to flashing:
1) mount everything
2) wipe cache
3) wipe dalvik cache
4) wipe system
5) factory reset/wipe data
6) wipe internal storage (if you do this, make sure to change your TiBu backup folder to your external1 directory, or this will be gone too!!!!! also make sure that the system backup you made is on the external1 directory as well
7) reboot recovery
8) install ROM
9) install GApps
Click to expand...
Click to collapse
And it's working flawlessly. Able to download or restore anything from Gapps. Was able to restore some specific app data from Titanium Backup (did not want to ruin the phone again and do that full restore so I selected specific apps that I really wanted the data on).
Thanks to everyone who took the time to assist me and a special thanks to jco23 and netizenmt who were with me through this whole debacle, leading me through every possible fix they could think of. As for those of you that may be wondering which ROM I settled on... AOKP.
Good for you bro! That stinking TWRP 2.4.0 is such a menace! Wish there was a way to have it yanked from circulation. Glad you're up and running!
Sent from my Droid Razr M using xda premium
Jersey846 said:
Back in business! Wow thank you all so much! What a pain it's been but without the help I'd have never guessed how to get this running as perfectly as it is now. Here's what worked for me:
Installed TWRP 2.5 (Instead of what I had, 2.4)
Then followed jco23's precise directions:
And it's working flawlessly. Able to download or restore anything from Gapps. Was able to restore some specific app data from Titanium Backup (did not want to ruin the phone again and do that full restore so I selected specific apps that I really wanted the data on).
Thanks to everyone who took the time to assist me and a special thanks to jco23 and netizenmt who were with me through this whole debacle, leading me through every possible fix they could think of. As for those of you that may be wondering which ROM I settled on... AOKP.
Click to expand...
Click to collapse
glad you finally got it working - this is just the first step in becoming a crack-flasher....
jco23 said:
glad you finally got it working - this is just the first step in becoming a crack-flasher....
Click to expand...
Click to collapse
Yeah, I've got it bad. I have had CM 10.1, Slimbean, Carbon AND AOKP on my phone all in the last 2 days. Carbon is on it right now. No telling what will be on it by tonight.
Sent from my XT907 using xda premium
netizenmt said:
Yeah, I've got it bad. I have had CM 10.1, Slimbean, Carbon AND AOKP on my phone all in the last 2 days. Carbon is on it right now. No telling what will be on it by tonight.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
funny, and the goal is to find a ROM that you're happy with and don't need to flash.
but I've been on Carbon since 7/5, and very happy.
Hello All,
I am hoping the XDA community can help me out.
My current situation is that I am rooted, runnig Madhi 4.4.2 rom. I also have TWRP installed, with backup for stock rooted rom, and a backup for
my current Madhi Rom. Here lies my problem. I can't flash any other rom, nor can I flash my stock backup rom.
When I try to flash a different rom I get bootloops causing it to constantly restart, which is the same thing that happens when i try to flash my stock
backup. Can someone be kind enough to tell me what I am doing wrong (before i was able to restore my backup to stock), and what do i need to
do to be able to change out my rom. Hopefully there is a way to do so without having to bring my phone completely back to stock, then rerooting.
I've searched the threads but i wasn't able to find the answer.
Thanks in advance for your help guys.
JD
jdizzle316 said:
Hello All,
I am hoping the XDA community can help me out.
My current situation is that I am rooted, runnig Madhi 4.4.2 rom. I also have TWRP installed, with backup for stock rooted rom, and a backup for
my current Madhi Rom. Here lies my problem. I can't flash any other rom, nor can I flash my stock backup rom.
When I try to flash a different rom I get bootloops causing it to constantly restart, which is the same thing that happens when i try to flash my stock
backup. Can someone be kind enough to tell me what I am doing wrong (before i was able to restore my backup to stock), and what do i need to
do to be able to change out my rom. Hopefully there is a way to do so without having to bring my phone completely back to stock, then rerooting.
I've searched the threads but i wasn't able to find the answer.
Thanks in advance for your help guys.
JD
Click to expand...
Click to collapse
What version of TWRP are you running and how are you wiping? Make sure you go into advanced and wipe cache, dalvik, data AND system.
Do this 3 times! Because sometimes it doesn't work. Flash your rom then wipe cache and dalvik and restart.
scottdanpor said:
What version of TWRP are you running and how are you wiping? Make sure you go into advanced and wipe cache, dalvik, data AND system.
Do this 3 times! Because sometimes it doesn't work. Flash your rom then wipe cache and dalvik and restart.
Click to expand...
Click to collapse
Thanks for the tip. I am running 2.6.3.3 TWRP.
I normally do the full wipe, but i took your advice and went into advanced wipe and wiped dalvik, cache, system & data but unfortunately still the same result.
do you have any idea of what boggered up my phone? for right now, im stuck on Mahi Rom. I can restore back to Mahi Rom, and flash Mahi Rom, but that's the extent of it.
I do recall that when I originally flashed Mahi Rom, i had to flash a patch for the Sprint version of the G2. Do you think that has something to do with my problems?
i didn't have this problem before...just kinda baffled that now its giving me issues....
Thanks for your time, much appreciated. Hope someone can help me get to the bottom of this
JD
jdizzle316 said:
Thanks for the tip. I am running 2.6.3.3 TWRP.
I normally do the full wipe, but i took your advice and went into advanced wipe and wiped dalvik, cache, system & data but unfortunately still the same result.
do you have any idea of what boggered up my phone? for right now, im stuck on Mahi Rom. I can restore back to Mahi Rom, and flash Mahi Rom, but that's the extent of it.
I do recall that when I originally flashed Mahi Rom, i had to flash a patch for the Sprint version of the G2. Do you think that has something to do with my problems?
i didn't have this problem before...just kinda baffled that now its giving me issues....
Thanks for your time, much appreciated. Hope someone can help me get to the bottom of this
JD
Click to expand...
Click to collapse
I'm baffled as well, I would say it's time for a .tot restore. The rooting doesn't take long really, I think you'll spend more time trying to troubleshoot than it takes to wipe and restore your apps with TBU.
Are you by chance using the zva radio?
Sent from my LS980 4G using Tapatalk
scottdanpor said:
I'm baffled as well, I would say it's time for a .tot restore. The rooting doesn't take long really, I think you'll spend more time trying to troubleshoot than it takes to wipe and restore your apps with TBU.
Click to expand...
Click to collapse
Thanks for taking the time out to help me out. I'm afraid you might be right. It's just the the files for the .tot restore are huge! One file was over 2.1 gb, which sucks for me cause my internet is really slow. funny thing is i was dl'ing that file took like 5 hours, and when it got to 2gb downloaded, the site froze and i wasn't able to pause/resume my download. it was very frustrating.
Dshook1979 said:
Are you by chance using the zva radio?
Sent from my LS980 4G using Tapatalk
Click to expand...
Click to collapse
I don't think i ever updated my radio. is this something i should do in order to flash or restore?
jdizzle316 said:
Thanks for taking the time out to help me out. I'm afraid you might be right. It's just the the files for the .tot restore are huge! One file was over 2.1 gb, which sucks for me cause my internet is really slow. funny thing is i was dl'ing that file took like 5 hours, and when it got to 2gb downloaded, the site froze and i wasn't able to pause/resume my download. it was very frustrating.
Click to expand...
Click to collapse
Most roms are around 1.5gb. If you are getting disconnects it could also be causing what you see with the other roms you're flashing. Unless they are the same ones that you flashed successfully before of course.
Either way having a .tot restore file backup up on your PC is really handy to have.
scottdanpor said:
Most roms are around 1.5gb. If you are getting disconnects it could also be causing what you see with the other roms you're flashing. Unless they are the same ones that you flashed successfully before of course.
Either way having a .tot restore file backup up on your PC is really handy to have.
Click to expand...
Click to collapse
Thank you again...thats what im going to do tonight after work.
Hi guys, I've got a problem with my phone. I restored a data nandroid and have tried multiple different ones and these backups have previously worked but my phone boots up and the screen goes black and that's it. Please help me. If I flash a rom without restoring the data then it boots fine. The nandroid shouldn't be causing an issue as I've used these backups with no problems previously. If anyone can help me that would be greatly appreciated. Thank you!
DEVILOPS 007 said:
Hi guys, I've got a problem with my phone. I restored a data nandroid and have tried multiple different ones and these backups have previously worked but my phone boots up and the screen goes black and that's it. Please help me. If I flash a rom without restoring the data then it boots fine. The nandroid shouldn't be causing an issue as I've used these backups with no problems previously. If anyone can help me that would be greatly appreciated. Thank you!
Click to expand...
Click to collapse
I've honestly never successfully restored any Nandroid backup on the 6P and don't even bother making them anymore. I think I read that there was a problem restoring backups on the latest version of TWRP. You should probably check out their XDA thread.
jhs39 said:
I've honestly never successfully restored any Nandroid backup on the 6P and don't even bother making them anymore. I think I read that there was a problem restoring backups on the latest version of TWRP. You should probably check out their XDA thread.
Click to expand...
Click to collapse
Okay thanks, so if the most recent versions have problems would I b able to restore on older versions?
DEVILOPS 007 said:
Okay thanks, so if the most recent versions have problems would I b able to restore on older versions?
Click to expand...
Click to collapse
The latest build 3.1.0.0 works perfectly backing up and restoring backups made with that same version. Older builds certainly have issues, so you may not be able to properly restore a backup made with an earlier version. I think the greater question is what happens when you flash stock? I'd be wondering about the display issue myself.
v12xke said:
The latest build 3.1.0.0 works perfectly backing up and restoring backups made with that same version. Older builds certainly have issues, so you may not be able to properly restore a backup made with an earlier version. I think the greater question is what happens when you flash stock? I'd be wondering about the display issue myself.
Click to expand...
Click to collapse
There are no problems with stock. I flash my custom rom or stock but the problem only happens after restoring data and rebooting. I made the backup on the same version of TWRP I am currently on trying to restore it so I don't know what the issue is.
I have multiple backups that work perfectly fine on both the official and the f2fs modified builds. Like mentioned above, older versions had issues. Are you trying to restore on a different version of TWRP than the backup was created on? That is sometimes an issue also, though I'm not familiar with that issue on the 6P. Try to figure out what is different now than when the same backups we successful.
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
I have multiple backups that work perfectly fine on both the official and the f2fs modified builds. Like mentioned above, older versions had issues. Are you trying to restore on a different version of TWRP than the backup was created on? That is sometimes an issue also, though I'm not familiar with that issue on the 6P. Try to figure out what is different now than when the same backups we successful.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
I made the backup on unofficial twrp 3.1.0-7 f2fs and tried restoring on it too. The backup has worked fine on this same version of TWRP before but isn't now. The backup restores fine but the screen just goes black after it boots up.
DEVILOPS 007 said:
I made the backup on unofficial twrp 3.1.0-7 f2fs and tried restoring on it too. The backup has worked fine on this same version of TWRP before but isn't now. The backup restores fine but the screen just goes black after it boots up.
Click to expand...
Click to collapse
Did you try clearing art/dalvik cache and cache in TWRP advanced wipe maybe?
Good luck...
5.1 said:
Did you try clearing art/dalvik cache and cache in TWRP advanced wipe maybe?
Good luck...
Click to expand...
Click to collapse
I even formatted my phone
DEVILOPS 007 said:
I even formatted my phone
Click to expand...
Click to collapse
Thought it could be some old cache between ROM installs that could cause issue...
Good luck...
The bug I read about is apparently on version 3.0.2-1 and not on the latest build and involves a problem restoring the EFS partition, which probably doesn't apply to you. Sorry for the bad info. But I've made Nandroid backups on various builds of TWRP and never restored one successfully --and I've been rooting my phones and flashing custom Roms for years. The 6P is the only phone I've ever had that problem on.
jhs39 said:
The bug I read about is apparently on version 3.0.2-1 and not on the latest build and involves a problem restoring the EFS partition, which probably doesn't apply to you. Sorry for the bad info. But I've made Nandroid backups on various builds of TWRP and never restored one successfully --and I've been rooting my phones and flashing custom Roms for years. The 6P is the only phone I've ever had that problem on.
Click to expand...
Click to collapse
Try not to restore the vendor partition. I've seen a year ago it would cause problem.
Thanks for the info everyone. I really appreciate it. I couldn't work this out and just bit the bullet and used nandroid manager to restore apps which sucks but everything seems fine now.
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.