Database Users

VZW SCH-i800 (7.1) 2.3.5 flashed but retains old wallpaper/FC apps!!

Hey guys. I have a very interesting situation happening with a VZW Galaxy Tab 7.1 that I bought from someone (I own a business buying/selling/trading cellphones and tablets)..
As soon as you boot it up, every app starts to force close!
If you sit there long enough and accept them all, you can actually use it a little bit. Apps keep FCing as you play with it, though.
The only noticeable thing is that the wallpaper always stays the same. It was 2.3.4 (I believe) when I got it, but I've tried flashing stock ROMs and the Galaxy Cubed 3 ROM through Heimdall, but that wallpaper ALWAYS stays there!
I just flashed the Galaxy Cubed 3 ROM on there 20mins ago, and everything switched over (the look, the battery icon, notification bar, window animations) EXCEPT that wallpaper (which ironically is of B.I.G.) and the FC issues.
I read somewhere about JTAG or something, but it boots fine, just having software issues.
PLEASE, if anyone knows anything about this issue, I need to sell this thing so I can make some money =) Thanks in advance for the help!

im in the exact same boat with a customers tablet. ive tried everything. takes forever to boot and factory reset does nothing. 4 installed apps never uninstall either.

Do you have custom recovery installed? After flashing with Heimdall, enter custom recovery and wipe data and cache. Reboot. No more issues.

I can't find a way to get custom recovery to flash. I've tried every walkthrough. There's no explanation as to why factory reset/wipe doesn't work

Phone won't boot past "Galaxy S4" splash screen

So I recently purchased my AT&T Galaxy S4 with MDL baseband. I rooted and installed TWRP via motochopper. I then loaded Kangabean 4.2.2 and everything was great. Got notification for OTA update to 4.3 and decided might as well load Kangabean 4.3 as opposed to dealing with the OTA notification. I did so (after formatting internal SD and performing factory reset) and now my phone won't boot beyond the Galaxy S4 splash screen. I restored a nandroid backup of the original software and was able to boot the phone once, but couldn't load the custom rom again, nor can i load into the stock rom anymore either. Does it sound like my phone may have a hardware failure? Would attempting to restore through odin be the next logical step? I'm by no means an expert with these sort of things but my S2 has never given me any sort of grief when flashing various roms in the past. Any advice would be greatly appreciated. Thanks in advance!

Try a different kernel, also, pull the battery for 5 min, it will boot.

TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
Yeah I left the phone off with the battery removed all night - didn't want to boot this morning. I'm also noticing an oddity with TWRP - it's for some reason asking for a password on startup even though I've never set one. It also gives an error when attempting to wipe the phone or re-flash

id try odin

Don't Odin yet. If you can get into recovery see if you can flash a new recovery onto the phone. Try this http://forum.xda-developers.com/showthread.php?p=41746967

jd1639 said:
Don't Odin yet. If you can get into recovery see if you can flash a new recovery onto the phone. Try this http://forum.xda-developers.com/showthread.php?p=41746967
Click to expand...
Click to collapse
It will not let you past the password, been there, it will only do simulated flashes.
Odin is his only option.

So I managed to flash back to stock with odin. I was then able to re-root and re-install recovery. Something is still wrong here though. I was able to load kangabean 4.3, but when i installed the SIM card (kept it out to prevent OTA updates) the phone would no longer boot. I then re-flashed with odin, re-rooted, installed sim, THEN loaded the rom and it worked.... For a while. I had the phone plugged in to my laptop as i had recently transferred some ringtones to the internal SD. I powered down the phone. It seemed to shut the OS down but it then displayed a battery symbol with a rotating circular animation, as if it was trying to show that it was charging the battery. The phone froze in this state.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
I find it odd that the rom that i flashed would stop working if i've flashed the rom with the sim removed from the phone, then introduced the sim to the phone after the flash is complete. Is this normal? I'm also unsure if my phone has faulty hardware, or maybe there's some sort of software glitch that's causing it to hang and overhead (like an infinite loop caused by faulty software).
I think if / when I can get it working with the stock rom again, I'll root it and run it for a while and see what it does. I never intended to run this phone with the stock rom as I prefer vanilla android.
I'm wondering if there's something wrong with the kernel. Perhaps I should re-download the ROM and re-install it. I'm not sure but I think the kernel is responsible for charging issues. Perhaps a bad kernel WOULD explain why the phone sometimes freezes at the "battery charging" logo? I'm somewhat at a loss as to what to do. I could try exchanging it through AT&T. If so, I hope they nave another one in their stock that has the MDL baseband as I know I'd be screwed with the current one...

