Database Users

[Q] Razr M Stuck in Fastboot

Before I start. I would like to address the reason why. The first thing I hated about Motorola is that when you have updated to Jellybean OTA. It won't be unlocked. Unlike my past phones (ex: Samsung)
1) So it started when I installed SAFESTRAP, which did installed successfully.
2) Placed the Eclipse ROM in the root of my sd card.
3) Made a new ROM SLOT.
4) Saving some space, I deleted the whole /stock files. (Factory reset, wipe data and so on.)
5) When I was about to launch it. Everything was smooth until when I tried to delete files. Nothing can't be deleted or transferred. Which is weird.
6) Out of clumsiness, since I loved the JB look and thinking that would fix my file problem, I downloaded the Eclipse ROM ( the one I think isn't safe-strap compatible)
7) When I was about to boot to the system. It got stucked on ap fastboot, recovery can be accessed but even the button combos can't boot it normally.
The error shown :
Device is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
Anyone can help me? Thank you so very much if you did.

Cyb3rw0lfest1 said:
Before I start. I would like to address the reason why. The first thing I hated about Motorola is that when you have updated to Jellybean OTA. It won't be unlocked. Unlike my past phones (ex: Samsung)
1) So it started when I installed SAFESTRAP, which did installed successfully.
2) Placed the Eclipse ROM in the root of my sd card.
3) Made a new ROM SLOT.
4) Saving some space, I deleted the whole /stock files. (Factory reset, wipe data and so on.)
5) When I was about to launch it. Everything was smooth until when I tried to delete files. Nothing can't be deleted or transferred. Which is weird.
6) Out of clumsiness, since I loved the JB look and thinking that would fix my file problem, I downloaded the Eclipse ROM ( the one I think isn't safe-strap compatible)
7) When I was about to boot to the system. It got stucked on ap fastboot, recovery can be accessed but even the button combos can't boot it normally.
The error shown :
Device is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
Anyone can help me? Thank you so very much if you did.
Click to expand...
Click to collapse
Run this from windows
It's Russian . Just say yes. http://forum.xda-developers.com/showthread.php?t=2656659

Flash Failure
aviwdoowks said:
Run this from windows
It's Russian . Just say yes. http://forum.xda-developers.com/showthread.php?t=2656659
Click to expand...
Click to collapse
It now says Fastboot Reason : Flash Failure
I have tried fastboot option like from House of Moto and even the Droid Razr M Utility, but everytime it reaches
sending boot or system. it is stuck at that point.
Using RSD Lite, it shows failed flashing process gptmain0.bin (Something like that.)
I took the gptmain0.bin from the GPT Fix version of Droid Razr M Utility, placed it in there, and it reaches to failed flashing process tz.mbn
What to do? I'm all out of options really. Thanks.
UPDATE: Tried the logo.bat you sent me, it just says waiting for device. It won't even budge a little. Back to the usual hab boot error. Successfully flashed it using it 1.10. Just that I'm back to the first part. (Boot failure)

So you are locked on ...94 (1) right?

Boot Failure
aviwdoowks said:
So you are locked on ...94 (1) right?
Click to expand...
Click to collapse
Tried the logo.bat you sent me, it just says waiting for device. It won't even budge a little. Back to the usual hab boot error. Successfully flashed it using Razr M Utility1.10 (I don't know what version it flashed.). Just that I'm back to the first part. (Boot failure)

aviwdoowks said:
So you are locked on ...94 (1) right?
Click to expand...
Click to collapse
^^^^^^^^^^ what he said.
Build you are on? Locked boot?

aviwdoowks said:
^^^^^^^^^^ what he said.
Build you are on? Locked boot?
Click to expand...
Click to collapse
Now I can access safestrap recovery.
Shows
Unable to mount '/data' (tw_mount)
Unable to mount '/cache' (tw_mount)
Unable to mount '/ss' (tw_mount)
Unable to mount 'datamedia' (tw_mount)
Failed to mount /datamedia (Invalid argument)
Everytime I do something in the safestrap..

