Develop Bugs

[OTA] System fingerprint needed!

As it's Android One device, it probably uses Google OTA service. If you would be able to provide me with system fingerprint, there's a chance for me to get full OTA link to start up the development for this and possibly other devices.
How to do it?
Install Terminal Emulator from Google Play, type:
Code:
getprop | grep fingerprint
and click enter.
if you want to provide more of usable data, use just
Code:
getprop
Thread will be updated with links once somebody helps. Or will be closed in case of no solution.

pastebin.com/wWpYHPHd

WmcB said:
pastebin.com/wWpYHPHd
Click to expand...
Click to collapse
No update available yet, so I can't check currently if there will be full OTA zips. If you still have the access to this device, try getting kdz download link or file itself (via the official LG tool). Or post/*pm* the IMEI (it may be without last three numbers, because I don't need your own, but just any of them to simulate LG Bridge request). Basically, the only way to get fw now is to get the kdz. Aand last question: is G7 One bootloader unlockable? From what I saw in getprop, there was a prop suggesting that OEM unlock switch is blocked.

j1505243 said:
No update available yet, so I can't check currently if there will be full OTA zips. If you still have the access to this device, try getting kdz download link or file itself (via the official LG tool). Or post/*pm* the IMEI (it may be without last three numbers, because I don't need your own, but just any of them to simulate LG Bridge request). Basically, the only way to get fw now is to get the kdz. Aand last question: is G7 One bootloader unlockable? From what I saw in getprop, there was a prop suggesting that OEM unlock switch is blocked.
Click to expand...
Click to collapse
After enabling developer mode, I am given the option of unlocking the bootloader from the developer menu. I am able to enable it but I didn't test it.
The config [sys.oem_unlock_allowed]: [1] is now set
I tried using LG Mobile Support tool. Software is up to date, so I went into Upgrade Recovery menu option. It did a few checks and failed after "analyzing software version."
The error was "problem with communication between cell phone and PC." Maybe LG's support tool isnt updated to handle the phone yet.
I'll PM you an IMEI

WmcB said:
After enabling developer mode, I am given the option of unlocking the bootloader from the developer menu. I am able to enable it but I didn't test it.
The config [sys.oem_unlock_allowed]: [1] is now set
I tried using LG Mobile Support tool. Software is up to date, so I went into Upgrade Recovery menu option. It did a few checks and failed after "analyzing software version."
The error was "problem with communication between cell phone and PC." Maybe LG's support tool isnt updated to handle the phone yet.
I'll PM you an IMEI
Click to expand...
Click to collapse
Ok, managed to decrypt LGMST thingies. So, it seems that LG just didn't push any kdz yet. But the good news is that we should be able to fetch them as soon as they do it. In the free time, see if you can extract the Camera app from the device. Through Solid Explorer, for example.

j1505243 said:
Ok, managed to decrypt LGMST thingies. So, it seems that LG just didn't push any kdz yet. But the good news is that we should be able to fetch them as soon as they do it. In the free time, see if you can extract the Camera app from the device. Through Solid Explorer, for example.
Click to expand...
Click to collapse
Camera apk extracted
drive.google.com/drive/folders/1aRgQAUxq_aqtU7kOeXd3A1OD_dR6oUDo

WmcB said:
After enabling developer mode, I am given the option of unlocking the bootloader from the developer menu. I am able to enable it but I didn't test it.
The config [sys.oem_unlock_allowed]: [1] is now set
Click to expand...
Click to collapse
Did you end up unlocking the bootloader? I am considering getting this phone tomorrow but only if the bootloader can be unlocked.

jfd3220 said:
Did you end up unlocking the bootloader? I am considering getting this phone tomorrow but only if the bootloader can be unlocked.
Click to expand...
Click to collapse
I may not be savvy enough to test if it is unlocked. I ran "adb reboot bootloader" but it rebooted normally. Is there another way I can check?

WmcB said:
I may not be savvy enough to test if it is unlocked. I ran "adb reboot bootloader" but it rebooted normally. Is there another way I can check?
Click to expand...
Click to collapse
Maybe try
Code:
fastboot oem device-info

Bootloader unlocked from dev options.

I recall seeing other phones with that option that did not actually have unlockable bootloaders.

Pr0l1f1k said:
Bootloader unlocked from dev options.
Click to expand...
Click to collapse
Thanks but that's just a setting that you have to change to enable the unlocking. You also have to enable USB Debugging in Developer Options, then reboot into fastboot as instructed here.
Enable USB-Debugging on your phone. USB-Debugging is required for the commands “adb” and “fastboot” to work. To enable USB-Debugging, go to Settings > About phone > Software info and tap Build number 7 times. Return to the previous screen, select Developer options and enable USB-Debugging.
Enable OEM unlock on your phone. Activating the "Enable OEM unlock" is necessary for the bootloader unlock. To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock.
You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window. Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window.
Are you able to retrieve the Device ID?
EDIT: Never mind. I just got this from LG Support Chat: "As per our MC Specialists, unlocking the bootloader on G7 One is not possible anymore."

jfd3220 said:
EDIT: Never mind. I just got this from LG Support Chat: "As per our MC Specialists, unlocking the bootloader on G7 One is not possible anymore."
Click to expand...
Click to collapse
I can confirm that this phone will not enter fastboot with the "adb reboot bootloader" command. It just reboots to system like normal.

snardos said:
I can confirm that this phone will not enter fastboot with the "adb reboot bootloader" command. It just reboots to system like normal.
Click to expand...
Click to collapse
So is that it? Will we ever be able to unlock the bootloader.

j1505243 said:
As it's Android One device, it probably uses Google OTA service. If you would be able to provide me with system fingerprint, there's a chance for me to get full OTA link to start up the development for this and possibly other devices.
How to do it?
Install Terminal Emulator from Google Play, type:
Code:
getprop | grep fingerprint
and click enter.
if you want to provide more of usable data, use just
Code:
getprop
Thread will be updated with links once somebody helps. Or will be closed in case of no solution.
Click to expand...
Click to collapse
Hi ! I will receive my LG G7 One this week and I'm fully commited to help you get the files / test things on my device.
Please let me know, if can be any help !

