Develop Bugs

[Q] can't mount system.img

i'm trying to mount system.img to extract the files, but i get errors every time.
i think i don't use the right command, can anyone tell me what is the command for mounting the system.img?

can someone please help me?

should be mount -o rw,remount /dev/block/mmcblk0p1 /system

sinkster said:
should be mount -o rw,remount /dev/block/mmcblk0p1 /system
Click to expand...
Click to collapse
no i get this error:
Code:
can't find system.img in /etc/fstab or /etc/mtab

OverLo4d said:
no i get this error:
Code:
can't find system.img in /etc/fstab or /etc/mtab
Click to expand...
Click to collapse
Which command you are using?

ameer1234567890 said:
Which command you are using?
Click to expand...
Click to collapse
this time i tried the command he suggested, but i tried also this:
Code:
mount -o loop system.img system
or this:
Code:
mount -t ext4 -o loop system.img system
and nothing works

OverLo4d said:
this time i tried the command he suggested, but i tried also this:
Code:
mount -o loop system.img system
or this:
Code:
mount -t ext4 -o loop system.img system
and nothing works
Click to expand...
Click to collapse
I am guessing that you are trying to mount yaffs2 image from nandroid backup! Android does not support mounting yaffs2 images. Perhaps it's a kernel thingy, but I haven't come across any kernel which can do it. Perhaps someone could make a module or something?
In case if you are trying to mount an ext4 image, first create a folder in your sdcard named "system". Then:
Code:
mount -o loop system.img /sdcard/system

ameer1234567890 said:
I am guessing that you are trying to mount yaffs2 image from nandroid backup! Android does not support mounting yaffs2 images. Perhaps it's a kernel thingy, but I haven't come across any kernel which can do it. Perhaps someone could make a module or something?
Click to expand...
Click to collapse
no, it's a system.img converted from system.sin
is there any other way to way or command to extract the files?

OverLo4d said:
no, it's a system.img converted from system.sin
is there any other way to way or command to extract the files?
Click to expand...
Click to collapse
system.img converted from system.sin is the same as system.img from a nandroid backup.
Since you want to extract the img file, you could use this: http://forum.xda-developers.com/showthread.php?t=1645412 or http://forum.xda-developers.com/showthread.php?t=1112906

ameer1234567890 said:
system.img converted from system.sin is the same as system.img from a nandroid backup.
Since you want to extract the img file, you could use this: http://forum.xda-developers.com/showthread.php?t=1645412 or http://forum.xda-developers.com/showthread.php?t=1112906
Click to expand...
Click to collapse
doesn't work, i already tried any kind of unyaffs2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

OverLo4d said:
doesn't work, i already tried any kind of unyaffs2
Click to expand...
Click to collapse
The sin2img tool you are using may not be compatible with all sin files. Try converting sin to img from flashtool.

ameer1234567890 said:
The sin2img tool you are using may not be compatible with all sin files. Try converting sin to img from flashtool.
Click to expand...
Click to collapse
i'm using bin4ry's sin2img, and it's the only that worked.

I extract the yaffs2 fs with flashtool and got system.yaffs2, but unyaffs2 does not work on it... any idea? (pagesize or something else?)

ldrolez said:
I extract the yaffs2 fs with flashtool and got system.yaffs2, but unyaffs2 does not work on it... any idea? (pagesize or something else?)
Click to expand...
Click to collapse
I already solved the problem and made a tutorial. Look for it in the general section
Sent from my LT18i using xda premium

OverLo4d said:
I already solved the problem and made a tutorial. Look for it in the general section
Click to expand...
Click to collapse
Thanks! To sum up, unyaffs2 does not work, and yaffey does.

[Solved] Can't Flash Fresh ROM using Fastboot Or Recovery

SOLVED
Well, I guess I made a goof up.
I was using parted to modify the system partition and the userdata partition. I did so and reverted back to the way they were originally
i.e 838 MB for system 403 MB for cache and the rest for the userdata.
I had made a TWRP backup of my system, data and cache, which I restored once I was done playing around with parted.
Now the problem is that I cannot install any new ROM using Fastboot or Recovery.
While using Fastboot and MI Flash Tool
I get an error when it tries to flash the system partition saying "Unspecified Error(0x80004005: Failed (remote: size too large)"
When I use Minimal ADB and Fastboot to flash system partition it shows success, but upon reboot its stuck in bootloop
When using Recovery to flash any rom zip files it gives me reads "patching system images unconditionally" and stays put. There is no increment on the progress bar or anything. I kept it that way for 2 hours and still not change.
When i chose to flash images instead of zips. There is no option to select the system partition via recovery.
Also everytime I reboot from fastboot to recovery there is an error stating "cannot mount /system"
to resolve this i Wipe the system partition and then its able to mount.
Also I am able to restore the Backup I made using TWRP after wiping cache, system, data partitions.
This is the output for the Print command in the parted utility
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have no clue on exactly what the problem could be.
Any guidance/solution/discussion welcome.
UPDATE:-
I made a little mess in recreating partitions, the system partition was 1 mb less than what it actually was
recreated it using the actual bytes [not rounded off] from the partition table in the fastboot rom

