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...
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
Hi Everyone
First post on this forum and first time trying to fool around with android.
I just replaced a new lcd + touch+ frame to an N4 its build was JOP40C
1) I said to myself why not trying to update manually to lollipop, well the N4 stayed stuck while booting with the colored dots.
2) I said to myself lets go back to JOP40c but that does not exist on google anymore so tried for hours many until JDQ39 and finally could get into my phone, but the number 6 and 7 where missing on the touch (???).
3) I said to myself well lets reinstall again and got totally my touch working.
4) Once done I received automatically an OTA from google, said to myself well lets do google, well the same happened again the phone was kind in a bootloop with the colored X.
Any help would be appreciated on why I am not able to update this phone, do I miss something that I should know and not found over all what I have read over the internet.
I have spent at least 3 working days on this and now I have to go back, make a living and hope that a pro will help.
I assume you're flashing the factory image and then you get a bootloop? Go into the stock recovery after flashing and do a factory reset.
Sent from my Nexus 5 using XDA Free mobile app
Tried that too lots of post over the internet about that but nothing keep getting blocked on the colored cross or bowls.
Tried also with Nexus Root Toolkit
Just received again the google update to 4.3 jelly beans on the N4 pressed restart and install then got the green robot and saying installing system update.
Then the phone got stuck in his bootloop and tird again the factory reset.
Still stays stuck in its bootloop.
invitro59 said:
Tried that too lots of post over the internet about that but nothing keep getting blocked on the colored cross or bowls.
Tried also with Nexus Root Toolkit
Just received again the google update to 4.3 jelly beans on the N4 pressed restart and install then got the green robot and saying installing system update.
Then the phone got stuck in his bootloop and tird again the factory reset.
Still stays stuck in its bootloop.
Click to expand...
Click to collapse
Try checking the SkipSoft.net Android Tool Kit
I hope that helps
You ever check all sensors work?
Maybe the same problems with this http://forum.xda-developers.com/nexus-4/help/issue-sensors-update-t2973047#post60470486
HI
I have checked with another N4, installed a software and checked the differences.
Well you are wright on this one the luminosity and proximity sensors are not showing any sign of life.
It is already past midnight here in France, so I will check tomorrow if I can do something on these sensors.
Will keep you posted if I can fix the sensors and do an update after that.
Hi
How stupid I am, after screen change connector sensor was not pluged in and since I had placed the plastic cover with the screws, could not see it anymore.
At least after have lost so much time, next time I will post a little earlier and at least tonight I will go bed less stupid than yesterday
Google just send the 4.3 upgrade and everything went smooth just no touch anymore so cannot use the phone.
ok installed lollipop but still the same no touch, but now I can install an update but not use the phone.
Anyone on that touch problem
Dear Experts,
I just got a brand new Note 3 with Android 5. I started encrypting the phone as brand
new, so that it would contain as less data as possible. It rebooted, then it showed the
picture with percentage. After reaching 100%, it rebooted again and is now for almost 1 hour showing the SAMSUNG logo with some stars flying around it.
Please kindly let me know if this is normal ? I think that when the stars are moving on the screen, the CPU must be working in order to display that...
Also, the blue LED is flashing... Please kindly advise on what to do.
Thank you!
It's flashing blue because the phone is trying to boot but it's not having any luck. You may have to boot into recovery, perform a factory wipe, and start over.
Personally, I do not encrypt my phone because it becomes a pain to get data off the phone if the data is encrypted.
Thank you. So you think it makes no sense to wait any longer ?
But how can this happen with a brand new phone ????
Btw. this is why it's being encrypted - to not be able to get the data out of it
You could wait but the flashing blue led means the phone is in the process of loading the ROM with the associated apps and data partitions. If it can't load the data, it will hang the phone.
OK, THANK GOD I was able to reset it and it finally booted! I had been doing a few little things with the phone, just the few minutes after I started using it. Maybe this made the encryption fail.
I am relaunching the whole process once again and we'll see. If it fails again. I'll have to be using it unencrypted :-/
Unless someone has a better idea...
Nope, still the same !!! What to do ??????? Please advise...
Come on, anyone, anything, PLEASE ???
Is the phone running a pure stock ROM, including recovery?
I always avoid encrypting phones. Too many risks and issues. I recommend just having a strong password lock.
Sent from my LG-D801 with CM13 using Tapatalk
darkman088 said:
Come on, anyone, anything, PLEASE ???
Click to expand...
Click to collapse
Simplest solution. Is to try to boot into recovery. Perform data wipe. Do a clean boot
If that fails.
Try to go into download mode. Flash stock rom. Clean boot.
If that fails.
Do emergency recovery in kies or smart switch. After that clean boot
After that. Disable encryption. Yeah it's more secure but also as you experience now. When it fails a pain to solve.
Sent from my SM-G935F using Tapatalk
@audit13 - yes, it was running stock Android 5.0, which btw. looks much nicer than 6.0.
Today I have flashed Marshmallow on it and it looks TERRIBLE :-/ I'm sooooo unhappy with the design!
Perhaps I should find a Jelly Bean ROM to flash to my phone :-/
@aquatarkus - why ? You don't think that anyone will unsolder the chips from your phone in order to read them out ? Is the screen lock really so strong ? No way to go around it through some USB attacks ?
And what about your SD card ?
@Michel - it's more or less what I did, but still no solution for that stock ROM that the phone came with.
Thank you for answering!
darkman088 said:
@audit13 - yes, it was running stock Android 5.0, which btw. looks much nicer than 6.0.
Today I have flashed Marshmallow on it and it looks TERRIBLE :-/ I'm sooooo unhappy with the design!
Perhaps I should find a Jelly Bean ROM to flash to my phone :-/
@aquatarkus - why ? You don't think that anyone will unsolder the chips from your phone in order to read them out ? Is the screen lock really so strong ? No way to go around it through some USB attacks ?
And what about your SD card ?
@Michel - it's more or less what I did, but still no solution for that stock ROM that the phone came with.
Thank you for answering!
Click to expand...
Click to collapse
So could you please state the current problem again? Because if I'm correctly you van boot into the rom atm, but encryption fails? Or you are still stuck in the boot process?
What is it exactly what you want right now?
Sent from my SM-G935F using Tapatalk
I no longer have the note 3 but I have the Nexus 5 running stock MM and it looks fine to me.
Maybe encryption needs a stock ROM with stock recovery? I never use encryption on any phone as I don't have anything that is that confidential on my phone.
OK, let me put this together very quickly:
2 days ago I got my brand new Note 3. I played with it a little and said - let's encrypt the phone, till I didn't put much stuff on it, so it will be faster. Once it got to 100%, it rebooted and stayed at the SAMSUNG logo with stars flashing around it and the diode flashing blue. I was waiting and waiting and waiting and nothing! I reset it to factory settings from the original recover, repeated the process - the same! I also tried the fast encryption option - again the same!
Then I have flashed the latest TWRP recovery and tried:
1. The VisionX ROM - Android 5. When I selected encrypt, the screen went completely black. I went to sleep. The next morning it was only showing the SAMSUNG logo in fire and that kept on for another couple of hours till I decided to kill it by taking out the battery.
2. The Slim ROM Android 5.0 - when I select encrypt, it immediately reboots. It kept showing just circles for 2.5 hours with no change. Then I decided that it makes no point to wait longer and I killed it by taking out the battery.
3. The TouchWiz Marshmallow for Note 3 ROM - SUCCESS !!!
The question is - why all the Android 5 ROMs are failing to encrypt the phone ? I prefer to stay on Android 5, as Android 6 is extremely ugly, I can't stand its looks with all the white background and round icons. Perhaps I should flash a ROM with Jelly Bean 4.3, just don't know how it looks with encryption there - pretty miserable I guess...
Thank you!
darkman088 said:
OK, let me put this together very quickly:
2 days ago I got my brand new Note 3. I played with it a little and said - let's encrypt the phone, till I didn't put much stuff on it, so it will be faster. Once it got to 100%, it rebooted and stayed at the SAMSUNG logo with stars flashing around it and the diode flashing blue. I was waiting and waiting and waiting and nothing! I reset it to factory settings from the original recover, repeated the process - the same! I also tried the fast encryption option - again the same!
Then I have flashed the latest TWRP recovery and tried:
1. The VisionX ROM - Android 5. When I selected encrypt, the screen went completely black. I went to sleep. The next morning it was only showing the SAMSUNG logo in fire and that kept on for another couple of hours till I decided to kill it by taking out the battery.
2. The Slim ROM Android 5.0 - when I select encrypt, it immediately reboots. It kept showing just circles for 2.5 hours with no change. Then I decided that it makes no point to wait longer and I killed it by taking out the battery.
3. The TouchWiz Marshmallow for Note 3 ROM - SUCCESS !!!
The question is - why all the Android 5 ROMs are failing to encrypt the phone ? I prefer to stay on Android 5, as Android 6 is extremely ugly, I can't stand its looks with all the white background and round icons. Perhaps I should flash a ROM with Jelly Bean 4.3, just don't know how it looks with encryption there - pretty miserable I guess...
Thank you!
Click to expand...
Click to collapse
I can't answer the question why the encryption keeps failing. What I do know is that marshmallow offers a lot more then lollipop. And that with the option of the theme store and or a custom launcher and icons packs. You can customize the white background and icons to your liking.
Sent from my SM-G935F using Tapatalk
There is no stock mm rom for this phone so we are stuck with LP for a stock rom.
Michel, as you started the topic about themes - can you pls briefly describe how that works ?
I googled it a bit, but didn't find a simple method. Many thanks!
darkman088 said:
Michel, as you started the topic about themes - can you pls briefly describe how that works ?
I googled it a bit, but didn't find a simple method. Many thanks!
Click to expand...
Click to collapse
Samsung included the home store for later end flagships.
I know that through the use of the phoenix rom the galaxy S5 which didn't had support for the theme store got access to it.
You should check with the developer of the rom. Or the Op of the rom if the mm rom available on here comes with support for the theme store.
If it includes that.
You can access the Samsung theme store from touchwiz and download another skin for touchwiz.
This will affect the icon set, notification / dialer and contacts page.
Sent from my SM-G935F using Tapatalk
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.