Related
Hello All, This is my first time posting so could not post directly into http://forum.xda-developers.com/showthread.php?t=2021640&page=23.
I’ve been having a problem with SPH-D710 FK23 and from what I’ve read and searched, it doesn’t seem to be common but would like to ask the experts. I’ve installed FK23 from the above thread [LINK][ROM][ODIN][TAR]SPH-D710 FK23 (FK23 Modem/Kernel/ROM - Root/Stock), trying first the Rooted_Nodata but then using Rooted_Restore. I’ve redone the phone three times now using Rooted_Restore and the first thing that seems very odd is that the internal USB did not get wiped. After it completed and booted, the items on the internal USB (such as in the downloads directory) were still present. Once I entered my Google account, the apps reinstalled from Google.
Aside from not seeming to completely wipe the device, there didn’t appear to be any problem until I turned on Bluetooth. Once Bluetooth was turned on and paired with my BlueAnt Q2 v.1.1, the device would freeze and reboot. At this point, I’m not able to turn off Bluetooth as even after rebooting (including a battery pull) the system only responds to touch during the initial few moments of boot while showing scanning and/or initializing SD. After a few moments, no screen interaction will respond other than vibration feedback when pressing any of the four bottom buttons. Volume up/down is not responsive though the power button will still blank or turn the screen on. Aside from that the device appears locked than will eventually reboot itself.
Has anyone seen similar and/or any suggestions?
kdean7 said:
Hello All, This is my first time posting so could not post directly into http://forum.xda-developers.com/showthread.php?t=2021640&page=23.
I’ve been having a problem with SPH-D710 FK23 and from what I’ve read and searched, it doesn’t seem to be common but would like to ask the experts. I’ve installed FK23 from the above thread [LINK][ROM][ODIN][TAR]SPH-D710 FK23 (FK23 Modem/Kernel/ROM - Root/Stock), trying first the Rooted_Nodata but then using Rooted_Restore. I’ve redone the phone three times now using Rooted_Restore and the first thing that seems very odd is that the internal USB did not get wiped. After it completed and booted, the items on the internal USB (such as in the downloads directory) were still present. Once I entered my Google account, the apps reinstalled from Google.
Aside from not seeming to completely wipe the device, there didn’t appear to be any problem until I turned on Bluetooth. Once Bluetooth was turned on and paired with my BlueAnt Q2 v.1.1, the device would freeze and reboot. At this point, I’m not able to turn off Bluetooth as even after rebooting (including a battery pull) the system only responds to touch during the initial few moments of boot while showing scanning and/or initializing SD. After a few moments, no screen interaction will respond other than vibration feedback when pressing any of the four bottom buttons. Volume up/down is not responsive though the power button will still blank or turn the screen on. Aside from that the device appears locked than will eventually reboot itself.
Has anyone seen similar and/or any suggestions?
Click to expand...
Click to collapse
Actually think I have an answer for this now... and it has to do with the change to the storage structure and/or mount points. Before the main mount point for /sdcard was... /sdcard. Now looks like it's /storage/sdcard0. That's the only reason I can think of why it would fail - the script is still triggered so only if it didn't find /sdcard would it skip.
garwynn said:
Actually think I have an answer for this now... and it has to do with the change to the storage structure and/or mount points. Before the main mount point for /sdcard was... /sdcard. Now looks like it's /storage/sdcard0. That's the only reason I can think of why it would fail - the script is still triggered so only if it didn't find /sdcard would it skip.
Click to expand...
Click to collapse
Any idea on the unresonsiveness and rebooting?
kdean7 said:
Any idea on the unresonsiveness and rebooting?
Click to expand...
Click to collapse
Think it's part of the nodata flash effects still lingering.
Try this:
1) Flash FI27 full restore (rooted)
2) Reboot to Odin
3) Flash FK23 full restore (rooted)
That should fix it if it's old data not playing nice.
If it still happens after this the next step we'll do is check your battery.
garwynn said:
Think it's part of the nodata flash effects still lingering.
Try this:
1) Flash FI27 full restore (rooted)
2) Reboot to Odin
3) Flash FK23 full restore (rooted)
That should fix it if it's old data not playing nice.
If it still happens after this the next step we'll do is check your battery.
Click to expand...
Click to collapse
Is it possible that kdean7's problems are because of restoring Google's backup during the initial configuration process?
garwynn said:
Think it's part of the nodata flash effects still lingering.
Try this:
1) Flash FI27 full restore (rooted)
2) Reboot to Odin
3) Flash FK23 full restore (rooted)
That should fix it if it's old data not playing nice.
If it still happens after this the next step we'll do is check your battery.
Click to expand...
Click to collapse
Not sure if what i've done is the same outcome as above but did this yesterday before this was posted. Booted to recovery mode and wiped device / factory restore then flashed FK23 full restore (rooted). SInce then, I've added back my google account, added my Samsung account, added one exchange email and one pop3 email and have been letting the device self-update and reinstall the apps from the Play store. Made one test call and a couple txt messages. I've been waiting until no further updated occur before turning bluetooth back on but so far have't seen any random reboots though don't think I've used it long enough to see any screen locking. More to come as I test further this morning.
kdean7 said:
Not sure if what i've done is the same outcome as above but did this yesterday before this was posted. Booted to recovery mode and wiped device / factory restore then flashed FK23 full restore (rooted). SInce then, I've added back my google account, added my Samsung account, added one exchange email and one pop3 email and have been letting the device self-update and reinstall the apps from the Play store. Made one test call and a couple txt messages. I've been waiting until no further updated occur before turning bluetooth back on but so far have't seen any random reboots though don't think I've used it long enough to see any screen locking. More to come as I test further this morning.
Click to expand...
Click to collapse
Don't recall if the factory reset wipes USB storage, that would be the only possible difference.
Hope that gets you back into shape, will be checking during the day to see if you need any further help!
Same thing happening still
garwynn said:
Don't recall if the factory reset wipes USB storage, that would be the only possible difference.
Hope that gets you back into shape, will be checking during the day to see if you need any further help!
Click to expand...
Click to collapse
Same symptoms happened again. I am going to make another attempt based on the the previous method starting back at ics.
garwynn said:
Think it's part of the nodata flash effects still lingering.
Try this:
1) Flash FI27 full restore (rooted)
2) Reboot to Odin
3) Flash FK23 full restore (rooted)
That should fix it if it's old data not playing nice.
If it still happens after this the next step we'll do is check your battery.
Click to expand...
Click to collapse
This will sound like a very basic NOOB question but I want to ensure I do this exactly as suggested. I've flashed using SPH-D710_FI27_CL1127689_Rooted_Restore.
For reboot to Odin; Is that mean to boot by holding the Down Vol + Pwr then just powering down from that screen? Or possibly boot by holding Up + Vol and selecting one of those options?
I would also like to say THANK YOU to everyone who has been working on the D710. I've been following postings on this device and the knowledge everyone shares is simply amazing!!!
Still Freezing
kdean7 said:
This will sound like a very basic NOOB question but I want to ensure I do this exactly as suggested. I've flashed using SPH-D710_FI27_CL1127689_Rooted_Restore.
For reboot to Odin; Is that mean to boot by holding the Down Vol + Pwr then just powering down from that screen? Or possibly boot by holding Up + Vol and selecting one of those options?
I would also like to say THANK YOU to everyone who has been working on the D710. I've been following postings on this device and the knowledge everyone shares is simply amazing!!!
Click to expand...
Click to collapse
After installing SPH-D710_FI27_CL1127689_Rooted_Restore.exe, booting into odin mode, then installing SPH-D710_FK23_549262_Rooted_Restore.exe, I provided account information for Google and Samsung but this time did not allow the automatic reinstall of apps from the play store. The phone seemed to not exhibit any issues until after the apps shown as needing updates from the play store and the installation of IP Cam Viewer Pro, the phone again started freezing and became unresponsive.
I appreciate the suggestions but will move back to FI27 for a while.
kdean7 said:
After installing SPH-D710_FI27_CL1127689_Rooted_Restore.exe, booting into odin mode, then installing SPH-D710_FK23_549262_Rooted_Restore.exe, I provided account information for Google and Samsung but this time did not allow the automatic reinstall of apps from the play store. The phone seemed to not exhibit any issues until after the apps shown as needing updates from the play store and the installation of IP Cam Viewer Pro, the phone again started freezing and became unresponsive.
I appreciate the suggestions but will move back to FI27 for a while.
Click to expand...
Click to collapse
Think one of your apps may not like the JB build. You could try installing 1-2 at a time and see when it starts acting up to get a better idea of which one it may be...
Sent from my SPH-D710 using Tapatalk 2
Found app causing crash
Looks like I may have found the app causing the crash. Breaking News Newtork (BNN). I saw that it crashed after installing that app last time as I was taking everything very slow and testing after individual apps. It wasn't immediate upon install, only after a reboot. So far without that being reinstalled, things are still working. Still running with minimal apps but so far so good.
[Q&A] [SM-T525] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 10.1 LTE (picassolte)
Q&A for [SM-T525] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 10.1 LTE (picassolte)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [SM-T525] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 10.1 LTE (picassolte). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
RaiBinger said:
Hi again!
In 211014 ROM trouble with video in YouTub. If set pause then after play again video not work. Tell me please in last build ROM nightly update this issue resolved?
Click to expand...
Click to collapse
I have the same problem. at the same time when it occurs in other players turns off hardware decoding.
@crpalmer "As far as I am concerned, installing Xposed is the exact opposite of a clean install. Xposed can cause all kinds of problems (it just randomly changes how internals of the system work!).
If you have problems with a clean install (without Xposed), please provide logs.
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access here -->."
I have factory reset, data wipe cache and delvik wipe and then just flashed Nightly from 24.10.2014 and gapps. Cannot even get through the set up before the screen flickers and the device reboots.
So installed the nightly from 27.10 and all was good for a few hours then the random reboots have started again. No xposed or any other mods. Will provide logs.
joeb690 said:
So installed the nightly from 27.10 and all was good for a few hours then the random reboots have started again. No xposed or any other mods. Will provide logs.
Click to expand...
Click to collapse
So I'm not sure what to do next, device is unfortunately unusable, I must of made a mistake somewhere along the line.
What I have tried so far:
1. boot into cwm recovery
2. wipe data/factory reset
3. wipe cache
4. wipe delvik cache
5. install nightly 27.10.2014
6. wipe cache
7. wipe delvik cache
8. install gapps from link provide in OP
9. repeat steps 6 & 7
10 reboot system.
Sometimes it will boot normally and allow me to proceed through set-up but will then very quickly crash/reboot and the it seems to be in a bootloop, or other times it will show the Samsung splash and then power off.
Yesterday I was able to use it for several hours with out a problem but then suddenly it restarted and was once again very unstable.
Also getting very erratic battery readings ( I preformed a battery calibration before wiping Touchwiz probably a big mistake I realise now )
Any help or ideas would be greatly appreciated. :good:
not sure how to provide logs as the device is so unpredictable.
joeb690 said:
So I'm not sure what to do next, device is unfortunately unusable, I must of made a mistake somewhere along the line.
What I have tried so far:
1. boot into cwm recovery
2. wipe data/factory reset
3. wipe cache
4. wipe delvik cache
5. install nightly 27.10.2014
6. wipe cache
7. wipe delvik cache
8. install gapps from link provide in OP
9. repeat steps 6 & 7
10 reboot system.
Sometimes it will boot normally and allow me to proceed through set-up but will then very quickly crash/reboot and the it seems to be in a bootloop, or other times it will show the Samsung splash and then power off.
Yesterday I was able to use it for several hours with out a problem but then suddenly it restarted and was once again very unstable.
Also getting very erratic battery readings ( I preformed a battery calibration before wiping Touchwiz probably a big mistake I realise now )
Any help or ideas would be greatly appreciated. :good:
not sure how to provide logs as the device is so unpredictable.
Click to expand...
Click to collapse
There isn't any crash in the last_kmsg. Are the logs pulled after a crash?
Yes. Will provide another log today.
Unfortunately cannot provide another log as it the device will not work long enough to email the log, will flash stock ROM and see what happens. Maybe it a physical problem.
So flashed stock using odin and problems persist. Rebooting at what seems like random times. And then during the reboot it will reboot and then sometimes nothing it's dead and doesn't react to any action except putting it in download mode. Doesn't matter if I have several apps running or if I let it idle. Never had any issues like this before rooting. Any ideas as to where I went wrong.
I know this has nothing to do with your ROM but any feedback would be appreciated. Thanks.
joeb690 said:
So flashed stock using odin and problems persist. Rebooting at what seems like random times. And then during the reboot it will reboot and then sometimes nothing it's dead and doesn't react to any action except putting it in download mode. Doesn't matter if I have several apps running or if I let it idle. Never had any issues like this before rooting. Any ideas as to where I went wrong.
I know this has nothing to do with your ROM but any feedback would be appreciated. Thanks.
Click to expand...
Click to collapse
Are you sure you flashed the right Odin images? Did you factory reset?
One thing to try would be to flash the CM recovery (twrp would also be fine if it supports last_kmsg and I forget if it does) and let it sit and see if it reboots. If so, then grab the last_kmsg via adb. If you want to flash CM again, you can try to use adb to get a last_kmsg via adb since it just has to boot long enough for adb to access it.
I flashed the latest image for the German sm t525 model from sammobile. I have performed a factory reset but I thought that when you flashed an image with odin the device is wiped clean? Do you mean CWM recovery you provide in the OP? Thanks for you reply.
Hi,
I have Bluetooth issues since some versions. Cannot connect to any device....
Other question: is it still ro.sf.lcd_density=320 ?
dft601 said:
Hi,
I have Bluetooth issues since some versions. Cannot connect to any device....
Other question: is it still ro.sf.lcd_density=320 ?
Click to expand...
Click to collapse
Do you know (and if you not would you mind trying a couple of versions) when bluetooth problems would have started?
I recently changed the density setting to ro.sf.lcd_density=320 because it seemed to fix some apps that had weird issues (e.g. Chrome Beta's tabs). Is it causing a problem for you?
crpalmer said:
Do you know (and if you not would you mind trying a couple of versions) when bluetooth problems would have started?
I recently changed the density setting to ro.sf.lcd_density=320 because it seemed to fix some apps that had weird issues (e.g. Chrome Beta's tabs). Is it causing a problem for you?
Click to expand...
Click to collapse
Hmm, sorry, do not know which version I had last before 200141109, I already deleted from my device.. at least 200141107....
No, I have no problem with the density. It fixes also problems for me (e.g. Swiftkey, Navigon,....) Till now I added this manually.
Mike
Autorotate and Contact view
Hi
I'VE installed the latest version and untill now everything is fine for me,
But whenn I open my contacts the autorotate function stops to work and I have to turn my tab by 180°
Hello there!
The rom is working great, battery time is better than stock rom, and its much faster and smoother!
Altough I am having one issue with my tablet. Sometimes on random (really random!), when I try to unlock the tablet it stops responding to touch - at all! I cannot unlock it, cannot restart it normally, cannot do anything. I have to reboot the tab by holding power button down.
I changed dpi to 240, because 320 was too high for me, everything was so big - but I don't think that dpi has something to do with the issue.
Also sometimes my Link2SD script doesnt load the 2nd sdcard partition - but this might not be connected with the rom.
But anyway this rom is great and I am happy to have it on my tablet! You're doing great job mate! Thanks a lot. The only thing I miss is multi- and floating- windows, but I can live without it.
PS I noticed you are working on Cyanogenmod 12 for exynos version, do you plan building and trying it for our snapdragon version?
poleq16 said:
Hello there!
The rom is working great, battery time is better than stock rom, and its much faster and smoother!
Altough I am having one issue with my tablet. Sometimes on random (really random!), when I try to unlock the tablet it stops responding to touch - at all! I cannot unlock it, cannot restart it normally, cannot do anything. I have to reboot the tab by holding power button down.
I changed dpi to 240, because 320 was too high for me, everything was so big - but I don't think that dpi has something to do with the issue.
Also sometimes my Link2SD script doesnt load the 2nd sdcard partition - but this might not be connected with the rom.
But anyway this rom is great and I am happy to have it on my tablet! You're doing great job mate! Thanks a lot. The only thing I miss is multi- and floating- windows, but I can live without it.
PS I noticed you are working on Cyanogenmod 12 for exynos version, do you plan building and trying it for our snapdragon version?
Click to expand...
Click to collapse
I posted a status update in the sm-t320 thread. The snapdragons are in much better shape than the exynos...
joeb690 said:
I flashed the latest image for the German sm t525 model from sammobile. I have performed a factory reset but I thought that when you flashed an image with odin the device is wiped clean? Do you mean CWM recovery you provide in the OP? Thanks for you reply.
Click to expand...
Click to collapse
So I sent my Tab in for repair and all went well, they never mentioned KNOX but this was a private company contracted by Samsung here in Germany to do repairs. Not sure of all the details but its was a hardware failure.
Unfortunately my Tab was "lost" by the courier firm contracted to return my device. In the process of making a claim and will probably receive a new device.
random touchscreen knockout
Hi there,
Just curious: do some more people have random loss of the touchscreen functionality for some seconds or even until a reboot is performed?
Hardware buttons are always fine, though.
I found one post related to this, but no clear answer.
Wiped data and cache but did not install latest nightly yet.
Is that a "known issue something" for build 20141112?
Maybe I should mention that I'm noob level: ultra...
CWMR (Recovery) flash file for ODIN
CWMR (Recovery): (use latest version)
Download: http://download.crpalmer.org/downloads/picassowifi/
* Unzip the .ZIP file and then flash the .tar.md5 that it contains using Odin
Click to expand...
Click to collapse
crpalmer could you pleas upload your flash file again? it's the best way for me because I hate to use the free alternative to ODIN...
EDIT: SORRY SHOULD BE FOR USING WITH SM-T520 DEVICE - DID USE WRONG THREAD!!!
Hi, I just updated to 2.20.40.139 on my stock ROM. Then selected the option encrypt device. Now If I change the theme to any one of the ZENUI theme provided in the system itself I face strange problems mainly on lock screen. The lock screen is now totally blurred,if I have set a PIN or a Pattern I can not see them , thus it is quite problematic to unlock the device. Other problems include laggish animation, distorted image & video in any application including system boot or start up.
Any one facing the same problem.
Any one with a solution ...
please guide me.
I don't have any issues except for installation if xposed. I believe its the encryption.
Sorry that i can't help. One suggestion is to wipe cache and dalvik.
Tiongkia said:
I don't have any issues except for installation if xposed. I believe its the encryption.
Sorry that i can't help. One suggestion is to wipe cache and dalvik.
Click to expand...
Click to collapse
Thanks buddy, I once again reset the mobile now without encryption. It's working fine now with all the themes and personalisation option with background change in phone and dialer also no issue now at boot or start up screen. All animations , image & video all OK.
Thanks again...it was the encryption that caused all those issues.
Very sorry to say that the issue arises again and again.
I applied full 1.12gb ROM wiped Cache partion so many times. When I do so initially it is OK like the problem has been resolved I become happy but sadly after 1 hour or so it's the same issue.
I observed that 2/7 part (Upper part) of the screen is OK while the lower 5/7 part of screen freezes ...it is seen that the last screen was frozen at shut down becomes the first screen after I restart the device. For example as I use 2 layer mode (All apps drawer mode with gride size 5*5 ) the uper 1 row is free from the bug and works as per my wish while lower 4 rows is freezed in bar code style. the same bar code style is seen even in fast boot mode or in recovery mode.
Somebody suggested it might be display / screen related hardware issue......but I wonder how hardware related issue does not affect in some apps like SMS and other apps why does it gets resolved for one hour or so after full firmware updation.
Now i'll try to downgrade to 2.20.40.97 again and see if it reinstate me to earlier bug free device and a happy end user.
I hope some geeks out there might have good suggestion and must help me.
Thanks.
Hey guys,
I have a HTC M9
I am trying to install the Xposed Framework on my Rooted M9 with stock ROM but inside the Xposed app it tells me that it's not installed.
I have TWRP installed.
I rooted my phone with SuperSU v2.65 (After trying a couple of versions that would result in boot loop)
I checked my phones CPU (ARM64) and downloaded "xposed-v86-sdk23-arm64" as well as "XposedInstaller_3.0_alpha4.apk".
I booted into TWRP and Installed the xposed-v86-sdk23-arm64 Framework, it gets to Placing Files and then my phone reboots (I don't know if this is normal or not).
My phone reboots and I open XposedInstaller, under Framework it says "The latest version of Xposed is currently not active, Did you install the Framework and reboot?"
Inside the Framework menu it says "The Xposed Framework is not installed. Please download the latest ZIP file from XDA and flash it manually via reocvery."
The options Install/Update, Uninstall, Recovery (Flash zip automatically) are grayed out.
When I press the Soft Reboot button the phone does restart but no change.
When I try to press the Reboot option I get this error:
Code:
sush: <stdin>[8]: /data/user/0/de.robv.android.xposed.installer/cache/busybox-xposed: not found
Reboot failed please use the device's normal reboot function.
I have restarted the phone normally a couple of times with no change.
I'm new to rooting but I don't find this stuff too difficult to understand, I had a lot of problems trying to get my phone to root in the beginning, I had to try a few SuperSU versions before I could get my phone past boot looping. When I run Root Check it tells me that my phone is Rooted.
I'm not sure what other information I can post to help yous help me but if there's anything you need to know just ask and I'll reply asap.
Cheers guys
I basically want access to Xposed so I can use the FakeGPS and the Hide Mock Location modules.
EDIT (29/07 2:00PM)
I re-downloaded xposed-v86-sdk23-arm64 and tried flashing it again, I read somewhere someone mentioning to clear the caches after the install has finished but when I start the install and it reaches "Placing Files" the phone automatically reboots itself, so I held Volume down and Power to go straight back into Download Mode > Boot Mode > Recovery Mode and cleared the caches, let the phone boot up and still have the exact same problem as the above post.
Seeing as though I haven't gotten any advice yet I am going to try an older version of the Installer app, I have 2 seperate backups of my device so if anything goes wrong I can restore, wish me luck!
I have almost the same problem, with the exception that I don't get to see errors.
I have it rooted with superSU 2.64 (beta) and with TWRP 3.0.2.
Start the flash process using TWRP and after a couple of seconds it just black screens and reboots. Some times it survives and boots, sometimes it doesn't boot.
Since I have backed up my whole system before rooting, I can return back to normal.
The funny thing is, I have managed to install Xposed on the first run, but after restoring a back up, it refuses.
No idea what to do
Wolf_vx said:
I have almost the same problem, with the exception that I don't get to see errors.
I have it rooted with superSU 2.64 (beta) and with TWRP 3.0.2.
Start the flash process using TWRP and after a couple of seconds it just black screens and reboots. Some times it survives and boots, sometimes it doesn't boot.
Since I have backed up my whole system before rooting, I can return back to normal.
The funny thing is, I have managed to install Xposed on the first run, but after restoring a back up, it refuses.
No idea what to do
Click to expand...
Click to collapse
You have described my situation perfectly.
I have a back up I can restore through TWRP if I soft brick it, which at this moment I just did.
I tried flashing the same superSU version again seeing as though it was the only one I could get to work (didn't try your version though) and then installed the latest Framework version right after without rebooting, cleared the two caches and rebooted, I get past the first boot screen, I see my mobile providers boot screen, I then get to the screen with One in big letters and it stops there, I'll try a few more reboots before I restore.
Xposed isn't stable on the m9 and is why I have avoided installing it. Some people get it running first time, no issues. Some people brick their phones. It really is a roll of the dice.
I'd stay away from it if i were you. Htc's can't be easily recovered.
Beamed in by telepathy.
it doesn't brick the phone, but there are a few tutorials with other methods of flashing xposed, should be inside software development of android forum. please try those solutions and please stop creating two threads, with nearly same problem. both things can be asked in one thread, thanks
stock rom has often problems. you need to install busybox to have it working properly
Hey guys,
Need some help troubleshooting what's going on with my Pixel 6 Pro.
Short version:
It's freezing up ~30-60s after booting and unlocking the phone, and then soft-rebooting some time after. If i don't unlock the phone it doesn't reboot. Safe mode also works but with lots of scary errors in logcat.
ROM: Stock, May 2023
Magisk: Yes
Kernel: Kirisakura Ravianth 1.0.5_6
Long version:
I rebooted manually to check something and then shortly after the screen froze up. It rebooted on its own and then it froze again. I then rebooted into safe mode and although it doesn't freeze up in safe mode, there are a lot of errors in the logcat (maybe these are normal for safe mode). Rebooting normally again, it freezes up every time 30-60s after unlocking, but is fine if I don't unlock. I then flashed the stock May 2023 image, without -w, so data was not wiped. I assume this means that Magisk and Kirisakura kernel is gone. The problem is still happening! Yikes!
What should I try? Can I clear data of the system without actually clearing all data on the phone (factory reset)?
We'll get to speculations on what could have caused this after I recover it...
I'm attaching two error level logcats:
1) During regular boot:
--------- beginning of kernel--------- beginning of system2023-06-06 22:35:2 - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
2) During safe mode boot: Freeze_safe_mode_boot.txt
--------- beginning of main--------- beginning of kernel--------- beginning - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
I've never used Pixel 6 (so I'm not completely sure this is available, but I'm fairly certain it is), but you should be able to try loading it in (or have you tried/considered trying?) safe mode...
simplepinoi177 said:
I've never used Pixel 6 (so I'm not completely sure this is available, but I'm fairly certain it is), but you should be able to try loading it in (or have you tried/considered trying?) safe mode...
Click to expand...
Click to collapse
Try loading what in safe mode? Please read the whole post. It's able to boot into safe mode and stays unfrozen but there are still a lot of errors in logcat. I have posted the logs.
Flyview said:
Try loading what in safe mode? Please read the whole post. It's able to boot into safe mode and stays unfrozen but there are still a lot of errors in logcat. I have posted the logs.
Click to expand...
Click to collapse
My apologies...I didn't see/overlooked that you had loaded up in safe mode...
One of the main points of utilizing safe mode is to show/prove that it is Magisk and/or one of its modules that are causing issues. I suggest you either load them up one by one until you replicate the issue and/or remove all traces of Magisk and completely unroot and try flashing Magisk and modules again.
FYI, you state "I'm attaching two error level logcats: 1) During regular boot: Freeze_normal_boot.txt 2) During safe mode boot: Freeze_safe_mode_boot.txt" which I assume are text files, but no such files are attached in the post....thought you should know....
simplepinoi177 said:
My apologies...I didn't see/overlooked that you had loaded up in safe mode...
One of the main points of utilizing safe mode is to show/prove that it is Magisk and/or one of its modules that are causing issues. I suggest you either load them up one by one until you replicate the issue and/or remove all traces of Magisk and completely unroot and try flashing Magisk and modules again.
FYI, you state "I'm attaching two error level logcats: 1) During regular boot: Freeze_normal_boot.txt 2) During safe mode boot: Freeze_safe_mode_boot.txt" which I assume are text files, but no such files are attached in the post....thought you should know....
Click to expand...
Click to collapse
Thanks! The files must have been too big. I edited the post with external links to the logs.
I assumed that flashing the stock May update would un-root and get rid of Magisk. Is that not the case?
Flyview said:
Thanks! The files must have been too big. I edited the post with external links to the logs.
I assumed that flashing the stock May update would un-root and get rid of Magisk. Is that not the case?
Click to expand...
Click to collapse
Not necessarily. It is true that your device is unrooted, but that's only because the init_boot partition is flashed to stock ("May update") -- you merely just can't have "root" access. Magisk still remains in the root directory -- it's how modules and settings remain, even after flashing full factory images (removing -w from flash-all method of course, having -w remain would obviously remove it and wipe all other data to factory reset).
Your whole system has been broken. I would recommend you reflash all new system.
Kris Chen said:
Your whole system has been broken. I would recommend you reflash all new system.
Click to expand...
Click to collapse
How can you tell?
simplepinoi177 said:
Not necessarily. It is true that your device is unrooted, but that's only because the init_boot partition is flashed to stock ("May update") -- you merely just can't have "root" access. Magisk still remains in the root directory -- it's how modules and settings remain, even after flashing full factory images (removing -w from flash-all method of course, having -w remain would obviously remove it and wipe all other data to factory reset).
Click to expand...
Click to collapse
Alright so what should I do? Is this recoverable without wiping all data? When I said I flashed the May update, I meant the entire image as I got it from Pixel Factory images:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Flyview said:
Alright so what should I do? Is this recoverable without wiping all data? When I said I flashed the May update, I meant the entire image as I got it from Pixel Factory images:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Click to expand...
Click to collapse
If you wish to do what Kris Chen suggests (he may have gotten to his conclusion by reading your logs), you could simply flash the Full Factory image that you linked -- you could do it manually or there are multiple tools that can do it for you; you were able to root, so I imagine you already have a method. Try to back up as much as you can.
If you wish to completely unroot, there are guides and methods I imagine.
If I found myself in your situation, this is what I would do...
update every module
a bug may be what's causing glitching and corrected in newer version
disable every module
update/establish Magisk stable version -- this may mean downgrading if on canary or delta
unhide Magisk if hidden
reboot
enable one module and reboot and see if the system loads up correctly
see if can't narrow down if it is a specific module
if that does result in a stable loading system,
it was a buggy module
if that doesn't result in a stable loading of system,
take a photo of installed modules
I would remove/delete the Magisk subdirectory from the root directory
flash the stock init_boot
*I'm sure there are more official, better ways to "remove root"
if that does result in a stable loading of system
install Magisk stable version
patch stock init_boot; flash it
install single module -- rebooting right after each one & confirm system stability before installing next one
maybe Magisk just needed to be intensively re-initialized
if that does not result in a stable loading system
remove Magisk
flash stock init_boot
flash stock kernel
if that does result in stable loading of system
it's your kernel, not Magisk
if that does not result in stable loading of system
lost cause
back everything up
flash Full Factory image with wipe included
Those are just things I, personally, would do -- take it as much as a suggestion as you will (as you probably did many of them already anyways). Good luck to you!
Thanks for the suggestions! I have already flashed the full factory image, but without the "-w" so data was not wiped. The Magisk app itself has remained, yes, but the modules in Magisk don't show up, since there is no longer root. Correct me if I'm wrong, but I don't think the Magisk modules can be causing a problem once the stock boot.img has been flashed as part of flashing the full factory image.
I am seeing some scary things in the logs:
"WM-ForceStopRunnable E The file system on the device is in a bad state. WorkManager cannot access the app's internal data store."
and there are a lot of com.google.android.gms errors as if it doesn't even exist:
"JobScheduler.Component E Job exists for non-existent package: com.google.android.gms"
Flyview said:
Thanks for the suggestions! I have already flashed the full factory image, but without the "-w" so data was not wiped. The Magisk app itself has remained, yes, but the modules in Magisk don't show up, since there is no longer root. Correct me if I'm wrong, but I don't think the Magisk modules can be causing a problem once the stock boot.img has been flashed as part of flashing the full factory image.
I am seeing some scary things in the logs:
"WM-ForceStopRunnable E The file system on the device is in a bad state. WorkManager cannot access the app's internal data store."
and there are a lot of com.google.android.gms errors as if it doesn't even exist:
"JobScheduler.Component E Job exists for non-existent package: com.google.android.gms"
Click to expand...
Click to collapse
I'm unsure, I don't know too much about "safe mode", but I just assume that if it all works in safe mode, it usually means it's a module -- in my experience, rooted users only enter that mode when there's an issue with Magisk and/or its modules.
And in the quintessential rooting guide in the P7P forum (and all his other guides), roirraW "edor" ehT suggests to disable modules before flashing the update (even if you are losing root) -- which I infer that modules can still mess with the system even if you don't have root access....
I'm unsure what else safe-mode disables -- if you research and figure that out, maybe you can narrow down what safe-mode is disabling that is causing your issue. Maybe uninstall the last 5-10 apps/modules you installed (if it's not Magisk related)? I doubt running in safe-mode reverts the kernel as well (so I can't imagine that's proving it), but maybe its the custom kernel (like something the custom kernel is interacting with it doesn't like and causing a glitch)?
I think the best thing would be to backup all your data and do a clean flash.
Rachid.Ala said:
I think the best thing would be to backup all your data and do a clean flash.
Click to expand...
Click to collapse
Yea I'm in the process of doing a backup of the sdcard right now, while I still can, if this turns out to be a hardware issue. I would still very much like to get to the bottom of what happened here so it doesn't happen again! There's two changes I made recently:
1) Disabled Digital Wellbeing with SwiftBackup last night.
2) Installed a magisk module that increased temperature throttling thresholds a few days ago. The phone was not hot at all when this happened, and I had been running it for a few days without issues.
[TEST MOD]Thermal-Throttling-Modifier[Pixel 6/Pro]
/* * Your warranty is now void. * I am not responsible for bricked devices thermonuclear war, or you getting fired because the alarm app failed * Please do some research if you have any concerns about what this MOD does before flashing it *...
forum.xda-developers.com
I doubt either of these is the cause but all thoughts are welcome. Has anyone taken a look at the logs? What other logs should I grab?
Flyview said:
Yea I'm in the process of doing a backup of the sdcard right now, while I still can, if this turns out to be a hardware issue. I would still very much like to get to the bottom of what happened here so it doesn't happen again! There's two changes I made recently:
1) Disabled Digital Wellbeing with SwiftBackup last night.
2) Installed a magisk module that increased temperature throttling thresholds a few days ago. The phone was not hot at all when this happened, and I had been running it for a few days without issues.
[TEST MOD]Thermal-Throttling-Modifier[Pixel 6/Pro]
/* * Your warranty is now void. * I am not responsible for bricked devices thermonuclear war, or you getting fired because the alarm app failed * Please do some research if you have any concerns about what this MOD does before flashing it *...
forum.xda-developers.com
I doubt either of these is the cause but all thoughts are welcome. Has anyone taken a look at the logs? What other logs should I grab?
Click to expand...
Click to collapse
Have you spent time on studying the log what's going on ?
I think most of us is similar as you that we may not understand what's going on but we have ability of doing debug.
- Reflash all system to check whether it's ok.
- Then disable digital wellbeing to check whether it's ok.
- If NG,how about enable it ?
- Next flash magisk module to check whether it's ok.
- If NG,how about removing it ?
I think it's not so hard to find out which one to result in so much error, right ?
Kris Chen said:
Have you spent time on studying the log what's going on ?
I think most of us is similar as you that we may not understand what's going on but we have ability of doing debug.
- Reflash all system to check whether it's ok.
- Then disable digital wellbeing to check whether it's ok.
- If NG,how about enable it ?
- Next flash magisk module to check whether it's ok.
- If NG,how about removing it ?
I think it's not so hard to find out which one to result in so much error, right ?
Click to expand...
Click to collapse
Yes, I've been looking at the logs but I don't know what the problems point to. There are literally thousands of errors.
I have reflashed the entire factory image (so far only without wiping) and am still seeing the freezing and reboots. So clearly something is majorly messed up. Is there any way to only wipe the "system" partition? Or is that a thing of the past?
Flyview said:
Yes, I've been looking at the logs but I don't know what the problems point to. There are literally thousands of errors.
I have reflashed the entire factory image (so far only without wiping) and am still seeing the freezing and reboots. So clearly something is majorly messed up. Is there any way to only wipe the "system" partition? Or is that a thing of the past?
Click to expand...
Click to collapse
I think what @Kris Chen is alluding to is that, while you have flashed the Full Factory image without wiping, you haven't done anything to narrow the issue down (by disabling everything [modules or any other possible conflicting aspect]) and enabling them one by one (sort of how you would find what switch is connected to what socket so you turn all switches off, plug something into each socket, and turn them on one by one) -- you seem to feel very strongly about not flashing to stock and losing all data, but unwilling to do the necessary troubleshooting outside of that method.
But it is unfortunate -- I feel as you do -- that gone are the days of TWRP (at least for the Pixel 7's and/or Android 13 [even Android 12 support is limited]) where you could wipe and re-apply (from a backup) the data & system partition only....
Flyview said:
Yes, I've been looking at the logs but I don't know what the problems point to. There are literally thousands of errors.
I have reflashed the entire factory image (so far only without wiping) and am still seeing the freezing and reboots. So clearly something is majorly messed up. Is there any way to only wipe the "system" partition? Or is that a thing of the past?
Click to expand...
Click to collapse
Well, it seems that you live in the past... Until now, no twrp support for A13.
So you cannot manage to wipe specific partition.
simplepinoi177 said:
I think what @Kris Chen is alluding to is that, while you have flashed the Full Factory image without wiping, you haven't done anything to narrow the issue down (by disabling everything [modules or any other possible conflicting aspect]) and enabling them one by one (sort of how you would find what switch is connected to what socket so you turn all switches off, plug something into each socket, and turn them on one by one) -- you seem to feel very strongly about not flashing to stock and losing all data, but unwilling to do the necessary troubleshooting outside of that method.
But it is unfortunate -- I feel as you do -- that gone are the days of TWRP (at least for the Pixel 7's and/or Android 13 [even Android 12 support is limited]) where you could wipe and re-apply (from a backup) the data & system partition only....
Click to expand...
Click to collapse
Yes!
Until now, no TWRP support for A13.
I don't know if this will help -- especially with consideration of not wiping the device (don't know with this tool as I've never used it before); I have a small bit of experience using the Android Flash Tool, I imagine this is similar to that -- but I have just recently been made aware of this tool (url below)...maybe it might help where things did not manually with you; might have a better chance as it is an official Google tool....
Google Pixel - Update and Software Repair
With this or anything else, good luck!
simplepinoi177 said:
I don't know if this will help -- especially with consideration of not wiping the device (don't know with this tool as I've never used it before); I have a small bit of experience using the Android Flash Tool, I imagine this is similar to that -- but I have just recently been made aware of this tool (url below)...maybe it might help where things did not manually with you; might have a better chance as it is an official Google tool....
Google Pixel - Update and Software Repair
With this or anything else, good luck!
Click to expand...
Click to collapse
Interesting! I might give that a shot but I have an
UPDATE:
I was up until 4AMtrying different things and somehow got it working again!?
Earlier, before reflashing the factory image, I had opened up Magisk and seen that my 2 modules, the "AK3 Helper Module", which is part of the Kirisakura Kernel, and the throttling mod were disabled. At this same time, I tapped on the delete icon for the throttling mod, which put a line through it. I didn't think about this at the time but perhaps it would have to get removed on the next boot? After this I flashed the factory image, which removed Magisk root, but possibly left that module installed?
After this, I could no longer see the modules as Magisk root was technically gone and only the app remained.
Around 3AM I reflashed the magisk rooted boot.img that I still had thinking that maybe I would see the modules again and check that it had been uninstalled. It still froze up after booting and unlocking, but I was able to check the modules and both AK3 Helper Module and the thermal throttling mod was gone. I figured re-flashing Magisk did nothing since it still froze, so I went back into safe mode. After some more time trying different things in safe mode, I rebooted normally again all of a sudden it was fine!?
So now I'm confused. Could it have been the thermal throttling mod, which needed Magisk to be there to get completely uninstalled? And that only happened once I flashed Magisk back and also rebooted again? I'd really like to get to the bottom of this! I suppose it could have been the thermal throttling mod causing the phone to somehow overheat, before CleanSlate was able to apply the battery saver which reduces the CPU frequencies. Perhaps I had never rebooted since applying the thermal throttling mod a few days ago, it's hard to remember now. I had been meaning to do this before, but now I'm going to take a look at exactly what values are changed with this mod I installed, comparing it to the stock file, and see what if anything could have been dangerous, and rewrite it.
Flyview said:
Interesting! I might give that a shot but I have an
UPDATE:
I was up until 4AMtrying different things and somehow got it working again!?
Earlier, before reflashing the factory image, I had opened up Magisk and seen that my 2 modules, the "AK3 Helper Module", which is part of the Kirisakura Kernel, and the throttling mod were disabled. At this same time, I tapped on the delete icon for the throttling mod, which put a line through it. I didn't think about this at the time but perhaps it would have to get removed on the next boot? After this I flashed the factory image, which removed Magisk root, but possibly left that module installed?
After this, I could no longer see the modules as Magisk root was technically gone and only the app remained.
Around 3AM I reflashed the magisk rooted boot.img that I still had thinking that maybe I would see the modules again and check that it had been uninstalled. It still froze up after booting and unlocking, but I was able to check the modules and both AK3 Helper Module and the thermal throttling mod was gone. I figured re-flashing Magisk did nothing since it still froze, so I went back into safe mode. After some more time trying different things in safe mode, I rebooted normally again all of a sudden it was fine!?
So now I'm confused. Could it have been the thermal throttling mod, which needed Magisk to be there to get completely uninstalled? And that only happened once I flashed Magisk back and also rebooted again? I'd really like to get to the bottom of this! I suppose it could have been the thermal throttling mod causing the phone to somehow overheat, before CleanSlate was able to apply the battery saver which reduces the CPU frequencies. Perhaps I had never rebooted since applying the thermal throttling mod a few days ago, it's hard to remember now. I had been meaning to do this before, but now I'm going to take a look at exactly what values are changed with this mod I installed, comparing it to the stock file, and see what if anything could have been dangerous, and rewrite it.
Click to expand...
Click to collapse
Curious/Interesting.... I always assumed clicking on the trash icon and rebooting simply but effectively uninstalled the module. But it's also why I stated that you should remove each module and reboot after each time....*very important the rebooting
I imagine somewhere between this
so I went back into safe mode. After some more time trying different things in safe mode
Click to expand...
Click to collapse
may be what corrected what was causing it to glitch...? That or, again, getting the module properly/completely removed or re-initialized properly corrected it -- we told you that it was most likely the modules; when things run smoothly in safe-mode, it's usually the culprit...
Tweaking with frequencies & thermal often end up with random glitches -- from my very limited experience of overclocking my CPU and GPU, the way to go about it is to tweak those things until just riiight about the system doing random reboots....It's easy to imagine this all being a symptom of such things...it's why I suggested even going back to stock kernel after removing all Magisk & modules....
Glad you stabilized your device though!