Database Info

[Q] FAILED (data transfer failure (Too many links))

Hi, I was trying to flash stock 4.4.3 to my Nexus 5 using this method. Something happened and now it won't boot up past the "Google" splash screen with the padlock.
I decided to try using Nexus Root Tool v1.8.3 to flash it, using Back to Stock > Current status: Soft-Bricked/Bootloop. I saw that there is an older thread where someone had a similar issue, but I'm still fairly new (I'd say intermediate level) at this stuff and I don't understand what they're saying and I'm on the verge of freaking out because I do everything through my phone.
I can still access the Bootloader and Recovery, so I believe there's hope, but I keep trying over and over again and the command line keeps spitting out errors, then fastboot crashes. Please help! :crying:

I tried method #2 in this guide on XDA, and fastboot picks up my phone, but some of the commands are failing, stating "FAILED (command write failed (Invalid argument))" or "FAILED (command write failed (No such device or address))" or the error mentioned in the thread title.
After trying it, my phone is still bootlooping.

seems odd that bootloader and recovery flash fine
try, long shot, fastboot format userdata obviously you will lose data, but I think that's gone anyway.
or maybe better fastboot flash a custom recovery and boot to it via fastboot, see if you can repair from there with some adb commands
otherwise it seems your partitions are messed up, I think maybe a full .tot flash with lgtool is in order

175
meangreenie said:
seems odd that bootloader and recovery flash fine
try, long shot, fastboot format userdata obviously you will lose data, but I think that's gone anyway.
or maybe better fastboot flash a custom recovery and boot to it via fastboot, see if you can repair from there with some adb commands
otherwise it seems your partitions are messed up, I think maybe a full .tot flash with lgtool is in order
Click to expand...
Click to collapse
I tried
Code:
fastboot format userdata <directory>\userdata.img
and it failed (you can see it in the 2nd screenshot in the 2nd post). Don't I need to be rooted to be able to flash a custom recovery? I'd successfully unrooted before this mess occurred.
What's .tot flashing about? I'm willing to try that if flashing custom recovery is a lost cause.

you can flash a custom recovery as long as your unlocked, root is not needed.
looking at your screen shots shows that recovery is flashing ok.

Hi! You could try to upgrade your fastboot and adb binaries with your drivers as well. Use usb2.0 port only, and restart your PC
Tapatalk-kal küldve az én Nexus 5-el

meangreenie said:
you can flash a custom recovery as long as your unlocked, root is not needed.
looking at your screen shots shows that recovery is flashing ok.
Click to expand...
Click to collapse
I got TWRP v2.7.1.1 installed. How do I do repairs using adb commands?
bitdomo said:
Hi! You could try to upgrade your fastboot and adb binaries with your drivers as well. Use usb2.0 port only, and restart your PC
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Hi. How do I upgrade the binaries? I believe everything is up-to-date, though. I'd installed everything fresh yesterday, for the purpose of flashing 4.4.3.

Also, in case it's important, TWRP showed this (see attachment):

Dalae said:
I got TWRP v2.7.1.1 installed. How do I do repairs using adb commands?
Hi. How do I upgrade the binaries? I believe everything is up-to-date, though. I'd installed everything fresh yesterday, for the purpose of flashing 4.4.3.
Click to expand...
Click to collapse
Latest drivers for phone http://developer.android.com/sdk/win-usb.html
Latest adb and fastboot in the sdk/platform tools folder in android sdk http://developer.android.com/sdk/index.html. Copy use those binaries for the flashing process.
Oh sorry as I see from the pictures you already have teh latest of everything. You could try this http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833

I don't know if you can repair it with adb commands, but there was a thread on the general section which had a lot of info on repairing the data partition, you might want to have a search for it.. I can't remember what it was called, sorry. .. maybe something like... corrupt data recovery
otherwise the tot method linked above should get you up and running quickly.

bitdomo said:
Latest drivers for phone http://developer.android.com/sdk/win-usb.html
Latest adb and fastboot in the sdk/platform tools folder in android sdk http://developer.android.com/sdk/index.html. Copy use those binaries for the flashing process.
Oh sorry as I see from the pictures you already have teh latest of everything. You could try this http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
Click to expand...
Click to collapse
meangreenie said:
I don't know if you can repair it with adb commands, but there was a thread on the general section which had a lot of info on repairing the data partition, you might want to have a search for it.. I can't remember what it was called, sorry. .. maybe something like... corrupt data recovery
otherwise the tot method linked above should get you up and running quickly.
Click to expand...
Click to collapse
Okay, thanks. I'll try the LG Flashtool. If I have any questions, I'll ask here. Either way, I'll post results.