Simshady97 said:
As it's Android One device, it probably uses Google OTA service. If you would be able to provide me with system fingerprint, there's a chance for me to get full OTA link to start up the development for this and possibly other devices.
How to do it?
Install Terminal Emulator from Google Play, type: and click enter.
if you want to provide more of usable data, use just
Hi ! I will receive my LG G7 One this week and I'm fully commited to help you get the files / test things on my device.
Please let me know, if can be any help !
Click to expand...
Click to collapse
Nah, we are seemingly clogged, until kdz start to distribute. For now, you may just capture the OTA link in adb.

Heads up for anyone interested in this phone: it is available on ebay. I've looked a few times over the last week, and there have been several of them up for grabs for a reasonable price. It's also available on Canadian Amazon (amazon.ca).
If anyone is wondering what frequency bands the phone will use, let me know and I can call around and ask some place that sells this phone.

Ok
Sent from my LGE LG-Q710AL using XDA Labs

fingerprint
O:/ $ getprop | grep fingerprint
[ro.boot.vendor.lge.fingerprint_sensor]: [1]
[ro.bootimage.build.fingerprint]: [lge/phoenix_lao_com/phoenix_sprout:9/PKQ1.180904.001/191471306ed81:user/release-keys]
[ro.build.fingerprint]: [lge/phoenix_lao_com/phoenix_sprout:9/PKQ1.180904.001/191471306ed81:user/release-keys]
[ro.vendor.build.fingerprint]: [lge/phoenix_lao_com/phoenix_sprout:9/PKQ1.180904.001/191471306ed81:user/release-keys]
:/ $

Can someone please share the stock camera APK of this phone?

Add L24 LTE bands to BND-L22 or BND-AL10?

Just got the phone bootloader unlocked (thanks to Wh1t3Rose for the guide) and now need to add the LTE bands from L24. Settings > About says the model is BND-AL10, however, HCU client says it's BND-L22 so a little confused. Can't find any fw in firmware finder for L22 so assuming AL10 is the right model.
Can I now safely use HuRUpdater to flash BND-L24C567CUSTC567D1B344 (8.0.0.344) FullOTA-MF on this device? Or I am missing some steps like rooting / installing TWRP etc.?
Another question - what TWRP to use with HuRUpdater? Would the first one from here work for 7x?
Thanks for any comments!

rexian said:
Just got the phone bootloader unlocked (thanks to Wh1t3Rose for the guide) and now need to add the LTE bands from L24. Settings > About says the model is BND-AL10, however, HCU client says it's BND-L22 so a little confused. Can't find any fw in firmware finder for L22 so assuming AL10 is the right model.
Can I now safely use HuRUpdater to flash BND-L24C567CUSTC567D1B344 (8.0.0.344) FullOTA-MF on this device? Or I am missing some steps like rooting / installing TWRP etc.?
Another question - what TWRP to use with HuRUpdater? Would the first one from here work for 7x?
Thanks for any comments!
Click to expand...
Click to collapse
If you need to change model bands , it takes more than that.
If you do like that , the model number doesn't change and modem bands also stay the same. You will need to do what is referred to as "re-brand" which changes the oeminfo file , then flash the l24 full ota.
Changing the oeminfo. Makes bootloader lock again. But the same key is supposed to still work.
It can be easy to make brick during re-brand
. You should Study the bnd-hwota-eng script to understand the process.

mrmazak said:
If you need to change model bands , it takes more than that.
If you do like that , the model number doesn't change and modem bands also stay the same. You will need to do what is referred to as "re-brand" which changes the oeminfo file , then flash the l24 full ota.
Changing the oeminfo. Makes bootloader lock again. But the same key is supposed to still work.
It can be easy to make brick during re-brand
. You should Study the bnd-hwota-eng script to understand the process.
Click to expand...
Click to collapse
Thanks mrmazak. Is this a viable option of getting L24 bands on AL10?

Found the L24 oeminfo here. Is there a way I can backup the oeminfo from my AL10 just in case I brick it
Maybe installing TWRP and taking a full backup is a better idea but can't find a TWRP img for AL10 Naugat :|

rexian said:
Found the L24 oeminfo here. Is there a way I can backup the oeminfo from my AL10 just in case I brick it
Maybe installing TWRP and taking a full backup is a better idea but can't find a TWRP img for AL10 Naugat :|
Click to expand...
Click to collapse
I will look at it tonight when I get home.
I had found good hwota tool with the re-brand script in it. I had to translate from russain and add L24 oeminfo but ithas been used successfully.
I will look at that linked oeminfo and compare to the one I put in the hwota tool.
A search on the 7x main page for "bnd hwota- eng" or similar should show the tool like.
If you don't find Ivan upload again.

mrmazak said:
I will look at it tonight when I get home.
I had found good hwota tool with the re-brand script in it. I had to translate from russain and add L24 oeminfo but ithas been used successfully.
I will look at that linked oeminfo and compare to the one I put in the hwota tool.
A search on the 7x main page for "bnd hwota- eng" or similar should show the tool like.
If you don't find Ivan upload again.
Click to expand...
Click to collapse
Thanks again, mrmazak. I saw your post in the other thread while searching but wasn't sure if there is more up to date information or an alternate tool.
Is it possible to just add certain bands to a model without removing existing bands? The only bands of interest are LTE 12 and 17 that are missing in this. The person doesn't really care about Oreo or Nougat - as long as it works with AT&T

Thanks mrmazak for updating HWTOA. I'll try rebranding AL10 to L24 tomorrow. Don't see a way to just add new bands so rebranding L24 seems to be the only way for now.
BTW, I took a backup of Boot, OEMInfo, System and modem_fw partitions. For some reason backup of Data partition failed after multiple attempts (unable to find partition for path /system and createTarProcess() ended with error 255). Is Data partition important in this case? The phone has no real data or app installed anyway as it's not in use.
Another question - planning to use HWOTA7 since I have Nougat right now but downloaded BND-L24C567CUSTC567D1B344 (8.0.0.344) full OTA - is this ok? I can't find a Nougat version for L24C567.

I flashed from L21C10 to TL10,before that I saved 8 modem files with L21 to him and the emui tweaker from the phone,then I restored it,and I had 4G+,try so.

