Database Users

imei repair and baseband unknown!! (need help??)

i have g900i
i was on note 7 based rom
after some day of use'my imei is null
baseband unknown
no network signal!!
any help will be appritiatble!!

nikhil_setia03 said:
i have g900i
i was on note 7 based rom
after some day of use'my imei is null
baseband unknown
no network signal!!
any help will be appritiatble!!
Click to expand...
Click to collapse
I just copy what I wrote in another thread (First and second Post):
MysteryIII said:
If you don't have a proper Backup you need to use NV Writer to write IMEI to EFS Partition yourself. Everything about it here.
Read everything careful, it's an immersive action! If you tried everything exactly like described in this thread and it still doesn't work (some kind of connect or R/W error) than you have a fully corrupted EFS Partition. To fix this you need to flash working PIT file for your device and than write IMEI again.
It sounds easy as I write it, but it took me a whole while to find out the trick and you must be extremely careful.
Click to expand...
Click to collapse
MysteryIII said:
Link for NV Reader/Writer is working. You can get latest drivers here. If you have KIES/Smart Switch installed you already have necessary drivers. But make sure any process of KIES/Smart Switch is terminated!
Also check if drivers are installed correctly after connecting device and setting it to RMNET Mode or Download Mode. For me drivers for RMNET weren't installed automatically, so I needed to install drivers manually in Device Manager.
At first I flashed only PIT file than PIT file together with ROM just to be sure. Than it worked and I could write IMEI to "new" EFS partition. I added my own PIT file, you can try if it helps (SM-G900F 16GB).
Here is another tutorial.
Click to expand...
Click to collapse

MysteryIII said:
I just copy what I wrote in another thread (First and second Post):
Click to expand...
Click to collapse
Links not working. Please can you give to the proper links or a walk through of how to fix this issue? My s5 has been broken for 6 months because of this....First i had baseband null then i flashed something and now whenever i turn on my phone it says enter sim unlock code.it was a globally unlocked phone from the beginning. Please help me.

Seems like links in quote broke, but if you go to original posts (linked) they still work.
However I uploaded files I have:
EFS Professional (NV Reader/Writer is integrated in this powerful tool)
NV-Items Reader/Writer
RMNET Driver for S5 (probably need to be installed manually with Device Manager in Windows)
http://www8.zippyshare.com/v/7PT0oMuc/file.html
NV Generator
Official Driver Installer
And here is the link to the alternative method.
€: Links removed. All tools that edit an IMEI are banned here due to legal issues in many countries.

MysteryIII said:
I just copy what I wrote in another thread (First and second Post):
Click to expand...
Click to collapse
i have g900i
u have g900f
is there any problem or procedure is same!!!

MysteryIII said:
Seems like links in quote broke, but if you go to original posts (linked) they still work.
However I uploaded files I have:
EFS Professional (NV Reader/Writer is integrated in this powerful tool)
NV-Items Reader/Writer
RMNET Driver for S5 (probably need to be installed manually with Device Manager in Windows)
http://www8.zippyshare.com/v/7PT0oMuc/file.html
NV Generator
Official Driver Installer
And here is the link to the alternative method.
€: Links removed. All tools that edit an IMEI are banned here due to legal issues in many countries.
Click to expand...
Click to collapse
Brother i have downloaded everything but can't do it properly. The nv writer doesn't detect my phone but the rmnet drivers are installed. Can you please give me some detailed instructions? I can't use a sim in my s5. It has been broken for the last 2 months..

Probably whole partition corrupt (at least this was my problem). In second post I wrote that flashing PIT file fixed it for me.
Somebody else made a new thread to for this question and here is another way to fix it.

MysteryIII said:
Probably whole partition corrupt (at least this was my problem). In second post I wrote that flashing PIT file fixed it for me.
Somebody else made a new thread to for this question and here is another way to fix it.
Click to expand...
Click to collapse
Brother my problem is that at 1st i lost my baseband but after flashing a file through Odin i fixed it but now when i turn on my phone it shows sim locked need unlock code. I bought my phone unlocked. It's a globally unlocked g900f.. Please can you tell me how i can fix it?