I flashed the firmware and everything seems hunky-dorey. :victory: Thanks for your help, both of you. I realize that restoring device factory version is optional, but what's it about? As in, under what circumstances would I want to do this?
PS: When my phone booted up, it showed that the 4.4.3 OTA update is available. If I were to update would that have any effect on my device factory version?

Dalae said:
I flashed the firmware and everything seems hunky-dorey. :victory: Thanks for your help, both of you. I realize that restoring device factory version is optional, but what's it about? As in, under what circumstances would I want to do this?
PS: When my phone booted up, it showed that the 4.4.3 OTA update is available. If I were to update would that have any effect on my device factory version?
Click to expand...
Click to collapse
you have to restore your original factory device version if it bothers you that it is not your original . Btw the name of the tot file will be your new device factory version. if you flash a tot file which has the same name as your original factory device version then you have to do nothing
Tapatalk-kal küldve az én Nexus 5-el

bitdomo said:
you have to restore your original factory device version if it bothers you that it is not your original . Btw the name of the tot file will be your new device factory version. if you flash a tot file which has the same name as your original factory device version then you have to do nothing
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Ah, alright. Thanks! I don't really care that it's not the original, as long as it doesn't have any undesirable effects. And, just for the heck of it, here's what was in the log regarding the original and the result:
[15:46: 7] 11. device factory version = LGD820AT-00-V10a-NXS-XX-OCT-09-2013-KQS81M-USER-32G+0
[15:46: 7] 12. device factory out version = LGD820AT-00-V10a-NXS-XX-OCT-03-2013-KRS59B-FACTORY-XXG+0
I installed the 4.4.3 OTA and it went smoothly. I'm free to unlock my bootloader, root, and install custom recovery now, correct?

nice to see your up and running
yes. now you can unlock and root
just one thing to watch out for, after running the unlock command you must let your phone fully boot once. this is because the original recovery is needed to complete the process during boot up.
then your free to install a custom recovery and flash a root zip, supersu by chain fire recommended by me. then when booted install and run busybox from the playstore

Great, thanks! I rooted using NRT, which installed BusyBox Free for me.
Sent from my Nexus 7 using Tapatalk

I have been getting this kinda crap on my Nexus 7 2013 and Nexus Player when I upgrade between OS Versions.
The Fix is to open up the system update ZIP file, extract the individual partitions and flash SYSTEM.img manually
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
I think it has to do with a Fastboot memory limitation or something. It could be an older version, but it seems it just can't flash everything at once. If you separate it out and flash each one separately, it works fine.

[XT1032] Moto G stucks on logo boot

Hi everyone. First of all, excuse me for my not well English. Today I've tried to reset my Motorola Moto G XT1032: it's a GPE converted by me some months ago. I've not succeded to reset it using Android settings. So, I've tried using the flashboot menu (Volume down + power, Recovery, Volume up + power, delete all), but all data has remained on the phone.
So I tried to re-flash GPE firmware, as I did some months ago, but after the process the phone does not boot and stucks on Google boot logo with an the opened lock. I've tried many guides but I've not succeded to repair. Please, help me! Thanks.
P.S. I'm using Linux for fastboot and other tools.

I'm trying again by re-flashing. Now I'm seeing that there is an error on flashing partition.gpt. Why?

u can change a rom

Hi !
I have the same problem, beside all that my phone is in bootloop i cannot install any custom recovery, what ever custom recovery i flash i get hab check failed or partition mismatch and then i end up with the stuck recovery (i know i should not reboot right after the flash and i go to recovery mode but the moment i boot up i see the old recovery)
I am not sure what is wrong but i guess there should be something wrong with my partitions. the only rom that gets flashed with no errors (but still gets stuck in the bootloop) is XT1032_FALCON_RETFR_5.1_LPB23.13-56_cid7_CFC
I managed to see my files via the command fastboot boot recovery recovery.img but then i only have read access, If only i had write access i could upload some files to my phone and get it working with updating from SD card .
any help is appreciated

Have you guys tried flashing stock firmware image (not flashable zip)? Take a look at http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795 and at the guide in the OP on how to flash it.
Enviado de meu SM-G900M usando Tapatalk