rexian said:
Thanks mrmazak for updating HWTOA. I'll try rebranding AL10 to L24 tomorrow. Don't see a way to just add new bands so rebranding L24 seems to be the only way for now.
BTW, I took a backup of Boot, OEMInfo, System and modem_fw partitions. For some reason backup of Data partition failed after multiple attempts (unable to find partition for path /system and createTarProcess() ended with error 255). Is Data partition important in this case? The phone has no real data or app installed anyway as it's not in use.
Another question - planning to use HWOTA7 since I have Nougat right now but downloaded BND-L24C567CUSTC567D1B344 (8.0.0.344) full OTA - is this ok? I can't find a Nougat version for L24C567.
Click to expand...
Click to collapse
There is a nougat full it's. It is labeled for Oreo roll-back. But should work for you . It is found as 'bond' intead of 'bnd'. ( Wait, the rebrand script is looking for three files. I will try and adjust the script to not fault out with just two.)
And link is actually in the hwota thread as a downgrade package.
I do reupload most current hwota file yesterday. I found a bug when I did a downgrade. So I proof read through the files again and re-uploaded.
Also added link to bnd-hwota-eng to the guide thread.

Klirensxp said:
I flashed from L21C10 to TL10,before that I saved 8 modem files with L21 to him and the emui tweaker from the phone,then I restored it,and I had 4G+,try so.
Click to expand...
Click to collapse
Did you do this to rebrand the phone to support other LTE bands? Or just to get OTA updates keeping the same radios? Sounds like latter.
I am trying to get the US radio bands on my AL10 by rebranding it to L24.

mrmazak said:
There is a nougat full it's. It is labeled for Oreo roll-back. But should work for you . It is found as 'bond' intead of 'bnd'. ( Wait, the rebrand script is looking for three files. I will try and adjust the script to not fault out with just two.)
And link is actually in the hwota thread as a downgrade package.
I do reupload most current hwota file yesterday. I found a bug when I did a downgrade. So I proof read through the files again and re-uploaded.
Also added link to bnd-hwota-eng to the guide thread.
Click to expand...
Click to collapse
Ok, will wait for the updated script. I downloaded rest of the files.
In the oeminfo folder I see AL10C00 img but not AL10C675. Trying to root the phone to be able to copy custom.bin/oeminfo so that I can go back to stock later. For some reason SuperSU doesn't work... will try Magisk now

rexian said:
Ok, will wait for the updated script. I downloaded rest of the files.
In the oeminfo folder I see AL10C00 img but not AL10C675. Trying to root the phone to be able to copy custom.bin/oeminfo so that I can go back to stock later. For some reason SuperSU doesn't work... will try Magisk now
Click to expand...
Click to collapse
I have been looking at some ways to edit the script to make it automatically adjust if there is only 2 update files. And it will be easier to just manually edit the one script before you run it.
Add a "#" to the front of line 332 of hwota.sh.
"HWOTA_BND\HWOTA7_BND-eng\hwota.sh"
Need to just comment out the line with "$TARGET_UPDATE_DATA"
Code:
echo
echo "Copying recovery files, please be patient and wait...."
$ADB push $RECOVERY $RECOVERY_TMP
$ADB push $RECOVERY2 $RECOVERY2_TMP
$ADB shell "dd if=$RECOVERY_TMP of=/dev/block/bootdevice/by-name/recovery bs=1048576"
$ADB shell "dd if=$RECOVERY2_TMP of=/dev/block/bootdevice/by-name/recovery2 bs=1048576"
$ADB shell "echo --update_package=$TARGET_UPDATE > /cache/recovery/command"
#$ADB shell "echo --update_package=$TARGET_UPDATE_DATA >> /cache/recovery/command"
$ADB shell "echo --update_package=$TARGET_UPDATE_HW >> /cache/recovery/command"
$ADB reboot recovery
$ADB kill-server

mrmazak said:
I have been looking at some ways to edit the script to make it automatically adjust if there is only 2 update files. And it will be easier to just manually edit the one script before you run it.
Add a "#" to the front of line 332 of hwota.sh.
"HWOTA_BND\HWOTA7_BND-eng\hwota.sh"
Need to just comment out the line with "$TARGET_UPDATE_DATA"
Code:
echo
echo "Copying recovery files, please be patient and wait...."
$ADB push $RECOVERY $RECOVERY_TMP
$ADB push $RECOVERY2 $RECOVERY2_TMP
$ADB shell "dd if=$RECOVERY_TMP of=/dev/block/bootdevice/by-name/recovery bs=1048576"
$ADB shell "dd if=$RECOVERY2_TMP of=/dev/block/bootdevice/by-name/recovery2 bs=1048576"
$ADB shell "echo --update_package=$TARGET_UPDATE > /cache/recovery/command"
#$ADB shell "echo --update_package=$TARGET_UPDATE_DATA >> /cache/recovery/command"
$ADB shell "echo --update_package=$TARGET_UPDATE_HW >> /cache/recovery/command"
$ADB reboot recovery
$ADB kill-server
Click to expand...
Click to collapse
Cool, done commenting #332. Also was able to root and make a copy of custom.bin / oeminfo.
Now, going to run the script :fingers-crossed:

Alright, an update - it went through lot of steps as expected (including installing oeminfo and unlocking the bootloader) but ended up with "software update failed" error on the phone. On command prompt here is the last few lines of the log -
Use the volume buttons to select YES and press the power button
...
(bootloader) The device will reboot and do factory reset...
OKAY [ 11.001s]
finished. total time: 11.001s
Wait for the device to boot into TWRP.
Press Enter to continue...
Wait for the files to load. Neither of which you do not need to press !!!.
Copying is in progress ....
[100%] /data/update/HWOTA/update.zip
Copying is in progress ....
adb: error: cannot stat 'D:/UX/HCU-Client/HWOTA7_BND-eng//update/update_data_public.zip': No such file or directory
Copying is in progress ....
adb: error: cannot stat 'D:/UX/HCU-Client/HWOTA7_BND-eng//update/update_all_hw.zip': No such file or directory
Copying recovery files, please be patient and wait....
[100%] /tmp/BND_RECOVERY_NoCheck.img
[100%] /tmp/BND_RECOVERY2_NoCheck.img
35+1 records in
35+1 records out
37109760 bytes (35.4MB) copied, 0.414091 seconds, 85.5MB/s
35+1 records in
35+1 records out
37109760 bytes (35.4MB) copied, 0.508804 seconds, 69.6MB/s
The system update should start automatically.
Press Enter to continue...
Click to expand...
Click to collapse
Error for update_data_public.zip was expected and on close inspection I noticed there was an extra '.' in the name of update_all_hw.zip. It was update_all_hw..zip.
So, fixed it and put the phone in fastboot mode and re-ran update.bat. It installed recovery and asked me to put into TWRP. I tried but it never went to TWRP started installing the previously copied ZIP files. It took a while but after it restarted, it went to straight to Android (YAY!). Went to Settings > About and say the model as BND-L24 and build number System 5.1.0.98(07DV).
So far it seemed everything was fine - then I inserted the FreedomPop SIM (uses AT&T towers), added the fp.com.attz APN and restarted it - AND the same issue, can't see the carriers and 0 bars
The oeminfo was definitely installed as I see a lot more options in "preferred network mode" but selecting Global or LTE or anything else does nothing...
Since I am not able to boot into TWRP, I wonder if that's causing an issue. Every attempt to boot into TWRP goes into a screen showing "installing update" with 5% status. It eventually (after 10 minutes or so) boots into Nougat.

