Database Develop

[HELP]Moto G hard bricked

Hello guys
Today morning i was on cyanogenmod11 and after some time i decided to restore back to stock Lollipop so i restored a backup of Lollipop system image and suddenly a error poped up saying unable to mount /data /system
I thought this might me minor issue then i tried using fastboot to flash the stock lollipop images
When i started the flashing process i got some serious errors on my cmd
"Failed to erase partition"
"failed to write partition"
And for now only Fastboot Mode is working with UTAG "flashfail" error
i tried to flash recovery images and partition gpt file but no luck looks like my partitions are messed up bad
have a look at my attachments :crying:

any help would be appreciated

Hello ?anyone there?
Sent from my GT-S5830i using XDA Free mobile app

haytham.kenway said:
Hello ?anyone there?
Click to expand...
Click to collapse
Be patient. Not everybody lives in the same timezone. Your posted at 2.32am cet.
gpt.bin and motoboot.img can't be flashed if the version on the device is the same or higher version.
Just ignore these two.
Code:
fastboot oem fb_mode_set
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
That should do it.

doppelhelix said:
Be patient. Not everybody lives in the same timezone. Your posted at 2.32am cet.
gpt.bin and motoboot.img can't be flashed if the version on the device is the same or higher version.
Just ignore these two.
Code:
fastboot oem fb_mode_set
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
That should do it.
Click to expand...
Click to collapse
i followed as u said,executed first command and got "FAILED <Remote failure>"
rest all got same errors as posted in above post

haytham.kenway said:
i followed as u said,executed first command and got "FAILED <Remote failure>"
rest all got same errors as posted in above post
Click to expand...
Click to collapse
Sometimes it's the fastboot version. Try this:
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ABC99999999 fastboot
now copy the images into the directory where your command window is open and start flashing.

doppelhelix said:
Sometimes it's the fastboot version. Try this:
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ABC99999999 fastboot
now copy the images into the directory where your command window is open and start flashing.
Click to expand...
Click to collapse
dude i know how to flash these images,and i tried latest version of fastboot from google still problem persists

No OS, adb: Total xfer=0.00x

Hi everyone.
Accidentally wiped the OS, apparently people fixed it using ADB. I'm trying to sideload a rom but adb says "Total xfer 0.00x" and my moto g says ADB Sideload Complete: Failed.
Any ideas how to fix this?
ADDED:
In case if someone wonders how I fixed this:
1) Reboot the phone into bootloader mode.
2) Open a command prompt / terminal (Start -> cmd.exe in Win7) and browse to the folder with the extracted firmware.
3) Connect your phone to your PC.
4) Flash stock firmware.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot -w

some commands can not load
and no know such device:silly:

Can't find /efs and /persist. No mobile signal.

Yesterday, I unlocked the bootloader of my Sanders, installed OrangeFox via fastboot, wiped all partitions, ran
Code:
rm -rf /
, and installed Havoc + Gapps. To my utter dismay, in spite of inserted SIM, there was no cellular network. I don't have a backup for /efs or /persist. I connected the phone with ADB and ran
Code:
adb shell
and then
Code:
ls -al /
. The result didn't show efi or persist directory.
So, here's the summary:
1. Wiped all partitions, ran
Code:
rm -rf /
, installed Havoc + Gapps.
2. No cellular network, even with working SIM.
3. Cannot find /efs or /persist using adb or OrangeFox.
My model number is XT1804, Indian dual sim variant.
What I want is to be sure if /efs is destroyed. I do realise that if /efs is destroyed, I have an expensive paperweight, but I want to make sure of that.

Time for a new phone

Download Stock ROM Android 8 and Flash it using Fastboot
Stock MotoG : https://drive.google.com/file/d/159wxnPbTYMxGaMmRRCRGVGf8x-sepyu5/view
Fastboot Flash 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 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 system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot

Flash stock rom without inserting Sim and insert it after boot

Guide: restore River to good as new stock, clean bootloader

Edit: i just realized I put this in the wrong area, can a mod help me out
This took me hours to figure out honestly, and I have experience with this stuff. So, I want this to be as easy to find as possible for other folks.
To go back to stock:
1. Hold down Power and Volume till the boot menu shows up.
2. Plug the phone into your PC
3. Get the newest firmware for your phone model. I bought mine at Best Buy, so it was RETUS aka retail US. https://mirrors.lolinet.com/firmware...iver/official/
4. Extract the archive, and enter that folder in your terminal
5. Run the following commands from that folder. I saved these commands in a shell script and ran it but I think you can just paste it
THIS WILL WIPE ANY DATA ON YOUR PHONE AND PUT IT BACK TO FULL FACTORY FIRMWARE WITH LOCKED BOOT LOADER. At least when I ran it, it got my phone 100% no more complaints when it boots about untrusted code. This also restored my OTA ability and I was able to get the Android 10 update without any issues.
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
Click to expand...
Click to collapse

idumych said:
Edit: i just realized I put this in the wrong area, can a mod help me out
Click to expand...
Click to collapse
[Using "Report" button] How to Report issues / Moderators assistance by TonyStark
https://forum.xda-developers.com/showthread.php?t=1718423
Sent from my ali using XDA Labs

Please, how can I uninstall Magisk??

Please help me with your knowledge for a little while. I really need help because my android is bootlooping and this is the only phone I have. I really need your help here.
-I followed this guide with little differences https://forum.xda-developers.com/moto-e5/how-to/guide-root-twrp-moto-e5-play-explained-t3856182
-I took precautions and I downloaded the respective twrp for my phone (moto e5 nora).
-I couldn't make a backup because I'm lower-class college student and I can't afford a micro sd bigger than 4gb (I should have given up here).
-I installed Magisk and i thought it went well because no errors showed (at least that's what I think)
-Bootloop showing some numbers (80012a99-867fda48-...)
-I tried to uninstall using the uninstaller.zip so I could install an older version of Magisk but twrp says "cannot access /data please uninstall with magisk manager" but I just can't do it because android it's bootlooping.
Other data (it may be useful):
-After installing the last version of Magisk, abd won't recognize the phone ("adb devices") but "fastboot devices" will.
-I cannot repair /data but I can format it to ext4,ext2, etc (but it didn't work).
-I'm downloading stock image but I don't know how safe will it be to reinstall the whole Android. I'm afraid I can permanently damage my phone after what I have done here.
This is the first time I post here. I don't usually ask for help, I don't like to bother people. Thanks in advance and forgive me for my English!

FIXED
If someone has the same problem, this is what I did:
1-Download the LAST (this is very important) version ROM. I recommend lolinet (dot) com for our Moto E5.
2-Download adb and decompress the ROM into the adb folder.
3-Open command promt and go to adb's directory.
4-Check that your phone is being recognized by your pc:
Code:
fastboot devices
5- Copy and paste:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash dsp adspso.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
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 erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
Then fastboot reboot and there you go!
I'm very glad and I hope you, future readers, find this useful enough to get your phone running as it used to run when we were real happy.