Database Users

[Q] ParanoidAndroid boot loop

I bought a used Nook Color this spring on ebay, already rooted. It is JellyBean 4.1.2, CM10-20121216-UNOFFICIAL, ParanoidAndroid 2.99. It had Goo Manager, but not TWRP that I could tell.
It's always gone into boot loops, when I asked the seller he said use Goo Manager to look for an update. There has never been an update found. I tried installing TWRP through Goo Manager today, but it tells me no recoveries found. May have managed to install from the computer's Play Store, haven't been able to check yet because it is still looping. (Does not look like it downloaded, many updates were ahead of it.)
The past few weeks it has spent more time rebooting than working. Cyanoboot loads, but the little jellybean guy just glows and the eyes move around on the beans. Sometimes it will load after awhile, sometimes it takes hours. I have it charging the whole time, but it does not charge while it is looping. Once it finally loads and I unlock it, it shows a popup that Process Service isn't responding. If I hit wait, it will load.
The NC did not come with a charger, I bought a non-OEM charger on Amazon that was listed as NC-compatible. It seems to work fine, although doesn't quite keep up when watching video or anything screen-intensive. I normally leave the NC plugged in when I am home, when it comes out of the looping it is usually in the 90 plus percent range. I tried leaving it unplugged overnight while looping once, it ran down fairly low but recharged fully after finally loading.
For a week or two before the constant looping started, two other issues appeared. When I woke it up in the morning, it would not be connected to wifi. The icon is just an outline, and when I check under settings it says scanning for wifi networks. If I reboot, it connects fine.
The second problem is the SD card keeps unmounting. Generally I will get a popup from Evernote that the SD card has changed. Most of the time if I go into settings > storage I can see that the card is unmounted and tell it to mount. Sometimes it says it is mounted, so then I reboot. Today I noticed the internal card was also showing as unmounted. I was able to mount both, at least until the NC rebooted itself again. I'm using a SanDisk Ultra (Class 10) 32 GB card.
It finally loaded, but looks like no wifi again. Battery is at 92 percent. It did finally manually connect after telling me avoided due to poor connection (about 5 feet tops away from the modem).
Would re-rooting or flashing a new ROM work, or is something else wrong? Why can't Goo Manager find any updates?
Thanks for any help!

