Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
napstr said:
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
Click to expand...
Click to collapse
Hi.
According to what you say, it seems an hardware problem of you phone. Don't know if it may help but you can try installing an older factory image (for example kitkat) and seeing if the "force closing" problems are still there. If your phone is ok it should be able to run a factory image at least.
Download the nexus root toolkit, create a nandroid backup, then when either in CWM or TWRP wipe everything off the phone then try to flash a ASOP rom like Cataclysm if nothing else works then I don't know how to help sorry-.-
So I tried to get the stock ROM up and running again, and it seems even that is not possible. Several processes keep crashing during various tasks, even when idling. After having a short chat with Google Support about the issues I got an RMA offered, so things are cool. I locked the phone again, set the tamper-bit to false and wiped everything.
I had CM12 for a long time now, but it kept annoying me with update notifications, so I finally gave in.
Installation went fine and booted.
Then I installed this gapps. Upon booting, it kept going in a loop of "Google Services has stopped working". Then after a few minutes it went into a boot loop that keeps crashing a few moments after human interaction is possible.
The worst part is that I also can't get into recovery. I can go to fastboot mode, but upon trying to enter recovery the phone boots normally instead.
Did it get bricked?
Thanks.
To follow up, I went to sleep, and after I woke up, my phone finally agreed to go into recovery for some reason, so I formatted everything and reflashed CM13 with Open Gapps this time, and it seems to work.
I noticed the Open Gapps notes for Android 6 say it must be installed before booting, while I installed the above gapps after booting, so that might have been the problem.
I might as well try here if anyone will see my post.
I'm screwed. Latest stock ROM, unrooted and locked bootloader. I have/had the Google App (beta) installed on my phone but for the past couple of days it was constantly crashing and my phone became sluggish so I decided to uninstall it today. I left the beta program and as provided with instructions there went to uninstall the beta version to install the non-beta one.
It stayed on "uninstalling" for about 10 minutes and I presumed it was just a Google Play glitch and decided to reboot my phone. Big mistake! After the first install it was optimizing apps (but only one, so it was probably the Google App but it never got out of the next step (starting system/app, I don't recall what it said exactly right now)). I decided, stupidly, to reboot the phone since it was stuck and now I'm stuck on a bootloop and the phone won't even go past the Android logo animation. I guess the uninstallation never completed somehow and the app got corrupted(?).
I'm lost and I don't know what my options are except trying a factory reset and/or even unlocking the bootloader and getting a custom recovery and potentially rooting the phone too. But I really don't want to lose my data!! I have no backups.
Is there ANY chance I could somehow manage to solve the problem? Is it possible to sideload an app with a locked bootloader and stock recovery? I'm trying to sideload the Google app back in case it got corrupted but it doesn't work. I get the following errors:
Code:
E: footer is wrong
E: signature verification failed
installation aborted
Haaalp!
EDIT: Even weirder. I just let it run the booting sequence again and it got beyond the lollipop logo animation and is now stuck on "Android is starting... Starting apps." message.
Hi, this is my first post here. I've been using Oneplus one since 2014 and recently I facing a really strange issue. I have the CM 11.0-XNPH30O running in my OPO. I tried to flash LineageOS 15.1 and 14.1 but those got stuck in the boot and kept restarting after a certain period of time. That is why I had to come back to CM 11. Now the problem is, if I install a certain type of apps like- Viber/Whatsapp/Messenger/Greenify/Android health checker/Imo etc. then the phone restarts and does not boot, it falls in a bootloop. But I have installed some other apps(instagram) and games and those work totally fine. So, if I boot the phone into safe mode and then uninstall the apps that cause this bootloop (viber/messenger) and reboot, then the phone behaves normal again. I don't understand why this is happening. I wiped the phone clean a several times and tried to flash other ROMs but unfortunately no effect. Could anyone please give me suggestions? Thanks.
Note: I replaced my battery recently because the previous one was got me in the nonstop bootloop.
Pardon for a long story but someone gave this Samsung J7 Prime(SM-G610F) to me with an issue "An Error Has Occurred While Updating The Device Software". So I gave Samsung Smart Switch a try sadly they removed the Initialize option and old version don't seam to do what it suppose to do so I wen to a traditional Odin flashing. I then look for a stock rom for the phone that I think is the right one. Started with android 6 MM region pakistan and flashing went well. I was able to use it for a good hour or two until I notice it restarted by it self, then it keeps doing it 10-20 seconds after booting up. I though its the firmware I'm using so I went and look for Oreo version this time I region india (I don't know if region matters). So I flashed it again and tested the device again. I'm still able to use it for a good while till it restarted again. I then keep testing it to see what may be causing the problem. I notice that when the WIFI is on it just crash the phone to reboot so as soon as the phone reboots I turned the wifi off and it didn't crash anymore. I then factory reset the phone cleared everything, wipe cache then installed benchmark tools first. Thing I notice is it crashes when Google Play store is trying to install or download something. I tested it a couple of times to see when it crash and it does crash when downloading or installing something. I was still able to install 3Dmark and run it with wifi off. It completed the test without crashing so it couldn't the processor issue. I then look for another rom and tried flashing it. This time I had issue with it failing at system.img even if I use recent rom that worked. I then keep trying till flashing TWRP worked and flashing the rest of the rom is fine again.
What bothers me is why doesn't it crash during the first couple of hours. I've search similar issues and they say it may have been and app issue. I've already disabled bunch of app but nothing changed. Run the phone in safe mode but this time instead of crashing and rebooting right away it freezes for a few seconds. I suspect if google play or something being an issue since I've tried disabling it and it didn't crash for a couple of hours. Looked for allot of related thread but none of them seam to solve my problem.
I suspect either its the rom that I'm using and it can only be fixed by using the original rom, or its having a memory issue but don't know how to pin point it. Anyone can suggest on how I can debug this? I'm used to debugging things in real time and my knowledge with android is a quite slim but as a programming understanding the errors won't be a problem. I hope.
Edit: Hmm. Does copying kernel log with TWRP work or the kernel logs get overwritten every time the phone reboots? Because I see the kernet logs but don't see anything failing except for something saying SHUTDOWN but I don't think thats it. :S
Still no reply. :S I think its /system dismounting it self while doing a write operation. but it doesn't trigger until a certain amount of time after the phone is flashed or factory reset. I have to go to recovery and mount system back but that only happens on marshmallow. over version it remounts it self after the random reboot. After factory reset I'm able to install COD mobile and play a couple of match. after a long while it just decides to reboot.
I also tried z3x and after reading PIT from phone OK. the phone just reboots and flashing completes without it doing any flashing.