yashsingh1/xdaforums huggingface dataset:
[Moto G7 Questions & Answers] Ayush758:
Hey guys,

I was trying to install HavocOS on my moto g7(River) and while wiping cache and internal storage through TWRP I accidentally also wiped the System as well, now the phone boots up into fastboot mode with the oem status shows up as Locked. I tried flashing stock Rom using fastboot ( as the phone still enters fastboot mode) it returns a error saying

FAILED (remote: '')

fastboot: error: Command failed

Trying to enter recovers give the following error

Startup failed:

No bootable A/B slot

failed to boot Linux, falling back to fastboot

Boot up failed

And trying to flash TWRP gives the same error

C:\platform-tools>fastboot boot twrp-3.5.2_10-0-river.img

Sending 'boot.img' (32754 KB) OKAY [ 0.710s]

Booting (bootloader) permission denied!

FAILED (remote: '')

fastboot: error: Command failed

any help would be appreciated.
[Moto G7 Questions & Answers] Spaceminer:
Try the following...

fastboot erase userdata
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2

If it fails to erase userdata, then use fastboot -w. Erase what you can regardless, and reboot directly to the bootloader. Then try flashing vbmeta first. If that doesn't work. Make sure you have the correct firmware and make sure it's the same or a newer version than what you were on. If all else fails, you need to trigger EDL somehow and blank flash.
[Moto G7 Questions & Answers] Ayush758:
Where do I find vbmeta ? The stock firmware image I have does not have vbmeta

this is where I am downloading the stock firmware from https://mirrors.lolinet.com/firmware/moto/river/official/
[Moto G7 Questions & Answers] Spaceminer:
I didn't expect that. Start with gpt and the bootloader. See if it works.
[Moto G7 Questions & Answers] Ayush758:
When I try to flash boot loader I get the following error

C:\platform-tools>fastboot flash bootloader bootloader.img

(bootloader) is-logical:bootloader: not found

Sending 'bootloader' (7419 KB) OKAY [ 0.355s]

Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'

(bootloader) Invalid partition name aboot

(bootloader) Invalid partition name rpm

(bootloader) Invalid partition name tz

(bootloader) Invalid partition name devcfg

(bootloader) Invalid partition name cmnlib

(bootloader) Invalid partition name cmnlib64

(bootloader) Invalid partition name keymaster

(bootloader) Invalid partition name prov

(bootloader) Invalid partition name sbl1

(bootloader) Cancelling 'bootloader.default.xml'

FAILED (remote: '')

fastboot: error: Command failed

And when I flash GPT this is the error

C:\platform-tools>fastboot flash partition gpt.bin

(bootloader) is-logical:partition: not found

Sending 'partition' (45 KB) OKAY [ 0.167s]

Writing 'partition' (bootloader) Validating 'gpt.default.xml'

(bootloader) Image primary_gpt failed validation

(bootloader) Preflash validation failed

(bootloader) Cancelling 'gpt.default.xml'

FAILED (remote: '')

fastboot: error: Command failed
[Moto G7 Questions & Answers] Jleeblanch:
When in bootloader/fastboot, check what the output of "fastboot getvar all" and it should show build fingerprint in some of the output. Are you flashing same firmware as shown in the output? I'd assume same or newer should work 🤔. But otherwise may need to trigger EDL to blank flash as already mentioned
[Moto G7 Questions & Answers] Ayush758:
This is the output of fastboot getvar all

C:\platform-tools>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: MBM-2.1-river_retail-0ff2029-191127

(bootloader) product: river

(bootloader) board: river

(bootloader) secure: yes

(bootloader) hwrev: PVT

(bootloader) radio: 6

(bootloader) storage-type: emmc

