Database Users

No wifi, and prevention info notification.

Ok, talk to me like I'm an idiot about this stuff, because apparently I am.
I decided to root using chainfire autoroot, and that was successful, aside from a couple weird things like my UCCW widgets suddenly not stretching fully across the desktop, and what seemed like some new lag. I then flashed slimbean. My contacts didn't restore from google or anywhere, and my sd card seemed to be having problems. I then decided to flash blue kaban or whatever, and that straight up wouldn't boot. However, at that point my sd card fully stopped working, and that is the place I had the slimbean zip. So I did not have a working rom on my phone.
So what I decided to do was unroot and start from scratch. I used the method in this video on youtube by qbking
The result is that my wifi is not working and I have a persistent notification that says Prevention information the device has detected an application attempting etc.
Also software version is MDL, Baseband version is MDL, and Build number is MDC. I was under the impression that they would all be MDC and it would automatically push the MDL but apparently I suck.
My ultimate goal is get back to pure out-of-the-box stock so I can start the rooting process over and try flashing something stable again. But abviously the most important thing right now is to get the wifi working and (I think) the Basbeband and build numbers to match. But I don't know. Please help me. Please. I beg of thee.

ok so after an hour or so it pushed the update to me and my wifi is now working, and everything is MDL. The SD card still says damaged and my contacts aren't there. Any ideas on why those two things would be casualties of rooting and flashing?

I've got the same problem after flashing back to stock from some rom. Would you mind telling me how you got the wifi to work and that notification to go away? I'm not getting an update.
Did the SD card problem happen afterwards? Did you do a factory reset and delete data before you reflashed it? Sometimes when you flash over a partial thing system apps get corrupted.

I have actually performed this and had this happen a few times. What I have found thay it does on some devices is will not properly install random MDL firmware(Saw MDL Firmwares In Settings Still Being Reported). So what I found to be the proper steps for me is before installing any ODIN tarballs thatcare firmware based besides rec9eries are to boot into Recovery and wipe "System, Data, Dalvik, Cache and Preload(Dont Know Why All Of Those) then immediately reboot into Download Mode, install tarball and then when it reboots I go ahead and let it go into recovery and do what it wanrs and when it reboots from stock recovery I hold vokume down to go into download mode and if it says Samsung Official/Official for both options then you are set but if not then I reinstall tarball while I am already in Download Mode again. It happens literally every time I ODIN back to bone stock. I have had to do it at the most 2 extra times after the initial ODIN install.
Sent from my SPH-L720 using Tapatalk 4 Beta
---------- Post added at 12:06 AM ---------- Previous post was at 12:04 AM ----------
Now, I also do go ahead and after initial install of tarball go into OS and if I dont have working wifi then I go ahead and do an FDR while I am in the OS just in case even though should helo whatsoever lol then start going to download mode to check Recovery and Software Status.
Sent from my SPH-L720 using Tapatalk 4 Beta

Brains, did you ever get it to work?
Sent from my SPH-L720 using Tapatalk 4 Beta

[Q] Nexus 4 updated to Kit Kat via OTA and got looped on boot

Hi, this is my first post here. I'm new into Android and I've always updated my Nexus 4 when the system prompts me to do it. Today, I got the notification to update from 4.3 to 4.4... I did it and restarted my phone. Then I got (and have been) stuck on the boot sequence after the Google logo. The thing is that I've tried to wipe and restart the phone by Bootloader (I don't know if I lost all of my files) and didn't work out. So now I'm trying with Nexus Root Toolkit but I don't know if that will work. I'm really needing some help, here in Venezuela not so many people have this cellphone and I really don't know how to proceed. I'm upset with Google for these kind of fails, my phone was working 100% good. Please help me! Sorry if my english is not so perfect.

I did experience the same.
Never rooted or unlocked bootloader & I was patiently waiting for OTA. It came and it was the worst thing to happen! Infinite bootloop!
I waited 2 hours, before I restarted the phone, but in vain. No use!
I never enabled debug settings, so i couldn't use ADB command and it wasn't recognizing my device!
Here is what worked for me:
1. Unlock bootloader (using fastboot command)
2. use fastboot to flash the factory image
3. I did remove (-w) wipe option, but still lost my data.
however image works, now phone is back to life!

Same case, nothing works.

I had the same problem, go stuck on a boot loop and then it just said 'no command' or 'error' with an android lying down. Im a noob so i used ncry toolkit to reset it to factory 4.3 and then i upgraded to 4.4 again and all worked fine. Did lose data though, but i had it all backed up.

Do a clean flash of KitKat via fastboot.

