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...
Related
Hi guys, I recently trying to root the SGS2 with ClocworkMod 4.0.1.5..during my 1st try, The update was unsuccessful because when i used the Odin, the progress bar stopped...already waiting for like 15 minutes, no progress...wait for another 15, no progress also..so I decided to unplug it, close the Odin, and changed the USB port to another port, restart Odin, and I got it working to flash it (Odin display PASS)..However, the problem starts now, I cannot get pass the blackscreen of my SGS2 to go to the splash screen. I tried going to Recovery Mode, but i cannot do anything. I tried wiping the data, cache, and even trying to change the firmware, but no avail. Recovery mode always give error cannot mount the appropriate file..any help with this?
my tap was working fine and then it suddenly stops, and hang, i restarted it, but every 4-5 secs, it restarts itself again, then i came up with this so called bootloop. then i tried to open the system recovery menu and i selected wipe data, i've waited for so long and took hours but i ended up with nothing, i have no idea on how long will it take to wipe the data on my device, i also tried to factory reset it, same result, still stuck on boot loop. what should i do? help please. no custom roms installed, just rooted.
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.
Hello, I installed a flash for Nexus lollipop a long time ago and i think it could affect it.
I currently have android Marshmallow and I saw a may update (13mb) and I clicked to install it. I came back to it after around 15 minutes and I noticed that the phone is still booting up (the four dots). It's been stuck like this for around 20 minutes. So I launched the phone in recovery mode and I wiped the cache portion successfully. After that I rebooted it and it was still stuck on the reboot, so I started it in recovery mode again and I clicked the wipe data/factory reset option and it has been wiping the data for around 10 minutes and nothing has happened. I don't know what to do know and I don't mind losing my Data as long as I can get the phone working again, thanks.
Edit 1: It just finished wiping the data and I clicked the reboot option, but it has been stuck on the four dots again for around 3 minutes so far
Edit 2: Nothing changed, it stayed in reboot, I am back in the recovery option and I just wanna give you guys more information, this is what it says at the top:
Android Recovery
google/hammerhead/hammerhead
6.0.1/MOB30H/2751534
user/release-keys
Use volume up/down and power.
RoBoTcLoNe said:
Hello, I installed a flash for Nexus lollipop a long time ago and i think it could affect it.
I currently have android Marshmallow and I saw a may update (13mb) and I clicked to install it. I came back to it after around 15 minutes and I noticed that the phone is still booting up (the four dots). It's been stuck like this for around 20 minutes. So I launched the phone in recovery mode and I wiped the cache portion successfully. After that I rebooted it and it was still stuck on the reboot, so I started it in recovery mode again and I clicked the wipe data/factory reset option and it has been wiping the data for around 10 minutes and nothing has happened. I don't know what to do know and I don't mind losing my Data as long as I can get the phone working again, thanks.
Edit 1: It just finished wiping the data and I clicked the reboot option, but it has been stuck on the four dots again for around 3 minutes so far
Edit 2: Nothing changed, it stayed in reboot, I am back in the recovery option and I just wanna give you guys more information, this is what it says at the top:
Android Recovery
google/hammerhead/hammerhead
6.0.1/MOB30H/2751534
user/release-keys
Use volume up/down and power.
Click to expand...
Click to collapse
Hi,
Just boot into fastboot mode and flash the stock img . Refer this guide : http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
NOTE : That guide is for 5x. So download the img for hammerhead and follow the steps to flash procedure from that guide
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!