Develop Bugs

My Tab 8 pro lte T325 keeps restarting

When I start an app - doesnt matter which, my tab restarts. Not all of the time, but many times. This started a month or so ago. Does anybody know a cure? Thanks

original or custom rom? Tried resetting to defaults?

Originaliteit or custom ROM? Its the original ROM andere have reset my T325 tot default. No succes

have you ever tried to root it or use another rom before (or was it used)? it could be a tripped knox issue, usually that causes the tablet to reboot when the knox check fails...
if not then perhaps somehow the system files got corrupted and you might just want to completely re-flash the whole stock firmware with odin or kies

Knox could be the problem. I have not rooted this tab. But i have knox disabled. Should i turn it on? Its for me such a useless app.

if you have never rooted then knox is unlikely the problem, you can try to re-enable the app though see if it helps..
-if you still get reboots I suggest doing a factory reset , then boot into download mode and re-flash the whole device using the latest firmware
In my testing there is only a few things that can make the tablet reboot and that is
1. a kernel panic similar to linux (maybe a bug in a filesystem driver ..etc)
2. knox
3. overheating when the cpu is at 100-105c it can make the tablet shut down or reboot

i have been thin king and i guess it has to do with the battery. Until the last update my T325 had loadin g troubles. I think that this also has to do with the same problem. Next week i will visit the samsung service store and see what they can do for me. If that doesnt work will i start thinking about rooting and perhaps another rom. Sometimes i wish i never bought this tab. My former (rooted) P1000 never gave troubles!

As good as the P1000 was, I don't miss mine over the Tab PRO, for starters LTE is sweet. Secondly the +1.5 (i.e. 2GBs), of RAM make for a much more pleasant experience. About the only thing the P1000 has or had going for it was some support. Likely do to the fact that it was Samy's first Phablet.

Accidentally Botched SW3 Firmware by Flashing TWRP

When I got my SW3 last summer, I stupidly ignored all those warnings about flashing TWRP to recovery, mostly because I didn't see what harm could come of it. However, while investigating a battery drain that's persisted despite multiple flashes to stock and more than a few attempts to use crpalmer's LCA43 kernel, I discovered via my SW3's kernel log that it's got some serious weirdness going on with its firmware.
As it turns out, it's reloading the pedometer firmware every three seconds. This happens because every time it loads the firmware, it promptly encounters some manner of error while running it, which then prompts Android to try to reload the firmware. My first hint that this was a firmware issue came from the fact that I can't access any sensor data via the developer menu. Under 'Manufacturer: Menu-Launcher' at the bottom of Developer Options, the entries for Accelerometer, Gyro, Magnetometer, and Compass are all blank, while Ambient Light Sensor and Step Counter are perpetually stuck at 0.0.
After trying everything I could think of in my attempts to fix this issue, I then began investigating other variations from stock that I'd had over the months that I've had my SW3. Rooting didn't appear to change anything related to the firmware, and crpalmer's LCA43 kernel (and craigcharlie's simple MTP mod and, later on, alex6600's modified version of the kernel itself) didn't appear to cause any of the issues I'd been experiencing for anyone else. Finally, I found a comment somewhere about the fact that flashing TWRP to recovery instead of just booting it would really mess things up because it uses a device tree different from the SW3's stock device tree.
Since then, I've been trying everything I can imagine to fix this, but I haven't had any success thus far. Because of that and a few other reasons, I haven't been able to mess with this since the end of January, but I'm really getting tired of my SW3 only lasting for about 6-8 hours with pretty minimal use. I think the closest I got to any sort of progress was using dd to individually flash partitions that'd been uploaded, but I don't think I was ever able to find an upload of mmcblk0p19, dt-blob.
Does anyone have any ideas about what I might be able to do to fix this? Specifically, I'm curious to know whether or not dding partitions damaged when I flashed TWRP should work; if so, would someone be so kind as to either post or PM me dded copies of the relevant partitions? Thanks in advance for the help!

Repair with PCCompanion. Did that some weeks ago. Version is LCA43.

If pc companion does not work (and it probably wont), hold down the button on boot, and you can force it to usb mode. If that does not work, hit the button twice to go to fastboot and flash the original OS (look for the repair threads).
Good luck.
Sent from my SM-T810 using Tapatalk

Sprint Galaxy Note 4 Android 6.0.1 problems