Similar Situation
Chidvilas said:
I did experience the same.
Never rooted or unlocked bootloader & I was patiently waiting for OTA. It came and it was the worst thing to happen! Infinite bootloop!
I waited 2 hours, before I restarted the phone, but in vain. No use!
I never enabled debug settings, so i couldn't use ADB command and it wasn't recognizing my device!
Here is what worked for me:
1. Unlock bootloader (using fastboot command)
2. use fastboot to flash the factory image
3. I did remove (-w) wipe option, but still lost my data.
however image works, now phone is back to life!
Click to expand...
Click to collapse
I'm in the same situation as most... Sadly I updated via the OTA distro that was released a few days ago. I looked into rooting options and I got the "go ahead" from a thread somewhere, saying it is a minor update. Knowing how easy it was to restore root priveliges when I upgraded from 4.2 to 4.3, I trusted their encouragement and installed the update. Then, like everyone else, I got stuck in the bootloop at the "circles" screen.
As a last resort, I tried to factory reset to no avail. I cleared the dalvik cache and wiped the cache partition a few times... Then I tried restoring it to factory defaults, again! Same results every time. Unfortunately, because of where it gets hung up, I can't seem to get my computer to talk to it. I certainly can't access the SD Card to do any backing up, but can look at the contents through CWM recovery mode (v6.0.2.3).
It's been awhile since I last was active in flashing my phone, so while I no longer consider myself a noob, I am definitely back to being a beginner. The fastboot commands don't seem to work, as I get stuck at "<waiting for device>". Does anyone know if there is a way to force it into a drive mode? Any additional help with this matter would be greatly appreciated, as currently it seems Google has bricked my phone!
Last question, it looks like it may be possible to force a mount through CWM; is that true using the "mounts and storage" menu? I spoke to Google briefly and they were of no help (they just told me to call LG). I'm going to try going into the T-Mobile store and seeing what they will say, but I'm not holding my breath for them to come up with a solution; I'm relying on the community to help me out!
STATS:
Bootloader: MAKOZ20i
HW Version: rev_11
Secure Boot: enabled
Lock State: unlocked
CWM: v6.0.2.3
Computer OS: Linux-Ubuntu 13.4
---------- Post added at 03:48 PM ---------- Previous post was at 03:39 PM ----------
NissanskylineN1 said:
Do a clean flash of KitKat via fastboot.
Click to expand...
Click to collapse
Sorry to sound so dumb, but can you point me in the right direction to find instructions on how to do that with Linux?

http://forum.xda-developers.com/showthread.php?t=2302780
Its actually way easier to set it up on Linux than on windows.
Edit: java jdk6 was giving me issues on install so I used openjdk instead and it works perfect.
Edit: (last one, I promise), I don't know how new you are to Linux but if you are super new, anytime that guide mentions "code" in a box, copy and paste one line at a time into the terminal. Leave out the dollar signs when copying.
AMarted said:
I'm in the same situation as most... Sadly I updated via the OTA distro that was released a few days ago. I looked into rooting options and I got the "go ahead" from a thread somewhere, saying it is a minor update. Knowing how easy it was to restore root priveliges when I upgraded from 4.2 to 4.3, I trusted their encouragement and installed the update. Then, like everyone else, I got stuck in the bootloop at the "circles" screen.
As a last resort, I tried to factory reset to no avail. I cleared the dalvik cache and wiped the cache partition a few times... Then I tried restoring it to factory defaults, again! Same results every time. Unfortunately, because of where it gets hung up, I can't seem to get my computer to talk to it. I certainly can't access the SD Card to do any backing up, but can look at the contents through CWM recovery mode (v6.0.2.3).
It's been awhile since I last was active in flashing my phone, so while I no longer consider myself a noob, I am definitely back to being a beginner. The fastboot commands don't seem to work, as I get stuck at "<waiting for device>". Does anyone know if there is a way to force it into a drive mode? Any additional help with this matter would be greatly appreciated, as currently it seems Google has bricked my phone!
Last question, it looks like it may be possible to force a mount through CWM; is that true using the "mounts and storage" menu? I spoke to Google briefly and they were of no help (they just told me to call LG). I'm going to try going into the T-Mobile store and seeing what they will say, but I'm not holding my breath for them to come up with a solution; I'm relying on the community to help me out!
STATS:
Bootloader: MAKOZ20i
HW Version: rev_11
Secure Boot: enabled
Lock State: unlocked
CWM: v6.0.2.3
Computer OS: Linux-Ubuntu 13.4
---------- Post added at 03:48 PM ---------- Previous post was at 03:39 PM ----------
Sorry to sound so dumb, but can you point me in the right direction to find instructions on how to do that with Linux?
Click to expand...
Click to collapse