(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005

(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F

(bootloader) cpu: SDM632

(bootloader) serialno: b92aa885

(bootloader) cid: 0xDEAD

(bootloader) channelid: 0x00

(bootloader) uid: 0000000000000000000000000000

(bootloader) securestate: oem_locked

(bootloader) iswarrantyvoid: n/a

(bootloader) max-download-size: 536870912

(bootloader) reason: Failed to initialize partition table

(bootloader) imei:

(bootloader) meid:

(bootloader) date:

(bootloader) sku:

(bootloader) carrier_sku:

(bootloader) battid:

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time:

(bootloader) ro.build.fingerprint:

(bootloader) poweroffalarm: 0

(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) devcfg.git: devcfg.git

(bootloader) keymaster.git: keymaster.git

(bootloader) cmnlib.git: cmnlib.git

(bootloader) cmnlib64.git: cmnlib64.git

(bootloader) prov.git: prov.git

(bootloader) aboot.git: MBM-2.1-river_retail-0ff2029-191127

(bootloader) frp-state: no protection (err)

(bootloader) ro.carrier:

(bootloader) current-slot:

(bootloader) running-boot-lun: must + g->mlen

(bootloader) running-slot:

(bootloader) slot-suffixes: _a

(bootloader) slot-count: 1

(bootloader) slot-successful:_a: INVALID

(bootloader) slot-successful:_b: INVALID

(bootloader) slot-bootable:_a: INVALID

(bootloader) slot-bootable:_b: INVALID

(bootloader) slot-retry-count:_a: unknown

(bootloader) slot-retry-count:_b: unknown

all: listed above

The build fingerprint seems to be blank.
[Moto G7 Questions & Answers] Spaceminer:
Try running "fastboot oem blankflash" and see if it reboots into EDL mode. If so you'll just need a blank flash file and that should fix you up.
[Moto G7 Questions & Answers] Ayush758:
Yes it enters blankflash mode , do we have a link to the blank flash file?
[Moto G7 Questions & Answers] Spaceminer:
Oh yeah! There's a bunch of them. What's your model number and device code name? I'll help you find it, and I know where the tools are to run it.

Edit: I found it! River - there are 3 here. https://mirrors.lolinet.com/firmware/moto/river/blankflash/

If those don't work, I know there's more in the threads here. We just gotta find the right one. And here's the tools you'll need. Runs on windows 7/8/10. If you use Linux then I think we'll need to find RSD lite.

QPST utilities
[Moto G7 Questions & Answers] Spaceminer:
Here's an easy step by step I put together a long time ago. It'll work on the G7 too. Just make sure to use your blank flash files.

https://xdaforums.com/t/successful-blankflash-on-xt1952-4.4002643/#post-81954663
[Moto G7 Questions & Answers] Ayush758:
Hey i tried all the steps and thanks to you I can boot back to fast boot menu, but I have having other problems now. I am trying to flash the default firmware here's the list of commands

fastboot getvar max-sparse-size

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_b system_b.img_sparsechunk.0

fastboot flash system_b system_b.img_sparsechunk.1

fastboot flash vendor vendor.img

fastboot flash oem oem.img

fastboot flash oem_b oem_other.img

fastboot erase userdata

fastboot erase DDR

This is the error it returns

flash modem NON-HLOS.bin

(bootloader) is-logical:modem_a: not found

Sending 'modem_a' (65884 KB) OKAY [ 1.945s]

Writing 'modem_a' OKAY [ 0.346s]

Finished. Total time: 2.386s

and also recovery only works if I do fastboot boot recovery.img

once I have access to recovery and i flash the recovery.zip the new installed recovery does not respond to touch screen( I did try older versions of TWRP all have the same issues) .

and it's also not able to mount /data so I have to wipe-> Format data for it to work.
[Moto G7 Questions & Answers] Spaceminer:
"flash modem NON-HLOS.bin

(bootloader) is-logical:modem_a: not found

Sending 'modem_a' (65884 KB) OKAY [ 1.945s]

Writing 'modem_a' OKAY [ 0.346s]"

This isn't an error. It flashed correctly. Just flash everything in there and in order. The OS should boot up after that.
[Moto G7 Questions & Answers] Ayush758:
Okay so I flashed everything but it just boots up and goes to fastboot mode, does not boot up to the OS
[Moto G7 Questions & Answers] Spaceminer:
Boot stock recovery and factory reset.
[Moto G7 Questions & Answers] Ayush758:
Recovery mode says No command with a exclamation mark on the android logo.
[Moto G7 Questions & Answers] Spaceminer:
That's good. Hold the power button and tap vol down 2x then release. If that doesn't work try power+Vol up 2x and release.
[Moto G7 Questions & Answers] Ayush758:
Thank you for all the help, It was not the recovery but a error I made . The flash commands were wrong I forgot to add some files in the commands list here is the full command list if someone wants to use it.

fastboot getvar max-sparse-size

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_b system_b.img_sparsechunk.0

fastboot flash system_b system_b.img_sparsechunk.1

fastboot flash system_b system_b.img_sparsechunk.1

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

Thank you for you help again man I am able to boot into my phone now . Will make a guide on all this so if someone has the same issue they can fix it.
[Moto G7 Questions & Answers] mkeaton1967:
I have a similar problem with a hard bricked Moto G7. I successfully installed Lineage 18, but was getting error / nag messages at startup. A Motorola pop-up saying the device was unsafe. After about 10 seconds it would then boot into Lineage successfully.

I then rooted the device in an attempt to stop the nag messages, and now it won’t boot up into the OS. It will boot into fastboot / boot loader. But if you try to boot the OS it just goes to a black screen and the OS never starts.

I can’t get it to flash for TWRP. If I type “fastboot devices” the phone will show up in the list. But if I try to flash TWRP.img it says that no devices are present.

I would appreciate any suggestions you might have. Thank you!
[Moto G7 Questions & Answers] Ayush758:
If you are able to enter fastboot mode you can try blankflashing your device and see if that fixes the issue.

>Enter fastboot mode

>Once the device enters the fastboot mode type the following into the command window

fastboot oem blankflash

let me know if it enters blankflash mode we can fix it after that.
[Moto G7 Questions & Answers] mkeaton1967:
Thanks for replying back so quickly. Here’s what I get when I try those commands…

C:\adb>fastboot devices

ZY323T7TSV fastboot

C:\adb>fastboot oem blankflash

(bootloader) command restricted

FAILED (remote: '')

fastboot: error: Command failed

I tried it both in Android Studio (platform-tools directory) and in the ADB “15-second” tool
[Moto G7 Questions & Answers] Ayush758:
Try these commands

fastboot erase userdata
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2

and also can you show me the output for the following

fastboot getvar all
[Moto G7 Questions & Answers] Ayush758:
The phone not being detected can be due to corrupted partitions.

So you can still temporary flash the TWRP , try flashing the TWRP and then try resetting everything ( Factory Reset, try erasing system as well ) and let me know if you face any errors.
[Moto G7 Questions & Answers] mkeaton1967:
I must have goofed somthing up when I used magdisk (not correct spelling) to root the phone. I get an error message saying there isn’t a recovery partition.

Is there a command I can use to see what partitions are still out there?

C:\adb>fastboot devices

ZY323T7TSV fastboot

C:\adb>fastboot flash recovery twrp.img

(bootloader) is-logical:recovery: not found

Sending 'recovery' (33352 KB) OKAY [ 1.002s]

Writing 'recovery' (bootloader) Invalid partition name recovery

FAILED (remote: '')

fastboot: error: Command failed
[Moto G7 Questions & Answers] mkeaton1967:
I should also note that when I type fastboot devices, it will return a serial number for the phone. If I use adb get-serialno or adb get-state, then I get an error message that says “no devices or emulators found”.
[Moto G7 Questions & Answers] Ayush758:
Blankflash is the only way to fix this now. Did you try flashing the stock firmware?
[Moto G7 Questions & Answers] mkeaton1967:
I did try the OEM — unfortunately, I get the error message that says “no devices or emulators attached”. Although the device does show up when I do the fastboot devices command.

Appreciate you trying to help. It’s an old phone, I was trying to fix it up for a family member and breathe new life by updating it to Lineage 18 (in order to get Android 11).
[Moto G7 Questions & Answers] mkeaton1967:
When I try to run blankflash I get a different error message:

C:\adb>fastboot oem blankflash

(bootloader) command restricted

FAILED (remote: '')

fastboot: error: Command failed

I tried it both in Android Studio (platform-tools directory) and in the ADB “15-second” tool
[Moto G7 Questions & Answers] mkeaton1967:
And I did confirm that it is unlocked via ”fastboot flashing unlock”
[Moto G7 Questions & Answers] mkeaton1967:
One other issue that is worth mentioning… I’ve downloaded and installed the USB Drivers. If I type in “fastboot devices” it will return the serial number. If I type in “adb devices” it will return the words ‘List of devices attached’ but no devices are listed.
[Moto G7 Questions & Answers] NTGDeveloper:
I'll go out on a limb and say that the error message at startup was saying that the device was insecure and unverified or something like that. If that was the case and you want to get rid of it, you need to flash a custom boot logo. {Mod edit}. Are you able to boot into the lineage recovery? If so, try flashing the TWRP zip from there, or honestly, try doing fastboot boot twrp.img and you can flash the zip from there if Lineage gives you issues (which let's be honest, it probably will)

Try that out and let us know how that works! :)

