Database Users

Bricked? can't mount sdcard

tried a new rom, wiped, flashed, rebooted then it had sdcard mount problems thought it was the rom so i wiped and then tried to flash with no luck it says
build: RA-sapphire-v1.5.2H
E:Can't mount /dev/block/mmcblk0p1 (or dev/block/mmblk0)
(No such file or directory)
E:Can't mount SDCARD
Boots RA-sapphire-v1.5.2H and fastboot just fine
SAPPHIRE PVT 32A
HBOOT-1.33.2010 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
So can't flash any new roms...
is the phone bricked?
Really need some help here i'm stuck

It´s no bricked dude. Try remove ur sdcard and insert again.
Good luck.

Allready tried that and tried several sdcards, all cards worked before and is working on the pc

Try enable sdcard via usb toggle in RA-recovery. Insert usb cable into phone and pc. Check if your pc recognize your sdcard.

Tried to enable USB-MS no luck in windows

Try clicking the flash button a whole bunch of times, sometimes it just takes a while; I've only seen this on the hero recovery, though.

also tried that

Sorry to hear that.
So can't flash any new roms...
is the phone bricked?
Really need some help here i'm stuck
Click to expand...
Click to collapse
If it's any consolation, you're not bricked! You can install everything using fastboot, you'll have to scour the forums or google, but you should be able to find the instructions to flash an install this way. Generically it will be something like:
Code:
./fastboot erase system -w
./fastboot flash boot ./misc/boot.img
./fastboot flash system ./misc/system.img
./fastboot flash userdata ./misc/userdata.img
Sorry, I can't provide more details, right now.

Btw an actual brick is when you can't even fastboot or get into recovery.
Far as the SD card have you tried to format it with a PC via a card reader?

Searched alot if anyone could provide a link it would be great, sound good that i'm not bricked!!!
tried to format 2 different cards on the pc

did you make a nandroid backup before you flashed the new rom? if so then y not try and load the backup.

Should be same if another rom or nandroid backup through fastboot?

1) Go into fastboot
2) fastboot erase system -w (do it about 5 times in a row.)
3) Completely power down your phone. (battery out, wait)
4) Go into fastboot.
5) Repeat number 2.
6) Complete power down. (remove battery).
7) Boot into recovery.
8) Test sdcard.
Follow these steps exactly and it might work.
I had this same problem from a bad flash.
Hope it works for you.

Still nothing
TigerTael said:
1) Go into fastboot
2) fastboot erase system -w (do it about 5 times in a row.)
3) Completely power down your phone. (battery out, wait)
4) Go into fastboot.
5) Repeat number 2.
6) Complete power down. (remove battery).
7) Boot into recovery.
8) Test sdcard.
Follow these steps exactly and it might work.
I had this same problem from a bad flash.
Hope it works for you.
Click to expand...
Click to collapse

Okay,
My situation, after a bad flash (which I did not actually know was a bad flash), my SDcard reader in my phone would not read an SDcard at all. It would detect that one had been inserted, but acted as if nothing was there.
Also, my hboot showed that my bootloader was now 'S-ON' and not 'S-OFF'.
I was getting denied remote flash commands and everything.
After numerous wipes via recovery and then numerous wipes in fastboot, eventually one of the fastboot wipes fixed the problem.
I'm not 100% sure if it was a combination of erasing and then flashing a new ROM to system (via fastboot, not recovery) or what, but eventually my bootloader changed back to 'S-off' (What it always was for me) and then my SDcard could be read in the phone.
The key here was fastboot/hboot, and not recovery.

how did you flash a rom with fastboot? and which one?
S-ON is there in fastboot/hboot
also tried my nandroid backup with fastboot it says FAILED (remote: signature verify fail)
¤#"%¤#¤

Cronner said:
how did you flash a rom with fastboot? and which one?
S-ON is there in fastboot/hboot
Click to expand...
Click to collapse
In the "Rogers Mandatory Update" thread, post #139, there are clear instructions on flashing the stock Rogers ROM. I'm not suggesting you do this, though, I doubt you want the new radio, just use this as an example and search around for the files that are appropriate for what you want.
But really, I'd only resort to this to get the phone to boot and to try formatting the SD card.
Can you use adb to log into the phone?
Also, correct me if I'm wrong, but doesn't S-ON and S-OFF just indicate if the phone's locked to a carrier?

