Develop Bugs

[Q] Rooted Device Unusable After A Toddler Accident

My Device Info:
Rooted, AT&T Galaxy Note 2 running 4.1.2...no custom ROMs, kernals, tweaks or mods, etc...
The Issue:
I've been ignoring the latest OTA update that AT&T has been pushing since my device is rooted. However, unbeknownst to me at the time, my phone got into my toddlers hands last night and I'm assuming he accidentally pressed something that caused the download process to begin.
What I've Tried So Far:
The phone will boot up like normal, but when I try to select anything then the screen goes black showing nothing but the notification bar. Then after a few seconds the phone auto-reboots itself. Sometimes it hangs on the Samsung splash screen while I hear notifications going off in the background. From recovery, I've selected to wipe data/factory reset and wipe Dalvik cache, but no change. I had one Clockwork mod backup on my extSDcard that won't restore giving me and MD5 mismatch error. It was only from a couple weeks ago so it was created from this device. I'm a relatively seasoned Android OS tweaker but its been a while since I've been actively doing anything but rooting. I need some suggestions as to how I should proceed....thanks in advance

Momomuffins said:
My Device Info:
Rooted, AT&T Galaxy Note 2 running 4.1.2...no custom ROMs, kernals, tweaks or mods, etc...
The Issue:
I've been ignoring the latest OTA update that AT&T has been pushing since my device is rooted. However, unbeknownst to me at the time, my phone got into my toddlers hands last night and I'm assuming he accidentally pressed something that caused the download process to begin.
What I've Tried So Far:
The phone will boot up like normal, but when I try to select anything then the screen goes black showing nothing but the notification bar. Then after a few seconds the phone auto-reboots itself. Sometimes it hangs on the Samsung splash screen while I hear notifications going off in the background. From recovery, I've selected to wipe data/factory reset and wipe Dalvik cache, but no change. I had one Clockwork mod backup on my extSDcard that won't restore giving me and MD5 mismatch error. It was only from a couple weeks ago so it was created from this device. I'm a relatively seasoned Android OS tweaker but its been a while since I've been actively doing anything but rooting. I need some suggestions as to how I should proceed....thanks in advance
Click to expand...
Click to collapse
In Settings/About Device: you can tell which build you have or if you had the update or not. The phone was prolly shipped with MA4..or MC3. The newer update was MH3.
I don't know if updating if would cause that issue though.
Mebby it's something that the toddlers did or coincidental hardware issue.
You might need a reset from in the device..under Setting/Backup Reset..this may erase all you data and info on the SDCard
If you are still having issues...mebby an Odin back to stock MA4 and test again

qkster said:
In Settings/About Device: you can tell which build you have or if you had the update or not. The phone was prolly shipped with MA4..or MC3. The newer update was MH3.
I don't know if updating if would cause that issue though.
Mebby it's something that the toddlers did or coincidental hardware issue.
You might need a reset from in the device..under Setting/Backup Reset..this may erase all you data and info on the SDCard
If you are still having issues...mebby an Odin back to stock MA4 and test again
Click to expand...
Click to collapse
Once the phone boots and the pre-home screen displays ready to swipe. Once I swipe, like I'm trying to access the home screen, the entire display goes black except the status/notification bar. If I power off the screen and back on again, the swipe screen displays again, swipe it again, it goes black again. The status bar, volume selection pop-up display on the screen are responsive and functional. I just can't navigate through the phone whatsoever past the swipe screen. It's like the home screen UI/launcher doesn't exit. Previous to the problem, I was running Smart Launcher Pro with no problems....this is by far the weirdest issue I've ever run across

Momomuffins said:
Once the phone boots and the prOute-home screen displays ready to swipe. Once I swipe, like I'm trying to access the home screen, the entire display goes black except the status/notification bar. If I power off the screen and back on again, the swipe screen displays again, swipe it again, it goes black again. The status bar, volume selection pop-up display on the screen are responsive and functional. I just can't navigate through the phone whatsoever past the swipe screen. It's like the home screen UI/launcher doesn't exit. Previous to the problem, I was running Smart Launcher Pro with no problems....this is by far the weirdest issue I've ever run across
Click to expand...
Click to collapse
It could be a launcher issue.. perhaps an inverted color scheme
Flash a different launcher or rom in cwm..or odin to stock
Or push a different launcher then install and reinstall your own

