Database Users

[Q] Spontaneous bootloop on certain stock roms

Hello all,
This is yet another bootloop story, although I haven't found anything quite like it yet, hence the idea to post it here for reference and in case some of you have interesting ideas to explore...
This is gonna be a bit long, but TL;DR: After my phone got "spontaneously" stuck into a bootloop, I find that only the stock 4.2.2 rom works, and no other.
So, tuesday I get back home with an empty battery and a Nexus 4 (running latest OTA) that has switched itself of after a day of somehow intense usage. No worries, I plug the AC adapter, let it charge for a bit and switch it back on. Booting seems a bit long, but I have to take care of a few home chores so I let it do its thing before coming back to it a few hours later. Only to find it still displaying the animated nexus logo. After a few switch off/switch on cycles, I understand its pretty stuck and I need to be more radical about it. So I enter the bootloader menu, and OEM unlock the phone (I had never needed to do that) hoping the full wipe associated with that will clear things up.
Well, it didn't. So I guess I'll need to flash a stock rom, and so I do. Since 4.4 is available on Google's stock roms page I try that, the animated logo changes but the end result is the same. So I try again with the latest JB (4.3) and still the same result. I get more than a bit frustrated but it's late and I need some sleep.
The next day, I call Google's warranty desk in France. They tell me that since the phone fell a few month ago, they cannot take it under the warranty program, and so I have to ask LG. Knowing there's no reasoning that will get me past the clerk that answered the phone I hang up after saying I'll get back to them via snail mail. Which I'll probably do soon, because I'm very disappointed with the way that warranty desk works.
Once at work, everytime I have a few spare minutes, I try to reflash with a new tool just in case it does more than automate what I did manually (nexus root toolkit being the one I tried most). It doesn't change a thing and my phone is still a nice animated paperweight.
I don't know why I ended up trying that, but I finally tried flashing the original 4.2.2 rom, and lo and behold, my phone finally got to the SIM code screen ! Everything worked nice after that, so once back at home, I go for the offered OTA upgrade to 4.3. Well, guess what, back to paperweight. Before reflashing 4.2.2, I took the time to flash CWM and activate adb by modifying /system/build.prop in the 4.3 image. This showed a recurrent problem with "system_server" segfaulting at launch (and it might have been caused by hal_sensors_get_list not returning anything, I have no clue). Trying the same on 4.4 yielded the same result.
Back to 4.2.2 and everything works fine, but I get nagged by the OTA notification, and more than that I'm wondering if there's any hope I might understand and fix the problem with my phone.
So, ladies and gentlemen, any clue that would help me is very welcome !
I plan to try a CM rom this week-end to see if it has the same problems as the stock one, but I have little confidence it doesn't. My guess is I have a hardware problem that's non-critical except it triggers a bug in 4.3+...
Thanks for reading !
--
Alain Perry

Same case, mi phone is totally stock and stuck on logo

KRT16S: no luck
I only had the time to try KRT16S this week-end, and this latest update doesn't change a thing. Same symptoms. So I guess I'm stuck on JB 4.2 for the coming week...

[Q] Reboots after Lollipop

Verizon Note 3 here, I received the Lollipop ota today and thought no harm in taking it as I was already stuck without root on 4.4.4.
It worked ok for the first couple minutes, then a reboot, then same thing, about 5 minutes and a reboot. Sometimes ~2 minutes, seems using it in any situation made the reboots happen. I did a factory reset thinking that would clear things up. Unfortunately now it is even worse, as it's rebooting anywhere from the first touch to the screen, to about 15 seconds of activity, literally dozens of reboots.
I downloaded the update on my pc and installed via Odin hoping that the ota was just corrupted or some bad luck like that. Nothing changed at all.
It will idle after booting just fine, I just can't do much of anything, every touch of the screen feels like a roll of the dice. Every few reboots or so I can make it to settings maybe but haven't been able to actually change much of anything, not that it would seem to matter here.
I've flashed via Odin twice, cleared the cashe many times, factory reset 3 or 4 times. Am I screwed here? What else to try?
*UPDATE* I flashed back to 4.4.4 with Odin and no more issues. It appears that my device alone is completely incompatible with the new firmware.

