Since updating to Pie every once in a while after a reboot the phone wont take my PIN and tells me it's wrong. Rebooting fixes it generally but I'm worried at some point it wont any longer. Has anyone else had this issue?
thenags said:
Since updating to Pie every once in a while after a reboot the phone wont take my PIN and tells me it's wrong. Rebooting fixes it generally but I'm worried at some point it wont any longer. Has anyone else had this issue?
Click to expand...
Click to collapse
Rooted or not? If rooted, what magisk version are you using?
Yes, rooted. I'm using the latest Beta of Magisk due to issues with the stable version. After posting this it happened again so I had to reboot and upon rebooting it started loop booting. I reflashed Pie over itself and that got me out of loop boots and I've already had the wrong pin issue come up again since. I may just wipe today and start fresh.
Sent from my Pixel 2 XL using Tapatalk
thenags said:
Yes, rooted. I'm using the latest Beta of Magisk due to issues with the stable version. After posting this it happened again so I had to reboot and upon rebooting it started loop booting. I reflashed Pie over itself and that got me out of loop boots and I've already had the wrong pin issue come up again since. I may just wipe today and start fresh.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Did you try flashing this version of Magisk.. https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
No, I hadn't. I hadn't seen anyone else mention the PIN issue. Granted, I don't look in the Magisk threads very often. Unfortunately, the link he posts isn't working.
praveen6585 said:
Did you try flashing this version of Magisk.. https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
thenags said:
No, I hadn't. I hadn't seen anyone else mention the PIN issue. Granted, I don't look in the Magisk threads very often. Unfortunately, the link he posts isn't working.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I had this issue by rooting with the non-twrp method. I believe it also was caused by not removing all security before rooting...fingerprints and all. Eventually I ended up in the bootloop of death which I recovered only with fastboot flash-all.
I rooted again after all this (needed my substratum) and so far no issues since remembering to disable all security before rooting.
Ya know. I've always removed all security before flashing but read it's no longer necessary and when flashing Pie it was the first time I ever didn't. Wonder if that's related.
Sent from my Pixel 2 XL using Tapatalk
thenags said:
No, I hadn't. I hadn't seen anyone else mention the PIN issue. Granted, I don't look in the Magisk threads very often. Unfortunately, the link he posts isn't working.
Click to expand...
Click to collapse
Bingo. That's your solution :good:
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
thenags said:
No, I hadn't. I hadn't seen anyone else mention the PIN issue. Granted, I don't look in the Magisk threads very often. Unfortunately, the link he posts isn't working.
Click to expand...
Click to collapse
Here ya go if the link isn't working :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Badger50 said:
Bingo. That's your solution :good:
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Here ya go if the link isn't working :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Click to expand...
Click to collapse
Thank you. At the gym right now but will give it a shot when I'm home.
Sent from my Pixel 2 XL using Tapatalk
Does it solve the PIN Incorrect issue in TWRP as well?
JazonX said:
Does it solve the PIN Incorrect issue in TWRP as well?
Click to expand...
Click to collapse
Negative. That's a twrp thing. Which is hit and miss for many. The 3.2.2-0 seems to work better than the 3.2.3-0 version in that regard. However, it's not consistent among all users
Badger50 said:
Bingo. That's your solution :good:
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Here ya go if the link isn't working :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Click to expand...
Click to collapse
Just installed it. Hopefully this does it. Thanks for the help :good:
After a sequence of
1 Shutting down the phone
2 rebooting into safe mode
3 shutting down the phone again
and finaly my pin will work.
I believe its something with android P as I had the updated versions of Magisk and TWRP and worked fine on O.
And of course googles solution is to reset everything. That dose not help ever. Only makes me more frustrated.
Holy ____ just got the same issue and was on the verge of resetting. I was able to boot to recovery and sideloaded the Magisk version above, and it fixed the issue! Thanks @Badger50 !
Badger50 said:
Bingo. That's your solution :good:
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Here ya go if the link isn't working :good:
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
Click to expand...
Click to collapse
WorldOfJohnboy said:
Holy ____ just got the same issue and was on the verge of resetting. I was able to boot to recovery and sideloaded the Magisk version above, and it fixed the issue! Thanks @Badger50 !
Click to expand...
Click to collapse
Scary as **** the first time, eh? I had just got into bed for the night and was ready to sleep and rebooted my phone for some reason. Bam. Wrong PIN. I was like here we go... gonna be a long night.
praveen6585 said:
Did you try flashing this version of Magisk.. https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
Click to expand...
Click to collapse
This zip makes my phone bootloop. Is there an updated one? I am failing safetynet today, anyone else?
JazonX said:
Does it solve the PIN Incorrect issue in TWRP as well?
Click to expand...
Click to collapse
Badger50 said:
Negative. That's a twrp thing. Which is hit and miss for many. The 3.2.2-0 seems to work better than the 3.2.3-0 version in that regard. However, it's not consistent among all users
Click to expand...
Click to collapse
Try "adb reboot recovery" next time or switch to a custom kernel. This way you should always be able to enter your pin without the freezing/crashing. I'd recommend flashing @nathanchance's Flash Kernel via Franco Kernel Manager. Just flash and forget.
SirVilhelm said:
This zip makes my phone bootloop. Is there an updated one? I am failing safetynet today, anyone else?
Click to expand...
Click to collapse
There is this one..
https://nathanchance.me/downloads/magisk/Magisk-v16.7(1675006)-gbfac1f1bc28b.zip
Safety net failing is a known issue.. topjonwu has made the change in the code but a new version is not out yet with that change
praveen6585 said:
There is this one..
https://nathanchance.me/downloads/magisk/Magisk-v16.7(1675006)-gbfac1f1bc28b.zip
Safety net failing is a known issue.. topjonwu has made the change in the code but a new version is not out yet with that change
Click to expand...
Click to collapse
Boot loop on this one as well. oh well, the stable version doesnt seem to be having issues for me.
Related
Seems @nheolinkin solved this problem with a fair solution that I haven't tried (yet). Please go to his thread, I abandoned this experiment, but I thought I need to edit this post for a better solution and keep forum cleaner. Please visit:
https://forum.xda-developers.com/zenfone-5/general/share-discussion-users-problems-unlock-t3629739
Old experiment:
Hello folks!
I think i made it to unlock bootloader without any freezes.
This unlocker provides 6 different method to try.
If none of these work, there's nothing I can do more, sorry (for now...).
There's a latest beta script. I don't know it will freeze or not, go and test it.
First of all I am not responsible if it bricks your device and becomes unusable, so try if you want.
===AUTOMATED QUICK SCRIPT===
I made an automated flasher. Here's a quick explaination:
1 for my freeze patch.
2 for relock bootloader.
https://drive.google.com/open?id=0B6AxuGkWld1yYU5zNGR0SzQ2OXc
It will give you a better result but not the real fix.
==============================
===MY CONFIGURATION'S SCRIPT===
Quick explaination:
1 for unlock bootloader
https://drive.google.com/file/d/0B6AxuGkWld1yMUhpWWd5TWN0ZFk
This is the LATEST testing version.
Probably it won't work. Use Automated Quick.
=============================
==========KERNEL==========
Latest version number: 16.05
http://forum.xda-developers.com/zen...ne-5s-bootloader-freeze-t3362234/post66882948
===========================
Important Notes:
Thanks all the XDA Zenfone 5 Community and the friends that I've been talking about.
Disable dt2w for the reboots and I recommend using the latest Resurrection Remix by @tank0412, CM is a bit old; so that might do reboots.
Fastboot Archive (WIP): https://drive.google.com/folderview?id=0B6AxuGkWld1yYVdFZTFLckhaUDQ&usp=drive_web
Ifwi Archive: https://drive.google.com/open?id=0B6AxuGkWld1yWHV5Rm0yZUd4Q1U
When trying a new fastboot; for the best results you should wipe cache and dalvik cache.
If anyone bricked the phone when doing this, check the link: http://forum.xda-developers.com/zenfone-5/help/zenfone-5-a500cg-zenfone-6-a600cg-t3354645 (Credits to @swiczak )
@kanodiatushar tested and it worked. Thanks.
I searched about camera bugs and when i disable one core of my cpu, camera is not launching (I normally have camera on unlocked bootloader). So, about camera: Some cpu based bug on some devices makes camera bug on custom roms. Make sure you have four of four cores active and available.
Please give a credit to http://ozankaraali.com when sharing if it worked as i did to other users.
As I said, this is experimental and may or may not be working, even maybe it can brick your device and I need feedbacks negative or positive.
you are still experience freezing?what rom are you using @ozank?
davidjay26 said:
you are still experience freezing?what rom are you using @ozank?
Click to expand...
Click to collapse
i am still experiencing freeze sometimes but not that frequent, as i said i used 12 hours no-freeze then freezed. i am taking logcat now for the next time if it happens. until i make this i was getting freeze nearly every 30 minute-like and as i said, i need feedbacks for this experiment. i think this is not the end of all the freezes but still noticeable difference for me and i need to hear from the others
by the way using dgadelha's cm13, 18 apr kernel and 15 apr system.
Will try.i use cm13 by dgadelha too
Sent from my ASUS_T00F using Tapatalk
i used it on stock LP (.78 ) for 2-3 hrs
it freezes every 10mins
my device is zenfone 5 T00J
kanodiatushar said:
i used it on stock LP (.78 ) for 2-3 hrs
it freezes every 10mins
my device is zenfone 5 T00J
Click to expand...
Click to collapse
Thanks for the information, i will try better about that.
By the way can you see your serial number properly on this fastboot?
ozank said:
Thanks for the information, i will try better about that.
By the way can you see your serial number properly on this fastboot?
Click to expand...
Click to collapse
Yes, it did change to something EZA***
Edit: its E8AZCY***
kanodiatushar said:
Yes, it did change to something EZA***
Edit: its E8AZCY***
Click to expand...
Click to collapse
thanks for the information, i will try to find a more proper way, as i said, i partially fixed on my phone with this and i will try to fix for most of the devices
ozank said:
thanks for the information, i will try to find a more proper way, as i said, i partially fixed on my phone with this and i will try to fix for most of the devices
Click to expand...
Click to collapse
Thank you very much for your efforts and time
---------- Post added at 11:33 AM ---------- Previous post was at 10:54 AM ----------
ok i followed the procedure in OP and after the freezes i decided to relock the bootloader
i used the tool provided in the RR-LP thread to relock the bootloader
but then i unlocked it again by the flashing dnx then if.bin provided in the OP
and haven't faced any freezes since then
---------- Post added at 11:37 AM ---------- Previous post was at 11:33 AM ----------
@ozank is it because of the if.bin i placed in /system/etc/firmware/ ?
or does it have something to do with the your fastboot?
kanodiatushar said:
Thank you very much for your efforts and time
---------- Post added at 11:33 AM ---------- Previous post was at 10:54 AM ----------
ok i followed the procedure in OP and after the freezes i decided to relock the bootloader
i used the tool provided in the RR-LP thread to relock the bootloader
but then i unlocked it again by the flashing dnx then if.bin provided in the OP
and haven't faced any freezes since then
---------- Post added at 11:37 AM ---------- Previous post was at 11:33 AM ----------
@ozank is it because of the if.bin i placed in /system/etc/firmware/ ?
or does it have something to do with the your fastboot?
Click to expand...
Click to collapse
I thank you for your efforts about trying at least and giving me a feedback
I am happy that seeing you having not much freezes at all until now
And i don't know what's making the freeze and what is not making the freeze, i was just trying to get a solution, i researched that from the other users' ideas.
I think the if.bin placement is the key, without it, it freezed a lot more according to my experiment.
But as i said this solution wasn't the end of the all freezes so i am still searching the problem but it makes a little bit difference at least and wanted to share for relaxing our devices a bit.
Files were from the 1.18ish version (JB) and i will try earlier files like 1st asus rom and if it makes difference i will share.
i tried reverting back to 1.17.40.16WW and use the official unlocker and after unlock i immediately flashed the RR-MM rom and it freezed....
I will test it for a day... but can you suggest me if it will work on the RR-MM rom?
i mean i flash the rom
place the if.bin
set permission
and then unlock again using the files you provided?
---------- Post added at 12:30 PM ---------- Previous post was at 12:09 PM ----------
1st freeze
---------- Post added at 12:52 PM ---------- Previous post was at 12:30 PM ----------
2nd freeze
kanodiatushar said:
i tried reverting back to 1.17.40.16WW and use the official unlocker and after unlock i immediately flashed the RR-MM rom and it freezed....
I will test it for a day... but can you suggest me if it will work on the RR-MM rom?
i mean i flash the rom
place the if.bin
set permission
and then unlock again using the files you provided?
---------- Post added at 12:30 PM ---------- Previous post was at 12:09 PM ----------
1st freeze
Click to expand...
Click to collapse
I did like so on cm13 rom. I didn't revert, only changed fastboot images and i am having 12 hour no freeze duration and wanted to share the way, no need to officially unlock, it makes no difference except warranty. I will try to use ifwi, dnx and fastboots of other versions for no freeze at all and i think it varies for the different product bands (like august vs june factory phones).
So, when you trying this way make sure fastboot and ifwi, dnx files of same date and copy if to firmware.
There is just one if.bin for unlocking so this makes the problem and it cannot be compiled by anyone except asus, so we are trying to find the most compatible fastboot and dnx-ifwi bins to our phone. I think that's the key and kernel might search for if.bin on firmware folder if i understand correctly, if it couldnt find it freezes. (If the case is not placebo at all)
Well done... your solution make mine less freeze than before... thank you.
Sr for my bad english
akiralee said:
Well done... your solution make mine less freeze than before... thank you.
Sr for my bad english
Click to expand...
Click to collapse
i thank you for the giving feedback and trying my solution, have a good day and if i find any better solution i will update the first post
Edit: Check the first post, I uploaded a new kit, haven't tried that much so if you want to be a tester, go ahead and check it
ozank said:
i thank you for the giving feedback and trying my solution, have a good day and if i find any better solution i will update the first post
Edit: Check the first post, I uploaded a new kit, haven't tried that much so if you want to be a tester, go ahead and check it
Click to expand...
Click to collapse
Hi, I tried the tutorial in the first post with V2 files and I get a locked bootloader with ifwi 59.27. Why I get a locked bootloader?
leonardohenrique10 said:
Hi, I tried the tutorial in the first post with V2 files and I get a locked bootloader with ifwi 59.27. Why I get a locked bootloader?
Click to expand...
Click to collapse
try to flash if.bin again, if it doesn't work revert to v1.
edit: it's a testing build and as i said it may not work and even brick the device, so be careful.
that gave me a a1 bootloader and when i controlled that said signed bootloader, maybe this was a bug and first post edited with your feedback, i will try this build for a night and will report if it freezes.
i have noticed that my zen5 got freeze only when charger is conected, and i play some game (eg Contest of Chamions, Marvel)... after some like 40-50 mins, device is overheating, and freeze.
in other cases i dont have freezes
killar_aka_arabu said:
i have noticed that my zen5 got freeze only when charger is conected, and i play some game (eg Contest of Chamions, Marvel)... after some like 40-50 mins, device is overheating, and freeze.
in other cases i dont have freezes
Click to expand...
Click to collapse
yes i was talking about "not the end of the freezes" :laugh: on normal usage it works okay with this tutorial, but on charging and using heavy apps occurs freezes.
actually on another thread @pedromd did some ifwi.bins that i haven't tried yet. if anyone wants to try that, can check out his files.
that night, i will look at my v2-like solution and logcat it.
(it may not be working for the other users according to reports but i am now o my v2)
ozank said:
i thank you for the giving feedback and trying my solution, have a good day and if i find any better solution i will update the first post
Edit: Check the first post, I uploaded a new kit, haven't tried that much so if you want to be a tester, go ahead and check it
Click to expand...
Click to collapse
i think i dont need to try it.. because i used my phone last night and have no freezing during 3-4h... i think there no freeze more... thank for your help... :highfive::highfive::highfive::highfive:
akiralee said:
i think i dont need to try it.. because i used my phone last night and have no freezing during 3-4h... i think there no freeze more... thank for your help... :highfive::highfive::highfive::highfive:
Click to expand...
Click to collapse
You're welcome.
With 20 Kernel 19 System of dgadelha's CM, i didn't get any reboots on night charge and logcat terminal was there on morning. Only a bit network issue i found on latest release but not that much, if anyone encountering freezes, should try the latest build. I am going to test for daily freezes now. But it should be fixed with these files i suppose.
Thanks for the feedback and have a good day!
So yesterday I was taking a look to xda developers when I saw a post with cyanogen mod 14 for the Nexus 5x so I installed it. Everything went ok but after looking at the OS for a bit I thought that the OS i had was better (it was nougat 7.1.1, beta program) so before installing cyanogen mod i had made a backup of my older system. I tried to restore the backup but when i tried to turn on the phone it froze when booting, and that started happening over and over, it turns on shows google logo starts booting and freezes, turn of, turns on ....
I've tried to install many diferrent roms from here xda, the normal ones in root toolkit and nothing works, every rom freezes when booting. I've wiped the phone i've done everything i could do in TWRP.
Please if someone out there can help i would be very thankful.
Im sorry for bad english!
Usually you repair it by flashing firmware
rp158 said:
Usually you repair it by flashing firmware
Click to expand...
Click to collapse
How can i do that?
mike_seventeen said:
How can i do that?
Click to expand...
Click to collapse
Since you already tried toolkit and it didn't work,? Wugfresh?
---------- Post added at 03:25 PM ---------- Previous post was at 03:22 PM ----------
mike_seventeen said:
How can i do that?
Click to expand...
Click to collapse
Read this carefully, at the end there is a tutorial how to flash stock. It's number 9 or 10. http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930/page150
Stevica Smederevac said:
Since you already tried toolkit and it didn't work,? Wugfresh?
---------- Post added at 03:25 PM ---------- Previous post was at 03:22 PM ----------
Read this carefully, at the end there is a tutorial how to flash stock. It's number 9 or 10. http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930/page150
Click to expand...
Click to collapse
Sorry I had to leave. but i done what said in the tutorial and everything went ok. Now i have to install a rom right?
Thanks!
mike_seventeen said:
Sorry I had to leave. but i done what said in the tutorial and everything went ok. Now i have to install a rom right?
Thanks!
Click to expand...
Click to collapse
Yes but be careful what version of Nougat it is and try to match the vendor accordingly.
Stevica Smederevac said:
Yes but be careful what version of Nougat it is and try to match the vendor accordingly.
Click to expand...
Click to collapse
I installed the lastest version from google's developers website and now it just stays in google logo forever when booting
mike_seventeen said:
I installed the lastest version from google's developers website and now it just stays in google logo forever when booting
Click to expand...
Click to collapse
Didn't you say that everything went ok? What did you do in the meantime? You just flashed stock img? Try to do a factory reset from stock recovery
Stevica Smederevac said:
Didn't you say that everything went ok? What did you do in the meantime? You just flashed stock img? Try to do a factory reset from stock recovery
Click to expand...
Click to collapse
I done step 10 as you said to do from that post (http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930) then i installed the rom and know its basically happening the same thing that happened in first place.
I probably done something wrong installing the rom.
I've done factory resets several times in stock and custom recoverys
mike_seventeen said:
I done step 10 as you said to do from that post (http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930) then i installed the rom and know its basically happening the same thing that happened in first place.
I probably done something wrong installing the rom.
Click to expand...
Click to collapse
Or it's a hardware issue. Apparently, a lot of 5x are dying suddenly and lately. Try the factory reset first before you flash stock again.
Stevica Smederevac said:
Or it's a hardware issue. Apparently, a lot of 5x are dying suddenly and lately. Try the factory reset first before you flash stock again.
Click to expand...
Click to collapse
I'll do as you say, but if i can´t solve this i'm kinda screwed because i have no possibilities to buy another phone and i have this one for like 3 months, i have to solve this, i really do. Thanks for all the help! Really appreciated.
Ran into the same exact problem as OP, while restoring 7.1.1 backup when coming from MIUI 8 rom.
Same stuff when completely restoring to stock/installing a different rom etc.
Mike, did you restore EFS from TWRP backup? I have a feeling that it gets corrupted and it wont let the device boot anymore.
Because TWRP runs absolutely fine and even the file manager in it works perfectly, which indicates that it may not be similar to the hardware issue which people might be having.
Phone restarts after first loop of the bootscreen (after all the blue-red-yellow-green dots have turned to their initial size), correct?
Edit: See post #14 for fix.
tauio111 said:
Ran into the same exact problem as OP, while restoring 7.1.1 backup when coming from MIUI 8 rom.
Same stuff when completely restoring to stock/installing a different rom etc.
Mike, did you restore EFS from TWRP backup? I have a feeling that it gets corrupted and it wont let the device boot anymore.
Because TWRP runs absolutely fine and even the file manager in it works perfectly, which indicates that it may not be similar to the hardware issue which people might be having.
Phone restarts after first loop of the bootscreen (after all the blue-red-yellow-green dots have turned to their initial size), correct?
Anyway I did not manage to get it to boot again, I recommend you restore to stock via fastboot and lock your bootloader before you take it to warranty.
Click to expand...
Click to collapse
I restored through TWRP the backup i have then when i turned it on the dots just stoped the animation then the phone restarted and it just kept restarting over and over again. The problem is that the warranty ended few months ago, so or i solve this problem or i lose my money.
(I only have the phone for about 3/4 months but the warranty was almost over when i bought it(online))
mike_seventeen said:
I restored through TWRP the backup i have then when i turned it on the dots just stoped the animation then the phone restarted and it just kept restarting over and over again. The problem is that the warranty ended few months ago, so or i solve this problem or i lose my money.
(I only have the phone for about 3/4 months but the warranty was almost over when i bought it(online))
Click to expand...
Click to collapse
It seems you made the same mistake as I - You backed up the EFS partition and restored it. I read that this function does not work correctly with TWRP 3.0.2-1,2,3. It will corrupt your EFS partition.
http://forum.xda-developers.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119
Follow the first post exactly (even though its from the 6P thread), and it will get fixed .
tauio111 said:
It seems you made the same mistake as I - You backed up the EFS partition and restored it. I read that this function does not work correctly with TWRP 3.0.2-1,2,3. It will corrupt your EFS partition.
http://forum.xda-developers.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119
Follow the first post exactly (even though its from the 6P thread), and it will get fixed .
Click to expand...
Click to collapse
You have no ideia of what you've done, you are an angel, you just SAVED my life, i done as it says in the thread and the phone started, I can´t explain how thankful i'm feeling right now, THANK YOU SO MUCH, really, thank you so so so so much, I will never NEVER forget you. Thank you for saving my life! :victory: :good:
mike_seventeen said:
You have no ideia of what you've done, you are an angel, you just SAVED my life, i done as it says in the thread and the phone started, I cant explain how thankful i'm feeling right now, THANK YOU SO MUCH, really, thank you so so so so much, I will never NEVER forget you. Thank you for saving my life! :victory: :good:
Click to expand...
Click to collapse
No problem, just share the link to the thread from the 6P forums if you find someone with a similar problem.
Alright I posted about this on reddit.com/r/googlepixel earlier tonight and thought I fixed my issue. I installed Bully Scholarship Edition and within the first couple minutes of gameplay, my phone froze and some black bars appeared on screen. It rebooted several times then went totally blank. Couldn't get into bootloader/recovery. After putting it on the charger for a little bit, it turns back on. I thought all was good until after a couple hours it does the same thing after just being on the home screen. I consider myself pretty knowledgeable when it comes to smartphones and rooting/roming but am stuck. I tried flashing stock system images and it was okay again for a while but it eventually froze with the black bars on screen and kept rebooting. Is my best bet to RMA it. Any help would be appreciated.
Edit: Ok its officially dead. Screen won't turn on but can hear vibrations from notifications or if I hold power button to get to the power menu. RIP
I personally would try to RMA it, it sounds like a persistent issue. Did you try not installing apps and just run that way for 24 hours?
chapelfreak said:
I personally would try to RMA it, it sounds like a persistent issue. Did you try not installing apps and just run that way for 24 hours?
Click to expand...
Click to collapse
Ya I just got off of chat with Google. They are replacing it
what? dude all you have to do is flash stock boot.img why the hell wasn't that the first thing you tried. sounds like a kernel panic to me
---------- Post added at 04:24 PM ---------- Previous post was at 04:22 PM ----------
not sure why you would ever RMA without trying to first go back to stock firmware and factory reset
diabl0w said:
what? dude all you have to do is flash stock boot.img why the hell wasn't that the first thing you tried. sounds like a kernel panic to me
---------- Post added at 04:24 PM ---------- Previous post was at 04:22 PM ----------
not sure why you would ever RMA without trying to first go back to stock firmware and factory reset
Click to expand...
Click to collapse
I'm not dumb. I did both a factory reset first with no luck then flashed latest factory images. Still same issues persisting. It must be a hardware issue. I should be receiving a new one fairly soon
bdog2015 said:
I'm not dumb. I did both a factory reset first with no luck then flashed latest factory images. Still same issues persisting. It must be a hardware issue. I should be receiving a new one fairly soon
Click to expand...
Click to collapse
okay you didnt mention that
diabl0w said:
okay you didnt mention that
Click to expand...
Click to collapse
From the OP....
I tried flashing stock system images and it was okay again for a while
Click to expand...
Click to collapse
Threadskimmer!
CZ Eddie said:
From the OP....
Threadskimmer!
Click to expand...
Click to collapse
system images don't overwrite anything but the system partition
diabl0w said:
system images don't overwrite anything but the system partition
Click to expand...
Click to collapse
I don't think anyone would be dumb enough to only flash a system.img and not the whole factory image
Sent from my Pixel XL using Tapatalk
As the title States. I see a few builds of lineage for our phones. Curious if anyone has tried them out and if so how there running.
Update: Builds are running well. Issues on startup
1- If you can't get pass restoring ftom another device-remove sim to by pass issue...
OK google works. Even with screen off and unplugged
Root is built in
Gapps installed
Edit:
Here is the link to download. Permission granted by invisiblek. Big thanks to him for the builds.Give him credit for everything. Thanks cz for finding info!
http://www.invisiblek.org/roms/lineage-14.1/marlin/
Sent from my Pixel XL using XDA Free mobile app
I can't imagine it's far off from what CM was doing. Does anyone know if it's still heavily CAF?
Sent from my Pixel XL using Tapatalk
Nice to know. Is the pixel actually a supported device?
Where are these builds posted?
Not sure if they're still CAF based. I'd I.agine so since it's still basically cm. I haven't found any topics on em per se just builds. Invisiblek is where to look. There's builds for the marlin
Sent from my Pixel XL using XDA Free mobile app
Didn't realize it was out yet.
Was just about to reflash my DU but will download & try out the Lineage just to see what it looks like.
Consider me your first "thanks" for bringing this to our attention. :up:
Edit. It's booting up right now.
---------- Post added at 02:51 PM ---------- Previous post was at 02:35 PM ----------
I'm not getting far on the 1/14/2017 build of 14.1.
It boots up.
Gives this error which I've seen before and aren't worried about:
"There's an internal problem with your devices"
Then it quickly picks up and connects to my WiFi.
Then quickly enables my Data.
But then drops me into this screen:
"On your other device, open the Google app".
"1) Say Ok Google, set up my device"
"2) Touch Pixel XL on the list, and follow the on-screen instructions"
And I can't get past this.
I think it wants me to restore stuff from my other phone but I can't figure out how to get past this section.
So I can't get to Settings or desktop or anything else.
Lol well "thanks" sir. No problem.Ya wasn't sure if there usable or not yet . I have the 1/14 build downloaded was gonna pull the trigger to see what happens. Perhaps I try 13 build
Sent from my Pixel XL using XDA Free mobile app
CZ Eddie said:
Didn't realize it was out yet.
Was just about to reflash my DU but will download & try out the Lineage just to see what it looks like.
Consider me your first "thanks" for bringing this to our attention. :up:
Edit. It's booting up right now.
---------- Post added at 02:51 PM ---------- Previous post was at 02:35 PM ----------
I'm not getting far on the 1/14/2017 build of 14.1.
It boots up.
Gives this error which I've seen before and aren't worried about:
"There's an internal problem with your devices"
Then it quickly picks up and connects to my WiFi.
Then quickly enables my Data.
But then drops me into this screen:
"On your other device, open the Google app".
"1) Say Ok Google, set up my device"
"2) Touch Pixel XL on the list, and follow the on-screen instructions"
And I can't get past this.
I think it wants me to restore stuff from my other phone but I can't figure out how to get past this section.
So I can't get to Settings or desktop or anything else.
Click to expand...
Click to collapse
Where are these builds located? Lineage isn't doing official builds yet.
CZ Eddie said:
Didn't realize it was out yet.
Was just about to reflash my DU but will download & try out the Lineage just to see what it looks like.
Consider me your first "thanks" for bringing this to our attention. :up:
Edit. It's booting up right now.
---------- Post added at 02:51 PM ---------- Previous post was at 02:35 PM ----------
I'm not getting far on the 1/14/2017 build of 14.1.
It boots up.
Gives this error which I've seen before and aren't worried about:
"There's an internal problem with your devices"
Then it quickly picks up and connects to my WiFi.
Then quickly enables my Data.
But then drops me into this screen:
"On your other device, open the Google app".
"1) Say Ok Google, set up my device"
"2) Touch Pixel XL on the list, and follow the on-screen instructions"
And I can't get past this.
I think it wants me to restore stuff from my other phone but I can't figure out how to get past this section.
So I can't get to Settings or desktop or anything else.
Click to expand...
Click to collapse
I was able to get the 13 build running. i am trying the same on the 14 build to see if itll work on that one as well
Got the 14 build up and running. Seems pretty snappy. Gonna play around a bit to see how it is overall.
Edit:
Seems to be running well. Currently restoring apps. Has cm camera and apps loaded but can get all google apps back including pixel launcher.Pretty well polished as far as i can tell
@CZ Eddie, the "internal problem with your device" is due to an out of date vendor IMG usually. You can reflash the latest vendor.img from the factory IMG to get rid of this message.
Yeah, I knew it was something like that.
But it wanted Q instead of V.
And flashing that didn't resolve my issue where it's stuck at trying to restore from some other device (or whatever that prompt is).
I tried flashing the Q bootloader too and still got stuck.
CZ Eddie said:
Didn't realize it was out yet.
Was just about to reflash my DU but will download & try out the Lineage just to see what it looks like.
Consider me your first "thanks" for bringing this to our attention. :up:
Edit. It's booting up right now.
---------- Post added at 02:51 PM ---------- Previous post was at 02:35 PM ----------
I'm not getting far on the 1/14/2017 build of 14.1.
It boots up.
Gives this error which I've seen before and aren't worried about:
"There's an internal problem with your devices"
Then it quickly picks up and connects to my WiFi.
Then quickly enables my Data.
But then drops me into this screen:
"On your other device, open the Google app".
"1) Say Ok Google, set up my device"
"2) Touch Pixel XL on the list, and follow the on-screen instructions"
And I can't get past this.
I think it wants me to restore stuff from my other phone but I can't figure out how to get past this section.
So I can't get to Settings or desktop or anything else.
Click to expand...
Click to collapse
CZ Eddie said:
Yeah, I knew it was something like that.
But it wanted Q instead of V.
And flashing that didn't resolve my issue where it's stuck at trying to restore from some other device (or whatever that prompt is).
I tried flashing the Q bootloader too and still got stuck.
Click to expand...
Click to collapse
You can get it running. I have it running right now.Very smooth
Sent from my Pixel XL using XDA Free mobile app
tcarave said:
You can get it running. I have it running right now.Very smooth
Click to expand...
Click to collapse
Did you flash TWRP immediately after flashing the ROM?
I did.
Trying something else now and noticed that I somehow now have CM Recovery.
I stared at it for a minute wondering how Clockwork Recovery got installed on my phone till I realized what it actually was. :silly:
Yea I installed TWRP after ROM. Did flashing u vendor IMG get rid of internal error for you? I tried v and still got error but everything seems to be working well
Sent from my Pixel XL using XDA Free mobile app
CZ Eddie said:
Did you flash TWRP immediately after flashing the ROM?
I did.
Trying something else now and noticed that I somehow now have CM Recovery.
I stared at it for a minute wondering how Clockwork Recovery got installed on my phone till I realized what it actually was. :silly:
Click to expand...
Click to collapse
On initial boot don't set wifi. By pass it to get around restore. Wifi will pop up again at end
Sent from my Pixel XL using XDA Free mobile app
tcarave said:
On initial boot don't set wifi. By pass it to get around restore. Wifi will pop up again at end
Click to expand...
Click to collapse
Hah, yeah skipping WiFi setup got me past that restore from other device thing.
I'm logged in now and checking it out.
There are several custom options hidden throughout the menus. Not all packed into one section like AOSP ROM's.
I can't find an option to remove the brightness slider though, I really like that option and would miss it.
npjohnson said:
Where are these builds located? Lineage isn't doing official builds yet.
Click to expand...
Click to collapse
Also curious where these builds are. I tried googling it and nothing came up
Post #4 tells you where to find it.
---------- Post added at 06:33 PM ---------- Previous post was at 06:32 PM ----------
It wants the "Q" vendor image.
Its really smooth and has built in root...only thing I don't like is lack of pixel home button animation and it don't allow unlimited backup but I'm sure those features will become available in the near future (or I hope they will)
Great job with the ROM invisiblek!
Help me out ..this is what happens when I try to unlock boot loader.. I did factory reset but still the problem persists...
excitedgeek said:
Help me out ..this is what happens when I try to unlock boot loader.. I did factory reset but still the problem persists...
Click to expand...
Click to collapse
Logout and login in that should do
I also face this issue. Did you fix this anyhow?
Kaffer94 said:
I also face this issue. Did you fix this anyhow?
Click to expand...
Click to collapse
Verify your email...
Kaffer94 said:
I also face this issue. Did you fix this anyhow?
Click to expand...
Click to collapse
Verify your email that u used to login your SYNC IT app...
excitedgeek said:
Verify your email...
Click to expand...
Click to collapse
Believe me. I did that. Aswell as a ton of other things but nothing seems to work...
---------- Post added at 11:49 AM ---------- Previous post was at 11:32 AM ----------
excitedgeek said:
Verify your email that u used to login your SYNC IT app...
Click to expand...
Click to collapse
It somehow looks like i can't connect to the lenovo servers. When i check for OTA updates, i get an error saying that i have no network available.
I tried rebooting, logging in and out, even did a factory reset but i'm still somehow unable to unlock my bootloader and now also check for otas..
Kaffer94 said:
Believe me. I did that. Aswell as a ton of other things but nothing seems to work...
---------- Post added at 11:49 AM ---------- Previous post was at 11:32 AM ----------
It somehow looks like i can't connect to the lenovo servers. When i check for OTA updates, i get an error saying that i have no network available.
I tried rebooting, logging in and out, even did a factory reset but i'm still somehow unable to unlock my bootloader and now also check for otas..
Click to expand...
Click to collapse
Then create a new Lenovo id...I hope it works.....I did the same thing & it worked
excitedgeek said:
Then create a new Lenovo id...I hope it works.....I did the same thing & it worked
Click to expand...
Click to collapse
Wow, i just did this and it worked. So strange that it works but it works.
Thank you for your help, i was at loss here!
Kaffer94 said:
Wow, i just did this and it worked. So strange that it works but it works.
Thank you for your help, i was at loss here!
Click to expand...
Click to collapse
Thank my post ..
I've done the same, logged out, factory reset and created a new Lenovo ID but it still isn't working for me
I've done the same, logged out, factory reset and created a new Lenovo ID but it still isn't working for me