qkster said:
It could be a launcher issue.. perhaps an inverted color scheme
Flash a different launcher or rom in cwm..or odin to stock
Or push a different launcher then install and reinstall your own
Click to expand...
Click to collapse
Just did Odin to Stock...successful...BUT the phone booted up and I have the "Android is upgrading...<starting apps.>" box...its been sitting there for at good 15min+...

Also...once the screen went black earlier the phone would reboot even after wiping it clean of absolutely everything...something somewhere got seriosuly borked...

Momomuffins said:
Just did Odin to Stock...successful...BUT the phone booted up and I have the "Android is upgrading...<starting apps.>" box...its been sitting there for at good 15min+...
Click to expand...
Click to collapse
***UPDATE***
Pulled the battery and booted into stock recovery....wiped data/factory reset/wipe cache...reboot...I was able to nav further into the UI than I was previously able to like into the SMS app and system settings then BAM...auto-reboot again and the famous "Android is upgrading..." box is back...sitting there...again...this is insanity...it's no longer rooted, stock firmware, no data aside what's generated during the initial device set-up... SAME shiz as far as the reboot and the spontaneous, hanging OTA upgrade...

Horizontal Pixel lines just before OS launch

Dear xda--developers members,
I have attached a photo for preview
I have upload a view on youtube (the link is in the attached txt file because I am a new user so I can't add links directly), the title:
"Samsung Hercules (SGH-T989) Horizontal Pixel Lines on Screen "
I have been experiencing the following issue, since two days my Hercules (Samsung Galaxy SII SGH-T989), restarted spontaneously and when it reloaded until the samsung logo,the welcome screen was totally fine just until the systems actually starts; horizontal pixel lines start to appear then they persist for ever and the lines keep changing while the system doesn't load, the confusing thing is that the screen works totally fine before this stage and I have worked within TWRP and CWM for hours and the screen is totally fine and it's able to show the welcome animation just fine, I have tried everything I know to resolve the issue I have done factory reset, reflashed the two original stock roms using odin/or TWRP & CWM and these didn't work.
Then I tried the available custom ROMs such as CM and when the installation is successful and I turn on the device after reboot the first Samsung logo appears then the device turns off, I have of course done the wiping part of the cache and the davlik to not avail. Then I thought the issue is maybe due to something on the internal sdcard so I formatted it after backup. I don't have ext. sdcard.
Now I don't know if there's something wrong with hardware, and I can't imagine this conclusion since the screen totally works fine unless the actual android is loading, but maybe it's a possibility.
Guys do you have any solutions? I am really

[Q&A] [SM-T525] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 10.1 LTE (picassolte)

[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!!!

File based encryption or Full Disk encryption

I flashed Nougat's factory image on my 5x a week ago. After playing for a while i noticed the encryption change option in 'Developer Options'.
Also, read that new devices will be coming with File based encryption since it allows direct boot mode.
Is there any performance difference if change the encryption to 'File based' ? I read few user reviews and they were saying that changing encryption to file based did improved little performance.

I'm also interested in this. So bump for a more knowledgeable member to comment.

I think this thread proved pretty conclusively that there is no real world performance benefit in decrypting.
I activated file encryption on my N5X, specifically to allow for direct boot. I had N with full disk encryption on my N5X for about 72 hours before switching. I see no performance difference -- it was smooth before, and it is smooth now.

rockhardy said:
I flashed Nougat's factory image on my 5x a week ago. After playing for a while i noticed the encryption change option in 'Developer Options'.
Also, read that new devices will be coming with File based encryption since it allows direct boot mode.
Is there any performance difference if change the encryption to 'File based' ? I read few user reviews and they were saying that changing encryption to file based did improved little performance.
Click to expand...
Click to collapse
I doubt there is noticeable performance difference.
The main benefit is if your phone reboots in your backpack, it'll boot to the lock screen instead of being stuck asking you for your pattern/pin/password and basically being a useless phone if you don't notice it rebooted.
If you don't have the phone configured to act that way, then it probably isn't of real benefit, currently. There may be additional benefits later on or perhaps with the workplace contexts.

sfhub said:
I doubt there is noticeable performance difference.
The main benefit is if your phone reboots in your backpack, it'll boot to the lock screen instead of being stuck asking you for your pattern/pin/password and basically being a useless phone if you don't notice it rebooted.
If you don't have the phone configured to act that way, then it probably isn't of real benefit, currently. There may be additional benefits later on or perhaps with the workplace contexts.
Click to expand...
Click to collapse
Thanks for your comment.
In that case i think i will be switching to File-based encryption to enjoy direct boot feature.

sfhub said:
I doubt there is noticeable performance difference.
The main benefit is if your phone reboots in your backpack, it'll boot to the lock screen instead of being stuck asking you for your pattern/pin/password and basically being a useless phone if you don't notice it rebooted.
If you don't have the phone configured to act that way, then it probably isn't of real benefit, currently. There may be additional benefits later on or perhaps with the workplace contexts.
Click to expand...
Click to collapse
Hey but can you tell me why the phone reboots in pocket ?
My phone also reboots in midnight when I set a fingerprint on it .
So will decryption solve this issue ?
Thanks in advanced

ABSathe said:
Hey but can you tell me why the phone reboots in pocket ?
My phone also reboots in midnight when I set a fingerprint on it .
So will decryption solve this issue ?
Thanks in advanced
Click to expand...
Click to collapse
My phone never reboots, but some people have set ups that do. It is usually some bug in Android that is triggered by some software you are running or there is some data corruption in your system.
First thing to try would be booting in "safe mode"
https://support.google.com/nexus/answer/2852139?hl=en
If the reboots stop, then it is some app you are running.
If that doesn't narrow it down, try factory reset, then install under new android account, install a couple of apps at a time, until you see reboot. If it reboots right away on fresh install on new account, then you might have hardware issue.
I seriously doubt decrypting your user partition will help with your reboots, but you are welcome to try. If it does help, it will probably be coincidence because you had to format user partition to decrypt your phone which is equivalent of factory reset.

sfhub said:
My phone never reboots, but some people have set ups that do. It is usually some bug in Android that is triggered by some software you are running or there is some data corruption in your system.
First thing to try would be booting in "safe mode"
https://support.google.com/nexus/answer/2852139?hl=en
If the reboots stop, then it is some app you are running.
If that doesn't narrow it down, try factory reset, then install under new android account, install a couple of apps at a time, until you see reboot. If it reboots right away on fresh install on new account, then you might have hardware issue.
I seriously doubt decrypting your user partition will help with your reboots, but you are welcome to try.
Click to expand...
Click to collapse
Actually this issue is there from the first day I started using my phone .. but booting in safe mode does not give any reboots so far and also fingerprint is working nicely too
So I guess I will try factory reset .. can I do it using the option already present in settings ? Or should I flash a factory image ?
Thanks

ABSathe said:
Actually this issue is there from the first day I started using my phone .. but booting in safe mode does not give any reboots so far and also fingerprint is working nicely too
So I guess I will try factory reset .. can I do it using the option already present in settings ? Or should I flash a factory image ?
Thanks
Click to expand...
Click to collapse
Before you do factory reset, I suggest you get rid of any pin/pattern/password you might have configured. This will disable the factory reset protection, just to be on safe side.
You can do it from android.
If you say this problem was there from beginning, then it probably migrated over from existing account restoration of apps. You might want to try installing onto a new google account to test that theory out. The install a couple of apps at a time while verifying everything remains stable.

Hi,
Do folks think that switching to File Based Encryption might help avoid this issue - a decryption failure on reboot with Factory Reset the only solution? My phone is 13 months old and now out of warranty and this has happened 5 times to date - once about 6 months ago, once about 3 months ago and then worryingly 3 times in the last month. Stock unmodified on 7.1.1

Hey, When will TWRP support this? I've been waiting for ages.....

Possible fix for random bootloops (after rooting and installing gapps)

Sometimes my rooted Nokia X likes to do a bootloop after it discharged.
After checking out logcat logs I've noticed that file
Code:
/data/system/notifications.db
is broken. When I've removed it (with cached version), system started booting properly again.
The only side effect is cleaned up Fastlane menu, but I think this quick fix will be useful before trying full data wipe when phone catches bootloop.

I have never these type of problem. Wait for other developers or search google for these type of problem for other android phones.

BluRaf said:
Sometimes my rooted Nokia X likes to do a bootloop after it discharged.
After checking out logcat logs I've noticed that file
Code:
/data/system/notifications.db
is broken. When I've removed it (with cached version), system started booting properly again.
The only side effect is cleaned up Fastlane menu, but I think this quick fix will be useful before trying full data wipe when phone catches bootloop.
Click to expand...
Click to collapse
I also has that problem on stock..
sometimes when the phone discharges to zero , it goes into bootloop

like you known the stock rom are odex some no odex file will cause bug i have a way to de-odex your rom but you need to follow all what i am going to tell you in pv message