Develop Bugs

mount: mounting /dev/block/mmcblk0p12 on /sdcard failed: Invalid argument

Any ideas?

lonelliott said:
Any ideas?
Click to expand...
Click to collapse
Which command did you send?
Sent from my Kindle Fire using Tapatalk

are you logged in on adb? Try to type "exit" then "adb shell".
You don't have to mount your sdcard after using adb shell. (at least I didn't have to on my mac)

For some reason it will not mount my sdcard, at all. I can adb shell onto it, but when I try to run the update.zip from it, I get an error saying it cannot mount the sd card.

I had the same issue on mine. Heres the fix:
In TWRP with the fire connected to the pc run:
Code:
adb shell
echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file
Windows will probably respond that the volume/device needs formatted before using it.
Thats okay. choose quick format and let it format it as fat32 block size 4096.
when its done
in twrp choose the mount option and mount USB storage then hit unmount again
tap the box next to Mount SDCard. It should now look like
[X] Unmount SDCard.
Download the 6.2.1 pre-rooted zip file from the thread in the dev section.
choose mount USB Storage
Place on SDCard
Turn off usb storage
choose wipe
choose cache
choose factory reset
choose dalvik cache
choose system
go back and choose install
choose the zip you placed on your sdcard
flash it.
reboot. if it reboots back into twrp
run
Code:
adb shell
idme ? <--that will probably tell you the bootmode is 0x5003
idme bootmode 0x4000
exit
in twrp choose reboot
choose system
enjoy! it may take a while to boot

I have the same problem. Can't mount sdcard.
I'm doing your fix step by step in Win XP. I formatted partition into Fat32. Though it didn't allow me to select block size. It just has one option "Default allocation size". Capacity is 200MB.
After that I'm trying to tap on the Mount SDCard option, but it wouldn't change to [X] Unmount SDCard. So it wouldn't mount and I'm back to the problem.
Any ideas on what could go wrong?

I finally figured it out!
The key thing is that sdcard HAS to be formatted in a certain way - FAT32 (and presumingly block size 4096 as mentioned above).
Brief history:
I followed the above instruction and formatted sdcard on a mac with Disk Utility. That didn't work. It still wouldn't mount. I tried to do the same thing in Windows XP. No luck. It wouldn't mount with the same "Invalid argument" error.
I figured that I should try and format sdcard right from the TWRP shell. I deleted and recreated partition with fdisk. Then I learned that TWRP 2 comes with pretty old busybox which doesn't have mkfs or mkfs.vfat to format the partition to FAT 32. So took the busybox binary from the pre-rooted 6.2.1 and pushed it to the KF. And I used mkfs.vfat.
Instructions:
Download and unzip pre-rooted 6.2.1..
Rename busybox to busybox1 (just not to mess up existing version) and copy it to your KF.
Code:
adb push /path_to_unzipped_6.2.1/system/xbin/busybox1 /sbin
Go to shell:
Code:
adb shell
~ # chmod 755 /sbin/busybox1
~ # busybox1 mkfs.vfat /dev/block/mmcblk0p12
~ # mount sdcard
There you go! Now your sdcard is mounted. And you can proceed with the instruction above.

death2all110, thanks for the post. This solved my issues....beer money sent!
Brad

Thanks Dmitry_G, That was exactly what I needed!

You guys are amazing and you have brought my Kindle back from the dead. Thank you sincerely.

i need someone to help me with this please i'm a newbie with the same problem

Same to me, but i got error, help me!
I follow your guide, but have error, pls help!!!
C:\>adb shell
~ # chmod 755 /sbin/busybox1
chmod 755 /sbin/busybox1
~ # busybox1 mkfs.vfat /dev/block/mmcblk0p12
busybox1 mkfs.vfat /dev/block/mmcblk0p12
mkfs.vfat: can't open '/dev/block/mmcblk0p12': No such file or directory
~ # ^

You try copy mmcblk0p12 file from another KF to your KF.
This error by mmcblk0p12 deleted

Death, I don't know if you will see this reply because this thread is so old but if you do,THANK YOU!!!!!! THANK YOU!!! THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! I had messed with kfu, unbrick utility and many other methods to try to unbrick my kindle and your guide was exactly what I needed.

