Develop Bugs

Moto e4 (XT1768): Unlock Bootloader/root permission - corrupted /system partition

Hi,
This is less of a question and more of an experience. That being said, if anyone has any suggestions, I still do not have a correctly mounted /system partition (I think).
Background:
I am new to the world of custom ROM's and the community with which it resides. I did dabble in it a few years back with the original casio commando, but that was before I ever touched a linux machine or read a line of code. I decided to mess with my new Moto e4 (XT1768), mostly to remove bloatware and maybe flash a custom ROM, though I did like the factory.
Procedure:
I unlocked the bootloader and flashed a custom recovery (TWRP) through fast boot. Flashed Magisk and got superuser permissions. Everything seemed to go fine. I didn't notice it at first, so I'm not exactly sure which step caused it, but every time I would reboot the phone, it would boot to recovery.
I was able to boot into fastboot from TWRP. From there I could start the OS. So i ignored it. But upon trying to run system updates they would fail.
Problem:
NOW I decided this minor glitch was the result of a larger issue. Turns out, somewhere between flashing TWRP recovery and flashing Magisk, I inadvertently removed/corrupted my /system partition. I get a error on reboots "unable to mount partition." When I tried to flash a custom rom RR, it would raise errors about /system not existing. In the TWRP "mount" menu, "system is unchecked, even when I check it and reboot. When I reboot the bootloader from TWRP I would get a msg NO OS Installed. This last one is contradictory because I can still access the OS, could make calls, etc.
Troubleshooting:
I tried remounting the /system partion, though I don't think I did it correctly. I couldn't find much about fixing partitions, and do not feel like breaking my phone, since it still works. Unfortunately I did not take a backup of the factory installation (won't do that again). The only backup I had was after the bootloader was unlocked and Magisk was installed. Rolling it back to this image, I am able to flash RR custom rom and it works fine, though the original issue still exists. I tried a few attempts to remove Magisk from the backup image, but results in a boot loop when booting to the OS. When it went well, I was able to boot straight to the OS, without it automatically booting to recovery, but the boot loop prevented any advancement.
I so far have not seen this particular issue happen to anyone else. If you have any suggestions, or advice on where to find a compatible factory ROM for the Moto e4 (XT1768), send them over. I've tried to flash a factory ROM that was close to my model, but no luck. If anyone has run into this probem, let me know so I don't think I'm the only one out here.
Nich

I know of one instance which can cause rebooting to result in recovery mode and system mount issues, as well as a solution to resolve it. When installing firmware via fastboot, or any other files via fastboot (even unlocking the bootloader with fastboot), it is extremely important that your first command is this:
fastboot oem fb_mode_set
And your last command this:
fastboot oem fb_mode_clear
Sometimes, a failure to initiate and close fastboot with the above command lines will result in exactly what you are describing. Of course, to fix the issue, you will need to flash a compatible stock firmware package with the opening and closing lines I've listed. I will check my sources and try to find a package for your model.
Update: I have found a factory firmware package for the xt1768, which I am downloading now. I'll get you a link as soon as I get it downloaded, then uploaded to my cloud host.

Amazon xt1768 Moto E4 stock firmware package -- Build No. NPQS26.69-64-8
https://drive.google.com/file/d/12hABSzvUpSZOYEUdX5ssCXYZmjA-Z10n/view?usp=drivesdk

nich42 said:
I so far have not seen this particular issue happen to anyone else. If you have any suggestions, or advice on where to find a compatible factory ROM for the Moto e4 (XT1768), send them over. I've tried to flash a factory ROM that was close to my model, but no luck. If anyone has run into this probem, let me know so I don't think I'm the only one out here.
Click to expand...
Click to collapse
If you have a retail (aka open market) XT1768 - you can get firmware from here. The one at the bottom dated September 18th is the most recent.
The Amazon one posted by MotoJunkie01 may have differences from the this one (i.e. Amazon apps/branding).

hitokage004 said:
If you have a retail (aka open market) XT1768 - you can get firmware from here. The one at the bottom dated September 18th is the most recent.
The Amazon one posted by MotoJunkie01 may have differences from the this one (i.e. Amazon apps/branding).
Click to expand...
Click to collapse
Thanks everyone. Yeah I have the open market version. I'll give these a look.
MotoJunkie01, I have not seen these commands before, which would probably explain why I broke it. Thanks I'll try and implement them.
fastboot oem fb_mode_set
And your last command this:
fastboot oem fb_mode_clear

nich42 said:
Thanks everyone. Yeah I have the open market version. I'll give these a look.
MotoJunkie01, I have not seen these commands before, which would probably explain why I broke it. Thanks I'll try and implement them.
fastboot oem fb_mode_set
And your last command this:
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
This is probably a dumb question. How do I flash it with fastboot? I've only installed a ROM from TWRP, so not sure how to run it from fast boot. do I need to install each partition separately or is there a flash-all file. I notice the flashfile file has a lot of command like arguments in it. Can I use that?
Thanks,

nich42 said:
This is probably a dumb question. How do I flash it with fastboot? I've only installed a ROM from TWRP, so not sure how to run it from fast boot. do I need to install each partition separately or is there a flash-all file. I notice the flashfile file has a lot of command like arguments in it. Can I use that?
Thanks,
Click to expand...
Click to collapse
Yes if you flash it with fastboot you do it one image at a time. You can also install RSD Lite on a Windows computer and it will do it all for you by selecting either the flashfile.xml or the service file. XML.

UPDATE:
Thanks for the assistance. I know it's been a while, but I've been busy the past few months.
I found a guide that had all the pieces I was looking for. As far as I can tell it went well, though it doesn't seem to be completely back to normal. I was able to unmount the recovery partition, but it was not re-mounted/installed.
I plan to unlock and install TWRP as the recovery. I may also try and root the phone, but keep the factory OS. But we'll see...

TWRP Freeze - close call?

Hi,
I had the bootloader unlocked on my 6.1 today.
Seemed to go well and guy was ver y professional.
Anyway connected my pc, and through adb rebooted to bootloader.
Phone entered download/fastboot mode.
Was recognised by my pc so I then booted into a temporary twrp - I got the image from the twrp site as compatible with the device.
Up came the twrp opening screen
--and that was that?
Did not go beyond this screen, and phone became completely unresponsive- not even holding power button for a minute helped.
Oh dear.
Fortunately, I left it for a couple of minutes and then held power and volume up for quite a while, and ''whew'' it booted fine, and is back to normal?
ANy ideas what I did wrong?
Many Thanks
pootler

pootler said:
Hi,
I had the bootloader unlocked on my 6.1 today.
Seemed to go well and guy was ver y professional.
Anyway connected my pc, and through adb rebooted to bootloader.
Phone entered download/fastboot mode.
Was recognised by my pc so I then booted into a temporary twrp - I got the image from the twrp site as compatible with the device.
Up came the twrp opening screen
--and that was that?
Did not go beyond this screen, and phone became completely unresponsive- not even holding power button for a minute helped.
Oh dear.
Fortunately, I left it for a couple of minutes and then held power and volume up for quite a while, and ''whew'' it booted fine, and is back to normal?
ANy ideas what I did wrong?
Many Thanks
pootler
Click to expand...
Click to collapse
Ok so quick update
I decided to use a different recovery
I was installing lineages 17, so used their recovery.
Everything worked fine?

HI,
I obtained a nokia 6.1 recently.
I had the bootloader unlocked.
I then went to flash the latest ( official) lineage 17
I did all the usual stuff ( i am not a stranger to installing custom roms ), and then tried to temporarily boot into twrp, in order to flash the lineage zip.
I was using the twrp as recommended on lineage site for this device ( nokia 6.1 TA 1050 )
For some reason, after using fastboot boot twrp.img, ( I renamed the image) the phone just booted back to android one screen.?
I could use power/vol up, to get out and back to existing installation, but nothing else.
I then tried temporarily booting the lineage recovery. ( according to the lineage installation instructions)
This involves using a combination of ''fastboot flash boot'' and hardware keys to get there
This worked fine - and I was able to sideolad the lineage zip.
Problem is, if I want to flash images , and do other stuff the lineage recovery cant, i need twrp ( even temporarily).
After installing lineage 17, I tried again to get into twrp, with the same (non) results.
I was wonderinfg if I was getting confused about slots.
I believed that booting twrp temporarily would boot to the right slot? - maybe not.
I then decided to do fastboot flash boot_a, ( etc, ) and then fastboot flash boot_b, ( etc ) to make sure it would boot off either slot. With hindsight, this was dumb
That got me twrp., but lost me the ability to boot into the lineage installation.
After a bit of a panic, I managed to get back to my lineage install.
I have tried since to temporarily boot twrp ( not to both slots ), and am still getting the same results- it boots to the android one screen, and just sits there.
But - if I try to get to recovery using the hardware buttons, I can get to Lineage recovery - which I find strange, because I thought official lineage packages did not install their recovery by default?
Makes me wonder when I thought I had booted lineage recovery temporarily, that maybe I hadn't, and I just booted into a pre installed recovery using the hardware method.
I am probably doing something stupid ( quite common for me ), can anyone enlighten me ?
Many Thanks
pootler

O.k
So I think I found a method in the thread below this - on the third page
I will chek iif it works
Pootler

pootler said:
O.k
So I think I found a method in the thread below this - on the third page
I will chek iif it works
Pootler
Click to expand...
Click to collapse
Yes - it appears that if you cannot boot into twrp temporarily , then this worked for me!
--at your own risk---
fastboot flash recovery <filename>.img
This will FAIL - but ignore and then right after,
fastboot boot <filename> .img
Voila - boots into TWRP temporarily.
Cheers
pootler

I wanted to ask what firmware you are running because I am having the exact same issue on my Pixel 3. I tried the final method you outlined but no luck. I'm running stock Android 10 build QQ3A.200805.001. I have the google USB driver from the platform sdk tools installed, I have ADB added to my $Path.
fastboot boot C:\twrp-3.3.0-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.251s]
Booting OKAY [ 3.451s]
Finished. Total time: 3.784s
Something strange happens, it looks like the reboot to TWRP screen comes on for an instant before going to the unlocked bootloader warning message. Then it proceeds to boot into the android screen instead of the recovery. No idea why, could it be the ADB drivers?