Gave up and started from scratch (after installing TWRP img mount manually) and it completed successfully (with expected error for the missing update_data_public.zip). Build number changed to BND-L24C567B150 so both zips were installed yet the problem remains the same - no cellular connectivity and settings > More > Mobile Network > Carrier remains disabled...

rexian said:
Did you do this to rebrand the phone to support other LTE bands? Or just to get OTA updates keeping the same radios? Sounds like latter.
I am trying to get the US radio bands on my AL10 by rebranding it to L24.
Click to expand...
Click to collapse
It’s just that the L21 is always 4G,and on the TL10 it goes to 3G,I switched from L21 to TL10 because of gestures, now I have 4G+ as well as on L21.

rexian said:
Gave up and started from scratch (after installing TWRP img mount manually) and it completed successfully (with expected error for the missing update_data_public.zip). Build number changed to BND-L24C567B150 so both zips were installed yet the problem remains the same - no cellular connectivity and settings > More > Mobile Network > Carrier remains disabled...
Click to expand...
Click to collapse
Good catch with the renamed file. You did right thing to start over, because that first build number was not correct.
As far as I know this should have changed the radio files (modem).
I will keep looking for other confirmed way to change the selected bands.

mrmazak said:
Good catch with the renamed file. You did right thing to start over, because that first build number was not correct.
As far as I know this should have changed the radio files (modem).
I will keep looking for other confirmed way to change the selected bands.
Click to expand...
Click to collapse
Thanks mrmazak. What could be the reason behind disabled option? Earlier with AL10, I could go inside and see AT&T listed but selecting that would not help as corresponding radios were not enabled in AL10.
Now, even if L24 radios are not properly installed / enabled, I should be able to go inside and see AT&T listed - makes me wonder if all the radios are now disabled.
Is there another way to check what radios are available in a phone by running some app?

rexian said:
Thanks mrmazak. What could be the reason behind disabled option? Earlier with AL10, I could go inside and see AT&T listed but selecting that would not help as corresponding radios were not enabled in AL10.
Now, even if L24 radios are not properly installed / enabled, I should be able to go inside and see AT&T listed - makes me wonder if all the radios are now disabled.
Is there another way to check what radios are available in a phone by running some app?
Click to expand...
Click to collapse
Not sure about other ways to check the bands. There are playstore apps that will show what band you are connected to, but have not seen one that shows which ones you can connect to.
side note::: Funkyhuawei (paid service) says of there rebrand guide, that you must flash the new firmware at least 2 times. So maybe take the flash one more time.
some general questions about your problem.
On about phone screen, what is shown for 'baseband' ?
does the imei # number show?
are you installing sim into slot #1 ? (#2 does not support 4g)
did you verify freedom pop sim is activated? (tested in other device)
edit:
found few posts in some "rebranding" threads, that say what you want to do might not be possible.
They say on the software side it will have drivers for the correct bands. But he hardware may not suppport it.
here:
https://forum.xda-developers.com/showpost.php?p=76462513&postcount=175

