Database Users

Moto G4 Plus (XT1641) Android Nougat 7.0 Softbricked after installing SuperSu

I was trying to root my Moto G4 Plus (XT1641) (Dual SIM bought in Wallmart, Mexico), installed the superuser-zip file, but it never loaded. Heres the deatiled info:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.03
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: (**********)
(bootloader) cid: 0x0032
(bootloader) channelid: 0x22
(bootloader) uid: B129A00000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354116070814435
(bootloader) meid:
(bootloader) date: 05-21-2016
(bootloader) sku: XT1641
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Apr 14 10:46:36 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: 25.93-14/16:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.16.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62R ATHENE_LATAM_DSD
(bootloader) version-baseband[1]: S_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-g478d03a (hudsoncm
(bootloader) kernel.version[1]: @ilclbld26) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Jan 6 05:12:56 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.03-0-ge433b40
(bootloader) rpm.git: git=a970ead
(bootloader) tz.git: git=119e5b2-dirty
(bootloader) hyp.git: git=119e5b2-dirty
(bootloader) keymaster.git: git=119e5b2-dirty
(bootloader) cmnlib.git: git=119e5b2-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.03-0-gb44c0ee
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retmx
all: listed above
finished. total time: 0.102s
-First, i had to get the unlock bootloader code from Motorola following the steps on the website
(1) https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
(2) https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
(3) https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-c
And it was the result:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock (******************)
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) invalid boot state
OKAY [ 0.006s]
finished. total time: 0.007s
but, as it said in the las section, my device appears to succesfuly unlocked bootloader:
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
- Following the next post https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 i installled Minimal ADB and Fastboot on my pc, and flashed twrp-3.1.0-0-athene.img. BUT, I DIDN´T NOTICE THE WARNING ON TOP OF THE POST: "If you are on NPJ25.93-11/12/14 (non-soak test Nougat), you MUST flash the ElementalX kernel (link) after step 4. Make sure to backup the stock kernel before proceeding". (and honestly i have no f****** idea if i was on NPJ25.93-11/12/14). I finished installing that post's phh's SuperUser, and Voila!, it didn't worked
-After loking for any solutions to this issue, i've found this post: https://forum.xda-developers.com/moto-g4/how-to/how-to-root-g4-fix-bootable-attempted-t3417592 and tried rooting and tried typing echo SYSTEMLESS=true>>/data/.supersu on the TWRP's terminal and using it's SuperSU file.
-Also: I forgot to make an Backup on TWRP :crying: before installing my first superuser file
I can acces bootloader on my cellphone and TWRP witouth problem, so it's softbricked.
1: How can i finish rooting my device and make ti work? or
2: Is there any way i could reinstall the OS (nougat or Lollipop) using any recovery file, re-stock, re-lock or something?

Okay, a few things from what I see from your post:
You're on NPJ25.93-14/16 (from your getvar infor fingerprint), so that build requires ElementalX or another custom kernel. I think that requirement stands for any Nougat build on Moto G4 devices anyway, since Google appears to have enforced kernel security under Nougat.
Regardless, you'll need to flash a custom kernel to get any root solution (or somehow bypass dm-verity), else you won't be able to boot. You may be able to copy ElementalX (https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836) to a SD card, or use the 'adb push' commands from your adb terminal to push the file onto your device.
Then, you may be able to boot into TWRP, flash the ElementalX kernel, wipe your cache/Dalvik then reboot.
If your device boots, then you may wish to check if phh Superuser is still active.
If no root is present, reboot into TWRP and then flash phh Superuser.
If you still get bootloops or are unable to get ElementalX onto your device, you may wish to flash the stock Nougat ROM (same build as what you have currently) from here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 This will wipe TWRP and any root present (as your kernel and recovery will be stock again), you do not have to re-lock your bootloader if you choose not to, and if you do not use 'fastboot erase userdata' and the OEM lock commands, you may be able to retain your data (though hopefully someone else can chime in on this point). However, for a stable system, I'd recommend using all the erase commands as listed (which potentially means losing your data)
EDIT - from toppits' post here (https://forum.xda-developers.com/showpost.php?p=71461568&postcount=64), you may be able to use these commands for the fastboot ROM (may save your data if you choose to re-flash the fastboot stock ROM):
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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
As always, you may have to erase your data if your system becomes unstable, but hopefully you may be able to boot and recover your data. You may then wish to continue on with your system as is or, after backing up your data, fully wipe and re-flash to get a stable system.