MigueTK said:
I wanted to ask what firmware you are running because I am having the exact same issue on my Pixel 3. I tried the final method you outlined but no luck. I'm running stock Android 10 build QQ3A.200805.001. I have the google USB driver from the platform sdk tools installed, I have ADB added to my $Path.
fastboot boot C:\twrp-3.3.0-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.251s]
Booting OKAY [ 3.451s]
Finished. Total time: 3.784s
Something strange happens, it looks like the reboot to TWRP screen comes on for an instant before going to the unlocked bootloader warning message. Then it proceeds to boot into the android screen instead of the recovery. No idea why, could it be the ADB drivers?
Click to expand...
Click to collapse
HI,
I am sorry but my knowledge is really limited in this area - I wish you luck

pootler said:
HI,
I am sorry but my knowledge is really limited in this area - I wish you luck
Click to expand...
Click to collapse
Thanks for the reply, I still haven't figured it out and am running a manually patched boot image for magisk without a recovery, fastbootd is "enough". Another weird thing is If I installed a custom Rom certain pixel features would be lost such as the OCR and lens integration into the recents menu, pixel stand standby and wallpapers. I love the features of a custom Rom but the overview copy and paste functions are a must have for me.

Well, I use Raghu Varma's unofficial TWRP. It works like a charm, I've had no issues with it so far. Just be careful to choose the correct one between the build for Android 10 and the one for Android 11 -- I think that got me into trouble once, can't remember clearly.

