IMEI=0 - Moto G4 Plus Questions & Answers

My moto g4 plus (XT1643) imei =0 after flashing the stock 8.1 android.
I execute the command fastboot gervar imei . It return the imei
I checked the persist partition there is no such file
Dhob.bin
Shob.bin
Id_00
Id_01

Maybe too late to reply but flashing latest official rom is the only solution.
Either use fastboot method or use TWRP flashable official roms,

Related

[XT1643]Problem relocking bootloader

I am unable to lock my bootloader for XT1643. I ended up getting here because I did the following:
> Purchased a Moto G4 plus (XT1643)
> Manually updated to official Nougat(Soak Test).
> Unlocked the bootloader.
> Flashed twrp recovery
> Flashed supersu2.78.zip
> Because it gave me a bootloop so I flashed 6.0.1 firmware(24.139-13) for XT1641. This took away my network and wifi connectivity
> Installed modem from original firmware (24.139-64) for XT1643. Got back radios on my device.
Now when I try to flash the complete 24.139-64 firmware, I get an error when flashing boot.img and recovery.img saying that it is not signed/verified and that downgrading is not possible(or something on those lines). So I have flashed the system.img from the firmware and have baseband of 24.139-64 now.
I believe I need to downgrade from the 7.0 boot.img and also be able to lock my bootloader before I can root my device, or install the soak test again, or both. Please guide me how do I go about doing this. This XT1643 is my primary phone.
Edit: I found the -63 baseband file, flashed it, boot.img and recovery.img flashing still failed but I have got -63 baseband now.
bro did u find any solution? please share me. Thanks
bro did u find any solution? please share me. Thanks
slyfth said:
I am unable to lock my bootloader for XT1643. I ended up getting here because I did the following:
> Purchased a Moto G4 plus (XT1643)
> Manually updated to official Nougat(Soak Test).
> Unlocked the bootloader.
> Flashed twrp recovery
> Flashed supersu2.78.zip
> Because it gave me a bootloop so I flashed 6.0.1 firmware(24.139-13) for XT1641. This took away my network and wifi connectivity
> Installed modem from original firmware (24.139-64) for XT1643. Got back radios on my device.
Now when I try to flash the complete 24.139-64 firmware, I get an error when flashing boot.img and recovery.img saying that it is not signed/verified and that downgrading is not possible(or something on those lines). So I have flashed the system.img from the firmware and have baseband of 24.139-64 now.
bro did u find any solution? please share me. Thanks
I believe I need to downgrade from the 7.0 boot.img and also be able to lock my bootloader before I can root my device, or install the soak test again, or both. Please guide me how do I go about doing this. This XT1643 is my primary phone.
Edit: I found the -63 baseband file, flashed it, boot.img and recovery.img flashing still failed but I have got -63 baseband now.
Click to expand...
Click to collapse
slyfth said:
I am unable to lock my bootloader for XT1643. I ended up getting here because I did the following:
> Purchased a Moto G4 plus (XT1643)
> Manually updated to official Nougat(Soak Test).
> Unlocked the bootloader.
> Flashed twrp recovery
> Flashed supersu2.78.zip
> Because it gave me a bootloop so I flashed 6.0.1 firmware(24.139-13) for XT1641. This took away my network and wifi connectivity
> Installed modem from original firmware (24.139-64) for XT1643. Got back radios on my device.
Now when I try to flash the complete 24.139-64 firmware, I get an error when flashing boot.img and recovery.img saying that it is not signed/verified and that downgrading is not possible(or something on those lines). So I have flashed the system.img from the firmware and have baseband of 24.139-64 now.
I believe I need to downgrade from the 7.0 boot.img and also be able to lock my bootloader before I can root my device, or install the soak test again, or both. Please guide me how do I go about doing this. This XT1643 is my primary phone.
Edit: I found the -63 baseband file, flashed it, boot.img and recovery.img flashing still failed but I have got -63 baseband now.
Click to expand...
Click to collapse
Can I ask how you're flashing your MM firmware? You might have to use adb and fastboot to get a reliable transfer.
I'd also try flashing this ROM using these steps (for XT1643) as I've had good luck with it, even though I'm on an XT1642
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
The steps appear similar to downgrading your phone from Nougat to MM: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961

Urgent Need for Moto G4 Plus scatter file.