mrmazak said:
Not sure about other ways to check the bands. There are playstore apps that will show what band you are connected to, but have not seen one that shows which ones you can connect to.
side note::: Funkyhuawei (paid service) says of there rebrand guide, that you must flash the new firmware at least 2 times. So maybe take the flash one more time.
Click to expand...
Click to collapse
I tried once more tonight but the same result - no service and carrier disabled.
mrmazak said:
some general questions about your problem.
On about phone screen, what is shown for 'baseband' ?
does the imei # number show?
are you installing sim into slot #1 ? (#2 does not support 4g)
did you verify freedom pop sim is activated? (tested in other device)
Click to expand...
Click to collapse
There are 2 long numbers for the baseband - both start with 21C60B. Yes, both IMEIs show and are the same as before.
Yes, I always used the dedicated SIM slot as I have a micro-SD inserted for backup.
mrmazak said:
edit:
found few posts in some "rebranding" threads, that say what you want to do might not be possible.
They say on the software side it will have drivers for the correct bands. But he hardware may not suppport it.
here:
https://forum.xda-developers.com/showpost.php?p=76462513&postcount=175
Click to expand...
Click to collapse
I am inclining towards this as well - possibly missing hardware
Now, how do I get back to AL10C675 (don't see a Nougat option in FW Finder) and original radio? HWOTA doesn't have C675 as option, it has C00. I do have the original custom.bin and oeminfo but how do I create a zip to install with TWRP?

My complete bootloader unlock and root guide.

So I just got this phone just for fun, it was 75 USD, and went straight to XDA to root it so i can remove some bloat etc. but holy moly i ended up have 10 tabs with different guides open, i have compiled what I did to get this phone rooted.
I want to thank everyone who made different threads about rooting and installing Magisk on this phone, i have read so many guides now so i cant remember their names!.
BUT THANK YOU!.
Let's get to it
Here is what I did for to unlock the bootloader, install magisk and root my Huawei P20 Lite ANE-LX1
First you need to install HiSuite: https://consumer.huawei.com/minisite/HiSuite_en/
and then install ADB and Fastboot drivers: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
(extract the platform-tools folder to the root of your C: drive)
Plug in your phone and let it install drivers.
Then you need to downgrade your firmware to 146 using Dload method, as DCU Client can't read the bootloader unlock code on newer firmwares.
I used "Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.146(C432) Firmware Android 8.0.0 EMUI 8.0.0 05014YXX androidhost.ru.zip" (https://androidhost.ru/6ti)
When finished downloading, open the zip file, open software and copy the folder "Dload" to the root of your EXTERNAL SD CARD, not internal storage!.
Now take your phone and "dial" *#*#2846579#*#* go to Software Upgrade -> SdCard Upgrade and click OK.
Your phone should now begin installing the old firmware, when the phone first boots up, dont set it up, turn it off and hold Volume up + Power and select Wipe Data/Factory Reset, Wipe Cache, and then reboot.
With the phone booted, enable USB Debugging (Settings > System > About Phone > version number > Tap it 7 times to become developer, AND click OEM-Unlock, then go to Settings > System > Developer Options > USB Debugging).
Now we need to buy 4 credits from DC-Unlocker (4 Euro) ( https://www.dc-unlocker.com/buy ) when you have 4 credits on your account, go and download https://hcu-client.com/download/hcu-client-v1-0-0-0287/ Password: hcu
extract the contents of the zip to a folder called HCU in the root of your C: drive
Open up HCU.exe, type in your username and password (check your mail, the info will be there).
Grab your phone and dial *#*#2846579#*#*, go to Background Settings -> USB Port Settings -> Manufacture Mode and press close.
Plug in your phone and let it install drivers.
Open up HCU client, select Unlock, and then Read Bootloader Code.
when you have the code, save it!
Turn off your phone
Hold volume down and power, now we are in fastboot mode.
Open CMD and write:
CD C:\platform-tools
fastboot oem unlock YOUR UNLOCK KEY HERE
Accept the stuff and unlock your bootloader, your phone will be factory reset, and all your data lost if you dont have a backup.
Turn the phone off and on again, set it up, and go to settings -> System -> System update, and update, mine was ANE-LX1 8.0.0.162(C432)
Now re-enable USB Debugging option in Developer Options.
install Magisk Manager (https://github.com/topjohnwu/Magisk/releases/download/v18.0/Magisk-v18.0.zip)
Download patched_ramdisk.img (https://mega.nz/#!GWp1ia6R!xUcg_T_17v1ktlFQPq-Ujo4DRKfAg8E4-_k2J2zLO60)
and place it in the root of your phones internal storage
Open up Magisk Manager, press install -> install -> Patch Boot Image File -> find the patched_ramdisk.img and click OK.
Now open CMD and write:
CD C:\platform-tools>
adb pull /storage/emulated/0/download/patched_boot.img
Now you should have the patched_boot.img in your platform tools folder.
Turn off your phone, hold volume down and power to get to fastboot mode.
in CMD write:
CD C:\platform-tools>
fastboot flash ramdisk patched_boot.img
reboot your phone and check if magisk was installed correctly and check if you have root.
Hope this works for you!

Great guide. Just a tip instead of using cd C:\platform-tools you can shift+right click on the adb folder and click "open powershell here". Saves some time

Thank you for this, but I have a question about this part:
Then you need to downgrade your firmware to 146 using Dload method, as DCU Client can't read the bootloader unlock code on newer firmwares.
Click to expand...
Click to collapse
Mine is ANE-LX3, what would be the equivalent to 146 so that DC-unlocker can read it?

Yes, you just need to find a firmware for LX3, i dont think flashing a 64gb firmware on a 32gb device is smart.

dcduartee said:
Great guide. Just a tip instead of using cd C:\platform-tools you can shift+right click on the adb folder and click "open powershell here". Saves some time
Click to expand...
Click to collapse
I have tried that and PowerShell doesnt Work on my pc(i have replaced shift click shortcut so its CMD indtraf) and i wanted a noob proof way to make this work
And thanks.

Where could i find the correct firmware of ANE-LX1

Just use the address bar
brugernavn said:
I have tried that and PowerShell doesnt Work on my pc(i have replaced shift click shortcut so its CMD indtraf) and i wanted a noob proof way to make this work
And thanks.
Click to expand...
Click to collapse
Maybe you already know but I learned that you can just clic the address bar in a Windo(w)s system and write 'cmd' which is exactly the same as 'open a command prompt that starts in this very specific folder'.
E.g. in attachments.
Now I just want to know what firmware to downgrade to :/

LLoTE said:
Where could i find the correct firmware of ANE-LX1
Click to expand...
Click to collapse
Use the link in my guide.
lalovzg said:
Maybe you already know but I learned that you can just clic the address bar in a Windo(w)s system and write 'cmd' which is exactly the same as 'open a command prompt that starts in this very specific folder'.
E.g. in attachments.
Now I just want to know what firmware to downgrade to :/
Click to expand...
Click to collapse
Sweet thanks!.
Try and use this firmware:.
https://androidhost.ru/9V2

Using that as a reference I found one for my region I think (C69) that says:
Integrates Google security patches released in Apr 2018 for improved system security.
Click to expand...
Click to collapse
Is this April FullOTA a safe security patch to work with DC-u?
ANE-LX3C69CUSTC69
An another one big question: I am in the believe that my P20 lite is Single-SIM. Does it matter if that FullOTA (or any ROM/Update.app/etc) says DUAL-SIM? Should I look for the oldest Single-SIM??? or a Dual-SIM file would work just fine?

lalovzg said:
Using that as a reference I found one for my region I think (C69) that says:
Is this April FullOTA a safe security patch to work with DC-u?
ANE-LX3C69CUSTC69
An another one big question: I am in the believe that my P20 lite is Single-SIM. Does it matter if that FullOTA (or any ROM/Update.app/etc) says DUAL-SIM? Should I look for the oldest Single-SIM??? or a Dual-SIM file would work just fine?
Click to expand...
Click to collapse
If its single sim, you need a single sim firmware and just use a firmware under 150, you should be okay

Would someone like to pay for me cuz I don't got a way to pay i don't have any credit cards..i know this is stupid but im just a teenager and my parents wouldn't pay for it so here i am lol

@brugernavn
Bro your instructions are super perfect tuttorial very very BIG thankx
would know exactly the firmware that would go without a bootloader unlock hunger everywhere this Huawei P20 Lite firmware ANE-L21 Anne-L21 8.0.0.166 (C432)
The only thing is that which one is right where the to sdcard firmware into the dload folder and installs without problems
because of what I was looking for and so I made a mistake to link to the Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.166 (C432) in format like This post forum
what i found for dual sim so all su with unlocked bootloader hurts me
PLEASE REPLY will be glad

HEKER510 said:
@brugernavn
Bro your instructions are super perfect tuttorial very very BIG thankx
would know exactly the firmware that would go without a bootloader unlock hunger everywhere this Huawei P20 Lite firmware ANE-L21 Anne-L21 8.0.0.166 (C432)
The only thing is that which one is right where the dam to sdcard firmware into the dload folder and installs without problems
because of what I was looking for and so I made a mistake to link to the Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.166 (C432) in format like aky maš na forum
what i found for dual sim so all su with unlocked bootloader hurts me
PLEASE REPLY will be glad
Click to expand...
Click to collapse
Im sorry, i dont understand what you are writing

brugernavn said:
Im sorry, i dont understand what you are writing
Click to expand...
Click to collapse
i flashnig for sdcard firmware 146 for you link
i have must firmware 166 for sdcard
you helping my for firmware 166 for huawei p20 lite dual firmware 166(c432) flashing install sdcard for servis menu upgrade
identic 146 for 166 firmware
you understand my brother ?

HEKER510 said:
i flashnig for sdcard firmware 146 for you link
i have must firmware 166 for sdcard
you helping my for firmware 166 for huawei p20 lite dual firmware 166(c432) flashing install sdcard for servis menu upgrade
identic 146 for 166 firmware
you understand my brother ?
Click to expand...
Click to collapse
You first flash 146 firmware with Service menu.
Then unlock bootloader
Then update via the settings menu

brugernavn said:
You first flash 146 firmware with Service menu.
Then unlock bootloader
Then update via the settings menu
Click to expand...
Click to collapse
Bro 166 firmware for servis menu yes ? thankx you very much

thank you very much for your guide, brugernavn.:good:
I arrived without problems at the point: "Turn the phone off and on again, set it up, and go to settings -> System -> System update, and update, mine was ANE-LX1 8.0.0.162(C432)"
but the phone can not find updates ... (i before was in 150) but this isn't a problem.
My doubt is on how to install Magisk Manager (https://github.com/topjohnwu/Magisk/...gisk-v18.0.zip) .... with TWRP ?
Thank you again

Hey, to root my p20, flashing magisk via recovery, don't need ramimage, all works fine

how to do it
how to flashing magisk via recovery? (whit TWRP or not??) you can explain the passage?

cirovi said:
thank you very much for your guide, brugernavn.:good:
I arrived without problems at the point: "Turn the phone off and on again, set it up, and go to settings -> System -> System update, and update, mine was ANE-LX1 8.0.0.162(C432)"
but the phone can not find updates ... (i before was in 150) but this isn't a problem.
My doubt is on how to install Magisk Manager (https://github.com/topjohnwu/Magisk/...gisk-v18.0.zip) .... with TWRP ?
Thank you again
Click to expand...
Click to collapse
what software are you running now?

How to Install Leaked Android 10 Beta OTA on Sprint LG V50

Orginal Title: Sprint LG V50 may get Android 10 beta by End of 2019 (V450PM)
I saw this article here: https://www.mylgphones.com/sprint-lg-v50-thinq-5g-android-10-update-will-release-soon.html?amp
Leaked Frimware details:
Model:LM-V450PM
Size:1508.11MB
Android Pie 9.0: LMV450PMAT-V10p-310-120-SEP-19-2019-ARB00+0
Android 10 Beta: LMV450PMAT-V18a-310-120-OCT-29-2019-ARB00+1
File name: LMV450PM-V10p-310-to-LMV450PM-V18a-310.up
Click to expand...
Click to collapse
The article source won't release the beta frimware though. Anybody know where/how to get this or convince them to share it? However though, this is great news!
Edit: Special Thanks to chortya for purchasing the file. The link to download the file comes from the domain dl01.gdms.lge.com which is a legit source from LG directly. The file received is a .mo file, you just rename it to get a .up file. chortya has graciously shared the OTA file in the mega.nz link below!
chortya said:
https://mega.nz/#!gjJi3KiK!ebsQdxmnXtEYRiG69F5oAlVqNnsZ3c9D7SpWahGI8OQ
even patch name stipulates specific old firmmware version. And yes, I am on v10p.
Click to expand...
Click to collapse
Now lets figure out how to flash it!
Edit 2: Wow, that was fast! Thanks to aiap for figuring out how to flash this OTA.
aiap said:
SUCCESS!
I ended up not using LGUP, instead this is how I did it. (Make sure to backup, for some reason I had to factory reset because mine was stuck rebooting after "android is installing" notification completed.)
STEPS:
1. Download .up file: https://mega.nz/#!gjJi3KiK!ebsQdxmnXtEYRiG69F5oAlVqNnsZ3c9D7SpWahGI8OQ (thanks @chortya)
2. Rename file to LGUP_FOTA.up
3. Place file in root of internal storage on V50.
4. Download "Activity Launcher" from Play Store
5. Find FOTA Update
6. Hit the first option (com.lge.lgfota.permission.FotaTestActivity)
7. Follow prompts.
Click to expand...
Click to collapse
Edit 3: Some screenshots thanks to @aiap
https://forum.xda-developers.com/v5...-beta-2019-t3995429/post80870307#post80870307

I may have found the firmware on a LG firmware site called LGBBS. If someone knows how to purchase from Alipay and risk 50 yuan ($7.10 USD) and would be willing to share the file on Google Drive or so: http://www.lgbbs.com/plugin.php?id=lg_ota&lg_ota=fwbuy&fwid=LCmN1NXswX8eTAJVn1Dhsg==

andrewwm said:
I may have found the firmware on a LG firmware site called LGBBS. If someone knows how to purchase from Alipay and risk 50 yuan ($7.10 USD) and would be willing to share the file on Google Drive or so: http://www.lgbbs.com/plugin.php?id=lg_ota&lg_ota=fwbuy&fwid=LCmN1NXswX8eTAJVn1Dhsg==
Click to expand...
Click to collapse
Maybe you could ask @ngocgiap32 to help you and donate to him... he gave us for free the other 3 korean otas:good::highfive:

Inerent said:
Maybe you could ask @ngocgiap32 to help you and donate to him... he gave us for free the other 3 korean otas:good::highfive:
Click to expand...
Click to collapse
I'd donate. I tried creating an Alipay account but when I went to pay, it wanted a Chinese bank card.

any news?

Hell, I got $7!

hooutoo said:
Hell, I got $7!
Click to expand...
Click to collapse
did u got the rom?

No I'm just saying I would happily contribute the $7

I am not able to install it. Tried multiple options:
- LGUP FOTA upgrade - device protected error
- recovery mode - both SD card recovery and adb are not working. SD card mounting fails and it seems that my V50 is not connecting to PC if in recovery mode so adb does not see it. adb works fine with phone fully booted, so developer options are enabled and phone is authenticated with pc
- lgup_cmd does not even recognize *.up files
Any thoughts?
Does it make sense to move this to the kernel/firmware section?

chortya said:
I am not able to install it. Tried multiple options:
- LGUP FOTA upgrade - device protected error
- recovery mode - both SD card recovery and adb are not working. SD card mounting fails and it seems that my V50 is not connecting to PC if in recovery mode so adb does not see it. adb works fine with phone fully booted, so developer options are enabled and phone is authenticated with pc
- lgup_cmd does not even recognize *.up files
Any thoughts?
Does it make sense to move this to the kernel/firmware section?
Click to expand...
Click to collapse
how did u got the rom?

Paid 50 RMB.

chortya said:
Paid 50 RMB.
Click to expand...
Click to collapse
and they did not explain how to install?

chortya said:
I am not able to install it. Tried multiple options:
- LGUP FOTA upgrade - device protected error
- recovery mode - both SD card recovery and adb are not working. SD card mounting fails and it seems that my V50 is not connecting to PC if in recovery mode so adb does not see it. adb works fine with phone fully booted, so developer options are enabled and phone is authenticated with pc
- lgup_cmd does not even recognize *.up files
Any thoughts?
Does it make sense to move this to the kernel/firmware section?
Click to expand...
Click to collapse
Yes. You must flash it with LG-UP 1.16.0.3.
Install lg USB drivers 4.4.2
Install lgup 1.16.0.3
Install lg common dll 1.40
Download and Copy the ui config file (from the LG-UP thread here on the forum) and paste it where the common dll is.
Then enable USB debugging in dev options
Then connect to pc
Then start lg up
Then chose FOTA upgrade
Then load your android 10 beta fota file. Make sure it has. Up extension
Then click start on lgup. Wait for the minute and it should start flashing.

chortya said:
Paid 50 RMB.
Click to expand...
Click to collapse
Can you share it over Google drive? Also did they have firmware for g8?

Inerent said:
Yes. You must flash it with LG-UP 1.16.0.3.
Install lg USB drivers 4.4.2
Install lgup 1.16.0.3
Install lg common dll 1.40
Download and Copy the ui config file (from the LG-UP thread here on the forum) and paste it where the common dll is.
Then enable USB debugging in dev options
Then connect to pc
Then start lg up
Then chose FOTA upgrade
Then load your android 10 beta fota file. Make sure it has. Up extension
Then click start on lgup. Wait for the minute and it should start flashing.
Click to expand...
Click to collapse
did you test it?

Inerent said:
Yes. You must flash it with LG-UP 1.16.0.3.
Install lg USB drivers 4.4.2
Install lgup 1.16.0.3
Install lg common dll 1.40
Download and Copy the ui config file (from the LG-UP thread here on the forum) and paste it where the common dll is.
Then enable USB debugging in dev options
Then connect to pc
Then start lg up
Then chose FOTA upgrade
Then load your android 10 beta fota file. Make sure it has. Up extension
Then click start on lgup. Wait for the minute and it should start flashing.
Click to expand...
Click to collapse
My setup is exactly as you described. I need to check the version if the USB driver, but don't think this will improve anything.
As I have written I am getting "protected device" error.
My V50 is locked, does it have any influence?

chortya said:
My setup is exactly as you described. I need to check the version if the USB driver, but don't think this will improve anything.
As I have written I am getting "protected device" error.
My V50 is locked, does it have any influence?
Click to expand...
Click to collapse
If you have the right ota it should work.
And also the correct security patch. Maybe this is why it's not working...

Inerent said:
If you have the right ota it should work.
And also the correct security patch. Maybe this is why it's not working...
Click to expand...
Click to collapse
did u tried?

Inerent said:
If you have the right ota it should work.
And also the correct security patch. Maybe this is why it's not working...
Click to expand...
Click to collapse
Can you explain why the security patch matters or why u can only fota upgrade from certain firmwares?

https://mega.nz/#!gjJi3KiK!ebsQdxmnXtEYRiG69F5oAlVqNnsZ3c9D7SpWahGI8OQ
---------- Post added at 09:07 AM ---------- Previous post was at 09:06 AM ----------
antintin said:
Can you explain why the security patch matters or why u can only fota upgrade from certain firmwares?
Click to expand...
Click to collapse
even patch name stipulates specific old firmmware version. And yes, I am on v10p.

[LINUX] Unlock bootloader of HUAWEI P20 lite with PotatoNV in Linux

The genius Andrey Smirnoff, author of PotatoNV, offers a version of the program that can be used in Linux, called PotatoNV-crossplatform, written in python3.
Steps to unlock bootloader of HUAWEI P20 lite with PotatoNV in Linux (can be used for any Huawei phone listed, tested in Arch Linux)
1) Prepare the software
- Download PotatoNV-crossplatform, unpack and cd inside it
- Prepare a venv, using python3/pip3 :
Code:
python -m venv ./
source ./bin/activate
pip install -r requirements.txt
- Fix some bugs of the software:
i. in file main.py, line 48, replace %s with the name of the folder, that lies under ./bootloaders and contains the bootloader of your phone, eg for P2 lite:
Code:
args.manifest = "./bootloaders/hisi659a/manifest.json".format(args.bootloader)
ii. in file imageflasher.py, comment out lines 59, 67 and 76, as function ui.debug is not defined in module ui
2) Prepare the hardware (omitting the details, you can find them easily online)
- open the back case using heat from a hair dryer, better start from the left side as you see the phone from the back
- connect (short, ground) the test point with the adjucent metal case
- connect the phone to USB cable with the spare hand (eg. by pushing the cable while the phone is hold at a fixed edge)
- notice if the phone screen lights on. If it does, unplug the cable and try again until no light comes up (you can see light through the chips of the open phone)
- check that the device /dev/ttyUSB0 shows up (the interface well known to those who connect devices with UART...)
3) Run the program:
-
Code:
python -m usrlock
(if you hit at permission problem run the above as root)
- select any bootloader (as you have hardcoded the correct one)
- select any 16-digit code, eg 1111111111111111
Wait as the 'magic' happens!
Your phone's bootloader in now unlocked. The phone will reboot, low level reset and start!
Good luck with flashing!

Thanks for sharing!

Thanks for sharing this quide.
In my case it didn't work. Lack of knowledge, propably. I got message
Code:
PotatoNV-crossplatform-master]$ python -m usrlock
Traceback (most recent call last):
File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/home/xxxx/Lataukset/PotatoNV-crossplatform-master/usrlock/__main__.py", line 2, in <module>
import chalk
ModuleNotFoundError: No module named 'chalk'
Everyting seemed to be installed. But I quess something is missing. There is no "chalk" in anywhere. Do you happen to know about this case?

kuukkeli01 said:
Thanks for sharing this quide.
In my case it didn't work. Lack of knowledge, propably. I got message
Code:
PotatoNV-crossplatform-master]$ python -m usrlock
Traceback (most recent call last):
File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/home/xxxx/Lataukset/PotatoNV-crossplatform-master/usrlock/__main__.py", line 2, in <module>
import chalk
ModuleNotFoundError: No module named 'chalk'
Everyting seemed to be installed. But I quess something is missing. There is no "chalk" in anywhere. Do you happen to know about this case?
Click to expand...
Click to collapse
same boat here

kuukkeli01 said:
Thanks for sharing this quide.
In my case it didn't work. Lack of knowledge, propably. I got message
Code:
PotatoNV-crossplatform-master]$ python -m usrlock
Traceback (most recent call last):
File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/home/xxxx/Lataukset/PotatoNV-crossplatform-master/usrlock/__main__.py", line 2, in <module>
import chalk
ModuleNotFoundError: No module named 'chalk'
Everyting seemed to be installed. But I quess something is missing. There is no "chalk" in anywhere. Do you happen to know about this case?
Click to expand...
Click to collapse
Use this on your terminal:
Bash:
python -m venv ./
source ./bin/activate
pip install -r requirements.txt
After that don't close the terminal and continue with the next command:
Bash:
python -m usrlock
To running as root you must first do:
Bash:
sudo su
and next run all the above commands (you can skip the install part: "pip install -r requirements.txt").

In my case this didn't work even after OP bug fixes. I had to add one line to main.py file in write_nvme function after ui.success("Bootloader code updated") just before rebooting:
Code:
fb.unlock(key)
Which makes sense to me, if script wasn't even trying to unlock bootloader then why should it be? Wonder why this worked for you guys, maybe I have too new EMUI?

Hello!
Just updating since I just followed your tutorial and ended up unlocking my P8 so thank you!
For anyone encountering an error with M2Crypto when performing pip install requirements.txt, it's a problem with depedencies that I solved following this post: https://github.com/google/python-adb/issues/112#issuecomment-530824958
Also, I used the bootloader from the main PotatoNV release, doing so I had to use another manifest.json since the windows release bootloaders use a xml file, i just modified the name of it and dragged it in the directory of the new bootloader, it went fine. I precise that I have no idea wtf I was doing but since the "adress" line of the two other file was the same I assumed the manifest was the same with just another format. Anyway it worked, and I think I had to do this because installing the "old" bootloaders, hisi659a, returned an error in potatoNV, whilst hisi65x_a went fine.
Thanks again, I will now brick it while installing shady roms and making big mistakes.

LeSplendide said:
Hello!
Just updating since I just followed your tutorial and ended up unlocking my P8 so thank you!
For anyone encountering an error with M2Crypto when performing pip install requirements.txt, it's a problem with depedencies that I solved following this post: https://github.com/google/python-adb/issues/112#issuecomment-530824958
Also, I used the bootloader from the main PotatoNV release, doing so I had to use another manifest.json since the windows release bootloaders use a xml file, i just modified the name of it and dragged it in the directory of the new bootloader, it went fine. I precise that I have no idea wtf I was doing but since the "adress" line of the two other file was the same I assumed the manifest was the same with just another format. Anyway it worked, and I think I had to do this because installing the "old" bootloaders, hisi659a, returned an error in potatoNV, whilst hisi65x_a went fine.
Thanks again, I will now brick it while installing shady roms and making big mistakes.
Click to expand...
Click to collapse
On debian I had to add a bit more of dev packages:
- libxslt1-dev
- libxml2-dev
- python3-dev
- libssl-dev
- python3-m2crypto
- swig
- python3-rsa
I have a question though, as I am not familiar with those bootloader for huawei devices.
Is there a specific fastboot image (bootloader) for P8 ?
Thanks

I have a general question, though, might not be the place but.
The phone I have is FRP locked and bootloader locked.
If I can unlock the bootloader would I be able to run some kind of `fastboot oem erase-frp`?
Thanks

dave2017 said:
fastboot oem erase-frp`?
Click to expand...
Click to collapse
for what reason? You can change FRP status in settings > developers option. Btw, the command fastboot oem erase-frp doesn't work on Kirin, afaik.

-Alf- said:
for what reason? You can change FRP status in settings > developers option. Btw, the command fastboot oem erase-frp doesn't work on Kirin, afaik.
Click to expand...
Click to collapse
The reason is that phone was given to me, reset and frp locked. The previous user does not remember the account she used.

dave2017 said:
The reason is that phone was given to me, reset and frp locked. The previous user does not remember the account she used.
Click to expand...
Click to collapse
so you need google account bypass, not FRP unlock on the phone, it's not the same...
dave2017 said:
The previous user does not remember the account she used
Click to expand...
Click to collapse
Really?

-Alf- said:
so you need google account bypass, not FRP unlock on the phone, it's not the same...
Really?
Click to expand...
Click to collapse
Yeah really, she is 70 year old and does not really get an understanding of what an account is.

-Alf- said:
so you need google account bypass, not FRP unlock on the phone, it's not the same...
Really?
Click to expand...
Click to collapse
And what is a google account bypass? How can I get something for that? Thanks

Amazing!
I just discovered it. Thank you so much! We're going to be able to unlock our phones finally!