Should I bother upgrading from MM?

I'm on Pure Nexus, and I'm contemplating whether or not to even bother with this NPH25.200-22 update.
I'm looking for a good, stable, custom ROM that's themeable.

abense said:
I'm on Pure Nexus, and I'm contemplating whether or not to even bother with this NPH25.200-22 update.
I'm looking for a good, stable, custom ROM that's themeable.
Click to expand...
Click to collapse
I'd go with aicp or dirty unicorns personally. I think these roms are definitely worth the upgrade and they're both extremely stable. AICP has a thread here on xda. Called the Android Ice Cold Project...and dirty unicorns has a website and g+ page.

Okay, I decided to do this:
Moto X Pure Factory Firmware Nougat NPH25.200-22
Here's my batch commands (I removed the line where it erase's user data)
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
And then I downloaded the latest TWRP, 3.2.1.0
Code:
adb reboot bootloader
fastboot flash recovery twrp-3.2.1-0-clark.img
fastboot reboot recovery
Performing a backup of everything onto my ext-sdcard.
Going with AICP, just like I did 2 years ago when I first got this thing.
installing this version: aicp_clark_n-12.1-NIGHTLY-20171213.zip
And open_gapps-arm64-7.1-nano-20171216.zip
Here goes...

SuperSU from here
http://www.supersu.com/download
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip

abense said:
SuperSU from here
http://www.supersu.com/download
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
Click to expand...
Click to collapse
I'd go magisk, it's so simple to flash, and passes safety net easily, it's such a Breeze, and definitely the way to go rather than superSU!

So, it appears that I need to flash the MM radios?? I'm not getting LTE
Oh I already regret this.

abense said:
So, it appears that I need to flash the MM radios?? I'm not getting LTE
Oh I already regret this.
Click to expand...
Click to collapse
Probably best to flash the stock Nougat image via fastboot first, verify operation, then TWRP and root/ROM.

What's the part about bricking if I upgrade/downgrade modem firmware?

Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.52
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 32GB Samsung REV=07 PRV=02 TYPE=57 PNM=BWBD3R
(bootloader) ram[0]: 3072MB Samsung S8 SDRAM DIE=6Gb M5=x1 M6=x5 M7=x0 M
(bootloader) ram[1]: 8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA394xxxxx
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: xxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 10-29-2015
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 30 21:11:20 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:7.0/NPH
(bootloader) ro.build.fingerprint[1]: 25.200-22/21:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.11.22.clark_retus
(bootloader) ro.build.version.full[1]: .retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not available>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-ge617f58 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT T
(bootloader) kernel.version[3]: ue Aug 29 00:53:54 CDT 2017
(bootloader) sbl1.git: git=MBM-NG-VA0.52-0-g17b2538
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=2d08904-dirty
(bootloader) hyp.git: git=2d08904-dirty
(bootloader) sdi.git: git=d9f358f
(bootloader) pmic.git: git=MBM-NG-VA0.52-0-g17b2538
(bootloader) aboot.git: git=MBM-NG-VA0.52-0-g69ca042
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (142)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.016s

abense said:
What's the part about bricking if I upgrade/downgrade modem firmware?
Click to expand...
Click to collapse
That's not the problem... the "bricking" issue is if you are on Nougat, then downgrade the ENTIRE device to Marshmallow, then take the Nougat OTA update again, this will cause a hard brick. Simply flashing the modems does not cause a problem with bricking.

acejavelin said:
Probably best to flash the stock Nougat image via fastboot first, verify operation, then TWRP and root/ROM.
Click to expand...
Click to collapse
acejavelin said:
That's not the problem... the "bricking" issue is if you are on Nougat, then downgrade the ENTIRE device to Marshmallow, then take the Nougat OTA update again, this will cause a hard brick. Simply flashing the modems does not cause a problem with bricking.
Click to expand...
Click to collapse
Gotcha.
Do you have any insight as to this problem? I ran a getvar all that you suggested in another thread.
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.52
(bootloader) product: clark

