Hi,
i'm pretty new to this and i have kinda big problem. I had MIUI 7 rom installed on my S4 I9505, but yesterday after the update phone wont boot. I downloaded new .zip file, put it on SD card, boot into recovery, wipe everything and tried to install new rom. With no succes. I tried 3 differrent roms, i even tried with diffirent recovery, still nothing.
This is what it says:
Installing: /storage/sdcar1/cm-12.1-20151106-NIGHTLY-jfltexx.zip
Finding update package
Opening update package
Installing update
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid argument
unmount of /system failed: no such volume
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by_name/userdata
Patching system image unconditionally...
And that's it. Previosly i was getting errors, status 0 and status 7 if i remmember correctly, but now not even that
Now what to do? Please be noob friendly At this point i don't even care any more what rom to install, stock or custom, but i think i would prefer stock.
Thanks for your help!
Edit: I found this guide, will it do it? forums.androidcentral.com/ambassador-guides-tips-how-s/499009-guide-samsung-how-flash-stock-rom-via-odin-new-interface.html
It worked. Admin, you can close/delete this thread.
Related
Hi guys, Im having a little trouble, hoping somebody could tell me what Im missing or should be doing differently. I am currently on 2.2 OTA. i just rooted using RoOoLeR's Guide to ROOT / BACKUP / ROMS for 2.2 OTA (sticky under hacks). I then downloaded Bootstrap. Opened the app and hit "bootstrap recovery", got the pop-up saying "Success". Then i rebooted into recovery and started a nandroid backup. about a minute into it, it failed and gave me the following message.
E: Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)
(Device or resource busy)
Can't mount /sdcard/.android_secure!
I have yet to install rom manager and load any custom roms beacuse i want to make sure i have a good backup before doing anything.
Suggestions? Thank you so much in advance.
--
Garret
It sounds like you have an issue with the SD card. I would backup the data on the card to a PC, format it blank, and the let the X reinitialize it.
After Flashing latest arabic rom
the device reboot on to recovery mode and shows that:
update media please wait
E:Can't mount /dev/block/stl10
(invalid argument)
E:copy_dbdata_media:can't mount DBDATA:
your storage not prepared yet,please use UI menu for format and reboot actions.
copy default media content failed
then when i rebooted it from recovery the boot animation appears with the sound then after a while the screen goes blank.then the thing starts vibrating.help me to get this fixed guys.
goto a rom that works seems there to be a problem with the rom ur using try rotohammers rom
Roufosso said:
After Flashing latest arabic rom
the device reboot on to recovery mode and shows that:
update media please wait
E:Can't mount /dev/block/stl10
(invalid argument)
E:copy_dbdata_media:can't mount DBDATA:
your storage not prepared yet,please use UI menu for format and reboot actions.
copy default media content failed
then when i rebooted it from recovery the boot animation appears with the sound then after a while the screen goes blank.then the thing starts vibrating.help me to get this fixed guys.
Click to expand...
Click to collapse
The problem is that the ROM you flashed doesn't include the dbdata.rfs file. You will be able to extract one from the JM6 ROM from Samfirmware or from the JMG package I put together, here's a link to the post http://forum.xda-developers.com/showpost.php?p=10892253&postcount=305 You can flash dbdata.rfs directly to your Tab as it is now with Heimdall or otherwise you'll need to flash a ROM package like my JMG one that contains dbdata.rfs with Odin.
Hello everyone,
Please Help me to fix this issue
TWRP shows E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount internal storage
I have twrp v2.5
Actually, I am trying many solutions but nothing change
Hi, pal. I have the exactly same problem these days. On my opinion, when you have made wipe and wipe dalvik cache, you just deleted the system folder and data. I did same thing, now I'm stuck! :Д When you are trying to change the firmware, is the logo pictures changing for you every time you flash any other .zip file? We' are now complete lost man. Is your USB working like mine where PCs not detecting it? I think they've launched this kind of firmware only to destroy our device, so we can buy a new one. That's the idea. Go to the service and repair center of Lenovo and ask them for help! I wrote them down before a while, now I'm waiting for the response. We have left only two or three possibilities to flash the Rom with the Terminal in the Recovery. But if your PC recognizing the drivers, you will manage to flash the Stock 4.2.2 Rom with Flash tool , otherwise you are stuck too! I have no idea how to flash it. I can give you the terminal commands for you, which are hard to find, but you and me, we need the proper .img files for the flashing procedure. Go to the 4pda forum and ask for help, if you find any solution, come back here telling it and for me. There's a possibility, but it is difficult to create a proper .zip archive, because I only know that we need those folders and files: meta folder- updater-script, logo. bin, lk.bin, boot.img and system.img.
But when I insert the commands there, I don't know how the whole process must be working, something is happening there. The problem is that one of those lines did not work for me. Those are the commands for flashing any Rom with the terminal in the recovery. But first you must see if the PC is installing your drivers properly, open device manager and look for the drivers on the internet and try to install them. May be you have a working USB port, so there's no problem, just flash the stock rom with the Flash tool. But if it is not working as it is here, no other possibilities left, my boy! The only one left or two of them : Flashing the device either through fast boot mode or adb sideload, but you must install those drivers so PC can find the device. Well, you can always do this at your own risk from the terminal.
Oh, I forgot, those problem came when we deleted fstab file for our device.
Flashing firmware through the TWRP terminal commands:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p6 (for the memory ROW+ ) or
dd if=/external_sd/system.img of=/dev/block/mmcblk0p5 (for CN+ memory)
dd if=/external_sd/boot.img of=/dev/bootimg
dd if=/external_sd/lk.bin of=/dev/uboot
dd if=/external_sd/logo.bin of=/dev/logo
First, system.img must be converted to systemEXT4.img, then flashing it and you need to have a systemEXT4 in the .zip archive. But I think my system folder is deleted. :Д
simg2img /external_sd/system.img /external_sd/systemEXT4.img
Good luck to you! According to me there is a space after the dot and it must be like this: system. img, boot. img. But not sure!
Hi again. Tooday It occurred to me where our problem may be came with the tablets. When we flashed a custom Rom, we put it for the wrong MTK processor. Ours is MT8389, not 6589. The stock roms are too for the MT8389 according to me. We flashed a wrong Rom. Now the tab must be formatted somehow either through some commands from the terminal, or USB port and path to the USB must be repaired. Then, flashing with the Flash tools is our only option left! Sorry! );
They killed our device on purpose with the Custom rom. Do not flash them any more with such Roms.
To be quick, I have a very specific error in all TWRP versions on LS997 that won't let the system stay mounted while flashing roms, "Failed to mount '/system' (invalid argument)".
I believe I found a fix for it in a dead reddit thread, but I can't understand how to do it on an LG v20.
Help is much appreciated.
It reads
"for anybody that stumbles upon this thread: I got it working by using a parted binary and mkfs.ext4 binary.
I removed the partition and added it again with parted, don't forget to name it correctly. And then I reformatted with mkfs.ext4. Those three links might help:
https://en.miui.com/thread-340966-1-1.html
https://android.stackexchange.com/q...in-terminal-emulator-on-my-android-smartphone
https://forum.xda-developers.com/android/help/how-to-boot-sd-card-qmobile-z8-bricked-t3712171"
The thread.
https://www.reddit.com/r/LineageOS/comments/aozjvf/twrp_can_not_mount_system_with_invalid_argument/
strapdad said:
To be quick, I have a very specific error in all TWRP versions on LS997 that won't let the system stay mounted while flashing roms, "Failed to mount '/system' (invalid argument)".
I believe I found a fix for it in a dead reddit thread, but I can't understand how to do it on an LG v20.
Help is much appreciated.
It reads
"for anybody that stumbles upon this thread: I got it working by using a parted binary and mkfs.ext4 binary.
I removed the partition and added it again with parted, don't forget to name it correctly. And then I reformatted with mkfs.ext4. Those three links might help:
https://en.miui.com/thread-340966-1-1.html
https://android.stackexchange.com/q...in-terminal-emulator-on-my-android-smartphone
https://forum.xda-developers.com/android/help/how-to-boot-sd-card-qmobile-z8-bricked-t3712171"
The thread.
https://www.reddit.com/r/LineageOS/comments/aozjvf/twrp_can_not_mount_system_with_invalid_argument/
Click to expand...
Click to collapse
I’m also looking at the thread, and the miui link is stale because miui cleaned their forum.
I tried erase data (entire partition). I tried wiping system data cache, no matter what I did it was error 7 or unable to mount system.
I’m suspecting it might be which kdz I used for the downgrade but honestly it can’t be the case because I did this before 2 months ago and it was ok, now I can’t do anything.
Hi,
I am trying to install the latest Lineage version on my Samsung Nexus 10 via twrp, but so far it always immediately fails with
Error E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineage-17.1-20220318-UNOFFICIAL-manta.zip'
I tried wiping the entire system, cache and all and I tried both the adb push method and sideloading adb and they all produce the exact same error.
This is my first time doing this type of thing, so any help would be greatly appreciated.
P.S. I am currently running Windows 10, but could boot into a Linux Live Medium if that would be useful.
Edit: I was following this tutorial for the setup.
I'm facing exactly the same issue here with the installation of `lineage-17.1-20220919-UNOFFICIAL-manta.zip` file.
I'm currently on the latest original Google Android ROM flashed with `image-mantaray-lmy49j.zip` and want to update the system to the lineage OS as above.
I'm using TWRP v3.6.2_9.
What I did:
- uploaded `lineage-17.1-20220919-UNOFFICIAL-manta.zip` to `/sdcard` location;
- wiped out `dalvik-cache` and `cache` partitions;
- tried to install `lineage-17.1-20220919-UNOFFICIAL-manta.zip` as a single installation file;
Got this error. Here is an output from recovery.log:
Code:
Installing zip file '/sdcard/lineage-17.1-20220919-UNOFFICIAL-manta.zip'
Unmounting System...
I:Update binary zip
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
No path given to file labeling backend
selinux_android_file_context: Error getting file context handle (No such file or directory)
Warning: No file_contextsTarget: google/mantaray/manta:5.1.1/LMY49J/2640980:user/release-keysTarget: google/mantaray/manta:5.1.1/LMY49J/2640980:user/release-keys
Extracted file "/tmp/install/bin/backuptool.functions"
Extracted file "/tmp/install/bin/backuptool.sh"
Extracted 2 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 4 args
Backup/restore is not possible. Partition is probably empty
Patching system image unconditionally...
performing update
blockimg version is 4
maximum stash entries 0
creating stash /cache/recovery/4dd6bf24fbba9cc76c352f5c4cfaed0074be0244
535756800 bytes free on /cache (0 needed)
/cache/recovery/last_command doesn't exist.
erasing 3367 blocks
BLKDISCARD ioctl failed: Invalid argument
failed to execute command [erase 4,225950,228864,229947,230400]
new data receiver is still available after executing all commands.
Patching system image unconditionally...script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
I:Install took 0 second(s).
Error installing zip file '/sdcard/lineage-17.1-20220919-UNOFFICIAL-manta.zip'
Does anyone have any clue on what could be wrong here and why it fails?
unpack zip remove lines, then pack zip and try again. voilla
or utube eroor 7
I'd the same problem with twrp but does did successfully for version 16 installation. I tried the above listed way but failed again. Same thing happened even I unchecked the system in twrp before flashing again. Need expert to help fix the issue. Appreciate in advanced!
Cpluo said:
I'd the same problem with twrp but does did successfully for version 16 installation. I tried the above listed way but failed again. Same thing happened even I unchecked the system in twrp before flashing again. Need expert to help fix the issue. Appreciate in advanced!
Click to expand...
Click to collapse
Not enough space on /system. Resize the partition. After 17.1 is running for me. https://www.hovatek.com/forum/thread-32750.html
Thanks a lot Daniel! I will try your way.