Every once in a while, when I reboot my phone, it'll hang at the Axon logo (after the little "swoosh") for 15-20 minutes before it will completely boot up? It isn't running through the "Android is starting apps", I know to expect that when I clear the cashe or install a fresh ROM. This is just on a "Hey, I'm going to reboot my phone today".
I am rooted (for custom fonts and emoji's), no Xposed.
It doesn't happen every time, maybe 3 times over the past month.... But it always happens at the worst time (it seems).
My external SD card has about 28gb of stuff on it, could it be scanning that?
Do you use SuperSU ?
XblackdemonX said:
Do you use SuperSU ?
Click to expand...
Click to collapse
Yes
2.76
tele_jas said:
Yes
2.76
Click to expand...
Click to collapse
Using 2.76 su with Xposed, no long booting time,
Started happening when you replace fonts and emojis?
DrakenFX said:
Using 2.76 su with Xposed, no long booting time,
Started happening when you replace fonts and emojis?
Click to expand...
Click to collapse
No, that's why it's so hard to narrow down.... First time it did it, I actually had Xposed installed. I restored my TWPR backup to when I didn't flash any extra's, just the stock apps and my user apps. I let that be for a few days and it did it to me then too, so I realized my fonts and emoji's didn't make a difference, so I put them back in, but left Xposed off.
I wish I had a backup of before I installed all my apps, right after I installed TWRP, but I deleted it on accident.
tele_jas said:
Yes
2.76
Click to expand...
Click to collapse
I suspect that this could be why. Try SuperSU 2.65 like suggested in DrakenFX's post
Source: My OnePlus One takes 7 minutes to boot
Maybe you can get a logcat while it boots? We might be able to see what's happening in those 15 minutes.
dennis96411 said:
Maybe you can get a logcat while it boots? We might be able to see what's happening in those 15 minutes.
Click to expand...
Click to collapse
that is actually a good solution ,
Related
It's been running perfectly fine the past 24 hours, but I hadn't wiped these since adding all the new apps to my phone, so I wiped those (in advanced wipe) like I've done 100's of times before on other ROOTed phones. Now, my A7 has been sitting at the Axon logo for about 15 minutes.
It's warm/hot like it's doing something but I can't tell? I rebooted it and it did the little swoosh and animation, then back at the Axon logo again.
Has anyone else experienced a LONG wait at the Axon 7 logo after wiping those?
[EDIT]
I gave up and did a complete wipe and restored my backup from last night. I didn't wipe anything after the restore and it booted up in less than 2 minutes and seems to be working fine.
tele_jas said:
It's been running perfectly fine the past 24 hours, but I hadn't wiped these since adding all the new apps to my phone, so I wiped those (in advanced wipe) like I've done 100's of times before on other ROOTed phones. Now, my A7 has been sitting at the Axon logo for about 15 minutes.
It's warm/hot like it's doing something but I can't tell? I rebooted it and it did the little swoosh and animation, then back at the Axon logo again.
Has anyone else experienced a LONG wait at the Axon 7 logo after wiping those?
[EDIT]
I gave up and did a complete wipe and restored my backup from last night. I didn't wipe anything after the restore and it booted up in less than 2 minutes and seems to be working fine.
Click to expand...
Click to collapse
i now you just edited your OP, but here a few Note:
1- when you do a Dalvik Cache wipe , Your device will take minutes to boot (is like your done a Full Factory Reset and yes may take longer tahn 10 or 15 mins sometimes)
2- now that you know you have a perfect backup, do a extra copy and move it to your PC or SDCard or just both.
DrakenFX said:
i now you just edited your OP, but here a few Note:
1- when you do a Dalvik Cache wipe , Your device will take minutes to boot (is like your done a Full Factory Reset and yes may take longer tahn 10 or 15 mins sometimes)
2- now that you know you have a perfect backup, do a extra copy and move it to your PC or SDCard or just both.
Click to expand...
Click to collapse
I have a backup on my SD card now.....
I've been running custom ROMs for 4 years and have done this probably 2000+ times. Usually it doesn't hang at the logo that long, but instead goes to the optimizing apps screen. When it has hung, like on my Nexus 6P, it meant something screwed up and I had go back and restore a backup. But I've also come to realize that every phone is different and the Axon may have needed a few more minutes.
But, I did wipe them when I installed Xposed yesterday afternoon and it didn't hang?
There's no telling? I know this is all new right now for the A7, it'll get easier and more reliable as time goes by.
Did you use systemless root?
Sent from my 6045I using XDA Premium HD app
Recon Freak said:
Did you use systemless root?
Sent from my 6045I using XDA Premium HD app
Click to expand...
Click to collapse
I'm not sure?
I unlocked my bootloader
Flashed TWRP
Flashed SuperSU 2.65
adb command to disable system write protection
Flashed Xposed (which I know breaks systemless ROOT).
tele_jas said:
I'm not sure?
I unlocked my bootloader
Flashed TWRP
Flashed SuperSU 2.65
adb command to disable system write protection
Flashed Xposed (which I know breaks systemless ROOT).
Click to expand...
Click to collapse
Try using the latest supersu (2.74 maybe). But before you flash it go to terminal inside twrp. Once in terminal type (no quotes) "echo SYSTEMLESS=true >> /data/.supersu. Then flash the latest supersu. Upon reboot it will take longer than normal. Once rebooted open supersu app. It should tell you the binary needs updated. Update ti using the normal option. Then reboot. Supersu should be good to go. Then if you like falsh the Xposed. See if all is gtg.
Delete
So this started happening right after flashing the newest TWRP through TWRP and the newest SuperSU through recovery as well. I rebooted and then it started. No other obvious issues besides the constant notification-like vibrations. There has to be a way to fix this right? Oh, I have JasmineROM installed too, it wasn't happening until I did this though.
CakeWizard said:
So this started happening right after flashing the newest TWRP through TWRP and the newest SuperSU through recovery as well. I rebooted and then it started. No other obvious issues besides the constant notification-like vibrations. There has to be a way to fix this right? Oh, I have JasmineROM installed too, it wasn't happening until I did this though.
Click to expand...
Click to collapse
Which TWRP? Make sure it is the hltevzw version.
Also, try this... Boot into recovery, wipe cache and davlik, reboot. It will take a while to fully boot.. But you'll see a message about updating (it's rebuilding davlik) app X out of Xxx... This could take 10 or 15 minutes.. So make sure you have at least 50% battery or plug in to charger when you reboot.
See if the vibration goes away.
Sent from my SM-N900V using Tapatalk
donc113 said:
Which TWRP? Make sure it is the hltevzw version.
Also, try this... Boot into recovery, wipe cache and davlik, reboot. It will take a while to fully boot.. But you'll see a message about updating (it's rebuilding davlik) app X out of Xxx... This could take 10 or 15 minutes.. So make sure you have at least 50% battery or plug in to charger when you reboot.
See if the vibration goes away.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Yeah, I tried that and it was still persisting so after that I just pulled a "**** it" and reflashed everything, the rom and superSU. Lo and behold I haven't noticed it vibrating randomly anymore. My battery was dying fast because of that issue but I think that's also fixed now. Thanks anyway good sir. :victory:
CakeWizard said:
Yeah, I tried that and it was still persisting so after that I just pulled a "**** it" and reflashed everything, the rom and superSU. Lo and behold I haven't noticed it vibrating randomly anymore. My battery was dying fast because of that issue but I think that's also fixed now. Thanks anyway good sir. :victory:
Click to expand...
Click to collapse
What Kernel you are using?
Hello, I am uploading my MOD ROM and kernel for Sprint. A previous attempt failed, and I just learned that the boot.img I had received was not the actual stock Sprint ROM, so the RAMdisk did not work.
Need someone, or some people to test, so I can make an official post in the ROM section.
As always, I recommend doing a full backup in TWRP to be able to restore to if the ROM does not work.
Also, Titanium Backup is the go-to app to backup your apps (do not backup system apps, only apps that you yourself have downloaded).
Must be on the latest TWRP. Must be fully decrypted. Do a clean flash.
Here is the latest test. I believe it should be fine. Static boot will remain since you have a bootloader not made for your device.
(reuploading, old zip would not flash due to a typo)
Updated, fixed link : https://mega.nz/#!LdkglIyY!8xJVm_1tTNwfrItn-t1n9bq4ZPginAL-DpW07hMwj8o
Tilde88 said:
As always, I recommend doing a full backup in TWRP to be able to restore to if the ROM does not work.
Also, Titanium Backup is the go-to app to backup your apps (do not backup system apps, only apps that you yourself have downloaded).
Must be on the latest TWRP. Must be fully decrypted. Do a clean flash.
Here is the latest test. I believe it should be fine. Static boot will remain since you have a bootloader not made for your device.
https://mega.nz/#!bUlE1RRa!Owuf3BVtZ...Gq8iNcSBRbe4bw
Click to expand...
Click to collapse
what is the decryption key? it will not allow me to download it without it.
ruthlessnature said:
what is the decryption key? it will not allow me to download it without it.
Click to expand...
Click to collapse
whoops
Tilde88 said:
whoops
https://mega.nz/#!bUlE1RRa!Owuf3BVtZ3Hlm96b5jVPGDZZP7gsMGq8iNcSBRbe4bw
Click to expand...
Click to collapse
thanks gonna download now and give it a go I will report back as soon as I can.
ruthlessnature said:
thanks gonna download now and give it a go I will report back as soon as I can.
Click to expand...
Click to collapse
hold on. i gotta reupload... there was a typo in the script >.> my bad
Tilde88 said:
hold on. i gotta reupload... there was a typo in the script >.> my bad
Click to expand...
Click to collapse
Ok let me know when it's good to go.
Sent from my iPhone using Tapatalk
ruthlessnature said:
Ok let me know when it's good to go.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Here is the updated link
Sorry about that!
https://mega.nz/#!LdkglIyY!8xJVm_1tTNwfrItn-t1n9bq4ZPginAL-DpW07hMwj8o
Tilde88 said:
Here is the updated link
Sorry about that!
https://mega.nz/#!LdkglIyY!8xJVm_1tTNwfrItn-t1n9bq4ZPginAL-DpW07hMwj8o
Click to expand...
Click to collapse
I have not been able to get it to boot up. it stays stuck on the static screen? I tried 3 times and did a full wipe all 3 times.
ruthlessnature said:
I have not been able to get it to boot up. it stays stuck on the static screen? I tried 3 times and did a full wipe all 3 times.
Click to expand...
Click to collapse
How long are you waiting? First boot takes about 15 mins.
You still have to do whatever the static boot fix is.
Tilde88 said:
How long are you waiting? First boot takes about 15 mins.
You still have to do whatever the static boot fix is.
Click to expand...
Click to collapse
I waited awhile id say atleast 30 min each time. it never gets to the point where I can shut off the screen to do the static fix. I'm in the process of trying again I will let it sit for awhile longer and see what happens.
Still couldnt get it to boot not sure why.
I locked up too. It happens just about a second into the boot animation. I can see maybe colored balls swirling and then some light text starts to fade in right in the center of the screen then it locks up. Pulled the battery and booted it up a 2nd time just in case but it also locked up and never finished. Gave it 30 minutes the first time and 15 on the second boot attempt.
I have system-less root on my Huawei Ascend XT and also system-less Xposed installed and working. See https://forum.xda-developers.com/showpost.php?p=70512435&postcount=3 for Xposed installation instructions I used.
Let's discuss anything regarding Xposed and modules in this thread .
Thanks, divineBliss
EDIT: WARNING: NOTE: CAUTION:
Please be aware that if you install Xposed framework on your XT, at times the phone won't boot correctly as evidenced by the fact that if you try to go to bring up the phone settings window/app, the screen will just flicker and the settings screen won't open. The simple solution is to just reboot the phone. Sometimes it takes multiple reboots before the phone successfully reboots/settings app can be successfully opened. This issue has been experienced by me and several others who installed Xposed framework on the XT.
For me personally, the advantages of using Xposed modules far outweigh this minor inconvenience which only happens after a phone reboot.
Not running xposed yet but have there been any issues or maybe a list of what works and doesn't? I'd like to know what others are getting from xposed.
Sent from my H1611 using Tapatalk
I got Xposed modules that let me listen to YouTube with app YouTube app minimized and even screen off.
And another module to adjust YouTube volume/scroll video by swiping on video screen.
See
http://www.howtogeek.com/263663/how...k-for-frustration-free-android-customization/
I used Magisk to install Xposed framework.
Also see: https://forum.xda-developers.com/showpost.php?p=70472229&postcount=488
Some how Xposed didn't install right, It wasn't working so I uninstalled it. My phone started to boot to recovery mode. Couldn't get passed it. I went into TWPR and recovered the Boot backup that TWRP installs to your internal. It "worked" but whenever it booted back to the home screen I got a black screen with nothing but for my notification bar and soft keys.
I tried to use my Backup from whenever I rooted but they are not showing up. I backed them up onto my computer so I put them onto my SD card and they are still not showing up in TWRP
1. After you installed Xposed with Magisk and rebooted the phone, what happened?
2. Did you wait about 30 minutes if the screen was dark or on the boot logo?
3. Go into TWRP and make sure you selected external SD for source. Use the TWRP file manager to make sure you it can access external SD - specifically the folder where you put the TWRP backup.
dabadguycr said:
Some how Xposed didn't install right, It wasn't working so I uninstalled it. My phone started to boot to recovery mode. Couldn't get passed it. I went into TWPR and recovered the Boot backup that TWRP installs to your internal. It "worked" but whenever it booted back to the home screen I got a black screen with nothing but for my notification bar and soft keys.
I tried to use my Backup from whenever I rooted but they are not showing up. I backed them up onto my computer so I put them onto my SD card and they are still not showing up in TWRP
Click to expand...
Click to collapse
divineBliss said:
1. After you installed Xposed with Magisk and rebooted the phone, what happened?
2. Did you wait about 30 minutes if the screen was dark or on the boot logo?
3. Go into TWRP and make sure you selected external SD for source. Use the TWRP file manager to make sure you it can access external SD - specifically the folder where you put the TWRP backup.
Click to expand...
Click to collapse
1. It was working great for about 20mins than everything started to freeze up and crash. Everything before was working great.
2. Yes, it only took around 10mins to boot back up.
3. I did that and my SD card is showing up. What file should the backups be in? I'm thinking I should make another backup than place the ones I have into that file.
I'm wondering if it is something with my launcher. I get Notification bar with everything and Soft key but nothing else.
1. After it booted up fine for 20 minutes, what did you do during that 20 minutes before it crapped out?
2 . So after you installed Xposed Framework with Magisk, the phone booted up fine within 10 minutes?
3. Yes, go back into TWRP and backup just the recovery so you see what directory it creates, then put your original TWRP backup into a similar parallel directory and see what happens.
What launcher are you using?
dabadguycr said:
1. It was working great for about 20mins than everything started to freeze up and crash. Everything before was working great.
2. Yes, it only took around 10mins to boot back up.
3. I did that and my SD card is showing up. What file should the backups be in? I'm thinking I should make another backup than place the ones I have into that file.
I'm wondering if it is something with my launcher. I get Notification bar with everything and Soft key but nothing else.
Click to expand...
Click to collapse
divineBliss said:
1. After it booted up fine for 20 minutes, what did you do during that 20 minutes before it crapped out?
2 . So after you installed Xposed Framework with Magisk, the phone booted up fine within 10 minutes?
3. Yes, go back into TWRP and backup just the recovery so you see what directory it creates, then put your original TWRP backup into a similar parallel directory and see what happens.
What launcher are you using?
Click to expand...
Click to collapse
I did 3. Took about 5mins to reboot. No launcher but luckily I had a pop up for updates so I was able to get into store to download a launcher.
imma try to download one.
It just says Download Pending nothing else.
Did you just restore a TWRP backup? Rooted backup or before root backup? Why was there no launcher in this backup?
dabadguycr said:
I did 3. Took about 5mins to reboot. No launcher but luckily I had a pop up for updates so I was able to get into store to download a launcher.
imma try to download one.
Click to expand...
Click to collapse
divineBliss said:
Did you just restore a TWRP backup? Rooted backup or before root backup? Why was there no launcher in this backup?
Click to expand...
Click to collapse
I thought I froze the stock launcher I think I may have deleted it. The stock launcher is found in the System files since it's read only I can not restore the system.
I thought I placed the stock recovery on my phone but I guess not. I still have super user and root.
I just checked my root with rootchecker and its working perfectly.
You can check or uncheck the box when TWRP starts to make System writable and you need to do that now to restore your System backup from TWRP. If you made a backup after rooting, you could try to restore that.
dabadguycr said:
I thought I froze the stock launcher I think I may have deleted it. The stock launcher is found in the System files since it's read only I can not restore the system.
I thought I was using a stock back up but I still have root.
Click to expand...
Click to collapse
Is your phone working now? What was the lesson learned out of all this? Got some notes/bullets to share for others?
dabadguycr said:
I thought I froze the stock launcher I think I may have deleted it. The stock launcher is found in the System files since it's read only I can not restore the system.
I thought I placed the stock recovery on my phone but I guess not. I still have super user and root.
I just checked my root with rootchecker and its working perfectly.
Click to expand...
Click to collapse
divineBliss said:
Is your phone working now? What was the lesson learned out of all this? Got some notes/bullets to share for others?
Click to expand...
Click to collapse
Yes, it's working again!!
I learned be very very careful removing Xposed and do not remove or freeze the stock launcher.
If you are restoring from a older backup and it doesn't show up. Make a new backup (I did cache only back up so I could tell the difference easier) on your SD Card. It should create a folders called
TWRP/BACKUP/(folder with 8 different letters and numbers) / (Then your new backup file)
Place your old backup folder under the new one. It will now show up in TWRP.
It's safe to restore a backup with root and super user. Takes around 10mins first boot.
Now that you have mastered restoring in 10 minutes, try Xposed again. I got it installed first try with Magisk. .
Every time I boot, I click the settings icon to make sure it works. Sometimes the screen just flashes and no settings screen comes up, so I just reboot. I'm not sure if that's caused by Xposed or what at this point, but it's not worth uninstalling Xposed for me to find out at this point.
dabadguycr said:
Yes, it's working again!!
I learned be very very careful removing Xposed and do not remove or freeze the stock launcher.
If you are restoring from a older backup and it doesn't show up. Make a new backup (I did cache only back up so I could tell the difference easier) on your SD Card. It should create a folders called
TWRP/BACKUP/(folder with 8 different letters and numbers) / (Then your new backup file)
Place your old backup folder under the new one. It will now show up in TWRP.
It's safe to restore a backup with root and super user. Takes around 10mins first boot.
Click to expand...
Click to collapse
divineBliss said:
Now that you have mastered restoring in 10 minutes, try Xposed again. I got it installed first try with Magisk. .
Every time I boot, I click the settings icon to make sure it works. Sometimes the screen just flashes and no settings screen comes up, so I just reboot. I'm not sure if that's caused by Xposed or what at this point, but it's not worth uninstalling Xposed for me to find out at this point.
Click to expand...
Click to collapse
I honestly think Magisk uninstall was what crashed my phone. I think I may have uninstalled it wrong. From the guide I read it said download the uninstall go into custom recovery and open the zip. I just thought it was Xposed because that's when my system started freezing.
divineBliss said:
Thanks, these details are important. So make a backup of Boot, System, and Data (and be sure you already have a good backup of Cust somewhere) if you want to try installing Xposed again. Depending on what else you do, you should only need to restore System if things get messed up trying to install Xposed again. And again, I have it installed with Xposed modules working, so it's possible.
Click to expand...
Click to collapse
Does installing Xposed even touch the system? It looked like it modifies the boot but doesn't touch the system.
The Xposed install is supposed to be system-less, and you get did things working by only restoring Boot, that's why I said probably just Boot needs to be restored. If things didn't work after that, I'd restore System, and then if still not working, restore Data after that.
If you do try and reinstall Xposed, can you take notes on where it takes a long wait before something happens ........ I forgot to do that and don't remember now. It's not fun when the screen goes dark and you don't expect it ....... actually I seem to remember that happening for like 30 minutes ??? when I install Magisk/Xposed ........ the screen wasn't even on.
dabadguycr said:
Also
Does installing Xposed even touch the system? It looked like it modifies the boot but doesn't touch the system.
Click to expand...
Click to collapse
divineBliss said:
The Xposed install is supposed to be system-less, and you did things working by only restoring Boot, that's why I said probably just Boot needs to be restored. If things didn't work after that, I'd restore System, and then if still not working, restore Data after that.
If you do try and reinstall Xposed, can you take notes on where it takes a long wait before something happens ........ I forgot to do that and don't remember now. It's not fun when the screen goes dark and you don't expect it ....... actually I seem to remember that happening for like 30 minutes ??? when I install Magisk/Xposed ........ the screen wasn't even on.
Click to expand...
Click to collapse
I'm going to install it manually. I think Magisk was what missed up my phone last time so I rather go that path then taking the chance at missing something up again.
I'm going to install sdk23 should I install arm arm64 or x86.
I don't believe our phone is a 32bit system so x86 is out. I think arm64? Correct?
Yes, arm64. Take notes and good luck . Do you have a link on how to install it manually?
dabadguycr said:
I'm going to install it manually. I think Magisk was what missed up my phone last time so I rather go that path then taking the chance at missing something up again.
I'm going to install sdk23 should I install arm arm64 or x86.
I don't believe our phone is a 32bit system so x86 is out. I think arm64? Correct?
Click to expand...
Click to collapse
divineBliss said:
Yes, arm64. Take notes and good luck . Do you have a link on how to install it manually?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3034811
I'm using this link.
Believe I just download the zip to SD card
Go into TWRP
Click install
Find the zip
Swipe to install
Click Wipe
Wipe cache and dalvik
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.