I'll try this again (this website crashed when first posting this)
Leased phone (January 2017) use for my business. Has had (3) OTA updates since April. Started having issues after 3rd update mid-June (freezes / reboots). Most times have to pull the battery to get it to boot. Have wiped & restore several times, from Settings and Recovery boot menu. Cleared App cache and partition cache. Had the local Sprint Store 'supposedly' flash the OS from a PC but nothing improved. Described these issues below but was only met with a blank stare and an offer to open my wallet to replace with a refurbished phone without knowing what is causing the issue.
On some occasions when the device is not responding it heats up. Messages of Apps that stop responding include System UI, Package Access Helper, Touchwiz and Gmail, among others.
When going to Boot recovery menu to try clearing the partition cache the Android Icon shows up with the message 'Installing system update', which it's clearly not doing. Sometimes that's followed by the icon laying down and the message 'No command'. Does this mean the update didn't properly install? Another message I've noticed once the menu comes up is 'dm-verity verification failed . . . '
Further trying to diagnose, Sprint Zone / Device Diagnostics / Flagged / System Updates - always states 'Update now', but Settings / System Update / Software update message reads 'The latest updates have already been installed (N910PVPS4DPE2 / N910PSPT4DPE2 / N910PVPS4DPE2).
Investigated alternatives with Samsung (they replied the same day, Sprint Community message July 20th still hasn't replied) I can take it to a service center to have the hardware checked for a fee but it is not nearby and I'd like to first understand what the issue is.
From what I've described does anyone know what could be causing these issues? I have read where some updates were causing problems but I've tried most of those remedies and nothing has helped yet. Perhaps the Sprint Store, in an effort to extract more money (this is how it seemed) did not or was not able to flash the OS?
Any help would be greatly appreciated.

best thing to do is odin back to an older version and retake the update if you wanna go thru that again
but id recommend reverting back to OG5 and then flashing a rom you will have less reboots....as least on my end i did

JLFitzpatrick said:
...When going to Boot recovery menu to try clearing the partition cache the Android Icon shows up with the message 'Installing system update', which it's clearly not doing. Sometimes that's followed by the icon laying down and the message 'No command'. Does this mean the update didn't properly install? Another message I've noticed once the menu comes up is 'dm-verity verification failed . . . '...
Click to expand...
Click to collapse
The stock recovery you describe, it's normal for the Android guy to fall down and display the red x or whatever you saw when there's no update to apply but the dm-verity failure isn't normal. It could indicate bad repair or maybe it was rooted at some point? Wiping and Odin flash doesn't always rid the phone of that but Knox trip remains always until Samsung repairs a rooted phone. Dunno the cause of your dm-verity failure but maybe, if it was stock un-rooted all along, it may a read only partition failed or corrupted?
As suggested above, you may fix the dm-verity by taking a couple of OTA updates after Odin flashing an older one. Don't go back any older than OG5 though.
I think the problem may also stem from old data from Lollipop not getting wiped. I'd recommend disabling the reactivation lock on Settings/Security, remove your accounts from phone, a factory reset within Settings, boot to recovery and factory reset and wipe dalvik and cache in stock recovery and power off. Reboot to download mode and flash an older stock tar and let it OTA a couple of times.
That may solve some issues but it could be hardware failure or a corrupt partition. If the dm-verity goes away, see if your problems are resolved. If you didn't root and have a warranty, make whoever warrants it replace it; the failure is legit.
Sprint Zone and ItsOn is garbage IMO. Bloat that kills the experience that Samsung intended. Albeit, Samsung isn't so innocent with bloat ruining the experience either. Just my opinion on the bloat. By the time users add their own bloat, there's but enough RAM and with all the services running, battery takes a hit and phone lags. Run package disabler (search in Google Play) or root to manage it is what I'd suggest. FWIW, I have no random reboots or phone heating up while in standby running Marshmallow. My phone sleeps like a baby.
If no warranty applies and root is an option, you could try rooting with Chainfire Auto Root for Note 4 and then full un-root. The developer removes the dm-verity flag if it's there for modified read only partition reasons. But of coarse that also trips Knox warranty bit, so be aware. Dm-verity can prevent OTA's from updating but that's an alternative with root and Knox trip risks. No warranty should mean less risk unless the phone belongs to your employer.
Sent from my SM-N910P using Tapatalk

Thank you for your replies.
I had pointed out the 'dm-verity verification failure' text to the goof-offs at the Sprint Store, you'd think I was speaking in a foreign tongue. Phone is leased on our personal family plan and used for my business. I've never rooted it myself, not sure what the Sprint people did at the store but that text was there before they supposedly flashed the OS.
I apologize but am in over my head with the suggested repairs. Although having upgraded PC's am familiar with the process; revert to previous clean OS and upgrade over that. I'll take your suggestions and just have to study a little more to understand the correct procedure.
Yesterday afternoon I tried the folks at Samsung again since their support team had replied the same day before (still waiting for a support response from Sprint since July 20th) and went to a live support chat. The woman was very helpful but unfortunately, I had to jump off for a meeting. Before I jumped off she had me put the phone into Safe Mode. I had tried to get there before but the instructions I was given were incorrect (not found in recovery boot). It has since been in that mode and has been much more stable, still freezes occasionally but doesn't reboot itself and runs zippy as hell except for momentary freezes. I have the Chat ID # and will try again today to see what they can do before trying other suggestions. I gave them the HEX DEC numbers and it sounded like they could access the phone with those, this morning their Chat was full so I'll have to try later.
samep, if you don't mind can you give me some clarification on your suggestion:
"I think the problem may also stem from old data from Lollipop not getting wiped. I'd recommend disabling the reactivation lock on Settings/Security, remove your accounts from phone, a factory reset within Settings, boot to recovery and factory reset and wipe dalvik and cache in stock recovery and power off. Reboot to download mode and flash an older stock tar and let it OTA a couple of times."​
My interpretation:
Settings / Security / disable reactivation lock
Remove accounts (first back up phone log & sms to samsung account, back up wifi passwords to google account)
Settings / Backup and reset / Factory data reset
Boot to recovery menu / factory reset again (partition and dalvik cache evidently get cleared through reset)
Boot to recovery menu / 'flash an older tar' ? (Is this 'Apply update from ADB (Odin)' or SD card? This is where things get fuzzy. Can I load the stock tar (OS?) to a formatted sd card and apply the update from there or do I have to install Odin on a PC? Where is the best place to get a 'stock tar' (or Odin) from and which version(s) should I use for a Note 4, or is that explained on a particular website. There are many sources of information on Odin and firmware but I'm not sure which to trust if I need to do this would prefer to do this just once.)
Thank you again for your help, and I apologize for my ignorance on this subject.
But the best thing about ignorance is that it can be overcome with a little effort and knowledge.

To answer the question, boot into download mode from powered down state by holding volume down, menu and power. Yes, you use Odin installed on PC for that. But first you need the Samsung USB driver and Odin installed, plus the stock tar.
This thread will get you going with resources and brief instructions.
http://forum.xda-developers.com/showpost.php?p=63868221&postcount=1
I'd suggest PC1 stock tar, then let it OTA.
(Your interpretation was mostly right up to the question about how to flash the tar after the factory reset and power down.)
Sent from my SM-N910P using Tapatalk

Thank you samep,
Understanding the tar file versions are listed alpha-numeric the oldest version is PD1 so I will start with that version.
Have downloaded Odin and all three tar files (in case of any issues with PD1). Samsung Chat referred me to bring the phone in, after reviewing information on using Odin will try your suggested method first and then check for dm-verity failure.
Another tar file resource found is updato-dot-com (as a newbie unable to post link):

JLFitzpatrick said:
Thank you samep,
Understanding the tar file versions are listed alpha-numeric the oldest version is PD1 so I will start with that version.
Have downloaded Odin and all three tar files (in case of any issues with PD1). Samsung Chat referred me to bring the phone in, after reviewing information on using Odin will try your suggested method first and then check for dm-verity failure.
Another tar file resource found is updato-dot-com (as a newbie unable to post link):
Click to expand...
Click to collapse
If you're feeling overwhelmed, you could bring it in. There's a chance it is hardware and the steps may prove redundant.
Up to you. At least you have something to point to as an issue.
Sent from my SM-N910P using Tapatalk

So I've gone through all the steps, phone is wiped, reinstalled Samsung USB Driver, have Odin open as Administrator and the phone in 'Android Recovery', Phone does not show up in Odin.
Have seen a couple versions of setting a connection (Odin open first, phone connected first); tried all of those and tried Odin open not as administrator. There is no connection. Tried other instructions to put into Developer Mode and enable USB bugging. Nothing, disabled USB bugging and booted back to recovery. Still nothing.
In Recovery mode it does not state 'Odin mode'. Tried the Recovery menu option 'Apply update from ADB' message reads 'Update from external storage diabled'. Tried 'Reboot to bootloader' (WTH), that does show Odin Mode at top of screen but phone still does not show up in Odin on PC. Then have to pull battery to reboot to Recovery mode. What steps am I missing here?
When phone is booted up normally it connects to PC without issue.

Finally got Odin to recognize the phone. Through a few searches I tried one remedy that suggested manually updating the samsung usb drivers in device manager which did the trick. Realized earlier that from recovery mode you do need to select boot to bootloader to get into Odin mode (listed on top).
Installed 6.0.1 - PD1 currently phone is installing OTA updates, hopefully this does the trick. Thanks again for your help.

On Tuesday the phone updated OTA from PD1 (April 27, 2016) installed via Odin to PE1 (June 1, 2016) then PE2 (June 29, 2016). Recovery Mode screen no longer shows dm-verity failure message so that's fixed. Phone is mostly stable, however still not as stable as it was on PE1 from what I recall by the release dates. Phone still freezes although it usually does not crash if I leave it alone but still does crash at least once a day. Safe Mode does not help, as the worst culprits are system Apps (Gmail, Drive are the worst).
It seldom overheats now but did yesterday. 3rd Party CPU cooler found Package Access Helper, Context Service and System UI as causing an issue. Cleared App Cache for all three but problems persist. Clearing App Cache in Settings / Storage takes at least three tries to clear all but 4.00 KB. I have been clearing Partition Cache every morning just to get through most of the day otherwise it will freeze when I first start to use it. Battery is also draining faster than before.
Any suggestions? OTA updates were at work on a stable WiFi signal. I'm thinking of Odin flashing back to PE1 (or PD1) and stopping further OTA updates. Anybody tried this? Will be traveling for a couple of weeks and need a stable phone, like I used to have. Thank you.

Samsung has been having memory management issues. IMO, this is the reason they keep increasing RAM in recent phones and getting help from Google. But 3 gigs of RAM should be sufficient.
A custom ROM may resolve that but you could try a package disabler from Google Play to freeze some unneeded bloat.
I couldn't say which stock version is best because I've ran all of them without random reboots and lag is minimum. The custom ROMs have been daily driver stable for me. I use them when traveling too.
Sending PM to OP as well with additional info.
Sent from my SM-N910P using Tapatalk

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

Need help to install LineageOS 18.1 In Motorola Moto G7 play (Channel)

Hello, first of all I want to apologize for any grammatical mistake since I do not speak English and this text was translated through a web page. Let's start, for a long time I came with emotions to try custom roms on my device (motorola moto g7 play ((XT1952-2)), I decided to try the lineageOs and to my surprise I managed to make it work, but I did not have the Gapps so I wore To investigate to install them, after investigating, I tried to install them but everything went wrong, very bad, the cell phone had been soft bricked and I was about 5 hours trying to solve it since the bootloader had been blocked and there was no way to install ANYTHING, After solving it, I found that I cannot install LineageOS in any way, I spent about 4 hours testing and it always throws me an error and this affects the entire device since I have to use the Motorola assistant on every failed occasion ( Rescue and Smart Assistant), I attach one of the problems that I get when trying to install the OS. I hope a prompt solution, thank you very much
Instalando archivo zip
Buscando archivo digest...
Step 1/2
Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)
Proceso Updater terminó con ERROR : 1
Error instalando archivo zip
Actualizando detalles de la particion
I tried in all the ways I could but did not reach any solution, I only use the stock motorola firmware, but the fact of installing a custom rom rejects it anyway.

I will keep this simple and short but what did you use to flash Lineage, before the Gapps problem? What it sounds is your problem is one of two things, 1) are you wiping data partitions after each flash cause it will boot loop if you don't, and that leads to it then trying to switch to the other partition slot, and it still may see data (encryption) exists and from the stock rom, so it constantly reboots and trust the inactive slot the next time and on it goes. Check postings about booting twrp, flashing the rom, then boot twrp again, then wipe data and install Gapps. That should solve the problem. Oh, if you get stock running again and fix the boot loop, I recommend a full twrp backup to a safe place (external sd) to restore from. All this before the initial Lineage flash is best. This big thing is remember these phones have two slots, running the live instance in one slots, the other laying dormant for updates. When flashing Lineage twrp tells you the slot letter it's flashing too. After, always check for the slot when flashing Gapps, magisk. If not, you got switched up