So I flashed CM12 on my Galaxy Tab 2 10.1 and then tried to encrypt it. I had full battery and everything but I saw them message that it failed. It asked me to reset the device so I clicked it. It was the only option. When it rebooted, it went straight to TWRP but instead of loading TWRP, it just kept showing the splash/loading screen. Then it would flash black quickly and then show the splash screen again. I left it plugged in over night to see if it would load. It did not. So I let the battery completely die. Once I charged it, it still does the same thing. I've tried using ODIN to flash TWRP again. It says it successful but the same thing happens. I also successfully flashed CWM with ODIN but the screen flashing thing still happens. (I can put the tablet in Download Mode with no problem).
Does this mean I've fried my SD card or is there some other fix I'm not aware of?
I'm not sure why this worked but I was able to boot into CM by leaving the device in the boot loop and running the command `adb reboot bootloader`. After that CM12 loaded up. I decided to try restarting and it restarted just fine too. Everything seems to be back to normal.
Related
So ive been running CM 10.1 with CWM v6.0.4.3 for several months without major issue until last night. I went to send a text message to someone, and right as i went back to my home screen, the phone froze, rebooted, and when it finished rebooting, the deice would freeze again as soon as the lock screen was reached, and reboot again. Cue repeated circle of freeze, reboot, finish rebooting, freeze, reboot.
I turned the phone off by taking out the battery, put it back in and charged it overnight without booting it up. Went to start the phone today, same issue still. I would boot into recovery and try to re-flash the OS, and it would give me a status 7 error. After re-downloading everything into my sd card, i was eventually able to get the system to re-install cm10.1.3, and it booted up normally. I downloaded and installed ROM Manager, and installed the newest version of CWM Touch, version 6.0.4.5, and then tried to boot into recovery to install CM11. It showed the CWM Hat icon in the middle of the screen, with the version on the bottom of the screen, then rebooted on its own without showing any menu options.
Now if i try to boot into recovery, it just shows the icon and version again, then reboots, and wont go past the CM loading screen with the spinning cyanogenmod icon.
Not sure what to do at this point, i cant get into recovery to try and flash something new, and i cant get past the CM loading screen to actually use my phone. Any ideas? I have zero experience with adb, so im stumped.
UPDATE: Solved, i flashed TWRP over CWM using Odin, and was from there able to re-install the OS. Things seem to be working fine for the most part, with the exception of one random reboot last night.
Salomon3068 said:
So ive been running CM 10.1 with CWM v6.0.4.3 for several months without major issue until last night. I went to send a text message to someone, and right as i went back to my home screen, the phone froze, rebooted, and when it finished rebooting, the deice would freeze again as soon as the lock screen was reached, and reboot again. Cue repeated circle of freeze, reboot, finish rebooting, freeze, reboot.
I turned the phone off by taking out the battery, put it back in and charged it overnight without booting it up. Went to start the phone today, same issue still. I would boot into recovery and try to re-flash the OS, and it would give me a status 7 error. After re-downloading everything into my sd card, i was eventually able to get the system to re-install cm10.1.3, and it booted up normally. I downloaded and installed ROM Manager, and installed the newest version of CWM Touch, version 6.0.4.5, and then tried to boot into recovery to install CM11. It showed the CWM Hat icon in the middle of the screen, with the version on the bottom of the screen, then rebooted on its own without showing any menu options.
Now if i try to boot into recovery, it just shows the icon and version again, then reboots, and wont go past the CM loading screen with the spinning cyanogenmod icon.
Not sure what to do at this point, i cant get into recovery to try and flash something new, and i cant get past the CM loading screen to actually use my phone. Any ideas? I have zero experience with adb, so im stumped.
Click to expand...
Click to collapse
You can try to reflash CWM with Odin, if that not working, you could try to Odin back to stock.
buhohitr said:
You can try to reflash CWM with Odin, if that not working, you could try to Odin back to stock.
Click to expand...
Click to collapse
I figured it out yesterday actually and forgot to update! Indeed I was able to flash TWRP with odin, since CWM seemed to be blocking me from doing anything. Once that was up and running, things went back to normal, i was able to flash CM 10.2.1 and things seem to be working now.
One thing though, while playing skyrim last night i had it on the charger next to me, and the phone randomly rebooted without any interaction from me. Was odd, but it hasnt done it since. Keeping an eye on it still.
I have a rooted and bootloader-unlocked Inspire 4G. A few months ago, I had been using the MoKee 4.2.2 ROM for some time, and one day, my phone's screen simply froze. I thought I shouldn't be worried about it, so I pulled the battery off, slapped it back in and tried turning on the phone again. It never got past the MoKee loading screen. I tried charging it, leaving it to boot for hours but nothing.
Next, I tried rebooting into CWMrecovery to try different stable backups I had from some time before that happened. The backups restored successfully, but again, the phone stayed stuck in the loading screen. I tried the same with 4EXT Touch Recovery and wiping all the data before the backup, but still nothing worked.
Since I was too busy at the time to install a new ROM and flash a new boot image, I decided to put the phone away and use my backup Galaxy Ace. Today, a few months after that happened, I tried to boot the phone into bootloader and I can't even achieve that. Holding the volume down rocket and power buttons, the phone still boots normally and stays stuck on the loading screen.
What weirds me out the most is that this was all random--I did not drop the phone or did things to it that could break it.
I feel if I could get into recovery I'd be able to do something else about it.
Any ideas?
Me too
Weird, mine just did the same thing today. Crashed, had to pull battery, now stuck at Mokee. Tried clearing DC, cache, factory reset. No luck.
my nexus 4 was on temasek's unofficial cm12 build ver 6.1
recovery in use was recovery-philz_touch_6.59.0-mako
i decided to update the rom to build 6.5, so i downloaded the zip to my sdcard,
i had not made a nandroid bkp
after flashing the rom/gapps/superuser, wiping dalvik and cache, things went wrong
after that the phone would only show 'google', then freeze, then go blank, then again show 'google'. this is the first Loop i have encountered where the boot animation never even showed up.
after that in about 8 hrs, i tried all of the foll-
installing the stock images: my phone booted up the first few times i flashed stock images using fastboot, but after three times (because each time it successfully booted i would go back to recovery to try flashing the customromzip) my phone stopped booting up for stock.
it resolutely stayed stuck on the boot ani.
recovery: flashed many times, via sdcard and also via fastboot. no problem with the recovery
zips. absolute fail. nothing can get me past the 'google'
now there's another peculiarity, which makes me wonder if there is hardware damage involved in this softbrick story
after all this flashing my charge came down to 20%, so i tried to charge it (switched off, obviously, since it isn't booting up)
but every time i connect my charger, it boots up,and then shows me google, and freeze and restart..same old cycle
in a last ditch attempt to somehow charge my phone i have brought it to fastboot, and left it connected to my laptop. i don't know if this will work.
please help, also i am now considering using a toolkit, unified android or wugfresh (the latter, i have a previous bad experience with) to get my phone to atleast switch on with something.
should i use the toolkit or just take my brick to the servicecenter to check for damage to hardware
My n7105 runs on resurrection remix(marshmallow). It works fine but some times, the device reboots randomly. Last night it rebooted and was stuck in boot loop. I went into custom recovery to factory reset but it said FAILED TO MOUNT DATA, SYSTEM, CACHE......I tried everything. Finally i managed to get my sdcard storage to work on the device and i flashed the stock ROM. It flashed successfully but when i rebooted, the samsung logo didnt appear.The device was shut down and i couldnt get it to turn on. It wouldnt show any kind of response. But when i charged, the phone heated up a bit. So.... Is my emmc chip dead?
Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?
AMpageg2 said:
Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Sounds like a Hardware issue? Sorry to say what your saying doesn't add up and or make sense. Fastboot should work no matter what even if you soft brick it and mess up recovery. I suggest letting the power fully drain maybe and google how to fast boot in case you are doing it wrong.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Click to expand...
Click to collapse
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.
AMpageg2 said:
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.
Click to expand...
Click to collapse
I agree with what @Shinobi_warrior said.Seems like you just have a soft brick,so you should be able to boot into fastboot mode without any issues.Are you sure you're doing it the right way? Did you try draining battery completely and then booting into fastboot(yes,you don't need much battery to boot into fastboot mode)?
Well I was finally able to get the device detected by ADB, but it just shows as offline. I attempted to use the repair kit and nothing seemed to happen. I also attempted a different tool (https://forum.xda-developers.com/on.../oneplus-one-toolkit-manudroid19-gui-t2807418) and then booting into either fastboot or recovery that way, a terminal window pops up and quickly disappears, and then nothing else happens. I still see the TugaPower boot logo and it still goes to the blank black screen after this.