Squidbert said:
So I managed to flash back to stock with odin. I was then able to re-root and re-install recovery. Something is still wrong here though. I was able to load kangabean 4.3, but when i installed the SIM card (kept it out to prevent OTA updates) the phone would no longer boot. I then re-flashed with odin, re-rooted, installed sim, THEN loaded the rom and it worked.... For a while. I had the phone plugged in to my laptop as i had recently transferred some ringtones to the internal SD. I powered down the phone. It seemed to shut the OS down but it then displayed a battery symbol with a rotating circular animation, as if it was trying to show that it was charging the battery. The phone froze in this state.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
I find it odd that the rom that i flashed would stop working if i've flashed the rom with the sim removed from the phone, then introduced the sim to the phone after the flash is complete. Is this normal? I'm also unsure if my phone has faulty hardware, or maybe there's some sort of software glitch that's causing it to hang and overhead (like an infinite loop caused by faulty software).
I think if / when I can get it working with the stock rom again, I'll root it and run it for a while and see what it does. I never intended to run this phone with the stock rom as I prefer vanilla android.
I'm wondering if there's something wrong with the kernel. Perhaps I should re-download the ROM and re-install it. I'm not sure but I think the kernel is responsible for charging issues. Perhaps a bad kernel WOULD explain why the phone sometimes freezes at the "battery charging" logo? I'm somewhat at a loss as to what to do. I could try exchanging it through AT&T. If so, I hope they nave another one in their stock that has the MDL baseband as I know I'd be screwed with the current one...
Click to expand...
Click to collapse
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse
//

Squidbert said:
.
Another thing that I've noticed is that when this phone freezes, it gets warm. It also tends not to respond well until i've let it cool down. I'm now having difficulty booting the phone after re-flashing with odin. It loads to the white screen with AT&T logo and hangs (and gets warm). I plan to leave the phone alone with battery removed for the day and attempt to reboot or re-flash with odin later.
Click to expand...
Click to collapse
If you're on the stock AT&T rom and you're getting stuck on the AT&T boot logo try the following:
Power off your phone and hold down Volume Up, Center Home, and Power buttons together.
Once you see the Galaxy S4 splash - Keep holding down Volume Up and Center Home buttons but let go of Power button.
Choose the wipe datafactory reset. This will wipe your phone completely but it should boot after.
Hope that helps.

Well I've been toying around with this thing and much to my surprise, I have CM10 running stable w/o any issues booting! I think I would prefer to run Kangabean 2.05 (android 4.3) though. Assuming that the kernel could be a likely cause of the OS not booting, could someone recommend a suitable kernel for that rom? It appears to come packaged with the "KT" kernel...
Another thought i had was perhaps TWRP wasn't adding the loki feature to the roms that i was trying. I upgraded from 2.5x to 2.6. Hasn't seemed to have made a noticeable difference though.
Would the fact that CM10 runs absolutely flawlessly with no issues booting at all possibly help narrow down why the other roms that I'm flashing only load up the first time but fail at the "Galaxy S4" splash screen on subsequent reboots? Admittedly I'm a relative noob to roms and such but up until now i've been able to muddle my way through things and eventually figure them out. I'm not having the greatest luck with this one!

Squidbert said:
Well I've been toying around with this thing and much to my surprise, I have CM10 running stable w/o any issues booting! I think I would prefer to run Kangabean 2.05 (android 4.3) though. Assuming that the kernel could be a likely cause of the OS not booting, could someone recommend a suitable kernel for that rom? It appears to come packaged with the "KT" kernel...
Another thought i had was perhaps TWRP wasn't adding the loki feature to the roms that i was trying. I upgraded from 2.5x to 2.6. Hasn't seemed to have made a noticeable difference though.
Would the fact that CM10 runs absolutely flawlessly with no issues booting at all possibly help narrow down why the other roms that I'm flashing only load up the first time but fail at the "Galaxy S4" splash screen on subsequent reboots? Admittedly I'm a relative noob to roms and such but up until now i've been able to muddle my way through things and eventually figure them out. I'm not having the greatest luck with this one!
Click to expand...
Click to collapse
TWRP does not now and has never added LOKI to any ROM or Kernel. Only OUDHS CWM auto-LOKIs. You have to use A pre-LOKIed Kernel or flash the LOKI DokI script to LOKI anything with TWRP. You can do a search to find the LOKI DOKI script and how to use it.

fatah
hi my phone is galaxy s4 at&t i337 rooted but not installed recovery the phone was working good suddenly i deleted at&t software updater after that the phone rebooted it's self and then stuck in at&t boot logo won't bootup please help
TheAxman said:
Try a different kernel, also, pull the battery for 5 min, it will boot.
Click to expand...
Click to collapse

galaxy s4 i337 stuck on at&t bootAnimation
i tried everything but still same please help my phone is not booting up

fatahmusse said:
i tried everything but still same please help my phone is not booting up
Click to expand...
Click to collapse
Flash the stock firmware.

samsung galaxy s4 i337
thank you i flashed to mf3 everything is ok

fatahmusse said:
thank you i flashed to mf3 everything is ok
Click to expand...
Click to collapse
Glad to hear