EDIT: I never saw any of the troubleshooting above until after posting. Just a couple of things, fastboot flash recovery twrp.img will not work since the device does not have a recovery partition, and another suggestion is using the Lenovo Rescue and Smart Assistant tool. I'm sure a blank flash would be more effective, but that's just another option that might fix the partition issues.
[Moto G7 Questions & Answers] mkeaton1967:
Thanks, that seems to have helped. I booted into TWRP, had to erase files and repair file structure, and was then able to successfully install Lineage.

much appreciated, will be able to give this phone to a family member who isn’t able to afford one — good deed accomplished!
[Moto G7 Questions & Answers] Rodrick123:
How do I attach zip or jar folders to this? I have a blankflash that unhardbricked my xt1962-1 that I want to share.
[Moto G7 Questions & Answers] Oswald Boelcke:
@NTGDeveloper

I've edited your above post and removed the references to social media! As an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads. These conditions obviously don't apply to your posts or you. Additional information is also available here:

Telegram Chat Channels - Way Forward

WhatsApp/Telegram Groups and Channels - Going Forward Hello XDA family! Just notifying all members that posting certain links to Telegram and other sites like WhatsApp is now allowed on XDA. What does that mean? We will allow links to messages...

xdaforums.com

Please refrain from sharing of social media links in future unless done in an own development thread.