Cyb3rw0lfest1 said:
Now I can access safestrap recovery.
Shows FAILED TO MOUNT /DATAMEDIA (INVALID ARGUMENT}
Click to expand...
Click to collapse
Why do think you are on matt's version? If you were you could unlock!
You are on the one you last took the ota for or was on the phone. That is what locked means.
All you can do is rsd restore the above version or upgrade.

aviwdoowks said:
Why do think you are on matt's version? You are on the one you last took the ota for or was on the phone. That is what locked means.
All you can do is rsd restore the above version or upgrade.
Click to expand...
Click to collapse
I can access Safestrap recovery, flashed the boot.img separately. If I used RSD, it will only show failed flashing process gptmain0.bin or the tz.mbn

Cyb3rw0lfest1 said:
I can access Safestrap recovery, flashed the boot.img separately. If I used RSD, it will only show failed flashing process gptmain0.bin or the tz.mbn
Click to expand...
Click to collapse
Your boot is locked!
Read more.
I have a signature link...
Learn how to rsd ..94 & get on my SS dst rom.
Xposed works on locked boots.

aviwdoowks said:
Your boot is locked!
Read more.
I have a signature link...
Learn how to rsd ..94 & get on my SS dst rom.
Xposed works on locked boots.
Click to expand...
Click to collapse
Well now the only thing I can access is Safestrap recovery. Is there anyway I can fastboot in the safestrap recovery. The only thing I can see clearly in my Safestrap is that it can't mount CACHE or /CACHE/RECOVERY
Successfully fixed it myself. All it takes is trial and error all the way and the correct boot.img.

[ZE550KL] Can't Unlock bootloader/ install twrp/ install any rom

Hi,
My ZE550KL was locked in boot with this message: "Security Error: This phone has been flashed with an unauthorized software & is locked", so i followed some tutorials and was able to install TWRP recovery (i had bootloader already unlocked). Then when trying to reinstall stock rom, i realized i had to reinstall the stock recovery. I did it and installed the stock rom with version matching with the stock recovery i installed(UL-Z00L-WW-1.17.40.1531-user). Everything was going ok, but when my newly installed stock rom was popping multiple apps stopped working an i was unable to basically do anything. So i tried reinstalling stock rom again, but this is when things collapsed. As i entered recovery to reinstall the rom, it has lots of errors from partition cache
Code:
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
. This same errors happens when i try to wipe it from the recovery, but when i erase the cache partition on fastboot it says "OK". I also tried to reinstall twrp, but apparently my bootloader was blocked again, and it says it is flashed when i try, but when rebooting it boots again on stock recovery.
So i tried just booting twrp, but then it says my bootloader is blocked and can't boot twrp. Also tried sideloading stock rom from adb, but it gets the same cache partition errors. I tried
Code:
fastboot -w
and it says OK but the cache partition errors are still there. I also tried
Code:
fastboot erase ASDF
and i get some errors.
TLDR; I'm stuck at a cycle where i have to remount cache and all other partitions via TWRP, but i can't install TWRP because my bootloader got locked again and i can't unlock it because i need to install some rom to do it, but since my cache partition is destroyed i can't install anything, neither via fastboot on pc nor from recovery on the phone.

Did you tried the unoffical unlock way? It can done via PC in fastboot mode. Also did you tried `fastboot format system` kind of commands?

TheImpulson said:
Did you tried the unoffical unlock way? It can done via PC in fastboot mode. Also did you tried `fastboot format system` kind of commands?
Click to expand...
Click to collapse
I didn't. Can you please explain how to do it? Thanks

VMokaccino said:
I didn't. Can you please explain how to do it? Thanks
Click to expand...
Click to collapse
Damn! I just noticed that you will need to be in system to gain root access. I guess then it won't work. I suggest to try `fastboot format system/userdata/cache` way as it fixed my issues with partitions multiple times.
Here you go for unoffical guide: https://forum.xda-developers.com/ze...de-unlock-bootloader-asus-unlock-app-t3405850

