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?
Related
I got the device two days ago and rooted it the night I got it but remained stock to get use to it a little (came from MT4G) and still not use to the lack of physical menu buttons.
Anyways, after rooting and going through the process CWM, SU, ect. everything looked good for a while but today I had two random reboots from locked screen (went to unlock the device and it rebooted, the same way both times but not full reboots they were short and quick) and I was wondering if anyone else had this same issue and if so how to correct it.
There was another thing, when I boot into recovery it loads fine but when I reboot back to ROM it says there was an improper boot and wanted to send crash log to HTC. Not sure if this is going to be the normal thing but if anyone else is having this every time they go into recovery is there a way to opt out of it by default?
Thanks for reading.....
Orical said:
I got the device two days ago and rooted it the night I got it but remained stock to get use to it a little (came from MT4G) and still not use to the lack of physical menu buttons.
Anyways, after rooting and going through the process CWM, SU, ect. everything looked good for a while but today I had two random reboots from locked screen (went to unlock the device and it rebooted, the same way both times but not full reboots they were short and quick) and I was wondering if anyone else had this same issue and if so how to correct it.
There was another thing, when I boot into recovery it loads fine but when I reboot back to ROM it says there was an improper boot and wanted to send crash log to HTC. Not sure if this is going to be the normal thing but if anyone else is having this every time they go into recovery is there a way to opt out of it by default?
Thanks for reading.....
Click to expand...
Click to collapse
If you boot into recovery or hard reset by holding the power button. It will always ask to send crash report
OK cool so it's normal, thanks for the information.
I want to start out stating that i am very familiar with android's but have never experienced anything like this.
The first thing I tried was to oem unlock it from fastboot, which it claimed to do however i am skeptical as nothing else seems to stick, attempted to install cwm and TWRP neither with any success, even though it says the action was performed successfully.
The strangest thing is that i deleted all the apps on the device from settings/app, but when i rebooted my device they all came back!
All i wanted to do was do a factory reset, which also claims to finish successfully but after rebooting from recovery mode, i am back where i started.
App Updates also do not work as every time the tablet reboots, the apps have to be re-updated.
Its like the tablet is stuck in a read only state and when it reboots all changes are lost.
Like i said, this thing is acting weird and i have no idea where to go from here. Any help would be greatly appreciated!
[Update: Tried RSDLite, same results, Result is PASS however after system reboot everything is the same.]
Another update, tried downloading HWI69 which is the stock rom, tried to fastboot each image but nothing sticks even though it seems to say it writes it to the system. I'm starting to think the NAND memory is locked up and cannot be written to anymore if that's even a possibility.
BUMP
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.
Stock Galaxy S7, no root, no dubious apps, only AirWatch Agent: play.google.com/store/apps/details?id=com.airwatch.androidagent required for installing a corporate email client on the personal phone.
Everything worked fine for months, until yesterday, when the app AirWatch crashed, and would not start.
The user decided to reboot the phone. On the reboot, the phone got stuck on the second Samsung logo animation.
Wipe cache, force restart, reboot, reboot bootloader were tried, hoping to fix this boot issue, but without success. The phone still stays stuck at the Samsung logo animation.
What I'm looking for: to avoid phone ROM reflashing, because it has no backup and the data on the microSD card is encrypted.
I want to recover the personal data, by any means.
Any suggestions on how to achieve this?
Thank you.
If you can't flash stock, and have already wiped cache, and the guy doesn't have a backup (dumb), then there's not much else you can do really
I'm not sure which part of the phone the encryption key is stored, but you could try flashing just the Bootloader part of the ROM with ODIN
Also not sure if flashing the same stock ROM over the top, but using HOME_CSC instead of CSC to avoid the factory reset, would mess up the encryption, but as a last resort it would be what I would do
Backups are good, if the data is so important to encrypt I can't see why it would not also be backed up
I understand your point and I agree with it.
As a sidenote, that encryption was required by the app AirWatch, not by the phone's owner.
We'll try those steps as a last resort, but for the moment, we're gathering information, since most of the options are a "no way back" process.
For example, I'm thinking about a way to inspect the boot process, and alter it if there's something there that hangs.
Could this be possible? Is there any documentation about this?
germanino said:
I understand your point and I agree with it.
As a sidenote, that encryption was required by the app AirWatch, not by the phone's owner.
We'll try those steps as a last resort, but for the moment, we're gathering information, since most of the options are a "no way back" process.
For example, I'm thinking about a way to inspect the boot process, and alter it if there's something there that hangs.
Could this be possible? Is there any documentation about this?
Click to expand...
Click to collapse
You could trying running a logcat with the phone connected to USB during boot, not sure if it will connect to adb though, worth a shot
https://www.xda-developers.com/install-adb-windows-macos-linux/
If it works it should show you what it's hanging on, no idea how you would fix it though without a custom recovery
I've been using package disabled pro for a such long while but I made a terrible mistake in the last few days, I saw Google services are using too much ram, therefore I tried to disable all of them once for all and there were no any issue appeared at the moment, but a nightmare happened as when I was reboot the phone, the boot screen was stocked on "SAMSUNG" sign and I was waiting for a long time but the system won't boot up, so I realised I was screwed up that caused a lot of problems for me, for example I forgot my Google password when I tried to reset it shows that I need to receive the code of Google authenticator and I can't use my phone at the moment, so I tried also to use reserve number to receive the code, but the sim card just doesn't play nice with me because the sim card what I bought was from overseas, so I just stocked, ENVENTUALLY I decided to reset the phone from recovery, I tried but the system with same issue as when it booted up, so I decided to flash the firmware but I got only a raspberry pi 4 with me, it's running ArchLinux and I did some research on internet, eventually I found heimdall and then I tried to flash an official firmware I tried few times but it doesn't work and I realised that the FRP is locked I have no idea about how to unlock it, the point is I'm assuming if the App causes problem if I can turned it off, for example if I flash some specific *.bin or IMG it may works somehow? I'm not sure, please help me out!!~
The problem is solved by @hainguyenthao