abense said:
Gotcha.
Do you have any insight as to this problem? I ran a getvar all that you suggested in another thread.
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.52
(bootloader) product: clark
Click to expand...
Click to collapse
Does it work properly stock, before doing anything?

Need to use this
https://forum.xda-developers.com/showpost.php?p=74999345&postcount=1061

What if...?
acejavelin said:
That's not the problem... the "bricking" issue is if you are on Nougat, then downgrade the ENTIRE device to Marshmallow, then take the Nougat OTA update again, this will cause a hard brick. Simply flashing the modems does not cause a problem with bricking.
Click to expand...
Click to collapse
What if I were to manually downgrade to stock Marshmallow and then install the factory image for 7.0 later on?

Bill720 said:
What if I were to manually downgrade to stock Marshmallow and then install the factory image for 7.0 later on?
Click to expand...
Click to collapse
As was said, it involves taking an OTA upgrade, not using a factory image... You're good there.

Moto G4 Plus : CMD : Invalid Boot State

I sold my Moto G4 Plus and actually bought it back from my buddy. In the Bootloader Unlocked message, its reading ID: bad key. I am unable to fastboot flash TWRP, and when i give ANY Bootloader Lock or Unlock commands it reads :
c:\platform-tools>fastboot oem unlock critical
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) invalid boot state
OKAY [ 0.182s]
finished. total time: 0.192s
c:\platform-tools>fastboot oem unlock Unique_key
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) invalid boot state
OKAY [ 0.191s]
finished. total time: 0.198s
When i gave it to my buddy, it was rooted on 6.0 and when i got it back it was on 7.0.
I have a weird felling he ran an OTA and it F*CKED Sh*t up....
Any ideas?
Thanks in advance,
T

slot-count not found, slot-suffixes not found,bootloaer working fine

