Hello everyone,
I am having I9301I for few years. Two nights ago it rebooted during Play Store updates into bootloop and now behaves like crazy.
First I wiped it, clean install, even reverted it to stock and back to CM12. On stock it is always in boot loop, on CM/RR it boots up until "Unfortunately, Setup Wizard has stopped".
Now, I think it's mobo is dead - some of partitions have bad super blocks, I asume /dev/block/mmcblk0p20 and mmcblk0p22 (dunno what are these for tho but according to e2fsck they have bad superblocks).
I would like to try to fix it before I order new mobo (you can never know what condition it is when you are getting it here...)
Does anyone have ideas about what to do?
//Edit:
CM11 - KK4.4.4 works fine so far...
Gonna test more...
Device is and always was a secondary device and I don't care for it very much. It was used to debug first versions of CM11, so...
Related
Hi folks.
So after a sleepless night and a lot of guessing and clicking around with no luck, I finally decided to ask for help.
The story:
Yesterday, I decided to open up my lovely N4 to perform the thermal pad mod (that can be found on these forums), as it was going really hot around the CPU at time and it seemed like a good solution.
Now, I'm no stranger to disassembling microelectronics without breaking them (few weeks ago, I successfully resoldered a broken power button in my old T989 that I've been using before N4).
What couldn't let me sleep at night:
And here is where the problem emerged. After re-assembling my sweet little phone (yes, i did it perfectly right), I tried to boot up and all i could see was an endless and really annoying bootloop, but as the device booted up, I did not worry much. While doing some research, I read that there's people experiencing bootloops with 4.3, so I thought that after disconnecting the battery, it just might've had happened on its own (I was using stock 4.3 with faux kernel before the nightmare started)
At this point, I booted into recovery and tried to flash the rom over, but unfortunately nothing positive happened. Then I tried factory reset and flashing different roms, also with no luck. This is when things started to get really frustrating, as no matter what I flashed, the bootloop was (and is) still there. But then I tries to restore a backup that I did right after getting my N4, back in November, and it WORKED. Why do i still have a problem then? Because it was 4.1 and OTA was giving me error every time I wanted to flash the update, so I kept flashing till i get some results. And then one of the N4 toolkits wiped my entire internal memory and I ended up with only being able to use sideload. Then I tried ALL of the N4 toolkits that can be found in here, to wipe everything and bring my phone back to everything stock, but the bootloader is locked so it cant do it, and it cant unlock it because I cant boot into the system.
Conclusion:
The phone works fine, and it proved it. But no matter what I try to flash (other than the old backup), the persistent bootloop is still there smiling at me like an a****le.
Any ideas?
Hey all,
First post here on XDA and I'm hoping someone with more experience than me will be able to give me a hand! Until last week or so, I was running an up-to-date version of Lollipop (5.1.1), when my tablet started randomly freezing up on me, requiring "soft resets" to get it going again, or simply shutting off on me. Thinking it was software related, I tried wiping the cache with no success, so ended up doing a full factory reset. The issues *seemed* to clear up for a day or so, but came back, and so figuring it was Lollipop related, I wiped out the OS and installed CM12.1 (which was my first experience working with ADB and fastboot, and first time installing a non-stock ROM) with a TWRP recovery. A few days later, the freezing and shutting down issues began popping up again, with the shutdowns *usually* happening during sleep, but the freezing happening at anytime from initial "Google" logo to boot animation, to the middle of running an app. I had made a backup on TWRP when I got CM12.1 configured the way I wanted it, so I performed a soft reset when it froze on me, and booted into the bootloader. The tab kept freezing in the TWRP window before I could select a restore, so out of desperation I tried just doing a factory reset from within TWRP. Long story short, something must have happened during that reset, because it kept hanging on the boot screen. I thought I may have unknowingly messed something up, so I tried downloading and flashing a stock KitKat (4.4) ROM from Google's site, but kept encountering bootloader errors during the flashing and ended up only being able to boot to the bootloader screen (apparently got a faulty 4.3 bootloader in that ROM, which gave me a headache until I was able to get straightened out). I have been able to get a stock bootloader (4.23) up and running now, along with a stock recovery (going with Lollipop now, so stock for LMY47V) going, but that's it. I've tried flashing the stock lollipop image via shell script (I'm running a Fedora 23 machine), via individual commands, and via "fastboot update -w factory_image.zip" without success. ADB sideload still works via recovery, but I wasn't able to sideload the OTA packages for 5.1 either. The common errors that pop up seem to indicate an error (corruption? fragmentation?) on the cache partition, but I'm not a dev when it comes to Android, so I'm at a loss here... I keep getting "E: failed to mount /cache (Invalid argument)", and other errors associated with accessing/opening files further down the /cache tree. Would this error be more likely to be a hardware issue, or would it be a software/firmware issue? I've had similar errors before with USB drives, when they would start to bad and partitions begin failing, but have always been able to rebuild them and get my data back. If something like this is happening on my N7 and the cache partition has indeed become somehow corrupted and failed (but not physically....), is it possible at all to rebuild partitions on Android in a similar manner? I've scoured the web, but haven't been able to find anything that can help me out with something like that, so I figured my best bet before condemning the N7 to the junk drawer was to see if any of the pros around here had any words of wisdom that *might* get me back up and running. Thoughts and advice much appreciated!!
Thanks!
(Oh, I apologize for the lengthy post, but I wanted to be sure to provide enough background info..... Sorry for the lengthy read!!)
Honestly that sounds more like a hardware problem than a software problem.
During the early stages of booting, everything that happens is extremely deterministic - meaning that it should be completely repeatable in terms of the order & timing in which activities occur.
So, for it to behave erratically during early boot suggests that it is not software, but marginal hardware. If hardware is barely meeting logic levels or timing requirements, a small amount of random noise (which is always present) can cause a fault to occur at any time - and that sounds approximately like what you are observing.
Further, you replaced your ROM entirely and the problem persists - again suggesting that the problem is hardware, not software.
The most cost effective way of dealing with repair of a $200 tablet is - unfortunately - disposing of it and buying a replacement.
Sorry.
Thanks for the reply!! Shoot, that's what I was leaning towards too. What is the life expectancy of these tablets? I mean, I got 3 good years of use out of it, so I'm not going to complain, but it seems like they should have lasted longer... Would it be worthwhile to maybe grab a cracked screen N7 off eBay for parts and try to get my tab working with those parts maybe? I'm hoping the rumors are true about Google coming out with a new tab this fall, but I'd love to get mine working before then lol...
Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!
Hi, I have this exact same issue with my N910T and so far haven't found a solution to this. I really love my Note 4 so I'd like to know if this issue can be solved or not. I event went to a supposed repair shop and they couldn't figure out the problem, guess they weren't that good.
Sorry to hear this.
I have found issues that seemed similar, but not quite the same, and people hinted that it could be a worn out motherboard that is causing this top happen. But before I open up the phone (at the potential risk of breaking at least the screen) I would try everything else.
Or is there a way to test whether the motherboard is defective?
Its the plague of overheated, worn out emmc memories, sadly. Once it happen,the only way is a new/used motherboard,prefferably C model.
eMMC failure, snapdragon models are susceptible to this.
Tüddels said:
Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!
Click to expand...
Click to collapse
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.
Hey,
thank you for your responses. Yes, I read a lot about it being a motherboard problem.
I got it to work now thanks to this post: https://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
First nothing happened, but after I flashed Modem and the original Bootloader again (after installing the rom) the phone turned on and I was able to use it for a while (20mins maybe). Then suddenly it turned itself off and stayed on the "Samsung Galaxy" screen for a long time.
Apparently a lot of people are using Wakelock and it seems to be working for some of them, but that seems to defy the point somehow.
KirbyFan64 said:
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.
Click to expand...
Click to collapse
Which Stock Rom did you use exactly? Is your phone working fine?
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.
hi there guys, I have an issue since a lot of time with my G2; basically when I restore a stock ROM sometimes it works fine sometimes it constantly reboot after caching the apps when it starts.. For example I had the issue in the past then successfully restore Lollipop stock and rooted it; now I'm not able to make it boot again
anyway I just flashed the tot 16 GB firmware available and I choose to use for once the BOARD Dl option there. The device booted up into a test mode, I pick the All test choice and so I noticed something interesting.. the only voice that seems to fail is the TA wrong one.. it says Fail next to it.. I searched for this TA thing and it seems to be a Trim Auto partition, maybe where there are DRM stuff, proprietary things to make things harder for people wanting to root. but to be honest I never heard of it before ten minutes ago!
I also searched for this partition of the 16 GB partition available but I'm not sure there's one.. Still if it's true it's a partition!
Do you have any clue about that?
Also I would like to ask if to flash recent ROMs (Oreo / Pie) is mandatory to upgrade to stock Lollipop before or even KK would be good...
Thanks a lot guys, hope you could help, I feel bad for my G2, even if in the meantime I upgraded to new devices it's still my little one!
I rec ently changed the digitizer touch screen on my LG Stylo 4. Every thing seemed fine then now will blink what ever screen your on (on /off) (on /off) continuously without being able to touch anything to get out . I have to unplug cable from battery /reconnect. Per back up and it's fine as long as it is not moved. As soon as I pick it up same thing. I'm ready to throw it in the street or let my pit bull have a new chew toy! Would you have any suggestions?