weird pe 12 rom flash. not loading to system. help pls

got unlucky (or dumb) during an attempt to install pixel experience. something like a detective story
firstly i wrote vbmeta and twrp. ive got smth like a fastboot loop. i used different twrp and it booted into it well. tho noticed that the folders in "install" menu turned into something you get when you fall asleep on a keyboard (names like "303ujdw09ejcf09ejf"). the phone memory was inaccessible from pc.
so i wiped internal memory and it got fine. except the inability to mount system and stuff. trying to flash a room gave me errors like "failed to mount /system (np such directory)" etc.
then i tried different twrp build and it worked well and i even managed to flash pixel experience 12.
formatted and was happy as never. pressed a button to load into sys. but it took me to fastboot where it was reloading itself infinitely. an attempt to load into recovery gave me a twrp logo flickering screen.
i feel like there’s a tiny stupid mistake that i make
btw sorry for my partial incompetence. im much more of a front end dev rather then that deep end stuff
i woulld be very thankful for any reply, the whole situation gives such a frustration and sadness

the original stystem was RMX2063_11_A.51
then i maneged to upgrade to PixelExperience_RMX2061-12.0-20220121-1131-UNOFFICIAL
but now i only have the flickering screen with twrp logo

human_person2402 said:
the original stystem was RMX2063_11_A.51
then i maneged to upgrade to PixelExperience_RMX2061-12.0-20220121-1131-UNOFFICIAL
but now i only have the flickering screen with twrp logo
Click to expand...
Click to collapse
Use Ofox A11+.
Format data either from recovery or using fastboot -w.