If anyone has rooted Moto G4 Plus then please send me the scatter file or partition table. I have bricked my phone and my partition should be made new. Only fastboot is working. ADB is not working. I should flash by Flash Tool so i need a scatter file or from Moto Auto Flash Tool v8.2 By Jamesjerss.
Thank you well in advance.
Please do at the earliest.
tavikmacwin said:
If anyone has rooted Moto G4 Plus then please send me the scatter file or partition table. I have bricked my phone and my partition should be made new. Only fastboot is working. ADB is not working. I should flash by Flash Tool so i need a scatter file or from Moto Auto Flash Tool v8.2 By Jamesjerss.
Thank you well in advance.
Please do at the earliest.
Click to expand...
Click to collapse
Afaik scatter is only needed for mtk chipsets and its flash tool ?
In moto G4/plus, we have gpt.bin and it is partition table for us.
If fastboot is working, then use guide linked below for proper flashing.
First check that you have downloaded latest firmware (installing downgraded firmware and taking OTA update will brick your device again)
This is latest firmware and procedure (note to don't use lock command if you don't want to relock bootloader, read there correctly) : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

Finger print and IMEI. not working after flashing stock rom

Hello,
I have unlocked the bootloader and installed rescurriaion remix rom. Then I decided to install stock rom.I have installed the wrong rom and my device got hard bricked using' BLANKFLASH MG4P' I flashed a dummy bootloader then I installed 'NPJ25_93_14_18 APRIL 01 Patch rom 'for my indian varient xt1643...
The problem is Now the imei and finger print sensor is not working at all...and my moto g4 plus is showing as moto g4.
I have booted TWRP recovry and flashed the below files
1. Fsg.img
2. Modem.img
3. Hw.img
As i have refered the below link
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
While this procedure the hw.img cannot be flashed in twrp mode....while flashing this file the twrp get struck and the adb command stops in 100% ....then nothing happends to adb command...then the error appers
The error is
"adb: error: failed to copy 'hw.img' to '/dev/block/mmcblk0p43"
What can I do...?? Plzz help me...is there any valid hw.img file for my moto g4 plus....plz help me...

cant flash nougat stock rom

when try to attempt the commands to flash such as
fastboot flash partition gpt.bin and all of the next commands are failed
i had twrp recovery and lineage 14.1 and before flashing stock rom i even wiped the custom rom before flashing stock rom
please help i think i bricked my device when install the custom rom again my imei shows 0
:crying:
If you tried to flash nougat from command line, you wiped your imei as part of that process. Look up the "imei = 0" thread to restore it.

Moto G5 Plus on bootloop - would like a stable Android 10 experience