[Q] Where to go from MJE?

Have MJE and had stopped OTAs. Would like to move forward to lollipop on this phone. 2 different questions:
1. Would I be able to install a lollipop ROM from MJE or is it already locked down with no options
2. Phone is in "custom" mode. Can I just reenable OTA updates and let it receive updates OTA without bricking or does the knox need reset first? Not worried about warranty issues.
Please spare the flames, I dont know what I am doing much but can follow instructions and I am just looking for a little help. Dont want to blow my phone out and not be able to do anything with it. Thanks!

mwinschel said:
Have MJE and had stopped OTAs. Would like to move forward to lollipop on this phone. 2 different questions:
1. Would I be able to install a lollipop ROM from MJE or is it already locked down with no options
2. Phone is in "custom" mode. Can I just reenable OTA updates and let it receive updates OTA without bricking or does the knox need reset first? Not worried about warranty issues.
Please spare the flames, I dont know what I am doing much but can follow instructions and I am just looking for a little help. Dont want to blow my phone out and not be able to do anything with it. Thanks!
Click to expand...
Click to collapse
Im in the same boat with you. Im still on 4.3/MJE/Stock/Rooted. I rooted with RootMaster when i got the phone over a year ago and disabled OTA updates. Its been an awesome phone but recently been having glitches (screen flickers randomly when on and auto adjust brightness is turned off and google maps cannot find my location, the GPS icon never comes on anymore, other mapping apps still work fine) and ive had to disable my google play services from killing my battery. Also my music has been stuttering on poweramp (not sure if it is just a app issue). Another thing Ive noticed is when i restart my phone its been doing a double bootloop, it gets to the launcher screen then immediatly reboots, but then fully boots up the second time.
Any suggestions anyone? I want to keep root and dont mind stock. Go launcher gives me most of the customization i need, really only need root for AdAway (which doesnt work so well anymore), Gemini App Manager- so i can keep certain apps from startup upon boot, SD speed increase (which im not really sure actually does anything), and of coarse TITANIUM.
Do i need to do an ODIN flash or TWRP or CWM? Can i just hit the factory reset and keep my root? Maybe flash up to 4.4.2? I keep seeing that 4.4.4 and higher cant be rooted unless im mistaken.
Any direction from someone knowledgeable would be greatly appreciated.

Rooted for a few weeks -- rebooted and stuck on T-Mobile Screen + Random Vibration

Hello all! This is the second time this has happened to me, I've rooted my phone for about a week, and then for some reason when I decide to restart my phone -- it no longer boots up. It is stuck at the t-mobile screen and vibrates for a bit then stops, I have booted in to recovery mode and tried wiping that cache, but to no avail.
Any help would be appreciated -- or even how I can backup my data would be great too.

Wah gwan! My T-Mobile S7 Edge running TekHD v2. To have your phone running very nicely, you need to download the APD8 fireware. Make sure everything on your phone running APD8. download the files from max on highonandroid, flash the tar file twice using modified Odin from max. Once boot up screen say custom, next step download and extract TekHD.rar file .there's a part in the file that operates like cmd, right click and let it do its thing. Make sure your phone is on and a low USB debugging.
---------- Post added at 10:09 PM ---------- Previous post was at 09:43 PM ----------
Also this TekHD Rom is best for unlimited hotspot for Windows, Android and Mac. I have download about 20 more GB of files to make sure its good. The tutorial from max is good, the easiest way I see so far is to click on the root.dat in max files to add superSU. For TekHD click tekhd.bat. That was the easiest way after flashing the tar file. The hold process take 2 minutes once done right. I'm not a developer but a big Samsung Android fan. I have a Note 3,4,5 S6 Edge+ and S7Edge, I tried and tested many Roms at my own risk. Never had any problems. Make sure you always have the stock rom tar file for your device before any flashing any roms, is case something goes wrong you can start over.

first of all this is an eng boot root, so expect some hiccups and proble.. before u root make sure u back up everything then odin back to stock then root or else u will run into problems

You're going to have to ODIN back to stock. This seems to be happening to a lot of people (myself included) and a stock flash is the only way anyone has been able to recover. Flash all 4 files in ODIN simultaneously, but if you don't have a backup, try flashing the Home_CSC and see if it'll boot. I've heard reports that the Home-CSC file doesn't wipe your phone. If that doesn't work, then unfortunately you're going to have to re-flash, but this time use the standard CSC file, which will wipe your phone. Good luck.