debdeep98 said:
Use Ofox A11+.
Format data either from recovery or using fastboot -w.
Click to expand...
Click to collapse
thanks for reply
but theres a problem with ofox installation. when i tried to flash it from twrp it automaticly restarts and i just get to fastboot where it restarts itself over and over. im simply not able to load into anything

human_person2402 said:
but theres a problem with ofox installation. when i tried to flash it from twrp it automaticly restarts and i just get to fastboot
Click to expand...
Click to collapse
Flash it from fastboot.
Boot into ofox.
Flash the ROM.

Question Failed to load/authenticate boot image

Good Day All, I've seen a few thread regarding this but nothing stating what causes it to happen. Can anyone provide any insight?
I was about to perform a reflash of my rom but didn't even reach that far.
I restarted phone to recovery
Was going flash a firmware before the rom flash but decided to switch from slot a to b cuz i wasn't sure if the firmware is a global thing or per slot
Changed slots and restarted to recovery
Noticed no prompt for decryption key and my data/media was gone.
Changed slots again without doing anything and restarted (TWRP prompted no OS found)
After the recovery started again no prompt for decryption key again and no data
Figured twrp loaded badly or something. Restarted to recovery one more time
Phone did not boot to recovery. Keep bootlooping to fastboot
Attempted to reflash TWRP when I encounted the error "Failed to load/authenticate boot image"
After a quick google the solution seemed to be the flash over the stock rom via miflash and start over which I unfortunately did
While the solution worked. Does anyone have any clue why this might've happened so I can avoid it in the future? I don't think the Rom matters but I was running Arrow-v12.1-alioth-OFFICIAL-20220819-VANILLA.zip and the recommended firmware V13.0.4.0.SKHMIXM

Xiaomi Mi 10T keeps booting into fastboot