alexandrino said:
Have you guys tried flashing stock firmware image (not flashable zip)? Take a look at http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795 and at the guide in the OP on how to flash it.
Enviado de meu SM-G900M usando Tapatalk
Click to expand...
Click to collapse
Thank you for your reply. Is nt that exactly what i did ? i mean i looked at the files . there ate generally two types of files. some are XML which i need to use fast boot. the other one is a zip file with several folders in it which i dont know how to flash. do you mean there is my answer?

Inside the factory firmware file you should find several files (.img,. bin, etc.) inside the zip which you should flash following this guide: http://forum.xda-developers.com/showthread.php?t=2542219. Just remember to not downgrade (or just flash a Lollipop image)

alexandrino said:
Inside the factory firmware file you should find several files (.img,. bin, etc.) inside the zip which you should flash following this guide: http://forum.xda-developers.com/showthread.php?t=2542219. Just remember to not downgrade (or just flash a Lollipop image)
Click to expand...
Click to collapse
I have followed the guide but maybe here is actually my problem
there are two kinds of ROMS to my knowledge. one has several files in it boot.img recovery.img chucnks etc... and there are no folders in the ROM file it is usually called XML
second type is a zip file like this one http://forum.xda-developers.com/devdb/project/dl/?id=14940 if you exract it there is a file named boot.img and two folders META-INF and System.
in the system there are numerous files but there is nothing to flash. the only way i know is flashing via fastboot. i dont know how flash these zip files.
one more point is that i dont have a custom recovery ( and i cannot install one since it does not show up after each reboot for an unknown reason)
from what i read people upload these second type zip files to their phone and then install it with their custom recovery software, but i dont have that luxury!

I have just noticed that we have been discussing your problem in two different threads (I thought they were from different people).
So you have already tried using fastboot to flash all those bin and img files and it still does not work? What error are you getting while trying to perform those commands?

alexandrino said:
I have just noticed that we have been discussing your problem in two different threads (I thought they were from different people).
So you have already tried using fastboot to flash all those bin and img files and it still does not work? What error are you getting while trying to perform those commands?
Click to expand...
Click to collapse
yes i guess. we can continue here, and thanks.
For anyfirmware i get hab check failed and partition mismatched errors
for recoveries i get mismatched partition error
they said you should ignore them but i am not sure if i should!
the only firmware which flashes flawlessly is XT1032_FALCON_RETFR_5.1_LPB23.13-56_cid7_CFC.xml by works i mean it just does not come up with any errors and it flashes but still the bootloader loops.
by the way, is there anyway i could upload some images to the device ? i cannot side load adb cause it comes with verification error in the middle of upload for anything i tried.

Thank you everyone for the replies. Some months ago I converted my Moto G to GPE as reported in this guide. When I tried to do it again (with the purpose of resetting the device) I got the issue descripted in my first post. But I was doing the all procedure using Ubuntu: I opened the batch file, written in Windows Batch Language, and I executed all the commands through the bash. Maybe, that's the thing that has made the phone not starting anymore. In my last try I've followed the procedure using Windows and now everything is ok.

Falcon down

Hi all,
I'm after some help with a 1st gen Moto G. It belonged to my mother, and was happily running CM for years before dying on her one day. She posted it back to me months ago...I failed to fix it then, and I'm not having much luck this time either.
It sits on the bootloader ok, and I can fastboot interact with it, but although attempts to revert to stock, or update TWRP etc look like they've worked, nothing ever changes. It's as if its storage has gone read-only.
CM is still there, but bootloops 9 times out of 10. Occasionally it'll start properly, before rebooting seconds later, probably because it can't write anything and it crashes out.
I can however, boot (not flash) the latest TWRP and play around with that, but even simple file operations like trying to delete anything fails ("process ended with ERROR 1"). I've tried clearing, factory resetting, reformatting, etc, but nothing has an effect. CM and the old files are all still there.
I don't need this phone, nor the files on it - it'll go in the trash if it can't be fixed - so not worried about damaging it any way in an attempt to revive it
Thanks

Everything you describe suggests Emmc corruption. Threads are created about it regularly. It's an issue that can effect any android phone, and while age could be the key factor - my launch-day Falcon has never had an issue. There is no cure.
However, try the below just in case I am wrong.
Flash the latest Factory Firmware Image for your model using mFastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
mFastboot download: https://www.androidfilehost.com/?fid=24052804347778493
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219​