Solimian said:
In the "Rogers Mandatory Update" thread, post #139, there are clear instructions on flashing the stock Rogers ROM. I'm not suggesting you do this, though, I doubt you want the new radio, just use this as an example and search around for the files that are appropriate for what you want.
But really, I'd only resort to this to get the phone to boot and to try formatting the SD card.
Can you use adb to log into the phone?
Also, correct me if I'm wrong, but doesn't S-ON and S-OFF just indicate if the phone's locked to a carrier?
Click to expand...
Click to collapse
S-ON stands for security on, S-OFF, off. It's not locking to a carrier, but merely a security setting for the phone itself. There's a thread about it somewhere.
I don't think this has anything to do with formatting. As long as the SDcard can be read in another device such as a computer fine, I am still siding with the idea that it was a bad flash. I spent a day stressing that my SDcard reader on my phone was borked and now I would be screwed. Amon_Ra was there to offer support, but at the end of the day, after several wipes, the fastboot erase eventually got it to come right.
Amon_Ra and I summarised that somewhere a byte or a few bytes got written where it shouldn't have and corrupted some base code somewhere.

Solimian > is something wrong with the new radio?
yes adb and fastboot works now...
adb shell also works but can't mount sdcard there either!
C:\android>fastboot flash hboot hboot-1.76.2007.img
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
also tried: adb shell mount /sdcard
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory
and:
adb shell
/ # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory

TigerTael
TigerTael Please remind what you do, i have same problem

How to upgrade from rooted 1.5 to 2.2 on MT3G?

So...I'd really like to update to the 2.2 froyo mod but I get a script error when I'm trying. I can't even upgrade to cyanogen's 5.8 or whatever mod for some reason it gets stuck after installing on the boot up vodafone screen. I have a mytouch 3g 1.0 32b phone...do I need to update the radio or SPL in order to get any of these newer roms to work...how do I figure out which ones I need and what order should this be done in??

I have the exact same configuration (except I had 1.6 and had to downgrade to 1.5 first). I did not need to update the SPL or radio. Once I flashed 5.0.8, I got stuck at the boot screen. Then I wiped (on recovery screen Wipe --> All) and reflashed. This time, it worked like a charm. Which file are you using to flash?

anilo said:
I have the exact same configuration (except I had 1.6 and had to downgrade to 1.5 first). I did not need to update the SPL or radio. Once I flashed 5.0.8, I got stuck at the boot screen. Then I wiped (on recovery screen Wipe --> All) and reflashed. This time, it worked like a charm. Which file are you using to flash?
Click to expand...
Click to collapse
I don't remember off the top of my head...can you link me to the one you used? I had to do the same thing you did (downgrade from 1.6 to 1.5) so whatever you used should work for me...

Since I am a newb, the forum does not let me post URL's. I will send you a PM.

anilo said:
Since I am a newb, the forum does not let me post URL's. I will send you a PM.
Click to expand...
Click to collapse
I got your PM but I'm still having problems...I don't think have the right recovery thing installed (amonra or whatever?) because the only options I have when I reboot holding power + home are:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
nandroid v2.1.1 backup
nandroid 2.1.1 restore
I can't upgrade from zip files not named update.zip...and I can't even update the 5.0.8 file you linked me to even if I rename it to update.zip, it keeps giving me this error:
"e:cant mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (no such file or directory) e: cant mount sdcard:update.zip installation aborted."
I know when I had a G1 I was able to select a lot more options so my guess is I still need to change the amonrecovery? Do you know which one you're using or can you PM me a link to it?

Okay...so I found the recovery-RA-sapphire-v1.7.0G.img and am trying to upgrade it via the terminal by typing flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img and the first time I did this I didn't get a message or anything. I tried rebooting by holding down the power + the menu button but it just got stuck at the vodafone screen...
So I tried rebooting and going back into terminal emulator and doing it again, except now I get a long list of these errors:
mtd: read error at 0x00000000 (out of memory)
mtd: read error at 0x00020000 (out of memory)
and it just keeps going for like a page before it stops with different addresses...and now I can't get into a recovery at all....help!

colonelcack said:
Okay...so I found the recovery-RA-sapphire-v1.7.0G.img and am trying to upgrade it via the terminal by typing flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img and the first time I did this I didn't get a message or anything. I tried rebooting by holding down the power + the menu button but it just got stuck at the vodafone screen...
So I tried rebooting and going back into terminal emulator and doing it again, except now I get a long list of these errors:
mtd: read error at 0x00000000 (out of memory)
mtd: read error at 0x00020000 (out of memory)
and it just keeps going for like a page before it stops with different addresses...and now I can't get into a recovery at all....help!
Click to expand...
Click to collapse
install it via fastboot. that's a known issue with cm 5 and cm 6 roms.

Binary100100 said:
install it via fastboot. that's a known issue with cm 5 and cm 6 roms.
Click to expand...
Click to collapse
How do I actually install it onto my phone? I know the command to boot off an img file but whats the command to install it permanently so its always my recovery and I don't have to use fastboot every time?

colonelcack said:
How do I actually install it onto my phone? I know the command to boot off an img file but whats the command to install it permanently so its always my recovery and I don't have to use fastboot every time?
Click to expand...
Click to collapse
what the hell are you talking about???
Just fastboot flash recovery /computer/directory/recoveryfile.img
fastboot reboot

[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.

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.