I just had this happen for my second time and was stuck phoneless out of the house :/ I wish we could figure out the cause... Not sure if related, but my recovery has red text on the bottom "dm-verity verification failed"

ph00ky said:
Not sure if related, but my recovery has red text on the bottom "dm-verity verification failed"
Click to expand...
Click to collapse
No, that is not related, dm-verity verification fails because recovery still checks dm-verity even though the kernel does not.

Damn same thing just happened to me at work. Had to do factory reset...
When at that tmobile screen, hold down volume down + home button + power. It will reboot,and as soon as it does, switch volume down to vol up until it loads recovery to reset

This happened to me also. Go to lockscreen and security options and disable automatic security updates.

I think it could be new firmware update from Google. I tried to install TekHD Rom after update to the newest APG1. And it hapened to me also. Stuck on Samsung screen with random weird vibrations.

I can almost certainly say that the vibrate crash has something to do with the phone installing something behind the scenes. After getting the Amazon/Google/Samsung services multiple crash followed by the reset to the vibrating T-mobile screen I did a non-wipe ODIN, which works and works perfectly. What seems to not work though is re-installing root, it just leads back to the same screen, so I think Samsung is pushing something sneaky onto our phones probably through the security thing as mentioned.
---------- Post added at 01:41 PM ---------- Previous post was at 01:40 PM ----------
pawel30w said:
I think it could be new firmware update from Google. I tried to install TekHD Rom after update to the newest APG1. And it hapened to me also. Stuck on Samsung screen with random weird vibrations.
Click to expand...
Click to collapse
TekHD Only works on PD8, it's mentioned in the thread.

pawel30w said:
I think it could be new firmware update from Google. I tried to install TekHD Rom after update to the newest APG1. And it hapened to me also. Stuck on Samsung screen with random weird vibrations.
Click to expand...
Click to collapse
Can't run that ROM on APG1. If you want to try it, you will have to ODIN PD8. There is a post in a thread in this section that shows how.

I just had this same thing happen on PG1. Using ODIN with all of the various parts and Home_CSC got me back in without having to wipe and everything survived. Going to try and re-root with the engineering boot image now that I made a decent backup. Would be great if someone smarter than me figures out what is updating/changing and causing this problem.

I said it on page 1: In settings, go to lockscreen, then security options and disable automatic security updates.

rp3 said:
I said it on page 1: In settings, go to lockscreen, then security options and disable automatic security updates.
Click to expand...
Click to collapse
That might work to prevent this problem -- but what needs to be reverted once this problem starts? I can flash stock PG1 and if I use the (home_csc) it will fix the problem and not wipe my data.... but if I reflash the engineering bootloader it goes back to hanging at the tmobile screen.

im stuck on tmobile screen, and it keeps vibrating, idk what to do

swaggyyd said:
im stuck on tmobile screen, and it keeps vibrating, idk what to do
Click to expand...
Click to collapse
I haven't rooted but if your stuck just Odin back to stock.

I came to post that I'm having these issues as well, this is the second time it's happened to me.
The first time I had TEKHD on my Phone, and so with it constantly nagging to do a system update.
I figured when it did this the first time, it was because the update ran over my TEKHD side load "ROM" and corrupted. Ok , whatever, reloaded.
But now I'm just rooted, and stock ROM otherwise. Just happened to me again
Each time it's happened, I start getting "playstore has crashed" errors - dismiss and it comes right back. So I reboot, and then it boot loops and gets CRAZY hot. Man I've never been able to fry an egg on a phone quite like my S7 Edge...
Is there any light shed on what could be doing this? I may have to remain stock which makes me want to :crying: but I can't keep bothering my Work Admin's to unlock my Token account so I can re-register my same phone -
I shall try that home_CSC Flash when I get home though, hopefully I can recover it at least in a way to transfer token to my tablet or something.

posted that at work, I'm at home now. I tried to flash just the home CSC and that did not work, just booted into recovery with an error and wouldn't resurrect at all.
I shall try that disable auto updates thing though and see if it helps in the long run...

wotan2525 said:
I just had this same thing happen on PG1. Using ODIN with all of the various parts and Home_CSC got me back in without having to wipe and everything survived. Going to try and re-root with the engineering boot image now that I made a decent backup. Would be great if someone smarter than me figures out what is updating/changing and causing this problem.
Click to expand...
Click to collapse
you got a link for the home csc file you can send me I was good for about a month and a half and it finally happened to me as well and can confirm I was getting the play store/ google services errors right before the reboot and tmobile screen

Was having this issue as well, forgot that I needed to turn off Security policy updates.

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.