HELP - memory fail? - P6800/16GB/CarbonROM/ROOT - Galaxy Tab 7.7 Q&A, Help & Troubleshooting

Device : TAB 7.7 P6800
ROM : Carbon ROM build 12/12/14
ROOTED
CWM 6.0.3
Ok so I wake up yesterday to found out that my Whatsapp suddenly fc. And when i open it back, it shows that my chat backup are messed up and i need to restore it.
And while doing that, it started to reboot by itself.
I thought it will be okay after that.
It not.
Reboot, power on, Dropbox fc. Few seconds after that, reboot again.
power on, another apps fc. after few seconds, reboot again.
It keeps rebooting into the same state when i woke up that morning. Wifi turned on, few notifications on panel, (thou i keep clearing it everytime when it power on)
Now ive tried wipe data , wipe cache, everything in CWM. but it keeps rebooting into the same state!
Ive also tried flash with stock rom via ODIN.
Guess what?
It appear PASS on ODIN, but when the tab powered on, is still went back to the previous same state.
Ive google around and some said it is the sign of memory flash fail or smthing.
anyone maybe could help me out?
im on dead end.

Related

[Q] Factory Reset Did Not Wipe Anyhing

I'm trying to remove apps that's on this phone (GT-S7500) because some of the apps always force close and not working. Firstly, I tried uninstall the apps one by one, all went good until I rebooted the device, all of the apps are back again. Second, went to privacy>erase everything including SD card content, device rebooted and went straight to recovery. It was weird because normally it will reboot itself straight to home screen. So I select the option factory reset/wipe data, after that wipe cache partition and reboot. Device does not reboot but turned off completely (weird again) Turned it back on, and only saw that none of the apps were removed. Even the wallpaper are still the same. Next thing I do is manually boot into recovery menu and factory reset again, still the same thing, (device turned off without rebooting itself, turned it back on and everything was still the same) after few tries again, I finally decided to flash a stock rom with ODIN. Flashing was successful ODIN shows PASS, waiting device reboot but it shut off completely again. turned it back on, but nothing changes. wallpaper are still the same and every single downloaded apps were still there. Went to settings> about device only to found that it wasn't the same rom that I've flashed earlier using ODIN.(flashed 2-3 times again, results still the same) Very confused right now, suspected that the internal SD card was corrupted/damaged. Does anyone experiencing such thing on your galaxy ace plus? searched on xda forums and found that this issue was also happening on few other devices. This is not my phone, just helping a customer. Thank You.
After flashing stock rom
Go to recovery (stock of course)
Wipe data/factory reset
Wipe cache
Reboot
Sent from my Gt-S7500

[Q] [A700] won't boot

Hello
Today, as I was browsing, the tablet turned off and it would not turn back on again. Or I thought it wouldn't...
After about 30 or 40 times pressing on power and reset, turned on but stopped on the acer logo. I reset it again and after 40 tries I managed to go to cwm recovery.
Tried a wipe but I got a bunch of errors (showing on attached photos).
After 40 tries again I tried to flash cm 10.2.1 stable. Again a bunch of errors.
I even tried to install a wipe script found on the forum (OCDW1.2_with_data_wipe.zip) with no success.
And it won't go to bootloader mode also...
Is it time to bin the thing or we can do something to save it?
Thank you.
UPDATE
Now it won't go to cwm recovery:
Will display something like E: can't open log on ... and will turn off...

Phone Just Shut Off - Now Won't Boot

Okay this is the second time this happened. My phone just completely shut down randomly as I was opening a tab in Chrome. I turn it back on, flashes Samsung then the Slimkat screen but won't go past. I put the battery in it, it turns itself back on (vibrates right after I put the battery back in). I can get to recovery and I can get to download mode.
When I had CM11, the phone would keep rebooting. The last time it did this, it had the same problem, so last night I said screw it and went to Slimkat. To fix this issue, I had to go back to a stock rooted rom, then flash recovery, then flash Slimkat, etc. It worked until today. I flashed the build on my phone and that doesn't fix it either.
What is the problem? Seems like my phone is soft bricking itself? I'd rather not go back and configure everything yet again.
Okay I've wiped data, tried to reflash the rom, and now when I get into download mode, the phone just goes black.

