Database Info

[Q] Random Reboot and Reset

So i saw a lot of random reboot threads, but none like my problem. I'm running Embryo 6.11. I was using my phone today to take pictures and then the phone rebooted itself, but would not get past the Samsung glow logo. I waited about a minute and nothing, so I pulled the battery, waited about 5 minutes for the phone to cool down, just in case it was an overheating issue. Then I tried to reboot and the same thing happened, it got stuck at the glow logo. So i rebooted again, this time I got to my home screen, as soon as I tried to open an app, the phone rebooted and then it wouldn't get past the glow logo again. I pulled the battery, then put it back in and just charged the phone up while off, just in case i had to do a lot of stuff to it. So after i charged it up, I tried booting up again, no luck. So i booted into recovery, tried flashing the ROM over the current installation, in hopes that that would just fix the broken areas causing it not to boot, but it didn't, so i went back into recovery and did a full wipe and now i'm starting from scratch again. This happened a week ago today (the 15th) and it also happened on the 1st. I don't know what is going on, do I have a bad partition from doing the Sean 3x wipes in the past when i used skyICS (I don't do that anymore, just one wipe now), or maybe from using Darkside superwipe in the past?

fishlipsboy said:
So i saw a lot of random reboot threads, but none like my problem. I'm running Embryo 6.11. I was using my phone today to take pictures and then the phone rebooted itself, but would not get past the Samsung glow logo. I waited about a minute and nothing, so I pulled the battery, waited about 5 minutes for the phone to cool down, just in case it was an overheating issue. Then I tried to reboot and the same thing happened, it got stuck at the glow logo. So i rebooted again, this time I got to my home screen, as soon as I tried to open an app, the phone rebooted and then it wouldn't get past the glow logo again. I pulled the battery, then put it back in and just charged the phone up while off, just in case i had to do a lot of stuff to it. So after i charged it up, I tried booting up again, no luck. So i booted into recovery, tried flashing the ROM over the current installation, in hopes that that would just fix the broken areas causing it not to boot, but it didn't, so i went back into recovery and did a full wipe and now i'm starting from scratch again. This happened a week ago today (the 15th) and it also happened on the 1st. I don't know what is going on, do I have a bad partition from doing the Sean 3x wipes in the past when i used skyICS (I don't do that anymore, just one wipe now), or maybe from using Darkside superwipe in the past?
Click to expand...
Click to collapse
I had a similar issue on Embryo 7... ROM installed fine, worked fine for about a week then reboot and not going past the Samsung logo. What I found out was that the data and system partition were bad... running an e2fsck from adb shell while in recovery turned out a lot of logical errors (most of them were about inodes allocated to more files if I remember correctly but not only those). I found out while working on it that wiping these partitions from recovery is not fixing these errors.
What I did was I wiped everything (cache, data, system), ran e2fsck on each individual partition to fix the errors until no more were showing up then started from scratch (install ROM, restore apps, etc). So far, no more issues.

How do I run e2fsck? I'm not familiar with adb shell. I am a flasher and slight modder, but not a dev.

fishlipsboy said:
How do I run e2fsck? I'm not familiar with adb shell. I am a flasher and slight modder, but not a dev.
Click to expand...
Click to collapse
Reboot phone in recovery since you need those partitions unmounted. Connect phone to PC with USB then connect from PC with adb (run "adb shell"). If partitions (data, system, cache) are mounted you can unmount them from recovery.
Once you are in adb shell then you can run "e2fsck -fnv /dev/block/mmcblk0p24" to scan system partition. Repeat for data partition (mmcblk0p25), efs (mmcblk0p21), cache (mmcblk0p26), preload (mmcblk0p27). That will tell you only if you have errors; it will not fix them.
To fix them, run "e2fsck -fcyv /dev/block/<part name as above>".
You can also run "e2fsck" (with no parameters) to see the help and what each parameter means.
Also, see this great thread regarding the list of partitions in Skyrocket... http://forum.xda-developers.com/showthread.php?t=1629508
Hope this helps you. Let me know if you need more detailed instructions.
---------- Post added at 11:31 PM ---------- Previous post was at 11:27 PM ----------
fishlipsboy said:
How do I run e2fsck? I'm not familiar with adb shell. I am a flasher and slight modder, but not a dev.
Click to expand...
Click to collapse
BTW, if you find errors on your data and/or system partitions and choose to fix them, it does not mean that you phone will boot fine right away. Depending on how bad it is, you might need to reinstall the ROM.
Also, fixing the errors takes space (as *nix saves the recovered files under "lost+found" folder) so in my case, I chose to wipe the partitions from recovery first, then fix the errors and then re-install the ROM.

Bricked?

So my girlfriend bought this phone today, and when the phone got all up and running it wanted to do a system update to kitkat, said it would take about ten mins so she does the update and 2 hours later it still wasnt running ( got stuck on a screen that says "Finishing boot" ) after two hours it was rebooted and would not get past the motorola screen, so we took it back and exchanged it, came home and started setting up the new one and its stuck at finishing booting, can someone give me some advice on this

also its starting to get hot

It has went into a Bootloop, I would reboot into recovery and clear the cache

Wherezz said:
It has went into a Bootloop, I would reboot into recovery and clear the cache
Click to expand...
Click to collapse
its 100% stock, how do I go about doing that?

With the phone turned off, Press and hold Volume down + Power button for about 3 seconds, Select Recovery, then select wipe/format/clear (dont remember how it says) cache.
It should fix this
---------- Post added at 11:28 PM ---------- Previous post was at 10:47 PM ----------
So, did it work?

that did not work, now trying the factory option as I would assume it means factory reset

The factory reset must work for sure, but I told you to clean the cache because the factory reset deletes all the phone data
Sent from my SGH-I777 using Tapatalk

Yes but there was no option to clear the cache in the recovery options , factory reset kinda worked , it can receive calls however its stuck on whatever screen it displays can't go to the home screen either
Sent from my SPH-D710 using xda premium

Is the Verizon one? You must activate it before you can use it, there is a way to bypass the activation screen, http://youtu.be/qhphsyRFEy4
Sent from my SGH-I777 using Tapatalk

Idk what it was but the phone rang and it started working . it is Verizon and it was activated , it froze at the Motorola logo but it was weird cause it didn't start working ...... Very odd but no idea why that happened
Sent from my SPH-D710 using xda premium

Honor 8 softbricked and can't get past recovery screens

Hi,
Would appreciate any help anyone can offer. I have softbricked my phone. I have never attempted to root the device and so have no other apps that were installed that can help me. It is also out of warranty.
I have tried various things my model number is frd l09 and I purchased in the UK.
1. When I switch it on normally I get a emui screen that allows me to reboot, factory reset or wipe cache partition. I have tried all of these. When I factory reset it just reboots onto the same screen and so I get stuck in a loop.
2. I have also tried downloading the relevant firmware to the SD and then rebooting pressing volume up/down and power. When I do this it starts to install but then I get a message saying 'software install failed' with the only option to reboot now, which results in scenario 1.
3. I have also tried the erecovery with the cable plugged in go to download latest version and recovery, it tries to get package info but fails.
4. I have also tried to connect to hisuite and use system recovery pressing vol down and power, it starts to install but gets stuck on 5%.
I have tried searching for answers but have basic technical knowledge so any guidance would be really appreciated

Which firmware you were in before issue??
---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------
Your model number and build number??

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.