Related
Hey guys,
I tried using Rom Toolbox Pro to change my battery icon... after trying to install, the error "com.android.systemui has stopped working" continually popped up. I had to reboot by holding vol+, vol- and lock.
After rebooting, all soft buttons and the status bar are gone. I can't manage to get them back. I also can't manage to restore the battery icon - RTP prompted me to backup the icons before trying to install the new ones, and I did.
What have I done?
You've borked the system UI. Need to flash a new ROM or flash a factory image, I think.
Sent from my Nexus 7 using xda app-developers app
duloz said:
You've borked the system UI. Need to flash a new ROM or flash a factory image, I think.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Wow, that's so bull**** haha. Thanks for the quick reply
bulldozed said:
Wow, that's so bull**** haha. Thanks for the quick reply
Click to expand...
Click to collapse
So I went to restore my backup through CMW, it failed. Now I'm stuck on the Google screen. How do I flash it back to stock, in order to start all over again? I can get to the CMW page with the Android on his back, with "Start" up the top.
Appreciate any help!
bulldozed said:
So I went to restore my backup through CMW, it failed. Now I'm stuck on the Google screen. How do I flash it back to stock, in order to start all over again? I can get to the CMW page with the Android on his back, with "Start" up the top.
Appreciate any help!
Click to expand...
Click to collapse
That's not the clock work recovery. It's the bootloader. That's where you need to be to flash the image though.
First download the Nexus 7 image from https://developers.google.com/android/nexus/images#nakasijro03d
Once you have downloaded it extract the file twice until you see image-nakasi-jro03d.zip
Take that zip and move it to the directory where you have fastboot on your computer.
Open your command prompt pointing at that directory.
Then, type:
Code:
fastboot devices
if it returns a number you are good to go.
Next type:
Code:
fastboot -w update image-nakasi-jro03d.zip
This will wipe your user data and restore stock recovery. But you should be good to go.
geez, just reflash your rom, youll be ok.
El Daddy said:
snip
Click to expand...
Click to collapse
absolute legend. Thanks for the detailed reply, really appreciate it! I will give that a shot right now.
EDIT: haha took me five minutes to get it reflashed to stock. thanks again!
simms22 said:
geez, just reflash your rom, youll be ok.
Click to expand...
Click to collapse
haha sorry if my posts were a bit over the top, I was just sitting in bed having a play (with my Nexus 7........), then all of a sudden my tablet is seemingly wrecked simply from trying to change the battery icon... I FREAKED
Did something similar myself.
Just downloaded the factory image and flashed just the system.img file using fastboot and rerooted. A few system apps played up, most were fixed by wiping the cache but i had to delete all data from the contacts app, it resynced fine anyway.
To clarify extract the factory image to get the system.img and use the following
fastboot flash system system.img
Just rewrites the system partition.
Sent from my Nexus 7 using Tapatalk 2
The same thing happened to me trying to change the wifi icon. I guess Rom Toolbox doesn't play well with the Nexus 7?
Same thing on Galaxy Nexus... stumbled upon this thread searching for a solution. Was thinking we could restore from the backup that was made when swapping icons, but I guess that's not the case?
bulldozed said:
Hey guys,
I tried using Rom Toolbox Pro to change my battery icon... after trying to install, the error "com.android.systemui has stopped working" continually popped up. I had to reboot by holding vol+, vol- and lock.
After rebooting, all soft buttons and the status bar are gone. I can't manage to get them back. I also can't manage to restore the battery icon - RTP prompted me to backup the icons before trying to install the new ones, and I did.
What have I done?
Click to expand...
Click to collapse
Hello friends,
I am curious why, when such issues occured with your device, you did not contact Rom Toolbox Dev. to ask for help?
I am part of the support team from Rom Toolbox Pro, and I believe the post right before me is from someone who reached out to me to ask me about this, so allow me to explain the solution here real fast:
What happened is that when you changed the icon, it simply didn't work and messed up the UI. This occurs sometimes, and is the right time to restore a backup of the icons.
Problem is that now you can't restore, because the soft keys are all gone, and the Nexus 7 has no hard keys to do the dirty work.
So, here is the solution; you must use Root Browser to switch out the Systemui.apk and framework.apk files from the backup folder to the /system/app folder.
Where is the backup stored, you ask? Well, since it's very easy to break a rom by restoring the framework and systemui to the wrong rom, the backups are actually placed inside the app's data partition. This is to prevent tampering. If you are reading this post, then I assume you know what you're doing and are doing this with the EXACT same rom as the backups were created from.
The directory of the backups is /data/data/com.jrummy.liberty.toolboxpro/files/status_bar_backup/
Simply copy these over and paste them in /system/app, maybe renaming rather than deleting the old ones, just in case, then paste these and reboot your device.
And now your systemui and framework should be all restored.
Hope this helps! Be sure to contact the developer next time you need any help, We have arguably the best customer service of all the Play Store
And be sure to thank the one who referred me to this thread, if this helps!
Master Ramy said:
Hello friends,
I am curious why, when such issues occured with your device, you did not contact Rom Toolbox Dev. to ask for help?
I am part of the support team from Rom Toolbox Pro, and I believe the post right before me is from someone who reached out to me to ask me about this, so allow me to explain the solution here real fast:
What happened is that when you changed the icon, it simply didn't work and messed up the UI. This occurs sometimes, and is the right time to restore a backup of the icons.
Problem is that now you can't restore, because the soft keys are all gone, and the Nexus 7 has no hard keys to do the dirty work.
So, here is the solution; you must use Root Browser to switch out the Systemui.apk and framework.apk files from the backup folder to the /system/app folder.
Where is the backup stored, you ask? Well, since it's very easy to break a rom by restoring the framework and systemui to the wrong rom, the backups are actually placed inside the app's data partition. This is to prevent tampering. If you are reading this post, then I assume you know what you're doing and are doing this with the EXACT same rom as the backups were created from.
The directory of the backups is /data/data/com.jrummy.liberty.toolboxpro/files/status_bar_backup/
Simply copy these over and paste them in /system/app, maybe renaming rather than deleting the old ones, just in case, then paste these and reboot your device.
And now your systemui and framework should be all restored.
Hope this helps! Be sure to contact the developer next time you need any help, We have arguably the best customer service of all the Play Store
And be sure to thank the one who referred me to this thread, if this helps!
Click to expand...
Click to collapse
Hi Master Ramy,
I was the one who emailed JRummy.
I'm not sure I understand what you're saying actually. I guess your reply answers the OP's question - that is, in the event that we get the "com.android.systemui has stopped working" error , then we should do the stuff you said?
My issue is different... I hadn't swapped out my battery icons yet, cos I wanted to test the restore function in ROM Toolbox first before doing so. So I backed up both systemui and framework-res using ROM Toolbox, then simply tried to restore them using ROM Toolbox. But I got a toast notification saying "failed to get icons". I didn't get a big error like the OP's, but it was alarming enough that I didn't even try to change the icons in the end.
Are you saying that I should manually move my systemui and framework-res backups to system/app in order for ROM Toolbox to be able to restore them?
mlj11 said:
Hi Master Ramy,
I was the one who emailed JRummy.
I'm not sure I understand what you're saying actually. I guess your reply answers the OP's question - that is, in the event that we get the "com.android.systemui has stopped working" error , then we should do the stuff you said?
My issue is different... I hadn't swapped out my battery icons yet, cos I wanted to test the restore function in ROM Toolbox first before doing so. So I backed up both systemui and framework-res using ROM Toolbox, then simply tried to restore them using ROM Toolbox. But I got a toast notification saying "failed to get icons". I didn't get a big error like the OP's, but it was alarming enough that I didn't even try to change the icons in the end.
Are you saying that I should manually move my systemui and framework-res backups to system/app in order for ROM Toolbox to be able to restore them?
Click to expand...
Click to collapse
Yes, the post was in response to the OP talking about losing the soft keys and such Due to the different nature of your issue, I've sent you an email instead of responding here, so that we don't clog up this thread
So I saw the articles and threads on 12/25 reporting do not Disturb until next alarm was gone. After noting mine was gone too I turned off my 6P and went back to using my Galaxy S6 for 2 days.
I turned my 6P back on to get a file off it last night and noticed do not disturb symbol was on the top status bar. I pulled the toggles down saw it was lit with 'alarms only' under it. I clicked the toggle and it does not turn off. I tried double clicking and tried holding down toggle. I Pressed the volume up button and I can change volume for alarms and media, but ring tone slider is faded out so I can't modify it.
Then I went into settings and confirmed in the notifications section that there is no do not disturb schedule turned on and no apps have access to do not disturb. I also could not turn it off from inside settings either. I did a quick Google search and found a thread on 12/23 and 12/14 of this being reported on Android Central. Before this until next alarm disappeared. Every thread has no resolution if there was one.
I tried clearing all user cache and rebooting but it's still turned on. I also booted into twrp and wiped cache in there. It still shows! So it seems to be something in the system. I am rooted (systemless) but completely stock 6.0.1. I's anyone else experiencing this or have any suggestions?
Try reflashing /system only? Or flash the factory image but remove the -w from near the end of the batch file to preserve your userdata. Then just flash TWRP and systemless root again, after verifying it's fixed, of course.
fury683 said:
Try reflashing /system only? Or flash the factory image but remove the -w from near the end of the batch file to preserve your userdata. Then just flash TWRP and systemless root again, after verifying it's fixed, of course.
Click to expand...
Click to collapse
Too bad I didn't do a nandroid backup till last night after this happened. So I was fearing what you said might be the only solution, to just flash back to stock image and root again. Any other suggestions to avoid that?
AndroidPurity said:
Too bad I didn't do a nandroid backup till last night after this happened. So I was fearing what you said might be the only solution, to just flash back to stock image and root again. Any other suggestions to avoid that?
Click to expand...
Click to collapse
If you don't wipe userdata (remove the -w flag as I described) you won't need a nandroid. All your apps will remain intact, if you remove the -w.
Download the factory image, unpack it, edit the flash-all.bat to REMOVE the -w from the file (it's near the end), save the batch file. Put your phone in bootloader mode, run the factory image as you would normally. When complete, you'll be on a fresh install with all your data. This of course assumes the issue is /system related not /data related.
You could still take a nandroid in hopes that you could flash fully clean (without modifying the batch file) and then restore /data only from the nandroid. You'd need to offload that backup somewhere though because it would get wiped with the factory image.
Also I forgot to mention if you are going to use a nandroid, make sure you remove any pin/password/lock before you make it. I believe if you leave it on there and restore it, it won't accept the pin/password/fingerprint.
fury683 said:
Also I forgot to mention if you are going to use a nandroid, make sure you remove any pin/password/lock before you make it. I believe if you leave it on there and restore it, it won't accept the pin/password/fingerprint.
Click to expand...
Click to collapse
The work around for a nandroid with lock screen security is to delete the file locksettings.db from data/system. Use the file manager in twrp to erase it. Then once booted go to lockscreen security and toggle between swipe and fingerprint. It will erase the saved ones and let you start over.
XxMORPHEOUSxX said:
The work around for a nandroid with lock screen security is to delete the file locksettings.db from data/system. Use the file manager in twrp to erase it. Then once booted go to lockscreen security and toggle between swipe and fingerprint. It will erase the saved ones and let you start over.
Click to expand...
Click to collapse
Thanks, I was not aware. I thought it was just FUBAR if you didn't remove it before making the backup.
fury683 said:
Also I forgot to mention if you are going to use a nandroid, make sure you remove any pin/password/lock before you make it. I believe if you leave it on there and restore it, it won't accept the pin/password/fingerprint.
Click to expand...
Click to collapse
Haha good thing I didn't attempt yet! Lol! Thanks for coming back with the warning. I'll try everything later tonight or tomorrow. I'll follow up with the results or if I come across any issues.
XxMORPHEOUSxX said:
The work around for a nandroid with lock screen security is to delete the file locksettings.db from data/system. Use the file manager in twrp to erase it. Then once booted go to lockscreen security and toggle between swipe and fingerprint. It will erase the saved ones and let you start over.
Click to expand...
Click to collapse
Thanks! So just to clarify these are the options for nandroid security lock work around..
1.) Set lock security to nothing (just swipe), then do the nandroid backup
2.) Leaving pin/finger print security setting - delete the locksettings.db file using twrp. But is deleting it done before or after making the nandroid backup? Or after flashing the nandroid backup right before rebooting? Thanks!
AndroidPurity said:
Haha good thing I didn't attempt yet! Lol! Thanks for coming back with the warning. I'll try everything later tonight or tomorrow. I'll follow up with the results or if I come across any issues.
Thanks! So just to clarify these are the options for nandroid security lock work around..
1.) Set lock security to nothing (just swipe), then do the nandroid backup
2.) Leaving pin/finger print security setting - delete the locksettings.db file using twrp. But is deleting it done before or after making the nandroid backup? Or after flashing the nandroid backup right before rebooting? Thanks!
Click to expand...
Click to collapse
I believe @XxMORPHEOUSxX was just saying that if you were to make a nandroid and did not remove your PIN/password first, you can still use it by using his steps mentioned. If you remove it BEFORE the nandroid, you should be able to just restore it without issue. I haven't personally done either of those things, so you may want to wait until someone who has done it chime in, but that was my understanding.
fury683 said:
I believe @XxMORPHEOUSxX was just saying that if you were to make a nandroid and did not remove your PIN/password first, you can still use it by using his steps mentioned. If you remove it BEFORE the nandroid, you should be able to just restore it without issue. I haven't personally done either of those things, so you may want to wait until someone who has done it chime in, but that was my understanding.
Click to expand...
Click to collapse
Yes exactly. If you already made a nandroid and forgot, restore it and then erase that file. I've done it and it works.
fury683 said:
If you don't wipe userdata (remove the -w flag as I described) you won't need a nandroid. All your apps will remain intact, if you remove the -w.
Download the factory image, unpack it, edit the flash-all.bat to REMOVE the -w from the file (it's near the end), save the batch file. Put your phone in bootloader mode, run the factory image as you would normally. When complete, you'll be on a fresh install with all your data. This of course assumes the issue is /system related not /data related.
You could still take a nandroid in hopes that you could flash fully clean (without modifying the batch file) and then restore /data only from the nandroid. You'd need to offload that backup somewhere though because it would get wiped with the factory image.
Click to expand...
Click to collapse
So I downloaded the MMB29M factory image, and ran the flash-all.bat. Unfortunately I forgot to remove the -w. No biggie though I had no important pictures or documents that needed backed up. Just will have to sign into all my apps all over again. Anyways it did resolve the DND being stuck on, I figured it would since it went completely back to stock including user data.
However I am still baffled at how that could have happened when it was fine after the systemless root and never played around with the root files afterwards. No exposed modules or anything. Anyways I am about to flash twrp and install the new 2.65 SuperSU to root again. So I guess only time will tell if it happens again. Thanks for the help gentlemen!
Same problem but im on a stock phone. Not even rooted
Hi guys.
i'm new here and greatly appreciate the knowledge here. I recently installed purenexus on my 6p. first time installing a custom rom. worked beautifully until i decided to try out the lockscreen scramble pin feature. Now when I try to unlock my phone it doesn't recognize my PIN. i've tried many times and something undoubtedly went wrong. is this a known issue with scrambling your pin?
So what should i do? A quick google search suggested I restore a backup. Is this the recommended method? I did a factory back up, i think. i did the back up after the factory reset but before flashing purenexus. i used the default twrp back up settings, which i believe did not include the vendor file.
i'm a complete novice when it comes to this sort of thing so if someone can give me a step-by-step explanation for me to unscrew myself here i'd greatly appreciate it.
thanks.
ent3rpryze said:
Hi guys.
i'm new here and greatly appreciate the knowledge here. I recently installed purenexus on my 6p. first time installing a custom rom. worked beautifully until i decided to try out the lockscreen scramble pin feature. Now when I try to unlock my phone it doesn't recognize my PIN. i've tried many times and something undoubtedly went wrong. is this a known issue with scrambling your pin?
So what should i do? A quick google search suggested I restore a backup. Is this the recommended method? I did a factory back up, i think. i did the back up after the factory reset but before flashing purenexus. i used the default twrp back up settings, which i believe did not include the vendor file.
i'm a complete novice when it comes to this sort of thing so if someone can give me a step-by-step explanation for me to unscrew myself here i'd greatly appreciate it.
thanks.
Click to expand...
Click to collapse
Are you sure you're hitting the right numbers? They'll be in a different position every time.
Heisenberg said:
Are you sure you're hitting the right numbers? They'll be in a different position every time.
Click to expand...
Click to collapse
I am. 100% certain.
it really seems as if my password was for some reason changed. before someone asks i am definitely using the correct pin. its the same PIN i've been using for years.
how do i regain control of my phone?
ent3rpryze said:
I am. 100% certain.
it really seems as if my password was for some reason changed. before someone asks i am definitely using the correct pin. its the same PIN i've been using for years.
how do i regain control of my phone?
Click to expand...
Click to collapse
i rebooted to recovery mode and i discovered that i moved my backup to my laptop. so now backup file is available.
can i just wipe my phone and reinstall the purenexus rom which is still on my phone
ent3rpryze said:
i rebooted to recovery mode and i discovered that i moved my backup to my laptop. so now backup file is available.
can i just wipe my phone and reinstall the purenexus rom which is still on my phone
Click to expand...
Click to collapse
Yes, if you clean flash the ROM you'll be able to get back into it. Had you restored a nandroid backup recently by any chance?
Heisenberg said:
Yes, if you clean flash the ROM you'll be able to get back into it. Had you restored a nandroid backup recently by any chance?
Click to expand...
Click to collapse
thanks a lot for clarifying that. i guess i have no other option.
has this been known to happen? scrambling PIN causing the pin to change.
I dont have a recent nandroid backup because my purenexus flash is only days old. is there a way to automate nandroid backups? is it wiser to keep the backups on the phone?
ent3rpryze said:
thanks a lot for clarifying that. i guess i have no other option.
has this been known to happen? scrambling PIN causing the pin to change.
I dont have a recent nandroid backup because my purenexus flash is only days old. is there a way to automate nandroid backups? is it wiser to keep the backups on the phone?
Click to expand...
Click to collapse
I've never seen this happen before. I'm pretty sure you can use Tasker to automate backups. I usually advise people to keep at least one backup or ROM zip on their phone, just in case.
IT HAPPENED AGAIN!
Per the ever hepful Heisenberg's recommendation, I wiped my phone and reflashed purenexus. This was yesterday. Everything went smoothly. Recreated my security PIN. Was able to unlock my phone with it without incident...until just now. Incorrect PIN error 3 times.
What is going on?!?!
It should be noted that both times this has happened has come after I turned my phone off. This time I happened to be charging my phone while it was off. I can't recall if it was the same case the first time it happened. Is this a purenexus issue?
found the solution.
"Delete this file /data/system/locksettings.db from TWRP."
I wish I had known this the first time it happened. Oh well. I sure hope this helps someone else in the future.
ent3rpryze said:
found the solution.
"Delete this file /data/system/locksettings.db from TWRP."
I wish I had known this the first time it happened. Oh well. I sure hope this helps someone else in the future.
Click to expand...
Click to collapse
This is usually over necessary after a user has created (and later restored) a nandroid backup without removing lockscreen security first. Are you saying you hadn't done this at all prior to the problem occurring?
Heisenberg said:
This is usually over necessary after a user has created (and later restored) a nandroid backup without removing lockscreen security first. Are you saying you hadn't done this at all prior to the problem occurring?
Click to expand...
Click to collapse
i dont know what qualifies as a nandroid backup. the only backup i created was with the TWRP backup function which i later moved to my laptop, as previously mentioned. and yes, i did that before the problem occured. it was before I had even installed pure nexus.
btw, it happened AGAIN (#3 for those keeping score). i'm going to assume there's a bug in the rom and forego the use of a security pin. also, for the first time, when i went back into twrp to once again delete the locksettings.db file i was prompted to enter a password before i could modify the system. Odd.
ent3rpryze said:
i dont know what qualifies as a nandroid backup. the only backup i created was with the TWRP backup function which i later moved to my laptop, as previously mentioned. and yes, i did that before the problem occured. it was before I had even installed pure nexus.
btw, it happened AGAIN (#3 for those keeping score). i'm going to assume there's a bug in the rom and forego the use of a security pin. also, for the first time, when i went back into twrp to once again delete the locksettings.db file i was prompted to enter a password before i could modify the system. Odd.
Click to expand...
Click to collapse
When making a nandroid (backup) in TWRP remove any pin, patter or fingerprints before backup or getting locked out will continue.
elevatorguy said:
When making a nandroid (backup) in TWRP remove any pin, patter or fingerprints before backup or getting locked out will continue.
Click to expand...
Click to collapse
thanks for that, but i believe i did that because i backuped a clean factory 6.0.1, sans any security setup. not sure if that was necessary but that's what i did.
ent3rpryze said:
i dont know what qualifies as a nandroid backup. the only backup i created was with the TWRP backup function which i later moved to my laptop, as previously mentioned. and yes, i did that before the problem occured. it was before I had even installed pure nexus.
btw, it happened AGAIN (#3 for those keeping score). i'm going to assume there's a bug in the rom and forego the use of a security pin. also, for the first time, when i went back into twrp to once again delete the locksettings.db file i was prompted to enter a password before i could modify the system. Odd.
Click to expand...
Click to collapse
The problem isn't with the ROM, I (along with what I'm guessing is pretty much every other user) use fingerprint and/or PIN/pattern security on Pure Nexus with no issues. A nandroid backup is one of those backups you create with TWRP, so yes it's what you described. But this problem shouldn't be occurring on a clean flash of Pure Nexus, can you please explain in detailed steps how you installed the ROM?
ent3rpryze said:
Hi guys.
i'm new here and greatly appreciate the knowledge here. I recently installed purenexus on my 6p. first time installing a custom rom. worked beautifully until i decided to try out the lockscreen scramble pin feature. Now when I try to unlock my phone it doesn't recognize my PIN. i've tried many times and something undoubtedly went wrong. is this a known issue with scrambling your pin?
So what should i do? A quick google search suggested I restore a backup. Is this the recommended method? I did a factory back up, i think. i did the back up after the factory reset but before flashing purenexus. i used the default twrp back up settings, which i believe did not include the vendor file.
i'm a complete novice when it comes to this sort of thing so if someone can give me a step-by-step explanation for me to unscrew myself here i'd greatly appreciate it.
thanks.
Click to expand...
Click to collapse
On Marshmallow, the scramble pin option is bugged if you use a long pin. Some rom devs choose to leave this out entirely. I haven't played with it to determine the cut off point but 4 digits is fine. I think I tried 8 digits once and it locked me out.
Sent from my Nexus 5X using Tapatalk
ent3rpryze said:
found the solution.
"Delete this file /data/system/locksettings.db from TWRP."
I wish I had known this the first time it happened. Oh well. I sure hope this helps someone else in the future.
Click to expand...
Click to collapse
Awesome.. Thanks a bunch for posting this... I am using Oneplus 3T , Resurrection Remix 5.7.4 ( Marshmallow) . Had turned on Scrambled PIN.. Ran into same issue as yours.. Last option left for me was to do factory reset from TWRP but I was scared to lose Google Authenticator Setup on my phone and many other things... Your solution saved me!! :good::good:
I also had a similar problem:
- freshly installed Carbon ROM with TWRP
- added lockscreen password in phone
- locked screen
- tried accessing using password
The password just fails. Using a shorter password works normally. The failing password is 13 characters long.
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
I am stuck on the 'Phone is starting...' screen. This is how I landed here
1. Added Finger Print Customizations when the phone was working and they did work as expected.
2. Noticed update from 9.0.10 to 9.0.10
3. Flashed stock 9.0.10 image over Bluespark and Magisk rooted image
4. Flashing stock 9.0.10 caused getting stuck in the 'Phone is starting...' screen
5. I can hear my phone ringing on this screen, but I cannot answer any calls since the phone is stuck forever on this screen
6. I tried flashing bluespark and magisk in the hopes of being able to boot, but that just cases my old boot screen to show up and then going back to restarting in a loop again
I believe OPSystemUI.apk (file that I replaced under /system/priv-app for getting custom finger print animation) is causing the issue. I do not know how to restore the stock version of this file without wiping all my data clean. I am not sure if this is the file causing the issue. Is there any way to get the phone started by flashing some files via adb?
Appreciate the inputs in advance.
pramathesh said:
I am stuck on the 'Phone is starting...' screen. This is how I landed here
1. Added Finger Print Customizations when the phone was working and they did work as expected.
2. Noticed update from 9.0.10 to 9.0.10
3. Flashed stock 9.0.10 image over Bluespark and Magisk rooted image
4. Flashing stock 9.0.10 caused getting stuck in the 'Phone is starting...' screen
5. I can hear my phone ringing on this screen, but I cannot answer any calls since the phone is stuck forever on this screen
6. I tried flashing bluespark and magisk in the hopes of being able to boot, but that just cases my old boot screen to show up and then going back to restarting in a loop again
I believe OPSystemUI.apk (file that I replaced under /system/priv-app for getting custom finger print animation) is causing the issue. I do not know how to restore the stock version of this file without wiping all my data clean. I am not sure if this is the file causing the issue. Is there any way to get the phone started by flashing some files via adb?
Appreciate the inputs in advance.
Click to expand...
Click to collapse
You don't have launcher installed.
Just sideload any launcher apk using advanced and you should be good..
indian84 said:
You don't have launcher installed.
Just sideload any launcher aok using advanced and you should be good..
Click to expand...
Click to collapse
Are you sure? Before messing it up with stock boot image I had nova running for me and had also kept one plus stock installed. Not sure how I can side load a launcher. Any pointers to that, please?
pramathesh said:
Are you sure? Before messing it up with stock boot image I had nova running for me and had also kept one plus stock installed. Not sure how I can side load a launcher. Any pointers to that, please?
Click to expand...
Click to collapse
Not 100% sure it'll help.
But won't hurt to try..
indian84 said:
Not 100% sure it'll help.
But won't hurt to try..
Click to expand...
Click to collapse
True. Any idea on how to side load an apk? I usually side load zip. Apk is new to me.
pramathesh said:
True. Any idea on how to side load an apk? I usually side load zip. Apk is new to me.
Click to expand...
Click to collapse
Well, I shared a screenshot with you.
It's similar to sideloading a zip..
indian84 said:
Well, I shared a screenshot with you.
It's similar to sideloading a zip..
Click to expand...
Click to collapse
I am unable to open the image you have attached
pramathesh said:
I am unable to open the image you have attached
Click to expand...
Click to collapse
Google would help.
Too lazy to type..
Lol
pramathesh said:
True. Any idea on how to side load an apk? I usually side load zip. Apk is new to me.
Click to expand...
Click to collapse
Adb install name.apk
Where name.apk is the app you're installing
indian84 said:
Not 100% sure it'll help.
But won't hurt to try..
Click to expand...
Click to collapse
I am getting this while trying to sideload apk
C:\Program Files (x86)\Minimal ADB and Fastboot>adb install launcher.apk
adb: connect error for write: closed
If you use bluespark TWRP then you're several weeks late, use officially working TWRP check in ROM section
Sideload the whole ROM to go back to normal, with temporary boot TWRP in fastboot mode
Striatum_bdr said:
If you use bluespark TWRP then you're several weeks late, use officially working TWRP check in ROM section
Sideload the whole ROM to go back to normal, with temporary boot TWRP in fastboot mode
Click to expand...
Click to collapse
I have the 9.0.10 downloaded from here:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
I unzipped them found a .bin file. Is there any guide on extracting the binary files and flashing the entire rom via ADB?
pramathesh said:
I have the 9.0.10 downloaded from here:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
I unzipped them found a .bin file. Is there any guide on extracting the binary files and flashing the entire rom via ADB?
Click to expand...
Click to collapse
Use fastboot ROM in that case. See relevant threads
Striatum_bdr said:
Use fastboot ROM in that case. See relevant threads
Click to expand...
Click to collapse
Let me check, is it okay to PM you?
pramathesh said:
Let me check, is it okay to PM you?
Click to expand...
Click to collapse
No, I've never had to use that, and all is explained clearly in the threads giving fastboot ROM
Ultimate tool is msmdownload, there are dedicated threads also
Striatum_bdr said:
No, I've never had to use that, and all is explained clearly in the threads giving fastboot ROM
Ultimate tool is msmdownload, there are dedicated threads also
Click to expand...
Click to collapse
Sorry for being so naive but I couldn't find any ROM that would have fastboot support. There is very less stuff for 6T to comb from.
pramathesh said:
Sorry for being so naive but I couldn't find any ROM that would have fastboot support. There is very less stuff for 6T to comb from.
Click to expand...
Click to collapse
Not very hard to find
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Striatum_bdr said:
Not very hard to find
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
Silly me, I was looking in the ROM section. I will use this and update the thread again
Hey! It worked. The phone is up and running now. Only thing is I lost all the data on the phone
Solution
Next time you face this issue in any ROM, you can do the following to come out of it. However, you would need to have a customised notification panel, which will allow you to go to settings and security option. Also, ensure you do not have a default launcher, if you have more than 1 launcher in your phone that you use.
Just long press any icon which leads to settings, or click on the settings icon from the notification bar.
It will open a blank settings page. Do a scroll up and down, and it will refresh.
Then go to security and privacy and delete the fingerprints.
You may also need to delete the security pin or swipe or the lock screen settings.
NOTE: Do not delete the locksettings.db from Recovery mode. It will break everything and the above steps might not help.
BTW, I am facing this issue for the last 3 days. Have been doing clean flash everytime. I was searching this issue on internet, but yours came up just now, and I read, FingerPrint, and it stuck me. Now it worked. Rebooting now. But posting the comment here in case I face any issues. Want to help you, as I know what the feeling is like. Frustrated and tired, wanting to kill someone.
Edit: Rebooted without any lock pin or FP. Shows phoe is starting, and starts in 2 seconds and allows access.
Will set a pin and check now.
Then will set one FP and check.
Edit2: Set pin lock and rebooted. Works okay..