Hbk6699 said:
Brother my problem is that at 1st i lost my baseband but after flashing a file through Odin i fixed it but now when i turn on my phone it shows sim locked need unlock code. I bought my phone unlocked. It's a globally unlocked g900f.. Please can you tell me how i can fix it?
Click to expand...
Click to collapse
I'm really sorry, but never had an issue like that. I don't really know if it helps, but try to downgrade to Kitkat ROM and flash compatible pit file + rewrite IMEI. I don't really know if it helps, but as I read along this forum it seems Kitkat ROM is less restrictive.

Need blank flash for my moto g4 play

Hi guys ! I hope you'll be able to help me.
i restored my Moto G4 play to 6.0.1
Then, i updated it to 6.0.1 and after it installed the phone is no longer powering up, even plugged in USB. My computer is recognizing it as QHSUSB_bulk.
I installed a driver for it to ne recognized as a qualcomm com port.
I know that my bootloader is broken so i need a blank flash image to "reinstall" it
Can someone in this forum help me ?
My model is XT1603.
Thanks in advance !

please be aware that the partitions the op is requesting contain personal, sensitive data, like your google password, and imei, which can not be deleted with a standard recovery wipe. It is not recommended anyone who does no understand what information any partition backup contains, refrain from responding, for your own protection. with the collective partitions the op is requesting, they can have a 100% duplicate of your device, including your personal information.

You and developer if and it does not seem what I am losing is not files containing personal data to before answering question search first what is hardbrick

The file that I am requesting the file and the file of the motorola that released for moto g1 and the one to recover cell from the hardbrick

i fixed my xt1601 with this file
i am trying to post a link
blob:https:// mega.nz/ afae4b98 -8c17 -4f33 -8c3e -d334855e7dfa
i have tried lots of blank flashes and this one worked for my XT1601
remove all the spaces from link

jmak2008 said:
i am trying to post a link
blob:https:// mega.nz/ afae4b98 -8c17 -4f33 -8c3e -d334855e7dfa
i have tried lots of blank flashes and this one worked for my XT1601
remove all the spaces from link
Click to expand...
Click to collapse
do you have the blankflash ?, the link is not working

no imei no network no finger print sensor working...xt1643

i flashed stock rom https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
and now i have no network and my finger print sensor is not working...
then i flashed the 23.1 build
https://drive.google.com/file/d/0B6R99CgoFhmKQUVMVWE4ckEyRms/view
still its not working.
someone please help me.

jayeshaupe90 said:
i flashed stock rom https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
and now i have no network and my finger print sensor is not working...
then i flashed the 23.1 build
https://drive.google.com/file/d/0B6R99CgoFhmKQUVMVWE4ckEyRms/view
still its not working.
someone please help me.
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
Try this

blackbeats said:
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
try this
Click to expand...
Click to collapse
u had the same problem?

jayeshaupe90 said:
u had the same problem?
Click to expand...
Click to collapse
nope but i have read threads most suggested to updat to nougat modem and device specific framework

jayeshaupe90 said:
u had the same problem?
Click to expand...
Click to collapse
i am not able to flash .
I does not detect my phone
model: Usb imei not showing
and when i click on start it says failed gpt.bin something

jayeshaupe90 said:
i am not able to flash .
I does not detect my phone
model: Usb imei not showing
and when i click on start it says failed gpt.bin something
Click to expand...
Click to collapse
“Failed gpt.bin” something doesn't help us, or you.
Tell us the exact errors shown. We'll be then able to help you out to the best of our ability.
From my knowledge, you cannot flash a gpt partition file of an older ROM. You should, as Blackbeats mentioned, flash only the modem partition from the correct ROM for your device.

@jayeshaupe90
I think your phone became G4 (not plus !! )...
This happened because of flashing wrong firmware.. and this has no solution till now...
Check this [ https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-pluss-model-changed-to-g4-lost-t3496912 ]
If this happened (your phone became G4) then we cannot do anything to help you, otherwise correct me...
PS. Anyhow someone found solution for network.. read on second page of that thread..

zeomal said:
“Failed gpt.bin” something doesn't help us, or you.
Tell us the exact errors shown. We'll be then able to help you out to the best of our ability.
From my knowledge, you cannot flash a gpt partition file of an older ROM. You should, as Blackbeats mentioned, flash only the modem partition from the correct ROM for your device.
Click to expand...
Click to collapse
as an experimental idea flash twrp then a custom rom then the modem file and see if it detects
PS then jtaging is the last option