lost101 said:
Everything you describe suggests Emmc corruption.
Click to expand...
Click to collapse
Ah, interesting. It's not something I've come across before, so it's good to at least know what's (probably) wrong with it.
lost101 said:
However, try the below just in case I am wrong.
Flash the latest Factory Firmware Image for your model using mFastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.​
Click to expand...
Click to collapse
Not sure if this was the best way, but I booted TWRP and attempted to install via ADB sideload (couldn't think of any other way to get the zip across).
fastboot transfered about 26% of the file before exiting.
TWRP reported:
Code:
installing zip file '/sideload/pacakge.zip'
>>> XT1032 Retail Europe 5.1 (Untouched) <<<
Installing Android
Please wait...
symlink: no of symlinks failed = 1
Updater process ended with ERROR: 7

imilne said:
Not sure if this was the best way, but I booted TWRP and attempted to install via ADB sideload (couldn't think of any other way to get the zip across).
Click to expand...
Click to collapse
Do as I instructed to remove all doubt of Emmc corruption.

Need help for soft brick (eRecovery not working)

What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?

hey i can help ! which version of twrp are you trying to flash ?

lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.

Venkata Lochan Nune said:
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.
Click to expand...
Click to collapse
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi

King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
My bad , I thought the update website to be huawei's official one(something like update.hicloud and all isn't it?). Well, thanks for the information but I still prefer gsi. It's buttery smooth .
And one more thing, if you follow the youtube video I mentioned, you don't need any gsi. You can get your device back on stock EMUI 5.

King_of_Android said:
hey i can help ! which version of twrp are you trying to flash ?
Click to expand...
Click to collapse
Hey I have a doubt... Will the recoveries we find in twrp official website / app work on EMUI 8? I wanted to try them but I'm afraid I might brick my device again. Getting it back is a hectic thing and I already had to face it thrice. LOL .

King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.

lmaohelp said:
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.
Click to expand...
Click to collapse
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?

Venkata Lochan Nune said:
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?
Click to expand...
Click to collapse
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!

lmaohelp said:
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!
Click to expand...
Click to collapse
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?

Venkata Lochan Nune said:
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?
Click to expand...
Click to collapse
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?

lmaohelp said:
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?
Click to expand...
Click to collapse
I'm attaching one that works with emui 8 try using it (Remember you have to flash it to recovery_ramdisk).

Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result

lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson

speedson said:
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson
Click to expand...
Click to collapse
His problem us with twrp.
He can only access fastboot but isn't able to flash twrp...

Venkata Lochan Nune said:
Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result
Click to expand...
Click to collapse
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?

lmaohelp said:
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?
Click to expand...
Click to collapse
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img

Venkata Lochan Nune said:
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Yup, I tried that as well, and it told me "invalid command"

lmaohelp said:
Yup, I tried that as well, and it told me "invalid command"
Click to expand...
Click to collapse
Well as you said, you partitions must have been really messed up. I have no other ideas except the test point method.
Are you trying anything else?

Ok we have some option that could help you...
Im read in the 4PDA (the russian XDA xD) forum that it should be possible to flash the oeminfo by fastboot command. So just download the HWOTA_BLN_Eng and expand it. Then go to 7 or 8 Folder and there you go to oeminfo folder. There you choose the right one for your Device and local area...for example BLN-L21 (Device) C432 (European Area)
Extract the file to your desktop and rename it to BLN-L21C432.img
--->be sure that you have the right Device driver installed and the right ADB driver for your device to<---
ok now Copy and Paste the BLN-L21C432.img to ADB folder and start command with admin rights
start the phone into fastboot mode
--->bootloader must be unlocked<---
in the command
fastboot flash oeminfo BLN-L21C432.img
wait for the result and it can not hurt to pray a bit in this moment...hihi
if this have success...you type in command
fastboot reboot
wait to the screen you can press 3 seconds Vol+ to go into erecovery....connect to wlan and it should work step by step like it should.
after download and recover the stock rom reboot and go again to erecover by press Vol+ for 3 seconds and now go to the second option...wipe data/factory reset and write yes+enter
in stock recovery wipe Data after that wipe Cache...reboot and wait that system boot the initial boot for first setup.
If this will not working...tell me what honor 6x you have and wich local area you are from and wich firmware you stock had before you doing wronng
good luck bro
solong
speedson

Phone boots into fastboot, system files corrupted

Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?

Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.

Both failed. I attached the errors I recieved.

crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.

crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com

I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.

crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/

It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.

Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?

Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.

That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .

crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!