Related
I have already unlocked a few Motos, including Moto G4 Play without any problem.
But this time is different.
After my unlock attempt, the phone is not actually unlocked and 'fastboot getvar all' reads out the following:
Code:
fastboot getvar all
(bootloader) version-bootloader: moto-msm8952-B1.03
(bootloader) product: athene_13mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) sku: XT1625
athene:7.0/NPJ25.93-14/16
The phone boots and works ok, but the bootloader is NOT unlocked.
I guess I have to flash bootloader B1.03, 2016-10-21, (0xB103) from stock NPJ25.93-14?
Code:
fastboot flash bootloader bootloader.img
The getvar commands says that the bootloader is unlocked. What makes you think it isn't?
zeomal said:
The getvar commands says that the bootloader is unlocked. What makes you think it isn't?
Click to expand...
Click to collapse
Code:
(bootloader) securestate: flashing_unlocked
On bootloader screen:
Battery OK (Charging)
flashing_unlocked
On all other Motos I have unlocked it was:
Device is UNLOCK. Status Code:3
Regardless, did you try flashing a new recovery? If it works without a hitch, your device is unlocked.
Devices change.
del
zeomal said:
Regardless, did you try flashing a new recovery? If it works without a hitch, your device is unlocked
Click to expand...
Click to collapse
When I boot TWRP and run TWRP's file manager, I do not have access to files, even those on /external_sd.
which TWRP to use?
twrp-3.1.1-0-athene.img
twrp-3.1.1-athene_shreps.img
so you have twrp recovery installed correctly ???.
if yes then try to flash super su or custom rom ( resurrection remix best , i am using )
but take back up first with twrp
Sent from my Moto G4 Plus using Tapatalk
If you can flash and replace stock recovery with TWRP, your device is unlocked. You might want to enable TWRP to allow access to modify the system in the first screen, by flashing TWRP again and selecting that option in the first startup screen.
HI everyone
I have this firmware:
0PK7IMG_HIAU_ML_TUHL_M60_SENSE70_MR_HTC_Europe_2.30.401.1_Radio_1.1550V70.2501.0304_HT[W.T]_release_490382_combined_signed
I have :
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) version-main: 2.30.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711000
(bootloader) cid: HTC__J15
I used this method:
From fastboot you need to first re-lock your bootloader
fastboot oem lock
Once locked it will boot back into bootloader
fastboot oem rebootRUU
Now your booted to the black HTC screen. Make sure your Rom.zip file is in your adb/fastboot folder
fastboot flash zip Rom.zip
and this error :
C:\Users\Usuario Final\Desktop\platform-tools>fastboot flash zip 0PK7IMG.zip
load_file: could not allocate -1806505155 bytes
error: cannot load '0PK7IMG.zip'
this firmware: 0PK7IMG_HIAU_ML_TUHL_M60_SENSE70_MR_HTC_Europe_2.30.401.1_Radio_1.1550V70.2501.0304_HT[W.T]_release_490382_combined_signed has many zip files inside
What other method can I use?
Thanks
Used the latest version of fastboot.
If you install hTC sync manager on your PC, I would recommend to use the htc_fastboot located on
X:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync
Hi guys, I'm new here and I just wanted to know if someone else have had this issue too and knew how to solve it.
Yesterday I was playing pool on my phone when suddenly it turned off. I though the battery was very low but I had barely charged it. When I was trying to turn it on it didn't respond, I connected the charger and noticed that the only thing that was working was the LED and the screen never turned on again, I realized that it was a hardbrick.
I guess the cause was that a few days ago I changed the kernel, I installed Elemental X kernel, but I didn't like how it was working on my device so I restored the backup with the RR ROM I always use and everything was normal until yesterday.
I've been all the last day trying to fix it and I just have got blankflashed. Then I've tried to flash around 6 firmwares from 4 different sites and they all fail throwing me a "FAILED (remote failure)".
I use a zip file as help through adb commands on my laptop and the Fastboot Flash Mode (Secure) on my device.
I don't know what else to do and the problem is unknown for now.
Would it be the bootloader?
Is there a problem if the OEM is locked?
Is the non-existent IMEI interfering?
Am I doing things right?
What else should I do?
PS: It's obvious that I'm desperate and I know that is possible to save it.
Thanks for reading I hope someone answer.
Caney said:
I've been all the last day trying to fix it and I just have got blankflashed. Then I've tried to flash around 6 firmwares from 4 different sites and they all fail throwing me a "FAILED (remote failure)".
Click to expand...
Click to collapse
That's not good, flashing wrong firmware can be dangerous to losing fingerprint and losing IMEI.
Get latest December's patch ROM from link thred and try to flash it. : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
@Caney Have you tried pressing power button and volume down button for approx 10 mins.. this should force reset back into bootloader and go from there. Just make sure they is some charge in the battery but when pressing buttons make sure it's NOT connected to anything else it wont work
The device is in Fastboot Flash Mode (Secure), is it necessary to do that?
Caney said:
The device is in Fastboot Flash Mode (Secure), is it necessary to do that?
Click to expand...
Click to collapse
I'm not too sure what fastboot flash mode (secure) is tbh... Does the led just flash when you try to turn it on? And if you connect to pc it detects it something odd like qloader (I forget the exact name) if so yes. Try it
stehaworth said:
@Caney Have you tried pressing power button and volume down button for approx 10 mins.. this should force reset back into bootloader and go from there. Just make sure they is some charge in the battery but when pressing buttons make sure it's NOT connected to anything else it wont work
Click to expand...
Click to collapse
stehaworth said:
I'm not too sure what fastboot flash mode (secure) is tbh... Does the led just flash when you try to turn it on? And if you connect to pc it detects it something odd like qloader (I forget the exact name) if so yes. Try it
Click to expand...
Click to collapse
Yes, it was like that until I used blankflash and entered to Fastboot Flash Mode (Secure); It's like bootloader menu but instead of an android image you have a green "Start" text.
Caney said:
Yes, it was like that until I used blankflash and entered to Fastboot Flash Mode (Secure); It's like bootloader menu but instead of an android image you have a green "Start" text.
Click to expand...
Click to collapse
Tbh.... I'm not too sure... But I would start at looking into flashing full Moto stock image via fastboot (see other thread for details)
Hey, I think I have lock my bootloader accidentally :'c When I try to put the commands to flash firmware it throws me this:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
error: cannot load 'gpt.bin'
How do I unlock it?
You tried blank-flash too!! That's not good if you try with December's patch.
First, it will make confusion to discuss same thing on different threads, (reported other one)
Now discuss here,
when that green start is shown, type following commands.
To check if your device is connected,
- fastboot devices
To see your phone's information, post result of it.
- fastboot getvar all
C:\Users\hp>fastboot getvar all
(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: b61bc8aa
(bootloader) cid: 0x0032
(bootloader) channelid: 0x23
(bootloader) uid: 57A9A70100000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) aboot.git: git=MBM-NG-VB1.03-0-gb44c0ee
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.291s
@Caney from this data, i can see bootloader version is old, so you can try blank-flash with September's gpt and bootloader.
Follow (link below) thread for it, and where it says about download gpt and Bootloader files, go for September's one (2nd link there)...
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
When you get bootloader (after blank-flash), flash December's update.
____Mdd said:
You tried blank-flash too!! That's not good if you try with December's patch.
First, it will make confusion to discuss same thing on different threads, (reported other one)
Now discuss here,
when that green start is shown, type following commands.
To check if your device is connected,
- fastboot devices
To see your phone's information, post result of it.
- fastboot getvar all
Click to expand...
Click to collapse
Why isn't that good?
Caney said:
Why isn't that good?
Click to expand...
Click to collapse
In December's patch, there is update for bootloader, so when bootloader is updated, we need new blank-flash files for new bootloader, so we currently don't have blank-flash files for December's update...
But yours is B1.03 (in getvar info), which is old, so no need to worry about it. Just do as above i said, try blank-flash with September's gpt and bootloader...
____Mdd said:
In December's patch, there is update for bootloader, so when bootloader is updated, we need new blank-flash files for new bootloader, so we currently don't have blank-flash files for December's update...
But yours is B1.03 (in getvar info), which is old, so no need to worry about it. Just do as above i said, try blank-flash with September's gpt and bootloader...
Click to expand...
Click to collapse
Oooh man, can you please attach the link of that gpt here? I don't find it.
Caney said:
Oooh man, can you please attach the link of that gpt here? I don't find it.
Click to expand...
Click to collapse
GPT and bootloader of the September 2017 stock ROM update (NPJS25.93-14-10) - bootloader version B1:06. https://drive.google.com/open?id=0B-GUyOfb8Ogzc25FdW1WUDBMS1U
GPT and bootloader of the December 2017 stock ROM update (NPJS25.93-14-13) - bootloader version B1:07.
https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80
However, I would caution against just using these files, and suggest that you update fully by flashing the entire stock September or December 2017 ROM. Your bootloader is from the November/December 2016 firmware (B1:03) so just updating your bootloader isn't a good idea, especially when it comes to OTA updates.
Alternatively, if you want to reflash the stock ROM that has the same bootloader version as your reported bootloader, have a look at this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
I decided to download the file from the third link provided. But I don't know if I'm flashing correctly, how do I do it?
Caney said:
I decided to download the file from the third link provided. But I don't know if I'm flashing correctly, how do I do it?
Click to expand...
Click to collapse
Are you following a guide to help you flash?
Generally for any flashing via fastboot (e.g. for stock ROMs or for TWRP)
1)Install the ADB and Motorola drivers as directed by the guide.
1a)Extract the stock ROM zip file (should be about 2 GB in size extracted), copy all the files to your ADB folder (so they're on the same level as your adb.exe and fastboot.exe).
2)Reboot your device to the bootloader (fastboot mode) and connect to your computer via USB. Preferably this should be the same cable as came with your device or another high quality data + power USB cable.
3)Open the ADB terminal on your computer and verify that your device is communicating by typing 'fastboot devices' in the ADB terminal, without quotes. This should return your device's serial number.
4)If so, then proceed with flashing as per the guide's fastboot commands. They are the same as the stock ROMs for Moto G4/Plus devices have followed the same layout (7 sparsechunks for system, for example). If you do not wish to re-lock your bootloader, then do not use the two OEM lock begin or the OEM lock commands. If you wish to try to keep your data, then you can omit fastboot erase userdata. However, with your device in the state it is, it may be worth thinking about a fresh start and erasing your userdata.
For omitting bootloader re-locking and trying to preserve your data (though be aware you may have to wipe anyway, the following fastboot commands should suffice.
Code:
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 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
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
You can either edit a flashing script to mirror these commands and use the script or enter the commands, individually and in order, by copypasting each line into the ADB terminal, then executing. Ideally, you want to see [OKAY] before you proceed. You may see errors about 'Image signed with bad key' if you're actually still unlocked, that's normal.
However, if you see any other errors, such as pre-flash validation or security downgrade, then you will need to use a newer stock ROM. Depending on which blankflash you used, the September 2017 or December 2017 stock ROMs would be suitable candidates.
This is what I was doing but with flash script. If I'm going to flash one of those Dec o Sep, will be necessary to update my bootloader from B1.03 to B1.07 or B1.06?
And another problem, when I open a command window in the fastboot files Windows opens Windows PowerShell instead of adb.
Caney said:
This is what I was doing but with flash script. If I'm going to flash one of those Dec o Sep, will be necessary to update my bootloader from B1.03 to B1.07 or B1.06?
Click to expand...
Click to collapse
After flashing bootloader file from September ROM, your bootloader will be automatiically updated to B1.06 and same apply for December ROM.
But you have used the blank flash file so it is recommended to downloading the June 2017 fastboot ROM and flashing that in fastboot.
Caney said:
And another problem, when I open a command window in the fastboot files Windows opens Windows PowerShell instead of adb.
Click to expand...
Click to collapse
As of Windows PowerShell of WIndows 10 still it doesn't fully supported for all Commands and Features so Its better to use CMD or ADB.
Caney said:
This is what I was doing but with flash script. If I'm going to flash one of those Dec o Sep, will be necessary to update my bootloader from B1.03 to B1.07 or B1.06?
And another problem, when I open a command window in the fastboot files Windows opens Windows PowerShell instead of adb.
Click to expand...
Click to collapse
Then you may wish to try manually flashing each command individually, and in order, ensuring you see [OKAY] before continuing. The script may proceed too quickly to see if it's all worked, so manually flashing is another option. You could always add 'pause' before 'reboot' in the script (without quotes) to let you review the flash before rebooting.
As for Powershell instead of cmd, have a look at this thread: https://forum.xda-developers.com/moto-g4-plus/help/installing-twrp-using-powershell-t3727761/
As for updating bootloaders, I would recommend it - your bootloader is a crucially important piece of firmware and should stay at the same patch level as your system/device firmware. This should reduce the number of complications you may face and also ensure that OTA updates go more smoothly.
Be aware that the B1:06 bootloader in the June 2017 and September 2017 security patches (NPJS25.93-14-8 and NPJS25.93-14-10) close a bootloader vulnerability, which makes downgrading to an older stock ROM even more risky as it appears Motorola does not like you downgrading. Strictly speaking, it's not the act of downgrading, but the act of taking an OTA update whilst downgraded - the mismatch between your newer bootloader patch level and the older stock ROM can hard brick your device should you attempt to install an OTA update.
Furthermore, with the December 2017 stock ROM patch, bootloaders are updated to B1:07, meaning our current latest blankflash is not likely to work (blankflashes older than your current bootloader, corrupted or not, do not appear to be permitted to flash to your bootloader). So be careful when updating and flashing anything to your device if you choose to update to the December 2017 patch.
So i finally flashed my phone but i cant instal any stock rom on it, even before it bricked and i could access twrp all roms i tried said it was corrupted but i had no problem unziping them, right now after i install a stock rom the phone just stays in "unlocked bootloader" screen, my guess is it need latest update stock rom
Lenovo assistant doesnt reconize the phone either
Thanks
lolcos said:
So i finally flashed my phone but i cant instal any stock rom on it, even before it bricked and i could access twrp all roms i tried said it was corrupted but i had no problem unziping them, right now after i install a stock rom the phone just stays in "unlocked bootloader" screen, my guess is it need latest update stock rom
Lenovo assistant doesnt reconize the phone either
Thanks
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
Sent from my ali using XDA Labs
sd_shadow said:
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Where do I run the code?
sd_shadow said:
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-river_retail-0ff2029-200211
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: 0058554416
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 6E52853800000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 07-03-2019
(bootloader) sku: XT1962-4
(bootloader) carrier_sku: XT1962-4
(bootloader) battid: SB18C44558
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Feb 14 5:27:48 UTC 2020"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld158) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Tue Fe
(bootloader) kernel.version[3]: b 11 07:52:22 CST 2020
(bootloader) sbl1.git: MBM-2.1-river_retail-516ad1c-200211
(bootloader) rpm.git: MBM-2.1-river_retail-22daab3-200211
(bootloader) tz.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) devcfg.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) keymaster.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) cmnlib.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) cmnlib64.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) prov.git: MBM-2.1-river_retail-d9613e6-dirty-200211
(bootloader) aboot.git: MBM-2.1-river_retail-0ff2029-200211
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 2
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.376s
Firmware you are looking for is River/RetBR
https://mirrors.lolinet.com/firmware/moto/river/official/RETBR/
See my thread on Flashing Stock
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
You might want to try mfastboot
Flash commands should be like this
add a "m" if using mfastboot
Code:
fastboot getvar max-sparse-size
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
You may need to add
Code:
fastboot erase userdata
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sd_shadow said:
Firmware you are looking for is River/RetBR
https://mirrors.lolinet.com/firmware/moto/river/official/RETBR/
See my thread on Flashing Stock
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
You might want to try mfastboot
Flash commands should be like this
add a "m" if using mfastboot
Code:
fastboot getvar max-sparse-size
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
You may need to add
Code:
fastboot erase userdata
Click to expand...
Click to collapse
Thank you very much, i tried flashing the lates firmware but no succes, i cant follow the tutorials, i used a .bat file i found on the internt, but when it boots it takes me to the bootloader screen. I'm trying to find a bat file for moto g7 river, that might be the case
lolcos said:
Thank you very much, i tried flashing the lates firmware but no succes, i cant follow the tutorials, i used a .bat file i found on the internt, but when it boots it takes me to the bootloader screen. I'm trying to find a bat file for moto g7 river, that might be the case
Click to expand...
Click to collapse
sd_shadow said:
firmware you are looking for is river/retbr
https://mirrors.lolinet.com/firmware/moto/river/official/retbr/
see my thread on flashing stock
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
you might want to try mfastboot
flash commands should be like this
add a "m" if using mfastboot
Code:
fastboot getvar max-sparse-size
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem non-hlos.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth btfm.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase ddr
fastboot flash logo logo.bin
fastboot reboot
you may need to add
Code:
fastboot erase userdata
Click to expand...
Click to collapse
so i finally understood and compiled a .bat file with the latest firmware;.can u has boo
verymuch loco obrigado
sd_shadow said:
Firmware you are looking for is River/RetBR
https://mirrors.lolinet.com/firmware/moto/river/official/RETBR/
See my thread on Flashing Stock
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
You might want to try mfastboot
Flash commands should be like this
add a "m" if using mfastboot
Code:
fastboot getvar max-sparse-size
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
You may need to add
Code:
fastboot erase userdata
Click to expand...
Click to collapse
You helped me so much, how can i relock my bootloader? I cant check "Allow OEM Unlock" on my phone i even tried rooting my phone but still it wont allow me to check the option "Allow OEM Unlock" it says the bootloader is already unlocked, thing is i need to check that so i can relock using mfastboot
lolcos said:
Firmware you are looking for is River/RetBR
https://mirrors.lolinet.com/firmware/moto/river/official/RETBR/
See my thread on Flashing Stock
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
You might want to try mfastboot
Flash commands should be like this
add a "m" if using mfastboot
You may need to add
You helped me so much, how can i relock my bootloader? I cant check "Allow OEM Unlock" on my phone i even tried rooting my phone but still it wont allow me to check the option "Allow OEM Unlock" it says the bootloader is already unlocked, thing is i need to check that so i can relock using mfastboot
Click to expand...
Click to collapse
You don't change allow OEM unlock
That's not the issue
See
https://forum.xda-developers.com/general/rooting-roms/guide-locking-motorola-bootloader-t4079111
Sent from my ali using XDA Labs
*** [LATEST UPDATE, Unresolved] *** Issue Persists after reverting to original ROM and back to latest firmware (all signed, official copies)
I'm [STILL] stuck!
I was part of MFN beta test of android 10, but it would no longer allow me to install OTA updates of latest security patches, so i decided to try re-locking the bootloader, reverting back to stock 9 pie, and going back to OTA updates to get latest 10 Q official stock version...
Now I can't get valid boot image to re-lock bootloader with adb/fastboot!
(bootloader) Image signed with key bad key
(bootloader) Still require signed boot.img
I already tried LMSA rescue/software assistant. It reads device but when trying to rescue, doesn't like to play nice with my modified phone!
* [UPDATE 1]:
* flashed another firmware, now baseband doesn't work, no data/LTE signal good, not reading sim card at all?!
** [UPDATE 2]:
** After reverting back to PPOS29.114-134-14 (9 Pie) >>> now baseband works, LTE signal good, sim card reading again
** BUT STILL unsigned boot image (still void warranty, still can't lock bootloader to use Google Pay)
** Thanks, Huey for link to 10Q version, I'll try it out and post update...
*** [UPDATE 3]:
*** I flashed HueyT's 10 Q Rom (RIVER_QPU30.52-16-2)
*** Phone functioning again with 10 Q (network, baseband,etc all good)
*** BUT STILL unsigned boot image (STILL void warranty, STILL can't lock bootloader to use Google Pay)
*** "(bootloader) Image signed with key bad key"
*** "(bootloader) Still require signed boot.img"
:crying:
natesc0tt said:
I'm stuck!
I was part of MFN beta test of android 10, but it would no longer allow me to install OTA updates of latest security patches, so i decided to try re-locking the bootloader, reverting back to stock 9 pie, and going back to OTA updates to get latest 10 Q official stock version...
Now I can't get valid boot image to work with adb/fastboot!
(bootloader) Image signed with key bad key
(bootloader) Still require signed boot.img
I already tried LMSA rescue/software assistant. It reads device but when trying to rescue, doesn't like to talk to my modified phone!
now baseband not working, no signal, can't read sim card !?!?
Anyone have stock firmware xt1962-1 RETUS 10 Q, RIVER_QPU30.52 ????:crying:
Click to expand...
Click to collapse
Did you use a stock boot.img?
After the message "Still require signed boot.img" flash your boot.img again and run "fastboot oem lock". Then another message should appear like "Still require signed system.img".
---------- Post added at 07:55 PM ---------- Previous post was at 07:40 PM ----------
BTW: You must try to relock the bootloader while having Pie version installed and not beta version.
WoKoschekk said:
Did you use a stock boot.img?
After the message "Still require signed boot.img" flash your boot.img again and run "fastboot oem lock". Then another message should appear like "Still require signed system.img".
---------- Post added at 07:55 PM ---------- Previous post was at 07:40 PM ----------
BTW: You must try to relock the bootloader while having Pie version installed and not beta version.
Click to expand...
Click to collapse
Yes, stock, firmware directly from motorola with stock images, back on android 9 pie again, still not working...
(RIVER_PPOS29.114_134_14_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml)
Still not working: "(bootloader) Image signed with key bad key"
natesc0tt said:
Yes, stock, firmware directly from motorola with stock images, back on android 9 pie again, still not working...
(RIVER_PPOS29.114_134_14_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml)
Still not working: "(bootloader) Image signed with key bad key"
Click to expand...
Click to collapse
Pie version flashed completely?
Output fastboot getvar ro.build.fingerprint?
I guess relocking fails because it's like a downgrade for the bootloader while having stock Pie installed.
yes, that is why i am asking for a 10/Q stock firmware so it doesn't have to try reverting backwards to 9/pie
fastboot getvar all...
(bootloader) version-bootloader: MBM-2.1-river_retail-0ff20295b20-200404
(bootloader) product: river
(bootloader) board: river
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY********
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 24E8811B00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 355************
(bootloader) meid:
(bootloader) date: 12-06-2019
(bootloader) sku: XT1962-1
(bootloader) carrier_sku: XT1962-1
(bootloader) battid: SB18C34004
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 6 20:48:22 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/river/river:9/PPOS29.114-
(bootloader) ro.build.fingerprint[1]: 134-14/0cccf:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.281.20.river.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: M632_26.100.01.120.03R RIVER_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: clbld168) (gcc version 4.9.x 20150123 (p
(bootloader) kernel.version[2]: rerelease) (GCC) ) #1 SMP PREEMPT Sat Ap
(bootloader) kernel.version[3]: r 4 06:27:07 CDT 2020
(bootloader) sbl1.git: MBM-2.1-river_retail-516ad1ccba-200404
(bootloader) rpm.git: MBM-2.1-river_retail-22daab39-200404
(bootloader) tz.git: MBM-2.1-river_retail-e4c78bcf8f-200404
(bootloader) devcfg.git: MBM-2.1-river_retail-e4c78bcf8f-200404
(bootloader) keymaster.git: MBM-2.1-river_retail-e4c78bcf8f-200404
(bootloader) cmnlib.git: MBM-2.1-river_retail-e4c78bcf8f-200404
(bootloader) cmnlib64.git: MBM-2.1-river_retail-e4c78bcf8f-200404
(bootloader) prov.git: MBM-2.1-river_retail-e4c78bcf8f-200404
(bootloader) aboot.git: MBM-2.1-river_retail-0ff20295b20-200404
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: retus
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.012s
natesc0tt said:
yes, that is why i am asking for a 10/Q stock firmware so it doesn't have to try reverting backwards to 9/pie
Click to expand...
Click to collapse
I understand your problem. But there must be any solutions from Motorola for this issue. Otherwise you will have to wait for the Android 10 update.
https://drive.google.com/file/d/1ijf31WzBRAmlwBTtdLcTRPyTDtMjGn0a/view?usp=sharing
---------- Post added at 08:46 PM ---------- Previous post was at 08:46 PM ----------
natesc0tt said:
Yes, stock, firmware directly from motorola with stock images, back on android 9 pie again, still not working...
(RIVER_PPOS29.114_134_14_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml)
Still not working: "(bootloader) Image signed with key bad key"
Click to expand...
Click to collapse
See above
thanks HueyT! Do u know if this is for XT1692-1 variant? What's your venmo? If this works, I'm buying u a beer!
From what I understand, the stock fw for US,IN,EU ect. should be available before too much longer. Tired of waiting too but I'm not ready to risk using anything short of a perfect (signed) match to root with. I miss all my fav. root appz!
FYI, This was my Flashing procedure:
(every step passed besides "flash boot boot.img" <<< failed!)
fastboot oem lock begin
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.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 oem oem.img
fastboot oem lock
FYI, This was my Flashing procedure:
(every step passed besides "flash boot boot.img" <<< failed!)
fastboot oem lock begin
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.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 oem oem.img
fastboot oem lock