Related
I'm really sorry if the means of doing this has been posted but I have looked and I cannot find it. I would assume that I am not the only person who would want to do this, so if someone can either point me in the way of a definitive guide or tell me it simply isn't possible then I'm grateful for your help.
Here's what I know:
I can easily flash my Three UK (H3G) LG G5 to the open EU version of Nougat via Uppercut/LGUP
I can easily flash it to the EE version of Nougat for the UK
I can easily flash it back to the H3G version of Marshmallow
In the first two cases I get an error on boot which is related to the cust folder being set to H3G specifically. The only way to get the device to boot without these errors is to flash back to the Three firmware. There is no nougat firmware from Three for the G5 yet because they are utterly rubbish.
My question is, *is there a way to flash the open EU ROM, wipe or convert the cust folder by unlocking the BL and rooting, un-root, flash the normal recovery back on and re-lock the boot loader and basically convert my G5 into an Open EU model with OTA updates and no evidence that I have ever tampered with the device at all?*
Or do I have to accept that in buying a Three branded device it will always be hobbled in some way?
I've always found it incredibly easy to flash Samsung devices with ODIN so this level of PITA-ery is all new to me!
Thanks in advance everyone, and sorry once again if a guide for this has been posted, but I genuinely cannot find a guide specifically detailing the solution to my request.
On a side note, if I flash the Open EU KDZ (confession, I have), will I still get OTA up dates - for example, to 20C - once they arrive, or does the cust folder error on boot signal some borkery that will disable OTA updates from working?
Thanks again everyone
Also apologies but this should probably be in Q&A. Genuine user error!
Just find a European Nougat kdz flash it thro lgup and hey presto ....nougat on the G5 I've been running v20x ever since it was available.
I already did that, but I get an error everytime I reboot because even though I've flashed the KDZ for the open EU ROM the cust folder is still set to Three UK I believe. Was your device network branded?
leoni1980 said:
I already did that, but I get an error everytime I reboot because even though I've flashed the KDZ for the open EU ROM the cust folder is still set to Three UK I believe. Was your device network branded?
Click to expand...
Click to collapse
May be you have to flash boot logo. I have never checked flashing boot logo like I did with Nexus phones.
Sent from my LG-H850 using Tapatalk
There is no Three splash screen on my device - it is just running the stock splash screen now. The only issue I have is that I get the errors on boot relating to the CUST folder.
I got the official US model Xperia XZ1 from Amazon and wondering if there is a guide to flash the international firmware on the US model so that I can use the damn fingerprint sensor which Sony disables on the US model.
Anybody tried it on the XZ1? Would appreciate a simple guide or steps.
Sent from my G8342 using Tapatalk
Flashing XZ1 and XZ1 Compact is very similiar to flashing XZ premium.
1. Download XZ1 Driver
https://developer.sonymobile.com/downloads/drivers/xperia-xz1-driver/
2. Download xperiafirm and newflasher
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
3. Use Xperiafirm to download desired rom for your phone.
4. Place newflasher in the directory of the downloaded rom
5. Reboot the phone to flash mode (turn off and then hold volume down while connecting usb cable.
6. Install USB driver
7. Run newflasher - This will delete all userdata - there are better instructions if saving userdata matters to you.
8. After newflasher finishes, restart phone.
For one set of more detailed instructions
https://forum.xda-developers.com/showpost.php?p=72958788&postcount=16
rp3 said:
Flashing XZ1 and XZ1 Compact is very similiar to flashing XZ premium.
1. Download XZ1 Driver
https://developer.sonymobile.com/downloads/drivers/xperia-xz1-driver/
2. Download xperiafirm and newflasher
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
3. Use Xperiafirm to download desired rom for your phone.
4. Place newflasher in the directory of the downloaded rom
5. Reboot the phone to flash mode (turn off and then hold volume down while connecting usb cable.
6. Install USB driver
7. Run newflasher - This will delete all userdata - there are better instructions if saving userdata matters to you.
8. After newflasher finishes, restart phone.
For one set of more detailed instructions
https://forum.xda-developers.com/showpost.php?p=72958788&postcount=16
Click to expand...
Click to collapse
were can I find the instructions if I dont want to erase userdata? I searched the newflasher thread but still not shure what to do
I'm not very familiar with the changes to save userdata but, as near as I understand it, delete the userdata file to not flash it. The detailed instructions seems like they contain the exact files (of course, finding the XZ1 version) needed to accomplish the fingerprint enabling goal
rp3 said:
I'm not very familiar with the changes to save userdata but, as near as I understand it, delete the userdata file to not flash it. The detailed instructions seems like they contain the exact files (of course, finding the XZ1 version) needed to accomplish the fingerprint enabling goal
Click to expand...
Click to collapse
just flashed my phone, deleted userdata.sin and all .ta files and that worked perfect. Got the firmware I wanted and kept all userdata!
Sorry for the thread hijack
kirdroid said:
I got the official US model Xperia XZ1 from Amazon and wondering if there is a guide to flash the international firmware on the US model so that I can use the damn fingerprint sensor which Sony disables on the US model.
Anybody tried it on the XZ1? Would appreciate a simple guide or steps.
Sent from my G8342 using Tapatalk
Click to expand...
Click to collapse
I responded to a similar thread in Reddit:
https://www.reddit.com/r/SonyXperia/comments/7433id/has_anyone_enabled_xz1_fingerprint_scanner/
I'll repost the content here so you don't have to go to the page. I should preface this with "This worked for me. YMMV"
I have with Newflasher. I had an issue with the XZs and XZ1 where if I flashed another region's firmware, I could get a fingerprint scanner, but I could not send group MMS messages. And you know everyone will hate you if you screw up a perfectly good MMS group message session with individual SMS messages.
I tried following this guide for the XZ Premium to get the US firmware with a working fingerprint scanner from a CE1 firmware:
https://forum.xda-developers.com/xz-premium/help/version-flashing-internation-version-t3629823
but it didn't enable it for the XZ1.
So I was using the standard US firmware for the last week.
Fast forward to today, I decided to give it another shot using the CE1 firmware as a basis. After a few failed attempts, I decided to add additional *.sin files one at a time. The second one I added was the oem*.sin. That disabled my MMS group messages. So I flashed the US version back and it re-enabled MMS.
For my next step I decided to add a few more more to try to get the fingerprint scanner to work. That next attempt solved it. However, I do not know what exact combination of files are the minimum amount you need. Here are all of the sin files I flashed. They are sort of ordered by size because one of the examples in the xda thread was ordered that way.
These are the files I needed to flash to enable the fingerprint sensor on the US firmware from the CE1 firmware.
* system_X-FLASH-ALL-C93B.sin
* vendor_X-FLASH-ALL-C93B.sin
* partition.zip (someone else confirmed this is not necessary)
Note. When I was narrowing the files down, I flashed in a manner that kept my data. So my fingerprints were still usable once I re-enabled the fingerprint manager.
I'm not sure if edits may notify anyone watching this thread. If not, I narrowed down the files I needed to flash to get the US firmware working with a fingerprint sensor.
aj.eats.sushi said:
I responded to a similar thread in Reddit:
https://www.reddit.com/r/SonyXperia/comments/7433id/has_anyone_enabled_xz1_fingerprint_scanner/
I'll repost the content here so you don't have to go to the page. I should preface this with "This worked for me. YMMV"
I have with Newflasher. I had an issue with the XZs and XZ1 where if I flashed another region's firmware, I could get a fingerprint scanner, but I could not send group MMS messages. And you know everyone will hate you if you screw up a perfectly good MMS group message session with individual SMS messages.
I tried following this guide for the XZ Premium to get the US firmware with a working fingerprint scanner from a CE1 firmware:
https://forum.xda-developers.com/xz-premium/help/version-flashing-internation-version-t3629823
but it didn't enable it for the XZ1.
So I was using the standard US firmware for the last week.
Fast forward to today, I decided to give it another shot using the CE1 firmware as a basis. After a few failed attempts, I decided to add additional *.sin files one at a time. The second one I added was the oem*.sin. That disabled my MMS group messages. So I flashed the US version back and it re-enabled MMS.
For my next step I decided to add a few more more to try to get the fingerprint scanner to work. That next attempt solved it. However, I do not know what exact combination of files are the minimum amount you need. Here are all of the sin files I flashed. They are sort of ordered by size because one of the examples in the xda thread was ordered that way.
These are the files I needed to flash to enable the fingerprint sensor on the US firmware from the CE1 firmware.
* system_X-FLASH-ALL-C93B.sin
* vendor_X-FLASH-ALL-C93B.sin
* partition.zip (someone else confirmed this is not necessary)
Note. When I was narrowing the files down, I flashed in a manner that kept my data. So my fingerprints were still usable once I re-enabled the fingerprint manager.
Click to expand...
Click to collapse
are voLTE and voWIFI still active with this method?
WaxysDargle said:
are voLTE and voWIFI still active with this method?
Click to expand...
Click to collapse
According to this reply in Reddit, it worked for someone with an XZ1C on T-mobile. From what I've heard, the XZ1C has voLTE and voWIFI, but the XZ1 doesn't have it enabled. I'll admit that I haven't done any thorough research on it since I don't have T-Mobile. :
https://www.reddit.com/r/SonyXperia...yone_enabled_xz1_fingerprint_scanner/do1fipe/
aj.eats.sushi said:
According to this reply in Reddit, it worked for someone with an XZ1C on T-mobile. From what I've heard, the XZ1C has voLTE and voWIFI, but the XZ1 doesn't have it enabled. I'll admit that I haven't done any thorough research on it since I don't have T-Mobile. :
https://www.reddit.com/r/SonyXperia...yone_enabled_xz1_fingerprint_scanner/do1fipe/
Click to expand...
Click to collapse
If you search for volte in settings and select it, does it take you to any volte settings?
WaxysDargle said:
If you search for volte in settings and select it, does it take you to any volte settings?
Click to expand...
Click to collapse
I see it in the settings search but when I select it no volte settings appear.
Debrand Xz1
Hi,
Is the procedure for Sony XZ1 debrand equal to that of XZ Premium? There isn't "flash_session" subfolder in the firmware folder "Customized IT", why?. It's necessary extract the "partition.zip" and put the files into a folder named "partition" or delete some other files? It's possible run the procedure with the bootloader locked and the procedure unblocks the bootloader? After the flash with "newflasher" it's possible use the OTA update?
Thanks.
My phone is the XZ1 Dual (G8342) factory unlocked, I downloaded the "MY" firmware with a lot of TA files, including Simlock.TA, cust-reset.TA, etc.
I don't care about my personal files, I just want everything purged as if I got a brand new phone.
If I want to flash as much as I can without getting my phone bricked, which files should I take out from the folder before flashing it?
Do I just take out the Simlock.ta, or do I need to add some other .TA files? or can I just leave everything as it is?
Thanks.
aj.eats.sushi said:
I responded to a similar thread in Reddit:
https://www.reddit.com/r/SonyXperia/comments/7433id/has_anyone_enabled_xz1_fingerprint_scanner/
I'll repost the content here so you don't have to go to the page. I should preface this with "This worked for me. YMMV"
I have with Newflasher. I had an issue with the XZs and XZ1 where if I flashed another region's firmware, I could get a fingerprint scanner, but I could not send group MMS messages. And you know everyone will hate you if you screw up a perfectly good MMS group message session with individual SMS messages.
I tried following this guide for the XZ Premium to get the US firmware with a working fingerprint scanner from a CE1 firmware:
https://forum.xda-developers.com/xz-premium/help/version-flashing-internation-version-t3629823
but it didn't enable it for the XZ1.
So I was using the standard US firmware for the last week.
Fast forward to today, I decided to give it another shot using the CE1 firmware as a basis. After a few failed attempts, I decided to add additional *.sin files one at a time. The second one I added was the oem*.sin. That disabled my MMS group messages. So I flashed the US version back and it re-enabled MMS.
For my next step I decided to add a few more more to try to get the fingerprint scanner to work. That next attempt solved it. However, I do not know what exact combination of files are the minimum amount you need. Here are all of the sin files I flashed. They are sort of ordered by size because one of the examples in the xda thread was ordered that way.
These are the files I needed to flash to enable the fingerprint sensor on the US firmware from the CE1 firmware.
* system_X-FLASH-ALL-C93B.sin
* vendor_X-FLASH-ALL-C93B.sin
* partition.zip (someone else confirmed this is not necessary)
Note. When I was narrowing the files down, I flashed in a manner that kept my data. So my fingerprints were still usable once I re-enabled the fingerprint manager.
Click to expand...
Click to collapse
i just wanna say thank you. this really helped a great deal because i had the exact same situation. everything is working great now. thanks to everyone's contribution here.
Will this method allow you to receive OTA updates or will you need to do it for each OS version that comes out?
Question:
Is this still the preferred method, or does flashing via Flashtool work 100% for the XZ1 now?
Just got around flashing the UK version but I keep loosing data, phone is most of the time on 1 bar to completely none. Is this because the UK version or is there a fix I could do to get better signal or should i flash US version back? But I want to keep fingerprint enabled. I on cricket mobile, has anyone had this problem?
562TOKER said:
Just got around flashing the UK version but I keep loosing data, phone is most of the time on 1 bar to completely none. Is this because the UK version or is there a fix I could do to get better signal or should i flash US version back? But I want to keep fingerprint enabled. I on cricket mobile, has anyone had this problem?
Click to expand...
Click to collapse
Flash the US version but swap the system.sin and vendor.sin for the CE1(Europe) ones. Basically go inside the US firmware folder delete system.sin, vendor.sin, go back to the CE1(Europe) folder, copy system.sin, vendor.sin and paste them into US firmware folder. Flash!
dcrin3 said:
Basically go inside the US firmware folder delete system.sin, vendor.sin, go back to the CE1(Europe) folder, copy system.sin, vendor.sin and paste them into US firmware folder. Flash!
Click to expand...
Click to collapse
WARNING! I tried replacing system.sin and vendor.sin with the files from Central Europe before flashing the latest US firmware and it (temporarily) bricked an XZ1 Dual (8342). Screen just froze with perpetual Sony logo at bootup. Once I flashed back to straight US firmware, it booted as expected (but no fingerprint reader, of course).
Presumably this problem occurred because the current US firmware is Android 9.0 Pie (version 47.2.A.2.33_R2C) whereas the current CE firmware is still Android 8.0 Oreo (version 47.1.A.16.20_R7B). Maybe the selective replacement of certain .sin files works OK when both sets of firmware are for the same version, but it does not seem to work when the versions are different. Not surprising, I guess.
Any XZ1 users out there who have been successful in activating the fingerprint reader with Android 9.0 firmware?
biff_p said:
WARNING! I tried replacing system.sin and vendor.sin with the files from Central Europe before flashing the latest US firmware and it (temporarily) bricked an XZ1 Dual (8342). Screen just froze with perpetual Sony logo at bootup. Once I flashed back to straight US firmware, it booted as expected (but no fingerprint reader, of course).
Presumably this problem occurred because the current US firmware is Android 9.0 Pie (version 47.2.A.2.33_R2C) whereas the current CE firmware is still Android 8.0 Oreo (version 47.1.A.16.20_R7B). Maybe the selective replacement of certain .sin files works OK when both sets of firmware are for the same version, but it does not seem to work when the versions are different. Not surprising, I guess.
Any XZ1 users out there who have been successful in activating the fingerprint reader with Android 9.0 firmware?
Click to expand...
Click to collapse
Of course it's not going to work across different version numbers, there has been instances where it has but most of the time it's a no.
And for sure it will never work between 8.0/9.. That's risky to even attempt it.
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
duraaraa said:
This is TWRP to Mate 9/Android O, brought to you by FunkyHuawei.
It's just a preliminary build so I can't promise anything/everything will work! Keep that in mind. I'm not responsible if you brick your device.
EDIT: Does not work with Mate 10 series.
DOWNLOAD LINK:
https://drive.google.com/open?id=0B45NCsO2AL_1NEh2aDFLM3JlYkU
It works on the Android O build here:
https://www.reddit.com/r/FunkyHuawei/comments/75uwkd/october_12_first_official_android_o_beta_for/
and the official European beta.
To install:
First, have Android O running. Unlock the bootloader. Download the twrp image.
Then, run in fastboot mode:
fastboot flash recovery_ramdisk twrp_android_o_mate9_a1.img
Then, reboot holding volume up, and you've got TWRP!
Note: With the Android O update, it is no longer possible to flash the recovery2 partition. Furthermore, the names of the partitions have changed. Please keep that in mind, and don't mess around too much with TWRP, to be sure you don't brick your system!
Click to expand...
Click to collapse
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
AndDiSa said:
Hmm ... I wanted to ask you whether you have the full OTA package for your device? So you should be able to extract all the partition images from there and to fastboot flash them. But I checked on HFF and I do not see a full OTA package matching your device yet.
Click to expand...
Click to collapse
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
I've tried flashing the entire update.zip file in TWRP...but as noted TWRP is unable to mount internal storage. I'm not sure if I need to wipe and reformat first. I also have no clue whether the TWRP build I installed is properly compatible with the device. I had nothing to lose by giving it a shot.
thref23 said:
I've tried flashing system.img/ramdisk.img from the c00 package. Maybe I have to wait for c636 firmware, or maybe I have to flash additional .imgs. I am pretty sure that the specs and hardware I have are the same as the c00.
Click to expand...
Click to collapse
This will not work as the boot chain will be broken due to mismatching checksums. You need to have the correct images. To flash a OTA image you also need to have the standard recovery image installed ...
So...will someone correct please correct me if this is wrong?
If I were to flash a c00 oeminfo file, I could then install a c00 update.zip via dload folder?
Would c432 work as well (with a flashed oeminfo), even though the Euro hardware has different bands than my hardware?
There is now a full OTA on FF for C635.....still nothing for c636...
Finally, a full OTA is available for c636.
But the 'dload' method (update.app on an sd card) failed at 5%. And flashing ramdisk/recovery/erecovery/system images also failed.
Is this possibly because the OTA is B153, whereas my M5 was shipped B121?
(I hate to be that guy bumping his own thread, sorry)
I'm unbricked!
For those in a similar spot, looking to rebrand, or otherwise interested...
I finally e-mailed Funky Huawei for assistance. Their unbrick tool did not work. However, their e-recovery method worked perfectly (basically, you point your router's DNS to Funky Huawei, enter stock recovery and connect to wi-fi, and Funky Huawei's servers mimic Huawei's servers. If they do not have your firmware on their server, they will add it by request (provided it exists on the internet).
I paid $65 for a 30 day pass - a little steep, but I was impatient. I'm not sure if I could have gotten away with paying less. If you want to try and use my FH account over the next 30 days PM me (although I don't want to get carried away with that).
For those looking to rebrand, if you can flash an OEMinfo file successfully (FH has a rebrand tool and I have no clue how well it works), you should be able to use FH's erecovery method to flash firmware (don't blame me if something goes wrong).
One reason for the trouble I was having, if because I bootlooped after making a change to the vendor/build.prop file. This file was on the vendor partition, not the system partition, and for whatever reason the vendor partition cannot be flashed via fastboot (in theory it can be flashed, in reality it returns an error that doesn't have to do with the size of the partition).
Before reverting to FH, I finally got TWRP installled and functioning, and after all the attempts I made to recover my device, the same build.prop file which initially caused a bootloop was still in the /vendor folder. And TWRP wouldn't mount the system and vendor partitions as read/writeable - that was frustrating.
Now off to experiment with AOSP GSIs while I feel like I have little to lose...
Please help me
hello everyone,
i tried to rebrand my m5pro with help of ministryofsolutions. Something went wrong and my tablet (CMR-AL19) is stucked in the recovery mode. how can i fix it? Someone who ca help me? I will pay
Greeztings
Luigi
thref23 said:
Bricked your M5? Post here. I am one of three posters who have posted threads requesting assistance - we might as well create one thread where we can try and help each other.
My model? SHT-AL09 (C636). My story? I apparently made a bad change to my build.prop file, and had USB debugging disabled. I then probably dug myself a deeper hole trying to recover. I don't even get boot animation anymore. I'd happily pay someone to unbrick me.
The only potential progress I have made, is that I was able to install and successfully boot TWRP - although TWRP detects that I have no operating system installed and I am unable to mount any partitions except for my external SD card. Using TWRP's file manager, I can see that the system partition, for example, has not been entirely wiped, but many files seem to be missing. At the very least, TWRP allows me to turn the screen off without seeking to contantly reboot thereafter.
To install TWRP, I followed these instructions intended for Mate 9 owners:
Click to expand...
Click to collapse
Hi All,
I tried some custom ROM on my P20 lite and it got stuck in a boot loop. So I flashed the Stock ROM from this thread using HuRUpdater. I tried version 8.0.0.146 then realised my p20 lite is only single sim unlike my partner's one so flashed 8.0.0.143 to see if that works.
The phone boots with both but shows Build Number 8.0.0.046(0CXB) and I can't get it to update. My partner's P20 Lite shows Build Number 8.0.0.144(C432) so I assume mine should work with the 143 SS from the thread above. My partners phone is just left stock bootloader hasn't been touched.
Any ideas what I'm doing wrong? I've tried eRecovery and that just says can't get package info.
At a loss now.
MikeyAlder said:
Hi All,
I tried some custom ROM on my P20 lite and it got stuck in a boot loop. So I flashed the Stock ROM from this thread using HuRUpdater. I tried version 8.0.0.146 then realised my p20 lite is only single sim unlike my partner's one so flashed 8.0.0.143 to see if that works.
The phone boots with both but shows Build Number 8.0.0.046(0CXB) and I can't get it to update. My partner's P20 Lite shows Build Number 8.0.0.144(C432) so I assume mine should work with the 143 SS from the thread above. My partners phone is just left stock bootloader hasn't been touched.
Any ideas what I'm doing wrong? I've tried eRecovery and that just says can't get package info.
At a loss now.
Click to expand...
Click to collapse
Is your device an ANE-LX1C432 Single SIM ?
Do you have SIM locked or is free?
It's single SIM and as far as I know it's ane-lx1C432 bought in the UK. It's also sim unlocked
MikeyAlder said:
It's single SIM and as far as I know it's ane-lx1C432 bought in the UK. It's also sim unlocked
Click to expand...
Click to collapse
1- Install terminal emulator from google play
2- Run this command
Code:
getprop ro.hw.custPath
3- If the output is different from this => /cust/hw/eu => let us know
HWANE:/ $ getprop ro.hw.custPath
/cust/o2/uk
HWANE:/ $
you flashed wrong lx1 file, its same with me, i flashed for my dual sim what are ANE-LX1c432 (dual sim actualy are ANE-L21c432 but single sim are ANE-L01c432) so i flashed for my dual sim ANE-L01c432 and now in build number i have 8.0.0.046(09B8) you need to download right ANE-L01C432 and agine with hurupdate, and all be ok
oh, right, your cust info are different, my writed here are wrong (becasue for me cust are hw/eu)
MikeyAlder said:
HWANE:/ $ getprop ro.hw.custPath
/cust/o2/uk
HWANE:/ $
Click to expand...
Click to collapse
In your phone only ROM's from your provider (O2) will work without issues.
You should restore your backup from your original rom.
Thanks for the info. I seem to have deleted my backup so not sure where to get O2 ROMs from. Am I able to change it to accept the EU ROMs or is that not possible?
MikeyAlder said:
Thanks for the info. I seem to have deleted my backup so not sure where to get O2 ROMs from. Am I able to change it to accept the EU ROMs or is that not possible?
Click to expand...
Click to collapse
Yes it is, but void your warranty.
1. Backup your oeminfo partition, use TWRP.
2. Check the thread HwOTA8 for Huawei P20 Lite, in this tool you can learn how to change oeminfo to hw/eu
3. Then install full firmware B146, but the Dual SIM, because that oeminfo is for Dual. This installation can be done with HuRUpdater tool
4. It's done.
Other possible way to restore your device is use a TWRP backup from other device with O2 rom.
Do it at your own risk.
kilroystyx said:
Yes it is, but void your warranty.
1. Backup your oeminfo partition, use TWRP.
2. Check the thread HwOTA8 for Huawei P20 Lite, in this tool you can learn how to change oeminfo to hw/eu
3. Then install full firmware B146, but the Dual SIM, because that oeminfo is for Dual. This installation can be done with HuRUpdater tool
4. It's done.
Other possible way to restore your device is use a TWRP backup from other device with O2 rom.
Do it at your own risk.
Click to expand...
Click to collapse
Thanks for all your help. Just got round to do this tonight and all is working correctly now. ?
I am new to this and I am very confused, I have the bootloader blocked in my p20 lite, I have ANE-LX3 with bloatware operator, I just want to remove all the bloatware and leave my cell phone with stock version without bloatware operator .... as I could remove everything that and with what program do you start?
jorgerolonpy said:
I am new to this and I am very confused, I have the bootloader blocked in my p20 lite, I have ANE-LX3 with bloatware operator, I just want to remove all the bloatware and leave my cell phone with stock version without bloatware operator .... as I could remove everything that and with what program do you start?
Click to expand...
Click to collapse
read, try this
I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Guille05 said:
I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Click to expand...
Click to collapse
What original firmware was on it?Most definitely,always make a full back up first thing.
Surgemanxx said:
What original firmware was on it?Most definitely,always make a full back up first thing.
Click to expand...
Click to collapse
It was originally on version 20p of the sprint software. And yeah, I definitely hadn't quite read up on all of the important things I needed to backup beforehand.
Guille05 said:
I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Click to expand...
Click to collapse
The same thing happened to me, I came from a10 sprint and installed a11 from Canada, I was left without a network and without a fingerprint sensor, but the other sensors work without problem, to fix network and ntcode I think it is only possible by box, I don't know if of the fingerprint sensor is caused by the lack of serial and imei.
if you come up with a solution let me know bro
mclarenf195 said:
The same thing happened to me, I came from a10 sprint and installed a11 from Canada, I was left without a network and without a fingerprint sensor, but the other sensors work without problem, to fix network and ntcode I think it is only possible by box, I don't know if of the fingerprint sensor is caused by the lack of serial and imei.
if you come up with a solution let me know bro
Click to expand...
Click to collapse
Did you restore your 7 bin files after flashing the A11 software?
Guille05 said:
Did you restore your 7 bin files after flashing the A11 software?
Click to expand...
Click to collapse
They don't have a backup,that's the reason I ask what version software it was.
Guille05 said:
It was originally on version 20p of the sprint software. And yeah, I definitely hadn't quite read up on all of the important things I needed to backup beforehand.
Click to expand...
Click to collapse
Use this firmware.It will correct your issues.
Download LG Firmware for LG G8X ThinQ LMG850QM _Unknown kdz stock USA Rom
Download _Unknown KDZ stock firmware for download with direct link
lg-roms.com
Guille05 said:
Did you restore your 7 bin files after flashing the A11 software?
Click to expand...
Click to collapse
I have the backup of the 7 partitions but they are useless if all the original partitions have been deleted, that is what I understand, I restored the partitions of a KDZ a10 and then flashed it to a11
Surgemanxx said:
Use this firmware.It will correct your issues.
Download LG Firmware for LG G8X ThinQ LMG850QM _Unknown kdz stock USA Rom
Download _Unknown KDZ stock firmware for download with direct link
lg-roms.com
Click to expand...
Click to collapse
I've got version 30c of that firmware installed, you think going back one update would fix it?
mclarenf195 said:
I have the backup of the 7 partitions but they are useless if all the original partitions have been deleted, that is what I understand, I restored the partitions of a KDZ a10 and then flashed it to a11
Click to expand...
Click to collapse
When you flashed the A10 kdz, you followed netmsm's guide right? Did you get any errors when flashing the partitions with fhloader? When I extracted the kdz a few files were missing from the ones used by that code but every kdz I've extracted doesn't have them either.
Guille05 said:
I've got version 30c of that firmware installed, you think going back one update would fix it?
Click to expand...
Click to collapse
Yes,go to 30b it will all work.I tried 30c on my sprint model,and had issues with network connectivity as well.
Surgemanxx said:
Yes,go to 30b it will all work.I tried 30c on my sprint model,and had issues with network connectivity as well.
Click to expand...
Click to collapse
I have the 30a, it would be to try
Guille05 said:
When you flashed the A10 kdz, you followed netmsm's guide right? Did you get any errors when flashing the partitions with fhloader? When I extracted the kdz a few files were missing from the ones used by that code but every kdz I've extracted doesn't have them either.
Click to expand...
Click to collapse
yes, the netmsm's guide, fhloader only use it to restore the luns, restore the kdz partitions one by one with qfil, just try what Surgemanxx suggested first and tell me how it goes.
mclarenf195 said:
yes, the netmsm's guide, fhloader only use it to restore the luns, restore the kdz partitions one by one with qfil, just try what Surgemanxx suggested first and tell me how it goes.
Click to expand...
Click to collapse
It works very well.I tried 30c,and noticed it was slow and laggy and rolled back to 30b and it worked flawless.Fingerprint scanning and all worked with a T-Mobile sim with no issues.They should be good with 30b,all but the IMEI issue they have.
All right I completely erased the flash again and reinstalled following the steps very carefully. I'm now on 30b and can confirm that the sensors work once again. Although the major issues I think were deeper than just the update, because I updated before doing a full erase and it still wasn't working. Now I just have to keep trying to fix the IMEI and FP sensor.
Also I think I may have found my IMEI number thanks to having the ftm partition backed up and therefore still having the serial number. The first 8 digits are always 35886110 for the LG G8x sprint model (and maybe others in the US), the next 6 are the last 6 digits of the serial and the last one is a check digit that you can look up online. I've checked the number on multiple sites and it seems legit so I hope it's actually my number. Now I'll try to write it to the phone somehow, but at least having the IMEI back is a very big step forward.
IMEI is fixed, or at least it appears as such in the phone. I went through with the tutty method of installing the IMEI, and after much trouble (and tutty saying error to my command to write the IMEI) I was able to restore the IMEI to the phone. I confirmed this first using EFS Pro and going into qualcomm NV tools. The IMEI was still as 0 in my phone but after putting in a sim it appeared in the OS and has stayed there. However it still appears as permanently locked when a sim is inserted and the nt-code error does still happen, so the network doesn't work yet.
Guille05 said:
IMEI is fixed, or at least it appears as such in the phone. I went through with the tutty method of installing the IMEI, and after much trouble (and tutty saying error to my command to write the IMEI) I was able to restore the IMEI to the phone. I confirmed this first using EFS Pro and going into qualcomm NV tools. The IMEI was still as 0 in my phone but after putting in a sim it appeared in the OS and has stayed there. However it still appears as permanently locked when a sim is inserted and the nt-code error does still happen, so the network doesn't work yet.
Click to expand...
Click to collapse
That LUNS backup is for the Sprint U.S. model G850UM9.The IMEI is stored in modemst1 and 2 which is LUNS5 that I didn't include for that reason.The NT Code error shouldn't be there if it's the same model/region.Keep me posted.
Surgemanxx said:
That LUNS backup is for the Sprint U.S. model G850UM9.The IMEI is stored in modemst1 and 2 which is LUNS5 that I didn't include for that reason.The NT Code error shouldn't be there if it's the same model/region.Keep me posted.
Click to expand...
Click to collapse
I've flashed your backups and the NT Code error indeed disappeared. However I've still got the perm locked error (so my doesn't work), and the fp sensor still refuses record fingerprints. Was your phone network unlocked when you made that backup? Idk if that maybe interferes with the sim or something
Guille05 said:
I've flashed your backups and the NT Code error indeed disappeared. However I've still got the perm locked error (so my doesn't work), and the fp sensor still refuses record fingerprints. Was your phone network unlocked when you made that backup? Idk if that maybe interferes with the sim or something
Click to expand...
Click to collapse
Yes,it was network unlocked for sure.You're not the only one that has faced this after trying to repair the IMEI.It's perma blocked because it's embedded in the chipset itself,and so far I haven't seen any fix for it as of yet.