Hello, I am having bootloop issues after installing the update that showed up this morning and I'm hoping someone can help!
Samsung Galaxy S8, Android 9 Pie, US Unlocked model. I know we got an update a few days ago but apparently there's another one. The version is 9/PPR1.180610.011/G950U1UEU6DSJ4
The phone reboots a few times and goes to Android Recovery (it is not rooted) with the message Reboot Recovery Cause is [Binder: 1485_5:2416 RecoverySystemRescueParty]# No Support SINGLE-SKU
It also says
File-Based OTA, Supported API: 3
E: unknown volume for path [/odm], E: unknown volume for path [/vendor], E: unknown volume for path [/odm], E: unknown volume for path [/vendor]
I use Substratum Lite and Swift Black, along with a few other Substratum mods and tweaks for Android 9 Pie. Is there a way to remove these without resetting?
The phone appears to reboot before ADB can access anything. It says "This adb server's ADB_VENDOR_KEYS is not set"
The phone pops up in Windows Explorer, but the phone bootloops before it can be opened
The most confusing part is that the phone appears to make it to the SystemUI, though I don't see anything (no lockscreen, homescreen, etc.).
I have Fluid Navigation Gestures installed, my after phone gets past the Samsung logo , I see the toast for FNG pop up "FNG is Enabled" and stay on the black screen until my phone restarts.
Is there anything I can do to avoid resetting? I'm willing to try to root it to try to remove the Substratum Overlays through TWRP, but I don't know if that would be possible considering I can't currently interact with the phone
Thank you for taking a look!
Related
Ok, my Nexus 7 is stuck - not getting passed from Google boot screen.
Here is a bit of history..
I unlocked and installed Cyanogen 10.1 awhile back, and TWRP recovery. It's actually dual rom - I can't remember the name of the other ROM.
I haven't used it for a few months and today I charged the battery and used it. It was all good until I checked for update and found that there is Cyanogen 10.2.1. So I clicked download and install.
It downloaded, then rebooted. And when the system is up, I got the pop up saying Google Service is stopped unexpectedly. Some app icons I got on my home screen are still there, but there is no menu bar. There is no home button, no app drawer. So I rebooted, and the same google service error.
So I thought, maybe it's not compatible with 10.2. I rebooted into recovery mode and install 10.1 (the old rom zip file was still on the device) using TWRP. Only took a few seconds and then it says successful/done. To make sure, I also did wipe dalvik cache, then reboot.
Now the system only goes as far as Cyanogen loading screen. That's it. So I hold the power button for a few seconds, then when the device restart, pressed the volumn down button. Then I chose 'reboot recovery'.
It doesn't. It just hangs at Google screen. I tried a few times, the same. So trying to reboot into recovery hangs at google screen, and trying to reboot normally hangs at Cyanogen screen.
As a last attempt, I let the screen hangs on Cyanogen log, connected the device to my Mac, then tried "fastboot devices". Nothing.. empty.
But when I tried "adb devices", I get an entry something like this
Code:
List of devices attached
015d2bcxxxxxx unauthorized
Code:
./adb shell
error: device unauthorized. Please check the confirmation dialog on your device.
What should I do to get my tablet working again? I dont mind losing all data - I just want it working again. Someone please advice me..
I used the engineering bootloader to root my phone so I could install Xposed, but as it tried to reboot out of download mode it has been stuck for about 10 minutes so far on the AT&T splash screen, with the LED at the top changing colours, and the phone vibrating, three quick vibrations then a pause followed by a single slightly longer one. It's also getting pretty hot. I tried holding the power button and got no results, did I **** my phone?
EDIT - Okay, managed to soft reset it, but when it tries to boot it just hangs at the AT&T splash screen still. I can get into the recovery menu, should I do a factory reset?
EDIT 2 - Ended up doing the factory reset after I tried reinstalling the engineering bootloader and that seemed to fix it.
Okay so after I set my phone back up I restarted it and after I put in my pattern (I had set the phone to require my pattern to boot) it's stuck on a locking with a wheel around it that's changing colours on a black screen? Never seen that before. It's also getting very hot and doing the vibrating it was earlier.
I tried doing a factory reset and that did get me back into the OS, but I'm getting "Security notice: Unauthorized actions have been detected." And I can't seem to download apps from the play store, it just says "downloading" and has a green bar going across the progress bar but I don't think its actually downloading anything.
EDIT - Now Google Play won't open at all.
Can't re-flash or anything?
How about this? http://forum.xda-developers.com/tmobile-s7-edge/how-to/guide-post-root-common-bugs-fixes-t3427600
Bug #3: Notification warning that system has been modified.
Fix #1: Disable com.samsung.android.securitylogagent & com.tmobile.pr.adapt using your favorite package disabler. This will hide all notifications associated with this app as well as the root check that you might have encountered.
Fix #2: This fix requires Xposed. You can follow the instructions to install Xposed HERE.
Then install the Xposed module NotifyClean, activate the module, and reboot the phone. You will then use this app to block the notification under the package com.samsung.android.securitylogagent by clicking on the package so that it is highlighted red. The notification should disappear!
Note: This app can also be used to hide the icon for WiFi Calling if it's annoying you. You can still use the WiFi calling function while hiding the notification.
--------------------------------------------------------------------------------------------------
MY DEVICE DISPLAYED A NOTIFICATION, “UNAUTHORIZED ACTIONS HAVE BEEN DETECTED. RESTART YOUR PHONE TO UNDO ANY UNAUTHORIZED CHANGES.” WHAT DO I DO?
During regular security checks of the Linux kernel, the system has detected that the kernel has been modified. The following may be the possible causes:
You may have installed a malicious or flawed app, which attempted to modify the kernel code or file system
You may have accidentally removed or modified a system file
One of these messages may also appear, “To protect your device. It is recommended you reboot.” or “The device has detected an application attempting to perform actions that are not permitted. It is recommended that you restart your device.”
Restart your device to try to restore the kernel code back to normal. However, some kernel modifications made to the file system cannot be restored. Also, the original cause of the problem might still persist. Therefore, you might continue to see this error after the reboot.
https://www2.samsungknox.com/en/faq...actions-have-been-detected-restart-your-phone
Hi Everyone,
My phone asked for update then after update was complete it got turned on and it booted up to the encryption lock screen where it says to start up your device, enter your pin. So I enter my pin and then its says, "verified" and then "starting android". and then a padlock appears on the screen, it opens, and there's like a load up circle going around it. At first, I let the phone sit to see if it would do anything but after an hour, I figured something is wrong. I dont know why this happened. I don't want to have to factory reset and lose all my pictures and data. I can boot into recovery mode but sometimes when i turn it on it shows a screen that says installing update and has like a google ring looking thing that should be spinning around but it looks like its glitching out, after that screen it will go to a no command screen, and then it will eventually reach recovery mode but all I can see is:
#fail to open recovery_cause(no such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
Successfully verified dmverity hash tree
E:Failed to clear BCB Message: failed to find / misc partition.
I have tried safty mode, but this also didn't helped. I really hope someone can help or knows what is going on because, I really dont want to lose all my pictures.
Thanks you.
Veronica97 said:
Hi Everyone,
My phone asked for update then after update was complete it got turned on and it booted up to the encryption lock screen where it says to start up your device, enter your pin. So I enter my pin and then its says, "verified" and then "starting android". and then a padlock appears on the screen, it opens, and there's like a load up circle going around it. At first, I let the phone sit to see if it would do anything but after an hour, I figured something is wrong. I dont know why this happened. I don't want to have to factory reset and lose all my pictures and data. I can boot into recovery mode but sometimes when i turn it on it shows a screen that says installing update and has like a google ring looking thing that should be spinning around but it looks like its glitching out, after that screen it will go to a no command screen, and then it will eventually reach recovery mode but all I can see is:
#fail to open recovery_cause(no such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
Successfully verified dmverity hash tree
E:Failed to clear BCB Message: failed to find / misc partition.
I have tried safty mode, but this also didn't helped. I really hope someone can help or knows what is going on because, I really dont want to lose all my pictures.
Thanks you.
Click to expand...
Click to collapse
You can try and downgrade the update, but I cannot say for sure if it will wipe your phone. You can go back to recovery and in the yellow font area look for G935P. That will have your firmware version and if you go to sam mobile you can look for the version before it. Flash it with odin and you might be able to boot up again. Data recovery is hard when the phone is encrypted.
Good luck!
same problem ... i just update my phone in latest oreo via OTA and it never open stock in samsung s7 edge name... i coudnt downgrde it always failed in odin.. any soultion please..
did u manage to solve it ? i have same problem
Veronica97 said:
Hi Everyone,
My phone asked for update then after update was complete it got turned on and it booted up to the encryption lock screen where it says to start up your device, enter your pin. So I enter my pin and then its says, "verified" and then "starting android". and then a padlock appears on the screen, it opens, and there's like a load up circle going around it. At first, I let the phone sit to see if it would do anything but after an hour, I figured something is wrong. I dont know why this happened. I don't want to have to factory reset and lose all my pictures and data. I can boot into recovery mode but sometimes when i turn it on it shows a screen that says installing update and has like a google ring looking thing that should be spinning around but it looks like its glitching out, after that screen it will go to a no command screen, and then it will eventually reach recovery mode but all I can see is:
#fail to open recovery_cause(no such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
Successfully verified dmverity hash tree
E:Failed to clear BCB Message: failed to find / misc partition.
I have tried safty mode, but this also didn't helped. I really hope someone can help or knows what is going on because, I really dont want to lose all my pictures.
Thanks you.
Click to expand...
Click to collapse
i have same problem i guess but my phone keeps reabooting after failing to autoenter the recovery
I sent my phone to a Samsung Repair center because the Home-Button didn't work anymore (Fingerprint recognition worked, just no press-down function)
After 3 days I got an e-mail saying they are returning the phone because they ran into software issues. Seeing as my phone was out of warranty I was running TWRP and the Superman Rom, without issues mind you. However, Being a Samsung Repair center, they are forced to wipe phones before working on them. I have no idea what they've done but it's stuck in a software-less bootloop it seems.
So now I've got my S7 Edge back, stuck on an infinite Samsung load screen, TWRP seems to be gone and when trying to put the phone into Download mode the Volume up/down buttons stop functioning.
When messing about with different combinations of buttons, I am able to get into a very basic-looking recovery menu titled 'Samsung Recovery' I'm able to browse through the options using the Volume buttons but i cannot use the 'Apply Update from ADB' or 'Apply Update from SD Card' functions due to error: 'Update from external storage is disabled'.
Moving on to ADB, I can see my device in Sideload, but I cannot use command ADB REBOOT RECOVERY, it outputs error "adb reboot recovery error: closed"
I've tried the Samsung 300k tool, but it does not recognize the S7 Edge. Also Odin does not see my device as connected, I've reinstalled the samsung device drivers, done a few reboots, etc.
So... How do I install TWRP or any other bootmanager without being able to use the volume buttons in the recovery menu?
Also, since I'm able to use the PWR+Home+Vol.Down combination, I wonder if they did actually fix the home-button issue.
Today, I've updated Google Play Services on my Nokia 5 TA-1053 with Android 9 and the latest (July 2019) OS patches installed.
What happens now when I power the device on:
1. It vibrates once and shows the "Powered by Android" logo
2. It shows the Nokia logo and plays the Nokia sound
3. It prompts me to insert my PIN (for full disc encryption)
4. After entering the PIN, it shows "Checking"
5. It shows the Nokia logo for quite some time
6. It shows the lock screen
7. Now, whatever I do, after a few seconds it will show "Powered by Android" and repeat steps 5.-7. in an endless loop.
What can I do? Do you know how to debug or fix this issue? I do have adb installed but the device is not in developer mode I think and the "few seconds" in 7. are too short to open the system menu and get there.
I've already tried booting in "Safe mode" (by pressing volume down and power button at the same time to power it on). Result: Identical, only that the device shows a "Safe mode" label in the lower left.
Please note: The device is not rooted, the boot loader is not touched.
I tried getting into recovery mode following these steps:
1. turn off Nokia 5
2. connect to power supply
3. wait until phone went past "powered by android" screen and displays the battery loading animation
4. press down "Volume Up" and "Power" buttons and keep them pressed
Expected:
Android should open menu to recovery mode
What happens:
The phone displays android symbol with open stomach and a warning symbol. Below that it says "No command.".
Source: https://nokiatips.com/2017/08/21/nokia-5-recovery-mode/
Additional info: If I keep the two buttons pressed after the symbol is displayed, the device tries to reboot but doesn't even come to the "Nokia" logo.
Please note that – contrary to many guides on the internet – it does NOT show the "Please release key to power off" message at any time.
I found another guide, but I cannot get it to work, i.e. nothing happens except the full-disc encryption PIN prompt shows up:
https://www.hardreset.info/devices/nokia/nokia-5/recovery-mode/
Another guide:
https://www.teamandroid.com/2017/09/06/nokia-5-recovery-mode/
But the computer cannot connect to my Phone, and as a result, I get
$ adb reboot recovery
error: no devices/emulators found
How I finally got it working with the help of
https://nokiamob.net/2018/03/24/how...n-freeze-nokia-smartphones-with-android-oreo/
1. Turn off the phone and connect it to a PC or a charger
2. Wait until the battery sign appears
3. Hold the Power + Volume Up buttons until the phone vibrates
4. Release the Power button, but keep holding Volume Up until an Android logo appears
5. When the Android logo appears, press (and hold) the Power button and just click Volume Up
6. Now you should be in recovery mode
Some interesting stuff from the logs:
/cache/recovery/last_log[,.1-9] has no interesting info, no error messages, etc.
/cache/recovery/last_kmsg[,.1-9] has some interesting stuff:
It has a huge "NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE" block followed by these lines:
Code:
trace_printk() being used. Allocating extra memory.
This means that this is a DEBUG kernel and it is unsafe for produciton use.
If you see this message and are not debugging the kernel, report this immediately to your vendor!
So I did. If that is really true what it looks like (that Nokia ships debug kernels in production) I guess this is the reason why this device feels so slow…
A few pages below it also shows a kernel OOPS (Warning) about 3.5 seconds after boot:
Code:
----------[ cut here ]--------------
WARNING: CPU: 0 PID: 318 at /home/cm/Image/All_Project_Workspace/LINUX/android/kernel/msm-3.18/include/linux/of.h:770 smb_parse_dt+0x1198/0x11d8()
Modules linked in:
CPU: 0 PID: 318 Comm: kworker/u16:4 Not tainted 3.18.120-perf #1
Hardware name: Qualcomm Technologies, Inc. MSM8937-PMI8950 - FIH D1 DVT (DT)
Workqueue: deferwq deferred_probe_work_func
Call trace:
[<hex>] dump_backtrace+0x0/0x300
[<hex>] show_stack+0x20/0x28
[<hex>] dump_stack+0x80/0xa4
[<hex>] warn_slowpath_common+0x90/0xb44
[<hex>] warn_slowpath_null+0x38/0x44
[<hex>] smb_parse_dt+0x1198/0x11d8
[<hex>] smbchg_probe+0xb98/0x2be0
[<hex>] spmi_drv_probe+0x28/0x34
[<hex>] driver_probe_device+0x16c/0x384
[<hex>] __device_attach_driver+0x90/0xa0
[<hex>] bus_for_each_drv+0x98/0xc8
[<hex>] __device_attach+0x9c/0x130
[<hex>] device_initial_probe+0x24/0x30
[<hex>] bus_probe_device+0x38/0x98
[<hex>] deferred_probe_work_func+0xa8/0xd8
[<hex>] process_one_work+0x278/0x414
[<hex>] worker_thread+0x32c/0x450
[<hex>] kthread+0xec/0xf4
---[ end trace 65507f299931cd9e ]---
This warning repeats a few times.
At second 33, the device starts with these printouts to last_kmsg:
Code:
fih_statusroot efs_open: reado to open statusroot
[statusroot_readinfo_work_func] Fail to open systeminfo partition!
This warning also repeats a few times.
Later on I only get stuff from fih_dump_info and healthd, nothing looking wrong.
Wiping the cache (from the recovery menu) did not work.
Now the remaining useful options are:
Mount /system
Apply update from ADB
Wipe data/factory reset
But where do I get an update from ADB?
After retrying the regular boot many times, it randomly went back to normal.
I still would be interested in how to get this issue permanently resolved in case it happens again to me or somebody else.
Same issue
The same thing happened to me, but in my case it started happening after a system wipe, the initial setup worked just fine, but after that, it started doing the same thing as yours, I temporarily fixed it by disabling the Play Store app, right now the phone is working fine, but I can't use Play Store so I'm limited to installing apps through apks
A few days later, the Play Store metadata seems to suggest me to downgrade (!) the Play Services app.
Steps to see this:
1. Open Aurora store. Note that you won't see this in "Updates"
2. switch to "Installed"
3. Open "Google Play Services"
There it says it wants to "update" from 18.3.81 (100406-257258062) to 17.7.85 (100406-253824076).
So I'll try to do that after the next backup.
KaiiSukii said:
The same thing happened to me, but in my case it started happening after a system wipe, the initial setup worked just fine, but after that, it started doing the same thing as yours, I temporarily fixed it by disabling the Play Store app, right now the phone is working fine, but I can't use Play Store so I'm limited to installing apps through apks
Click to expand...
Click to collapse
I have the play store app permanently disabled and am using the Aurora store instead. As it operates on the same data, there should be no difference.