Hello,
I have a problem where around once a month or so my unit gets stuck on the Android boot animation and I am forced to do a factory reset to get it working again.
Has anyone else had a similar problem or an idea how to fix this?
Or do you think my unit is faulty perhaps?
Thanks in advance!
Did you fix the problem or?
If u havent fixed it yet, give me some info about your unit..
Let me know and I'll help u with it
---------- Post added at 10:30 PM ---------- Previous post was at 10:30 PM ----------
Did you fix the problem or?
If u haven't fixed it yet, give me some info about your unit..
Let me know and I'll help u with it
Not sure if the OP fixed their problem or not, but I have a very similar issue.
RK3188 Joying 1024x600 16GB
Original ROM ran fine. Updated MCU and ROM from Joying just fine but then decided to go with ROM from Malaysk (2/12/2016).
Originally selected Update System from Settings Menu and it seemed to be going well, but when it rebooted to run the ROM it is stuck at the animated logo. The initial screen shows the Malaysk artwork, but then goes to the animated logo and does not display the "Updating Android Apps" as I would expect.
I have ran the update process 4-5 times in a row, I have done the factory erase before installing, and have tried both option 2 and 3 in the recovery mode. Nothing or combination of anything seems to work.
I can restore the Joying updated ROM if I do a factory clear and then put the Joying ROM on the SD card.
Greatly appreciate any suggestions on what I might be doing wrong.
Hi I have the same problem after updating malayke 11.4 it worked for couple days and then got stuck with the logo, tried reset didn't work then recovery update wipe all the steps it shows updating and then black screen after reboot, any solution ????
Related
Hi,
a friend of mine had an issue with his Gnote 3 Neo (N7505XEF). Restart again and again and again.
I saw it and I said that I was able to fix it.
Went to recovery, wipe data/cache.
Reboot, and phone starts an update of sytem.
Before the end, bootloop on "galaxy note 3 lite" screen. Noway to have "samsung" bootanimation.
I ask him if he had installed an app recently. No for 4/5 days, and no issue since.
An OTA came sometimes ago and no issue with it.
So, I took his phone and expect to flash a stock firmware with odin. That what I've done with latest french firmware (5.1.1)
Reboot and.... bootloop
Sometimes, bootanimation "samsung" appears but doesn't go to the end of process, and restart the phone in "galaxy note 3 lite".
I wiped everything, test some others firmwares from 4.4.2 to 5.1.1.
I can always enter recovery and download mode, but the issue is usually the same, bootanimation doesn't finish.
I search everywhere but found nothing.
I remember with my old Gnote 2 that I had to install stock recovery once to solve a starting problem, but here, I can enter recovery, so I don't think that it is the same error.
Perhaps a kernel issue? I don't know, and I can't find them on the web!!
The phone has always been full stock, with no tweaks (root, custom recovery or rom....) The issue arrives without any signs. Hardware problem? Perhaps, but never been drown or wet....
What do you think I can do to solve this? Cause at the moment, I don't see haw I can!!
Thanks for all.
Yoh from France.
Excuse my bad english.
Keep trying and making a factory reset could help after installing a new rom. But I can't see more things.
Excuse my english, I'm french
Hello,
I really need your help and expertise.
I got the notification that I needed to update my N7 with the latest OTA security updates. I let it do its thing and noticed after some time that it was stuck on the Google logo. I tried restarting but nothing would work. I read what I could about some people tapping the back of their units and then working again but that unfortunately didn't work for me. I tried to start in recovery mode but that didn't work and then the power plus vol up. It tried to finish installing the update. But I soon got an error message with the Android guy laying on its back with a red arrow on its stomach saying only "Error" nothing more or less. Not sure what to do next, I tried to find info on suggestions but after about 5 minutes, it seemed to try to reboot and went right back to getting stuck on the Google logo.
I've never had any issues with this. It's stock (no root) and had the Marshmallow update on it running just fine. It's completely unusable now and I have no idea what to do to try to fix this. Any suggestions would be really helpful. Thanks so much!
Please post the output of:
fastboot format cache
but if the response is "FAILED (command write failed)" then let's discuss it in the thread linked in my signature.
use nrt, would solve your problem.
---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------
download the stock firmware latest and flash it either on fastboot or use nrt instead.
I had TWRP 2.8.7.0 working fine, but tried upgrading to 3.0 -
That had a weird issue where twrp would show the splash screen, the screen would intermittently turn off and on, and keep showing the splash screen, but never entered recovery.
Decided to revert to 2.8.7.0 using flashify... Now when I try to create a nandroid backup in 2.8.7.0, it starts working and then shows the twrp splash screen, and as in 3.0 the screen intermittently turns on and off.
Anyone experienced something like this before? Kind of unsure how to proceed.
Update: now it does the screen intermittently flashing on and off, stuck on twrp flash screen just trying to enter twrp.
Also tried removing SD-Card with no luck
Update2: The behavior is pretty much identical to what's seen in this video https://www.youtube.com/watch?v=Kr46ugrpL6U , except it only happens in recovery (I can enter the os normally if i dont attempt to go into recovery)
This has been common problem with twrp from the looks of it. Right now when I boot to twrp 2.7.x.x I get stuck at the twrp splash. However my problem I can't find any info on your there looks to be two terminal commands you can run to fix it..... Seeing this post I wanted to ask about mine at the same time couldn't hurt do to its starting to look related to the recovery boot loop. But like I said I'm just stuck at it not looping.... very odd.
---------- Post added at 03:14 PM ---------- Previous post was at 03:02 PM ----------
OK mine was sad and simple.... I formatted my SD card back to portable storage and poof it now boots to recovery don't know if it could be related but it's worth a shot!
cmjester6421 said:
This has been common problem with twrp from the looks of it. Right now when I boot to twrp 2.7.x.x I get stuck at the twrp splash. However my problem I can't find any info on your there looks to be two terminal commands you can run to fix it..... Seeing this post I wanted to ask about mine at the same time couldn't hurt do to its starting to look related to the recovery boot loop. But like I said I'm just stuck at it not looping.... very odd.
---------- Post added at 03:14 PM ---------- Previous post was at 03:02 PM ----------
OK mine was sad and simple.... I formatted my SD card back to portable storage and poof it now boots to recovery don't know if it could be related but it's worth a shot!
Click to expand...
Click to collapse
Unfortunately I don't think it's the same, because I still have issues even with the SD card removed. Also, I'm on lollipop if that helps.
I remember that happened once to me in a Samsung device. But eve worst, my device was unable to boot into OS. What I did was put download mode and flashed any version that was easy to root. Then, root, flash recovery TWRP, and then used a nandroid backup. You can apply same procedure on this LG G3 and you'll be back on the game.
Enviado desde mi LG-D851 mediante Tapatalk
Need some guidance on this one. Went through trying to root my Note 4. Upgraded from 4.4.4 to 5.1.1 after all this time waiting. From there, continually hitting soft bricks (referring to endless boot loop in regards to soft brick) and a lot of the issue I believe to be my battery. However, was originally able to flash the 5.1.1 FW (N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar.md5) and the brick would be remedied. At this point however, the note just goes into a endless boot loop where only thing it displays is the "Samsung Galaxy Note 4 Powered by Android" splashscreen (Never displays the oval samsung or verizon splashscreens) and vibrates twice as the screen display goes off for about 3 secs and pops back up with the same screen over again. At this point, the only thing I have found to remedy this is the Verizon Software Update program, which instantly updates to 6.0.1 (newest FW). This wouldn't be an issue, with the exception that the 5.1.1 FW still puts the phone into the soft brick state. Anyone have an idea why the FW is now putting into a brick and how to fix the issue so I can downgrade successfully?
In case it matters, to get the Verizon program to work, I would flash "N910VVRU2BPA1_StockRestore.tar.md5" via Odin and from there, download mode would then populate a screen stating update failed and to utilize the program. Seems to be the only way to get it to be able to connect.
Also, with all that said, the one thing I have thought about doing, but haven't is re-partitioning with a PIT file. However, I have not come across any threads on re-partitioning the Note 4 and those that refer state not to. With that said, I wouldn't mind attempting it if someone else feels like it may work. If so, please lead me to a thread with instructions along with a correct PIT file in order to run through the process please.
hey man I'm actually running into a similar issue. Ran into it while attempting to Root via Kingroot on 5.0.1 I was following a guide, the phone rebooted on it's own during the process and didn't have any issues rebooting, but at one point I wanted to reboot and instead of pulling the battery like normal, I decided to press the reboot option in the power menu, bad idea, now I'm bricked and Odining PA1 is not allowing a proper boot... have you found a solution to your problem? maybe it would help me with mine
---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------
well after a really long battery pull, its booting up for me, I hope you were able to resolve this issue
Hello, i hope im posting in the right place, i have a flyaudio head unit running 5.1.1, after trying to unlock it it with a custom firmware, it made automatic recovery update, now its on loop between two screens one black one white and its says loading recovery, system obviously not booting, is there any way to access fastboot or someway to fix this ?
Nothing seems to work Please Help
Ivgeniport said:
Hello, i hope im posting in the right place, i have a flyaudio head unit running 5.1.1, after trying to unlock it it with a custom firmware, it made automatic recovery update, now its on loop between two screens one black one white and its says loading recovery, system obviously not booting, is there any way to access fastboot or someway to fix this ?
Nothing seems to work Please Help
Click to expand...
Click to collapse
No fix,
Go to Gil-Cal and replace it.
Tell them you have no idea what happened
connect a keyboard and hit alt + print screen + e repeatedly, hopefully will tell you update failed and will roll you back. Good luck. Be persistent.
same to me atl+ not work