Hello,
I've recently tried to flash stock recovery to be able to receive update . I had TWRP installed already . But whenever I type fastboot command , I get error like slot-count not found .
And that's not the case . I've tried with flashing bootloader and gpt.bin as well and get the same error ! My bootloader is working fine! Also whenever I try these steps, I end up losing my WiFi/hotspot connectivity !
Here take a look . I get these errror in ADB :
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
C:\Windows\system32\cmd.exe O
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\User
s\MAYUR Desktop\New folder recovery.img"
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
bootloader) slot-suffixes: not found
(bootloader) has-slot recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.529s]
writing 'recovery'..
<bootloader) Image signed with key bad key
OKAY [ 9.668s]
finished. total time: 1.204s
rs\MAYUR\Desktop\New folder\gpt.bin"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition "C:\Use
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
<bootloader) slot-suffixes: not found
(bootloader) has-slot: partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.008s]
writing partition'.
(bootloader) Flashing prinary GPT image..
(bootloader) Flashing backup GPT image...
OKAY [ 9.093s]
finished. total time: 0.106s
C:\Program Files (x86)\Minimal ADB and Fastboot >fastboot flash bootloader "C:\US
ers\MAYUR Desktop\New folder\bootloader.img'
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
bootloader) slot-suffixes: not found
(bootloader) has-slot: bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.124s]
writing 'bootloader'.
(bootloader) validating: bootloader.default.xml
(bootloader will pass: flash:aboot
<bootloader) will pass: flash:tz
(bootloader) will pass: flash: rpm
(bootloader) will pass: flash: hyp
(bootloader will pass: flash: keymaster
(bootloader) will pass: flash:cmnlib
(bootloader will pass: flash sbli
(bootloader) committing: bootloader.default.xml
bootloader> flashing 'emmc_apps boot.mbn' to 'abooty
(bootloader) flashing 'tz.mbn' to 'tz'
<bootloader) flashing rpm.mbn' to rpm'
(bootloader) flashing 'hyp.mbn' to 'hyp'
(bootloader flashing 'keymaster.mbn' to 'keymaster'
bootloader) flashing 'canlib.mbn' to 'canlib'
OKAY [ 0.608s]
(bootloader) flashing 'sbll.mbn' to sbli'
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
(Getvar all) returned this : ?
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
C:\Windows\system32\cmd.exe
C:\Users\MAYUR\Desktop\New folder>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
<bootloader) version: 0.5
(bootloader) version-bootloader: moto-nsm8952-B1.07
bootloader) product: athene 16mp
<bootloader board: athene_16mp
<bootloader) secure yes
<bootloader) hwrey: P2A
<bootloader) radio: 4
<bootloader) storage-type ennc
<bootloader) emnc 16GB SAMSUNG QE13MB RU-08 PU-7 FU-OOOOOOOOOOOOOOOD
<bootloader) ran: 2GB SAMSUNG LP3 DIE=8Gb M501 M6-05 M2=00 M8 -17
(bootloader) cpu MSM8952
(bootloader) serialno: *protected*
<bootloader) cid: Ox0032
<bootloader) channelid: Oxco
(bootloader) uid: 2E2FAAOOOOOOOOOOOOOOOOOOO000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvo id: yes
(bootloader) reason: Volume down key pressed
bootloader> max-download-size: 536870912,
<bootloader) meid:
(bootloader) imei: *protected*
<bootloader) date: 05-31-2016
<bootloader) sku: XT1643
<bootloader) battid: SNN5966A
bootloader> max-sparse-size: 268435456
<bootloader) iccid:
<bootloader) cust_md5:
(bootloader> current-time "'Sat Apr 30 0:19:14 UTC 2016"
(bootloader) ro.build.fingerprint [0]: motorola/athene/athene:2.0/NPJS25.
bootloader) ro.build.fingerprint(1): 93-14-18/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.236.3.athene.reta
bootloader) ro.build.version.full[1]: il.en.US
bootloader) version-baseband: M8952_70030.25.03.62.02R DFLT_FSG
(bootloader) kernel.version [1]: 2526f <hudsoncneilclbld72) (gcc version
<bootloader) ro.build.version.qcon: LA.BR.1.3.6-01210-8926.0
bootloader) kernel.version [0]: Linux version 3.10.84-ge03508d-00131-944,
bootloader) kernel.version [2]: 4.8 (GCC) > 111 SMP PREEMPT Wed Mar 28 06
(bootloader) kernel.version [3]: :58:16 CDT 2018
(bootloader) tz.git: git-69dd24b-dirty
(bootloader) rpm.git: [email protected]
<bootloader) sbl1.git: git-MBM-NG-UB1.07-6-952d1343
(bootloader) hyp.git: git-69dd24b-dirty
(bootloader) cmnlib.git:git-69dd24b-dirty
(bootloader) aboot.git: git-MBM-NG-UB1.07-0-9f9b89ba
bootloader> keymaster-git: git-69dd24b-dirty
(bootloader) ro.carrier: retin
(bootloader) frp-state: no protection (0)
<bootloader> qe: qe 0/1
all: listed above
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
I've read all the related forum but none of them is similar to mine ! They say we've have to blank flash the bootloader . But mines working fine . Do I really need to blank flash or something else would work fine ? If i really need to blank flash , then pls guide me !
Thank you very much in advance !
Have a great day ?
P.S. = sorry if the related thread already exist !

As far as I know, those slot error messages are normal, and are more informational. The message relate to the flashing slots found on A/B partitioned devices (e.g Google pixels and newer device). We don't have that (G4 plus only had the one set of partitions) and so you expect to see that message on our device. For a newer device, fastboot may try to determine which update slot (either A or B) to flash to.
Flashing recovery or boot (kernel, not bootloader) will usually show image signed with bad key if your bootloader is unlocked. That is normal under that condition.
I'm not entirely sure where the idea to blank flash came from - that method is really only to be used if you've corrupted your bootloader and you cannot boot into the bootloader normally. It's a method of last resort and as you've got a working bootloader and GPT, you really have no need of it.
Your getvar looks mostly okay too, the information you have there matches what we expect from the April 2018 firmware. The odd thing is that your baseband is reporting DFLT_FSG rather than the expected ATHENE_INDIA suffix, which may explain the loss of radio. Can I ask if you flashed any other stock firmware before hand? You may wish to have a look through this thread for more information https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-pluss-model-changed-to-g4-lost-t3496912