I used that ROM for a while, it had some issues, but for the most part I enjoyed it. The SD I mounting issue can usually be solved by formatting it with your computer, and the bootloops can be fixed by reinstalling the ROM. Make a twrp sd card. (There's a thread in here somewhere) and reinstall it, or install other roms if you decide you don't like this one.
---------- Post added at 03:19 PM ---------- Previous post was at 03:19 PM ----------
Also, goo manager simply doesn't work with the pa 2.99 rom. Don't know why.

Mineturtle33 said:
I used that ROM for a while, it had some issues, but for the most part I enjoyed it. The SD I mounting issue can usually be solved by formatting it with your computer, and the bootloops can be fixed by reinstalling the ROM. Make a twrp sd card. (There's a thread in here somewhere) and reinstall it, or install other roms if you decide you don't like this one.
---------- Post added at 03:19 PM ---------- Previous post was at 03:19 PM ----------
Also, goo manager simply doesn't work with the pa 2.99 rom. Don't know why.
Click to expand...
Click to collapse
I can't find any recoveries, finally managed to install ClockworkMod's ROM Manager and it says both ClockworkMod and TWRP recoveries are there somewhere. SD card was unmounted again and while remounting it went into a bootloop again
Off to look for the twrp card thread, thanks!

Strangest problem - reboot restore flash memory to identical state

Hello, I just want to share with you strangest problem I ever had with Android device.
I have old Nexus 7 nakasi with stock 5.1 rooted. Past few weeks tablet was unused, charging from USB port in Sony Bravia TV.
Yesterday I've tried to use again, but I realized that it was turned off. After switching on and connect to wifi, he rebooted after a few minutes.
I found that without wifi lasts about 10 minutes before it restarts.
Strangest thing:
After each reboot, he booted into absolutely identical state. No matter that I uninstalled application, app was back, deleted files was back. But also all the changes of the past were gone.
I tried boot to save mode – after while he rebooted too
I tried leave tabled few hours in TWRP recovery - he has not rebooted, so he’s not unstable
I tried delete cache – no change
So I tried factory restore – after reboot he booted without change, hmm…
So I download nexus image a start “flash-all.bat”. No error, but after reboot. Surprise – no change – my old rooted system.
Via TWRP recovery I tried format/wipe everything, no change I even change filesystem from ext4 to F2FS – after reboot data are back
If I make backup in TWRK into internal memory (boot for instance), backup completes ok, but after reboot backup is gone.
If I start big backup (3gb data) into internal memory, backup fail after few minutes. But backup via otg to usb flash disk completes OK. So I can create full system+data backup.
It’s like flash memory is damaged and allow write only a small amount of data. And after reboot is restored to identical state. That would explain why Android reboots after a while, and recovery not.
What do you think? Can it be anything else than damaged flash memory? And if so, is there anything i could try, or "Zed is dead"
And finally it’s possible that Sony TV cause this? Thank you and sorry for my bad English.

Exact same thing happened to me, Bought a new motherboard for around $20 online... ebay I think and fixed it good as new... plus i upgraded to the 32GB model! replacement was pretty easy, I have never done anything like this before but didn't encounter any problems. I think its due to the flash memory dying, and becoming read only. I even formatted the whole drive from my computer and when I rebooted, Exact same old system. Here's the iFixit guide I followed: https://www.ifixit.com/Guide/Nexus+7+Motherboard+Replacement/9943

Happened to me too, and I also just replaced the motherboard. I have a feeling the equivalent of the boot sector fails, but on a ssd that puts the drive in read only mode. I seem to recall a fix using a non standard partitioning tool whose name escapes me, but our normal flash and recovery tools won't work. I wanted 32 meg upgrade anyway so decided it was best to replace rather than repair.
Sent from my Nexus 7 using Tapatalk
---------- Post added at 12:48 AM ---------- Previous post was at 12:43 AM ----------
Ah, tool is called NVFlash, but been years since I used it so can't help with instructions.
Sent from my Nexus 7 using Tapatalk

Thank you all for reply. Unfortunately cheapest 32GB motherboards on ebay cost 45$. But but I'm afraid that 32 gigabytes version will not be much faster. Nexus 7 has a terribly slow storage. Recently i bought Onda tablet V891, for 140$ and it's and it's perfectly fast device
When I think about it, the problem was caused by Titanium backup backuping every day. Finally, a flash memory did not last.
Thank for NVFlash I'll try to write here how it went

I just bought a nexus 7 / 32g with a broken screen for about 25$. Used, but worked. And now have a few extra parts...
Sent from my Nexus 7 using Tapatalk

Got my Asus Nexus 7 (2012) to finally charge and boot up!

Dear XDA,
Well please bare with me for a bit as a explain my situation. Back in 2013 I rooted my Nexus 7 using a toolkit. Was running great, but for some reason back in 2014 after loosing battery (to 0%) failed to charge, I forgot about it and left it plugged in for a week, somehow it was alive again! Similarly, 2 months ago the tablet died (0%) and i forgot the charge it for awhile, when I went to charge it, it wouldn't. Lo and behold tonight when i tried to charge it, it booted up fine!! I think its because I haven't been using it or forget about it that it does this! So I decided to use this more often as a testing device while keeping my s7e unrooted. The tablet was laggy and avg said there were some risk. I basically logged off everything, disabled backup and restore and did a factory reset, now its fine but I feel that after a load apps again it will slow down (again). So I am thinking of actually flashing a 6.0 rom (since 7.0 is pretty beta) but I am wondering how I should do it?
It seems I am on Teamwin v2.2.1 for recovery and I am on the Android 4.2.2, SmoothROM V5.0, Build number JDQ39, kernal version 3.1.00-g05b777c. I am planning on using it as a emulator tablet, streaming games from other hardware, media consumption and computing usng gnuroot debian and otg stuff along with using my s7e.
Any help would be appreciated!

Won't power on, won't power off, screen has nothing... help?

I went and installed a snapshot of CM11 to my nook color like an idiot, forgetting that it was a freaking snapshot and those are unstable. It worked fine, but when I powered it off.... It won't power on, I don't think it's off, but the screen won't even flash. Tried plugging it in, fully charged at the moment..... Read somewhere else on here that it can mean corrupted boot files - my microSD almost definitely doesn't have corrupted boot files because they worked just fine before and I did nothing that could corrupt them, yet it won't boot with or without the microSD in. Anyone know how to fix this?
Right now I'm trying something that has worked with a Motorola Xoom that I once overloaded the processor of - fully charging it, giving it a few days unplugged, and trying again to power it on.
Anything quicker than this that might help, if possible without requiring me to format my microSD?
Also, FYIs: Nook is long since rooted, had Cyanogenmod 10.1.2 running just fine but wanted an upgrade to 11. Stupid me didn't wait for the nightly to finish downloading and figured I'd try the snapshot, which may have killed it.

Same Problem So Far Nothing Working...
:crying:
just_magikkal said:
I went and installed a snapshot of CM11 to my nook color like an idiot, forgetting that it was a freaking snapshot and those are unstable. It worked fine, but when I powered it off.... It won't power on, I don't think it's off, but the screen won't even flash. Tried plugging it in, fully charged at the moment..... Read somewhere else on here that it can mean corrupted boot files - my microSD almost definitely doesn't have corrupted boot files because they worked just fine before and I did nothing that could corrupt them, yet it won't boot with or without the microSD in. Anyone know how to fix this?
Right now I'm trying something that has worked with a Motorola Xoom that I once overloaded the processor of - fully charging it, giving it a few days unplugged, and trying again to power it on.
Anything quicker than this that might help, if possible without requiring me to format my microSD?
Also, FYIs: Nook is long since rooted, had Cyanogenmod 10.1.2 running just fine but wanted an upgrade to 11. Stupid me didn't wait for the nightly to finish downloading and figured I'd try the snapshot, which may have killed it.
Click to expand...
Click to collapse
---------- Post added at 08:39 PM ---------- Previous post was at 08:24 PM ----------
I G
Dj-kream said:
:crying:
Click to expand...
Click to collapse

I actually waited a few days and then it worked again... Forgot to post here and say so xD my problem fixed itself c:

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.