death2all110 said:
I had the same issue on mine. Heres the fix:
In TWRP with the fire connected to the pc run:
Code:
adb shell
echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file
Windows will probably respond that the volume/device needs formatted before using it.
Thats okay. choose quick format and let it format it as fat32 block size 4096.
when its done
in twrp choose the mount option and mount USB storage then hit unmount again
tap the box next to Mount SDCard. It should now look like
[X] Unmount SDCard.
Download the 6.2.1 pre-rooted zip file from the thread in the dev section.
choose mount USB Storage
Place on SDCard
Turn off usb storage
choose wipe
choose cache
choose factory reset
choose dalvik cache
choose system
go back and choose install
choose the zip you placed on your sdcard
flash it.
reboot. if it reboots back into twrp
run
Code:
adb shell
idme ? <--that will probably tell you the bootmode is 0x5003
idme bootmode 0x4000
exit
in twrp choose reboot
choose system
enjoy! it may take a while to boot
Click to expand...
Click to collapse
THANK YOU! It worked! I was about to trash this thing.

[Q]: repartitioning hiccup [solved]

Ok, I posted this question in 2 other threads that had info on the process (will delete the posts when this one goes live), but no responses after a couple of days. One of them is old though.
I have TWRP 2.1.1 installed. ADB seems to be working normally. Superuser is working fine after booting to android. I'm running a custom ICS ROM (Energy); read that stock ROM can cause issues repartitioning.
I started with this How-to as it looked very straight forward.
I start throwing the commands at ADB and here's what I got for my efforts:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # su
su
/sbin/sh: su: not found
~ # cd /data
cd /data
/data # ls
ls
/data #
decided to go ahead and check the mount command:
Code:
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
~ #
and parted just for giggles:
Code:
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 2041MB 1192MB ext4 userdata
11 2041MB 2309MB 268MB ext4 cache
12 2309MB 7690MB 5380MB fat32 media
(parted)
Ok, so that much worked. Now I tried to shrink 12 so I could double the size of 9. I want to get Switchme set up for his/her profiles and 500MB just isn't going to cut it.
That's when I hit a brick wall:
Code:
(parted) resize 12 2846 7690
resize 12 2846 7690
resize 12 2846 7690
Error: Unable to satisfy all constraints on the partition.
(parted)

One thing that jumps out at me right away is this:
Code:
adb shell
~ # su
su/sbin/sh: su: not found
It seems you are not actually rooted.
To check, enter:
Code:
adb shell
ls /system/xbin
If you don't see "su" in the list, then you don't have root permissions, which would probably prevent you from doing what you need to accomplish.

That's what I was wondering, but apps are able to ask for and receive root permission from within the ROM. SU does exist, just not where the shell is looking when in recovery.
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # ls /system/xbin
ls /system/xbin
ls: /system/xbin: No such file or directory
~ #
I did an ls /system/xbin from adb shell and from Terminal Emulator within Android and both returned a long list containing SU.

TWRP provides an unsecured (unsecure? insecure?) boot. Whatever the terminology, it gives you immediate access to root privileges. Apparently CWMR (which was used in the OP of the thread you used) does not and so that author had to use su. For TWRP, it's not necessary and not even available. You already have root privileges as indicated by the hash prompt.
I tried resizing my /sdcard partition and it worked fine with the command you tried. I'm not sure what's going on with your storage device that it wouldn't resize it for you. At first I thought it might be mounted, but your mount command shows otherwise and parted gave me a different error when I had it mounted.
I don't know if this is going to help you, but you might try giving it the "MB" suffix in your numbers....
Code:
resize 12 2846MB 7690MB
Maybe even try changing units to bytes and giving the resize command byte sized boundaries.
Code:
unit B
print
will show you the numbers in bytes and you'd have to use the "B" suffix as in the "MB" example above.
If none of that works, you can always remove and remake the partition. For example...
Code:
rm 12
mkpartfs primary fat32 <start> <end>
name 12 media
You'd obviously need to insert acceptable boundaries for the start and end into that command. It might even be easier to just remove all 9, 10, 11, and 12 and remake/rename them, but remember 9, 10, and 11 are ext4 filesystems so the above mkpartfs command needs to be tweaked accordingly.
One thing I noticed while I was experimenting with the partition table this morning... all of the existing partitions have been allocated in 128MB chunks. I have no idea if this affects performance. I'd imagine you'd only need to stick to the 512B sector sizes, but you might want to stay with those conventions if it's not too inconvenient for you.
If you mess up the partition table, you can always go back to fastboot mode in FFF and use the...
Code:
fastboot oem format
feature to bring your partition table back to stock.
Good luck.

