I had 4 min till work and I decided to compile bootanimation zip really quickly.... 19 Frames... done with bootanimation factory. Used Rom toolbox pro to install it... rebooted...
Then this happened:
* Bootloop pre- bootani
--- Pulled battery
*Bootloop stopped, phone booted into rom (screen black)
I wasnt sure but the buttons turned on. on the bottom.... so I pulled battery out
After work-
* While waiting for ride I pulled battery decided to leave it with battery on and blank screen. I tapped vol up and sound went up... I actually kept getting my text message notifications and I received a call! Which I was able to answer with swiping....
After that, I dirtyflashed to get rom working once i was home which worked...but menu was a little laggy so I did nandroid and then did full wipe, reflash and restored. because usb doesn't mount until your in OS (if you have pin/pass) I had to guess location of digits on the screen which gladly worked in 1 shot to even put the zips on the external card to fix the phone)
EVERYTHING WORKED, Except the screen once it passed Samsung Boot sequence....its freaky
Its just really a mystery to me how bootanimation could muck things up like that.
nxneko said:
I had 4 min till work and I decided to compile bootanimation zip really quickly.... 19 Frames... done with bootanimation factory. Used Rom toolbox pro to install it... rebooted...
Then this happened:
* Bootloop pre- bootani
--- Pulled battery
*Bootloop stopped, phone booted into rom (screen black)
I wasnt sure but the buttons turned on. on the bottom.... so I pulled battery out
After work-
* While waiting for ride I pulled battery decided to leave it with battery on and blank screen. I tapped vol up and sound went up... I actually kept getting my text message notifications and I received a call! Which I was able to answer with swiping....
After that, I dirtyflashed to get rom working once i was home which worked...but menu was a little laggy so I did nandroid and then did full wipe, reflash and restored. because usb doesn't mount until your in OS (if you have pin/pass) I had to guess location of digits on the screen which gladly worked in 1 shot to even put the zips on the external card to fix the phone)
EVERYTHING WORKED, Except the screen once it passed Samsung Boot sequence....its freaky
Its just really a mystery to me how bootanimation could muck things up like that.
Click to expand...
Click to collapse
Odd. It's entirely possible that it's a coincidence, and unrelated to the boot animation. It might have done that on reboot even if you didn't change anything (to my knowledge, the boot animation can't do that.) It's kind of like a lot of the people I see who are saying rebooting and wiping cache/dalivk fixed so and so issue, when the reboot alone would've done it. I've had that happen to me on a few aosp roms, usually requiring a restore or new install, and didn't touch the boot animation.
Related
The problem only happens when I reboot or turn on the phone. When it boots up, I get multiple results. A: It boots up normally (not a problem) B: When it gets to the samsung screen, it freaks out and reboots itself again and again. It's like it's struggling to boot up. One time it got to the gs 3, but then it looped back. C: This just happened today. I booted up and it went pass the samsung screen but when it got to the gs 3 screen, the screen turned a faint pink and it stayed on that screen.
This just happened right after version 8. I know 10 was messed up but on 9 and 11, this problem persisted. Also,I don't think the issue is the phone, since I don't have this problem on other Roms. If I'm wrong please let me know .
Any suggestions, advice, help, etc is welcomed.
Please... i really need help.
I suggest you start over, this will remove any corruption and gremlins you have klinging to your phone..
http://forum.xda-developers.com/showthread.php?t=1904099.. Then re root and flash anew.
Naddict said:
I suggest you start over, this will remove any corruption and gremlins you have klinging to your phone..
http://forum.xda-developers.com/showthread.php?t=1904099.. Then re root and flash anew.
Click to expand...
Click to collapse
I unrooted, went back to stock, it did a factory reset so no bugs should have been alive. I re-rooted, made a backup, did a factory reset and wiped dalvik, then I flashed the rom zip and rebooted. It gets stuck on the Gs III screen. I waited like 5 minutes and it didn't move. My battery was at 50% so I just put it on the charger and tried to boot up and it went through to the set up screen for gmail.Just to see if it was coincedental, I did another reboot but this time it got stuck again. It sounds like a system problem but i'm not sure.Like i said earlier, this only happens on Jellybomb.
Any other ideas?
Edit: I've tried switching recoveries but it doesn't fix it.
Sigh.
it was normally working at night. I turned off the screen and went to sleep. the battery was about 90%
When i woke up,i found that the screen was lit. it was a little dark blue-ish. The phone did not respond to anything i do !
I made a battery pull and tried to reboot. the same dark blue-ish screen appeared again, the kernel's logo never shows up. i tried to charge it for a while then turning it on. the kernel's Logo appeared. I can now access both CWM and TWRP. but when it's turn for the boot animation. the dark blue screen pops in again
any ideas ??
Specs: Xperia Pro
ROM: Ultimate HD v2.0.3
Kernel: E-kernel (the dual recovery one)
MODS installed:
uHD MOD v2.4
Cybershot
walkman
Recharge it for a while
Try to clead cache and dalvik, fix permissions, try to boot
If it dont work, then change your kernel and try to boot.
If it dont work, revert back to a old backup or flash a stock rom
Thanks for your help.
I fixed it by formatting the system partition and reflashing the rom.
Now it's all good
if at some point the kernel logo doesn't show up, I'd put my two cents on the kernel for an issue... just saying... but as long as you are able to still connect the phone in fastboot mode, you can always try flashing a kernel to recover it.
Just saying. ... good you figured it out.
atmos929 said:
if at some point the kernel logo doesn't show up, I'd put my two cents on the kernel for an issue... just saying... but as long as you are able to still connect the phone in fastboot mode, you can always try flashing a kernel to recover it.
Just saying. ... good you figured it out.
Click to expand...
Click to collapse
I don't think it was a problem with the kernel.
At first the kernel's logo didn't show up because the mobile was low on battery. The screen was lit the whole night. When I charged it a little the kernel booted normally and I accessed recovery without any issues.
I really don't know what the heck happened.
The only thing the mobile should do at night is backing up apps with titanium backup.
I'll try to see if any apps didn't get backed up. Maybe it hangs on a certain app...
Sent from my Sony Xperia Pro using Tapatalk 2
Hi, I have been running JellyTime 4.2 R11 for few weeks now on my S-OFF Desire HD.
Today, I noticed that the light was blinking and battery was low 6%, so I decided to put it into charger, and somehow when I connected it soon I accidently disconnected the charger, and when I put it back, the phone probably crashed or something, since it went black and the white screen with HTC logo appeared and it started to boot again. Now, JellyTime tries to boot, the bootanimation goes fine for sometime but then it gets stuck after "playing" the bootanimation for a while, nothing happens, even if I wait 5 minutes, it's stuck, bootanimation is frozen, no matter do I have the charger connected or not.
So, is there anything I could do, or is reflashing the only solution? I did full wipe when I flashed the ROM.
If you need more information, sure, just ask.
You could try dirty flashing, but if that doesn't work you'll have to reflash.
bananagranola said:
You could try dirty flashing, but if that doesn't work you'll have to reflash.
Click to expand...
Click to collapse
Thanks for the tip, but it didn't help, gets stuck still on bootanimation.
Time to full wipe and flash it again then. Wipe&FlashTime
Happened to me a few times. I suggest a battery pull before anything else. Seems stupid. But it can work in some cases
- Sent from Guy's Super Duper S3
GuyInTheCorner said:
Happened to me a few times. I suggest a battery pull before anything else. Seems stupid. But it can work in some cases
- Sent from Guy's Super Duper S3
Click to expand...
Click to collapse
I did battery pull several times considering that the phone refused to shutdown even when holding the power button for 10 secs, so battery pull was needed every time.
Anyway, it's now running fine when I reflashed.
910263 said:
Hi, I have been running JellyTime 4.2 R11 for few weeks now on my S-OFF Desire HD.
Today, I noticed that the light was blinking and battery was low 6%, so I decided to put it into charger, and somehow when I connected it soon I accidently disconnected the charger, and when I put it back, the phone probably crashed or something, since it went black and the white screen with HTC logo appeared and it started to boot again. Now, JellyTime tries to boot, the bootanimation goes fine for sometime but then it gets stuck after "playing" the bootanimation for a while, nothing happens, even if I wait 5 minutes, it's stuck, bootanimation is frozen, no matter do I have the charger connected or not.
So, is there anything I could do, or is reflashing the only solution? I did full wipe when I flashed the ROM.
If you need more information, sure, just ask.
Click to expand...
Click to collapse
I have the same problem since a crash on opening the outlook-email App (JellyTime 4.2 R9).
I found, that the "data" partition causes the trouble when booting. Formating the "data" partition with "4ext recovery" fixes boot-freezing. But this is not an option for me as my last (working) backup is a couple of months ago (yes, I know - should backup more frequently...).
I was able to backup the up-to-date "data" partition (with 4ext recovery) but when restoring it (even on an fully wiped and updated system) boot sequence freezes again.
Any ideas???
Many thanks!
Solved the problem with the data-backup. Instead of restoring complete partition the APP "AppExtractor" works fine for restoring data of the partition backuped.
For now, system runs perfectly.
Conclusion:
If system hangs in Boot-Animation use Recovery for backup of up-to-date system. Full wipe system and install ROM of your choise. After that restore SMS, contacts, etc. with "AppExtractor". Apps should be installed from PlayStore as far as possible. "AppExtractor" allows restoring of app, data+app, data.
So I feel like this is different from a typical bootloop (certainly different from ones I've had in the past). Any ideas short of factory reset would be very much appreciated. I just need it to load once more to do a Titanium Backup (and I guess I should install TWRP and do a nandroid backup)!
I've been using my Tab Pro for years now, rooted, works perfectly, and I always leave it on. I thought yesterday, perhaps this is a bad idea, I should turn it off every once in a while. But I wanted to play a game before I did. I click the game icon and then everything froze and it restarted itself.
It gets stuck at the SAMSUNG logo page. Sounds like a typical bootloop. After 20 minutes of waiting, nothing changes, so I hold down the power button and it restarts and actually loads to my home screen! Great! I swipe the screen lock, click on my game -- it restarts, rinse, repeat. Each time it restarts itself it stops at the SAMSUNG page, forcing a second manual reboot that fully loads, but doesn't go 10 seconds before restarting. I try to load different things each time and finally give up.
So I look some stuff up online. There's a suggestion to go into recovery (I could've sworn I had custom, but apparently not?) and "Wipe Cache/Partition." I look up that this is safe and do it (Sidenote: Power+Home+Vol Up only works around every 5th try or so. It glitches out every other time, there's a quick flash and a horizontal line and it restarts again). Now I restart and it worked! It loads and no reboot!
But now, a third of my apps/games have the android guy as an icon and even more of the real icons are all grayed out. I figure one more restart and it would come back. Now I'm back into my weird bootloop. I try wiping cache/partition again and again and it no longer works as a solution...
TL;DR - Tablet keeps restarting to SAMSUNG logo, requires 2nd manual restart. Home screen loads, but then restarts 10 seconds later. Clearing cache/partition made things worse. HALP!
EDIT: My current build is KOT49H.T520XXUANAE. I can't even find the stock ROM for this! Does it exist?
EDIT 2: After letting it charge for an hour (it was already 93%) I went back to it and it had loaded! But the home screen was blank save for the Google search and the Apps icon (which found no apps....). I was able to get into settings and attempted to click Application Manager and then it froze again.
Update: Still in need of help if anyone has any. A wonderful person on the forums linked me to my stock ROM, I pushed that through ODIN, it worked and did the "Android is Updating App XX of 200" thing.
It loaded and didn't crash! Most of the icons came back, but were still grayed out (I have a second partition via Link2SD which, when not rooted, doesn't load!)
So I went to Settings to see if USB debugging was enabled... and it froze. Kind of. It let me bring up the task bar and close settings, but not reload anything. Eventually I was forced to restart because I couldn't do anything. I tried booting into safe mode and still nothing.
Now when it loads, I get repeated "Unfortunately, Samsung keyboard has stopped working." and then the touch screen stops functioning and it restarts. I'm having a great day.
hamstrman said:
Update: Still in need of help if anyone has any. A wonderful person on the forums linked me to my stock ROM, I pushed that through ODIN, it worked and did the "Android is Updating App XX of 200" thing.
It loaded and didn't crash! Most of the icons came back, but were still grayed out (I have a second partition via Link2SD which, when not rooted, doesn't load!)
So I went to Settings to see if USB debugging was enabled... and it froze. Kind of. It let me bring up the task bar and close settings, but not reload anything. Eventually I was forced to restart because I couldn't do anything. I tried booting into safe mode and still nothing.
Now when it loads, I get repeated "Unfortunately, Samsung keyboard has stopped working." and then the touch screen stops functioning and it restarts. I'm having a great day.
Click to expand...
Click to collapse
Few of this probs I did have too.
I would recommend to start from scratch and wipe also your data and sd-card (with TWRP). Install either stock or Custom, but put out your sdcard before re-booting.
Just play around and after that (with no probs hopefully) insert it again.
starbright_ said:
Few of this probs I did have too.
I would recommend to start from scratch and wipe also your data and sd-card (with TWRP). Install either stock or Custom, but put out your sdcard before re-booting.
Just play around and after that (with no probs hopefully) insert it again.
Click to expand...
Click to collapse
I appreciate the response, but as I said, I'm looking for anything shy of factory reset. If I lose all of my apps and data and configuration, I might as well throw out the tablet and buy a new one.
Still trying to figure out the pattern. I got another attempt of it not restarting for 10 full minutes. The keyboard failing is annoying because it doesn't stop, but I can live with it if it means being able to backup my tablet with Titanium Backup. I only got 6 apps backed up before it froze, but I'll get through all of them eventually (I hope). It's just going to be incredibly frustrating.
A few months ago, the display broke on my Moto Z Play. It took me awhile, but I finally got a replacement display.
During the time I was not using it (starting immediately after it broke) it would make the sounds for my calendar notifications as they would come up, and continued to do so until the battery died.
While the battery was dead, I carefully took off the remnants of the old broken LCD.
About two weeks before I got the new display, I plugged it into my computer to see if I could pull any of my information off of it. Unfortunately, I was unable to get it to show up as a drive on my computer so I couldn't pull anything off of it.
Since it had power, it once again made sounds for my calendar notifications until the battery died.
I got my new display in the mail a couple days ago. I set about installing it and after I was done, I charged the battery to 96%. The charging screen appeared perfectly normal. I had no indication that there was going to be any problem when I went to use it until I powered it on at 96%. It looked like it was going to boot up just fine and made it three screens (not counting the triangle screen) into the boot up process and restarted the process.
The last time the phone was fully functional (as well as while it was on with a broken LCD) it was running OmniROM and it has TWRP 3.2.1-0 recovery on it.
First I tried clearing the cache and dalvik cache. That didn't help. Then, as I keep a copy of the zip for that ROM on my SD card, I decided to reflash OmniROM and 8.1 gapps. That didn't help. So, I decided to do a nandroid backup. It got part of the way through the back up and failed at system image. So, I decided to try to backup my data so that I can at least hopefully restore some of it at a later date on my computer or something. Thankfully, I was able to successfully backup my data partition.
After the backup finished, I decided to attempt to dirty flash CosmicOS.
However, I experienced the same boot loop.
I then did a full wipe and did a clean flash of OmniROM.
Still: the triangle screen, 3 seconds of the boot process and then it starts over again.
I am lost as to what to do now.
Help!
Hello?...