Aight, so here's what happened, installed a custom boot animation, but it's in a loop, it keeps playing, cold boot doesn't work, recovery gives me the dead android, can't rly acces my tab in any way. The only thing I can do right now is getting it recognized as fastboot, everything else I tried results in my Hardware manager not even recognizing my tablet.
I got a rooted JB, not unlocked.
Rly got no idea what to do now, is it perma bricked or can I find a way out again?
Update: just left it bootlooping while I went for a spliff and voila, seems like it's done a factory reset or so
Looks like i lost EVERYTHING on the tablet but seems like it's working again, probably lost root etc though :/
Update 2: google is reinstalling all my apps now, gonna take a while
Update 3: at first looks, I still got root, rootchecker says I still have root, don't know what should happen with like ES file explorer if I don't have root but so far it all seems to work. Got it figured out what happened too, it wasn't a boot loop, it was just the custom animation that sorta ****ed up and kept rolling, I then started a recovery but didn't let it finish, so when I finally decided to stop tampering and just let the battery die out, it had enough time to actually finish that recovery.
Update 4: first reboot got me again, still the same animation, well, let's hope I still got root after next recovery, so I can fix that.
Update 5: all is good again, besides that everything from tab is gone, aah well, kinda wanted a fresh start with jb anyway
Hi guys...thanks for taking a minute to help me out.
I have been using the Cyanogenmod Nightlies for a few months, and have recently been experiencing a few random quirks since upgrading to the new version of Android. I decided that I'd do a full wipe and then install the new nightly. Everything worked fine, the phone booted, I could use apps, etc. Then, I decided to restore some of my apps and data from Titanium Backup.
It took about 40 minutes, and then finally got stuck on 98% which was "android data" or "system data" or something like that...i checked back a few minutes later and the phone was completely dead/frozen. I eventually pulled the battery and rebooted the phone, and now it's just stuck in a bootloop.
When I try to boot into recovery, it freezes on the "Samsung Galaxy S3" screen for a while, and then turns off. However, i CAN boot into download mode.
Can someone please point me in the right direction here? I know that android 4.2.2 reworks some of the system folders, making reverting back to a previous version difficult..? I don't know what to do. Really, I just need to be able to get into recovery, but I'm too ignorant to figure it out.
Thanks so much for taking the time to help me, it's very much appreciated!
hold tight, guys! for some reason, it booted into recovery after like the 50th try. hopefully i can figure it out from here! thanks
question. installing rls13 on verizon gs3. picked my own options. started loading rom and it stuck on installing aosp 4.2 keyboard. at 30%. can i restart phone or not. dont want to screw it up. flashed a lot but never had this happen. and yes i wiped
jjean0407 said:
question. installing rls13 on verizon gs3. picked my own options. started loading rom and it stuck on installing aosp 4.2 keyboard. at 30%. can i restart phone or not. dont want to screw it up. flashed a lot but never had this happen. and yes i wiped
Click to expand...
Click to collapse
Either hold the power button for about 10 seconds until it reboots, or pull the battery and boot into recovery. This is a problem with AROMA and it occasionally takes a few tries to get the flash done.
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.
Hello all!
Just got my One +1 today and I have an odd problem with it. Whenever I try to reboot it or reboot to install an update, it hangs up at the One +1 boot screen. I have to shut the phone down for a few minutes before it will start up again and it won't install updates to CM. So far I've tried going into Fastboot (hangs up at CM logo), factory reset (hangs up at One +1 logo), and even just plain reboot (One +1) logo.
It seems to work fine otherwise and I can power off and power back on again, but this is more than annoying. Has anyone encountered this before and have any wisdom to share so I can get past this?
Well, it seems to have fixed itself somehow.. Not exactly sure what went right, but there is hope if anyone else has the same problem.