To start android, enter your PIN - ZTE Axon 7 Questions & Answers

i successfully downgraded my A2017G to Oreo b02 from b03 about a week ago. I had to do a factory reset, then set it up with my Google account and after that it allowed to install b02.
After that I've only installed a few basic apps for my bank and so on while waiting for b04 to show up through OTA.
Anyway, fast forward to today. I haven't had any issues with it. But all of a sudden when coming back from working in another town its rebooted and ask me to enter PIN to start Android. After that when it's done rebooting I got some weird double spacing between rows of icons.
So, I reboot again and once more i have to enter pin to start Android.. But it looks better when finished. However, this Enter PIN to start Android feels a bit annoying. Apparently it's because Android thinks my phone is behaving strange. Is there a way to find out what it thinks is strange and stop it?

It may be a security requirement for your banking app. It's secure boot.
This is part of the options with lock screen method. Maybe try setting the phone back to a swipe unlock and restart, see if it stops the problem. If so, set up you preferred lock arrangement again.

Thanks. Sounds reasonable although I've been running these apps on this phone since I bought it back in 2016(maybe it's time for a new phone) with various Android versions and never had this before. The phone has also been running for about a week with the same ROM and app version before this happened.

I'd backup data and reset it. See if it runs better, but you could try going to stock recovery and clear the cache first, just in case that helps.
There may be some junk from flashing it.

Seems like a factory reset did the trick. It's been running smoothly for some time nu despite installing the same apps again. I even got the b04 upgrade through OTA. Thanks!

Cool, so you're happy with the A7 again?
I regressed mine from B03 to B02 and did forced update to B04 from stock recovery. Had a few hiccups but sorted them and it works ok now. Do want to reset it when practical though. I use it for work so not in a huge hurry, setup is a big deal........

RobboW said:
Cool, so you're happy with the A7 again?
Click to expand...
Click to collapse
Sort of happy I guess. There are still a few things like it not automatically mounting my sdcard after reboot and I'm a little thoughtful about how many more updates it will receive. But it works rather well now and I haven't found a suitable replacement yet so I'm happy with it for the moment.

Related

[Q] Encryption removal problem - CM to TriForce

I have been running CM (currently CM11) on my SGS4 since I bought it from Sprint in summer 2013. However, Sprint changed their international partners pretty seriously in the past 2 years, so I *really* need a PRL update for international travel. Normally the easiest way to do this is to reboot to stock or TriForce, run the "update PRL" and "update Profile" options from in TriForce, and go on with my life.
But I encrypt my phone. So I had to boot into TWRP, wipe and format *everything* and make sure the phone came up unencrypted in CM. All is OK.
So I reboot, flash TriForce 5.4 custom with stock (not KK) kernel. Flash works fine, I reboot... and am prompted to decrypt the device before I can do anything. None of the decryption passwords I've used in the past (I checked my password safe) are working. When I flash back to CM, it boots fine, and the settings says that the device is not encrypted.
I downloaded and tried TriForce 5.2 and 4.0, both are giving the same problem. I have used TriForce in the past on this phone, so it SHOULD be fine....?
Someone in #twrp said that the location of the encryption key changed from Android 4.4 to 5.0. So my only remaining thought now is that there was also a change from 4.3 to 4.4, and the encryption key for 4.3 didn't get removed in the wipe, and since the partition is NOT encrypted, the decryption, even if I have the right key, fails, so I can't get into the phone. Hope that makes sense.
Anyone have any guess better, or, if I'm right, know what I need to move/edit to fix this?
Followup: IRC #sgs4 suggested a full install of stock via odin, so I'll be trying that on Saturday, after I can get a new stock rom downloaded overnight. if there are thoughts before then, I'd love 'em.
docsmooth said:
Followup: IRC #sgs4 suggested a full install of stock via odin, so I'll be trying that on Saturday, after I can get a new stock rom downloaded overnight. if there are thoughts before then, I'd love 'em.
Click to expand...
Click to collapse
Followup - this was never solved before I dropped the phone and shattered the screen (literally days after this post). So if someone runs into the same thing... good luck.
docsmooth said:
Followup - this was never solved before I dropped the phone and shattered the screen (literally days after this post). So if someone runs into the same thing... good luck.
Click to expand...
Click to collapse
Thanks for the update, I was actually going to suggest stock ODIN instead of TriForce, but you are saying it did not work ? It's good to know for the future. I was initially going to encrypt my phone a long time ago, but I had concerns about decryption when switching ROMs.
My question is why the encryption was not removed after the format ? I've used TWRP to pretty much hose out everything inside the phone, so it's possible the encryption location is located somewhere else. I came across this article:
http://money.cnn.com/2015/05/21/technology/resell-android-phone/
So I guess even after a complete wipe everything ISN'T removed. Maybe your encryption was also stuck as well.................................... What new phone are you getting ?...................................
mikeprius said:
Thanks for the update, I was actually going to suggest stock ODIN instead of TriForce, but you are saying it did not work ? It's good to know for the future. I was initially going to encrypt my phone a long time ago, but I had concerns about decryption when switching ROMs.
My question is why the encryption was not removed after the format ? I've used TWRP to pretty much hose out everything inside the phone, so it's possible the encryption location is located somewhere else. I came across this article:
So I guess even after a complete wipe everything ISN'T removed. Maybe your encryption was also stuck as well.................................... What new phone are you getting ?...................................
Click to expand...
Click to collapse
I was never able to get the stock odin download. The whole problem came up because I was going overseas... I got around it by just buying a local SIM rather than using the Sprint roaming (again, I was doing all this just to update the PRL. new GSM SIM = no PRL update needed). On the way home less than a week later, I cracked the screen so bad the LCD and backlight wouldn't even go on.
I replaced it with a Nexus 6. A bit big, but it doesn't suffer Samsung software awfulness, so I didn't have to flash it with CM to make it usable.

Massive softbrick (haven't found a solution yet)

Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.
try safe mode
mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.
After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.
I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!
Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!

lag, freeze, restart after 6.0.1

hey guys, today i bought a used NOTE 4 for my mother, and when i checked the version it was 6.0.1...so i wiped everything and restarted the phone to get the best performance....but the phone lags and freezes a lot, especially in the camera, and it keep restarting all the time....what should i do? should i try to flash another FW through ODIN?
You mean you used the Factory reset option? That's not a full wipe, just resetting stuffs. And yes, you know the answer, wipe everything from a custom recovery, then flash stock MM ROM (always latest) via Odin. Earlier versions did have a reboot problem though, and lags here and there, but that's expected, but the last release, PE1, has got rid of all those problems, its a very good release already, and I am sure upcoming releases will only make it better. There are no major bugs at all, I don't even find any minor bugs except the need for a separate app to clear default apps selection.
Best of luck.
ithehappy said:
You mean you used the Factory reset option? That's not a full wipe, just resetting stuffs. And yes, you know the answer, wipe everything from a custom recovery, then flash stock MM ROM (always latest) via Odin. Earlier versions did have a reboot problem though, and lags here and there, but that's expected, but the last release, PE1, has got rid of all those problems, its a very good release already, and I am sure upcoming releases will only make it better. There are no major bugs at all, I don't even find any minor bugs except the need for a separate app to clear default apps selection.
Best of luck.
Click to expand...
Click to collapse
the phone is stock, it has the stock recovery, and i have the PE1 version, the exact name is "MMB29M.N910FXXU1DPE1"...and still got a lot of lag, freeze and rebooting.....is there another version?
EDIT: ok, so i flashed another MM through odin ( first time it gave me a fail) and then done a factory reset, now it's so much better, maybe not as smooth as my S6 but really fast and smooth enough...thanks for the help
EDIT: today the phone started to shutdown completly....not reboot....and you need to press the power button 10 seconds to reboot it or turn it on...is there any advice?
Guys . Ib tead the whole thread over last few day had wake lovk runnimg last couple weeks. Lastnight used kies for reset and it crashed half way.
I then used odin 307 and went back to stock 501
It booted strarted to restore from google apps ect .
I allowed the 1st 601 update
All apps running aok no crashing freezing no wakelock .. its asking for another 601 update. Im gonna hold back
Hope this helps .. will post agian in gew days with any updates
Good luck !!
Just download and install Wake Lock from Google Play Store. I had the same problem and more. Once I installed Wake Lock (on a fresh install from Android 5 up to all the 6.0..1 builds) phone doesn't shut off or freeze. Most importantly no more Boot Loops..

[A2017G] LineageOS 14.1 - Can not access TWRP anymore, can't get through setup either

Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks
OmegaFighter said:
Hey folks,
I did not find anything on this issue, seems to be rather unique. Let me describe the problem.
This is my father's Axon 7 and he wanted me to get him a different ROM on there, which I did, and it worked smoothly until today. It kept crashing, freezing and was literally unusable for unknown reasons.
So since he was going to be gone for the next few days, I had no choice but to remove the ROM and data and reflash it. HOWEVER I did not delete the internal storage since I did not think it would be necessary. Sitting in the setup, I had issues getting through it, it will not pop up the keyboard to let me type the wifi password neither does it let me pass through if I wanted to use mobile data. It simply gets stuck. Sometimes random android processes tend to crash and put me at the start of the setup and I can't get to the settings which does prevent me from enabling USB-debugging or OEM unlock.
If I try to get into the recovery (which is still on there) it will simply get stuck on the screen that says ZTE, did not work through fastboot either, same issue.
(I do personally think that some app data is corrupted and causes the issue, since I wiped everything except internal storage and I still have major issues)
So here am I, stuck. I hope someone can enlighten me, or tell me how stupid I am and point me at something completely obvious. Thanks
Click to expand...
Click to collapse
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty
Choose an username... said:
well, you can use EDL maybe?
The fastest way out is downloading the A2017G_FULL_EDL file from our Russian friends and use MiFlash while in EDL mode to flash the cluster**ck of a phone that you have.
The closest thing I've seen was a friend's Galaxy Grand 2 (like 5 years old) that maybe had a part of the system corrupted or a slightly dead eMMC. a bunch of stuff just crashed for no apparent reason. I reflashed the system and it got fixed for some time, then it started doing some weird sh!t again (after booting, you have an 80% chance that it will just freeze forever, hard reboot needed). But let's hope for the best and see if you can recover it by reflashing stock totally. If it still doesn't work you might be able to relock the BL and claim the warranty
Click to expand...
Click to collapse
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.
OmegaFighter said:
Hey,
After a long day I managed to fix it, I was able to use the adb in fastboot and could reinstall the recovery and managed to run it, deleted internal storage and reinstalled everything. Seems to have done the trick. I hope it will keep working now.
Click to expand...
Click to collapse
good

M9+ Marsmallow random restart problem

Hi!
First: Sorry for any miss spelling.
I successfully installed Marsmallow on my device with a weird way, but I have a problem with it.
It turns on well and I can use it (no bootloop or freeze on HTC logo).
After a random amount time, it seemingly freezes and exactly 10 secs after, it restasts itself from the HTC logo.
First, my way of installing 6.0:
I experienced the 25% error when I first tried to install 6.0 with the legit OTA software upgrade with my Europe version M9 plus (I Don't remember it's original build number, but this is a European modell). So I started the trial/error way of upgrading.
First thing was, bootloader unlock, and factory reset through recovery.
Second was finding here on xda a RUU collection for this device here
And I downloaded this one:
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_MR_HTC_Europe_1.85.401.6_Radio_1.1506V24P21.2005.0505_HT[W.T]_release_446584_signed.zip
I renamed and installed it with download mode.
I barely set it up, knowing what is my goal, and started OTA from there.
In short:
3 security update popped up for Lollipop, and then the first Marsmallow update.
It got through the 25% error, and installed without any problem, and with many update reboot.
After it booted, I checked if any more update was available and a second (security/bug fix) update popped up. (More on that later)
I did not updated thinking I got this far I might as well set it up (it is my daily driver).
I started to download my apps, but in the middle of it, freeze and automatic reboot.
I though it was okay, I continued the downloads and got into the settings to set that up... random freeze and reboot.
These happened random , not related to anything
I started to worry so I did that update.
After that, the problem remained, but less frequent and still seemingly unrelated.
What I tried:
Safe mode - nothing changed.
Factory reset - nothing changed.
First setup, then cache reset - nothing changed.
Keeping the phone's temperature low and monitoring it - nothing changed except it was cooler a bit of course.
Tried to block every possible app (even some system apps) without root access and using it a bit - nothing changed.
I tried these with the first 6.0 update as well.
This is where I need help. Any ideas what is the problem? I can post screenshots if needed.
I really like this phone despite the negative reviews and the lack of custom roms.
Thanks for every question and answer!

Categories

Resources