TheImpulson said:
Damn! I just noticed that you will need to be in system to gain root access. I guess then it won't work. I suggest to try `fastboot format system/userdata/cache` way as it fixed my issues with partitions multiple times.
Here you go for unoffical guide: https://forum.xda-developers.com/ze...de-unlock-bootloader-asus-unlock-app-t3405850
Click to expand...
Click to collapse
Well, i tried all these format commands, but nothing has changed

VMokaccino said:
Well, i tried all these format commands, but nothing has changed
Click to expand...
Click to collapse
Did you tried what this guide says: https://www.asus.com/zentalk/thread-116230-1-1.html

TheImpulson said:
Did you tried what this guide says: https://www.asus.com/zentalk/thread-116230-1-1.html
Click to expand...
Click to collapse
I tried this, but my phone is now stuck on Fastboot Mode. It doesn't matter if i press VOL + or VOL -, it always enters in Fastboot Mode

VMokaccino said:
I tried this, but my phone is now stuck on Fastboot Mode. It doesn't matter if i press VOL + or VOL -, it always enters in Fastboot Mode
Click to expand...
Click to collapse
It's because you don't have any recovery or ROM on your device. Try flashing stock recovery.

TheImpulson said:
Did you tried what this guide says: https://www.asus.com/zentalk/thread-116230-1-1.html
Click to expand...
Click to collapse
TheImpulson said:
It's because you don't have any recovery or ROM on your device. Try flashing stock recovery.
Click to expand...
Click to collapse
Well, i tried flashing all stock recovery versions i could find, but none of them worked. I guess my phone is dead.

VMokaccino said:
Well, i tried flashing all stock recovery versions i could find, but none of them worked. I guess my phone is dead.
Click to expand...
Click to collapse
Take your phone to service center I guess.

A6000 Plus stuck on Bootloader

I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.

If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!

kamesh_kraken said:
I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.
Click to expand...
Click to collapse
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query

StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
I was like why didn't I try this before.
You know what happened? The boot process on "Command Prompt" screen went fine. I heard the unplugging the device and replugging the device sound very well. But during all these process it stays on Fastboot mode forever.
I have the latest TWRP loaded for temporary boot process. (3.2.1)
Besides from that
I was finally able to flash with QFIL tool. But still stucks at Lenovo POWERED BY android logo. QCom Downloader didn't work. But QFIL tool did work. I was able to finally come over the "sahara error" by quickly clicking "Download" button after connecting the cable. Then it flashed all the files. Then it finished downloading. But then if I try to switch it on, it wouldn't boot. Still stucks at the screen that I mentioned earlier.

StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry!
I tried it with Stock Recovery of A6000 (not plus). It booted into recovery.
Now, I can boot into TWRP. Looks like all the partitions are gone. How do I recover that?

StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?

kamesh_kraken said:
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?
Click to expand...
Click to collapse
Just flash a new ROM

StillrunsKK said:
Just flash a new ROM
Click to expand...
Click to collapse
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.

jameeljb6 said:
If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!
Click to expand...
Click to collapse
Haha. I know how to do that. Thing is, I can't boot into System or Recovery normally even if I flash via Fastboot. I can only boot to recovery by "fastboot boot recovery.img" Then in TWRP there, I can't flash any roms as it shows Failed to mount /system /data /cache all the time. Tried fixing with "repair file system" option in TWRP. Still doesn't work.

kamesh_kraken said:
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.
Click to expand...
Click to collapse
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?

StillrunsKK said:
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?
Click to expand...
Click to collapse
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5

kamesh_kraken said:
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5
Click to expand...
Click to collapse
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)

StillrunsKK said:
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)
Click to expand...
Click to collapse
The TWRP I mentioned 3.1.0 was obtained from RR forum only where dev mentions "F2FS" support. It does show the same error that I mentioned earlier. I did repair, resize, format, change file system. What ever I do, I always get the mount error on 3 partitions. Can't flash any ROMs either. Shows that error 7 and 6. I even deleted the assert line. It would only land me on error 6. I even googled and tried to get rid of that error. But after the error 6 or 7, it shows the same "mount failed".
Not my device. One of my client's. Received as not working.