Huge problem S4 not working anymore..

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.

Note 4 diarrhea

Hi, I'm kinda lost ma mind right now.
Here's the story, my friend has note 4 SM-N910F Qualcomm , suddenly it began restarting with abnormal battery dropping.
I began repairing by trying to perform factory reset, to enter into a boot loop (without a root till the moment). Then I charged it fully which made it work.
I tried to root then install CM to replace stock rom (to repair any system issues), which was quite difficult, as I tried to install CM 12.1, it keeps fail due to incompatibility (the CM rom for trltexx and mine trlte as the root keeps shows me)
BTW the root I used was ( openrecovery-twrp-2.8.4.0-trltexx.img.tar ) *yea it confusing*
Finally I downloaded official stock 5.1.1 , and installed it, it finished well and booted also quite well, as language selection screen appeared, same original issue reappeared again ( *keeps rolling in boot loop* )
Now I'm worrying about hardware malfunctioning.
:silly::silly::silly::silly::silly::silly::silly::silly:

I accidentally posted in Android development. so sorry

I've seen this issue on my friend's tab s. The screen would freeze then it would reboot. This got worse as the battery power doped to the point that swiping to unlock would cause a reboot. The problem turned out to be the battery. It may be worth buying a new battery for very little money to see if this fixes it.

Dr.DL said:
Hi, I'm kinda lost ma mind right now.
Here's the story, my friend has note 4 SM-N910F Qualcomm , suddenly it began restarting with abnormal battery dropping.
I began repairing by trying to perform factory reset, to enter into a boot loop (without a root till the moment). Then I charged it fully which made it work.
I tried to root then install CM to replace stock rom (to repair any system issues), which was quite difficult, as I tried to install CM 12.1, it keeps fail due to incompatibility (the CM rom for trltexx and mine trlte as the root keeps shows me)
BTW the root I used was ( openrecovery-twrp-2.8.4.0-trltexx.img.tar ) *yea it confusing*
Finally I downloaded official stock 5.1.1 , and installed it, it finished well and booted also quite well, as language selection screen appeared, same original issue reappeared again ( *keeps rolling in boot loop* )
Now I'm worrying about hardware malfunctioning.
:silly::silly::silly::silly::silly::silly::silly::silly:
Click to expand...
Click to collapse
Did you try a Factory Reset?
Sent From My SM-N910W8 Running CMRemix 6.01

fatboyinlycra said:
I've seen this issue on my friend's tab s. The screen would freeze then it would reboot. This got worse as the battery power doped to the point that swiping to unlock would cause a reboot. The problem turned out to be the battery. It may be worth buying a new battery for very little money to see if this fixes it.
Click to expand...
Click to collapse
I'm in a doubt about the battery, I think it's slightly swollen.
I guess I'll give it a try.

shaggyskunk said:
Did you try a Factory Reset?
Sent From My SM-N910W8 Running CMRemix 6.01
Click to expand...
Click to collapse
First thing I did.

Dr.DL said:
Hi, I'm kinda lost ma mind right now.
Here's the story, my friend has note 4 SM-N910F Qualcomm , suddenly it began restarting with abnormal battery dropping.
I began repairing by trying to perform factory reset, to enter into a boot loop (without a root till the moment). Then I charged it fully which made it work.
I tried to root then install CM to replace stock rom (to repair any system issues), which was quite difficult, as I tried to install CM 12.1, it keeps fail due to incompatibility (the CM rom for trltexx and mine trlte as the root keeps shows me)
BTW the root I used was ( openrecovery-twrp-2.8.4.0-trltexx.img.tar ) *yea it confusing*
Finally I downloaded official stock 5.1.1 , and installed it, it finished well and booted also quite well, as language selection screen appeared, same original issue reappeared again ( *keeps rolling in boot loop* )
Now I'm worrying about hardware malfunctioning.
:silly::silly::silly::silly::silly::silly::silly::silly:
Click to expand...
Click to collapse
Install Custom recovery thro' ODIN (philz_touch)
Flash Nameless Kernel v 6 thro custom recovery.
And I think you are done.

If you tried factory reset and flashed a fresh stock rom and its still happening, the battery is the problem and also check if there is a micro sd inserted. If so, remove the card and check.
No custom rom or kernal will be better since they come with thier own bugs and not as stable as official firmware period!

dineshh said:
Install Custom recovery thro' ODIN (philz_touch)
Flash Nameless Kernel v 6 thro custom recovery.
And I think you are done.
Click to expand...
Click to collapse
Battery issue, solved with replacement

jetbruceli said:
If you tried factory reset and flashed a fresh stock rom and its still happening, the battery is the problem and also check if there is a micro sd inserted. If so, remove the card and check.
No custom rom or kernal will be better since they come with thier own bugs and not as stable as official firmware period!
Click to expand...
Click to collapse
Solved with battery replacement
huge thanx

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.