Thanks for your cooperation!

Regards

Oswald Boelcke

Senior Moderator
[Moto G7 Questions & Answers] Alanmoreirax:
i'm lost
[Moto G7 Questions & Answers] Alanmoreirax:
Solution!

https://xdaforums.com/t/hardbricked-moto-g7-river-xt1962-4-solution.4420575/
[Samsung Galaxy S21 Ultra] ankitsxperiago:
Hey folks!

I have orignal Samsung 45W charger (listed on their official site) and when I use it to charge my Galaxy S21 Ultra, it takes longer than what I have seen in some Youtube videos.

Mostly it takes the phone around 70 minutes to charge from 0 to 100.

But when i charge it using my Samsung 45W charger, i takes around 100 minutes ( 1 Hour 40 mins) to full charge.

I have tried charging the phone while the phone is turned OFF as well when it is ON, but i don't get the charging time around 70 minutes.

The fun thing is that if I plug the charger around 10-15%, it shows me that it will be charged completely in around 50mins to 1 hour, but as the time passes on, that figure increases and I get a completely charged phone in around 1 hour 40 minutes.

If anyone has a solution, please let me know.

The 45W Samsung charger says that it outputs as much current as required by the device.
[Samsung Galaxy S21 Ultra] Da1e7150:
The S21 series don't utilise 45w do you will only get 25w of power
[Samsung Galaxy S21 Ultra] Sonin66:
I have been at 1% and it said it would take 1 hour and 7 mins to fully charge
[Samsung Galaxy S21 Ultra] Da1e7150:
That's normal
[Samsung Galaxy S21 Ultra] mpore14:
View attachment 5295125

Im assuming you got these on?

If so, try a cable change.

If cable change doesn't fix it, try factory reset.

If it doesn't work, contact Samsung
[Samsung Galaxy S21 Ultra] ankitsxperiago:
I know that, but let's say it utilizes 25W, so it should fully charge the phone in 70 minutes but as i said in the orignal post, it takes around 100 minutes.

Moreover, the estimate that the phone shows, it does not stick to that
[Samsung Galaxy S21 Ultra] ankitsxperiago:
but why other S21 ultra charges faster?
[Samsung Galaxy S21 Ultra] ankitsxperiago:
Superfast charging and fast charging is on, shouldn't it be?
[Samsung Galaxy S21 Ultra] Da1e7150:
It will be to do with your actual house/flat power supply it might not be giving the full wattage needed I really wouldn't worry
[Samsung Galaxy S21 Ultra] ankitsxperiago:
I don't think that's the problem
[Samsung Galaxy S21 Ultra] blackhawk:
Temperature is a factor.