Need help P10+ bricked

Hi,
i was on VKY-L29C636 with Oreo B360. TWRP_3.2.1-0_OREO installed and rooted. bootloader unlocked
My bad i tried to unoot via supersu app and got bricked. now i cannot go to recovery.
Normal boot shows
Error!
Func NO : 10 (boot image)
Error No : 2 (load failed)
if i tried to go to recovery via vol Up + power then got
Func No : 11 ( recovery image)
Error No: 2 ( load failed)
i think i should have installed original boot.img to unroot.
installed twrp again from fastboot mode without luck.
can it be solved by installing boot.img and system.img??? but i cannot extract boot.img, system.img from update.app ( B360 firmware) via huawei rom extractor.
Thanking you...

Rommco05 said:
You need to flash over fastboot stock recovery, ramdisk and kernel. Good luck
edit: In huaweiExtractor go to settings and uncheck this options: verify header checksum, verify file checksum and keep original timestamp
Click to expand...
Click to collapse
Thanks.
i could see kernel and ramdisk but cannot find the recovery although there are 4 ERECOVERY_KERNE, _RAMDI, _ VMET, _VENDO
aslo
3 RECOVERY_RAMDIS, _VBMETA, _VENDOR are there.
Edit:
Thank you very much i flashed only kernel and ramdisk and the phone is booted and in good state
Edit2: TWRP working too

what are the exact commands? i have the same issue and kernel is saying FAILED (remote: partition length get error) when i try to flash it

helppp
I followed the procedure and installed ramdisk and the kernel but then later I can not restore via the procedure with hwota8 .. can anyone help me?I'm losing hope..I can still install the twrp. Can you help?

Rommco05 said:
fastboot flash kernel kernel.img
fastboot flash recovery_ramdisk recovery_ramdisk.img
Click to expand...
Click to collapse
ok i was able to flash those commands - it still doesnt boot...i was able to get twrp back tho is there something else i should try? thanks for your help.

sismario89 said:
I followed the procedure and installed ramdisk and the kernel but then later I can not restore via the procedure with hwota8 .. can anyone help me?I'm losing hope..I can still install the twrp. Can you help?
Click to expand...
Click to collapse
im in the same situation hwota8 didnt work for me either - did you figure it out?

rck408 said:
im in the same situation hwota8 didnt work for me either - did you figure it out?
Click to expand...
Click to collapse
My phone didn't turn on in any mode.. I have totally bricked.. I can try with warranty but is too hard

sismario89 said:
My phone didn't turn on in any mode.. I have totally bricked.. I can try with warranty but is too hard
Click to expand...
Click to collapse
Did u solve this? I have same problem.

hi, what are the exact comands you sent to your phone? and how you connected? thank you

Phone stuck on erasing boot loop

Hello guys, I ran into some trouble by trying to reset my phone to stock firmware. I followed this guide https://forum.xda-developers.com/showthread.php?t=2759495 but with the moto e4 firmware, now it bootloops to erasing and bad key. Please help, it doesnt let me boot into recovery

frederickrl said:
Hello guys, I ran into some trouble by trying to reset my phone to stock firmware. I followed this guide https://forum.xda-developers.com/showthread.php?t=2759495 but with the moto e4 firmware, now it bootloops to erasing and bad key. Please help, it doesnt let me boot into recovery
Click to expand...
Click to collapse
Update, I was able to boot into twrp, currently attemtping to flash a rom