Sir I've flashed RR, INVICTA,and many other ROMs but... Didn't face this issue before ... I've recently flashed stock firmware provided by @rajatgupta1998 in this thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138/amp/ .. and ended up here !! The thread you provided as reference is an older discussion where he downgraded his bootloader by flashing ROM from different Android version ... But I've done nothing like that ! Please help me how to het the radio working ! Thanks in advance sir !

echo92 said:
As far as I know, those slot error messages are normal, and are more informational. The message relate to the flashing slots found on A/B partitioned devices (e.g Google pixels and newer device). We don't have that (G4 plus only had the one set of partitions) and so you expect to see that message on our device. For a newer device, fastboot may try to determine which update slot (either A or B) to flash to.
Flashing recovery or boot (kernel, not bootloader) will usually show image signed with bad key if your bootloader is unlocked. That is normal under that condition.
I'm not entirely sure where the idea to blank flash came from - that method is really only to be used if you've corrupted your bootloader and you cannot boot into the bootloader normally. It's a method of last resort and as you've got a working bootloader and GPT, you really have no need of it.
Your getvar looks mostly okay too, the information you have there matches what we expect from the April 2018 firmware. The odd thing is that your baseband is reporting DFLT_FSG rather than the expected ATHENE_INDIA suffix, which may explain the loss of radio. Can I ask if you flashed any other stock firmware before hand? You may wish to have a look through this thread for more information https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-pluss-model-changed-to-g4-lost-t3496912
Click to expand...
Click to collapse
Hello ! I've tried to flash dsp,bootloader,and modem
In adb in twrp .. but my device doesn't detect when I type adb devices in TWRP ! Elsewhere it detects my device ... Be it when I do this while my device is on or in fasboot mode.... could you pls help me with that !!??
Without the radio it's nothing more than a iPod ... Sorry if didn't follow the steps mentioned correctly... pls help me with that ... I'd be very much thankful !
Waiting for your reply ??

Vs1607 said:
Hello ! I've tried to flash dsp,bootloader,and modem
In adb in twrp .. but my device doesn't detect when I type adb devices in TWRP ! Elsewhere it detects my device ... Be it when I do this while my device is on or in fasboot mode.... could you pls help me with that !!??
Without the radio it's nothing more than a iPod ... Sorry if didn't follow the steps mentioned correctly... pls help me with that ... I'd be very much thankful !
Waiting for your reply
Click to expand...
Click to collapse
Does your computer detect your device when you connect via USB whilst booted in TWRP (does your device appear in Device Manager if you're using Windows?) and what version of TWRP are you using? What version of fastboot/ADB do you have installed on your computer?
I'm not that familiar with helping to losing baseband - that's why I referred you to that thread - though it's old and perhaps not exactly what happened to your device, there may be some useful information as to fixing your device.

Can not find STOCK ROM for HTC U Ultra

Yesterday I wanted to flash LineageOS for my HTC Ultra. I used the ROM for 17.1 provided by tarkzim. Everything worked untill I tried to flash the unofficial GApps.
This put me in a bootloop and so to solve this problem I continued to flash LineageOS 16 with the official GApps. This worked fine! At least I thought.
After playing around with some apps, I noticed a lot of bugs and after a while I decided I wanted to flash back the original ROM.
However, I can not find the original ROM for the HTC U Ultra anywhere on the internet. The links that I did found, had outdated download links which do not work anymore. The ROM I am looking for has to be for the htc_oceauhl. I got the output below from the fastboot getvar all command.
Code:
(bootloader) kernel: lk
(bootloader) product: htc_oceuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno:
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 355166080417934
(bootloader) version-main: 2.21.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZF10000
(bootloader) cid: HTC__034
I hope someone can help me to install back the original ROM on my HTC U Ultra. I expect it is just flashing it through TWRP again?
If it is, that brings me to another problem:
Everytime I flash TWRP and start it up, my computer can not access the files on it. It will just keep loading. This mean I can not copy any files to my phone from my pc. Also abd sideload will not work.
However, it is possible to copy files when I install the TWRP by tarkzim at: https://forum.xda-developers.com/u-ultra/development/rom-lineageos-17-0-t3970921.
Can anyone help me through the process of flashing back the stock ROM? I am kinda stuck right now :/

here u r
https://androidfilehost.com/?fid=4349826312261625152