Hello guys, I recently formatted data on my phone to fix a bootloop I had. After fixing everything, SIM card and wifi was not working, I downloaded the Official Stock ROM of my phone and flashed bluetooth, modem, dsp and dtbo. The original plan was to run "flash_all_except_storage.bat" but that kept throwing errors. After I flashed those things I booted successfully and unlocked my phone. Problem is Wifi still doesn't work. So once again got into fastboot, tried running "flash_all_except_storage.bat", once again it threw an error, so I restarted my phone and ever since I can't boot into system. Whenever I restart it goes straight into fastboot, Power off and on again goes to fastboot, I can boot into TWRP, rebooting from there still goes into fastboot mode. I fix a problem and 2 more take it's place, I really need your help here.
Thanks a lot !
Edit:
Fix Attempt 1 (FAILED): I tried formating data through TWRP as I read online, it did not work
Attempt 2 (FAILED): Used
Code:
fastboot continue
and got this error:
Code:
Resuming boot FAILED (remote: 'Failed to load image from partition: No Media')
fastboot: error: Command failed
Attempt 3 (HALF FIX): After some digging I realized after a failed attempt to run "flash_all_except_storage.bat", the boot was erased. I tried flashing only the boot.img and the phone booted up with the wifi working as well. Problem is after a reboot I go back into fastboot and I have to flash boot.img again to boot into system.
Here is recovery.log Pastebin

Leonniar said:
Hello guys, I recently formatted data on my phone to fix a bootloop I had. After fixing everything, SIM card and wifi was not working, I downloaded the Official Stock ROM of my phone and flashed bluetooth, modem, dsp and dtbo. The original plan was to run "flash_all_except_storage.bat" but that kept throwing errors. After I flashed those things I booted successfully and unlocked my phone. Problem is Wifi still doesn't work. So once again got into fastboot, tried running "flash_all_except_storage.bat", once again it threw an error, so I restarted my phone and ever since I can't boot into system. Whenever I restart it goes straight into fastboot, Power off and on again goes to fastboot, I can boot into TWRP, rebooting from there still goes into fastboot mode. I fix a problem and 2 more take it's place, I really need your help here.
Thanks a lot !
Edit:
Fix Attempt 1 (FAILED): I tried formating data through TWRP as I read online, it did not work
Attempt 2 (FAILED): Used
Code:
fastboot continue
and got this error:
Code:
Resuming boot FAILED (remote: 'Failed to load image from partition: No Media')
fastboot: error: Command failed
Attempt 3 (HALF FIX): After some digging I realized after a failed attempt to run "flash_all_except_storage.bat", the boot was erased. I tried flashing only the boot.img and the phone booted up with the wifi working as well. Problem is after a reboot I go back into fastboot and I have to flash boot.img again to boot into system.
Here is recovery.log Pastebin
Click to expand...
Click to collapse
Can you flash full rom with mi flash tool

Rares6567 said:
Can you flash full rom with mi flash tool
Click to expand...
Click to collapse
Already did, it didn't work...

Leonniar said:
Already did, it didn't work...
Click to expand...
Click to collapse
Maybe is some motherboard issues?

I don't believe so. The problem I originally had was that after a restart the phone was booting into fastboot. But if I didn't restart the phone was working fine, cellular, wifi google services everything. So in order to fix that I flashed the full stock rom and that's how I ended up in the restart loop in the first place.
https://forum.xda-developers.com/t/decrypting-xiaomi-mi10t-pro-internal-storage.4544271/page-2#posts
Here are all the details, I started from a completely different problem and ended up here. They entire process I took is in that thread

Leonniar said:
I don't believe so. The problem I originally had was that after a restart the phone was booting into fastboot. But if I didn't restart the phone was working fine, cellular, wifi google services everything. So in order to fix that I flashed the full stock rom and that's how I ended up in the restart loop in the first place.
https://forum.xda-developers.com/t/decrypting-xiaomi-mi10t-pro-internal-storage.4544271/page-2#posts
Here are all the details, I started from a completely different problem and ended up here. They entire process I took is in that thread
Click to expand...
Click to collapse
There is no volume buttons problem?
If no maybe you should reflash whole phone, fastboot, recovery, all, using edl ig.... I don't have this phone or any Snapdragon phone, so I don't really know....

Yeah I did, I used the flash_all.bat that comes with the ROM file and pretty much replaced everything. I tried to run it a couple of times and it failed mostly but I was able to run it twice I think (without changing anything, just running it again and again at some point it worked)

