Stuck at fastboot screen, but can't flash ROMs - Xiaomi Mi 4i
I've recently received a Mi4i device from a friend who messed it up a little.. This looks hopeless, but I thought I might get some insights from folks around here..
When I hit the power button, I immediately see the fastboot screen. I can still get into recovery mode.
I'm using MiFlash, connecting the phone, and the device is detected. I use "flash all" to flash one of the few mi4i fastboot ROMs I dug up from the web, install successful. Then, the device boots itself immediately back to the fastboot screen each time
I'm out of ideas.. Is there anything else I could try?
Nadav
It seems to be pressing volume keys all the time, hence might be going into fastboot mode
stoppnadav said:
I've recently received a Mi4i device from a friend who messed it up a little.. This looks hopeless, but I thought I might get some insights from folks around here..
When I hit the power button, I immediately see the fastboot screen. I can still get into recovery mode.
I'm using MiFlash, connecting the phone, and the device is detected. I use "flash all" to flash one of the few mi4i fastboot ROMs I dug up from the web, install successful. Then, the device boots itself immediately back to the fastboot screen each time
I'm out of ideas.. Is there anything else I could try?
Nadav
Click to expand...
Click to collapse
Download TWRP file and flash it via fastboot. Then try a custom ROM. While flashing the file you can try fastboot boot twrp.img to boot into recovery. Then when TWRP opens up it will grant access to the storage, copy the files for flashing a custom ROM, don't forget the firmware zip file too. Try this if it helps.
Regards,
Sharan
sharan.nyn said:
Download TWRP file and flash it via fastboot. Then try a custom ROM. While flashing the file you can try fastboot boot twrp.img to boot into recovery. Then when TWRP opens up it will grant access to the storage, copy the files for flashing a custom ROM, don't forget the firmware zip file too. Try this if it helps.
Regards,
Sharan
Click to expand...
Click to collapse
Is there any other way to flash TWRP via fastboot without using ADB? I had USB Debugging Off in my device, before it got stuck in a boot loop. I can only access FASTBOOT and RECOVERY .
zak31 said:
Is there any other way to flash TWRP via fastboot without using ADB? I had USB Debugging Off in my device, before it got stuck in a boot loop. I can only access FASTBOOT and RECOVERY .
Click to expand...
Click to collapse
Actually we don't use ADB to flash the recovery. We always use FASTBOOT. The commands are to be ran when booted in fastboot mode. Just make sure that all the required drivers are installed or the phone will reboot at FASTBOOT mode if it is not detected by your computer.
ADB drives showing error code 10
sharan.nyn said:
Actually we don't use ADB to flash the recovery. We always use FASTBOOT. The commands are to be ran when booted in fastboot mode. Just make sure that all the required drivers are installed or the phone will reboot at FASTBOOT mode if it is not detected by your computer.
Click to expand...
Click to collapse
That's what is happening with me I think. I have installed all the ADB drivers required. When I go to Device manager, those drives show little yellow triangles with a !. I proceed to update them, they get updated but error code 10 shows up. Also, now my device isn't getting detected by my computer, and rebooting at FASTBOOT mode continuously. Sometimes, it does get detected by the computer. I enter into FASTBOOT mode and I start the flashing with MiFlash, then the device reboots itself. Please help.
zak31 said:
That's what is happening with me I think. I have installed all the ADB drivers required. When I go to Device manager, those drives show little yellow triangles with a !. I proceed to update them, they get updated but error code 10 shows up. Also, now my device isn't getting detected by my computer, and rebooting at FASTBOOT mode continuously. Sometimes, it does get detected by the computer. I enter into FASTBOOT mode and I start the flashing with MiFlash, then the device reboots itself. Please help.
Click to expand...
Click to collapse
Install Mi suite. Probably that will solve the issue. ... hopefully. :silly:
I am also facing similiar problem..... after flashing twrp when rebooting twrp via fastboot teturns error dtb not found...... if someone can help
i have the same problem,
I try to flash with any version of rom,
when i see the fastboot device info,
the bootloader status
(bootloader) Device unlocked: false
Click to expand...
Click to collapse
then i do bootloader unlock,
and the bootloader status become
(bootloader) Device unlocked: true
Click to expand...
Click to collapse
but after fastboot reboot,
the status of bootloader become false again,
(bootloader) Device unlocked: false
Click to expand...
Click to collapse
anyone know what shoult i do?
stoppnadav said:
I've recently received a Mi4i device from a friend who messed it up a little.. This looks hopeless, but I thought I might get some insights from folks around here..
When I hit the power button, I immediately see the fastboot screen. I can still get into recovery mode.
I'm using MiFlash, connecting the phone, and the device is detected. I use "flash all" to flash one of the few mi4i fastboot ROMs I dug up from the web, install successful. Then, the device boots itself immediately back to the fastboot screen each time
I'm out of ideas.. Is there anything else I could try?
Nadav
Click to expand...
Click to collapse
Were you able to solve this problem?. I have the same issue since past week. MiFlash works, tried fastboot commandline flashing, device restarts to fastboot only.
loaded twrp, unfortunately internal memory 0mb.
Hi guys,
+1 from me
I've totally screwed up ferrari.
Scenario: I was on Resurrection Remix 5.8.5 For some reason, I've started storage encryption. Probably it wasn't successful, and on next reboot, I've got error "Decryption unsuccessful, your password is ok, but data partition is corrupted, blah, blah, blah. I've successful rescued my storage files:
Code:
boot into TWRP:
adb pull /dev/block/mmcblk0p36
then, mounted mmcblk0p36 partition file under Linux on my PC (example):
sudo mkdir /mnt/data
sudo mount /home/stiw47/mmcblk0p36 /mnt/data
Whoala, few files was corrupted, but all from android internal storage (my personal files) was rescued.
Ok. After this, I've performed factory reset on phone, but device going to fastboot, not in Android OS. TWRP says that /data cannot be mounted.
I flashed latest MIUI from fastbot
Reboot
device going to fastboot, not in Android OS. TWRP says that /data, /system and /cache cannot be mounted.
Variable : In following text, "same" is equal to "device going to fastboot, not in Android OS. TWRP says that /data, /system and /cache cannot be mounted."
I've tried to flash fastboot ROM zilion times - same
Tried to flash from MI PC Suite - same (MI Suite giving "success" info)
XiaoMI Flash Tool - same (tool giving success info)
Was want to flash with QFIL (Qualcomm Flash Image Loader), after several Qualcomm Xiaomi driver installation, founded here and there over the internet, on two different PCs - No COM port detected, both in QFIL and in Device Manager
[*]Wipe from TWRP not working:[*]Failed to mount '/system' (Invalid argument)
[*]Failed to mount '/cache' (Invalid argument)
[*]Failed to mount '/data' (Invalid argument)[*]Format Data from TWRP not working:[*]Failed to mount '/system' (Invalid argument)
[*]Failed to mount '/cache' (Invalid argument)
[*]Failed to mount '/data' (Invalid argument)[*]Repair or change file system from TWRP not working:[*]Failed to mount '/system' (Invalid argument)
[*]Failed to mount '/cache' (Invalid argument)
[*]Failed to mount '/data' (Invalid argument)[*]Mount system cache data from TWRP not working:[*]Failed to mount '/system' (Invalid argument)
[*]Failed to mount '/cache' (Invalid argument)
[*]Failed to mount '/data' (Invalid argument)[*]TWRP => Advanced => Terminal:
Code:
Example:
mount -o remount,rw /dev/block/mmcblk0p36 /data
giving error:
mount: '/data' not in /proc/mounts
(same for adb)
/proc/mounts is pretty empty (wtf)
Code:
adb shell
cat /proc/mounts
rootfs / rootfs rw,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=949708k,nr_inodes=237427,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime,size=949708k,nr_inodes=237427 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
And here is the question
Can someone, please, upload /proc/mounts file here, I would like to do:
Code:
adb push mounts /proc/mounts
After that, I will try to reformat partitions with parted.
Of course, if someone has some more elegant solution, I'm listening, thanks in advance.
Notice: Sorry cause kilometer post, I was want to full explain that I've really tried every usual method to alive a phone. I suppose that first ~6 answers and propose would be - "Flash fastboot ROM", but this not helping in this stage.
Same problem with my MI4I
stiw47 said:
Hi guys,
+1 from me
I've totally screwed up ferrari.
Scenario: I was on Resurrection Remix 5.8.5 For some reason, I've started storage encryption. Probably it wasn't successful, and on next reboot, I've got error "Decryption unsuccessful, your password is ok, but data partition is corrupted, blah, blah, blah. I've successful rescued my storage files:
Code:
boot into TWRP:
adb pull /dev/block/mmcblk0p36
then, mounted mmcblk0p36 partition file under Linux on my PC (example):
sudo mkdir /mnt/data
sudo mount /home/stiw47/mmcblk0p36 /mnt/data
Whoala, few files was corrupted, but all from android internal storage (my personal files) was rescued.
Ok. After this, I've performed factory reset on phone, but device going to fastboot, not in Android OS. TWRP says that /data cannot be mounted.
I flashed latest MIUI from fastbot
Reboot
device going to fastboot, not in Android OS. TWRP says that /data, /system and /cache cannot be mounted.
Variable : In following text, "same" is equal to "device going to fastboot, not in Android OS. TWRP says that /data, /system and /cache cannot be mounted."
I've tried to flash fastboot ROM zilion times - same
Tried to flash from MI PC Suite - same (MI Suite giving "success" info)
XiaoMI Flash Tool - same (tool giving success info)
Was want to flash with QFIL (Qualcomm Flash Image Loader), after several Qualcomm Xiaomi driver installation, founded here and there over the internet, on two different PCs - No COM port detected, both in QFIL and in Device Manager
[*]Wipe from TWRP not working:[*]Failed to mount '/system' (Invalid argument)
[*]Failed to mount '/cache' (Invalid argument)
[*]Failed to mount '/data' (Invalid argument)[*]Format Data from TWRP not working:[*]Failed to mount '/system' (Invalid argument)
[*]Failed to mount '/cache' (Invalid argument)
[*]Failed to mount '/data' (Invalid argument)[*]Repair or change file system from TWRP not working:[*]Failed to mount '/system' (Invalid argument)
[*]Failed to mount '/cache' (Invalid argument)
[*]Failed to mount '/data' (Invalid argument)[*]Mount system cache data from TWRP not working:[*]Failed to mount '/system' (Invalid argument)
[*]Failed to mount '/cache' (Invalid argument)
[*]Failed to mount '/data' (Invalid argument)[*]TWRP => Advanced => Terminal:
Code:
Example:
mount -o remount,rw /dev/block/mmcblk0p36 /data
giving error:
mount: '/data' not in /proc/mounts
(same for adb)
/proc/mounts is pretty empty (wtf)
Code:
adb shell
cat /proc/mounts
rootfs / rootfs rw,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=949708k,nr_inodes=237427,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime,size=949708k,nr_inodes=237427 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
And here is the question
Can someone, please, upload /proc/mounts file here, I would like to do:
Code:
adb push mounts /proc/mounts
After that, I will try to reformat partitions with parted.
Of course, if someone has some more elegant solution, I'm listening, thanks in advance.
Notice: Sorry cause kilometer post, I was want to full explain that I've really tried every usual method to alive a phone. I suppose that first ~6 answers and propose would be - "Flash fastboot ROM", but this not helping in this stage.
Click to expand...
Click to collapse
Did you find any solutions for this. I have tried every single method mentioned above and getting same errors mentioned above like unable to mount/invalid cache/invalid data etc....
nepya1009 said:
Did you find any solutions for this. I have tried every single method mentioned above and getting same errors mentioned above like unable to mount/invalid cache/invalid data etc....
Click to expand...
Click to collapse
Hi,
Yes, I found solution, I bought MI 6
Related
recovery mode not working
Ok, so I was trying to reflash the modified rc30 update to start from scratch because when trying to do the auto rotate browser tweak I kept getting the not enough space message. I rebooted into recovery mode thinking all I had to do was run the update and it didn't do it. I thought maybe I needed to reflash the modified recovery image so I did that, but now when I reboot into recovery mode I get the G1 logo and then a blank screen. I tried pushing home+back to restart and get nothing. So I used adb to push the recovery image on the device and I get "no space left on device" Tried doing a factory reset and it hangs up on a blank screen there too. can I just wipe the data partition to fix it then reflash the recovery image to the device? The phone works fine, I just can't do anything with recovery. Can someone help me out here in getting back recovery mode? Thanks
When you tried to push the recovery image, did you do so to the sdcard? I am referencing these pages: http://android-dls.com/wiki/index.php?title=Keeping_Root http://code.google.com/android/reference/adb.html
Just remount /system as rw and adb push the recovery.img directly in. Also, if you have the engineering bootloader installed, you could try using fastboot to reflash the recovery partition from the bootloader.
doesn't mount -o remount,rw /dev/block/mtdblock3 /system remount the system as rw? That's what i've been doing, and still says device full. I went in and tried by putting the file on the sd card and then flashing it but get the same message. I don't have the engineering bootloader yet that was next on my list. Is there a way to see what is on my partition so I can remove things to free up space?
jdwme said: doesn't mount -o remount,rw /dev/block/mtdblock3 /system remount the system as rw? That's what i've been doing, and still says device full. I went in and tried by putting the file on the sd card and then flashing it but get the same message. I don't have the engineering bootloader yet that was next on my list. Is there a way to see what is on my partition so I can remove things to free up space? Click to expand... Click to collapse If you're on RC30 v1.2 put the recovery.img in /data not /system
so then my it should look like this? mount -o remount,rw /dev/block/mtdblock3 /data cd /data cat /sdcard/recovery_testkeys.img > recovery.img flash_image recovery recovery.img
jdwme said: so then my it should look like this? mount -o remount,rw /dev/block/mtdblock3 /data cd /data cat /sdcard/recovery_testkeys.img > recovery.img flash_image recovery recovery.img Click to expand... Click to collapse mtd3 is system. mtd5 is userdata. Don't execute that first step! userdata partition is rw anyway. Just start with step 2.
ok, i did execute the first step in the terminal emulator, is that bad? i will try it now starting with just cd /data
jdwme said: ok, i did execute the first step in the terminal emulator, is that bad? i will try it now starting with just cd /data Click to expand... Click to collapse Not sure. What do you get if you type mount with no args in the terminal emu?
nothing, it just goes to the next line and lets me enter in the next step. is there a way to flash from the standard bootloader?
jdwme said: nothing, it just goes to the next line and lets me enter in the next step. is there a way to flash from the standard bootloader? Click to expand... Click to collapse Really? What it should do is return a list of mounted devices, like so (this is a Mod RC30 v1.2 device): Code: # mount rootfs on / type rootfs (ro) tmpfs on /dev type tmpfs (rw,mode=755) devpts on /dev/pts type devpts (rw,mode=600) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k) /dev/block/mtdblock3 on /system type yaffs2 (ro) /dev/block/loop0 on /system/modules type cramfs (ro) /dev/block/loop1 on /system/xbin type cramfs (ro) /dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev) /dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev) /dev/block/mmcblk0p1 on /sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8) Stock bootloader can't be used to flash images to the mtd partitions.
ok i misunderstood, i did type just mount now and it shows what you posted. could i have two modified recovery images on there and it cant pick one so thats causing the problem?
Did you change directory to /data? If you can't get it to work from the terminal, as long as you have the recovery.img in /data, just power the G1 off completely and power it back on. It automatically writes the recovery partition every time you cold boot. Btw make sure that in the mount report the following two lines read exactly as such: Code: /dev/block/mtdblock3 on /system type yaffs2 (ro) /dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev)
yeah the mount report shows just that. i have cold rebooted everytime i tried to flash, then powered off and tried to boot back up in recovery mode and it doesnt work, gives the g1 logo then screen is black.
jdwme said: yeah the mount report shows just that. i have cold rebooted everytime i tried to flash, then powered off and tried to boot back up in recovery mode and it doesnt work, gives the g1 logo then screen is black. Click to expand... Click to collapse On your cold reboots were you seeing the flashing screen (arrow onto chip) before booting into Android?
nope, only showed that when i was able to upgrade to modified rc 30 or run the update in recovery mode
jdwme said: nope, only showed that when i was able to upgrade to modified rc 30 or run the update in recovery mode Click to expand... Click to collapse Are you sure you have the recovery.img in the /data directory? Strange. Maybe someone else has some ideas about whats going on here?
So I decided to show all my partitions listed on the system using cat /proc/partitions and this is what I got. Does this look normal? Not sure what it looks like on anyone else device major minor #blocks name 7 0 2248 loop0 7 1 3176 loop1 31 0 256 mtdblock0 31 1 5120 mtdblock1 31 2 2560 mtdblock2 31 3 69120 mtdblock3 31 4 69120 mtdblock4 31 5 76544 mtdblock5 179 0 7977472 mmcblk0 179 1 7973376 mmcblk0p1 I pushed it to the data directory before, followed the instruction thread, but using oi file manager recovery.omg shows in system, nothing shows in data
so does anyone have any ideas? I was thinking about going back to rc29 to try and fix this but without being able to get recovery mode to come on I can't do it, I also can't flash over to the dev boot loader
jdwme said: so does anyone have any ideas? I was thinking about going back to rc29 to try and fix this but without being able to get recovery mode to come on I can't do it, I also can't flash over to the dev boot loader Click to expand... Click to collapse Give me an IM if you want. I may be able to help fix your recovery mode. (debugging things like that is such a pain on a forum. real-time is much easier)
CWM Loop, fast support apprecciated
Hello guys, I recently installed CWM on my GoClever device. Booting into recovery from Android using ROM Manager didn't work, so I tried Code: su "echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1 conv=sync; sync; reboot" And I booted in CWM right after it rebooted but when I tried to boot the device back to Android, it booted to CWM. Also the CWM is unable to mount any of the directories. Code: CWM-based Recovery v6.0.1.2 E:Can't mount /cache/recovery/command E:Can't mount /cache/recovery/log E:Can't mount /open/recovery/log E:Can't mount /cache/recovery/last_log E:Can't open /cache/recovery/last_log ADB should work I guess Could anyone help me please? I guess it's not hard to fix this, probably some file modifying, but I don't really know what exactly to do... :/ EDIT: A recovery image that boots into Android instead of recovery would be a neat solution, but I'm not sure if it's possible LAST EDIT [SOLVED] : hajdulak said: So I flashed an officcial firmware from this thread: http://forum.xda-developers.com/showthread.php?p=36674128 Using this method: http://www.goclever.com/manuals/update_a93_en.pdf Didn't know the img contained a recovery image. Thank you XDA, for being helpful again I really appreciate it -> [SOLVED] pretty please Click to expand... Click to collapse Well, i guess A13's will never get some solid support... At least I got my 10 posts... Weeee!
Guys, what's with all the views and no answers? After some googling, I found out it's quite a frequent issue, but none of the googled threads helped in any way... Damn it... Also, A13 devices have SOOOOO low support... And an important thing I got a dumped stock recovery img on the /sdcard/, just need to know if I can flash it and how to flash it using ADB, I'm quite afraid of doing anything now
Soooo... When the device is plugged in, it identifies itself as "MID08" Seems i installed a wrong recovery image Now I need drivers for my TAB, as it can't appear in the Code: adb devices menu... :/
If anyone can really help, this is a list of my blockdevices: Code: loop0 loop1 loop2 loop3 loop4 loop5 loop6 loop7 nandf ram0 ram1 And this is my fstab Code: /dev/block/nandh /cache ext4 rw /dev/block/nande /data ext4 rw /dev/block/nandi /emmc auto rw /dev/block/nandd /system ext4 rw /dev/block/mmcblk0p1 /sdcard vfat rw /dev/block/mmcblk0p2 /sd-ext auto rw And this is recovery.fstab Code: # mount point fstype device /boot emmc /dev/block/nandc /cache ext4 /dev/block/nandh /data ext4 /dev/block/nande /emmc auto /dev/block/nandi /dev/block/nandi1 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 /sd-ext auto /dev/block/mmcblk0p2 /system ext4 /dev/block/nandd /recovery emmc /dev/block/nandg Also when I try to cd to some dirs i get can't cd to XXX I guess there's some script that does the mounting stuff, but I still don't know what it is... I just need to access my sdcard and get the recovery image outta there...
So I flashed an officcial firmware from this thread: http://forum.xda-developers.com/showthread.php?p=36674128 Using this method: http://www.goclever.com/manuals/update_a93_en.pdf Didn't know the img contained a recovery image. Thank you XDA, for being helpful again I really appreciate it
stuck on boot logo
hi at first i have to say my English is not good!! i have a tf700 and last night i installed CROMBi-kk on it after that because of lots of apps that i installed in past it had lots of lag then i decided to wipe my data so i went to twrp and did a full wipe but in middle of that battery ran out. i install CROMBi-kk again but it stuck on boot logo!!! i think there is no partition on it!! UNFORTUNATELY I DON'T HAVE ANY BACKUP!! PLZ HELP!!!!! thank you!!
Need more information. Which bootloader are you on? Which kernel are you on? Which kernel did you choose? Internal install? rom2sd? data2sd? Which options? recovery.log? aroma.log?
sbdags said: Need more information. Which bootloader are you on? Click to expand... Click to collapse android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.10-20130801" a03 sbdags said: Which kernel are you on? Which kernel did you choose? Click to expand... Click to collapse _that modded Asus OC Kernel v10 sbdags said: Internal install? rom2sd? data2sd? Click to expand... Click to collapse internal install sbdags said: Which options? Click to expand... Click to collapse data journaling is enable sbdags said: recovery.log? aroma.log? Click to expand... Click to collapse E:could not mount /data and unable to find crypto footer E: unable to mount ' /data ' E: unable to recreat /data/media folder. Updating partition details. . . E: unable to mount ' /data ' E: unable to mount internal storage. E: unable to mount /data /media during GUI startup. full SELinux support is present. E: unable to mount /data/media/twrp/ .twrps when trying to read settings file. E: no valid storage partition found for MTP E: unable to mount ' /data ' E: unable to mount ' /data ' in bootloader there is a line that say " key driver not found.. booting os on detecting file system phase : /data on internal (UDA) -> unknown
hoseinkh said: android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.10-20130801" a03 _that modded Asus OC Kernel v10 internal install data journaling is enable E:could not mount /data and unable to find crypto footer E: unable to mount ' /data ' E: unable to recreat /data/media folder. Updating partition details. . . E: unable to mount ' /data ' E: unable to mount internal storage. E: unable to mount /data /media during GUI startup. full SELinux support is present. E: unable to mount /data/media/twrp/ .twrps when trying to read settings file. E: no valid storage partition found for MTP E: unable to mount ' /data ' E: unable to mount ' /data ' in bootloader there is a line that say " key driver not found.. booting os on detecting file system phase : /data on internal (UDA) -> unknown Click to expand... Click to collapse Ignore the key driver message - we all get it. So you /data partition is not in a recognisable format and cannot be mounted. Please format it in TWRP or from adb use this command when in TWRP (make sure MTP is turned off) Code: adb shell killall -19 recovery make_ext4fs /dev/block/mmcblk0p8 reboot or in the bootloader use this: Code: fastboot erase userdata
sbdags said: Ignore the key driver message - we all get it. So you /data partition is not in a recognisable format and cannot be mounted. Please format it in TWRP or from adb use this command when in TWRP (make sure MTP is turned off) Code: adb shell killall -19 recovery make_ext4fs /dev/block/mmcblk0p8 reboot or in the bootloader use this: Code: fastboot erase userdata Click to expand... Click to collapse Code: C:\adb>fastboot erase userdata ^C C:\adb> C:\adb>adb shell * daemon not running. starting it now on port 5037 * * daemon started successfully * [email protected]:/ $ killall -19 recovery killall -19 recovery killall: recovery: no process killed 1|[email protected]:/ $ make_ext4fs /dev/block/mmcblk0p8 make_ext4fs /dev/block/mmcblk0p8 Need size of filesystem 1|[email protected]:/ $ reboot reboot reboot: Operation not permitted 1|[email protected]:/ $ how to turn off mtp?? when i select format data from TWRP it stuck on " formatting data using make_ext4fs function" and even after 30 min nothing happen!!
thank you man!! it's finally worked!! Thank you for your attention and answers!!
hoseinkh said: thank you man!! it's finally worked!! Thank you for your attention and answers!! Click to expand... Click to collapse You are welcome! Which one worked?
sbdags said: You are welcome! Which one worked? Click to expand... Click to collapse Code: fastboot earase userdata
erase data failed I just get the following: fastboot earase userdata ******** Did you mean to fastboot format this partition? erasing 'userdata'... FAILED (remote: failed to erase partition ) finished. total time: 5.065s device is unlocked, hang in bootloop, tried flashing but: E: Unable to mount '/cache' E: Unable to mount '/cache' E: Unable to mount /data/meida/TWRP/ . twrps when trying to read settings file. E: No valid storage partitions found for MTP. E: Unable to mount '/data' E: Unable to mount '/data' thanks for your answers.
homer56 said: E: Unable to mount '/data' Click to expand... Click to collapse In TWRP, go to wipe -> advanced -> format data. This can take more than an hour, so be patient.
TWRP cannot mount /data; nothing 'sticking' using fastboot
Hi all, hoping on the off-chance someone's still monitoring the Nexus 5 forums here So decided to dust off the old Nexus 5 (now with extra COVID-19 time on my hands!) to use as a backup device, but having serious issues getting it up and running. I had it rooted years ago, and had no issues installing custom roms. Now I'm having the following situation: I cannot flash the factory image using fastboot, nor anything is 'sticking' to the phone when I try to re-flash individual component for the factory image. I've also tried to flash TWRP, but again, it doesn't stick and the only way i can boot into TWRP is by using Code: fastboot boot recovery.img . However in recovery, the data partition is not mounting and all the tutorials/guides I read about fixing it aren't working (e.g. repairing the partition-- get a 'unable to repair data' error; changing from EX4 to EX2 and back-- get 'failed to mount '/data' error). Ran the following command in the terminal window in TWRP Code: cat /etc/fstab and got the following output: Code: /dev/block/mmcblk0p25 /system ext4 rw 0 0 /dev/block/dm-0 /data ext4 rw 0 0 /dev/block/mmcblk0p27 /cache ext4 rw 0 0 /dev/block/mmcblk016 /persist ext 4 rw 0 0 /dev/block/mmcblk0p1 /firmware vfat rw 0 0 /usb-otg vfat rw 0 0 tried using the make_ext4fs command, but again- nothing happens. Using TWRP 3.3.1-0 by the way Any ideas? is the phone completely bricked? it's stuck in a bootloop where the google colours come up but freeze within half a second, repeat and continue. Any advice would be very much appreciated!
Init_user0_failed After trying to update to 11.0.5.1
I have the same issue but I can't boot at all. I'm only limited to twrp and fastboot. I was previously running 11.0.3 with Magisk and a Magisk module called xXx_nolimit, downloaded the OTA update and went to reboot to recovery before being prompted for a pattern passcode (I hadn't set any fingerprint or password) so I rebooted into twrp and clicked fix bootloader. Now as I reboot it just boots back into twrp. I'm also getting these same messages: Failed to mount /data (Invalid argument) Unable to recreate /data/media folder. Unable to mount storage Unable to mount /data/media/TWRP/.twrps I'm currently running apbf to bruteforce the pattern passcode that I never set in hopes to decrypt my phone. Not even sure it will work though as I don't have FBE user 0 mounted? I have my dad's phone which basically has the exact setup as mine but I didn't update it yet. Anyway to use partition or parts data from his phone to fix mine? I really don't want to wipe my /data or /userdata as it's been a while since I backed anything up. All I have in my /data folder is: /data/india /data/recovery /data/reserve Update: I tried adb sideloading the previous 11.0.3.1 and as I reboot I get `Init_user0_failed` with a dmesg and android.log file saved in /op2. My /system/etc/fstab: /system_root ext4 ro 0 0 /dev/block/sda17 /metadata ext4 rw 0 0 /dev/block/sda19 /data ext4 rw 0 0 /firmware vfat ro 0 0 /dev/block/sda7 /op2 ext4 rw 0 0 /usbstorage vfat rw 0 0 /vendor ext4 ro 0 0 ls -al /dev/block/platform/soc/1d84000.ufshc/by-name/: http://dpaste.com/CFNTDVTRK dmesg.log: http://dpaste.com/DPRQLYCEE android.log: (added as attachement) I've been told I can use EDL but want to keep that as last resort as I don't have a backup of any of my files. Edit: I also tried the reboot to recovery, clear cache then reboot back to recovery and reboot system as mentioned on a couple of other threads but that didn't work either.
Don't know if this will help, but I recently ended up soft-bricked with that same error after upgrading to a newer version of TWRP. I believe it had something to do with the way TWRP interacts with the /data partition, although I'm not sure how exactly. Anyway, I was able to get the phone booting into OOS so I could at least back up my /sdcard partition before blowing it away and starting over. The way I did that was to flash crDroid's newest recovery boot img: https://forum.xda-developers.com/t/rom-android-12l-op7pro-crdroid-v8-6-26-06-2022.4184671/ https://sourceforge.net/projects/crdroid/files/guacamole/8.x/recovery/ For me, the phone would once again boot into OOS, but fingerprint authentication didn't work, and the phone consistently froze about 5 minutes after putting in my PIN at boot. I was able to extend this time by freezing the Magisk app in Titanium and turning off all radios (Airplane mode on, Bluetooth off, etc.) After like 30 reboots, I was able to get everything copied off the /sdcard partition. Hope this helps someone...