I should also note that I tried airplane mode, safe mode, and removing the sd card with no improvements.

After hours of messing with this thing and nearly giving up, not half an hour after I post here for help, I seem to have found a solution, although hopefully not a permanent one. The problem was happening when I would touch the screen, not scrolling ever, but making selections. On a whim I turned off sound and bam, no crashes.
I would still love it if someone had some insight about this problem, or better yet a solution.
I'm not sure yet if it is just the keypress sound that is killing it, or all sounds. I never did have any issues with the stock keyboard clicks now that I think of it, only the menu press sound. In any case it's not every time it made the sound, just half the time or so. Anything anybody could add to this would be appreciated.
*Edit* Not a solution, but it did help.

Well it's not as stable as I'd hoped. More like before the first factory reset now, but still not good at all. The various sounds definitely trigger crashes quickly(menu options, volume pings, mp3 songs from sd card), but regular silenced menu presses do sometimes as well still. Phone also bootloops several times often before it can get booted stable and 100% always crashes immediately if I try to unlock the screen in the first 5-10 seconds after booting up. Not sure if I'll be able to call or text as it's too late to test that atm. I'll update tomorrow, any insight appreciated.

I would say a bad download but I don't remember if ODIN checks MD5 sums (pretty sure it does). I would do a full wipe and reflash the stock image with odin

I am 100% stock not rooted never been rooted 5.0 vzw and I have had a couple of reboots. Never ever had one on this phone before. My old note 3 was rooted but I got this replacement after the root exploits had all been closed.

ehh not all have been closed

What is the root exploit for Verizon Note 3 with 5.0?

recDNA said:
What is the root exploit for Verizon Note 3 with 5.0?
Click to expand...
Click to collapse
None at the current time but CVE-2014-8609 seems like it could be some use

I spoke too soon when I said the phone was usable now. At best 5 minutes of light use as anything seems to crash it now. I did get a fresh image and used it with Odin with exactly the same result which makes me think its my phones hardware or something. Just seems crazy that it was working just fine before the update. The reason I pushed to 4.4.4 and lost root is because my phone suddenly started an issue where it would crash when making or receiving calls. It wasn't caused by any new apps or anything, just out of nowhere. I tried everything then updated as a last resort, carelessly I went to 4.4.4 instead of staying at 4.4.2 and lost chance of root, but it solved the problem I was having. I wonder if the issue is related somehow.

I was able to odin back to 4.4.4 and it's working fine so far, I assumed that you would not be able to revert back like the last ota and just tried it as a nothing to lose last effort. This is very important news to anybody that is having major issues with 5.0. Maybe, just maybe I'll try it again if they make an update patch for reported issues.
But for now, 4.4.4 it is for me.

VZW Note 3 update to Lollipop
I just finished the Lollipop update and my phone is working great for the past 30 minutes. Seems a little slower then usual but have had no issues besides my phone locking up after downloading the update, may have been due to my phone running down to 14%, but after removing the battery for 20 secs and putting it back on, phone came back on, I plugged into charger and started the update. Will post later if I have any issues.

I have been trying unsuccessfully through odin to downgrade but it keeps failing in odin, I downloaded the official firmware from sammobile.

Just curious if u r tried reinstalling newer odin? Try different USB port and cable. At this point maybe even try different pc if u have access to 1

sm t337a suddenly started freezing ALOT, touchwiz

I have an At&t (though no at&t mobile service currently) Samsung tab 4 8inch. In the last few days it has started freezing SEVERAL times a day. it doesnot matter what app, its likely to freeze on any of them. I would say it probably happens most when Im backing out/exiting an app. When it freezes I can stilll shut screen off but when I turn it back on I am just where it froze -not lock screen, it wont acknowledge plugging charger in, and cant click restart. Touchwiz has stopped message may or may not come up, but I cannot click on it even if it does. The ONLY way I can shut it down then is down vol +power for about 15seconds. Then it restarts and may do it 5 minutes later or 5hours later.
It just started this suddenly. I also had not just installed anything.
If a custom ROM or something would fix it, I wouldnt mind doing that if someone could possibly give me the link(s) to 1 that works for this model and links to how to do so/what I need.
I dont know if it is related or not, but about 3 or 4 days before this started, by battery life & battery charging went suddenly TOTALLY to hell.
Please help me fix this irritating &aggravating problem. Thank you very much for your time &assistance!