Leonniar said:
Yeah I did, I used the flash_all.bat that comes with the ROM file and pretty much replaced everything. I tried to run it a couple of times and it failed mostly but I was able to run it twice I think (without changing anything, just running it again and again at some point it worked)
Click to expand...
Click to collapse
So then why your phone goes to fastboot?

I really don't know, after running flash_all the second time now my phone is stuck in a restart loop. Shows the MI logo and restarts. I can manually boot to recovery or fastboot but if I leave it on it's own it keeps turning on and off

Leonniar said:
I really don't know, after running flash_all the second time now my phone is stuck in a restart loop. Shows the MI logo and restarts. I can manually boot to recovery or fastboot but if I leave it on it's own it keeps turning on and off
Click to expand...
Click to collapse
It seems that this a software bug ig, can you try go to recovery and flash the rom?

I could try but I am not sure how to do that. My rom comes in a .tgz format and not .zip and all guides mention you need a .zip file

Leonniar said:
I could try but I am not sure how to do that. My rom comes in a .tgz format and not .zip and all guides mention you need a .zip file
Click to expand...
Click to collapse
So where u downloaded the fastboot rom, there is a recovery rom too :
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Be sure u download the recovery rom not fastboot.
Btw use your miui version u had

Tho I'm not 100% sure if you flashed the fastboot rom correctly, did u :
1. Open MiFlashTool : download the tool from here if you don't have it ---> https://xiaomiflashtool.com/
2. Select your rom ( make sure your path to the rom isn't long and the folder/folders don't have long names )
3. Connect your phone
4. Click Refresh ( to make your device appear)
5. And click flash

I didn't do it with MiFlashTool because it kept throwing errors at me whenever I launched it so I tried the flash_all.bat batch file that runs cmd commands and flashes everything. the ROM I installed was the fastboot version. The official website on the recovery ROM stated that "This page shows a single update only" so I assumed it's just an update and not the full ROM. I was also told I should use the fastboot variant in the above mentioned thread

Leonniar said:
I didn't do it with MiFlashTool because it kept throwing errors at me whenever I launched it so I tried the flash_all.bat batch file that runs cmd commands and flashes everything. the ROM I installed was the fastboot version. The official website on the recovery ROM stated that "This page shows a single update only" so I assumed it's just an update and not the full ROM. I was also told I should use the fastboot variant in the above mentioned thread
Click to expand...
Click to collapse
Ok so to fix the error : go to miflashtool folder and create a new folder called : log

Fixed the start up error, I get the screen that says "Please install driver", I press Install and I get this:
https://prnt.sc/I53g6bs_8i5w
Pressing ok gets me back to the "Please install driver" screen

Well I just closed the Install driver window and flashed as is, I got this:
https://prnt.sc/Bk2eaj9w5Lq7 so presumably it failed but my devices rebooted and is now on system set up
Edit:
3 reboots later and phone still boots fine to system

Rares6567 said:
It seems that this a software bug ig, can you try go to recovery and flash the rom?
Click to expand...
Click to collapse
flashing miui_APOLLOEEAGlobal_V12.5.4.0.RJDEUXM_451a2324af_11.0.zip from stock recovery is good idea, you can do this from MicroSD card to circumvent any usb issues you are obviously facing on fastboot.

Leonniar said:
Well I just closed the Install driver window and flashed as is, I got this:
https://prnt.sc/Bk2eaj9w5Lq7 so presumably it failed but my devices rebooted and is now on system set up
Edit:
3 reboots later and phone still boots fine to system
Click to expand...
Click to collapse
So it worked?
This "error" isn't an "error" so don't worry about it

Leonniar said:
Well I just closed the Install driver window and flashed as is, I got this:
https://prnt.sc/Bk2eaj9w5Lq7 so presumably it failed but my devices rebooted and is now on system set up
Edit:
3 reboots later and phone still boots fine to system
Click to expand...
Click to collapse
This error is normal since you are not re-locking the bootloader.
If some functions are inoperative.
Try to flash the same rom (fastboot) that you had when you bought the phone, probably an A11.
Use clean all(flash_all.bat).
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/