I went back to stock Nougat from Oreo and didn't flash the GPT or Bootloader. I have the IMEI 0 issue. No Unknown baseband though. Clearly shows that mine is an Indian Retail device (ATHENE_INDIA_DSDS_CUST). IMEI SV is 11 for both SIMS.. I flashed the stock firmware (correct one) from rajat's thread (didn't flash GPT or Bootloader since it would have hard bricked my phone). What step should I take to fix the IMEI? I checked IMEI in fastboot. It's intact. No issues with FP sensor either.
Downloaded firmware from: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Device ID: XT1643 G4 Plus, 3/32GB variant
Edit: Used Heath's flash file to do this instead.
Related
Hello,
I´ve had b170 on my GRA-L09, but after updating to b191, it ended in bootloop, so I flshed back system.img from b170 with fastboot followed by boot.img from b170, now my P8 boots, but baseband and IMEI is unknown in settings, only with *#06# it shows IMEI.
what can I do, to get baseband and IMEI in settings back, to use my Simcard?
should I reflash recovery? because somehow I can´t get to recovery, to wipe cache.
even flashing an update out of update-app ends in bootloop, maybe because of defect recovery
good news, after flashing recovery via fastboot, I was able to do a full flash and get baseband and IMEI back
raider2k9 said:
good news, after flashing recovery via fastboot, I was able to do a full flash and get baseband and IMEI back
Click to expand...
Click to collapse
Hi, I have B200 and same problems: IMEI e BASEBAND.
Can You explain what have you did? I've reflash recovery.img (extracted from b200.zip), but I still have IMEI e BASEBAND unknown.
Please Help me!
My moto g4 plus stopped recognizing my sim card and IMEI code is blank after flashing stock rom
You flashed the wrong stock ROM image, download the right one with the correct sku-no + build-no and flash again.
OK going to try that
My friend flashed this firmware "POTTER_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" on his potter and now experiencing unknown baseband in bootloader and 0 imei's.
please guide me to fix it.
My device was using Oxygen OS Pie official version OTA 43 and the I got the notification for OTA 46 update.
Having an unlocked bootloader and TWRP codeworkx recovery 3.2.3-0, I removed the compatiblity.zip from the OTA, like the other times I did, and tried to flash it, which resulted into a failure. But after rebooting to bootloader and flashing the original oneplus recovery image, I tried to flash the zip again. Which also failed. I have no root, or modifications done to the system. However upon reboot I got the unlocked bootloader warning but nothing else showed up. I couldn't access the recovery nor the bootloader. Fastboot or ADB was unable to detect any device. So I was stuck with a Hard Brick.
After that I downloaded cheeseburger_23_O.13_170803 MsmDownloadTool 4.0 from the unbrick thread and followed the instructions. It completed successfully and I have stock Oneplus 5 on Oxygen OS 4.5.8 and Android 7.1.1 however system update was available to Oxygen OS 5.1.4 and I tried to install it, which failed. I unlocked the bootloader, installed twrp official 3.2.3 and tried again, which also failed with E3005: exit code 7
I tried flashing codeworkx recovery but it results into a black screen at the recovery and a continuous blue light at the LED — like when it was when Hard bricked. I don't understand what to do anymore. Also Bootloader has changed:
Product Name: QC_reference_Phone
Variant : MSM UFS
Bootloader Version: (it is blank)
Baseband Version: (also blank)
Serial Number: (present, same as what it used to be)
Secure Boot: yes
Device State : Unlocked
Did I miss something while Unbricking?
EDIT:
I don't know if something was wrong with my bootloader or unbricking, but I fixed the issue by using an updated version of unbrick tool from: Here
Some information is till missing from the bootloader screen ie. baseband version and bootloader version, but I could update to latest OTA at least.
Kj1594 said:
My device was using Oxygen OS Pie official version OTA 43 and the I got the notification for OTA 46 update.
Having an unlocked bootloader and TWRP codeworkx recovery 3.2.3-0, I removed the compatiblity.zip from the OTA, like the other times I did, and tried to flash it, which resulted into a failure. But after rebooting to bootloader and flashing the original oneplus recovery image, I tried to flash the zip again. Which also failed. I have no root, or modifications done to the system. However upon reboot I got the unlocked bootloader warning but nothing else showed up. I couldn't access the recovery nor the bootloader. Fastboot or ADB was unable to detect any device. So I was stuck with a Hard Brick.
After that I downloaded cheeseburger_23_O.13_170803 MsmDownloadTool 4.0 from the unbrick thread and followed the instructions. It completed successfully and I have stock Oneplus 5 on Oxygen OS 4.5.8 and Android 7.1.1 however system update was available to Oxygen OS 5.1.4 and I tried to install it, which failed. I unlocked the bootloader, installed twrp official 3.2.3 and tried again, which also failed with E3005: exit code 7
I tried flashing codeworkx recovery but it results into a black screen at the recovery and a continuous blue light at the LED — like when it was when Hard bricked. I don't understand what to do anymore. Also Bootloader has changed:
Product Name: QC_reference_Phone
Variant : MSM UFS
Bootloader Version: (it is blank)
Baseband Version: (also blank)
Serial Number: (present, same as what it used to be)
Secure Boot: yes
Device State : Unlocked
Did I miss something while Unbricking?
EDIT:
I don't know if something was wrong with my bootloader or unbricking, but I fixed the issue by using an updated version of unbrick tool from: Here
Some information is till missing from the bootloader screen ie. baseband version and bootloader version, but I could update to latest OTA at least.
Click to expand...
Click to collapse
try a different recovery like "Oreo" and if doesn't help then use unbrick tool
Himanshu.Shukla said:
try a different recovery like "Oreo" and if doesn't help then use unbrick tool
Click to expand...
Click to collapse
I did try to install codeworkx twrp recovery, for the Oreo build but it was giving me a hard brick, ie. A black screen and a blue LED when trying to boot to recovery. But as I said, using Unbrick tool v4.0.8 I was able to restore to Oxygen Os 5.1.7 and then everything worked fine.
I am just unsure why it didn't work with Oxygen Os 4.5.8
I mean, with a locked bootloader and a freshly installed OS, you should be able to get OTA updates, right? But the system update was failing. So maybe there was something wrong with the partitions? I don't know. The bootloader in the older Unbrick tool was different than stock. Maybe that was a fault, well, I'll never know. But all I'm saying is, newer Unbrick Tool worked wonders for me.
Can't flash firmware for S7 Edge G935V. Error: SW REV CHECK FAIL: Fused 10 > Binary 4
The firmware is G935VVRS4CRI1 (Android 8.0). Current firmwave on my S7 Edge G935V is G935VVRUACSH1.
I use Odin v3.13.1 to flash and meet this error:
SW REV CHECK FAIL: Fused 10 > Binary 4
How do I fix it? Thank you!
i get the same thing unsure of what to do
duchoa1995 said:
The firmware is G935VVRS4CRI1 (Android 8.0). Current firmwave on my S7 Edge G935V is G935VVRUACSH1.
I use Odin v3.13.1 to flash and meet this error:
SW REV CHECK FAIL: Fused 10 > Binary 4
Click to expand...
Click to collapse
You are attempting to flash an old bootloader version over a new bootloader. This message directly means that the e-fuse for a v10 bootloader is trying to be flashed over a v4 bootloader. You can identify the version of bootloader by looking at the fifth digit from the end of the firmware (G935VVRS4CRI1=v4, G935VVRUACSH1=v10). If you want to flash a stock frimware,please ensure that fifth digit from the end matches, as the bootloader version was upgraded early in 2019.
njmcinty said:
You are attempting to flash an old bootloader version over a new bootloader. This message directly means that the e-fuse for a v10 bootloader is trying to be flashed over a v4 bootloader. You can identify the version of bootloader by looking at the fifth digit from the end of the firmware (G935VVRS4CRI1=v4, G935VVRUACSH1=v10). If you want to flash a stock frimware,please ensure that fifth digit from the end matches, as the bootloader version was upgraded early in 2019.
Click to expand...
Click to collapse
Thank you so much. This will be helpful! :good:
duchoa1995 said:
The firmware is G935VVRS4CRI1 (Android 8.0). Current firmwave on my S7 Edge G935V is G935VVRUACSH1.
I use Odin v3.13.1 to flash and meet this error:
SW REV CHECK FAIL: Fused 10 > Binary 4
How do I fix it? Thank you!
Click to expand...
Click to collapse
Also because your device does not have an unlocked bootloader you are stuck on that firmware it is impossible to downgrade back to nougat. I have tried with every piece of firmware that exists for this variant and it is totally a 100% fused to at least V8. Now I'm on the absolute latest firmware which is V10. Luckily the Eng boot image for V8 still works on V10. But until they use the same bootloader on this firmware you will not be able to downgrade. However it is not looking very good that they will use the same one. Generally that only happens in some cases with the first firmware revision to the new Android version. In the case of g930p, there was no such instance. Basically your phone is the same phone is mine the only thing that differs is the carrier.
DragonFire1024 said:
Also because your device does not have an unlocked bootloader you are stuck on that firmware it is impossible to downgrade back to nougat. I have tried with every piece of firmware that exists for this variant and it is totally a 100% fused to at least V8. Now I'm on the absolute latest firmware which is V10. Luckily the Eng boot image for V8 still works on V10. But until they use the same bootloader on this firmware you will not be able to downgrade. However it is not looking very good that they will use the same one. Generally that only happens in some cases with the first firmware revision to the new Android version. In the case of g930p, there was no such instance. Basically your phone is the same phone is mine the only thing that differs is the carrier.
Click to expand...
Click to collapse
Actually I try all ways I can find to fix the "camera failed" error, but it's still not working now. So if I downgrade my phone to previous firmwares (as V10, V9, V8...), can I maybe fix it?