There are no custom ROMs for the SM-T337A unfortunately. Is your tablet on KitKat or Lollipop and are you rooted?
You should back up your internal storage and then factory reset and wipe cache in stock recovery. If you are rooted, you should remove system apps that you don't need with titanium backup or something similar. If you are on KitKat you might want to consider either updating to lollipop or factory resetting and reflashing the stock KitKat firmware with Odin.

No im not rooted. However i would like to, but didnt know there was a method of rooting the t337a.
I cant seem to fins out how to find whether its lollipop or kitkat or what?

gdownloads said:
I cant seem to fins out how to find whether its lollipop or kitkat or what?
Click to expand...
Click to collapse
Settings > About device > Android version. If it says 4.4.2 it's kitkat, if it says 5.1.1 it's lollipop

Thanks for the help.
Yes its kitkat then because it says 4.4.2 . I think 1st I'll go ahead and search how to update it to Lollipop then go from there... Does that sound like a wise decision to you??

STOOPID Question: I went to the posts at bottom of your posts (granted, I didnt go thru all 59 pages, lol) but I have a brain-fart question... would I try to root and then update to lollipop or vice-versa??

I have found temp root for lollipop. Just look in the general section. As you wouldn't be able to ota lollipop while rooted anyways.

Reocurring Boot Loops, Hardware?

Hey all! I'm having a strange issue regarding boot looping that I can't seem to find an answer to on here or anywhere else, I hope you guys can help.
So my T-Mobile Samsung Galaxy S5 (SM-G900T), purchased in May 2014, while perusing Facebook the other day, randomly shut down in the middle of perfectly normal use and started bootlooping. I had never had the problem before. The device had been rooted for months (I forget what method I used) but it was running a stock Lollipop rom. The first thing I did was factory wipe and cache wipe through Android stock recovery. It worked!... for a couple hours. Then the bootloop started again.
I went and sought a new stock rom, believing that somehow mine had been corrupted, and flashed it via Odin. I also flashed TWRP. Clean wipes, new rom, dalvic/etc. wipes, and booted into stock Marshmallow. It worked!... for a couple hours. Then it started bootlooping again. I went into TWRP and tried to wipe just caches and whatnot, but it wouldn't start again. Long battery pulls sometimes allowed the phone to boot, but it started looping again after ~5-10 minutes.
So I installed the Twisted Lollipop but couldn't even get that to boot. I went back and found the earliest available firmware for my device (as I bought mine right after it came out) and flashed it. Wipe wipe flash wipe whatever, and a succesful boot. It was looking good! I was able to install a number of OTA updates. I was at Android 5.1 when I decided to call it a night and hold off on the further OTAs for today. Today I got up and got ready for work, all's well. As I'm getting ready to leave, I allow Google to update some apps, and begin installing Facebook, Spotify, Cap Metro (for my area's public transit system) and maybe something else, I don't remember. Anyway, as the updates are downloading or installing and I'm checking my email, boom, crash, bootloop.
What's going on here? I've never heard of hardware causing boot loops, but could it be that? I dropped my phone (although protected by a Spigen case) earlier this summer and it cracked the screen-- could it have messed with the motherboard in some substantial way? I had noticed it getting hotter and the battery lasting less than usual, but I attributed that to the device's age.
Any help, any advice, any direction you could give would be extremely appreciated. I don't have the capital to replace the phone right now, and I use it all the time. Thanks folks!

Lenovo A6000Plus Bootloop problem (Unrooted device)

