hi there guys, I have an issue since a lot of time with my G2; basically when I restore a stock ROM sometimes it works fine sometimes it constantly reboot after caching the apps when it starts.. For example I had the issue in the past then successfully restore Lollipop stock and rooted it; now I'm not able to make it boot again
anyway I just flashed the tot 16 GB firmware available and I choose to use for once the BOARD Dl option there. The device booted up into a test mode, I pick the All test choice and so I noticed something interesting.. the only voice that seems to fail is the TA wrong one.. it says Fail next to it.. I searched for this TA thing and it seems to be a Trim Auto partition, maybe where there are DRM stuff, proprietary things to make things harder for people wanting to root. but to be honest I never heard of it before ten minutes ago!
I also searched for this partition of the 16 GB partition available but I'm not sure there's one.. Still if it's true it's a partition!
Do you have any clue about that?
Also I would like to ask if to flash recent ROMs (Oreo / Pie) is mandatory to upgrade to stock Lollipop before or even KK would be good...
Thanks a lot guys, hope you could help, I feel bad for my G2, even if in the meantime I upgraded to new devices it's still my little one!
I rec ently changed the digitizer touch screen on my LG Stylo 4. Every thing seemed fine then now will blink what ever screen your on (on /off) (on /off) continuously without being able to touch anything to get out . I have to unplug cable from battery /reconnect. Per back up and it's fine as long as it is not moved. As soon as I pick it up same thing. I'm ready to throw it in the street or let my pit bull have a new chew toy! Would you have any suggestions?
Related
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...
So this is my sad story..
I bought a second hand Samsung S4 (i337M Telcel) Unlocked, the day i got it, i tested in front of the seller everything was nice and smooth.. So i payed..
I was very excited and i proceed to make the Root proccess, at beginning i was having issues with the drivers and Odin, then i was able to fix it..
Anyways long story short i ended up with the ROOT, CYANOGENMOD CM11, and PHILZ 6.. The first day was working fine my cellphone.. (I must say i rooted in my life at least 4 devices even an S4 i9500 all of then with success and not a single problem.. Using them form months and even gears.. The latest was a Moto E..)
Ok so the i337M was working good since the first morning with the root, but in the afternoon it just turned off one time.. Was weird but i didnt pay much atention..
The second day i was listening music and suddenly it turned off, and since then the cellphone is not able to keep on for more than 10min..
Some times i can load the complete OS and ofter 2 min it turn off sometimes at the Samsung S4 logo turn off something i must say is that the Device every single time i turn it on, on the Samsung S4 screen says "kernel is not seandroid enforcing" in red letters, some people say it happens when the root process is not made correctly some says it normal because its rooted..
I already installed from Odin the Stock ROM from SamMobile, and the problem is exactly the same.. A friend of mine told me it could be the Logic Card AKA Motherboard.. But i want to believe its just a software problem.. Cuz' before i rooted cellphone was working..
- Download mode: Works like a charm not a single problem and basically its the only way i keep trying different options to install on the phone..
- Discovery mode: With CWM sometimes works good, sometimes it just turn off, with Philz runs good not turning off or something and its how i was able to wipe data, cache, dalvik, factory reset to the cellphone..
Im thinking in starting over like pretending i didnt do anything to the cellphone, try again the root, the rom, the PHILZ (dont know how to call it).. and hope for the best..
Any advice or reliable links where i can download the correct files for my S4 i337M.. You are basically the last reliable source i have to fix my S4 if you give up with me, then i must admit my cellphone has passed away ..
Hope you can help me thanks in advance and have an excellent day!!:laugh::good:
The first troubleshooting step (to determine if the issue is hardware or firmware related) is to flash back to stock with Odin. Since you have completed this step and find that the problem is still present, this suggests that it is a hardware problem.
I have seen a custom kernel cause sleep of death, which makes the phone appear to have turned off. But in those cases, flashing the stock kernel fixed the problem.
Perhaps you should see if you can return the phone to the seller for a full refund.
creepyncrawly said:
The first troubleshooting step (to determine if the issue is hardware or firmware related) is to flash back to stock with Odin. Since you have completed this step and find that the problem is still present, this suggests that it is a hardware problem.
I have seen a custom kernel cause sleep of death, which makes the phone appear to have turned off. But in those cases, flashing the stock kernel fixed the problem.
Perhaps you should see if you can return the phone to the seller for a full refund.
Click to expand...
Click to collapse
Thanks for your reply.. I still dont know how but with Philz recovery, i was able to make a full wipe, i mean it deletes everything every single folder previously made was erased, and i can tell you that because i have a folder called ROOM where i places my ROM, Kernel, etc.. So i can flash them in discovery..
So i erased everything and then proceeded to install via Odin the Stock Rom and guess what it works like a charm, not a single problem.. So, so far the cellphone is ok.. I tested for two hrs.. Now i tried to install a custom ROM and its doesnt load from the Samsung S4 screen jaja... But im still having acces to discovery and download mode so thats ok..
Just two advices.. Never ever download files from Youtube ****y links.. Always go to the source.. Youtubers are assholes.. Real help and information comes from real people that knows what they are talking about like this forum and also updated and real ROM's come from the main source not Mega o Linkbucks...
Other advice embrace your self to do it.. Study every single question you have in Android, from KERNEL to ROM and ROOT.. Isn't that difficult..
One more question, Which ROM with Lollipop would you suggest to install i have the i337M?
SUNDR1V3R said:
So i erased everything and then proceeded to install via Odin the Stock Rom and guess what it works like a charm, not a single problem.. So, so far the cellphone is ok.. I tested for two hrs.. Now i tried to install a custom ROM and its doesnt load from the Samsung S4 screen jaja... But im still having acces to discovery and download mode so thats ok..]
Click to expand...
Click to collapse
May I make a suggestion? Now that you have the phone working, can you possibly just use it for a week without doing anything to it? Don't try to root it or do anything other than text, make phone calls, and install a few programs. This will establish a baseline of behavior for your device, so you'll be able to tell when its behavior is out of the ordinary.
I understand your desire to make it your own. I got my S4 brand new from AT&T and said that I would wait at least a month before rooting it or changing roms, in case there was a problem and needed to return it. I had good intentions, but I couldn't stand it anymore and rooted it after only 3 days! It will take a lot of patience, but you really need to use it for more than a few hours to make sure that the hardware is okay.
I agree take baby steps, week stock, week root, week recovery. Figure out if its hardware or one of the steps is causing it.
I have been running CM (currently CM11) on my SGS4 since I bought it from Sprint in summer 2013. However, Sprint changed their international partners pretty seriously in the past 2 years, so I *really* need a PRL update for international travel. Normally the easiest way to do this is to reboot to stock or TriForce, run the "update PRL" and "update Profile" options from in TriForce, and go on with my life.
But I encrypt my phone. So I had to boot into TWRP, wipe and format *everything* and make sure the phone came up unencrypted in CM. All is OK.
So I reboot, flash TriForce 5.4 custom with stock (not KK) kernel. Flash works fine, I reboot... and am prompted to decrypt the device before I can do anything. None of the decryption passwords I've used in the past (I checked my password safe) are working. When I flash back to CM, it boots fine, and the settings says that the device is not encrypted.
I downloaded and tried TriForce 5.2 and 4.0, both are giving the same problem. I have used TriForce in the past on this phone, so it SHOULD be fine....?
Someone in #twrp said that the location of the encryption key changed from Android 4.4 to 5.0. So my only remaining thought now is that there was also a change from 4.3 to 4.4, and the encryption key for 4.3 didn't get removed in the wipe, and since the partition is NOT encrypted, the decryption, even if I have the right key, fails, so I can't get into the phone. Hope that makes sense.
Anyone have any guess better, or, if I'm right, know what I need to move/edit to fix this?
Followup: IRC #sgs4 suggested a full install of stock via odin, so I'll be trying that on Saturday, after I can get a new stock rom downloaded overnight. if there are thoughts before then, I'd love 'em.
docsmooth said:
Followup: IRC #sgs4 suggested a full install of stock via odin, so I'll be trying that on Saturday, after I can get a new stock rom downloaded overnight. if there are thoughts before then, I'd love 'em.
Click to expand...
Click to collapse
Followup - this was never solved before I dropped the phone and shattered the screen (literally days after this post). So if someone runs into the same thing... good luck.
docsmooth said:
Followup - this was never solved before I dropped the phone and shattered the screen (literally days after this post). So if someone runs into the same thing... good luck.
Click to expand...
Click to collapse
Thanks for the update, I was actually going to suggest stock ODIN instead of TriForce, but you are saying it did not work ? It's good to know for the future. I was initially going to encrypt my phone a long time ago, but I had concerns about decryption when switching ROMs.
My question is why the encryption was not removed after the format ? I've used TWRP to pretty much hose out everything inside the phone, so it's possible the encryption location is located somewhere else. I came across this article:
http://money.cnn.com/2015/05/21/technology/resell-android-phone/
So I guess even after a complete wipe everything ISN'T removed. Maybe your encryption was also stuck as well.................................... What new phone are you getting ?...................................
mikeprius said:
Thanks for the update, I was actually going to suggest stock ODIN instead of TriForce, but you are saying it did not work ? It's good to know for the future. I was initially going to encrypt my phone a long time ago, but I had concerns about decryption when switching ROMs.
My question is why the encryption was not removed after the format ? I've used TWRP to pretty much hose out everything inside the phone, so it's possible the encryption location is located somewhere else. I came across this article:
So I guess even after a complete wipe everything ISN'T removed. Maybe your encryption was also stuck as well.................................... What new phone are you getting ?...................................
Click to expand...
Click to collapse
I was never able to get the stock odin download. The whole problem came up because I was going overseas... I got around it by just buying a local SIM rather than using the Sprint roaming (again, I was doing all this just to update the PRL. new GSM SIM = no PRL update needed). On the way home less than a week later, I cracked the screen so bad the LCD and backlight wouldn't even go on.
I replaced it with a Nexus 6. A bit big, but it doesn't suffer Samsung software awfulness, so I didn't have to flash it with CM to make it usable.
Bootloop following contact with water? Or recent update?
Hello,
Here is my story : end of last wwek, my phone fall in a small amount of water (1cm) on the top (jack side). I wiped it very fast and use it for the next 30 min, everything is good. and then i let it 2 hours (charging or not i don't remember, i don't know if it can matter). After that i find it bootlooping was there an update, end of last week? Anyway i let it in that state at least 30 min and even more and then tried to restart it not better. I also tried a wipe cache and after that a factory reset, nothing...
Yersterday back to home, i tried to flash the 5.0.1 factory image ( didn't want to take the 5.1, because i feared a possible bad update on the image maybe) nothing better, even worst because after after some time of bootlooping, i've got the red light flashing :/
Same goes for the 4.4 flash but small miracle, it's working 4.2.2... During all those tries, i did some oem lock and unlock before and after each flash.
So my phone is working with the first version of android available, which is not the best.... I also tried the OTA update to the 4.3 and i also got stuck to a bootloop
So after that long story (sorry), I defer to your expertise because i don't know what else to do.
Please help :/
I just installed the lastest version of cyanogen and it's working well...
Still no idea whats happening there?
Seems to be a real big question i ask you there, but i continue my thinking on my side.
I dont like the idea, but it light be a hardware problem... Maybe a failing memory slot, or an unused component until then.
So it brings me 2 questions : how and where could i find logs after a failed update?
And how could i efficiently test my hardware CPU, RAM, as we can do on a computer?
Thanks in advance, any idea, help, joke are welcome
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.