Charging is an electrochemical reaction that needs heat.

Fast charging will not engage if the start temp is too low. Best start temperature is at least 85°F.

90F is better. Keep battery below 100F while charging, if it exceeds 101-102F it will disengage or stop charging entirely.

After reaching 70-75% or so it will ramp down.

At 90% it greatly ramps back protect the battery.

Try to limit charging to 30-90%; 40-72% being ideal for charge speed and battery longevity.

Avoid going below 20% as it greatly time. battery stress and provides little usable time.

Avoid charging of any kind if battery temp is below 72F as it can cause Li plating which permanently degrades the cell.

Drop in battery capacity and erratic fast charging can indicate a battery failure. This can happen at anytime but becomes more likely as the battery ages.

☠Any signs of cover bulging means the battery must be replaced asap. It rests on the display and can damage it, or worse...💥☠
[Samsung Galaxy S21 Ultra] iampunX:
Same here. My S21 Ultra (exynos) takes over 100 minutes to fully charge. Should I be contacting Samsung?
[Samsung Galaxy S21 Ultra] Da1e7150:
Use a 25w charger it's known the 45w charger charges the phone slower
[Samsung Galaxy S21 Ultra] blackhawk:
I've never seen that stated before.

Source?
[Samsung Galaxy S21 Ultra] Da1e7150:
It's on Samsung's own forums
[Samsung Galaxy S21 Ultra] blackhawk:
Could be a lot of reasons for that including temperature. The 45 w brick charge rate isn't that much greater anyway.

I get best fast charging results when the start temp is close to 90F on my N10+.

At a 72F start temp it's possible fast charging won't engage at all.

If fast charging fails to engage because of low temperature at the beginning of the charge cycle it will revert to slow charging for that entire charge cycle regardless if the temperature rises into the optimum range during the charge cycle.
[Samsung Galaxy S21 Ultra] babyboy3265:
Guys why are you so obsessed with charging the phone super fast?

It is better to let it take it's time, it will let the battery stay healthy for longer. Realistically if you have all the fast charging options OFF, and left your phone to charge at night, this would be the best scenario. The device can easily last a full day anyway.
[Samsung Galaxy S21 Ultra] blackhawk:
Charging overnight or to 100% is the worst way to charge an Li. Fast charging is really useful for the frequent midrange (40-70%) charging Li's prefer.

10 minutes vs 20 minutes for 20%.

If you don't mind the extra time then midrange slow charging is the optimum way to go.

Always keep battery temperature above 80°F and under 100F to avoid the possibility of the Li plating phenomenon though.
[Samsung Galaxy S21 Ultra] babyboy3265:
You may have a point. Over the years I have seen various sources talk about charging fast and slow and also indeed charging to 100 is not the ultimate scenario. The ultimate one is to charge it to about 90% and the phone would stop charging automatically. It is actually possible and adjustable with a Magisk script as I recall.

In the long term though, from my personal experience I have discovered that charging your phone at night slowly is best all-around scenario. For example, you need 2 good years to lose 10-20% of battery capacity. And realistically it is unlikely that you would use your phone for more than 3 years as you would most likely upgrade. So having to go trough the constant hustle of quick charging it and stopping it on time and etc, is just not worth it.

And if you do decide to use your phone for over 3 years, your phones waterproofness would gone anw, so you might as well just pop a new battery...
[Samsung Galaxy S21 Ultra] blackhawk:
My normal top off point is 65-75%, most times after 72-80% fast charging has ramped back a lot. What's nice about midrange charging is you take a 10 minute break and are good for another 2 hours.

On my Note 10+ I needed to replace the battery at 1.5 year mark. It saw some hot weather abuse and cold charging etc, etc, etc.

It swelled and had to proform an emergency batterydictomy🤣

Now that I know how to change it out it's no big deal... and charging protocols/battery longevity are sort of a game.

Lol, I ordered an extra charging port PCB too🤣
[Samsung Galaxy S21 Ultra] iampunX:
I was using the 25w charger. It overheats and took around 2 hours to fully charge from 10-100% yesterday. It looks like things are getting only worse here.