Good day everyone, i am going to report my delicate and infuriating problem that has been haunting my head for two months
I'll describe my problem in extreme detail, hoping you guys able to identify this disaster.
My android phone is Lenovo A6000 Plus, i've bought it 2 years ago and it's running on latest Lollipop version 5.1.1 I never alter the system files, since i only use my phone for games and communications, and i'm not really into tinkering android's software. so i use my phone like a normal person, do the updates when the settings asked me, update the apps, etc. and this phone running smoothly in my service. i wanted to ask both WISDOM and HELP in this thread.
1. The Bootloop disaster symptoms started on april 2018, when the phone boot SLOWLY AS HELL, seriously.. it took about 1-2 hours to boot, and it also shows the (ANDROID IS UPGRADING 0/132 apps) like wtf? , i haven't update or install any new android apps before this symptom happened. So i leave my phone plugged in and wait it to complete the upgrade; then it worked normally as it should. Unfortunately, it happened EVERYTIME i turn my phone on, EVERY SINGLE TIME.. T_T. so i struggled to avoid my phone from running out from battery as i can. This symptom happened for 3 weeks and it got from bad to worse. I wonder what kind of problem is this?
2. The worse part came when my phone is running at high RAM usage, let's say, i game on my phone alot in my spare time, using the ram up to 1800mb everytime i play game or open chrome browser (Lenovo A6000 plus have 2GB ram). When i close/task manager the apps, my phone launcher wont appear normally as it should (long pressing bottom left button) and it FORCED me to restart the phone and suffer the 1-2 hour LONG BOOT. That's unusual, i cleaned my phone regularly (using cleanmaster) and preserve both of my internal and external storage with 3-4GB free space. I wonder what kind of curse is this?
3. So the bootloop disaster finally got me this May when i turn my phone off and tried to reboot. And... no Android is upgrading 0/132 showed up, i waited for 4 hours and reboot my phone again and again and again. And its finally STRANDED on BOOTLOOP :crying:
Im on panic mode when problem 3 happened, then i searched the almighty Google for help, and found that i can backup my data with TWRP recovery, so i do as it said, followed the guides and BACKED UP all of my data.
For once i felt relieved my data is now saved. Now onto the main problem.
I've had enough of this problem so i format the phone into factory reset, wipe the Dalvik ****s, cache, system and data. All of it. thus, making my phone virgin again.
4. Now im trying to resurrect my phone, and tried my effort by downloading Stock Lollipop 5.1.1 OS again along with its prerequisites. I tried to zip-install it using TWRP but it said that "has not switched carriers and cannot be upgraded" i scratched my head and searched almighty Google again then found that i need to do ####6430### thingy before doing that. umm.. so my phone domain need to be changed, how can i do that with a phone who can't boot? (I'm from Singapore btw). What did i do wrong?? did my phone just turned into useless BRICK? but i've read that bricked phone can't even start the recovery, yet my phone still able to start either with Lollipop stock recovery or TWRP (if i adb fastboot it with adb tools from .cmd), so it's not totally fuc.. uh., BRICKED and i got the chance to fix it.
TL;DR
So, Guys.. i desperately need help. i'm a peon both in work and college, and a dead phone will not make a great company for a person like me.
I searched for enlightments and breakthroughs but always ended up failed resurrecting my phone, can you guys PLEASE :crying: tell/give me a SAFE and WORKING walkthrough to re-install my Lenovo A6000 Plus with Lollipop 5.1.1? And does it running a custom OS like those Cynadrogen thingy is good and worthy enough to speed up my phone? is the chances of getting bricked is unavoidable when running custom OS? I thought its going to be easy like reinstalling Windows, but i was wrong.
FYI, my phone now is UNROOTED and running on TWRP 3.0.2 and i can easily revert it back to Lollipop stock recovery if needed (does it considered rooting if i install custom recovery?) I also need a valid info if my phone would never turn like this again if i resurrect it again.
PLEASE HELP ME PEOPLE
THANK YOU.. ! :highfive:

