Related
OK. I'm running the Moto Z unlocked 64GB version. Everything is stock. I unlocked the bootloader, and then flashed a custom logo to get rid of the "Unlocked bootloader" warning screen. Now the phone will not get past the new logo that I flashed. What can I do? I can get into fastboot or recovery, or boot twrp from fastboot(stock recovery still installed)
How can I get my phone to boot? Even if I have to live with the unlocked bootloader warning I'm cool with that. Please help!
Willing to pay $20 paypal or google wallet to anyone that can help me get my phone back working....
SixShots said:
OK. I'm running the Moto Z unlocked 64GB version. Everything is stock. I unlocked the bootloader, and then flashed a custom logo to get rid of the "Unlocked bootloader" warning screen. Now the phone will not get past the new logo that I flashed. What can I do? I can get into fastboot or recovery, or boot twrp from fastboot(stock recovery still installed)
How can I get my phone to boot? Even if I have to live with the unlocked bootloader warning I'm cool with that. Please help!
Click to expand...
Click to collapse
You should be fine, I'm assuming you flashed that boot logo without installing a custom kernel to disable force encryption and here's how I flashed stock when i did something similar.
This is exactly what I did from a bricked phone. I got a strange "error" message after flashing this that looks like the no command error, but after holding power it rebooted to Nougat.
Using Minimal adb and Fastboot:
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Hope this helps!
I used the Mexican Nougat firmware from here, I'm on 32GB UK model though. https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Just don't flash a MM one if you're coming from Nougat, that will not work. And remember to check the number of system chunks it may not be 16 for whichever firmware you use.
I'm currently downloading the stock MM firmware in hopes that it helps, gotta love living in the middle of nowhere with a 3mb DSL connection :-\
So basically I can't flash a logo unless I flash the kernal first?
Secondly, With this stock MM that i'm downloading, once I flash all of it using fastboot it should be back to stock completely except still have the "Bootloader unlocked" warning, yea?
SixShots said:
I'm currently downloading the stock MM firmware in hopes that it helps, gotta love living in the middle of nowhere with a 3mb DSL connection :-\
So basically I can't flash a logo unless I flash the kernal first?
Secondly, With this stock MM that i'm downloading, once I flash all of it using fastboot it should be back to stock completely except still have the "Bootloader unlocked" warning, yea?
Click to expand...
Click to collapse
Okay so you haven't ever been on Nougat? Just making sure because when you OTA to Nougat there's no way back.
I think so, to be honest I only changed the boot logo after I flashed LineageOS so I'm not sure.. but you need to disable forced encryption by flashing custom kernel to modify system files without it getting stuck booting up. I went through this myself when i first unlocked it, this is what fixed it for me. Good luck!
Yup it should be back to stock but still unlocked bootloader.
supacrazyguy42 said:
Okay so you haven't ever been on Nougat? Just making sure because when you OTA to Nougat there's no way back.
I think so, to be honest I only changed the boot logo after I flashed LineageOS so I'm not sure.. but you need to disable forced encryption by flashing custom kernel to modify system files without it getting stuck booting up. I went through this myself when i first unlocked it, this is what fixed it for me. Good luck!
Yup it should be back to stock but still unlocked bootloader.
Click to expand...
Click to collapse
No I'm on Nougat now, But when I tried to flash one of the Nougat zip's from the post above it stated that I needed to have either 6.0* something OR 7.* something. Which made me think I could flash the 6.0 as an OTA, is that wrong?
I have the XT1650-03, which version of Nougat should I be pulling from that post? The one I got was obviously the wrong one :-\
SixShots said:
No I'm on Nougat now, But when I tried to flash one of the Nougat zip's from the post above it stated that I needed to have either 6.0* something OR 7.* something. Which made me think I could flash the 6.0 as an OTA, is that wrong?
I have the XT1650-03, which version of Nougat should I be pulling from that post? The one I got was obviously the wrong one :-\
Click to expand...
Click to collapse
Okay if you've updated to Nougat there's no way a MM firmware will work, thanks to Moto updating the bootloader making it incompatible. Where was the message that said you needed something? Did you unzip the file and flash each chunk in fastboot?
I think Rogers was a good option, i also have XT1650-03. Maybe try the Retmx like i did.
supacrazyguy42 said:
Okay if you've updated to Nougat there's no way a MM firmware will work, thanks to Moto updating the bootloader making it incompatible. Where was the message that said you needed something? Did you unzip the file and flash each chunk in fastboot?
I think Rogers was a good option, i also have XT1650-03. Maybe try the Retmx like i did.
Click to expand...
Click to collapse
Well... I was able to download and flash the entire ROGERS version, My phone will boot to the Cyan M logo screen and then instead of the animation "ring ring hello moto" the screen just goes black. Eventually it connects to my computer but I can't find a way to turn the screen on or do anything. Downloading the RETLA version to see if that works since I'm pretty sure that was what was on the phone to begin with... *sigh*
SixShots said:
Well... I was able to download and flash the entire ROGERS version, My phone will boot to the Cyan M logo screen and then instead of the animation "ring ring hello moto" the screen just goes black. Eventually it connects to my computer but I can't find a way to turn the screen on or do anything. Downloading the RETLA version to see if that works since I'm pretty sure that was what was on the phone to begin with... *sigh*
Click to expand...
Click to collapse
Ah I don't know why that is, as i said I'm at sure what's best for your model sorry. The easy flash to Nougat guide link i sent you may be better, but yeah if you know it came with RETLA then give that one a try :good:
I think your best bet is to try that RETLA firmware.
I'm not sure how it does with Moto phones, but some variants are kinda picky with their software channels. Factory images designed for retail ("RETxx") devices might have a better chance since my RETAPAC model is on a RETMX build of Nougat. It's slightly older than the TELUS build that's newer and comes with some bug fixes, including one that resolves an issue where the 2 HP CPU cores "park" after some time of use, although I've heard of some issues when using that build with some devices. Mine's a bit iffy, but otherwise seems to run quite nicely.
Once flashed, if you wanna flash system mods, do not boot just yet. Flash or boot into TWRP and try the following kernel
https://forum.xda-developers.com/moto-z/development/kernel-turbo-z-custom-kernel-moto-z-t3493354
This disables forced-encryption and dm-verity (the latter is what's responsible for your phone refusing to boot). Additionally, you can flash SuperSU using the following method.
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113
D13H4RD2L1V3 said:
I think your best bet is to try that RETLA firmware.
I'm not sure how it does with Moto phones, but some variants are kinda picky with their software channels. Factory images designed for retail ("RETxx") devices might have a better chance since my RETAPAC model is on a RETMX build of Nougat. It's slightly older than the TELUS build that's newer and comes with some bug fixes, including one that resolves an issue where the 2 HP CPU cores "park" after some time of use, although I've heard of some issues when using that build with some devices. Mine's a bit iffy, but otherwise seems to run quite nicely.
Once flashed, if you wanna flash system mods, do not boot just yet. Flash or boot into TWRP and try the following kernel
https://forum.xda-developers.com/moto-z/development/kernel-turbo-z-custom-kernel-moto-z-t3493354
This disables forced-encryption and dm-verity (the latter is what's responsible for your phone refusing to boot). Additionally, you can flash SuperSU using the following method.
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113
Click to expand...
Click to collapse
At this point i'm just trying to get my phone to boot lol. I wish I had read more to begin with... Knowing that unlocking the bootloader now breaks the safety net for Android Pay(it didn't with Moto X) is making me worry that it will also cause my Wells Fargo Mobile app to not work. At which point I might as well not even have the phone.
As of now I am able to flash the RETLA version but once I get past the Cyan M logo screen the screen goes blank and does not turn on even though my computer is recognizing that it's there. I'm about to try flashing the RSD rogers MM firmware(without the gpt and bootloader commands) and then sideloading Nougat to see if that gets me anywhere. If i can get it to boot normally I can at least sell it(at a loss) and buy another one. But I need it to at least boot up that way I don't have to sell it for 100 bucks lol. Any other ideas are welcome but I feel like i stepped in quicksand and the more I struggle with it the worse it's getting.
SixShots said:
At this point i'm just trying to get my phone to boot lol. I wish I had read more to begin with... Knowing that unlocking the bootloader now breaks the safety net for Android Pay(it didn't with Moto X) is making me worry that it will also cause my Wells Fargo Mobile app to not work. At which point I might as well not even have the phone.
As of now I am able to flash the RETLA version but once I get past the Cyan M logo screen the screen goes blank and does not turn on even though my computer is recognizing that it's there. I'm about to try flashing the RSD rogers MM firmware(without the gpt and bootloader commands) and then sideloading Nougat to see if that gets me anywhere. If i can get it to boot normally I can at least sell it(at a loss) and buy another one. But I need it to at least boot up that way I don't have to sell it for 100 bucks lol. Any other ideas are welcome but I feel like i stepped in quicksand and the more I struggle with it the worse it's getting.
Click to expand...
Click to collapse
Well, if you want my advice, if you can find it, flash the firmware that your device was last at before you flashed Nougat.
An OTA bricked my Z, but flashing the full firmware made exactly for my variant brought it back to life. If you can find it for yours, you might get a lucky break.
Also, Magisk can help with SafetyNet, though it needs root access.
D13H4RD2L1V3 said:
Well, if you want my advice, if you can find it, flash the firmware that your device was last at before you flashed Nougat.
An OTA bricked my Z, but flashing the full firmware made exactly for my variant brought it back to life. If you can find it for yours, you might get a lucky break.
Also, Magisk can help with SafetyNet, though it needs root access.
Click to expand...
Click to collapse
My issue with that is I can't figure out which firmware was made for my device. I thought it was the RETLA version but apparently I was wrong. Is there any way to figure out which one i need? I have all of the info from my getvar command in fastboot but it's not giving me any info(that i understand) that will point me in the direction of the correct firmware.
I'm currently downloading the rogers MM firmware to see if i can flash back to MM and then sideload nougat but I don't know if that's going to do any good considering that the screen won't load right now with the Nougat firmware I have on it.
SixShots said:
My issue with that is I can't figure out which firmware was made for my device. I thought it was the RETLA version but apparently I was wrong. Is there any way to figure out which one i need? I have all of the info from my getvar command in fastboot but it's not giving me any info(that i understand) that will point me in the direction of the correct firmware.
I'm currently downloading the rogers MM firmware to see if i can flash back to MM and then sideload nougat but I don't know if that's going to do any good considering that the screen won't load right now with the Nougat firmware I have on it.
Click to expand...
Click to collapse
Try RETUS if it fails?
I'm crossing my fingers hoping that the ROGERS firmware can help.
D13H4RD2L1V3 said:
Try RETUS if it fails?
I'm crossing my fingers hoping that the ROGERS firmware can help.
Click to expand...
Click to collapse
You mean the RETUS 6.0 firmware? And basically go through the same thing as the ROGERS firmware (flash mm without GPT and bootloader) and then try to upgrade? I haven't been able to find a RETUS 7.0 firmware anywhere yet so I assume that's what you mean...
SixShots said:
You mean the RETUS 6.0 firmware? And basically go through the same thing as the ROGERS firmware (flash mm without GPT and bootloader) and then try to upgrade? I haven't been able to find a RETUS 7.0 firmware anywhere yet so I assume that's what you mean...
Click to expand...
Click to collapse
Yeah.
Because the only other fix I can think of is basically flashing the entire firmware including GPT and bootloader via RSD. But that requires firmware that's made exactly for that device and bootloader just to make sure everything is fine.
I'm still crossing my fingers in the hopes that your Z will make it through.
D13H4RD2L1V3 said:
Yeah.
Because the only other fix I can think of is basically flashing the entire firmware including GPT and bootloader via RSD. But that requires firmware that's made exactly for that device and bootloader just to make sure everything is fine.
I'm still crossing my fingers in the hopes that your Z will make it through.
Click to expand...
Click to collapse
Well... to be honest the only reason I wasn't planning on rooting or using a custom ROM was because of the whole not working with android pay/wells fargo deal. If Magisk will help with that then that's definitely an option as well... Especially right now considering that I can't get ANYTHING to work if i can root, install a stock ROM and use magisk to hide the safetynet I'm totally fine with that as well. Any ideas?
SixShots said:
Well... to be honest the only reason I wasn't planning on rooting or using a custom ROM was because of the whole not working with android pay/wells fargo deal. If Magisk will help with that then that's definitely an option as well... Especially right now considering that I can't get ANYTHING to work if i can root, install a stock ROM and use magisk to hide the safetynet I'm totally fine with that as well. Any ideas?
Click to expand...
Click to collapse
Well, to even get Magisk and root to work, you need a working firmware.
The fact that your device showed the cyan Moto screen means that the firmware is recognized, and how your PC recognizes the phone means that something is indeed working.
But somehow, it's not displaying anything.
Sadly, the best piece of advice I can give right now is to try to flash a full firmware, especially one that was made for your device just to be safe. Motorola support probably won't be of much help since your warranty is void, though some did have success in the past, but I'd say that you might not get too much from them.
dm-verity is a pain, so I don't understand why it's not disabled when the bootloader is unlocked.
D13H4RD2L1V3 said:
Well, to even get Magisk and root to work, you need a working firmware.
The fact that your device showed the cyan Moto screen means that the firmware is recognized, and how your PC recognizes the phone means that something is indeed working.
But somehow, it's not displaying anything.
Sadly, the best piece of advice I can give right now is to try to flash a full firmware, especially one that was made for your device just to be safe. Motorola support probably won't be of much help since your warranty is void, though some did have success in the past, but I'd say that you might not get too much from them.
dm-verity is a pain, so I don't understand why it's not disabled when the bootloader is unlocked.
Click to expand...
Click to collapse
So right now my best course of action is to start with the MM firmware and work my way forward either way. Can I root/install stock 7.0 ROM/magisk from the MM firmware even if I'm keeping the 7.0 gpt and bootloader?
SixShots said:
So right now my best course of action is to start with the MM firmware and work my way forward either way. Can I root/install stock 7.0 ROM/magisk from the MM firmware even if I'm keeping the 7.0 gpt and bootloader?
Click to expand...
Click to collapse
Well, here's the problem.
If you're on the 7.0 GPT and bootloader, you're out-of-luck. Because Moto has changed the rules on those to not accept Marshmallow-based firmware. Trying to flash a MM firmware will result in failure. Trying to downgrade the bootloader may cause your device to be F.U.B.A.R.
If you're still on the MM bootloader, just use the steps outlined earlier in the thread to flash N and then use the instructions and threads I linked to flash both the custom kernel and root access. If everything goes well, your Z should come back to life with those sweet-sweet notification shade goodness.
Hey guys.
My WIFI suddenly stopped working along with Bluetooth and no rom fixed it. So I tried flashing the modem of the Oreo OTA and I wiped the modemst1 by accident...
Long story short, WIFI/Bluetooth can't be enabled and even though the phone recognizes the SIM card, there's no signal and I can't make calls/send or receive messages ( the IMEI is 0 ).
I've tried going back to stock but the issue persisted.
I've heard that other SD820 phones used QPST but the Moto Z can't use the Diag Port so that one fell into the water.
Can anyone help me?
I just need to restore the baseband, even if it's from someone else's Z, and I can change the IMEI back to mine after restoring if the IMEI even gets duplicated.
EDIT
Fastboot getvar all showed that my IMEI is still present but I can't get it to appear in the OS...
The Marionette said:
Hey guys.
My WIFI suddenly stopped working along with Bluetooth and no rom fixed it. So I tried flashing the modem of the Oreo OTA and I wiped the modemst1 by accident...
Long story short, WIFI/Bluetooth can't be enabled and even though the phone recognizes the SIM card, there's no signal and I can't make calls/send or receive messages ( the IMEI is 0 ).
I've tried going back to stock but the issue persisted.
I've heard that other SD820 phones used QPST but the Moto Z can't use the Diag Port so that one fell into the water.
Can anyone help me?
I just need to restore the baseband, even if it's from someone else's Z, and I can change the IMEI back to mine after restoring if the IMEI even gets duplicated.
EDIT
Fastboot getvar all showed that my IMEI is still present but I can't get it to appear in the OS...
Click to expand...
Click to collapse
I don't thinking wiping modemst1 has to do with anything. I'd recommend you flash stock Oreo from here
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
It should fix your problem.
I was on stock 7.1.1 with stock Oreo bootloader and had imei 0. But after flashing back to Oreo, I had my imei back. If it doesn't work, unlock bootloader and flash custom kernel. I recommend ElementalX Kernel 3.0.0 for stock OREO. Good luck.
hypafly said:
I don't thinking wiping modemst1 has to do with anything. I'd recommend you flash stock Oreo from here
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
It should fix your problem.
I was on stock 7.1.1 with stock Oreo bootloader and had imei 0. But after flashing back to Oreo, I had my imei back. If it doesn't work, unlock bootloader and flash custom kernel. I recommend ElementalX Kernel 3.0.0 for stock OREO. Good luck.
Click to expand...
Click to collapse
The sad part is that I was on my AEX build and after I came back from college, everything was working untill the phone discharded and shut down. After a full charge, wifi was gone. Then I flashed the modem and some other parts on top of aex which caused the disappearance of the IMEI.
I did try flashing that exact firmware and nothing changed besides my baseband returning. The only guess I can make is to possibly try going to pure stock and relocking the bootloader ( other Moto phones actually got fixed that way )...
The Marionette said:
The sad part is that I was on my AEX build and after I came back from college, everything was working untill the phone discharded and shut down. After a full charge, wifi was gone. Then I flashed the modem and some other parts on top of aex which caused the disappearance of the IMEI.
I did try flashing that exact firmware and nothing changed besides my baseband returning. The only guess I can make is to possibly try going to pure stock and relocking the bootloader ( other Moto phones actually got fixed that way )...
Click to expand...
Click to collapse
I don't think it's possible to relock the bootloader. Have you tried full flash using the official firmware I recommended? Flashing some parts of it will not fix anything for you. Try full flash having it in mind that all your data will be lost.
hypafly said:
I don't think it's possible to relock the bootloader. Have you tried full flash using the official firmware I recommended? Flashing some parts of it will not fix anything for you. Try full flash having it in mind that all your data will be lost.
Click to expand...
Click to collapse
I flashed everything in proper order besides the bootloader ( I already have that version, it would be rejected anyways).
I even tried wiping everything but it was still not helpful.
I have had it with this phone. I spent so much money replacing the battery and the motherboard and it suddenly craps out on me like this.
I've put it up for parts and my Xiaomi Mi 8 SE will arrive next week.
No more Motorola for me, a flagship phone shouldn't have this ****ty situations happening, especially when I didn't touch anything to begin with ( if I modified something myself, I would be okay with it, but this time it seriously died on its own ) .
The Marionette said:
I flashed everything in proper order besides the bootloader ( I already have that version, it would be rejected anyways).
I even tried wiping everything but it was still not helpful.
I have had it with this phone. I spent so much money replacing the battery and the motherboard and it suddenly craps out on me like this.
I've put it up for parts and my Xiaomi Mi 8 SE will arrive next week.
No more Motorola for me, a flagship phone shouldn't have this ****ty situations happening, especially when I didn't touch anything to begin with ( if I modified something myself, I would be okay with it, but this time it seriously died on its own ) .
Click to expand...
Click to collapse
So sorry to hear this.
My Moto Z has the WiFi bug too. But Bluetooth works though. It's very annoying because I've tried various fixes and different custom roms which didn't fix the problem. Maybe it's hardware? I wouldn't know. But I'm managing it for now until I get another phone.
The Marionette said:
I flashed everything in proper order besides the bootloader ( I already have that version, it would be rejected anyways).
I even tried wiping everything but it was still not helpful.
I have had it with this phone. I spent so much money replacing the battery and the motherboard and it suddenly craps out on me like this.
I've put it up for parts and my Xiaomi Mi 8 SE will arrive next week.
No more Motorola for me, a flagship phone shouldn't have this ****ty situations happening, especially when I didn't touch anything to begin with ( if I modified something myself, I would be okay with it, but this time it seriously died on its own ) .
Click to expand...
Click to collapse
try to flash this, that is my modem.bin file, i don't know what partitions is, but i did with this command "dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.bin", maybe can help you
here is the file: https://drive.google.com/file/d/18GGL9EAIM_fq8OCSOqsy8tsUcH9ipw1-/view?usp=sharing
---------- Post added at 11:59 PM ---------- Previous post was at 11:55 PM ----------
other possible solutions is this:
How to Fix EFS over ADB
Setup ADB and Fastboot on your PC.
Enable Developer options & USB debugging on your Android device.
Connect your device to the PC and open a command window on the PC.
Issue the following commands one by one:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'
adb reboot
How to Fix EFS from Bootloader Mode using Fastboot commands
Setup ADB and Fastboot on your PC.
Enable Developer options & USB debugging on your Android device.
Connect your device to the PC and open a command window on the PC.
Issue the following commands one by one:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
How to Fix EFS from TWRP recovery
Boot into TWRP recovery.
From TWRP’s main screen, selectAdvanced » then Terminal.
Type the following commands in terminal (one by one):
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Reboot device.
Edit: Those using twrp may experience efs restoration issues.
While creating the backup of EFS, you will end up with:
efs1.emmc.win (modemst1 partition raw data)
efs2.emmc.win (modemst2 partition raw data)
When restoring this EFS backup, what happened was the file name was not updated for restore, and you ended up with:
Restoring EFS…
Restoring efs1.emmc.win to modemst1
Restoring efs1.emmc.win to modemst2
It should have been:
Restoring EFS…
Restoring efs1.emmc.win to modemst1
Restoring efs2.emmc.win to modemst2
Twrp issue, the steps above will restore your devices.
Click to expand...
Click to collapse
its from this forum of oneplus https://forums.oneplus.com/threads/restoring-efs.486667/
eLaDiio said:
try to flash this, that is my modem.bin file, i don't know what partitions is, but i did with this command "dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.bin", maybe can help you
here is the file: https://drive.google.com/file/d/18GGL9EAIM_fq8OCSOqsy8tsUcH9ipw1-/view?usp=sharing
---------- Post added at 11:59 PM ---------- Previous post was at 11:55 PM ----------
other possible solutions is this:
its from this forum of oneplus https://forums.oneplus.com/threads/restoring-efs.486667/
Click to expand...
Click to collapse
I appreciate the help but it sadly didn't fix anything. :/
if you have acces to the fastboot commands, could you try to boot into twrp?, cause i have a backup, that can help you i guess
eLaDiio said:
if you have acces to the fastboot commands, could you try to boot into twrp?, cause i have a backup, that can help you i guess
Click to expand...
Click to collapse
I have access to everything, everything besides the wifi, bluetooth and sim functions works.
Mmm very weird, i have a full backup of my phone and sharing you, but i have the doubt if you restore it cause a hardbrick, if you wanna try, i can upload or share the link
eLaDiio said:
Mmm very weird, i have a full backup of my phone and sharing you, but i have the doubt if you restore it cause a hardbrick, if you wanna try, i can upload or share the link
Click to expand...
Click to collapse
I't not a hard brick, the phone boots. Wifi, Bluetooth and SIM functions are the only things that are dead. xD
Sorry, I expressed myself badly, what I wanted to say is that your case is a strange situation, by the way, I have a full backup of my phone and if you want, I can share it so you can try flashing it and see if you can recover the wifi, although I think it could end up in a hard brick so it is risky to try it. Tell me if you're interested in flashing my backup
The presented files for root in the official firmware f800 * Android 9. Based on the official sources PIE of the LG with minimal changes (fixed static boot ).
Only for F800 * phones with unlocked bootloader.
Small manual
LGup firmware in "partition dl" mode KDZ android 9, remove daws aboot, abootbak, laf ( laf must be left from android 7-8).
In Fastboot mode, run boot-twrp.bat (the kernel and TWRP will be flashed).
Go to TWRP: Cleaning - Selective cleaning - select the "ENCRYPTION" swipe ... be sure to before each DATA format .. (This is a feature of this TWRP only), data format, wipe cache and dalvik cache. Reboot TWRP.
Installing Magisk first, then Lg_rctd_disabler as desired. If you need to disable encryption, flash Disable_Dm-Verity_ForceEncrypt_03.04.2020, otherwise you do not need to flash this file. TWRP supports encryption MTP+ADB+OTG .
For F800S only: Before the first system boot, System / Product / Priv-app remove "Findlostphone".
Next, reboot into the OS.
TWRP 3.4.0 : Enable MTP before connecting to PC! , Use the data backup with the previously disabled password lock, pin code, ....
Config TWRP android 9 (us996.zip)
MTP, second screen...OS no problem F800S version (as in android 7-8).
The "fixed static boot" and "us996.zip" files are the source for developers who wish to build their own kernel or TWRP.
Presented as is. any borrowing, modifications and changes are welcome
I need a more detailed explanation
With LGup what exactly to do
And I say exactly
And in the BAT file I get an answer "waiting for the device
I have drivers and it recognizes it
I'm talking about the device F800L
Awaiting quick reply Thanks in advance
LGup for KDZ firmware, for example (F800L30e_00_1022.kdz) for F800L.
BAT file for Fastboot mode of the phone.
Boot-twrp.bat + TWRP.img + boot1.img must be put in the Fastboot folder before starting.
It's very simple if you have experience unlocking the bootloader.
Den4ik111111 said:
LGup for KDZ firmware, for example (F800L30e_00_1022.kdz) for F800L.
BAT file for Fastboot mode of the phone.
Boot-twrp.bat + TWRP.img + boot1.img must be put in the Fastboot folder before starting.
It's very simple if you have experience unlocking the bootloader.
Click to expand...
Click to collapse
I already have the F800L30e installed
And I have the KDZ file
Where do I get the BAT file from?
And I get waiting for device
When I try to play the file
Yes i have drivers
yes i checked it works
This is just for short answers for you
You mean the BAT file that is in the first message Or another file
Because the same file in the first post I tried several times
And it does not work for me
In which folder to run the file In the fastboot folder
Or from the main folder
In the "download mode" you will not succeed. You need to put the phone in "fastboot mode" to write TWRP + boot.
If you do not have "fastboot mode" then the bootloader is blocked. If I understood you correctly, then this is exactly so.
^^^Only for F800 * phones with unlocked bootloader^^^
Den4ik111111 said:
In the "download mode" you will not succeed. You need to put the phone in "fastboot mode" to write TWRP + boot.
View attachment 5223339
If you do not have "fastboot mode" then the bootloader is blocked. If I understood you correctly, then this is exactly so.
^^^Only for F800 * phones with unlocked bootloader^^^
Click to expand...
Click to collapse
1 Yes I have F800L As you can see in the picture
2 This Write download mode That's what I put it on
3 How do I get to "fastboot mode "
Volume down + cable not working
Yes the cable is connected to the computer
Yes the device is turned off
AVIMPEG said:
3 How do I get to "fastboot mode "
Click to expand...
Click to collapse
You need to make DirtySanta Bootloader unlock!
Den4ik111111 said:
You need to make DirtySanta Bootloader unlock!
Click to expand...
Click to collapse
I left everything alone
hi thank you for your effort
Could you enlighten me about the f800l bootloader unlock
I have applied the dirtysanta method to unlock then I root with magisk now I am under pie and root with magisk but when I check the bootloder status it displays locked under nougat and under pie (when updating)
I wonder if the ditysanta method and to bypass restriction of the bootloader to root the mobile or it is a permanent unlock or imissed sme think?
jeddouu said:
hi thank you for your effort
Could you enlighten me about the f800l bootloader unlock
I have applied the dirtysanta method to unlock then I root with magisk now I am under pie and root with magisk but when I check the bootloder status it displays locked under nougat and under pie (when updating)
I wonder if the ditysanta method and to bypass restriction of the bootloader to root the mobile or it is a permanent unlock or imissed sme think?
Click to expand...
Click to collapse
You can ignore it!
The dirtysanta method does not bypass the bootloader.
The bootloader is overwritten by the engineering unlocked from us996 (aboot.img, abootbackup.img).
With the rule ((LGup firmware in "partition dl" mode KDZ, remove daws aboot, abootbak)), there will never be problems when downgrading or upgrading the android version (repeating the "dirtysanta method" will not be needed).
In short, "permanent unlock" with an unlocked bootloader from us996.
Den4ik111111 said:
You can ignore it!
The dirtysanta method does not bypass the bootloader.
The bootloader is overwritten by the engineering unlocked from us996 (aboot.img, abootbackup.img).
With the rule ((LGup firmware in "partition dl" mode KDZ, remove daws aboot, abootbak)), there will never be problems when downgrading or upgrading the android version (repeating the "dirtysanta method" will not be needed).
In short, "permanent unlock" with an unlocked bootloader from us996.
Click to expand...
Click to collapse
thank you very much... in your small manual you did not explain how to use the fixed static boot file because I have this problem thank you in advance for your patience
jeddouu said:
thank you very much... in your small manual you did not explain how to use the fixed static boot file because I have this problem thank you in advance for your patience
Click to expand...
Click to collapse
Added an explanation of the files.
one thing if you allow
it is about mic the caller does not hear me except in free hand I test the mic with app recording it works well I deactivate voice google I resolved by changing some value to mixer_paths. xml but the recording in somme apps like whatsup is very low and not clear in pie and nougat if you have an idea
jeddouu said:
one thing if you allow
it is about mic the caller does not hear me except in free hand I test the mic with app recording it works well I deactivate voice google I resolved by changing some value to mixer_paths. xml but the recording in somme apps like whatsup is very low and not clear in pie and nougat if you have an idea
Click to expand...
Click to collapse
The F800 dialer has a built-in call recording and records well. Google Voice is not needed for this. WhatsApp, like many other messengers, does not have a built-in recording, attempts to record by third-party applications often lead to poor quality (the compression quality plays a big role as the connection quality). Try every possible application, even outdated ones, and you might find the right one.
I can be wrong somewhere, I don’t use call recording.
Den4ik111111 said:
You need to make DirtySanta Bootloader unlock!
Click to expand...
Click to collapse
Does the DirtySanta Bootloader Unlock work for the F800K model? I should have gotten the F800L, but I ended up with the F800K which seems to have little mention anywhere.
.
DonChino said:
Does the DirtySanta Bootloader Unlock work for the F800K model? I should have gotten the F800L, but I ended up with the F800K which seems to have little mention anywhere.
Click to expand...
Click to collapse
Yes.
Hi im on f800l with pie have you a kernel for software Version 30h? Thanks
TarAntonio said:
Hi im on f800l with pie have you a kernel for software Version 30h? Thanks
Click to expand...
Click to collapse
The official kernel sources for Android 9 (LGF800L_LGF800K_LGF800S_Android_Pie_v20a) were released in a single version, without updates. PIE 30h, 30e must be compatible with the kernel. This kernel was posted by me on another resource more than a year ago, here recently. So far no one has spoken about the incompatibility of the kernel with the "30h" firmware. Otherwise it would have been indicated.
Den4ik111111 said:
The official kernel sources for Android 9 (LGF800L_LGF800K_LGF800S_Android_Pie_v20a) were released in a single version, without updates. PIE 30h, 30e must be compatible with the kernel. This kernel was posted by me on another resource more than a year ago, here recently. So far no one has spoken about the incompatibility of the kernel with the "30h" firmware. Otherwise it would have been indicated.
Click to expand...
Click to collapse
Have you a link for download only the pie kernel?
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
Hello! Thx for posting this info. I have a few of questions. Can you post a simple set of instructions on how to apply this root? I have never rooted a Nubia device before but I want to root this. Will the flashing of the boot image require the bootloader unlock? Might you know if the viper4Android is working from the modules install in magisk? Thx in advance for any info you may be able to provide!
RngrYogi said:
Hello! Thx for posting this info. I have a few of questions. Can you post a simple set of instructions on how to apply this root? I have never rooted a Nubia device before but I want to root this. Will the flashing of the boot image require the bootloader unlock? Might you know if the viper4Android is working from the modules install in magisk? Thx in advance for any info you may be able to provide!
Click to expand...
Click to collapse
Also using your method would it require a user data wipe?
RngrYogi said:
Also using your method would it require a user data wipe?
Click to expand...
Click to collapse
yes, of course. it's like any standard boot loader unlocked. Which is why you do it first thing when you get the device.
Edit: I didn't see the question how to apply it -
just OEM unlock the device, and then
adb reboot bootloader
(wait for it too boot to boot loader)
fastboot flashing unlock
(accept unlocking voiding warranty, etc by pressing volume down and power)
fastboot flash boot <the boot.img>
Note that they don't recognize "fastboot boot" , which is my favorite way of rooting since it leaves the original image intact - and thus flashing is irreversible unless you get the stock OTA at a later time and flash it over. But this will not bring back the warranty and warnings.
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
greetings bro thanks for sharing the vbmeta.img file? didn't you use it?
few questions:
1. were did you find the stock firmware to pull the clean boot.img? Can you link it, I would like to have a backup if anything goes wrong
2. Is the patched boot.img for the North American Version?
So to lpedrot: Didn't need a vbmeta.
To superrama: Since it's the kernel, the CN/US/etc versions don't matter. That's handled at a much higher level of Android build, which is user mode. So same boot.img can be used anywhere (which btw is true in all cases - boot.img s only have kernel + Ramdisk anyway)
1. I found the original by looking for NX679 OTA . It was a rather large OTA payload.bin, which I used my imjtool to unpack the boot.img from. Don't have the link handy now, but I can probably dig up the payload.bin and put it in a link since I have it stored somewhere.
morpheus______ said:
So to lpedrot: Didn't need a vbmeta.
To superrama: Since it's the kernel, the CN/US/etc versions don't matter. That's handled at a much higher level of Android build, which is user mode. So same boot.img can be used anywhere (which btw is true in all cases - boot.img s only have kernel + Ramdisk anyway)
1. I found the original by looking for NX679 OTA . It was a rather large OTA payload.bin, which I used my imjtool to unpack the boot.img from. Don't have the link handy now, but I can probably dig up the payload.bin and put it in a link since I have it stored somewhere.
Click to expand...
Click to collapse
nice, thanks for the quick reply
morpheus______ said:
Hi everyone,
Got my RedMagic 7 today. Rooting was straightforward with Magisk 23. I have the patched boot.img in the Android Device Database - http://NewAndroidBook.com/ddb - in case anyone wants. Apparently, "Fastboot boot ..." won't be recognized, so you'd need "fastboot flash" of this image.
(Note that rooting voids warranty, etc, and also might interfere with fingerprint scanner and/or TrustZone applets)
Click to expand...
Click to collapse
On which rom you use it? Aparently its taken out from a Ianuary rom, latest being v2.32 afaik
Just whichever random firmware image I found. But you're overlooking one major thing which is - the kernel barely, if at all, changes between firmware versions . You can use this book image with any other firmware image of any date, earlier or later, and there's no reason why it wouldn't work. The Android OTA images are user mode, this is just the kernel + Ramdisk - and so are largely independent of each other. Only exception would be if there's some kernel vulnerability in that particular version of the kernel, which as far as we know now - there isn't.
Hi, thanks for the guide. I did the steps to unlock bootloader and do flash your provided boot.img.
They both worked successfully but not sure if the boot img did anything.
I have the chinese phone and I want to convert it to global. Going to the settings and choosing the local update file provided by the official website doesn't work.
Any tips?
LeonFresh said:
Hi, thanks for the guide. I did the steps to unlock bootloader and do flash your provided boot.img.
They both worked successfully but not sure if the boot img did anything.
I have the chinese phone and I want to convert it to global. Going to the settings and choosing the local update file provided by the official website doesn't work.
Any tips?
Click to expand...
Click to collapse
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
D1stRU3T0R said:
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
Click to expand...
Click to collapse
Rooting != Image locale change. To do an image locale change you need to get the device image for whichever locale you want (if you can find it) and then apply the usual Magisk method.
D1stRU3T0R said:
”we” have a telegram channel for RM7 users, join since most of them don't use XDA anymore and you'll get faster help here
Click to expand...
Click to collapse
Hi I just joined the TG but got banned any chance of unbanning me?
User is Indiana_Gems on TG I'm looking to change my RM7 CN to global
morpheus______ said:
Rooting != Image locale change. To do an image locale change you need to get the device image for whichever locale you want (if you can find it) and then apply the usual Magisk method.
Click to expand...
Click to collapse
Thanks, I thought the two was related. I can't find any of the img files, which is why I'm stuck I guess. For older versions of the phone like Red Magic 5 they exist.
If they don't exist, is there a process to make one? Or do I have to wait
LeonFresh said:
Thanks, I thought the two was related. I can't find any of the img files, which is why I'm stuck I guess. For older versions of the phone like Red Magic 5 they exist.
If they don't exist, is there a process to make one? Or do I have to wait
Click to expand...
Click to collapse
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
morpheus______ said:
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
Click to expand...
Click to collapse
morpheus______ said:
There is a long and painful process to make one, and it's not guaranteed to work. I'll explain:
If a given vendor (in our case, Nubia, but this applies to others as well) adheres to Google's specification their /system partition should effectively be identical to that of all other Android devices (of same version). The vendor is supposed to put the BSP or ODM specific files in /system_ext, /vendor, /product and /odm.
The language, in this case, is just a locale setting, and several other "overlay" files (which supersede those in /system) laid out in the vendor/odm/product partitions. The problem here is that all these partitions will A) differ by vendor B) be read/only and DM-verity enabled.
Thus, it would take going over the vendor's overlay files and locale settings, and changing every one. Impractical.
You're better off just going in the language settings and setting en_US, and working from there. Even on non-rooted device, you can always adb install any app you want.
Click to expand...
Click to collapse
Thanks for the details!
Is it impractical in terms of technical perspective , or is it just tedious to do? And do you think it will be released in future?
The reason I want to switch is that there are bugs mostly related to the google assistant. It resetting my settings like on default voice assistant app. It doesn't have ok google detection, sometimes doesn't open at all.
If that can be fixed maybe I can stay on CN rom, but honestly there's a lot of random bugs, it not only resets default apps for assistant but other apps too like fluid navigation gestures (FNG) app.
LeonFresh said:
Thanks for the details!
Is it impractical in terms of technical perspective , or is it just tedious to do? And do you think it will be released in future?
The reason I want to switch is that there are bugs mostly related to the google assistant. It resetting my settings like on default voice assistant app. It doesn't have ok google detection, sometimes doesn't open at all.
If that can be fixed maybe I can stay on CN rom, but honestly there's a lot of random bugs, it not only resets default apps for assistant but other apps too like fluid navigation gestures (FNG) app.
Click to expand...
Click to collapse
Hello. Have you found a solution to the problem? I also do not flash, says the version for the firmware is not suitable.
Morrovoker said:
Hello. Have you found a solution to the problem? I also do not flash, says the version for the firmware is not suitable.
Click to expand...
Click to collapse
Not yet, I guess we just have to wait
LeonFresh said:
Not yet, I guess we just have to wait
Click to expand...
Click to collapse
any news yet i wanna switch from global to cn lol
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.