Wow, excellent response. Just the kind of detail I was hoping to get and it confirmed a few suspicions I had while searching the kindle threads. I'll report back on my degree of success when I get some free time to tinker.
I have a nandroid backup (also saved to PC) just in case and saved the partition table as-found. If everything gets hosed and I do an oem format I can just restore that and go or try from square one again, yes?
Sent from my TBolt with the XDA App using 1 opposable thumb

ProfEngr said:
Wow, excellent response. Just the kind of detail I was hoping to get and it confirmed a few suspicions I had while searching the kindle threads. I'll report back on my degree of success when I get some free time to tinker.
I have a nandroid backup (also saved to PC) just in case and saved the partition table as-found. If everything gets hosed and I do an oem format I can just restore that and go or try from square one again, yes?
Sent from my TBolt with the XDA App using 1 opposable thumb
Click to expand...
Click to collapse
I'd say that's a safe bet. Just be very careful about handling partitions 1 and 2 because those two are critical to getting anything to boot on your device. As long as you don't touch the xloader in partition 1 and have FFF installed in partition 2, you can rebuild the rest of it.... in theory. I only say "in theory" because I've never actually had to do it, but I don't see why it wouldn't work.
A couple of additional things I figured out after you put me to work with parted....
It looks like parted doesn't know how to make an ext4 filesystem, so mkpartfs balks if you tell it to make one. You'll have to use mkpart which just makes the partition, but not the filesystem. Then exit out of parted and use mke2fs, which despite its name knows how to make an ext4 filesystem. Like this for the cache partition...
Code:
mke2fs -T ext4 /dev/block/mmcblk0p11
The other thing is that parted sets a "msftres" flag on the fat32 filesystem it makes. The flag apparently is to tell the OS that it's reserved for Windows, or something like that. I didn't have a problem mounting in Linux and MacOS X, but the stuff I've read seems to indicate that older OS's have a problem with it. Unfortunately, the version of busybox on TWRP doesn't have a module to make a fat32 filesystem. I'm looking around to see how to get around that.
In any case, this should get you most of the way there. I'll followup if I find something out.

Ok. I used to run n*x, but use only M$ right now. Haven't touched a 'mac' since Jr High (IIgs)
Sent from my TBolt with the XDA App using 1 opposable thumb

