I was playing around with build.prop file. After having a few successful boots i have added some more lines (sadly i dont remember what). This time i got an infinite boot animation, my tablet got too hot and i turned it off/. Since then it doesn't start at all. I have got a backup but i don't know how to apply it now. Would be thankfull for any help.
Related
hi there! I'm kind of new here so bare with me please!
so I recently rooted my Samsung Galaxy Note 2014 edition, and immediately went in and started messing around with the boot animations,I went in and accidentally got rid of the shutdown.qmg file but I thought I found a replacement one on this http://forum.xda-developers.com/showthread.php?t=1696903 form. unfortunately, it did not work and now my tablet refuses to shutdown or restart.every time I attempt to shutdown or restart it gives me a black screen for about 30 seconds before turning back on and going to the lock screen. it would be great if I could shut down my tablet again without having to reset the whole thing.
Thanks!
silverarrow66 said:
hi there! I'm kind of new here so bare with me please!
so I recently rooted my Samsung Galaxy Note 2014 edition, and immediately went in and started messing around with the boot animations,I went in and accidentally got rid of the shutdown.qmg file but I thought I found a replacement one on this http://forum.xda-developers.com/showthread.php?t=1696903 form. unfortunately, it did not work and now my tablet refuses to shutdown or restart.every time I attempt to shutdown or restart it gives me a black screen for about 30 seconds before turning back on and going to the lock screen. it would be great if I could shut down my tablet again without having to reset the whole thing.
Thanks!
Click to expand...
Click to collapse
Not sure what the problem is but what i would do is try to flash this tab s boot animation here. This is the one i use for my note.I do think i had this problem before and i couldnt figure out what is was and had to flash my rom over again. It wont hurt to try to flash this as it wont make anything worse.
http://forum.xda-developers.com/showthread.php?t=2779982
Try go to each of the qmg files and change their permissions or all read write and execute. I had the same problem
As the title says my s3 took a dump on my today. Its stuck on boot loop it gets as far as the Samsung logo that glows bluish. It also can go to the part where it has the android guy and says downloading. This is weird because I was using it 10 as my gps minutes earlier totally fine. No i didnt do anything to it, its not rooted nor did i attempt too, it just happened to me while i was on groupme. Is there anything i ca n do to fix this issue in a way that doesnt involve a factory reset(i want to at least save some of my texts,notes,contacts, and pics)
I'm having problems getting my phone past the bootup screen. It first loads the logo then goes to the animated logo then the rethink possible animation and then finally gets stuck on the glowing samsung logo. It then shuts off and redoes the loop a couple of times until it stops with the battery charge up screen and freezes there until I remove the battery.
History: Purchased an att phone for the mb to replace my original phones because it had the insane chip. Had to root it to be able to unlock the phone with my carrier(telus). Since I was in it I flash the DN4 custom rom and everything needed into the phone. The phone functioned fine for about a month and then frequent freezes and restarts started happening. Near the end, the phone was stuck in a boot loop, loading into the DN4 animation boot screen then shutting itself off then on again to endlessly repeat the loop.
Present: At first I was able to get into TWRP and tried some things in there but nothing happened. When there I notice it stated "internal memory 0"-not sure if this means anything.
I was able to flash the saved recovery file from TWRP. Once I did that I could no longer go in TWRP and now have to use the samsung install/recovery.
I have since flashed the stock rom several times with odin and also wiped data/factory reset many times still does the same in bootup. Tried flashing TWRP into phone using odin 3.07 but failed.
What should be my next move? Pretty new at this so I may be missing something very simple or perhaps a dead phone???
Finally got the phone to boot up and run fine. It seems everything was good except the battery was acting up.
Next step is to get the battery to charge when phone is off.
I'll post this question in new thread.
My Nexus 7 2013 tab is stuck on boot animation and not switching on thereafter. I installed a custom rom after flasing TWRP RECOVERY 3.0.2 via P.C and thereafter using the TWRP.
The installation process is successful each time but wont go further than the boot screen. I waited for almost an hour . Evem the Gapps zip is not installing and giving error on log saying that file not mapped. Any way out of this mess? Does it have anything to do with my process? ...I advance wipe the system , data and cache before flashing and the file.
Don't know if you ever figured this out, but last night, mine froze while the kids were playing a game. I couldn't do anything at all. I had to hold the power button down for a while and it finally shut down. I charged it overnight, and all I could get it to do was display the Google screen. I searched and searched for a solution, and the only crazy thing that actually worked was to give it a good whack! I don't know why, but as soon as I smacked it (not on the glass!!), it booted right up as normal. Very odd.
joskur98 said:
My Nexus 7 2013 tab is stuck on boot animation and not switching on thereafter. I installed a custom rom after flasing TWRP RECOVERY 3.0.2 via P.C and thereafter using the TWRP.
The installation process is successful each time but wont go further than the boot screen. I waited for almost an hour . Evem the Gapps zip is not installing and giving error on log saying that file not mapped. Any way out of this mess? Does it have anything to do with my process? ...I advance wipe the system , data and cache before flashing and the file.
Click to expand...
Click to collapse
Which rom? Do you use the right gapps? Flash the rom without gapps and look if it's booting
Don't know if you ever figured this out, but last night, mine froze while the kids were playing a game. I couldn't do anything at all. I had to hold the power button down for a while and it finally shut down. I charged it overnight, and all I could get it to do was display the Google screen. I searched and searched for a solution, and the only crazy thing that actually worked was to give it a good whack! I don't know why, but as soon as I smacked it (not on the glass!!), it booted right up as normal. Very odd.
Click to expand...
Click to collapse
Holy ****, this worked! Had the same problem last night for the first time (I used it until the battery drained and this morning I got the loop). Smacked it on the back and now it's fully on!
Shame I got desperate and did a factory reset first
i followed this guide
teamandroid.com/2016/03/08/update-tmobile-galaxy-note-2-t889-android-601-resurrection-remix-marshmallow-custom-rom/2/
and it worked perfectly until yesterday
the other day i looked at my phone and it formatted and restarted on its own. i didnt really lose much.
so i accepted it and reset up all my apps and such, and then when my phone died and i charged it
it got stuck in boot loop forever
i tried wiping both cache and reboot recovery it skips boot loop long enough to load up but as soon as i see my homescreen for a second it boot loops again.
so then i tried completely formatting the phone over which worked until this morning when i woke up my phone was dead. swapped batteries and turned it on. booom boot loop again.
is there any advice on what i should do?
im able to format it and get it working again if something needs installed etc
but i want to stop this from happening again
Q: is it possible that a certain app i downloaded is forcing the boot loop? i dont see why it would because ive had all the same apps for months and it just happened out of no where.
i appreciate any help, id just like to know why in the world its happening, and what the best course of action would be
im thinking maybe restore it back to factory firmware and unrooting and starting the process all over again
i seen something for 7.1 would that be better?