Alright, this is a weird one! Only of few instances of the mystical "pixel is starting..." screen show up online and I'm mostly out of ideas at this point.
First, some background:
I was still on the December 5th update (QQ1A.191205.008). Stock, unlocked, rooted with Magisk. I hadn't yet flashed the patched Magisk boot image, it was running only by fastboot boot pachted.img. The only root-related App I had installed was Battery Charge Limiter.
What happened:
I created a custom theme & changed my wallpaper. I then used Activity Launcher to launch the "hidden" System UI Tuner. While in there I disabled the clock in the system tray. I also went into the "Plugins" menu and toggled the "enable" toggle on, then off (I thought more plugin options, whatever they may be, were hidden since they were not enabled...). I fiddled with a few more settings hiding/showing icons and hit the home button.
When I returned back to the homescreen, my wallpaper had changed back to the default Pink/purple Pixel 3 wallpaper. "Huh? System UI Tuner must have reset this." I changed the wallpaper again but it didn't even change. After a few more attempts (tried changing just lockscreen wallpaper, just homescreen, both; nothing would actually change), I rebooted the phone.
Upon booting back up, I was greeted with a "Pixel is starting..." screen that won't go away. This occurs before the lock screen, prior to letting me enter my PIN.
Attempted recovery steps already taken
Rebooted many times. (Which which would have booted the factory boot.img; see above background)
Tried booting into "safe mode." (Same "Pixel is starting..." screen comes up with the words "Safe mode" in the bottom left)
sideloaded the most recent OTA for my device (QQ1A.200105.002)
Booted corresponding Magisk patched boot.img
Has this happened to anyone before? Can anyone think of a way recover anything at this point? Luckily I had adb enabled before this happened and it still functions; logcat doesn't show anything that seems helpful, though. Since I cannot unlock the device, I can't use adb to recover any data. I really wish adb had a means of unlocking via PIN!
My next step is likely going to be to flash a factory image (probably QQ1A.191205.008 as that was what I was using prior to this happening) with "-w" removed and praying I can at least unlock the phone.
Data recovered!
Edit: Wow! I wasn't able to fix the "Pixel is starting..." issue, but I was able to use adb to recovery all my data. I will follow up with what I did shortly! Dodged a bullet... unbelievable!
I couldn't fix the "Pixel is starting..." issue. Factory Flashing (after removing -w) QQ1A.191205.008 resulted resulted in being stuck at the "G" screen. I flashed the QQ1A.200105.002 factory image (again with -w removed) and was left in the same "Pixel is starting..." state.
Here is where things get interesting:
Over adb I launched the Settings app:
Code:
adb shell am start -a android.settings.SETTINGS
Next, I went into "Security," which prompted for my PIN, and then removed the screen lock. After doing this, I was able to get into /sdcard in the ADB shell, something that was not possible before.
Back in the settings app, I enabled USB File Transfer and copied all my files & photos off. I was also able to launch apps from within the apps list in Settings. This let me export settings/data from other apps that allowed it. :good:
So it seems that entering your PIN in the Settings app also unlocks the phone!
Thanks for describing this and how you ended up resolving it. I am seeing the same "Pixel is starting". Flashing the (March 2020) factory image didn't fix mine either.
I was able to get into Settings by pulling down the notification shade while the "Pixel is starting" message shows. I removed my fingerprints and PIN.
I don't seem to be able to launch apps from within the apps list in Settings. Can you describe how you did that?
I've tried this:
Settings-->Apps & notifications-->App info--> {select any app and tried clicking on icon at top of screen} Nothing. Poked around a bit and tried various things but couldn't figure out how to launch an app from here. Thanks in advance.
docdl said:
I don't seem to be able to launch apps from within the apps list in Settings. Can you describe how you did that?
Click to expand...
Click to collapse
There should be a "Open" shortcut just below the app icon to the left of "Uninstall" (or "Disable" if it is a built-in app).
_Ra1n_ said:
Alright, this is a weird one! Only of few instances of the mystical "pixel is starting..." screen show up online and I'm mostly out of ideas at this point.
First, some background:
I was still on the December 5th update (QQ1A.191205.008). Stock, unlocked, rooted with Magisk. I hadn't yet flashed the patched Magisk boot image, it was running only by fastboot boot pachted.img. The only root-related App I had installed was Battery Charge Limiter.
What happened:
I created a custom theme & changed my wallpaper. I then used Activity Launcher to launch the "hidden" System UI Tuner. While in there I disabled the clock in the system tray. I also went into the "Plugins" menu and toggled the "enable" toggle on, then off (I thought more plugin options, whatever they may be, were hidden since they were not enabled...). I fiddled with a few more settings hiding/showing icons and hit the home button.
When I returned back to the homescreen, my wallpaper had changed back to the default Pink/purple Pixel 3 wallpaper. "Huh? System UI Tuner must have reset this." I changed the wallpaper again but it didn't even change. After a few more attempts (tried changing just lockscreen wallpaper, just homescreen, both; nothing would actually change), I rebooted the phone.
Upon booting back up, I was greeted with a "Pixel is starting..." screen that won't go away. This occurs before the lock screen, prior to letting me enter my PIN.
Attempted recovery steps already taken
Rebooted many times. (Which which would have booted the factory boot.img; see above background)
Tried booting into "safe mode." (Same "Pixel is starting..." screen comes up with the words "Safe mode" in the bottom left)
sideloaded the most recent OTA for my device (QQ1A.200105.002)
Booted corresponding Magisk patched boot.img
Has this happened to anyone before? Can anyone think of a way recover anything at this point? Luckily I had adb enabled before this happened and it still functions; logcat doesn't show anything that seems helpful, though. Since I cannot unlock the device, I can't use adb to recover any data. I really wish adb had a means of unlocking via PIN!
My next step is likely going to be to flash a factory image (probably QQ1A.191205.008 as that was what I was using prior to this happening) with "-w" removed and praying I can at least unlock the phone.
Data recovered!
Edit: Wow! I wasn't able to fix the "Pixel is starting..." issue, but I was able to use adb to recovery all my data. I will follow up with what I did shortly! Dodged a bullet... unbelievable!
Click to expand...
Click to collapse
Hey! I just ran into the same dilemma. I toggled the "plugins" setting in System UI tuner (by mistake), and my wallpaper went black. Then I decided to just reboot. I'm in the same "Pixel is starting" loop you described. I'm also stock, rooted with Magisk, on the January update. I just found that I can get into adb, but I'm a loss of what do to from here. I can't believe toggling a system UI tuner setting could cause a catastrophic crash. How did you end up solving this? Were you able to flash the full factory image while preserving your data? I honestly have no idea what do to at the moment. I'm gonna have to use an older device and research this more after work.
Edit: I was able to remove my security PIN via launching Settings through ADB, and therefore getting into some apps. I guess I'm more bothered by having to set up the device from scratch then I am losing any data. So time consuming. I'm assuming you ended up wiping the phone entirely and flashing a full factory image in the end? Geez. I miss my Moto devices and TWRP...
Ditamae said:
Hey! I just ran into the same dilemma. I toggled the "plugins" setting in System UI tuner (by mistake), and my wallpaper went black. Then I decided to just reboot. I'm in the same "Pixel is starting" loop you described.
Click to expand...
Click to collapse
Interesting! Exact same order of events.
Ditamae said:
Edit: I was able to remove my security PIN via launching Settings through ADB, and therefore getting into some apps. I guess I'm more bothered by having to set up the device from scratch then I am losing any data. So time consuming. I'm assuming you ended up wiping the phone entirely and flashing a full factory image in the end? Geez. I miss my Moto devices and TWRP...
Click to expand...
Click to collapse
Yes, I wiped completely. Used it as an excuse to flash LineageOS, something I had been planing on doing for a while anyway. I load very little on my devices to begin with so really its just typing in a few passwords.
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
If so, take a look at the files within; that should be where SystemUI Tuner saves the settings you have selected. Maybe rename the directory & reboot so the settings can't be loaded?
Edit: Don't try messing around with anything until you're sure you got all of the data off the device though!
_Ra1n_ said:
Interesting! Exact same order of events.
Yes, I wiped completely. Used it as an excuse to flash LineageOS, something I had been planing on doing for a while anyway. I load very little on my devices to begin with so really its just typing in a few passwords.
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
If so, take a look at the files within; that should be where SystemUI Tuner saves the settings you have selected. Maybe rename the directory & reboot so the settings can't be loaded?
Edit: Don't try messing around with anything until you're sure you got all of the data off the device though!
Click to expand...
Click to collapse
That's a great idea about renaming the directory. When I'm home from work I will try to figure out how to copy internal user data to my PC and then I'll look into that directory. Do you know how to enable file transfer via adb or thru the Settings app (launched via adb)?
I did utilize the system UI tuner to disable my alarm icon from showing in the status bar, so I'm hoping I can perhaps find the file associated with the plugin specifically and rename that. Hmm. Only this is systemless... Might not be possible. This is my first rooted device without full read/write capabilities. Not sure how I feel about systemless.
Otherwise, other than time, the only bummer to all this is that I think I'm going to lose the Magisk module YouTube Vanced, as it's not longer supported.
Anyway, thanks very much for your help so far.
Ditamae said:
That's a great idea about renaming the directory. When I'm home from work I will try to figure out how to copy internal user data to my PC and then I'll look into that directory. Do you know how to enable file transfer via adb or thru the Settings app (launched via adb)?
Click to expand...
Click to collapse
If your luck is as good as mine, you should be able to just plug in the device and enable file transfer (Settings > Connected Devices > USB > "Use USB For ... File Transfer."
Note that, as explained above, I had to remove my security PIN in settings before that worked, though.
_Ra1n_ said:
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
Click to expand...
Click to collapse
I was able to backup my data, and use Solid Explorer with root to search through system files. But, I don't see that directory. I see: data/data/com.android.systemui but no systemui.tuner. Any other idea where those systemui tuner files might be lurking? I'm an RN with a kindergartener home from school, and as much as I love tinkering with Android, now is not a good time.
_Ra1n_ said:
Interesting! Exact same order of events.
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
Click to expand...
Click to collapse
Just wondering if you have any other troubleshooting ideas before I install a full factory image...
My device boots now, partially. It seems that after I disabled lockscreen security, my phone boots, but without all gesture navigation, status bar, notification overlay. Essentially all SystemUI elements appear missing. The devices behaves as it did immediately after I accidentally toggled the UI tuner "plugins" setting, before I rebooted. It's unusable as a daily, but I did get my data. As I said previously, I could not find the directory: /data/data/com.android.systemui.tuner. Seems odd. I wonder where those setting preferences are hiding. Any help/ideas would be much appreciated.
Ditamae said:
Just wondering if you have any other troubleshooting ideas before I install a full factory image...
My device boots now, partially. It seems that after I disabled lockscreen security, my phone boots, but without all gesture navigation, status bar, notification overlay. Essentially all SystemUI elements appear missing. The devices behaves as it did immediately after I accidentally toggled the UI tuner "plugins" setting, before I rebooted. It's unusable as a daily, but I did get my data. As I said previously, I could not find the directory: /data/data/com.android.systemui.tuner. Seems odd. I wonder where those setting preferences are hiding. Any help/ideas would be much appreciated.
Click to expand...
Click to collapse
Sorry for the slow reply. Unfortunately I'm mostly out of ideas.
I'd ask in the general Android Help subforum: https://forum.xda-developers.com/android/help
You'll likely get more eyes on the question (where does SystemUI Tuner store it's settings & how to reset them) and hopefully someone with better knowledge on Android settings/preferences can provide some incite.
Homeboy76 said:
Guide
Do #4 'keep data', then #9 to root.
Make sure you have the latest SDK platform-tools, there is a link in the guide.
Click to expand...
Click to collapse
Flashing the factory image with -w removed to keep the data won't help. The issue is that SystemUI Tuner saved some setting (related to enabling the mysterious "Enable Plugins" option) that prevents the phone from completely booting up. A factory flash retaining data will retain the setting that SystemUI Tuner screwed up.
_Ra1n_ said:
Flashing the factory image with -w removed to keep the data won't help. The issue is that SystemUI Tuner saved some setting (related to enabling the mysterious "Enable Plugins" option) that prevents the phone from completely booting up. A factory flash retaining data will retain the setting that SystemUI Tuner screwed up.
Click to expand...
Click to collapse
@Ditamae Rain is correct. I have edited my post.
Related
This will officially not work for 1.1
What it does:
Enables ADB via uRamdisk
Installs su and Superuser.apk
Installs Busybox
Installs Button Savior
Installs Go Launcher
Installs NookColor Tools (To Enable Non-Market Installs)
Installs Gapps (Gmail, Market, Youtube, Others)
System Files that get Modified:
/system/build.prop - Enabling Google Check In
packages.xml - Allows Gapps to install properly.
framework.jar - Should allow a proper Android ID to generate.
Changes:
June 24, 2011 -
Removed: Multitouch Permission
Added: Modified framework.jar
June 22, 2011 - Fixed: Script not running at boot.
June 20, 2011 - Initial Release
Before you begin:
You must already have a registered Nook Simple Touch
You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
You must either have dd (Linux) or WinImage (Windows) software.
You must have an external microSDCard reader or this will not work. Do NOT use the Nook Simple Touch.
You must have enough intelligence to follow instructions.
Let's get started:
Download TouchNooter from here: touchnooter-1-6-24.zip
Linux: Unzip and use dd if=touchnooter-1-6-24.img of=/dev/sdcard
Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
Windows Alternative: https://launchpad.net/win32-image-writer/+download
Power off your Nook Simple Touch.
Insert TouchNooter SDcard into your Nook Simple Touch.
Power on your Nook Simple Touch.
You should see the screen "Rooted Forever".
It will boot like normal and you should be asked to select a launcher now. (If not use Button Savior to go home. This will bring up the launcher chooser.)
That was the hard part, now to the simple stuff.
Upon boot unlock your screen.
At the Android Welcome Screen skip Sign In.
Enable Location Services when given the option.
Connect to Wifi and launch Youtube from Go Launcher's App Drawer (Or the App Drawer of your Choice).
Click the Menu button (The right one in the middle of the status bar).
Select "My Channel" and Login using your Gmail Account.
Exit Youtube and Launch Gmail from "Extras".
Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
Enable Non-Market Installs by running the NookColor Tools App.
If your Youtube fails to launch Uninstall and Reinstall Youtube from /data/app
Go to Settings > Device Info > SdCard > UnMount > Format
Thanks To:
Arnold Snarb - modified framework.jar
nemith - helping me figure out getting it to run at boot.
JesusFreke - For getting root.
MrMuffin - For the original Market Hack that we're using.
Currently Working On: TouchNooter 1.11.x
I've probably screwed up, but perhaps not too badly. Tried to follow all the steps and got the system files copied to media, and then to replace the main system files, but there I got confused. I ended up rebooting without attempting to install the youtube app, which I didn't find in the download. Even now, a lot looks like it is working, but I can't even attempt to sign in to google cause I can't get a keyboard to come up to allow me to enter my user name and password. Is there any help for me, or am I a total dunce needing to start over? thanks!
EDIT: I see I am screwed -- no keyboard is coming up for me anywhere. I guess I can go through a major reset but if anyone has a suggestion to just get the keyboard back I will appreciate it.
EDIT2: Well I got past that, simply chose multitouch keyboard instead of Gingerbread in NookColor Tools.
EDIT3: But now I am stuck again as I can't sign in to a google account... says can't establish a reliable data connection to the server, even though my wifi is fine. But at least at the moment everything else is fine, though the keyboard isn't working very well (but it does work; lots of ghosting)
An .img file is being uploaded for TouchNooter 1.6.20 It'll do all the copy and edit stuff, the only thing it can't do is create an android ID.
In the "GappsAndMore" there was some keyboards which were from the NC it was just a raw pull from AN. This is more refined with things that could cause issues removed. (Like Keyboards, Framework.jars from the NC, etc.)
william1853 said:
I've probably screwed up, but perhaps not too badly. Tried to follow all the steps and got the system files copied to media, and then to replace the main system files, but there I got confused. I ended up rebooting without attempting to install the youtube app, which I didn't find in the download. Even now, a lot looks like it is working, but I can't even attempt to sign in to google cause I can't get a keyboard to come up to allow me to enter my user name and password. Is there any help for me, or am I a total dunce needing to start over? thanks!
EDIT: I see I am screwed -- no keyboard is coming up for me anywhere. I guess I can go through a major reset but if anyone has a suggestion to just get the keyboard back I will appreciate it.
EDIT2: Well I got past that, simply chose multitouch keyboard instead of Gingerbread in NookColor Tools.
EDIT3: But now I am stuck again as I can't sign in to a google account... says can't establish a reliable data connection to the server, even though my wifi is fine. But at least at the moment everything else is fine, though the keyboard isn't working very well (but it does work; lots of ghosting)
Click to expand...
Click to collapse
I'd suggest a wipe and running TouchNooter... GappsAndMore had Keyboards and stuff in it and removed the stock keyboard =\
is a wipe in the nook touch holding down the power for 20 seconds?
No you need to do a complete wipe by triggering recovery, but I don't know how to trigger recovery yet.
oh well the perils of early adoption. I'll follow the thread with anticipation!
william1853 said:
oh well the perils of early adoption. I'll follow the thread with anticipation!
Click to expand...
Click to collapse
You could try 8 failed boots. Basically you power it on and then power it off before it fully boots. Do that 8 times and it might trigger recovery.
Confirmed this works great. I'm going to find a fix for the calendar.
GabrialDestruir said:
You could try 8 failed boots. Basically you power it on and then power it off before it fully boots. Do that 8 times and it might trigger recovery.
Click to expand...
Click to collapse
Recovery is holding the power button for 20+ seconds it will trigger recovery
xboxexpert said:
Recovery is holding the power button for 20+ seconds it will trigger recovery
Click to expand...
Click to collapse
Really? Is that from when it's off?
GabrialDestruir said:
Really? Is that from when it's off?
Click to expand...
Click to collapse
Not sure I have yet to try it but someone in the other thread said he called BN and they told him that and he did it.
xboxexpert said:
Not sure I have yet to try it but someone in the other thread said he called BN and they told him that and he did it.
Click to expand...
Click to collapse
I tried it and all I could get was it turning on and off
TouchNooter 1.6.20
This doesn't seem to work for me at all... I tried restoring the backup image and starting from scratch and it still will not work. I tried enabling Google Apps manually and it won't work for me either.
I think I'm done, if the 7th time wasn't the charm then I'm giving up for now...
MystaWright said:
This doesn't seem to work for me at all... I tried restoring the backup image and starting from scratch and it still will not work. I tried enabling Google Apps manually and it won't work for me either.
I think I'm done, if the 7th time wasn't the charm then I'm giving up for now...
Click to expand...
Click to collapse
I ran this on my Nook Touch and it worked just fine. Are you getting the "Rooted Forever" boot screen?
GabrialDestruir said:
I tried it and all I could get was it turning on and off
Click to expand...
Click to collapse
Didn't work for me either. 8 interrupted boots did.
i'm getting the rooted forever screen and then it just goes to the default stock home
any thoughts?
GabrialDestruir said:
I ran this on my Nook Touch and it worked just fine. Are you getting the "Rooted Forever" boot screen?
Click to expand...
Click to collapse
Same problem here... tried to return EVERYTHING to stock too.
yugoliang said:
i'm getting the rooted forever screen and then it just goes to the default stock home
any thoughts?
Click to expand...
Click to collapse
I did a reset of the device back to the out of the box experience, registered with my BN account, shut down and followed the directions to the letter. I had no luck at all. It just shows the Rooted Forever screen, then boots normally is if nothing happened.
Sorry Guys and Gals. Entirely my fault. It seems a combination of my own forgetfulness and bad scripting (I forgot proper codes and methods used in AN) caused this just to do nothing. I'm uploading a version as I'm typing this and will remove "BROKEN" from the title when it's up.
Still broken. init.rc isn't running it's script properly.
Script can be ran manually with:
Code:
adb shell sh /sdcard/nooter/tmp/scripts/Nooter
Will be working on getting it to trigger properly
Re-written to be more concise and readable:
Long story short: I installed the program "Permissions Denied" from the market and restricted a few games. When I rebooted something was broken and I can't quite figure out what, but it runs deep through the phone.
The phone isn't bootlooping, but when I starts up it will very often become unresponsive immediately after getting to the lockscreen, my theory is that things are trying to load and crashing in the background. The only fix for this is to wait until it appear to reboot itself; the screen will come back on and show me a quick few cycles of the boot animation, then back to the lockscreen. After this, it asks to re-activate on the network. Whether or not everything works after this point has been highly variable. Currently, my phone is on but has no way of signing into a google account (isn't even an option in the list under settings).
If I try to restore a nandroid, at the very end it spits out "Error while restoring /data!". I've done this with a couple nandroids that I've used fine in the past. Fully wiping from CWM and installing a fresh rom yields similar results.
Basically my thinking at this point is to back up anything I want while I have access to the phone and try to do as full a factory reset as possible. Any ideas? Of note is that I've run the "fix permissions" function both in CWM and ROM Manager, and when I run it in ROM Manager the log shows permissions for a bunch of programs that have been wiped. So I'm guessing that permissions settings persist across wipes, but I don't know what to address that with specifically.
Bump? (rewrote OP to make it less of a train wreck of my late-night detective work)
Edit with maybe-progress: I found and installed an older apk for Permissions Denied and even though this is an older nandroid and everything has been wiped time and again, the permissions for the games I changed are still disabled.
Having trouble getting the program to actually undo anything though, and rebooting the phone is a rather tiresome task with all this going on just to find out nothing changed.
Does anyone know
1)Where permissions live, and if I can reflash whatever that is, as it is clearly corrupt here.
2)Where I can get a copy of the v2.9 apk for this app, as maybe it will be better at restoring what it did than the older version I dug up.
Edit2:I eventually just did a factory reset and it fixed everything. I had also emailed the developer of the app and he got back to me with the following advice:
It sounds like the permissions file is locked, packages.xml. Try opening my app, going into the settings, and make sure that the first option is NOT checked.
Then hit the unlock option to unlock the file.
If that doesn't work, try the following in a terminal...
su
chattr -ia /data/system/packages.xml\
Click to expand...
Click to collapse
Intuitively this sounds like it may have fixed the problem, so I'm posting it here in case anyone ends up with similar problems and finds this thread searching.
Hello there,
Since I have updated my LG G4 to 6.0 MM, I get a message every time when data option reconnect. It says: "customize your phone. Download carrier's apps and content" . I know it's T-mobile customization, but I don't want it on my phone.
When I go to Setings - Apps - Show System - App updates - notifiations I have 3 options:
*Priority
*Allow Peeking
*Hide sensitive content
No matter what I try but the message keeps coming back.
When I press "Force Stop" the message dissapear. But when data connect again after losing wifi or after a restart, the message is coming back.
What can I do so the message wil never come back again. Root and download the T-mobile customization is not an option
Without root, you are screwed, and the workaround you found is the only one available.
You could take out the sim, but that would render it quite useless.
With root you can undo all their cosmetic changes (like freeze the APK).
You can root without unlocking the bootloader, which would still allow you to flash an original image (recommend you make your own backup)
But it would be a bit more cumbersome without a nice recovery on the phone itself.
If you softbrick you will need a computer.
Along with the cosmetic changes, they might optimize certain settings for their network (at least I think they could).
So unless you download the patch and study it's effects (backup, install, backup again, compare changes).
You might be missing out on channel/network changes that could affect the quality of your service.
If you root, you might be able to trick your current rom into thinking it already has the patch applied, but this would be complicated.
It's easier to just override or remove their changes after it has been applied.
Like the boot animation, ringtones, backgrounds, etc.
FreezyExp said:
Without root, you are screwed, and the workaround you found is the only one available.
You could take out the sim, but that would render it quite useless.
With root you can undo all their cosmetic changes (like freeze the APK).
You can root without unlocking the bootloader, which would still allow you to flash an original image (recommend you make your own backup)
But it would be a bit more cumbersome without a nice recovery on the phone itself.
If you softbrick you will need a computer.
Along with the cosmetic changes, they might optimize certain settings for their network (at least I think they could).
So unless you download the patch and study it's effects (backup, install, backup again, compare changes).
You might be missing out on channel/network changes that could affect the quality of your service.
If you root, you might be able to trick your current rom into thinking it already has the patch applied, but this would be complicated.
It's easier to just override or remove their changes after it has been applied.
Like the boot animation, ringtones, backgrounds, etc.
Click to expand...
Click to collapse
In that case, let's root!
Thnx
So hello there!
I'm having the following issue and I'm kinda out of ideas.
I was running a (KingRoot) rooted fireOS 4.6.6.1 (420) if I'm not mistaken.
So this is what happened:
Phone was running just fine, but I wanted to get rid of the facebook background services which kept running without the actual app installed. Also a friend proposed to run the 'fstrim' command. So reading through xda I found an app called 3C Toolbox (http://www.3c71.com/android/?q=node/916) which seemed to be safe to use. Installed it and still didn't change a thing except for the three 'fstrim' actions to perform. After that I restarted my phone.
Powered off just fine, but at the start only the 'Amazon' logo comes up and vanishes into a black screen with the backlight still on. Even after waiting several hours nothing changes.
So what did I attempt to get it wirking again?
At first I tried to simply restart it. --> Nothing changed.
Tried to get into recovery and clean the cache. --> Nothing changed except the 'Amazon' being on for a bit longer
Get into ADB and try pull/uninstall... --> Guess due to the locked bootloader I'm not allowed to issue any command other than 'adb sideload [packagename]' for system updates. As for ADB itself I can only get it to recognize on the PC when I get into recovery and choose the 'apply update from ADB' option.
Get into fastboot according to this tutorial (https://forum.xda-developers.com/showthread.php?t=1668159) --> doesn't work.
Get into 'Safe Mode' with this tutorial (https://forum.xda-developers.com/fire-phone/help/how-to-fire-phone-to-boot-safe-mode-t2828240) --> doesn't work either.
So does anybody has another idea I could give a try or should I just abondon all my data and flash a new clean image?
Also I'm not sure if updating from ADB will erase all personal data too. Guess so, but maybe I can get a clearification in here too.
Hi,
Somehow I managed to forget my screenlock pattern (freshly changed) on my OnePlus 5T and it seems like my enrolled fingerprints are useless now. I need some help to recover access to my phone (preferably without factory reset).
This is the current situation of my phone:
- Phone Rooted
- TWRP Custom Recovery
- USB Debugging enabled
- WiFi On/Data and GPS OFF
- Currently logged in with my google account on the phone, but can't access it over the google account (i kind of disabled history and other features in my google acc).
- Also "Unknown Sources" is enabled on my phone.
If there is any way to recover the password via ADB, or to unlock the Data, that would be just awesome...
Thanks for any help.
derei said:
Hi,
Somehow I managed to forget my screenlock pattern (freshly changed) on my OnePlus 5T and it seems like my enrolled fingerprints are useless now. I need some help to recover access to my phone (preferably without factory reset).
This is the current situation of my phone:
- Phone Rooted
- TWRP Custom Recovery
- USB Debugging enabled
- WiFi On/Data and GPS OFF
- Currently logged in with my google account on the phone, but can't access it over the google account (i kind of disabled history and other features in my google acc).
- Also "Unknown Sources" is enabled on my phone.
If there is any way to recover the password via ADB, or to unlock the Data, that would be just awesome...
Thanks for any help.
Click to expand...
Click to collapse
Hey Bud,
I had a similar issue when I restored a nandroid backup and the password had been glitched so that I couldn't sign into my phone anymore.
Anyways here's a shortened version of a solution I found here: https://forums.oneplus.com/threads/fix-wrong-pin-pattern-when-restoring-twrp-nandroid-backup.452384/
1. Boot into TWRP
2. Open the file manager inside of TWRP and delete (or rename - they get restored whenever the phone is booted so deleting them does no harm) the following files inside "/data/system":
-password.key
-pattern.key
-locksettings.db-wal
-locksettings.db-shm
-locksettings.db
(they might not all be there but whichever ones you can find, delete/rename)
3. Reboot your phone and you should no longer have any kind of pin/pattern on your lockscreen
4. Re-setup your password and don't forget it this time!
Hope this helps :good:
BenisMusical said:
Hey Bud,
I had a similar issue when I restored a nandroid backup and the password had been glitched so that I couldn't sign into my phone anymore.
Anyways here's a shortened version of a solution I found here: https://forums.oneplus.com/threads/fix-wrong-pin-pattern-when-restoring-twrp-nandroid-backup.452384/
1. Boot into TWRP
2. Open the file manager inside of TWRP and delete (or rename - they get restored whenever the phone is booted so deleting them does no harm) the following files inside "/data/system":
-password.key
-pattern.key
-locksettings.db-wal
-locksettings.db-shm
-locksettings.db
(they might not all be there but whichever ones you can find, delete/rename)
3. Reboot your phone and you should no longer have any kind of pin/pattern on your lockscreen
4. Re-setup your password and don't forget it this time!
Hope this helps :good:
Click to expand...
Click to collapse
Hi, thanks.
I've been checking that post, but something didn't quite match. The following files are available on my phone ( /data/system):
-gatekeeper.password.key
-gatekeeper.pattern.key
-locksettings.db-shm
-locksettings.db
-locksettings.db-wal
So, as you can see, there are two files with the "gatekeeper" prefix. Are those two supposed to be also deleted (renamed)? Did you have them when you did your fix?
Thanks.
derei said:
Hi, thanks.
I've been checking that post, but something didn't quite match. The following files are available on my phone ( /data/system):
-gatekeeper.password.key
-gatekeeper.pattern.key
-locksettings.db-shm
-locksettings.db
-locksettings.db-wal
So, as you can see, there are two files with the "gatekeeper" prefix. Are those two supposed to be also deleted (renamed)? Did you have them when you did your fix?
Thanks.
Click to expand...
Click to collapse
Hey man,
When I fixed my issue I didn't touch those - worst comes to worst just rename the files that were on the list I gave and leave the other 2. If it doesn't work then you can try renaming the files you found from my list as well as the two you have highlighted in red.
Give that a try
BenisMusical said:
Hope this helps :good:
Click to expand...
Click to collapse
Just did the steps (including the gatekeeper. prefixed files) - I just renamed them, so I can revert back. Indeed I was able to get my phone unlocked, but everything is blank. Only a wallpaper, status bar and Nav Bar. No apps, no app drawer, nothing. I can access the Settings, but that doesn't help much... (except that I can set a new password).
Going in Settings -> Apps, shows me all the apps, which is good. But I can't see them on screen.
Also, the following are happening:
- Settings -> Apps -> Defaults: Nothing set up for "Home App". And there is a blank grey menu when I click on it.
- Settings -> Apps -> Application List -> OnePlus Launcher: clicking on Open By Default, crashes the Settings Menu.
Is it possible that I did something wrong here?
derei said:
Just did the steps (including the gatekeeper. prefixed files) - I just renamed them, so I can revert back. Indeed I was able to get my phone unlocked, but everything is blank. Only a wallpaper, status bar and Nav Bar. No apps, no app drawer, nothing. I can access the Settings, but that doesn't help much... (except that I can set a new password).
Going in Settings -> Apps, shows me all the apps, which is good. But I can't see them on screen.
Also, the following are happening:
- Settings -> Apps -> Defaults: Nothing set up for "Home App". And there is a blank grey menu when I click on it.
- Settings -> Apps -> Application List -> OnePlus Launcher: clicking on Open By Default, crashes the Settings Menu.
Is it possible that I did something wrong here?
Click to expand...
Click to collapse
Possibly?
When I followed the method in the link in my previous post I had no issues - I just had to setup a new lock method.
It may have been the gatekeeper files - when I did this method previously I didn't touch those as I didn't know they were there
Do you have a backup from TWRP by any chance that you could restore?
BenisMusical said:
Possibly?
When I followed the method in the link in my previous post I had no issues - I just had to setup a new lock method.
It may have been the gatekeeper files - when I did this method previously I didn't touch those as I didn't know they were there
Do you have a backup from TWRP by any chance that you could restore?
Click to expand...
Click to collapse
Restored the gatekeeper files, but no success. Same behaviour. I have a backup, but is only a "initial backup" - sort of how the phone was at first. I was too dumb to do a backup after I set up everything.
It seems my only way now would be to do a factory reset and lose all data.
Unless there would be a way to recover the password from the database? I know is encrypted and salted, but that salt also has to be stored somewhere... maybe there would be a way to revert that hash into a pattern? grr, this is extremely frustrating.
derei said:
Restored the gatekeeper files, but no success. Same behaviour. I have a backup, but is only a "initial backup" - sort of how the phone was at first. I was too dumb to do a backup after I set up everything.
It seems my only way now would be to do a factory reset and lose all data.
Unless there would be a way to recover the password from the database? I know is encrypted and salted, but that salt also has to be stored somewhere... maybe there would be a way to revert that hash into a pattern? grr, this is extremely frustrating.
Click to expand...
Click to collapse
I apologise for possibly making matters worse whilst trying to help but this is beyond my understanding of TWRP's capabilities
It might be worth restoring your previous backup even if it is blank and then setting up your phone again. During the setup choose an option that should be something like: "Restore from the cloud" which will allow google to restore most of your app data. However, your internal storage will be completely wiped . Once that's all good and setup then definitely make a backup - it's a good habit to get into and will save you a lot of hassle in future.
I don't know if there's anything else I can suggest you to do,
hope this doesn't take up too much time - I personally know how infuriating it is to spend hours on something when there's no easy solution. You'd be better starting from a clean flash of OOS.
Sorry, there's nothing else I can think of to help you out
Best of luck bud.
BenisMusical said:
Sorry, there's nothing else I can think of to help you out
Best of luck bud.
Click to expand...
Click to collapse
I'm grateful for your effort. It offered a solution. It just got more complicated than expected. Probably the last Oxygen update patched some security issues - which is not bad after all (it's just bad for me NOW).
Personal data is encrypted with the screen lock pattern, so your only choice is a factory reset