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
Related
ok something crashed on my modaco rom. super user wont work when it goes to it it just shows black screen. tried deleting cache on it and data. no fix. cant use tether or anything root.
I'd reapply the ROM or restore from backup.
i cant do that. everytime i do a nandroid backup it messes up cause of apps2sd.
I had a similar problem. I installed the Su app from the marketplace over it then i uninstalled it and it fixed the app. Worked for me.
ok i tried reloading rom and same thing. i cant find the app you are talking about. is it the super user whitelist. i cant install anything root now when it goes to su and you have to allow it all i get is black screen and it force closes
pitmanr2003 said:
ok i tried reloading rom and same thing. i cant find the app you are talking about. is it the super user whitelist. i cant install anything root now when it goes to su and you have to allow it all i get is black screen and it force closes
Click to expand...
Click to collapse
Yes its the Super whitelist app.
try reformatting the ext partition first. Wipe the system than do a system restore or nandroid restore. If you did a nandroid backup of the faulty system than I hope you have the stock nandroid backup as well.
ok tried the super whitelist and it downloads but never installs just sends me back to the sprint flash and restarts. i dont really want to restore back cause then i have to download all my apps again. im seriously thinking that apps2sd are more trouble than they are worth. maybe some one can do a walkthrough on how to back them up in the event of a crash like this.
Same here
pitmanr2003 said:
ok tried the super whitelist and it downloads but never installs just sends me back to the sprint flash and restarts. i dont really want to restore back cause then i have to download all my apps again. im seriously thinking that apps2sd are more trouble than they are worth. maybe some one can do a walkthrough on how to back them up in the event of a crash like this.
Click to expand...
Click to collapse
I can confirm this behavior. I just reinstalled from a backup, installing whitelist from the Market gave me the unending HTC screen of death.
adb push Superuser.apk /system/app/
Superuser.apk can be found in any one of the available ROMs, fresh, gutted, MoDaCo, etc.
pitmanr2003 said:
ok something crashed on my modaco rom. super user wont work when it goes to it it just shows black screen.
Click to expand...
Click to collapse
Turn USB Debugging back on.
posguy99 said:
Turn USB Debugging back on.
Click to expand...
Click to collapse
Oh Snap! TY!
I'm having the same issue. Just in case, I ruu'd back and started over.
Everything works fine up to installing the rom.
Debugging is on.
Tried wiping the ext partion from flash screen, says "error" run wipe_ext via consle"
I tried installing the superuser whitelist app from market, and it won't install, says "incompatible update".
Tried pushing the superuser.apk, it says "failed to copy, read only file system.
Any ideas, i'm lost. I can run my nandroid back to before I installed the 1.2c modaco and it works fine, as soon as I install the rom nothing works in root.
I used SU File Manager & Terminal 3.0.6 to cut/copy/paste Superuser.apk back into the app folder. I then ran it and it installed with no problems and works great for me.
I made sure that I used the built in feature to make the system and data folders RW before I cut/copy/pasted anything. Hope this helps.
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 ,
Probably too soon to be asking but has anyone heard if Team Win is planning to support an Essential phone TWRP version?
Yes I know it's an old post, but I'm replying to this, rather then starting a new one...
Everyone knows TWRP sucks for this phone. Funny the OP asks about this. I was chatting the other day in the TWRP IRC channel on Freenode, and it seems, if they could get a phone, maybe this would be possible.
But in the meantime, is there anyone working on TWRP? It's really sad, that as long as this phone has been out, there's not better support for TWRP.
Hmm
I've only used twrp to boot to root on the PH1, but it does that perfectly every time (both IMG and zip).
What exactly doesn't it do?
kboya said:
I've only used twrp to boot to root on the PH1, but it does that perfectly every time (both IMG and zip).
What exactly doesn't it do?
Click to expand...
Click to collapse
1. Doesn't fit screen properly
2. Touch & Typing doesn't work properly
3. Backups & Restore don't seem to work properly - I'm still playing with it, maybe because of A/B I'm going about it wrong.
If this would fit the screen properly, and the touch and typing worked better, then it wouldn't be half bad.
I haven't noticed the first 2 (but touch in twrp has been janky on various phones since it began... A quick search will show this.)
Not tried backup/restore as Ive not used alpha/beta indy ROMs for several years (pre-6p I'd guess). Good luck with your mod attempt.
kboya said:
I haven't noticed the first 2 (but touch in twrp has been janky on various phones since it began... A quick search will show this.)
Not tried backup/restore as Ive not used alpha/beta indy ROMs for several years (pre-6p I'd guess). Good luck with your mod attempt.
Click to expand...
Click to collapse
If it fits the screen properly, can you take a picture? I'd like to see this.
For me, twrp leaves a space on the entire right side, it doesn't fill the screen properly...
I went back playing, and I did get a backup to work ok, now I'll need to see about restoring it and see if that goes ok.
I don't remember anything like the missing part you describe and I think if notice that! Sure, but it'll be next week before I can.
kboya said:
I don't remember anything like the missing part you describe and I think if notice that! Sure, but it'll be next week before I can.
Click to expand...
Click to collapse
I'm on the forum this week, but can't boot into TWRP till next week... LOL
What you loose your phone?
I've attached two screen shots, notice all the red dots, showing the gap on the right, compared to the left, and how the top right doesn't wrap around too...
Hahaha, no, I'm on holiday abroad without a laptop and I only boot into twrp via fastboot.
I've not noticed the gap that you show, but I'm not sure it would bother me enough to really consider it
I'll have a look when I get back.
DoR3M3 said:
I've attached two screen shots, notice all the red dots, showing the gap on the right, compared to the left, and how the top right doesn't wrap around too...
Click to expand...
Click to collapse
kboya said:
Hahaha, no, I'm on holiday abroad without a laptop and I only boot into twrp via fastboot.
I've not noticed the gap that you show, but I'm not sure it would bother me enough to really consider it
I'll have a look when I get back.
Click to expand...
Click to collapse
DoR3M3 said:
If it fits the screen properly, can you take a picture? I'd like to see this.
For me, twrp leaves a space on the entire right side, it doesn't fill the screen properly...
I went back playing, and I did get a backup to work ok, now I'll need to see about restoring it and see if that goes ok.
Click to expand...
Click to collapse
DoR3M3, he'll notice if he takes a close look at it. This is a documented issue that plagues EVERY PH1. It happens on my PH1 as well. Touch typing is indeed bad. The keyboard seems to be shifted left of what you actually are typing on.
Please keep us updated on your restoring experiences. I just rooted my 2nd PH1 and I'm also looking for ways to make a NANROID backup. Really want to hear your experience with the restoring part.
Thanks!
Try booting twrp on the opposite boot partition and make a nand backup from there and then try restoring from there. From what i understood it flashes to the opposite boot partition when twrp first came out im not sure if it still does that so its possible it does that to for nand backups and restores.
Ok I have managed to make a Backup and then Restore it!
MAKING THE BACKUP
These are the Steps I have taken, and take note, I do reboot, which some might assume isn't needed, but I have found, that if I didn't, then Magisk wasn't getting flashed in properly. Sometimes you just need to reboot between steps...
When you flash a Custom Rom, that should be on Slot A, then if you root with Magisk, Magisk will be flashed to Slot B. So now your BACKUP & RESTORE will be on Slot B! But some times I have seen people get their Slots flipped around, so however it ended up, the Slot you are making your BACKUP on, is the Slot that Magisk was flashed to, not the ROM!
1. IMPORTANT - TWRP does not backup the Internal Storage so this is a simple way of backing it up! Advanced > File Manager > data - RENAME the media folder > media.bak.
2. Now you are ready to make a BACKUP! All you need checked are Boot > System > Data - Click on (Auto Generate) to rename your BACKUP!
3. When the backup completes, now go back to Advanced > File Manager > data and you will see media, which is the new folder TWRP created with your backup in, and your old one you backed up, media.bak. Now you need to rename them both! Rename the new one to media.new and rename media.bak back to it's original name media. Now here's that reboot part I was talking about before, now Reboot > Bootloader.
4. For this step I'm assuming you're Rooted and using a Custom ROM, if that is the case, when you reboot back into TWRP > Install > lower right Install Image and pick the boot image, and make sure you flash it to Boot.
5. Now go back and Install Magisk.
6. You have now successfully made your TWRP backup, now reboot the system.
7. Once booted up and back in your system, start up your File Manager, I personally use and like FX File Manager with Root Access. Now you'll navigate to data and you should still see your two directories media & media.new. In FX File Manager I have this path, data > media.new > 0 > TWRP > BACKUPS. You want to copy BACKUPS to your Internal Storage TWRP directory. So in your Internal Storage you end up with TWRP > BACKUPS. Once you are done copying it, it's safe to delete the media.new directory, but just make sure you have copied the BACKUPS directory.
8. To test that you have your BACKUPS in the right path, boot into TWRP and click on Restore, if it shows up, you placed it in the correct path!
DOING THE RESTORE
With the A/B partitions, if you are rooted and running Magisk, then you will have noticed, that you installed your ROM into Slot A, then you should of rebooted back to the Bootloader, rebooted back into TWRP and installed the boot.img and Magisk, on Slot B. But as I mentioned above, some times people get their Slots flipped around, so remember, whichever Slot your flashed Magisk to, is the Slot you RESTORE on!
1. Boot into TWRP, which I'm assuming by my above statement, you are on Slot B, click Restore, click your backup, then make sure all partitions are checked, and then swipe.
2. Now reboot to the Bootloader, then reboot back into TWRP and Install your boot.img and Magisk.
3. Next go to Advanced > File Manager > data and you'll now see media & media.bak, confused? LOL Just think about it for a second, and you can delete media.bak.
4. Now reboot into your system and enjoy!
I'd like to add for anyone saying we don't need Twrp - Same reasons virtually every other phone gets a working build of it. If there was no need or demand for it, they'd cease to exist and people will stop using it. But every couple of weeks, there's an announcement of new phones getting TWRP.
DoR3M3 said:
Ok I have managed to make a Backup and then Restore it!
Click to expand...
Click to collapse
lol. Thanks for the step by step. It does seem a bit overwhelming for the uninitiated. I'll give it a try once I've had more time to digest the whole process.
Maybe we can get that post pinned. Thanks again for testing.
We do need TWRP, it's a great tool, that does simplify many things all in one...
@Lakino, it's not complicated at all, just a few steps, and once you've done it, then you'll see how easy it is, and come back and tell us then...
The TWRP guys have an Essential phone now so they will work on it but it sounds like not until Pie is figured out.
galakanokis said:
The TWRP guys have an Essential phone now so they will work on it but it sounds like not until Pie is figured out.
Click to expand...
Click to collapse
Woo time to round up the Army and head over to Freenode - #twrp
Get your butts over their people!
I'll be looking for Essential peeps chatting...
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.
I really miss the FULL backup that twrp used to have. Aka "nandroid" backup where you can backup partitions in case you add a module that screws up the phone. Is there another way to do this since there is no working twrp for the 8pro? (I'm on 11.0.2.2.IN11AA if that matters)
Thanks
glhelinski said:
I really miss the FULL backup that twrp used to have. Aka "nandroid" backup where you can backup partitions in case you add a module that screws up the phone. Is there another way to do this since there is no working twrp for the 8pro? (I'm on 11.0.2.2.IN11AA if that matters)
Thanks
Click to expand...
Click to collapse
No there is no functional TWRP for Android 11.
Primary reason for this is because it simply isn't needed.
There are scripts for ROMs that work just fine.
As for magisk modules then there is a simple fix for that too
Magisk module failure.
This works for any magisk module failure.
1. Power off your phone by holding the power button, then turn it back on.
2. As your phone gets to the bootloader warning screen, press and hold volume up and down and continue to hold until the phone shows the boot animation.
3. You'll boot to safe mode, simply reboot once more.
4. On next boot all your magisk modules will be disabled, remove the problematic module and re-enable the functional ones.
Unfortunately this all also means that there probably won't be any TWRP in the future as we just don't need it, it didn't hinder the developers of ROMs and we have an escape path from dodgy magisk ROMs and modules.
Xposed and kernels are slightly different but you still have a way back without restoring your OS.
So twrp is the only way to do a full backup then?
dladz said:
No there is no functional TWRP for Android 11.
Primary reason for this is because it simply isn't needed.
There are scripts for ROMs that work just fine.
As for magisk modules then there is a simple fix for that too
Magisk module failure.
This works for any magisk module failure.
1. Power off your phone by holding the power button, then turn it back on.
2. As your phone gets to the bootloader warning screen, press and hold volume up and down and continue to hold until the phone shows the boot animation.
3. You'll boot to safe mode, simply reboot once more.
4. On next boot all your magisk modules will be disabled, remove the problematic module and re-enable the functional ones.
Unfortunately this all also means that there probably won't be any TWRP in the future as we just don't need it, it didn't hinder the developers of ROMs and we have an escape path from dodgy magisk ROMs and modules.
Xposed and kernels are slightly different but you still have a way back without restoring your OS.
Click to expand...
Click to collapse
Thanks for your response... However i did find a case that the numbered steps above would not work. This was for renovate ice module. Safe mode produced system ui failure and couldn't get past it. I think it was you who helped me by resetting the system
glhelinski said:
Thanks for your response... However i did find a case that the numbered steps above would not work. This was for renovate ice module. Safe mode produced system ui failure and couldn't get past it. I think it was you who helped me by resetting the system
Click to expand...
Click to collapse
That's correct and probably due to the fact that R-ice does a lot more to your phone and doesn't revert back the changes it makes whereas the likes of xXx does,. AFAIK R-ice affects system but xXx does not.
For anything else it should be fine.
And lol yep I remember I think.
glhelinski said:
So twrp is the only way to do a full backup then?
Click to expand...
Click to collapse
In that sense yes, in regards to data and content no, titanium/swift, pc back up, Google sync
dladz said:
In that sense yes, in regards to data and content no, titanium/swift, pc back up, Google sync
Click to expand...
Click to collapse
I'm having good luck with swift. Titanium not so much anymore
glhelinski said:
I'm having good luck with swift. Titanium not so much anymore
Click to expand...
Click to collapse
Yea I know what you mean tbh
@glhelinski
What I found with titanium is that certain apps won't restore, games for example seem to.
But if you install the app from the play store it does allow you to restore app data
dladz said:
@glhelinski
What I found with titanium is that certain apps won't restore, games for example seem to.
But if you install the app from the play store it does allow you to restore app data
Click to expand...
Click to collapse
I could never nail down which apps wouldn't restore... Some would some wouldn't. I have never tried just restoring data (and not the app). Thanks
glhelinski said:
I could never nail down which apps wouldn't restore... Some would some wouldn't. I have never tried just restoring data (and not the app). Thanks
Click to expand...
Click to collapse
Tbh I'd like to know why too, I think it's down to security on Google play, perhaps it needs to check in or something within the app itself has to hit Google play to install, probably a DRM feature.
Anything installed from the internet will restore, WhatsApp and telegram restore.
All emulators fail, games in general fail.
I'm surprised that the developers of titanium haven't kept on top of that.
dladz said:
Tbh I'd like to know why too, I think it's down to security on Google play, perhaps it needs to check in or something within the app itself has to hit Google play to install, probably a DRM feature.
Anything installed from the internet will restore, WhatsApp and telegram restore.
All emulators fail, games in general fail.
I'm surprised that the developers of titanium haven't kept on top of that.
Click to expand...
Click to collapse
Titanium backup does not work for split apks, it could be because of that, or simply due the fact that's it's just outdated.
Swift backup on the other hand handles everything fine. There is also a free open source alternative called OAndBackupX which I've heard works great as well.
Full nandroid backup should *hopefully* be possible soon though, mauronofrio is currently working on updating TWRP to 3.5.
Lossyx said:
Full nandroid backup should be possible soon though, mauronofrio is currently working on updating TWRP to 3.5.
Click to expand...
Click to collapse
Many would love this
glhelinski said:
Many would love this
Click to expand...
Click to collapse
Totally agree dude, it's a ballache wiping your whole phone every time you want to change OS
Only reason I keep TiB is because I freeze some apps. Like when I install goog's camera and messaging ( and their phone . . . maybe too ) and don't want to see oneplus stuff. So, does 'swift' bu do the freezing thing too ?
I suppose the guru members know how to freeze with adb and maybe can share their knowledge . . .
old_fart said:
Only reason I keep TiB is because I freeze some apps. Like when I install goog's camera and messaging ( and their phone . . . maybe too ) and don't want to see oneplus stuff. So, does 'swift' bu do the freezing thing too ?
I suppose the guru members know how to freeze with adb and maybe can share their knowledge . . .
Click to expand...
Click to collapse
Never really looked into the freeze method visa adb, I would imagine it has a different term. After all it essentially disables apps instead of uninstalling them.
Swift does things on a different level to tib, so it can back up contacts, messages and call logs grouped or individually.
I haven't explored it enough buy it looks good and the apps seem to restore just fine.
You could adb uninstall the apps that you don't want. There's also another university called rabbit that can relive system apps where tib fails to find the APK. I think this is due to data/app being restricted by Google for certain apps
old_fart said:
Only reason I keep TiB is because I freeze some apps. Like when I install goog's camera and messaging ( and their phone . . . maybe too ) and don't want to see oneplus stuff. So, does 'swift' bu do the freezing thing too ?
I suppose the guru members know how to freeze with adb and maybe can share their knowledge . . .
Click to expand...
Click to collapse
SD Maid will freeze apps.