Hi all,
I have a Moto G5 Plus (dual sim, European version) that was on stock Android 8. I wanted to revive this old phone and use it for experimenting.
I unlocked the bootloader, installed TWRP recovery and then installed the unofficial Lineage OS 17.1 (here from xda: [ROM][UNOFFICIAL][10.0][POTTER] LineageOS 17.1).
I then proceeded to get root installed using no-verity and magisk.
I now have a boot loop that loads Lineage but then restarts into TWRP recovery.
It's been a really long time since I fooled around with bootloaders, recoveries and alternative roms (been using a Samsung S8 for several years now on stock rom).
So I am unsure how to proceed. What do you recommend that I do?
I would like to have a rooted Android 10 on the Moto G5 Plus, preferably without a bootloop
Update 1:
Using this thread I have been able to revert to stock Android 8.1 ROM: https://forum.xda-developers.com/showthread.php?t=2542219
But I would be interested to know which Android 10 ROM would be recommended for the Moto G5 Plus?
PartisanEntity said:
Hi all,
I have a Moto G5 Plus (dual sim, European version) that was on stock Android 8. I wanted to revive this old phone and use it for experimenting.
I unlocked the bootloader, installed TWRP recovery and then installed the unofficial Lineage OS 17.1 (here from xda: [ROM][UNOFFICIAL][10.0][POTTER] LineageOS 17.1).
I then proceeded to get root installed using no-verity and magisk.
I now have a boot loop that loads Lineage but then restarts into TWRP recovery.
It's been a really long time since I fooled around with bootloaders, recoveries and alternative roms (been using a Samsung S8 for several years now on stock rom).
So I am unsure how to proceed. What do you recommend that I do?
I would like to have a rooted Android 10 on the Moto G5 Plus, preferably without a bootloop
Update 1:
Using this thread I have been able to revert to stock Android 8.1 ROM: https://forum.xda-developers.com/showthread.php?t=2542219
But I would be interested to know which Android 10 ROM would be recommended for the Moto G5 Plus?
Click to expand...
Click to collapse
Problem; the procedure you followed is for a Moto G, and not a G5 Plus. If you used Moto G firmware on your Moto G5+, you may have induced more problems.
Moto g5+ firmwares are located at https://mirrors.lolinet.com/firmware/moto/potter/official/ Proper firmware for the Moto G5+ depends on your model and what country you are operating in.
potter - Moto G5 Plus = firmware
XT1680(LATAM/Argentina/Chile,2GB) {LATAM; Latin America}
XT1681(LATAM/Colombia/Mexico,2GB)
XT1683(Brazil,DS,DTV,2GB)
XT1684(Europe,3GB)
XT1685(Australia/NewZealand/Europe,3GB)
XT1686(India,3/4GB)
XT1687(USA,2GB/4GB)
{AMX, America Movil Mexico}{owns Claro}
{ATTMX; AT&T Mexico}
{AMZ; Amazon)
{RETAPAC; Retail Pacific; Australia, New Zealand}
{RETAR; Retail Argentina}
{RETBR; Retail Brazil}
{RETEU; Retail European Union)
{RETGB; Retail Great Britian}
{RETIN; Retail India}
{RETLA; Retail Latin America}
{RETMX; Retail Mexico}
{RETUS; Retail Unitied States}
{TEF, Telefonica S A.}
{TEFBR; Telefonica Brazil}
{TEFCO; Telefonica Columbia}
{TEFES; Telefonica European Sector}
{TEFMX; Telefonica Mexico}
Since your in Europe, your firmware group is probally RETEU, RETGB, or TEFES. You need to locate your model number of the phone, maybe a XT1684 or XT1685 and find the model number under the proper directory of firmware. I would download the latest, usually has 8.1.0_OPS28.85-17-6-2 in the firmware name and the lastest date. Extract the software and fastboot it.
For the 8.10_OPS28.85-17-6-2 firmwares the fastboot commands are:
Fastboot flash partition gpt.bin
Fastboot flash bootloader bootloader.img
Fastboot flash modem NON-HLOS.bin
Fastboot flash fsg fsg.mbn
Fastboot flash dsp adspso.bin
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 oem oem.img
Fastboot erase cache
Fastboot erase userdata
Fastboot erase DDR
Fastboot reboot
Again, this may not work because if the Moto G firmware you flashed on to the Moto G5+.....
Also, did LineageOS work on the phone before flashing Magisk and/or no-verity ?
Hi, thank you for your help.
Yes Lineage OS did work. Was it Magisk or no-verity that caused the bootloop?
So, I went to the proper stock ROM, and then I installed the Pixel Experience: https://download.pixelexperience.org/potter - so far nice and stable.
What is the commended/cleanest/safest way to get root?
PartisanEntity said:
Hi, thank you for your help.
Yes Lineage OS did work. Was it Magisk or no-verity that caused the bootloop?
So, I went to the proper stock ROM, and then I installed the Pixel Experience: https://download.pixelexperience.org/potter - so far nice and stable.
What is the commended/cleanest/safest way to get root?
Click to expand...
Click to collapse
Sorry to not reply earlier - was tied up with election recounts -----
Do not know what caused the boot loop. The proper way to install is to install LineagrOS first, boot LineageOS and make sure it comes up, Then go back to recovery/TWRP and install Magisk and the reboot to system and check LineageOS to make sure it came up. Then look in your apps and see if you have the Magisk icon. On the no-verity, I had a couple that did not work, I was turned on to Disable_Dm-Verity_ForcedEncrypt_02.04.2019.zip at
https://androidfilehost.com/?fid=11410963190603877244 (by WolfCity - thanks)
which worked for me. Use the procedure at paragraph 13 (my procedure that I listed
a PDF, its at http://s000.tinyupload.com/?file_id=...86655137330218 ) to install the program to decrypt the file system. Then reboot the phone and verify the phone is un-encrypted (it will say "Encrypt Phone" instead of Phone Encrypted). Then you will have to reboot back to recovery and reinstall Magisk again (its because when the file system was decrypted the memory was formatted/overwrited). Then boot back to system and verify Magisk is in your icons again. If you have Magisk, you should have root. You can verify root by either programs that check it root or open a terminal window and type in SU and Magisk will pop up a window asking if you want to give the program root access.
Hope that helped.

Categories

Resources