jayeshaupe90 said:
i am not able to flash .
I does not detect my phone
model: Usb imei not showing
and when i click on start it says failed gpt.bin something
Click to expand...
Click to collapse
one more casualty, sorry I'm out of tears over my own dead set!
others are also trying, maybe different path to hell, but same result: https://forum.xda-developers.com/moto-g4-plus/help/diag-mode-g4-qpsd-t3591683/page3

BlackBeats said:
as an experimental idea flash twrp then a custom rom then the modem file and see if it detects
PS then jtaging is the last option
Click to expand...
Click to collapse
no success

jayeshaupe90 said:
no success
Click to expand...
Click to collapse
Then jtag it go to the nearest repair shop and get the software restored

BlackBeats said:
Then jtag it go to the nearest repair shop and get the software restored
Click to expand...
Click to collapse
if jtag is what i understand it to be is handing it over to Moto-the-BI*** repair shop, he can't.
his bootloader is unlocked so they are basically going to replace the board which is 80% of phone price.

MK+2017 said:
if jtag is what i understand it to be is handing it over to Moto-the-BI*** repair shop, he can't.
his bootloader is unlocked so they are basically going to replace the board which is 80% of phone price.
Click to expand...
Click to collapse
Try some unauthorized shop local shop

There seems to be a lot of lost IMEIs in the G4 Plus Community, I and a few others have narrowed it down to NV Data corruption, which needs a flash box or a new logic board AFAIK. Good luck mate!

[Solved] Exploring LG G4 Root-Injection, exFAT, VoLTE issue ... H81210n Rogers/Fido

*See the Addendum at the bottom of this OP for The Solve*
This thread has arisen from a particular issue that was originally thought to have arisen* by flashing a pre-rooted system image that was prepared following the method outlined by Senior Member hackarchive in "Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks" (https://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586).
*later proved by Senior Member steadfasterX to be an erroneous assumption.
The issue: The H812 LG G4 (that has an un-lockable bootloader) that came from the carrier (Canada's Roger's/Fido) with Marshmallow (H81220x) installed. It was rolled back to Lollipop H81210h originally with the pre-rooted H81210n system image flashed after - the reason: both the stock and pre-rooted 'h' versions did not have the last stagefright vulnerability patch whereas the 'n' version did, hence an added level of security. However, no one had a confirmed Roger's/Fido stock H81210n kdz (Rogers/Fido is the only carrier in Canada that has the VoLTE option included and operational for the LG G4) that anybody could find a link to and when an exFAT formatted SD card was put in the pre-rooted 'n' version, it failed to recognize the format (no problem with FAT32) whereas it was recognized in the rooted earlier released 'h' version. The 4gb restriction size of FAT32 did not allow the backup of the system image with Senior Member steadfasterX's "TWRP-in-FiSH" (https://forum.xda-developers.com/g4/development/locked-twrpinfish-locked-g4-devices-t3573048) to the external sd card given the FAT32 size restriction. The exFAT recognition issue originally appeared to have arisen with the pre-rooted 'n' version when the missing original stock kdz was installed through the refurbish method with LGUP-NEW without an SD card installed or when the original system image was extracted OR, as steadfasterX has suggested, it was originally for a phone with a different kernel.
At the suggestion of steadfasterX and thanks to his work on this issue, the effort to reverse-engineer and revert to stock from the root-injection method itself has been undertaken. The work is all his, the testing to date and soft-bricking getting to this point, are mine.
Make no mistake ... this is a work-in-progress and soft-bricks and other risks, always a possibility
What you have here is a link to steadfasterX's latest revision to help unravel this issue that should not change anything if the DEBUG setting is left as it is: DEBUG=1. Follow his instructions exactly. I have run this version with DEBUG=1 with absolutely no problems and no issues rebooting after - no actual changes were made to the phone when the DEBUG=1 mode was used.
Note: Changing the 1 to a 0 will allow actual execution of the script and is not advised at this time*.
* Not advised at all as it will = Soft Brick.
Refer to the following link: https://forum.xda-developers.com/showpost.php?p=72837723&postcount=343
but please, post to this thread only if you are interested in helping/testing/solving or have any questions etc.
Thanks.
S.
Addendum: Credit for The Solve ...
Full credit for the solve goes to ReeS86- refer to his post @ReeS86
Special Thanks to all the work by steadfasterX he put into helping us get to this point.
For a quick and easy method to get an exFAT formatted SD card recognized in the pre-rooted Rogers/Fido H81210n system image: see the Addendum in my post @sdembiske

yea thats better here then there
ok lets see where it goes...
happy bricking
.

steadfasterX said:
yea thats better here then there
ok lets see where it goes...
happy bricking .
Click to expand...
Click to collapse
Here's a link to the DEBUG=1 log from revert_root_injection.sh v0.2:
https://paste.omnirom.org/view/be1a8f21
No issues/problems in executing or rebooting from the script in DEBUG=1 mode. :good:

sdembiske said:
Here's a link to the DEBUG=1 log from revert_root_injection.sh v0.2:
https://paste.omnirom.org/view/be1a8f21
No issues/problems in executing or rebooting from the script in DEBUG=1 mode. :good:
Click to expand...
Click to collapse
ok!
so now pls gimme this on your rooted device:
boot in TWRP
Code:
adb shell
mount /system <-- may complain that it is already mounted. if so ignore ;)
tar cvzf /tmp/init.tar.gz /system/etc/init.d/
exit
adb pull /tmp/init.tar.gz .
then e.g. upload the init.tar.gz here as a attachment .
.

steadfasterX said:
ok!
so now pls gimme this on your rooted device:
boot in TWRP
Code:
adb shell
mount /system <-- may complain that it is already mounted. if so ignore ;)
tar cvzf /tmp/init.tar.gz /system/etc/init.d/
exit
adb pull /tmp/init.tar.gz .
then e.g. upload the init.tar.gz here as a attachment ..
Click to expand...
Click to collapse
Here you go.

