Database Info

Partial Factory Resets?

So the past 2 days I've had an interesting problem, with even more interesting results.
Both mornings I've tried to use my GPS and it just hangs on trying to connect to it. The GPS says it's on, and I can toggle it off and back on again but it never finds any sats.
Yesterday I reboot the phone and it takes a while to boot the phone back up (most like the first time you boot after a fresh install), and when the phone came back online the GPS worked but all my bluetooth pairings were gone.
Today I have the same GPS problem so I reboot again, and again it takes a while to boot and so far I still have my bluetooth pairings, but I've been unable to connect to the devices, all my sound settings are back to the defaults, when I hold down the power button now the only option I have is Power Off, nothing else, when my screen times out and I hit power to bring it back on it goes right back to wherever I was, I don't see the lock screen anymore. And to top it all off my home button and my search button do not work.
What a mess, this phone is getting worse by the day, I'm actually starting to regret the purchase. I guess it's time to call it in and see what they say.
Edit: Forgot to add all my SMS messages were deleted as well.

Rooted? Have you done anything to it? That's definitely not normal but I guess you know that

Ya it's rooted and has nvflashed clockworkmod recovery installed. Rooted the day I got the phone and clockworkmod recovery has been installed for about a week.
I just tried clearing the cache partition, wiping Dalvik Cache, fixing permissions, and no change. Running a full backup via Titanium Backup now before I try a factory reset to see if that fixes it.
If that doesn't do it I'll try restoring a backup image from last week.

gohawks1 said:
Ya it's rooted and has nvflashed clockworkmod recovery installed. Rooted the day I got the phone and clockworkmod recovery has been installed for about a week.
I just tried clearing the cache partition, wiping Dalvik Cache, fixing permissions, and no change. Running a full backup via Titanium Backup now before I try a factory reset to see if that fixes it.
If that doesn't do it I'll try restoring a backup image from last week.
Click to expand...
Click to collapse
I would guess it's not the phone but the CWM made the mess. You probably want to try factory reset.

My Bluetooth settings and profiles randomly appear and disappear and I'm bone stock.

Well, factory reset got all my buttons working again, and my screen locks again. Since I'm back to stock now and have to re-setup everything now I think I'll go try out the Eaglesblood ROM and see how that goes.

Help needed diagnosing possible nand memory problem - Samsung Note 8.0 n5110

So I have this n5110 tablet which has performed without problems since I bought it last year in December. Device is running TWRP recovery and Resurrection Remix 5.7.4 (CM13 based).
The symptom: first time it happened was during an "apps upgrade" session. Google Play Store updated a bunch of apps and all in sudden the tablet froze. Completely. Dead. Clock in status bar stopped working. After an hour I gave it a reset (hold power until it reboots). The result: boot loop. After finishing the boot process, it showed the lock screen for couple of seconds, then reboot ... and so on.
Went into recovery, did a wipe of data & cache & dalvik & system and started all over. After restoring the system, i started installing apps. All in a sudden ... BOOM ... same problem again.
You can imagine - I went through this process about 7 times. Then I realized, no matter what I do, if free storage has decreased to about 7.6 GByte, the big boom happenes and the phone is dead (boot loop).
I began to suspect a nand problem. So after restoring the system (without reinstalling all my apps) I installed “eMMC Brickbug Check” which also does a memory check. The app showed no problem. All good.
So back to recovery, into terminal and there I tried to “zero” the data, cache and dalvik partitions using “dd if=/dev/zero bs=1M of=/dev/block/mmc...” - you get the idea. No error messages here so all 3 partitions did not cause a nand writing problem.
So I'm stuck now. Before I try to replace the motherboard ... does anyone have an idea on how to really “test” the nand to confirm my suspected nand write problem?
Thanks for any help!
Markus.

oldschool63 said:
So I have this n5110 tablet which has performed without problems since I bought it last year in December. Device is running TWRP recovery and Resurrection Remix 5.7.4 (CM13 based).
The symptom: first time it happened was during an "apps upgrade" session. Google Play Store updated a bunch of apps and all in sudden the tablet froze. Completely. Dead. Clock in status bar stopped working. After an hour I gave it a reset (hold power until it reboots). The result: boot loop. After finishing the boot process, it showed the lock screen for couple of seconds, then reboot ... and so on.
Went into recovery, did a wipe of data & cache & dalvik & system and started all over. After restoring the system, i started installing apps. All in a sudden ... BOOM ... same problem again.
You can imagine - I went through this process about 7 times. Then I realized, no matter what I do, if free storage has decreased to about 7.6 GByte, the big boom happenes and the phone is dead (boot loop).
I began to suspect a nand problem. So after restoring the system (without reinstalling all my apps) I installed “eMMC Brickbug Check” which also does a memory check. The app showed no problem. All good.
So back to recovery, into terminal and there I tried to “zero” the data, cache and dalvik partitions using “dd if=/dev/zero bs=1M of=/dev/block/mmc...” - you get the idea. No error messages here so all 3 partitions did not cause a nand writing problem.
So I'm stuck now. Before I try to replace the motherboard ... does anyone have an idea on how to really “test” the nand to confirm my suspected nand write problem?
Thanks for any help!
Markus.
Click to expand...
Click to collapse
Answering my own question here: after quite some hours of trying it turned out that my tablet seems to be just fine. The problem is something totally different and weird. If you are interested in what's going on, please continue reading here: https://forum.xda-developers.com/android/help/help-app-bricks-samsung-tablet-try-to-t3661516

