Database Users

Having problems after Froyo :(

Initially everything was good, clean install, had about 100 apps auto restored from market. The rest didnt restore because it was installing to system and ran out of space.
So enabled install to SD, installed most of the rest. Then put the new kernal on, and now nothing will install :/
It sits there saying its installing, but nothing happens Tried a fresh install and new kernal but still nope

Mine does this always, enabling apps on sd or not. Even after a fresh wipe, everything hangs at install. May be going back to 2.1 soon.

jsapp said:
Mine does this always, enabling apps on sd or not. Even after a fresh wipe, everything hangs at install. May be going back to 2.1 soon.
Click to expand...
Click to collapse
.................

I've noticed this, too. The app actually does finish installing, but the market app never clears the "installing" screen. It's annoying, but not actually a problem; if you just hit "back" and go on about your business, the app you were installing will be usable.

wmm said:
I've noticed this, too. The app actually does finish installing, but the market app never clears the "installing" screen. It's annoying, but not actually a problem; if you just hit "back" and go on about your business, the app you were installing will be usable.
Click to expand...
Click to collapse
Im trying to restore from titanium, which also reports the installation is failing.

I've had this problem on some 2.1 builds, but haven't run into a single issue since updating to 2.2. I haven't done any mods (except rooting) to 2.2 tho. Maybe that could be the problem?

Found solution at another xda thread: http://forum.xda-developers.com/showpost.php?p=6596969&postcount=3
Code:
adb reboot recovery #wait for recovery to load
adb shell
mount /sdcard
rm -r /sdcard/.android_secure
reboot
Click to expand...
Click to collapse
Worked for me. Good luck!

Bricked Vibrant, Assistance greatly appreciated

Hi all,
Sot of new to modding, think I screwed up and could use some help. Was doing this one click speed fix: forum.xda-developers.com/showpost.php?p=7587405&postcount=417
It didn't appear to work the first time, as I received a message and exited the application, however the symbol was still in the notification bar. Re-ran it, and it seemed to have worked, mostly, as the phone was blazing fast. Went immediately to run quadrant and check the benchmark, but it force closed every time it hit the i/o section. tried to go to market, foreclose every time. Figured it may need a reboot, powered off, and that's was all she wrote.
I can get into the battery charging screen and have been able to get to recovery, but nothing else. I haven't used adb or ODIN at all yet, but any assistance is greatly appreciated.
The phone was already rooted, and i have titanium back up and nandroid backups, but don't really know how to get to them.

If you did a nandroid backup, just go in recovery screen and restore backup. If not, flash back to stock rom.

well maybe i dont know what im talking about then. I guess I thought i did a nandroid.
When i go into recovery i get four options: reboot system now, reinstall packages, clear all user data, clear cache data.
none of them work

Did you install clock work recovery via Rom manager?

well it has turned on now. removed sim and memory card and hit reinstall packages. ive got the standard twlauncher running but, it repeatedly gives me force close notifications that android.process.media has stopped and i cannot access the menu

s15274n said:
Did you install clock work recovery via Rom manager?
Click to expand...
Click to collapse
yes, i did. i remember doing that precisely as shown in your tips and tricks thread

alright, so i got it into download mode, gonna reflash everything to stock and see where i went wrong as outlined here: http://forum.xda-developers.com/showthread.php?t=734475
Will update with results, but would be nice to figure out where i went wrong so as not to repeat the error.

If you can get into recovery just wipe and reflash eugenes vibrant4.zip.

Alright, back to stock. unrooted also? gonna mess some more and see if i can get my clockword recovery to restore everything.

okay, so my theory is that the lag fix i used installed an update.zip that overwrote the clockword mod one. Now im just trying to restore using titanium backup, but it is telling me that it doesnt have root access. i know im rooted, as i just did it and reinstalled rom manager and drocap. hmmmmm.....
Thats not all thats funny. i cant find the superuser app anywhere on here. also, i cannot install one from the market.
and im having issues with root explorer.

Civil Disobedient said:
okay, so my theory is that the lag fix i used installed an update.zip that overwrote the clockword mod one. Now im just trying to restore using titanium backup, but it is telling me that it doesnt have root access. i know im rooted, as i just did it and reinstalled rom manager and drocap. hmmmmm.....
Click to expand...
Click to collapse
DAKIDD236 said:
If you can get into recovery just wipe and reflash eugenes vibrant4.zip.
Click to expand...
Click to collapse
I would re-root and then follow the flash the ROM mentioned above. There is a thread in the DEV forum.

Civil Disobedient said:
okay, so my theory is that the lag fix i used installed an update.zip that overwrote the clockword mod one. Now im just trying to restore using titanium backup, but it is telling me that it doesnt have root access. i know im rooted, as i just did it and reinstalled rom manager and drocap. hmmmmm.....
Thats not all thats funny. i cant find the superuser app anywhere on here. also, i cannot install one from the market.
and im having issues with root explorer.
Click to expand...
Click to collapse
You need to root again to get the superuser on your phone. As for the one click lag fix, I used to original method and it went pretty well. No problems so far. I also flashed Vibrant4 by Eugene before doing the lag fix. Hope it helps

same thing happened to me. I'm stuck on the galaxy S boot screen. i can get into the samsung recovery screen but not the clockwork recovery. I backed up my nandroid and Rom but don't know how to get into the menu to restore. I only have the update.zip for the lag fix on the internal sd so can't restore that way. Any ideas? Much appreciated.

kwbdc said:
same thing happened to me. I'm stuck on the galaxy S boot screen. i can get into the samsung recovery screen but not the clockwork recovery. I backed up my nandroid and Rom but don't know how to get into the menu to restore. I only have the update.zip for the lag fix on the internal sd so can't restore that way. Any ideas? Much appreciated.
Click to expand...
Click to collapse
There may be other ways around it, but I restored fully to stock, then re-rooted. I'm back up and running no problem now. Had some issues with titanium backup but got around that and its batch restoring as i type.

Civil Disobedient said:
There may be other ways around it, but I restored fully to stock, then re-rooted. I'm back up and running no problem now. Had some issues with titanium backup but got around that and its batch restoring as i type.
Click to expand...
Click to collapse
Would you mind saying how you did that?
I tried wiping and flashing the stock via renaming it update.zip, and I'm still getting FC city. Mostly media, but, calendar, everything. I'm going to post a link to this in that thread, since many, it seems, were left hanging in a boot loop.

Janis said:
Would you mind saying how you did that?
I tried wiping and flashing the stock via renaming it update.zip, and I'm still getting FC city. Mostly media, but, calendar, everything. I'm going to post a link to this in that thread, since many, it seems, were left hanging in a boot loop.
Click to expand...
Click to collapse
Just follow what I did through the thread.
I did this http://forum.xda-developers.com/showthread.php?t=734475 to get back to complete stock, then i had to root it twice. Once did the one click, then the good root here http://forum.xda-developers.com/showpost.php?p=7150299&postcount=1
back up and running. had to research about titanium backup to get it up and running. I want to do the lag fix still, but im nervous from before.

Your nervous? I really would like to do this but i'm scared (cuss)less.
I've read what needs to be done and think that I've figured it out.
(pretty new to droid)... but, have also read the horror stories here
about bricking your phone...which nowadays can happen to any
phone you have....don't get me started on the apple pie!
But, really when it gets a simple as installing an .APK I'll be happy.

Damitu said:
Your nervous? I really would like to do this but i'm scared .......
Click to expand...
Click to collapse
The galaxy s seems pretty hard to brick. I'd say just go for the lag fix. Worse thing that happens is you have to take like 15min to download and use odin to reflash to stock. The lag fix seems pretty safe as long as you stay rooted
Sent from my SGH-T959 using XDA App

Vibrant Recovery Mode HowTo
THIS GUIDE WORKED ON USA T-MOBILE SAMSUNG VIBRANT BUT MAY VERY WELL WORK ON ALL SAMSUNG GALAXYS PHONES
After reading many XDA-Developers Forum Posts to try and figure out how to get into the Recovery Mode / Download Mode without any success, I gave T-Mobile Support a call.
After the usual noop run-down, "did you take the battery out" questions, I simply asked them how to get the Samsung Vibrant into recovery mode.
Unline the many tutorials that claim to require the Up or Down button pressed, along with the Home button then the Power, the true process is as follows:
1. Press the Up and the Down button at the same time (yes both). I too thought that button was a Toggle which only did either Up or Down, but found that in fact it does do both.
2. At the same time, press the power button.
3. As soon as the Samsung / Vibrant logo comes up on the screen, release the power button.
4. Release the Up and Down buttons.
5. PRESTO

[Q] What is it?

Hi!
I don't know why but for some reason I lost some of my users app with data. Seems like it is the apps which were installed on my SD card. I can restore it trough the Titanium backup.
Can somebody explain what is going on and how can I prevent it in the future?
Thank you!
Edit: After I turned my Epic off and then turned it on again, everything was ok. I still don't know what it was but it was the apps installed on SD Card.

Did you flash a rom and then restored things thru titanium or any app?

This happens sometimes when google sends out an update to the market. The market cache just needed to be reset. Thats why a reboot fixed it.

musclehead84 said:
Did you flash a rom and then restored things thru titanium or any app?
Click to expand...
Click to collapse
No. I did nothing like this. As I understand, before it happened my Epic did quick reboot by itself. Some of the program was causing it.

CWM Error

Whenever I try to make a backup with CMW, it gives me an error that says "An error occurred while attempting to run privileged commands"
How do I fix it?

You have S-Off?

estallings15 said:
You have S-Off?
Click to expand...
Click to collapse
Yep fully rooted and everything. It worked before but not sure why it's not working now.

HTC~TwikiE said:
Yep fully rooted and everything. It worked before but not sure why it's not working now.
Click to expand...
Click to collapse
Try reflashing your recovery. Sounds like it's borked.

estallings15 said:
Try reflashing your recovery. Sounds like it's borked.
Click to expand...
Click to collapse
I just tried that and it gives me "An error occurred while downloading your recovery."
How do I do it manually?

HTC~TwikiE said:
I just tried that and it gives me "An error occurred while downloading your recovery."
How do I do it manually?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1242901

estallings15 said:
http://forum.xda-developers.com/showthread.php?t=1242901
Click to expand...
Click to collapse
Just tried that, back to square one. Same error

HTC~TwikiE said:
Just tried that, back to square one. Same error
Click to expand...
Click to collapse
Hmm, I'm getting worried that this may be a hardware problem. Does anybody have any ideas?

estallings15 said:
Hmm, I'm getting worried that this may be a hardware problem. Does anybody have any ideas?
Click to expand...
Click to collapse
The error isn't necessarily hardware; that message could be occurring because of a software problem with the su application that is being used.
- Have you been flashing/nandroiding successfully with CWM in the past?
- Were your su binaries updated recently?
- Did the ROM get an OTA recently that might have updated the su binaries?
- Was this failed backup being done after/before flashing a ROM that wasn't full-wiped?
- EDIT: Why of course you have S-off and anyone who asked after you said so would be a silly fellow.
If all else were to fail, I'd suggest going back to a stock ROM and re-rerooting, and I imagine that your problems would 'go away'. I'm not sure what intermediate methods you could try, though, unless you wanted to try to run your backup commands over adb or re-push your su binaries or .apk.

tuxkamen said:
The error isn't necessarily hardware; that message could be occurring because of a software problem with the su application that is being used.
- Have you been flashing/nandroiding successfully with CWM in the past?
- Were your su binaries updated recently?
- Did the ROM get an OTA recently that might have updated the su binaries?
- Was this failed backup being done after/before flashing a ROM that wasn't full-wiped?
- Do you have S-off?
If all else were to fail, I'd suggest going back to a stock ROM and re-rerooting, and I imagine that your problems would 'go away'. I'm not sure what intermediate methods you could try, though, unless you wanted to try to run your backup commands over adb or re-push your su binaries or .apk.
Click to expand...
Click to collapse
I was under the impression that your recovery didn't need the SU binary to do it's job. The SU binary is used within Android, right?
Edit: Also, he already said that he has S-Off. If you're going to offer help, please pay attention.

I had the same error show up recently. I just went around it and did a backup while in boot recovery.
... now... what to do if that starts to fail... Hmm
Sent from my myTouch 4g using xda app

estallings15 said:
I was under the impression that your recovery didn't need the SU binary to do it's job. The SU binary is used within Android, right?
Click to expand...
Click to collapse
I'm referring to both the Superuser.apk and the general su/busybox binaries (that got installed as part of his rooting process) which I think get used when doing the calls to make backups to your SD card. He's most likely getting the message because either his rooting method has gone awry or whatever his phone thinks is the appropriate way to get elevated privileges is no longer able to do that. The possible causes for that pretty much boil down to either permissions needing fixing or needing to redo the installation of the su "stuff".
I'm not sure how that would _happen_. This goes back to knowing what happened recently to the phone from a software perspective (any new ROM flash lately, potentially to something that doesn't have root perms?). He was able to reinstall CWM, but he may need to re-push the su/busybox stuff in order to get back to full functionality (and maybe do it a few times, just like in the initial rooting process, to make sure it 'sticks').
Edit: Also, he already said that he has S-Off. If you're going to offer help, please pay attention.
Click to expand...
Click to collapse
I'm not sure why I wrote that. I did notice he said it, said 'meh' and wrote it down anyway. -_-