I was thinking of extending the system partition to make room for larger GAPPS, but i decided not to....

"Couldn't mount SD card" rooting Nexus 7 (2013)

Hi,
I have been trying to root a Nexus 7, and I always end up having the problem that the recovery cannot mount the sdcard. I have wiped the entire device several times and tried installing different google stock images: marshmallow (6.0.1 MMB29O and MMB29Q) and lollipop (5.1.1 LMY48T). I tried installing Cyanogenmod, but couldn't install it without access to the sdcard from the recovery. I also tried different recovery methods.
This is the bootloader loading screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The stock recovery function failing to mount:
Team Win Recovery:
And ClockworkMod Recovery:
I also tried other versions of those recovery tools, but with the same result. I have no problem accessing the SD card from the Android OS, and accessing the device in USB mode was not a problem either.
It would be great if someone knew what the problem is. I have been searching, but couldn't find anything that helped.
Thanks for the help.

Aitor86 said:
I have no problem accessing the SD card from the Android OS
Click to expand...
Click to collapse
Android works fine but recovery does not? Unusual.
Please boot TWRP, run the following and post the log file:
Code:
adb shell blkid > data.txt
adb shell cat proc/partitions >> data.txt
adb shell head /sys/block/mmcblk0/device/* >> data.txt
adb shell dmesg >> data.txt
adb shell cat /tmp/recovery.log >> data.txt

k23m said:
Android works fine but recovery does not? Unusual.
Please boot TWRP, run the following and post the log file:
Code:
adb shell blkid > data.txt
adb shell cat proc/partitions >> data.txt
adb shell head /sys/block/mmcblk0/device/* >> data.txt
adb shell dmesg >> data.txt
adb shell cat /tmp/recovery.log >> data.txt
Click to expand...
Click to collapse
Hi, thanks for the help. This is the output of that code:
pastebin.com/fP5q3DPE

Aitor86 said:
Hi, thanks for the help. This is the output of that code: pastebin.com/fP5q3DPE
Click to expand...
Click to collapse
Hi mate, you wrote "I have no problem accessing the SD card from the Android OS" but the reality is "a few weeks ago I had no problem" - correct?
Your log:
Code:
mmc0: unrecognised EXT_CSD revision 7
mmc0: error -22 whilst initialising MMC card
Try the latest TWRP first, OK?

k23m said:
Hi mate, you wrote "I have no problem accessing the SD card from the Android OS" but the reality is "a few weeks ago I had no problem" - correct?
Your log:
Code:
mmc0: unrecognised EXT_CSD revision 7
mmc0: error -22 whilst initialising MMC card
Try the latest TWRP first, OK?
Click to expand...
Click to collapse
I have no idea what the problem was, but using the latest TWRP (3.0) did the trick. The sdcard is visible, and I can access any file I want from there.
Just to answer your question, the SD card was still accessible from the Android OS, so summing up, the only recovery tool that worked was the latest version of TWRP.
Thanks for the help!!!! I thought I was using the appropriate version, and I had spent more time than I would admit trying to get this working.

Hi
Sent from my iPhone using Tapatalk

[SOLVED] Nexus 5X Not Booting after Flashing Pixel Mod2 (/vendor & /system)

Help! I flashed the Android Oreo Pixel 2 Mod over Android Oreo 8.1.0 with my apps and data on it, and then the phone wouldn’t boot. So I went back into the recovery (TWRP 3.2) and tried to wipe the phone. TWRP wiped everything except for /vendor, returning the error “Failed to mount /vendor (invalid argument),” and "Failed to mount /system (invalid argument)". In TWRP I also tried mounting /system and /vendor, but it wouldn't let me check the box. So tried installing the stock android from the google page, and while sending sparse file ‘system’, It says FAILED (data transfer failure(Unknown Error)). Please Help, I’m a pretty much a noob at this kind of stuff.
EDIT: SOLVED
After browsing online, I wiped the phone one more time, re-flashed TWRP, tried a few commands, I tried repairing the file system of /system, re-installed the vendor.img(probably this), then It worked!
I'm just thankful it works now.

Need help flashing my Mi Mix 2

Hey guys,
im completly new to this flashing thing an i think i made a big mistake.
I tried to flash a new miui version (Global) via the already installed TWRP on my phone.
But that didnt quiet work, after the installation it just booted back in TWRP and i couldnt get the phone to do otherwise.
I googled a bit and found this tool called MIFlash (ver. 2017.4.25.0)
i also downloaded the fastbood rom from the Offical miui site and saved it on C: in a folder called rom
So i put the Phone into Fastboot and tried to flash it with MiFlash but in the end i got an error ( error:FAILED (remote: Check CRC failed))
And after that i couldnt even wipe the Data via TWRP i got an error there too
"Could not mount '/data' and unable to find crypto footer."
"Failed to mount '/data' (invalid argument)"
"Unable to recreate /data/media folder"
"Unable to mount /data/media/TWRP/.twrps"
"Unable to mount Storage"
PLS HELP!!!! :crying: