Does anyone know what's wrong with my phone? The key attestation is deleted after i update my LG V50S to android 11 using lg up. I can't restore any backup from old phone and when i rollback to android 10 I did not having this problem.
me too my v50 has the same problem , so i rolled back to 20z version 10
your best shot is to backup your phone using a third party soft i suggest you DR FONE from wondershare then upgrade your phone normally then restore your phone data and forget about lg switch n so on
Related
Hi there,
I got a new LG G5 two days ago. I already unlocked the bootloader and rooted the device which worked great. I then restored my apps using Titanium Backup and removed some bloat apps, also using TB (stuff like LG Health and LG Backup). I restarted the phone today and suddenly when I tried to enter the PIN to boot it up again, it shows the "Enter PIN to unlock" screen but displays no keyboard. Anyone have any idea what I could do short of a factory reset?
TIA
SoWhy
SoWhy said:
Hi there,
I got a new LG G5 two days ago. I already unlocked the bootloader and rooted the device which worked great. I then restored my apps using Titanium Backup and removed some bloat apps, also using TB (stuff like LG Health and LG Backup). I restarted the phone today and suddenly when I tried to enter the PIN to boot it up again, it shows the "Enter PIN to unlock" screen but displays no keyboard. Anyone have any idea what I could do short of a factory reset?
TIA
SoWhy
Click to expand...
Click to collapse
Maybe you removed something related to the keyboard? In any case, if the problem is born after removing some apps the only solution is to flash the firmware through lgup, or flash a Custom rom through the twrp.
Sent from my LG G5 using XDA Labs
I tried to manually restore anything I removed using sideload flashing of TB generated files, but no avail. Luckily I had a TWRP backup made before changing anything and flashing system fixes it (while remembering all my settings which are apparently now stored in data)
Hi guys,
I have Tmobile LG V10 H90120j which its Wifi MAC address changes on every reboot.
Long story:
It was originally Lollipop, I updated to stock MM v20e then v20j. It was still OK after that.
Then I tried to root it using tungkick's method. However, the bad luck began, I forgot to change the Process to Upgrade instead of Refurbish when upgrading the TOT file. The phone bootloop to TWRP after that. Big thanks to @tungkick, he helped recover it.
I realized that from then the Wifi MAC address keeps changing on every reboot. The phone also cannot automatically get APNs from provider (I have to manually add them).
The really bad problem is the MAC issue. Only registered devices can connect to my home and my company Wifi networks. I can temporarily workaround by manually changing MAC address on rooted ROM after every reboot, but it's not an actual fix.
Factory Reset or Restoring to stock v20j can't help.
I did some search and found that some others also had the issue. Some said this method also can fix it: youtube . com /watch?v=8ejnFB5i5o8
But I can't see any nvram folder in my device.
Anyone has any ideas about fixing this, please help
Thanks.
anyone?
I have this with the T-mobile LG G5 H830 that is rooted on 20j (Nougat) with the dm-verity patch applied as well. I have 7 days left to return the phone). I also cannot find the nvram file/folder on my device (I am searching my LG G Pad 8.0 X to see where it is at via Root Explorer).
You mentioned you went back to stock (in TWRP, did you format the system and data directories and wipe the caches before; I ask because if you did not, I was going to do that, then re-stock).
My only other guess is the bootloader unlock would cause it (but then my LG G Pad 8.0 X is bootloader unlocked and doesn't do this). There was a CM7MAC.zip file (which I know is supposed to be for CM rom but I wonder if that fix would work for us).
uglyhoodlum said:
Hi guys,
I have Tmobile LG V10 H90120j which its Wifi MAC address changes on every reboot.
Long story:
It was originally Lollipop, I updated to stock MM v20e then v20j. It was still OK after that.
Then I tried to root it using tungkick's method. However, the bad luck began, I forgot to change the Process to Upgrade instead of Refurbish when upgrading the TOT file. The phone bootloop to TWRP after that. Big thanks to @tungkick, he helped recover it.
I realized that from then the Wifi MAC address keeps changing on every reboot. The phone also cannot automatically get APNs from provider (I have to manually add them).
The really bad problem is the MAC issue. Only registered devices can connect to my home and my company Wifi networks. I can temporarily workaround by manually changing MAC address on rooted ROM after every reboot, but it's not an actual fix.
Factory Reset or Restoring to stock v20j can't help.
I did some search and found that some others also had the issue. Some said this method also can fix it: youtube . com /watch?v=8ejnFB5i5o8
But I can't see any nvram folder in my device.
Anyone has any ideas about fixing this, please help
Thanks.
Click to expand...
Click to collapse
crazyut said:
I have this with the T-mobile LG G5 H830 that is rooted on 20j (Nougat) with the dm-verity patch applied as well. I have 7 days left to return the phone). I also cannot find the nvram file/folder on my device (I am searching my LG G Pad 8.0 X to see where it is at via Root Explorer).
You mentioned you went back to stock (in TWRP, did you format the system and data directories and wipe the caches before; I ask because if you did not, I was going to do that, then re-stock).
My only other guess is the bootloader unlock would cause it (but then my LG G Pad 8.0 X is bootloader unlocked and doesn't do this). There was a CM7MAC.zip file (which I know is supposed to be for CM rom but I wonder if that fix would work for us).
Click to expand...
Click to collapse
Been months, I cannot recovery my memory well. But I might not format the system and wipe the caches in TWRP before going back to stock. Still having the issue, and applying workaround after every reboot .
Bootloader unlock is unlikely the cause, cuz I rooted another H90120j (my cousin's) after that. I followed strictly the guide and made no mistake. The phone's still working well now.
Well I think you can give it a try. Looking forward to your good news
My 13th day is Saturday so I am going to get T-mobile to exchange it for a new one (since about 1/2 the posts on this topic says it's a hardware problem with certain chipset mac addresses and I hope that batch of phones that WA gets is different than the batch that HI gets) and reboot that several times before I leave.
I only found out I had this problem since Shaw Cable use MAC address for the 10 devices include in the Shaw Go wifi (wifi public hot spots) and when I put the original address in while still in HI, then got back to Calgary (after a couple of reboots had occurred during my trip) noticing Shaw would not auto-connect like it does on the other devices which are all rooted and sim unlocked (LG G Pad 8.0 X, Samsung Galaxy Note Edge, Moto X Play).
If not for Shaw, I would have been none the wiser until I got an employer that only used MAC address and by then, I'd be stuck with the phone.
I notice that this problem allegedly was based on a chipset and/or the Android software itself (there doesn't seem to be a consenus one direction or the other) when I googled this (and subsequently found your post on XDA). I have had several generations of Samsung Galaxy S and Note Series as well as Moto Triump (Sprint), the LG G Pad X, and Moto X Play and have never seen this phenomenon.
Since you say your cousins device is working well and you did the same thing with it as with yours, I suspect it's a hardware fault in our devices. I already returned a V20 to Freedom/WIND since that bootloader is locked and no root possible (will try to get T-mobile to give me the V20 instead of the G5 since I have to go through all this drama; the Freedom V20 was rebooted more than 7 times on purpose and no mac address change occurred).
uglyhoodlum said:
Been months, I cannot recovery my memory well. But I might not format the system and wipe the caches in TWRP before going back to stock. Still having the issue, and applying workaround after every reboot .
Bootloader unlock is unlikely the cause, cuz I rooted another H90120j (my cousin's) after that. I followed strictly the guide and made no mistake. The phone's still working well now.
Well I think you can give it a try. Looking forward to your good news
Click to expand...
Click to collapse
Hi there. I have H850 ver. 6.0.1
Ling ago i encrypted the phone and now every time i restart it i need to enter a pattern. And it annoys me!
How do i disable phone encription?
In the "fingerprints & security" options the encryption option is locked
I'm not familiar exactly with the G5 (I'm here to find info on it while I think about purchasing it), but I know that many versions of android don't allow you to decrypt your phone, you have to do a full factory reset. Just keep in mind that this might be the case with LG phones.
Hopefully someone can confirm for you
OtterNZ said:
I'm not familiar exactly with the G5 (I'm here to find info on it while I think about purchasing it), but I know that many versions of android don't allow you to decrypt your phone, you have to do a full factory reset. Just keep in mind that this might be the case with LG phones.
Hopefully someone can confirm for you
Click to expand...
Click to collapse
He's right encryption android can't be undone. Best few things you could do is. Log in. Backup pics to cloud. Contacts will be cloud back up to email account. Use LG backup great for apps. LG Backup may work idk? Factory reset.
I registered my account on this website just to share my awesome experience with Nokia 1.
I am very much thankful to XDA and many other sites whose text assisted me in recovering my mobile.
WARNING: VERY LARGE TEXT BELOW AND ITS JUST MY EXPERIENCE, I AM NOT RESPONSIBLE IF SOMEONE TRY TO GET ANY IDEAS FROM IT AND BRICK HIS PHONE
I purchased Nokia 1 (TA-1047). My only objective was to automatically record sound from 8AM to 2 PM. So I started root process (Devmode: OK, boot loader unlock: OK, TWRP flashing and running: OK)
BUT WHAT? TWRP is asking for a password... this was not provided in the guide. I tried blank password... not OK. Then I searched the Internet and learned that if I cancel on password screen and then Wipe data then it will be fine. I did that, then made full backup (ADB), and flashed Magisk (ADB)..OK. Restarted the phone and "bump": Phone told me it failed to decrypt and then it went into TWRP boot-loop.
Then I searched again and found TA-1060 recovery bin (from this site) and stock images. I flashed TA-1060 recovery (at that time I did not know that I could go to Boot-loader from TWRP and wasted like an hour to do it using buttons - Correct method is: power off the phone, connect the usb cable, press power and volume down till you see android logo). After flashing 1060 recovery I was able to reset phone and "voila" Magisk was also there.
Now I installed Schedule Voice Recorder, Team-Viewer Host (to transfer big files remotely), App locker (to lock settings and play store), Autostart and Stay (because recorder was getting closed), Dropbox and Dropsync --- and you can guess what would have happened. My mobile kept closing them randomly even if I made Recorder and AutoStart system app and whitelisted in developer setting and set to NOT optimized battery. So I tried to disable Nokia bloat-wares and damaged the system again. This happened for a few iterations before I realized that the Nokia 1 RAM is not sufficient to handle all these apps and I got an idea to upload earlier android version (Spoiler! Hard-brick is coming).
I searched on internet for similar mobile and found Huawei Y3 2017 with same chipset and configuration, Y5 with same chipset but higher configuration. Downloaded stock rom for both. First tried flashing boot and system from TWRP but failed saying that size was different? Downloaded SP flash tool, somehow passed through drivers issue (this would require another thread ). Tried flashing (with formatting) both Y3 2017 UO00 (which was different chipset but i altered scatter file) and Y5 but it failed on some check error. After that my phone was hard bricked!
Then I downloaded nokia 1 stock firmware but it was bad scatter file (only nvram and nvdata was showing), altered it, format+flash: failed again. Searched on internet and found that if I flash wrong preloader then I am done. I was not sure if I had already done it. I altered the scatter file again to include only preloader and thankfully it showed success but any other rom after it, it failed to flash. Found something like Nokia 3 DA and tried it but also failed.
FINALLY: I found nokia 1 nb0 rom and nb0 extractor, extracted rom using that, flash it and "voila" my phone was back alive. Tried to root but failed (because serial number was not same as before and new number did not work). Then I started iterations by mixing roms from my backup and using my "proinfo.bin" and stock rom my phone revived with my own serial number. BUT, then I flashed stock preloader and lk but everything else from Huawei, it failed with check error and then also refused to format for stock rom. Searched on internet about manual formatting, did that (WARNING: starting from address where preloader ends otherwise you would format your preloader as well) then it was back okay.
Rooted again, copied scheduler in sys-priv, whitelisted, not optimize battery. Also team viewer host (normal settings) and dropbox and sync (normal settings). As a work around I have now scheduled the app to record 24 hours instead of 8AM to 2PM so that it always remain as foreground app. 11 hour testing so far so good.
QUESTION: Can I not upload lesser android version (e.g. 4.4 or 5 or 6)? If I can then how.?
UPDATE: The Recorder is killed by OS again as well as team viewer host (even when recorder apk was in system/priv-app)
Is there any way to keep it always ON?
Or is there any way to installed some previous version of android?
goodboy84h said:
UPDATE: The Recorder is killed by OS again as well as team viewer host (even when recorder apk was in system/priv-app)
Is there any way to keep it always ON?
Or is there any way to installed some previous version of android?
Click to expand...
Click to collapse
Every Nokia 1 user is facing background app crash problem. Infact Nokia 5 users also. It simply crashes background apps like pressing force close and as of now there is no solution. we have to wait until nokia releases a fix.
By the way which build number are you using?
coolboyforeva said:
Every Nokia 1 user is facing background app crash problem. Infact Nokia 5 users also. It simply crashes background apps like pressing force close and as of now there is no solution. we have to wait until nokia releases a fix.
By the way which build number are you using?
Click to expand...
Click to collapse
TA-1047
coolboyforeva said:
Every Nokia 1 user is facing background app crash problem. Infact Nokia 5 users also. It simply crashes background apps like pressing force close and as of now there is no solution. we have to wait until nokia releases a fix.
By the way which build number are you using?
Click to expand...
Click to collapse
Maybe you have so many apps in the background, I had Instagram, YouTube and Facebook life in the background and I get rare force closes or I might be lucky I have a Nokia 1 TA-1060
mattwhite7102 said:
Maybe you have so many apps in the background, I had Instagram, YouTube and Facebook life in the background and I get rare force closes or I might be lucky I have a Nokia 1 TA-1060
Click to expand...
Click to collapse
No its an os bug from nokia side. It fails to work as it should after a particular update. Maybe u r not facing coz u have only 3 apps that too light ones from good app makers, google and fb. But if u add some more like any call recorder ( as mentioned by op)u would also face same problem i believe. It doesnt thows a FC but simple kills the app in background and u dont get notified.
UPDATE :- Here is the solution
https://forum.xda-developers.com/showpost.php?p=77685710&postcount=4
goodboy84h said:
UPDATE: The Recorder is killed by OS again as well as team viewer host (even when recorder apk was in system/priv-app)
Is there any way to keep it always ON?
Or is there any way to installed some previous version of android?
Click to expand...
Click to collapse
Try this to avoid app crash. it works.
https://forum.xda-developers.com/showpost.php?p=77685710&postcount=4
HELP!!! Mine is stuck at Nokia logo screen
goodboy84h said:
I registered my account on this website just to share my awesome experience with Nokia 1.
I am very much thankful to XDA and many other sites whose text assisted me in recovering my mobile.
WARNING: VERY LARGE TEXT BELOW AND ITS JUST MY EXPERIENCE, I AM NOT RESPONSIBLE IF SOMEONE TRY TO GET ANY IDEAS FROM IT AND BRICK HIS PHONE
I purchased Nokia 1 (TA-1047). My only objective was to automatically record sound from 8AM to 2 PM. So I started root process (Devmode: OK, boot loader unlock: OK, TWRP flashing and running: OK)
BUT WHAT? TWRP is asking for a password... this was not provided in the guide. I tried blank password... not OK. Then I searched the Internet and learned that if I cancel on password screen and then Wipe data then it will be fine. I did that, then made full backup (ADB), and flashed Magisk (ADB)..OK. Restarted the phone and "bump": Phone told me it failed to decrypt and then it went into TWRP boot-loop.
Then I searched again and found TA-1060 recovery bin (from this site) and stock images. I flashed TA-1060 recovery (at that time I did not know that I could go to Boot-loader from TWRP and wasted like an hour to do it using buttons - Correct method is: power off the phone, connect the usb cable, press power and volume down till you see android logo). After flashing 1060 recovery I was able to reset phone and "voila" Magisk was also there.
Now I installed Schedule Voice Recorder, Team-Viewer Host (to transfer big files remotely), App locker (to lock settings and play store), Autostart and Stay (because recorder was getting closed), Dropbox and Dropsync --- and you can guess what would have happened. My mobile kept closing them randomly even if I made Recorder and AutoStart system app and whitelisted in developer setting and set to NOT optimized battery. So I tried to disable Nokia bloat-wares and damaged the system again. This happened for a few iterations before I realized that the Nokia 1 RAM is not sufficient to handle all these apps and I got an idea to upload earlier android version (Spoiler! Hard-brick is coming).
I searched on internet for similar mobile and found Huawei Y3 2017 with same chipset and configuration, Y5 with same chipset but higher configuration. Downloaded stock rom for both. First tried flashing boot and system from TWRP but failed saying that size was different? Downloaded SP flash tool, somehow passed through drivers issue (this would require another thread ). Tried flashing (with formatting) both Y3 2017 UO00 (which was different chipset but i altered scatter file) and Y5 but it failed on some check error. After that my phone was hard bricked!
Then I downloaded nokia 1 stock firmware but it was bad scatter file (only nvram and nvdata was showing), altered it, format+flash: failed again. Searched on internet and found that if I flash wrong preloader then I am done. I was not sure if I had already done it. I altered the scatter file again to include only preloader and thankfully it showed success but any other rom after it, it failed to flash. Found something like Nokia 3 DA and tried it but also failed.
FINALLY: I found nokia 1 nb0 rom and nb0 extractor, extracted rom using that, flash it and "voila" my phone was back alive. Tried to root but failed (because serial number was not same as before and new number did not work). Then I started iterations by mixing roms from my backup and using my "proinfo.bin" and stock rom my phone revived with my own serial number. BUT, then I flashed stock preloader and lk but everything else from Huawei, it failed with check error and then also refused to format for stock rom. Searched on internet about manual formatting, did that (WARNING: starting from address where preloader ends otherwise you would format your preloader as well) then it was back okay.
Rooted again, copied scheduler in sys-priv, whitelisted, not optimize battery. Also team viewer host (normal settings) and dropbox and sync (normal settings). As a work around I have now scheduled the app to record 24 hours instead of 8AM to 2PM so that it always remain as foreground app. 11 hour testing so far so good.
QUESTION: Can I not upload lesser android version (e.g. 4.4 or 5 or 6)? If I can then how.?
Click to expand...
Click to collapse
HELP: mine, TA-1047 is stuck at Nokia logo screen.
Please share me a life saver as you mentioned "I found nokia 1 nb0 rom and nb0 extractor, extracted rom using that, flash it and "voila" my phone was back alive."
I tried many many solutions like SP Flash Tool, Miracle Box, fastboot, .... but still failed and stuck.
I'm suffering day by day trying with no hope and now see your post. Please support me!
Much appreciate!
HELP!!!
My Nokia 1 (TA-1047) was hard bricked and won't turn on. I tried to flash my phone by SP Flashtool but my PC didn't recognize my phone. :crying::crying:
Could you give me the drivers you use and steps to recover my phone. Please help me. Thank u.
Hi, I own a samsung galaxy A31F, I rooted it back in April of 2021 and decided to not update till android 12 comes out. I downloaded the firmware from samfrew and everything went perfectly until I opened the phone and found out that my IMEI is "unknown".
Both of them are, I have tried every method to restore them.
Including re flashing android again with root or without it. Nothing seems to work I tried apps.
I tried to use Xposed.
IMEI flashing software for PC.
Nothing seems to work and I would really appreciate it if someone decides to help.
Thanks.