tuxkamen said:
I'm referring to both the Superuser.apk and the general su/busybox binaries (that got installed as part of his rooting process) which I think get used when doing the calls to make backups to your SD card. He's most likely getting the message because either his rooting method has gone awry or whatever his phone thinks is the appropriate way to get elevated privileges is no longer able to do that. The possible causes for that pretty much boil down to either permissions needing fixing or needing to redo the installation of the su "stuff".
I'm not sure how that would _happen_. This goes back to knowing what happened recently to the phone from a software perspective (any new ROM flash lately, potentially to something that doesn't have root perms?). He was able to reinstall CWM, but he may need to re-push the su/busybox stuff in order to get back to full functionality (and maybe do it a few times, just like in the initial rooting process, to make sure it 'sticks').
I'm not sure why I wrote that. I did notice he said it, said 'meh' and wrote it down anyway. -_-
Click to expand...
Click to collapse
No offense, but I'm fairly positive you can perform all the functions in recovery with a completely wiped system partition. If that is the case, then that theory is debunked. S-Off should give you all access/permissions you need. This is why I said that I'm worried about his hardware. If his bootloader was HTC dev unlocked, then I would say he needed S-Off.

estallings15 said:
No offense, but I'm fairly positive you can perform all the functions in recovery with a completely wiped system partition. If that is the case, then that theory is debunked. S-Off should give you all access/permissions you need. This is why I said that I'm worried about his hardware. If his bootloader was HTC dev unlocked, then I would say he needed S-Off.
Click to expand...
Click to collapse
The error message he's getting is from trying to start his backup out of ROM Manager, not recovery--that error usually pops up before going into the backup process. You can verify this yourself by temp unrooting in Superuser, launching ROM Manager, and trying to do something like make a backup or fix permissions. I have a feeling TwikiE could do backups by _booting_ into recovery.
That's why I'm suggesting the need to check the Superuser implementation. ROM Manager doesn't think it has either root permission or privileges. If TwikiE isn't seeing the 'you must be rooted' popup when starting ROM Manager, then the phone is rooted but the app doesn't think it's privileged to send the phone into the backup process. If this the first time TwikiE's tried a backup since his last ROM flash, the ROM might have a bad or incompatible set of root tools, or some other app may have been installed that has bad tools. Or maybe it's as simple as having accidentally hit Deny on a Superuser prompt.
Some things TwikiE could do to try and resolve the problem without rerooting could be:
- Try Fix Permissions out of ROM Manager and see if the same error message appears. If it succeeds, try backing up again. If not...
- Check the Superuser app settings to see if ROM Manager is on the list as allowed or denied. If it's on deny, clear it out. If it's allowed or not there, move on.
- Clear out the application data and cache for both the Superuser app and ROM Manager from the apps menu. Try to backup again and see if the superuser prompt appears.
- If that doesn't work, try uninstalling and reinstalling Superuser and ROM Manager from the Play Store, reinstalling both, then try to backup.
Beyond that comes more drastic steps.

tuxkamen said:
The error message he's getting is from trying to start his backup out of ROM Manager, not recovery--that error usually pops up before going into the backup process. You can verify this yourself by temp unrooting in Superuser, launching ROM Manager, and trying to do something like make a backup or fix permissions. I have a feeling TwikiE could do backups by _booting_ into recovery.
That's why I'm suggesting the need to check the Superuser implementation. ROM Manager doesn't think it has either root permission or privileges. If TwikiE isn't seeing the 'you must be rooted' popup when starting ROM Manager, then the phone is rooted but the app doesn't think it's privileged to send the phone into the backup process. If this the first time TwikiE's tried a backup since his last ROM flash, the ROM might have a bad or incompatible set of root tools, or some other app may have been installed that has bad tools. Or maybe it's as simple as having accidentally hit Deny on a Superuser prompt.
Some things TwikiE could do to try and resolve the problem without rerooting could be:
- Try Fix Permissions out of ROM Manager and see if the same error message appears. If it succeeds, try backing up again. If not...
- Check the Superuser app settings to see if ROM Manager is on the list as allowed or denied. If it's on deny, clear it out. If it's allowed or not there, move on.
- Clear out the application data and cache for both the Superuser app and ROM Manager from the apps menu. Try to backup again and see if the superuser prompt appears.
- If that doesn't work, try uninstalling and reinstalling Superuser and ROM Manager from the Play Store, reinstalling both, then try to backup.
Beyond that comes more drastic steps.
Click to expand...
Click to collapse
Who does anything in ROM Manager? Damn it, OP, reboot into recovery and do it right.

Heh. I didn't want to put it *exactly* that way...
Sent from my HTC myTouch 4g using xda app-developers app

Xposed on Huawei Ascend XT

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