sevenvoldizm said:
Good day everyone, i am going to report my delicate and infuriating problem that has been haunting my head for two months
I'll describe my problem in extreme detail, hoping you guys able to identify this disaster.
My android phone is Lenovo A6000 Plus, i've bought it 2 years ago and it's running on latest Lollipop version 5.1.1 I never alter the system files, since i only use my phone for games and communications, and i'm not really into tinkering android's software. so i use my phone like a normal person, do the updates when the settings asked me, update the apps, etc. and this phone running smoothly in my service. i wanted to ask both WISDOM and HELP in this thread.
1. The Bootloop disaster symptoms started on april 2018, when the phone boot SLOWLY AS HELL, seriously.. it took about 1-2 hours to boot, and it also shows the (ANDROID IS UPGRADING 0/132 apps) like wtf? , i haven't update or install any new android apps before this symptom happened. So i leave my phone plugged in and wait it to complete the upgrade; then it worked normally as it should. Unfortunately, it happened EVERYTIME i turn my phone on, EVERY SINGLE TIME.. T_T. so i struggled to avoid my phone from running out from battery as i can. This symptom happened for 3 weeks and it got from bad to worse. I wonder what kind of problem is this?
2. The worse part came when my phone is running at high RAM usage, let's say, i game on my phone alot in my spare time, using the ram up to 1800mb everytime i play game or open chrome browser (Lenovo A6000 plus have 2GB ram). When i close/task manager the apps, my phone launcher wont appear normally as it should (long pressing bottom left button) and it FORCED me to restart the phone and suffer the 1-2 hour LONG BOOT. That's unusual, i cleaned my phone regularly (using cleanmaster) and preserve both of my internal and external storage with 3-4GB free space. I wonder what kind of curse is this?
3. So the bootloop disaster finally got me this May when i turn my phone off and tried to reboot. And... no Android is upgrading 0/132 showed up, i waited for 4 hours and reboot my phone again and again and again. And its finally STRANDED on BOOTLOOP :crying:
Im on panic mode when problem 3 happened, then i searched the almighty Google for help, and found that i can backup my data with TWRP recovery, so i do as it said, followed the guides and BACKED UP all of my data.
For once i felt relieved my data is now saved. Now onto the main problem.
I've had enough of this problem so i format the phone into factory reset, wipe the Dalvik ****s, cache, system and data. All of it. thus, making my phone virgin again.
4. Now im trying to resurrect my phone, and tried my effort by downloading Stock Lollipop 5.1.1 OS again along with its prerequisites. I tried to zip-install it using TWRP but it said that "has not switched carriers and cannot be upgraded" i scratched my head and searched almighty Google again then found that i need to do ####6430### thingy before doing that. umm.. so my phone domain need to be changed, how can i do that with a phone who can't boot? (I'm from Singapore btw). What did i do wrong?? did my phone just turned into useless BRICK? but i've read that bricked phone can't even start the recovery, yet my phone still able to start either with Lollipop stock recovery or TWRP (if i adb fastboot it with adb tools from .cmd), so it's not totally fuc.. uh., BRICKED and i got the chance to fix it.
TL;DR
So, Guys.. i desperately need help. i'm a peon both in work and college, and a dead phone will not make a great company for a person like me.
I searched for enlightments and breakthroughs but always ended up failed resurrecting my phone, can you guys PLEASE :crying: tell/give me a SAFE and WORKING walkthrough to re-install my Lenovo A6000 Plus with Lollipop 5.1.1? And does it running a custom OS like those Cynadrogen thingy is good and worthy enough to speed up my phone? is the chances of getting bricked is unavoidable when running custom OS? I thought its going to be easy like reinstalling Windows, but i was wrong.
FYI, my phone now is UNROOTED and running on TWRP 3.0.2 and i can easily revert it back to Lollipop stock recovery if needed (does it considered rooting if i install custom recovery?) I also need a valid info if my phone would never turn like this again if i resurrect it again.
PLEASE HELP ME PEOPLE
THANK YOU.. ! :highfive:
Click to expand...
Click to collapse
When 5.1.1 update arrived?
Okay lets get to the point. Just don't panic. You have the stock rom file, extract a file named 'system.zip'. Now go to TWRP, perform advance wipe (wipe dalvik, data, system and cache partitions) and flash that file from TWRP. You'll be on stock rom with a fresh new experience.
---------- Post added at 10:38 PM ---------- Previous post was at 10:33 PM ----------
Custom ROMs are amazing and far better than the stock lenovo rom. Believe me, no one here is using that crap stock rom. You just need some instructions to flash and your phone will get a new life. We are here to assist you.