[2016]Random Reboots on my ONE. Please help.

Later edit5: Tried to restore my nandroid backup and TWRP froze. Had to hard reboot the phone...
Later edit4: It started working. It f***** started working. Out of nowere. Last night, the last thing i tried was this: https://forums.oneplus.net/threads/fix-for-sudden-death-and-boot-loop.146107/
I rebooted the phone and it didn't work. I gave up.
This morning I turned it back on and ... surprise, surprise... it started working (optimizing apps and actually booting into cos12.1).
My happiness didn't last because as soon as the phone started updating some apps, it crashed, and entered a boot loop again. Good thing i managed to copy one of my previous backups.
Can someone explain this behavior?
Later edit3: my phone is still stuck in a bootloop. Neither roms are working.
Things I've tried:
- flash new roms
- erase/ flash persist
- flash color os
Nothing works!
Later edit2: while on cm13, i plugged it in to recharge. While connected to wall plug it did nothing(working fine, as it should be). As soon as i unplugged it started rebooting over and over again... a boot loop. This phone is starting to look like one of the biggest mistakes i ever made. I regret purchasing it.
Later edit: now it just turned off, and pressing the power button won't turn it back on. Had to press it for about 10 - 15 seconds. ANNOYING!
OP: I've been experiencing random reboots on my oneplus ONE since I've had it.
When i first got the phone, i was so excited about it and started flashing custom roms, just for fun and to see which one suites me. I messed up the phone (my camera wouldn't work anymore. All the roms gave me the same message"Camera has stopped working" ) and sent it back to warranty, here in my country, at the shop from which i've bought it. After two weeks they sent it back to me with the note "restored to factory settings". I've checked the "About" section and it was running cos12.1, 1 jan 2016 security patch, kernel 3.4.67.
So I've decided to stick with this rom because I didn't want to mess it up again. But, out of nowhere it rebooted. First i thought that it was an app that needed the phone to reboot. I didn't mind it. I've left my phone over the night and in the morning it was saying "enter pin" as it has rebooted.
Long story short, ever since it reboots at least 1 time a day, and it is getting really frustrating! Sometimes when i'm in an app, sometimes when it just lays around.
Reasons it rebooted:
- no reason, just siting and it rebooted
- opened waze app
- browsing chrome
- tried to connect to a saved wireless network, it rebooted and afterwards the network was not recognized anymore and had to retype the password
- no reason!!! just sitting!!
- fresh install of cos 12.1, i queued about 20 apps to install... it rebooted and continued installing after reboot.
- sometimes i heavily use it and it runs perfectly, but when i stop using the phone and lay it down it reboots. (this only happend one time)
Things I've tried:
- factory reset
- clear cache and dalvik cache
- power cicle the phone
- new rom
None of these worked.
Today I installed sultans CM13, with his 3.4.0 - sultan - caf kernel, hoping that my problems would disappear. (I installed TWRP 2.8.7.0.5, flashed the rom, cleared the cache, flashed the gapps, cleared the cache and reboot.)
It ran flawlessly. I've installed all my apps, played a little with it, configured it as I pleased and I've left it the table for about 15 minutes. When i picked it up, it rebooted(AGAIN!) out of nowhere.
What could it be? As I read through the forums i found out that a log with the exact problem is impossible to get because it gets deleted.
Could it be the wireless network? Could it be the sim card I am using or the phone modem? Could it be because of the launcher?
(for now, i've disabled my sim pin so when my phone reboots i don't miss phone calls if i don't notice it has rebooted)
Please help, as this problem is getting more and more frustrating...
Reboot log
Quickly after a reboot i reconnected the phone, opened cmd and typed adb logcat.
This is the log. 22:17 is the time when the phone rebooted so i extracted only that fragment of the log.
I am going to flash the stock cm13 nightly with the "stock" version of gapps. (until now i always flashed "nano").

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!

Categories

Resources