similar problem: recovery loop
frederickrl said:
Update, I was able to boot into twrp, currently attemtping to flash a rom
Click to expand...
Click to collapse
Hello,
this is my situation:
- switchin-on my new moto e4 (XT1762)
- boot into recovery (TWRP)
- in TWRP, I am able to 'work', i.e. install LineageOS 15.1 (this is my main goal)
--- I WIPE
--- I INSTALL the lineage ZIP file (lineage 15.1 20180310 unofficial woods
--- I REBOOT
BUT, sadly, the reboot is done again into TWRP.
The installation of lineageos did not report any error.
How can I check, that what I've installed so far (TWRP and magisk) is correct and working?
Did I forget something? E.g. do I have to install GAPPS as well? Or Magisk? Or SUperSU?
Shall I try another custom ROM? Or another version of lineageOS? (Oh, yes, I tried Lineageos 15.0, but I got 'ZIP error'.
Thanks for your help!

Fussloseskriechtier said:
Hello,
this is my situation:
- switchin-on my new moto e4 (XT1762)
- boot into recovery (TWRP)
- in TWRP, I am able to 'work', i.e. install LineageOS 15.1 (this is my main goal)
--- I WIPE
--- I INSTALL the lineage ZIP file (lineage 15.1 20180310 unofficial woods
--- I REBOOT
BUT, sadly, the reboot is done again into TWRP.
The installation of lineageos did not report any error.
How can I check, that what I've installed so far (TWRP and magisk) is correct and working?
Did I forget something? E.g. do I have to install GAPPS as well? Or Magisk? Or SUperSU?
Shall I try another custom ROM? Or another version of lineageOS? (Oh, yes, I tried Lineageos 15.0, but I got 'ZIP error'.
Thanks for your help!
Click to expand...
Click to collapse
I imagine you are having the same problem that I was having. This is what I think happened, there is a particular partition which TWRP fails to erase, if this is the case I believe you are able to boot into the device by hitting start in the bootloader, hold volume down and power then select start. Tell me how it goes

TWRP loop
frederickrl said:
I imagine you are having the same problem that I was having. This is what I think happened, there is a particular partition which TWRP fails to erase, if this is the case I believe you are able to boot into the device by hitting start in the bootloader, hold volume down and power then select start. Tell me how it goes
Click to expand...
Click to collapse
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?

Fussloseskriechtier said:
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?
Click to expand...
Click to collapse
I have no other recommendations as to what to do. Just flash stock firmware with rsdlite and everything will be back to normal, if you have any data that you need to back up you can use TWRP to transfer the files to a PC

Fussloseskriechtier said:
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?
Click to expand...
Click to collapse
In twrp select reboot bootloader. In bootloader, tap volume until you see "start". Tap power. Do not try holding buttons together in bootloader. It doesn't do anything. Single taps.

madbat99 said:
In twrp select reboot bootloader. In bootloader, tap volume until you see "start". Tap power. Do not try holding buttons together in bootloader. It doesn't do anything. Single taps.
Click to expand...
Click to collapse
After "REBBOT BOOTLOADER" in TWRP, I get a black screen, where (on the very bottom) there are two lines: => FASTBOOT mode
=> device unlocked
Tapping or holding the volume&power buttons does not work in this state.
As mentioned before, by any reason I do not have this nice menue anymore, the one with RECOVERY, START, ...
So this could be the problem, right? Is my bootloader not working properly? Which part is telling the device to startup either in TWRP (=recovery) or into the Bootloader/System?
Mmmmh....

Fussloseskriechtier said:
After "REBBOT BOOTLOADER" in TWRP, I get a black screen, where (on the very bottom) there are two lines: => FASTBOOT mode
=> device unlocked
Tapping or holding the volume&power buttons does not work in this state.
As mentioned before, by any reason I do not have this nice menue anymore, the one with RECOVERY, START, ...
So this could be the problem, right? Is my bootloader not working properly? Which part is telling the device to startup either in TWRP (=recovery) or into the Bootloader/System?
Mmmmh....
Click to expand...
Click to collapse
Fastboot mode is bootloader. Why the options aren't there I couldn't tell you. I see you flashed a rom for woods. Do you have the mediatek version? Hopefully you didn't flash wood stuff on a Perry device. Bootloader may be different. I have Qualcomm. Was that option ever there in fastboot mode?
This is how to fix the recovery loop. And possibly boot you in to whatever is left of your os.

madbat99 said:
Fastboot mode is bootloader. Why the options aren't there I couldn't tell you. I see you flashed a rom for woods. Do you have the mediatek version? Hopefully you didn't flash wood stuff on a Perry device. Bootloader may be different. I have Qualcomm. Was that option ever there in fastboot mode?
This is how to fix the recovery loop. And possibly boot you in to whatever is left of your os.
Click to expand...
Click to collapse
Thanks again for your hints!
First of all, my device variant is XT1762, i.e. woods. I did not use PERRY software.
The bootloader options (RECOVERY MODE, FACTORY MODE, etc.) were there, but it seems I've somehow broken this peace of code... I believe this is the reason of my problems. Unfortunately I do not understand the Android boot sequence...
However, I tried >> fastboot erase misc << via terminal:
result:
erasing 'misc'...
FAILED (remote: partition table doesn't exist)
finished. total time 0.009s
I double checked it vie file manager in TWRP: there is no MISC folder.
It seems, my only option is to go back to stock ROM... :crying:

Fussloseskriechtier said:
Thanks again for your hints!
First of all, my device variant is XT1762, i.e. woods. I did not use PERRY software.
The bootloader options (RECOVERY MODE, FACTORY MODE, etc.) were there, but it seems I've somehow broken this peace of code... I believe this is the reason of my problems. Unfortunately I do not understand the Android boot sequence...
However, I tried >> fastboot erase misc << via terminal:
result:
erasing 'misc'...
FAILED (remote: partition table doesn't exist)
finished. total time 0.009s
I double checked it vie file manager in TWRP: there is no MISC folder.
It seems, my only option is to go back to stock ROM... :crying:
Click to expand...
Click to collapse
I think the partitions are different in mtk version. But I would try flashing stock.

I have exactly the same problem after trying to flash lineage 14.1 to my XT1762.
Unfortunately I have only a TWRP Backup of my stock system before the flash and recovering that didn't fix the problem.

Fussloseskriechtier said:
Perhaps any other hints?
Click to expand...
Click to collapse
MiGri said:
I have exactly the same problem after trying to flash lineage 14.1 to my XT1762.
Unfortunately I have only a TWRP Backup of my stock system before the flash and recovering that didn't fix the problem.
Click to expand...
Click to collapse
I know what a pain in the ass my Perry variant was just to get the root going, so I can just imagine your frustration.
Did you guys take the update they're pushing out on the phones? Check. Some of the updates might be forced or you may accidentally said Okay and didn't realize it- that could be the reason why you're having trouble. The significant other got an update on the E4, and now can't do root.

I was able to get my phone back to work using https://forum.xda-developers.com/moto-e4/development/rom-original-stock-firmware-woods-twrp-t3766902

Stock ROM used to repair bootloader
Articul8Madness said:
I know what a pain in the ass my Perry variant was just to get the root going, so I can just imagine your frustration.
Did you guys take the update they're pushing out on the phones? Check. Some of the updates might be forced or you may accidentally said Okay and didn't realize it- that could be the reason why you're having trouble. The significant other got an update on the E4, and now can't do root.
Click to expand...
Click to collapse
Hello!
In the meantime I actually deleted everything and flashed the Stock ROM on my XT1762.
After that, my Bootloader menue (RECOVERY MODE, FACTORY MODE, START, ...) appeared again...
I felt lucky and started the whole procedure again: use TWRP, backup, delete Cache, Flash custom ROM, delete Cache, restart... and finally, I got lineageOS 15.1 and CrDroid running on my phone.
Now I use CrDroid, because LineageOS 15.1 did not Support my SIM Card... ? However, I am happy with CrDroid: fast, slim, nice looking, ...
So in the end, it seems that I deleted a specific part in my Flash which caused the "boot Loop". But I could repair it by flashing the Stock ROM again.
Thanks guys, you're doing a good Job!
Buy!

Fussloseskriechtier said:
Hello!
In the meantime I actually deleted everything and flashed the Stock ROM on my XT1762.
After that, my Bootloader menue (RECOVERY MODE, FACTORY MODE, START, ...) appeared again...
I felt lucky and started the whole procedure again: use TWRP, backup, delete Cache, Flash custom ROM, delete Cache, restart... and finally, I got lineageOS 15.1 and CrDroid running on my phone.
Now I use CrDroid, because LineageOS 15.1 did not Support my SIM Card... ? However, I am happy with CrDroid: fast, slim, nice looking, ...
So in the end, it seems that I deleted a specific part in my Flash which caused the "boot Loop". But I could repair it by flashing the Stock ROM again.
Thanks guys, you're doing a good Job!
Buy!
Click to expand...
Click to collapse
I'm also stuck in boot loop... What directories/files did you delete? Have backup of stock rom, but restore fails:
This /data backup was made with f2fs file system! The backup may not boot unless you change back to f2fs
Failed to mount /data (Invalid argument)
TWRP says that file system of /data is ext4. Not possible to change or repair the file system in TWRP with Wipe / Advanced wipe / Repair or change file system. Result:
Error changing file system
or
/sbin/e2fsck -fp /dev/block/mmcblk0p27 process ended with error: 8
Phone is always starting in TWRP ending with:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
In terminal no problem to create (mkdir) and delete directories.
Flashing of lineage 14.1 or 15.1 for woods ends also with:
Failed to mount '/data' (Invalid argument)
This command in TWRP terminal didn't work:
fastboot erase misc
erasing 'misc'...
FAILED (remote: Partition table doesn't exist)
There is no misc folder.
Any ideas?
Thank you in advance!

pancobe said:
I'm also stuck in boot loop... What directories/files did you delete? Have backup of stock rom, but restore fails:
This /data backup was made with f2fs file system! The backup may not boot unless you change back to f2fs
Failed to mount /data (Invalid argument)
TWRP says that file system of /data is ext4. Not possible to change or repair the file system in TWRP with Wipe / Advanced wipe / Repair or change file system. Result:
Error changing file system
or
/sbin/e2fsck -fp /dev/block/mmcblk0p27 process ended with error: 8
Phone is always starting in TWRP ending with:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
In terminal no problem to create (mkdir) and delete directories.
Flashing of lineage 14.1 or 15.1 for woods ends also with:
Failed to mount '/data' (Invalid argument)
This command in TWRP terminal didn't work:
fastboot erase misc
erasing 'misc'...
FAILED (remote: Partition table doesn't exist)
There is no misc folder.
Any ideas?
Thank you in advance!
Click to expand...
Click to collapse
Just flash stock firmware with rsdlite, it's the simplest way to go. Then if you'd like flash your rom

frederickrl said:
Just flash stock firmware with rsdlite, it's the simplest way to go. Then if you'd like flash your rom
Click to expand...
Click to collapse
Thank you for the hint on rsdlite, didn't know the program! Unfortunately I have two problems, have only access to an old XP box (I'm normally on a mac), and rsdlite doesn't recognise the phone, driver problem presumably... And the program doesn't recognise the format of the backup I made with TWRP...
Is it possible to repair the file system on the phone via terminal? Or to delete parts of the system safely and reinstall the stock system? The other guy apparently did something like that. Or to unpack a custom rom and place the parts via terminal so it can install on next boot?
Thank you!

Did following check:
mount /data
mount: '/dev/block/mmcblk0p27'->'/data': Invalid argument
e2fsck -n /dev/block/mmcblk0p27
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p27
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Would it be safe to rmdir /data and mkdir /data ?
Thanks...

pancobe said:
Thank you for the hint on rsdlite, didn't know the program! Unfortunately I have two problems, have only access to an old XP box (I'm normally on a mac), and rsdlite doesn't recognise the phone, driver problem presumably... And the program doesn't recognise the format of the backup I made with TWRP...
Is it possible to repair the file system on the phone via terminal? Or to delete parts of the system safely and reinstall the stock system? The other guy apparently did something like that. Or to unpack a custom rom and place the parts via terminal so it can install on next boot?
Thank you!
Click to expand...
Click to collapse
Rsdlite is not meant to install your twrp backup. It's for installing the official firmware package. And you need to install moto drivers of course.