Wokeup to my phone stuck in a bootloop... [SOLVED]

UPDATE: I have finally managed to get my phone working again! Am now currently re-downloading all my apps and transferring all my files back to my phone, running AOSPExtended (https://forum.xda-developers.com/oneplus-one/development/rom-aospextended-rom-t3732194) with OpenGApps. I'll write the steps I took to figure this mess out at the end of this post for anyone who might encounter the same problem in the future. :good:
So last night I left my phone charging overnight from 54% as I was downloading a couple of files (my internet is 1Mbps or 125KB/s). I've done this a couple of times before with no problems what so ever. But this morning I woke up and my phone was in a boot loop. I've tried everything I can think of and everything I could find on these forums, but to no luck. I am at my wits end and I have no clue what to do except to do a full factory reset, which I'd rather not do as its been a while since my last backup and I would lose a lot of precious files...
My Phone: OnePlus One 64GB Sandstone Black, purchased in August 2014.
ROM: cm-13.0-ZNH5Y-20161105-STABLE-Sultan-bacon
Recovery: TWRP+3.0.3-2-TugaPower
Firmware: bacon_firmware_update_2016_1-25_.4.0.1.c7-00011
The boot loop itself is odd, I'll describe them separately here.
-I can boot into fastboot, but not while the USB is plugged into my PC. I have to boot into fastboot, followed by plugging it into my PC. If I try to boot into fastboot while it is plugged in, the screen goes completely black and goes back into the bootloop. However, the phone shows up in Device Manager during the black screen.
- I can boot into Recovery, but the phone automatically reboots and goes back into the bootloop after a few minutes. One thing I have noticed is that if I let it reboot by itself, all the settings reset (including the confirmation to allow modifying of files when you first boot into recovery). But if I manually reboot back into recovery, the settings remain the same; atleast until it reboots automatically again.
Here, I'll list the things that I have tried to no avail:
1. Following this post - https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/, when I try to wipe Dalvik cache and cache from recovery, the phone goes right back into the bootloop
2. I tried flashing a newer version of TWRP (3.2.1-0 and 3.2.1-K2). After flashing I try to boot into recovery but the TWRP loading screen displays, and then goes right back into the bootloop. It wont even let me into the main menu.
3. I tried flashing a ROM through fastboot (via this post, https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/). The phone still remains in a bootloop.
HOWEVER, if I flash my previous recovery (TWRP+3.0.3-2-TugaPower replacing the stock cyanogen recovery from this method), my phone manages to get past the 1+ screen, and goes through my custom power on screen, and reaches the "Android is starting... Optimizing app 1 of 67." But it never gets past app 1, freezes, and then reboots. So now it's stuck in this "extended" bootloop thing.
What I want to know: is there anyway to fix my phone, or will I have to lose all my data and do a full factory reset through the ColorOS method? If anyone has any experience with this or knows a way to help, please don't hesitate!
Thank you in advance.
WHAT WORKED FOR ME:
After following the steps in this post (https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/) my phone was booting up, but was kicked back into a boot loop after freezing at the "Android is starting.. Optimizing app 1 of 67" screen. However, the recovery was now the default CyanogenMod recovery. I then re-flashed my previous recovery (TWRP+3.0.3-2-TugaPower) from fast boot, and it was now stable (no more auto-reboots). From there I made a backup off all my files onto my PC before proceeding. After that, I did what this post said (https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/) and wiped Cache + Dalvik cache. This allowed me to boot all the way past the "Android is starting" screen. However, the phone was still rendered unusable as there were non-stop notifications saying various apps had stopped working. I then booted back into recovery, downloaded and pushed a new ROM and GApps package on to my phone, wiped system, data, cache, dalvik cache, and installed the ROM and GApps pacakge, clearing the cache one more time before rebooting. Everything is working beautifully so far and I could not be happier! I hope this helps anyone else who encounters this problem, Cheers!

Failed to mount '/data' (Invalid Argument)

Trying to root my phone. Flashed TWRP in Odin, then installed SuperSU through TWRP. At the end it gives me the error in the title, and I get a 'failed integrity check' when booting into the system.
Help?

I've always read you have to do a factory reset after TWRP installation due to encryption, but apparently you don't have to
It still says you lose your OS though.
https://forum.xda-developers.com/galaxy-s7/help/root-twrp-flashing-t3535545
AzzyC said:
No factory reset required. Basically, the file system of your Data partition is incorrect and that is why it can't be mounted on to.
Go to 'Wipe'->'Advanced Wipe'->Click on the Data box->'Partition Options'->(You may be seeing values like 0mb for most of the information displayed and why you can't mount to it; if you are not let me know!)->'Change File System'->(Try out different File Systems until you being to see true values for the sizes, but avoid using EXT2 and EXT3 if you can)
Doing all this you will be able to Mount to your Data partition, however your OS will be deleted! So get your phone into Download mode, open up Odin program on your PC, and flash a Bootloader (BL) and your phone will be fine.
Then flash the 'no-verity-encryption-opt.zip' and then your SU Binary and Xposed Framework etc.
Good luck again Buddy!
---------- Post added at 05:41 PM ---------- Previous post was at 05:12 PM ----------
Wait Install the No-verity zip first then, then flash a BL
Click to expand...
Click to collapse

It's a brand-new phone so I don't really care about the OS.
Also I tried restoring my Nandroid backup, but the drive appears empty when I go to the "Restore" option in TWRP. Not sure if I need to fix the data thing first anyway, but surely it should show up?
EDIT: Now that I think about it wasn't there some requirement to clear a cache at some point? I vaguely remember that from the last time I rooted an S7.
I've tried formatting, and the readout says "formatting" and then "Done.", but there's still a progress bar and the title area still says "Formatting...".
EDIT 2: It's plugged in but the battery is still dropping, and it only started at 8%. So it might just die anyway.

I recently went back and forth between Oreo and a TWRP Nougat backup, and was flashing TWRP each time I went up to Oreo because I was installing it via Odin which was blowing away TWRP.
I must have had to factory reset and flash the dm-no verity.zip a few times each TWRP install before I got /system and /data to not return an error. I was probably doing something out of order, but it always seemed finnicky.

How does one do the factory reset?
TWRP still reckons it's formatting, even though it says "Done.", but the battery has just hit 0% so it won't last much longer anyway.
EDIT: Or not...battery still going strong at apparently 0%. But it's been formatting for over two hours now.

Advanced wipe with data, cache, and davlik cache checked should be enough

When was I supposed to do that step? It rings a bell but it isn't in the instructions I found.
The phone finally died, and now I cant' seem to get past the TWRP splash screen.
EDIT: Just plugging it in results in the TWRP splash screen. None of the buttons seem to do anything, so I can't get into download mode and reflash TWRP or anything...

Okay, so I left it on the charger for a couple of hours.
Pressing and holding the power button turns it off. A few seconds after plugging it in, I get the Galaxy splash screen followed by the TWRP splash screen, and then the latter just stays there. Forever.
Once I turn it off, I'm unable to turn it back on at all - standard boot, recovery or download. I pressed and held the buttons for a full minute, made no difference.
EDIT: Leaving it off the charger results in the screen turning off a few minutes later. Again, no amount of pushing the buttons will do anything.
EDIT 2: Got it into download mode by plugging it in and holding the buttons down while waiting for it to automatically boot. Next step? Flash a bootloader, or reflash TWRP, or both?

Tried reflashing TWRP, changes nothing. Also tried flashing a BL and CP from the last time I installed SupermanROM, but it failed in Odin. Not sure if they're just too old or something, I have no idea how that stuff works or how updated my software is or anything.
It's the same handset I had before, but it had to go back to Samsung for repair because the battery blew up, so they very kindly wiped everything, reset Knox, etc.

Question Soft boot loop after wiping cache partition - Rooted S908E

I need help. After rooting the device and after several days of using it, and saw that Wipe cache partition can clean up stuff and increase battery life and performance. So I went ahead, connected my phone using a USB-C cable to PC, hold the UP button while booting, and selected Wipe cache partition. Booted it up again, and it was running fine but the phone has starting for almost like after every minute it hangs, and goes back to the Samsung logo, and the cycle repeats. I was only able to escape via booting in Safe Mode.
Any advice what to do to prevent the boot loop? Is there any way to know which or what makes the phone hang?
Running in Android 12 One UI 4.

givememysandwich said:
I need help. After rooting the device and after several days of using it, and saw that Wipe cache partition can clean up stuff and increase battery life and performance. So I went ahead, connected my phone using a USB-C cable to PC, hold the UP button while booting, and selected Wipe cache partition. Booted it up again, and it was running fine but the phone has starting for almost like after every minute it hangs, and goes back to the Samsung logo, and the cycle repeats. I was only able to escape via booting in Safe Mode.
Any advice what to do to prevent the boot loop? Is there any way to know which or what makes the phone hang?
Running in Android 12 One UI 4.
Click to expand...
Click to collapse
Not sure why that would do that.. But it seems like the only solution now would do a complete factory reset and start over.

Thank you for the reply. For some reason, the phone just decided to fix itself. What I did was just let it be in Safe Mode for several hours, went back to Normal mode, and somehow it stopped hanging.