sdembiske said:
Here you go.
Click to expand...
Click to collapse
ok so far so good.
now it is "safe" to DEBUG=0 ..
give it a try :fingers-crossed:
and upload the log from the ext sd afterwards again..
.

steadfasterX said:
ok so far so good.
now it is "safe" to DEBUG=0 ..
give it a try :fingers-crossed:
and upload the log from the ext sd afterwards again...
Click to expand...
Click to collapse
No go this time either. Softbricked same as last time on the reboot - however, this time TWRP didn't freeze up and allowed the reboot from inside. Pulling the battery and trying normal power up gave the same result. No sound and couldn't get past the spinning lg logo. It'll take me a bit of time to get up and running again.
Here's the link to the log: https://paste.omnirom.org/view/19951ee0

I'm curious what security fixes and other fixes were present between the h and n versions of the Rogers H812 system software. It seems to me a good option may be to install 10h KDZ and then root, then copy any libstagefright files needed from the 10n KDZ and check to see if the vulnerabilities are fixed. I might try this out because I had no issues with the 10h firmware including the exFAT working correctly while rooted.

ReeS86 said:
I'm curious what security fixes and other fixes were present between the h and n versions of the Rogers H812 system software. It seems to me a good option may be to install 10h KDZ and then root, then copy any libstagefright files needed from the 10n KDZ and check to see if the vulnerabilities are fixed. I might try this out because I had no issues with the 10h firmware including the exFAT working correctly while rooted.
Click to expand...
Click to collapse
Good idea. I know some of the stock Motorola LTE versions were updated with the first stagefright vulnerability patch and it was able to be ported over into to copies of stock versions that didn't have it. Refer to the Miscellaneous section in the following thread https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
You may want to check with recognized contributor lost101, author of that thread for any suggestions.
The other approach might be to try and get the Roger's-Fido/VoLTE app/settings off the the 'h' version and see if they can be incorporated into the stock 'n' version that does handle exFAT but doesn't have VoLTE as it is carrier specific, although, I think your approach might bring more fruitful results quicker.

