I know there are a ton of these already, but I haven't been able to figure out how to fix the issue that I am having with my OPO.
I just started a new job that uses google apps for email servers and calendar and stuff, and requires me to put Google Device Manager on the phone, which requires encryption.
So I am on 38R, rooted, with TWRP and unlocked bootloader. I am trying to encrypt, it starts to go through its process, reboots with the green android, then looks like the entire device just reboots at that point, and goes back to the OPO splash and boot screen, then back to the OS for me to unlock to open and use.
It doesn't do anything, no encryption, no wiping the system...it just...reboots.
Anyone ever experience this and figure out how to get past it?
So I'm here at work.. working with my phone plugged in, charging, doing it's thing which shouldn't be much when I look over at it there's a bunch of "application x has crashed" and then reboots. Except it only sort of reboots. It sometimes hangs on the reboot, and if I reboot it 3-4 times it might come up into the OS but then all those messages appear again and it'll reboot itself.
I don't think I've installed anything crazy recently and blocked updates a long time ago when I got it, and am rooted with TeamWin recovery on it. I go into recovery and do a fix permissions and permissions and I get a bunch of errors to the effect of "e: xml error parsing file"
I do see that I have a nandroid backup from about 3 months ago that I might just have to try restore, but it's just weird that it seems like the phone just crashed itself. Can anyone think of any options I can try before I do that?
Also I don't think the phone has ever been updated since I got it as I froze/killed that process. Should I try upgrading to the latest? Are there big fixes/security issues that I should be concerned with that would make me want to upgrade?
Thanks for the help.
natboy said:
So I'm here at work.. working with my phone plugged in, charging, doing it's thing which shouldn't be much when I look over at it there's a bunch of "application x has crashed" and then reboots. Except it only sort of reboots. It sometimes hangs on the reboot, and if I reboot it 3-4 times it might come up into the OS but then all those messages appear again and it'll reboot itself.
I don't think I've installed anything crazy recently and blocked updates a long time ago when I got it, and am rooted with TeamWin recovery on it. I go into recovery and do a fix permissions and permissions and I get a bunch of errors to the effect of "e: xml error parsing file"
I do see that I have a nandroid backup from about 3 months ago that I might just have to try restore, but it's just weird that it seems like the phone just crashed itself. Can anyone think of any options I can try before I do that?
Also I don't think the phone has ever been updated since I got it as I froze/killed that process. Should I try upgrading to the latest? Are there big fixes/security issues that I should be concerned with that would make me want to upgrade?
Thanks for the help.
Click to expand...
Click to collapse
1. What did you do to that x applications? Did you just disable like location in the privacy guard?
2. Well, try to wipe the x application's data in settings -> app menu. If you can't navigate to there, try wipe all your data via recovery
3. Try to dirty flash your rom
4. Change into another rom
After a bunch of reboots, I was able to get the phone up but half my applications were deleted including Google Play store and most other Google apps including Inbox, Gmail, Hangouts. I might be paranoid, but maybe it was a Stagefright virus, but I have no proof that was it.
In the end I restored my nandroid from 4 months ago and it's now stable. But seriously I wasn't touching it when it started and then proceeded to destroy itself. Very strange behavior.
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 am asking this mainly because I hope I'm wrong about my own assumption.
My phone recently started randomly rebooting itself. At a certain point I woke up and the battery was dead. So recharged it and found it not getting passed the Samsung logo. Thought it was a xposed module since it had been acting up since I activated that again. So decided to disable xposed completely without any luck.
At that point I have tried to put a new rom on it. First time it rebooted during the installation throuwh TWRP. Second time it actually completed the installation and I managed to get into the OS.
But when I tried to install an application through the Google Play Store, in this case Chrome, it rebooted again and get stuck in the boot loop again for a while until booting up again but as soon as I tried to install the app again it crashed again and this kept going.
Have now also tried to install a different rom but the phone either crashes during the installation in TWRP or afterwards while it's trying to boot at the flashing samsung logo.
My assumption is that the problem is hardware related since it happens with multiple roms and even during the installation of said roms. But I really hope I'm wrong about this.
It's a SM-925F if that is important to know somehow.
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.