ProfEngr said:
Ok. I used to run n*x, but use only M$ right now. Haven't touched a 'mac' since Jr High (IIgs)
Sent from my TBolt with the XDA App using 1 opposable thumb
Click to expand...
Click to collapse
I have a IIgs sitting in the basement... but it's not a mac, it's an Apple ][.
Found the last piece...
Code:
/system/bin/newfs_msdos /dev/block/mmcblk0p12
will make a fat32 filesystem correctly. I think that's all you'll need.
EDIT: OK, I must have been half asleep when I posted the above. That binary is on the stock system software I had mounted. There's nothing on TWRP to create a fat32 filesystem correctly.

Yeah, ][e was my first computer that didn't crash at the drop of a keystroke. Had an Adam tape drive model, but it froze up constantly.
Sent from my TBolt with the XDA App using 1 opposable thumb

So, I met with success following the repartition thread and tweaking it with your suggestions. I didn't quite move and many MB around as I thought, but it was enough to move me a little farther down the road with SwitchMe. At least it doesn't tell me I don't have enough memory for a 2nd profile now.
I still think it has issues with ICS or EnergyROM itself. When I created a new profile and rebooted to it I was stuck on Nova launcher instead of GO like the main profile. Strange.
I'll consider this thread to have fulfilled its usefulness. Thanks again for the help.

no device found
ProfEngr said:
So, I met with success following the repartition thread and tweaking it with your suggestions. I didn't quite move and many MB around as I thought, but it was enough to move me a little farther down the road with SwitchMe. At least it doesn't tell me I don't have enough memory for a 2nd profile now.
I still think it has issues with ICS or EnergyROM itself. When I created a new profile and rebooted to it I was stuck on Nova launcher instead of GO like the main profile. Strange.
I'll consider this thread to have fulfilled its usefulness. Thanks again for the help.
Click to expand...
Click to collapse
I get
(parted)
Error: No device found
Retry/Cancel

Unable to mount data & cache

Hi all, got my kindle fire brick. I think my partition is messed up. I bought a factory cable which able me to install twrp and i succefully(i guess) flashed energy ICS. But it prompt me "e:unable to mount '/data" e:unable to mount '/cache". I were to boot to normal boot it will just boot endlessly but i still can access to fff and twrp.i did some research on repartitioning for kindle fire but i need some guidance. Help is much appreciated
Sent from my GT-I9100 using xda app-developers app

Usually this is a fairly bad indication but do this go to the mount section in twrp and make sure there are no checks in the boxes of data and system if so uncheck them, I know you said data and cache but this should have a check in the box then try a reboot also were you previously using cwmr? If so you may have been bitten by the bug a very unsightly one that generally means the death of your kindle unless you know how to repartition around a broken emmc. What did you do prior to this that caused this to happen?
Also energy is not the best for good mounting just saying...

I was using fireparted to backup my partition when my pc suddenly shut down. Thats when everything screws up. Also my data and cache are not able to check or uncheck. I hope theres a kind soul to guide me through this process
Sent from my GT-I9100 using xda app-developers app

If you ask me I would say its toast but maybe someone knows a way to restore factory partitions I know many are looking for a solution for thier parts only kindle....

From what I understand...
Code:
fastboot oem format
...will rewrite your partition table to stock. And as long as you haven't messed with the partition sizes, your data will stay intact.
Enter:
Code:
shell cat /proc/partitions
To get a list of your current partitions and sizes to check to see if they even exist to begin with. And if so, it's likely just a case of broken or missing mountpoints.
Now, whether or not "fastboot oem format" will restore broken or missing mountpoints, I couldn't tell you for sure; I've never had to try it. But in your situation, it probably couldn't hurt to try.
You can also recreate mountpoints manually if needed.
[Edit:] It has just been explained to me that "fastboot oem format" won't do anything about mountpoints.

Assuming you can get into TWRP and run adb shell, execute the following command...
Code:
adb shell parted /dev/block/mmcblk0 unit b print
Note: version 2.2.0 is missing the parted binary, so you'll need to use 2.1.1
This will give you a detailed layout of your storage device and the filesystems for each partition. I'm running from memory here, but the right column should show the filesystem types it sees for that particular partition. For userdata (which is mounted as data) and cache, those should be ext4. If you don't see that, you need to remake those partitions.
Code:
adb shell mke2fs -T ext4 /dev/block/mmcblk0p10
adb shell mke2fs -T ext4 /dev/block/mmcblk0p11
Then you can repeat the parted command above and see if the commands worked. If the commands were successful, you can use the mount command or it's probably easier to just reboot into TWRP and it should do it automatically.

kinfauns said:
Assuming you can get into TWRP and run adb shell, execute the following command...
Code:
adb shell parted /dev/block/mmcblk0 unit b print
Note: version 2.2.0 is missing the parted binary, so you'll need to use 2.1.1
This will give you a detailed layout of your storage device and the filesystems for each partition. I'm running from memory here, but the right column should show the filesystem types it sees for that particular partition. For userdata (which is mounted as data) and cache, those should be ext4. If you don't see that, you need to remake those partitions.
Code:
adb shell mke2fs -T ext4 /dev/block/mmcblk0p10
adb shell mke2fs -T ext4 /dev/block/mmcblk0p11
Then you can repeat the parted command above and see if the commands worked. If the commands were successful, you can use the mount command or it's probably easier to just reboot into TWRP and it should do it automatically.
Click to expand...
Click to collapse
Pardon me for my Noob-ness, are the code to be execute on pc or on TWRP?

dean11 said:
Pardon me for my Noob-ness, are the code to be execute on pc or on TWRP?
Click to expand...
Click to collapse
Step back a bit and figure out how all of these things work together by reading the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
It will be a lot easier for you to understand what you are doing and why you are doing them. It will also explain how and where to run the commands.

kinfauns said:
Step back a bit and figure out how all of these things work together by reading the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
It will be a lot easier for you to understand what you are doing and why you are doing them. It will also explain how and where to run the commands.
Click to expand...
Click to collapse
OH MY GOOOOD!!!! MY KINDLE IS ALIVE!!!! THANK YOU SO MUCH @kinfauns!

kinfauns said:
Assuming you can get into TWRP and run adb shell, execute the following command...
Code:
adb shell parted /dev/block/mmcblk0 unit b print
Note: version 2.2.0 is missing the parted binary, so you'll need to use 2.1.1
This will give you a detailed layout of your storage device and the filesystems for each partition. I'm running from memory here, but the right column should show the filesystem types it sees for that particular partition. For userdata (which is mounted as data) and cache, those should be ext4. If you don't see that, you need to remake those partitions.
Code:
adb shell mke2fs -T ext4 /dev/block/mmcblk0p10
adb shell mke2fs -T ext4 /dev/block/mmcblk0p11
Then you can repeat the parted command above and see if the commands worked. If the commands were successful, you can use the mount command or it's probably easier to just reboot into TWRP and it should do it automatically.
Click to expand...
Click to collapse
I have the similar situation.
And when I use "parted" to check my kidle partition, there is no cache, and the userdata is ext2.
Number Start End Size File system Name Flags
1 131072B 262143B 131072B xloader
2 262144B 524287B 262144B bootloader
3 524288B 11010047B 10485760B dkernel
4 11010048B 212336639B 201326592B ext4 dfs
5 212336640B 229113855B 16777216B recovery
6 229113856B 296222719B 67108864B ext4 backup
7 296222720B 306708479B 10485760B boot
8 306708480B 311951359B 5242880B ext4 splash
9 311951360B 848822271B 536870912B ext4 system
10 848822272B 849000447B 178176B ext2 userdata
12 2448000000B 7748000255B 5300000256B fat32 media msftres
When I use the mke2fs to change the file system type, it returns this error
Not enough space to build proposed filesystem while setting up superblock.
Please help!
Thank you in advance!

june12 said:
I have the similar situation.
And when I use "parted" to check my kidle partition, there is no cache, and the userdata is ext2.
Number Start End Size File system Name Flags
1 131072B 262143B 131072B xloader
2 262144B 524287B 262144B bootloader
3 524288B 11010047B 10485760B dkernel
4 11010048B 212336639B 201326592B ext4 dfs
5 212336640B 229113855B 16777216B recovery
6 229113856B 296222719B 67108864B ext4 backup
7 296222720B 306708479B 10485760B boot
8 306708480B 311951359B 5242880B ext4 splash
9 311951360B 848822271B 536870912B ext4 system
10 848822272B 849000447B 178176B ext2 userdata
12 2448000000B 7748000255B 5300000256B fat32 media msftres
When I use the mke2fs to change the file system type, it returns this error
Not enough space to build proposed filesystem while setting up superblock.
Please help!
Thank you in advance!
Click to expand...
Click to collapse
I don't know who or what did that to your partition table, but partitions 10-12 are not right. It looks like mke2fs is complaining because your userdata partition is only ~178KB. I'm also a bit concerned that you've extended the media partition as far as you have. You might have some additional problems there.
The easiest way for you to get started on a fix is to get into fastboot mode with FFF and run...
Code:
fastboot oem format
That will bring your partition table back to stock, so you can run those mke2fs commands to remake those filesystems on the two partitions. You'll also have to remake the media partition in parted. You can find some instructions on how to do that here...
http://forum.xda-developers.com/showthread.php?t=1658885

Hey,
My current ROM is fine, but I can't mount data & cache in TWRP.
Nothing happens when I click mount data or mount cache in TWRP 2.6.3.1
I reflashed twrp two times and checked the md5sum.
When I try to backup my rom:
When I try a factory reset:
This is what I tried in fastboot:
Code:
fastboot oem format
...
OKAY [ 0.064s]
finished. total time: 0.065s
fastboot oem idme bootmode 4000
...
OKAY [ 0.081s]
finished. total time: 0.081s
fastboot reboot
rebooting...
finished. total time: -0.000s
adb shell cat /proc/partitions
major minor #blocks name
7 0 8348 loop0
179 0 7553024 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 196608 mmcblk0p4
179 5 16384 mmcblk0p5
179 6 65536 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 524288 mmcblk0p9
179 10 1164288 mmcblk0p10
179 11 262144 mmcblk0p11
179 12 5254144 mmcblk0p12
179 64 512 mmcblk0boot1
179 32 512 mmcblk0boot0
254 0 8347 dm-0
The parted command isn't working for me.
I have never repartitioned them as far as I know.
Wha't wrong with my partitions?

Any alternative for flashing a recovery?

I'm using the U.S. Glide running dmans cm10.1 with the Aquethys touch CWM recovery and I have messed up my USB Port and cannot transfer any data what so ever. I decided to explore alternatives to update the recovery and I found the flash_image command to be the best option as I was unable generate a cwm flashable zip from the Odin tar file (a bit too complexed for me (I have a windows pc)) and while attempting the command flash_image recovery /sdcard/recovery. Img in the phones terminal (image extracted from the new cwm built from source (great job guys!!!!)) and got a partition error and after more research found this to be a common error with people with phones containing the Emmc layout. But of course no solutions presented themselves without needing a solid USB connection. Any help or troublshooting would be appreciated! Other routes included fastboot interface but I don't think this phone uses it (correct me if I'm wrong )
Sent from my SGH-I927

wat about twrp recovery... u can find it on the goomanager app

You should try the nontouch version of cwmr. I've heard several people running into similar problems as you with the touch version.
Sent form my SGH-i927 running dman's cm10.1

Right but how do I flash it without a functional USB Port?
Sent from my SGH-I927 using xda premium

Cprager said:
Right but how do I flash it without a functional USB Port?
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
Connect your phone and laptop to your wifi.
Goto Settings developer options - turn on "ADB over netwrok"
adb connect 192.168.x.x:5555
Now follow this http://forum.xda-developers.com/showthread.php?t=1630519 . Replce the .img file with the glide verison of recovery.
The above should work for you, though i've not tried it myself.

awesome, I will attempt this today and report back.

Cprager said:
awesome, I will attempt this today and report back.
Click to expand...
Click to collapse
adb push recovery.img /data/local/
adb push flash_image /data/local/
(Permission denied, copied files to sdcard and then through phone moved to /data/local)
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
(Operation not permitted, I then decided to run the following commands:
adb shell
su
chmod 777 /data/local/recovery.img
chmod 777 /data/local/flash_image
no errors listed, it seemed to function)
adb shell rm /data/local/rights/mid.txt
(rm failed for /data/local/rights/mid.txt, no such file or directory)
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
(sh: syntax error: 'in' unexpected)
adb reboot
adb shell /data/local/flash_image recovery /data/local/recovery.img
(error scanning partitions: No such file or directory (seems like its failing because it doesn't know where the recovery partition is located maybe a DD command with the correct block containing the recovery partition??)
(I also tried the above in a root adb shell with the same error being encountered)

greeneyez15o said:
wat about twrp recovery... u can find it on the goomanager app
Click to expand...
Click to collapse
And what version of twrp did you flash and for what device to work on the glide? Without smashing your partitions..
Sent from my SGH-I927 using xda premium

Cprager said:
adb push recovery.img /data/local/
adb push flash_image /data/local/
(Permission denied, copied files to sdcard and then through phone moved to /data/local)
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
(Operation not permitted, I then decided to run the following commands:
adb shell
su
chmod 777 /data/local/recovery.img
chmod 777 /data/local/flash_image
no errors listed, it seemed to function)
adb shell rm /data/local/rights/mid.txt
(rm failed for /data/local/rights/mid.txt, no such file or directory)
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
(sh: syntax error: 'in' unexpected)
adb reboot
adb shell /data/local/flash_image recovery /data/local/recovery.img
(error scanning partitions: No such file or directory (seems like its failing because it doesn't know where the recovery partition is located maybe a DD command with the correct block containing the recovery partition??)
(I also tried the above in a root adb shell with the same error being encountered)
Click to expand...
Click to collapse
Try this :
Adb shell
Su
Change to the directory you have your img file in.
./flash_image recovery filexxxxxxx.img
Sent from my SGH-I927 using xda app-developers app
---------- Post added at 10:09 PM ---------- Previous post was at 09:47 PM ----------
ninthsense said:
Try this :
Adb shell
Su
Change to the directory you have your img file in.
./flash_image recovery filexxxxxxx.img
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
You can also try doing the same from inside a terminal emulator app from within the CM10. Just found out that CM10 comes with flash_image already loaded.
Sent from my SGH-I927 using xda app-developers app

ninthsense said:
Try this :
Adb shell
Su
Change to the directory you have your img file in.
./flash_image recovery filexxxxxxx.img
Sent from my SGH-I927 using xda app-developers app
---------- Post added at 10:09 PM ---------- Previous post was at 09:47 PM ----------
You can also try doing the same from inside a terminal emulator app from within the CM10. Just found out that CM10 comes with flash_image already loaded.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Just attempted the following:
adb shell
su
cd /data/local
./flash_image recovery recovery.img
"error scanning partitions: No such file or directory" I am getting the exact same error through the terminal

Cprager said:
Just attempted the following:
adb shell
su
cd /data/local
./flash_image recovery recovery.img
"error scanning partitions: No such file or directory" I am getting the exact same error through the terminal
Click to expand...
Click to collapse
drop the "./" just try "flash_image recovery recovery.img" from the terminal. Remember to be "su" and in the same directory where the recovery.img is.

ninthsense said:
drop the "./" just try "flash_image recovery recovery.img" from the terminal. Remember to be "su" and in the same directory where the recovery.img is.
Click to expand...
Click to collapse
Ok, I just did the revised commands and got a different error output:
opened terminal:
su
cd /data/local (the directory where flash_image and the recovery.img are located)
flash_image recovery recovery.img
"failed with error: -1"
I believe the Flash_image cannot find the partition housing the current recovery but am unable/don't know how to find the correct partiton
but assuming the correct one is found, do you think the below command would be a viable option?
dd if=/data/local/recovery.img of=/dev/block/mmcblk0xxxxx

Cprager said:
Ok, I just did the revised commands and got a different error output:
opened terminal:
su
cd /data/local (the directory where flash_image and the recovery.img are located)
flash_image recovery recovery.img
"failed with error: -1"
I believe the Flash_image cannot find the partition housing the current recovery but am unable/don't know how to find the correct partiton
but assuming the correct one is found, do you think the below command would be a viable option?
dd if=/data/local/recovery.img of=/dev/block/mmcblk0xxxxx
Click to expand...
Click to collapse
Delete the flash_image you've downloaded and run the command again. The flash_image is inbuilt in CM10, so i guess using that one makes more sense.
Also rename the .img file to recovery .img and place it in the root of your sdcard and issue the following command :
su
flash_image recovery /sdcard/recovery.img

ninthsense said:
Delete the flash_image you've downloaded and run the command again. The flash_image is inbuilt in CM10, so i guess using that one makes more sense.
Also rename the .img file to recovery .img and place it in the root of your sdcard and issue the following command :
su
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Same error, "failed with error: -1"

ninthsense, dd'ing the image as he said should work, something like
dd if=/path/to/cwm/boot.img of=/dev/block/mmcblk0pX
But you'll have to do some digging to figure out what X is. Flash CWM the normal way, then head boot.img and each mmcblk0pX and find the one that's identical.
And DON'T just guess; flashing the wrong partition can brick your phone.

roothorick said:
ninthsense, dd'ing the image as he said should work, something like
dd if=/path/to/cwm/boot.img of=/dev/block/mmcblk0pX
But you'll have to do some digging to figure out what X is. Flash CWM the normal way, then head boot.img and each mmcblk0pX and find the one that's identical.
And DON'T just guess; flashing the wrong partition can brick your phone.
Click to expand...
Click to collapse
didn't suggested cause i don't know the values for those xxx myself and don't want him to end up wiping/briking his phone.

ninthsense said:
didn't suggested cause i don't know the values for those xxx myself and don't want him to end up wiping/briking his phone.
Click to expand...
Click to collapse
I appreciate the concern gentlemen! i definately WILL NOT execute a command without knowing full well its purpose.
Im a PC guy so this linux command stuff is a bit newer to me, that being said, there must be a way (command) to see the partitions?
**I have currently the touch CWM so if you need me to "then head boot.img and each mmcblk0pX" to find the one thats identical I may be able to do so.
edit** don't know if this helps
cat /proc/partitions
major minor #blocks name
179 0 7552000 mmcblk0
179 1 12288 mmcblk0p1
179 2 614400 mmcblk0p2
179 3 319488 mmcblk0p3
179 4 3932672 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2097152 mmcblk0p6
179 7 16384 mmcblk0p7
259 0 5120 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 8192 mmcblk0p10
259 3 524288 mmcblk0p11
179 16 512 mmcblk0boot1
179 8 512 mmcblk0boot0
179 24 7786496 mmcblk1
179 25 7785472 mmcblk1p1

Cprager said:
I appreciate the concern gentlemen! i definately WILL NOT execute a command without knowing full well its purpose.
Im a PC guy so this linux command stuff is a bit newer to me, that being said, there must be a way (command) to see the partitions?
**I have currently the touch CWM so if you need me to "then head boot.img and each mmcblk0pX" to find the one thats identical I may be able to do so.
Click to expand...
Click to collapse
Nothing really, besides just ls /dev/block/mmcblk0p*
Phone partitions are quite a bit different from computer partitions -- about half the partitions don't even have filesystems; the entire partition is dedicated to some image that is important to one thing or the other.
I've got a pretty good overview of the CGlide ICS partitions here: http://forum.xda-developers.com/showthread.php?t=2051327

From my touch recovery logs
Starting recovery on Fri Dec 28 19:23:18 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v6.0.0.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p9 (null) 0
2 /cache ext4 /dev/block/mmcblk0p3 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /recovery emmc /dev/block/mmcblk0p8 (null) 0
5 /sdcard vfat /dev/block/mmcblk0p4 /dev/block/mmcblk0 0
6 /system ext4 /dev/block/mmcblk0p2 (null) 0
7 /efs ext4 /dev/block/mmcblk0p1 (null) 0
Note : I would advise you to pull out the file system into a .img file and keep the backup before flashing it with recover.img. Jsut in case you need to restore back to the original state

ninthsense said:
From my touch recovery logs
Starting recovery on Fri Dec 28 19:23:18 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v6.0.0.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p9 (null) 0
2 /cache ext4 /dev/block/mmcblk0p3 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /recovery emmc /dev/block/mmcblk0p8 (null) 0
5 /sdcard vfat /dev/block/mmcblk0p4 /dev/block/mmcblk0 0
6 /system ext4 /dev/block/mmcblk0p2 (null) 0
7 /efs ext4 /dev/block/mmcblk0p1 (null) 0
Note : I would advise you to pull out the file system into a .img file and keep the backup before flashing it with recover.img. Jsut in case you need to restore back to the original state
Click to expand...
Click to collapse
YOU GUYS ROCK !!!!!
I understand the procedure for replacing the previous recovery with the new recovery.img through the DD command,
but am unsure how to backup the current one. I will do more research and run my procedure by you guys before attempting anything
**edit**
to backup:
dd if=/dev/block/mmcblk0p8 of=/sdcard/current-recovery.img
to flash new recovery:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p8
there was an attribute listed bs=4096 (maybe bit size??)
please let me know if my commands are correct, and I will give it a go (fingers crossed lol)

[Q]HOX Stuck on quietly brilliant screen

I put ARHD ROM and everything was fine, until i put Fonter module and changed font and then HOX stuck at quietly brilliant screen..
I was in panic and i wiped everything, and sdcard, and data, and system, everything.. And then i f**** up all..
So now i can go into recovery, i can go in fastboot, everything is working, just i cannot get sdcard to work. I think that it should be formatted but it won't work.. I tried several ways that i googled and on every i stuck
I tried put TWRP but it stuck on swipe to unlock and it won't work, i tried several versions, still nothing..
I tried this How to: Fix a corrupted DATA partition on the HTC One on ARHD webpage ( I cannot put links )
And when i put this
Code:
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
It say
Code:
Could not stat /dev/block/mmcblk0p37 --- No such file or directory
Then i tried this
Code:
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Once all that's done, your recovery program should be able to mount both the /data and /cache partitions. If that's true, you're pretty much done! One thing I found was that I couldn't directly install a new OS (I tried both Cyanogen and Ultimate). In both cases, it would look for stuff in the davik-cache that it couldn't find, so something wasn't installing correctly I think. So, if that happens, flash back to the stock PB31IMG.zip (put it in the root of your /sdcard/ and let hboot install it), and then root your phone anew. That's what I ended up doing.
Again, huge credit for this goes to -Steveo- and ciwrl for helping me figure out which partitions were the right ones (and for supplying parted, which I hadn't been able to find anywhere). If something doesn't end up working, just drop me a pm and we'll see what we can do.
And here it wont when i put command
Code:
parted /dev/block/mmcblk0 mkfs ext2
it say
Code:
Error: /dev/block/mmcblk0: unrecognised disk label
But when i do this
Code:
fdisk -l /dev/block/mmcblk0
it say
Code:
Disk /dev/block/mmcblk0: 31.2 GB, 31268536320 bytes
4 heads, 16 sectors/track, 954240 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
I am sorry for bad english, but i really need help, i were searching the web for 10hours and nothing worked.. I need to full format sdcard, so could anyone help me?
Thanks

Please help someone, i need my phone

So nobody wants to help me??

lepi991 said:
So nobody wants to help me??
Click to expand...
Click to collapse
Flash Philz recovery 5.15.9 and mount sd card search in Q&A section I sheared via google drive

I tried that and when i go to Mount SD card it give me only to choose UnMount

lepi991 said:
I tried that and when i go to Mount SD card it give me only to choose UnMount
Click to expand...
Click to collapse
un mount and mount and wait 2 minutes or unmount and wait 2 minutes work with sure on 5.15.9

That didnt worked, when i enter sd card there is only unmount and when i choose that nothing happend..
Finnaly i fixed with busybox and formated card completely and then through adb shell pushed ROM and installed it..
You can lock thread