ReeS86 said:
I'm curious what security fixes and other fixes were present between the h and n versions of the Rogers H812 system software. It seems to me a good option may be to install 10h KDZ and then root, then copy any libstagefright files needed from the 10n KDZ and check to see if the vulnerabilities are fixed. I might try this out because I had no issues with the 10h firmware including the exFAT working correctly while rooted.
Click to expand...
Click to collapse
sdembiske said:
Good idea. I know some of the stock Motorola LTE versions were updated with the first stagefright vulnerability patch and it was able to be ported over into to copies of stock versions that didn't have it. Refer to the Miscellaneous section in the following thread https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
You may want to check with recognized contributor lost101, author of that thread for any suggestions.
The other approach might be to try and get the Roger's-Fido/VoLTE app/settings off the the 'h' version and see if they can be incorporated into the stock 'n' version that does handle exFAT but doesn't have VoLTE as it is carrier specific, although, I think your approach might bring more fruitful results quicker.
Click to expand...
Click to collapse
Well my first try on this would be:
Backup v10n
Flash v10H
Restore v10n system image only
See what happens. Normally there are low chances that this brick anything but there are still no guarantees..
Btw I would like to see a DEBUG=1 run on a v10h..
I wonder if there are diffs in the root injection..
.
Sent from my LG-H815 using XDA Labs

All this trouble because no bootloader unlock... what a shame
---------- Post added at 10:27 AM ---------- Previous post was at 10:21 AM ----------
ReeS86 said:
I'm curious what security fixes and other fixes were present between the h and n versions of the Rogers H812 system software. It seems to me a good option may be to install 10h KDZ and then root, then copy any libstagefright files needed from the 10n KDZ and check to see if the vulnerabilities are fixed. I might try this out because I had no issues with the 10h firmware including the exFAT working correctly while rooted.
Click to expand...
Click to collapse
What is the difference between H and N versions?

steadfasterX said:
Well my first try on this would be:
Backup v10n
Flash v10H
Restore v10n system image only
See what happens. Normally there are low chances that this brick anything but there are still no guarantees..
Btw I would like to see a DEBUG=1 run on a v10h..
I wonder if there are diffs in the root injection..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Will try and get to it sometime over the long weekend that we have coming up here and give it a shot as well as providing the DEBUG=1 log on a v10h .
Thanks again.

sdembiske said:
Will try and get to it sometime over the long weekend that we have coming up here and give it a shot as well as providing the DEBUG=1 log on a v10h .
Thanks again.
Click to expand...
Click to collapse
You may could ask the maintainer of :
https://forum.xda-developers.com/g4/development/h815-freedom-rom-t3630056/post72866870
He made an installer for his ROM which let you select VoLTE so he may now what is needed to activate it. I know it's for the h815 but it should be similar..
.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Well my first try on this would be:
Backup v10n
Flash v10H
Restore v10n system image only
See what happens. Normally there are low chances that this brick anything but there are still no guarantees..
Btw I would like to see a DEBUG=1 run on a v10h..
I wonder if there are diffs in the root injection..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
As suggested, here are the revert_root_injection logs (x2 - DEBUG =1 and DEBUG=0), plus the TWRP recovery log of system image restore of the 'n' version from 'h' internal.
Same problem with revert-root-injection when the DEBUG option was set to "0" to execute - i.e., soft brick ... lol.
And, perhaps not unexpected, the exFat formatted card was still not recognized but what did surprise me is that none of my settings, apps etc., were restored on the 'n' system image restore after.
Link to logs: https://gist.github.com/sdembis/89de74e401def3ed0e091c565a19e0e9
I then restored all (excluding system image) from my backup in external after the first restore attempt - it failed on the Data restore but everything was back to normal from what I could tell on the reboot.
PS: I pm'ed both you and ReeS86 the response from the rom author you suggested I contact re: the VoLTE install. He was very helpful and sounds like a good guy. Thanks for the suggestion. Much appreciated.
Best,
S.

sdembiske said:
As suggested, here are the revert_root_injection logs (x2 - DEBUG =1 and DEBUG=0), plus the TWRP recovery log of system image restore of the 'n' version from 'h' internal.
Same problem with revert-root-injection when the DEBUG option was set to "0" to execute - i.e., soft brick ... lol.
And, perhaps not unexpected, the exFat formatted card was still not recognized but what did surprise me is that none of my settings, apps etc., were restored on the 'n' system image restore after.
Link to logs: https://gist.github.com/sdembis/89de74e401def3ed0e091c565a19e0e9
I then restored all (excluding system image) from my backup in external after the first restore attempt - it failed on the Data restore but everything was back to normal from what I could tell on the reboot.
PS: I pm'ed both you and ReeS86 the response from the rom author you suggested I contact re: the VoLTE install. He was very helpful and sounds like a good guy. Thanks for the suggestion. Much appreciated.
Best,
S.
Click to expand...
Click to collapse
Hm the following is not clear for me:
You have restored the system image of N to H as suggested. Ok. And then? Does it soft brick as well?
the recovery log shows the backup only.. But it wouldn't be helpful anyways or do you had an error while restoring?
Yes using the revert script on H was 99% sure that it soft bricks as well that's why I said DEBUG=1 but it seems u like it so.. nvm
Thx to the log It looks like the root method between H and N is not different btw..
.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Hm the following is not clear for me:
You have restored the system image of N to H as suggested. Ok. And then? Does it soft brick as well?
the recovery log shows the backup only.. But it wouldn't be helpful anyways or do you had an error while restoring?
Yes using the revert script on H was 99% sure that it soft bricks as well that's why I said DEBUG=1 but it seems u like it so.. nvm
Thx to the log It looks like the root method between H and N is not different btw..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
No, neither of the restores resulted in a soft brick. The first restore of the 'n' backed up system image (from internal) went fast with no issues but didn't have the apps and settings that I backed up - that is the TWRP log I attached in my last post. The 2nd restore (all except system image from external), done right after the first, failed on restoring Data but I was able to reboot from within TWRP and all settings and apps were back as they should have been.
Here is the link to that log: https://gist.github.com/sdembis/160047faa4b22717edf36658e5e42ea7
Any ideas as to why the reversion is failing and whether it might be able to be overcome?
Thanks again,
S.
.

sdembiske said:
No, neither of the restores resulted in a soft brick. The first restore of the 'n' backed up system image (from internal) went fast with no issues but didn't have the apps and settings that I backed up - that is the TWRP log I attached in my last post. The 2nd restore (all except system image from external), done right after the first, failed on restoring Data but I was able to reboot from within TWRP and all settings and apps were back as they should have been.
Here is the link to that log: https://gist.github.com/sdembis/160047faa4b22717edf36658e5e42ea7
Any ideas as to why the reversion is failing and whether it might be able to be overcome?
Thanks again,
S.
.
Click to expand...
Click to collapse
The idea of restoring the system image (ONLY this!) from N to H :
this was a test to see if you have the VoLTE working afterwards - was VoLTE working?
.

steadfasterX said:
The idea of restoring the system image (ONLY this!) from N to H :
this was a test to see if you have the VoLTE working afterwards - was VoLTE working?.
Click to expand...
Click to collapse
Sorry, I didn't check it because the other problem, namely exFAT was no longer recognized was still present. I'll re-check everything today.

steadfasterX said:
The idea of restoring the system image (ONLY this!) from N to H :
this was a test to see if you have the VoLTE working afterwards - was VoLTE working?.
Click to expand...
Click to collapse
Thinking this through a little - as the rooted Roger's/Fido 'h' version does have VoLTE, I would expect it to have VoLTE when the 'n' version system image with VoLTE is restored over that 'h' version. I am going to try instead taking the 'n' version without VoLTE but recogning exFat that I've rooted and restore the system image from the pre-rooted 'n' version with VoLTE but not recognizing exFat, to see if VoLTE is present. If it is, I suspect that exFAT will still not be recognized as it was with the retored 'n' version over the 'h' version, I would only end up with the same problem I have now with the pre-rooted 'n' version - VoLTE with no exFAT recognition.
Or, did you mean restoring the rooted 'n' version system image without VoLTE over the rooted 'h' version with VoLTE and exFAT recognition?

I was able to loop mount both the bell H812n and Rogers H812n rooted system images and run KDiff3 on both of the root directories. It seems there are a few config files here and there that reference VoLTE as well as the odd missing file between the two. I'm going to keep digging maybe I'll find something about ExFAT as well.
Edit: Looks like the rooted system image posted to the Canadian G4 thread is from Videotron in Quebec. Still don't see anything about ExFAT...

IMEI, Volte and 4G fix ( work started )

It's looking like I am going to need a new motherboard replacement for my IMEI 0 problem + can't call or text.
My mum also has a Moto G5 with everything working and on stock
what I am going to do since I need a motherboard replacement anyway is use the backup and restore App to backup all the partitions from my mums phone and restore them to my phone one by one and hopefully restore atleast 4G, Volte and the ability to use calls and texts as well as Data, if anything goes wrong or gets worse, I need a motherboard replacement anyway ( until I fix this problem by doing this or someone finds a fix that works everytime )

I don't understand why android oreo has to be so destructive for the g5

because is build on 64 bits, and moto g5 has partitions on 32 bits, from here we must start to discover where is the incompatibility

heres a solution to fix missing imei and network

madscientistdam said:
heres a solution to fix missing imei and network
Click to expand...
Click to collapse
i've already tried this method + others
my IMEI remains at 0 and i'm only able to use 3G data ( can't use calls or texts )

woozie.2007 said:
because is build on 64 bits, and moto g5 has partitions on 32 bits, from here we must start to discover where is the incompatibility
Click to expand...
Click to collapse
even then the 8.0 roms only touch the system and boot partition
it never touches the persist, fsc, fsg, DDR, Aboot it doesn't modify those important partitions

Livi-Tech said:
It's looking like I am going to need a new motherboard replacement for my IMEI 0 problem + can't call or text.
My mum also has a Moto G5 with everything working and on stock
what I am going to do since I need a motherboard replacement anyway is use the backup and restore App to backup all the partitions from my mums phone and restore them to my phone one by one and hopefully restore atleast 4G, Volte and the ability to use calls and texts as well as Data, if anything goes wrong or gets worse, I need a motherboard replacement anyway ( until I fix this problem by doing this or someone finds a fix that works everytime )
Click to expand...
Click to collapse
Good start man!! Even I'm trying to copy data from another G5 to test whether 4G works or not.

shad.man92 said:
Good start man!! Even I'm trying to copy data from another G5 to test whether 4G works or not.
Click to expand...
Click to collapse
My phone's bricked
My sister flashed a Moto G3 partition file instead of the Moto G5 partition file

Livi-Tech said:
My phone's bricked
My sister flashed a Moto G3 partition file instead of the Moto G5 partition file
Click to expand...
Click to collapse
Oh dear! ?

Livi-Tech said:
even then the 8.0 roms only touch the system and boot partition
it never touches the persist, fsc, fsg, DDR, Aboot it doesn't modify those important partitions
Click to expand...
Click to collapse
ok, but i understand that some partition will migrate on twrp 64 recovery and do not comeback on 32 bits recovery, somebody said that, i dont remember who, here or on another forum

Livi-Tech said:
My phone's bricked
My sister flashed a Moto G3 partition file instead of the Moto G5 partition file
Click to expand...
Click to collapse
So have you tried flashing the stock rom again with the Correct procedures?

shad.man92 said:
So have you tried flashing the stock rom again with the Correct procedures?
Click to expand...
Click to collapse
I can't boot into download mode
Screen is black with blinking light
get QDLoader 9008 in device manager

Livi-Tech said:
I can't boot into download mode
Screen is black with blinking light
get QDLoader 9008 in device manager
Click to expand...
Click to collapse
You mean to say you can't go to bootloader menu??

shad.man92 said:
You mean to say you can't go to bootloader menu??
Click to expand...
Click to collapse
Dead bootloader. Phone is dead, the only solution is motherboard replacing.

CypherPotato said:
Dead bootloader. Phone is dead, the only solution is motherboard replacing.
Click to expand...
Click to collapse
We have only 3 methods
A blankflash file for Moto G5 - but none have been created or leaked by Motorola
EMMC_prorammer_firehose.mbn file for the Snapdragon 430, patch0.xml and rawprogram.xml files for the G5 gets released or made so we can use QPST - but none available for G5
booting using loader.img from Sdcard - doesn't appear to work

Livi-Tech said:
We have only 3 methods
A blankflash file for Moto G5 - but none have been created or leaked by Motorola
EMMC_prorammer_firehose.mbn file for the Snapdragon 430, patch0.xml and rawprogram.xml files for the G5 gets released or made so we can use QPST - but none available for G5
booting using loader.img from Sdcard - doesn't appear to work
Click to expand...
Click to collapse
Why booting using loader.img from sdcard ins't working?

CypherPotato said:
Why booting using loader.img from sdcard ins't working?
Click to expand...
Click to collapse
It hasn't worked for other users and didn't work for me